diff --git a/assets/images/help/codespaces/CSV-usage-report.png b/assets/images/help/codespaces/CSV-usage-report.png
new file mode 100644
index 0000000000..09a6048b72
Binary files /dev/null and b/assets/images/help/codespaces/CSV-usage-report.png differ
diff --git a/assets/images/help/codespaces/exported-codespace-secret.png b/assets/images/help/codespaces/exported-codespace-secret.png
new file mode 100644
index 0000000000..9e8f55f5c4
Binary files /dev/null and b/assets/images/help/codespaces/exported-codespace-secret.png differ
diff --git a/assets/images/help/education/community-exchange-repo-submission-offers.png b/assets/images/help/education/community-exchange-repo-submission-offers.png
new file mode 100644
index 0000000000..f13dcd8231
Binary files /dev/null and b/assets/images/help/education/community-exchange-repo-submission-offers.png differ
diff --git a/assets/images/help/education/community-exchange-repo-submission-purpose.png b/assets/images/help/education/community-exchange-repo-submission-purpose.png
new file mode 100644
index 0000000000..2c8c22755c
Binary files /dev/null and b/assets/images/help/education/community-exchange-repo-submission-purpose.png differ
diff --git a/assets/images/help/education/community-exchange-repo-submission-repo.png b/assets/images/help/education/community-exchange-repo-submission-repo.png
new file mode 100644
index 0000000000..e30f2034af
Binary files /dev/null and b/assets/images/help/education/community-exchange-repo-submission-repo.png differ
diff --git a/assets/images/help/education/community-exchange-search-and-filter.png b/assets/images/help/education/community-exchange-search-and-filter.png
new file mode 100644
index 0000000000..a3240b92d9
Binary files /dev/null and b/assets/images/help/education/community-exchange-search-and-filter.png differ
diff --git a/assets/images/help/education/community-exchange-submission-add-repo.png b/assets/images/help/education/community-exchange-submission-add-repo.png
new file mode 100644
index 0000000000..54012b80aa
Binary files /dev/null and b/assets/images/help/education/community-exchange-submission-add-repo.png differ
diff --git a/assets/images/help/education/community-exchange-submissions-tab.png b/assets/images/help/education/community-exchange-submissions-tab.png
new file mode 100644
index 0000000000..4b63b491ab
Binary files /dev/null and b/assets/images/help/education/community-exchange-submissions-tab.png differ
diff --git a/assets/images/help/enterprises/audit-data-retention-tab.png b/assets/images/help/enterprises/audit-data-retention-tab.png
new file mode 100644
index 0000000000..7917192512
Binary files /dev/null and b/assets/images/help/enterprises/audit-data-retention-tab.png differ
diff --git a/assets/images/help/enterprises/audit-log-retention-dropdown.png b/assets/images/help/enterprises/audit-log-retention-dropdown.png
new file mode 100644
index 0000000000..9bde6511a8
Binary files /dev/null and b/assets/images/help/enterprises/audit-log-retention-dropdown.png differ
diff --git a/assets/images/help/enterprises/enable-git-events-checkbox.png b/assets/images/help/enterprises/enable-git-events-checkbox.png
new file mode 100644
index 0000000000..a80196bdac
Binary files /dev/null and b/assets/images/help/enterprises/enable-git-events-checkbox.png differ
diff --git a/assets/images/help/issues/migrate-menu-item.png b/assets/images/help/issues/migrate-menu-item.png
new file mode 100644
index 0000000000..db189ea475
Binary files /dev/null and b/assets/images/help/issues/migrate-menu-item.png differ
diff --git a/assets/images/help/issues/migrate-option.png b/assets/images/help/issues/migrate-option.png
index 000c38f814..b82f0de40c 100644
Binary files a/assets/images/help/issues/migrate-option.png and b/assets/images/help/issues/migrate-option.png differ
diff --git a/assets/images/help/issues/migrate-to-beta.png b/assets/images/help/issues/migrate-to-beta.png
deleted file mode 100644
index d2509a67e8..0000000000
Binary files a/assets/images/help/issues/migrate-to-beta.png and /dev/null differ
diff --git a/assets/images/help/issues/project_side_bar.png b/assets/images/help/issues/project_side_bar.png
deleted file mode 100644
index 60f9ad26fb..0000000000
Binary files a/assets/images/help/issues/project_side_bar.png and /dev/null differ
diff --git a/assets/images/help/issues/projects-beta-assign-button.png b/assets/images/help/issues/projects-beta-assign-button.png
deleted file mode 100644
index fb2d23e8ca..0000000000
Binary files a/assets/images/help/issues/projects-beta-assign-button.png and /dev/null differ
diff --git a/assets/images/help/issues/projects-beta-assign-dropdown.png b/assets/images/help/issues/projects-beta-assign-dropdown.png
deleted file mode 100644
index 66fffb8f6d..0000000000
Binary files a/assets/images/help/issues/projects-beta-assign-dropdown.png and /dev/null differ
diff --git a/assets/images/help/issues/projects-classic-org.png b/assets/images/help/issues/projects-classic-org.png
index 8a9b474691..461b5d77c0 100644
Binary files a/assets/images/help/issues/projects-classic-org.png and b/assets/images/help/issues/projects-classic-org.png differ
diff --git a/assets/images/help/issues/projects-classic-user.png b/assets/images/help/issues/projects-classic-user.png
index 0f628bb786..47131211cd 100644
Binary files a/assets/images/help/issues/projects-classic-user.png and b/assets/images/help/issues/projects-classic-user.png differ
diff --git a/assets/images/help/pages/unpublish-site.png b/assets/images/help/pages/unpublish-site.png
new file mode 100644
index 0000000000..50647f357d
Binary files /dev/null and b/assets/images/help/pages/unpublish-site.png differ
diff --git a/assets/images/help/projects-v2/access-change-role.png b/assets/images/help/projects-v2/access-change-role.png
new file mode 100644
index 0000000000..1e9035927d
Binary files /dev/null and b/assets/images/help/projects-v2/access-change-role.png differ
diff --git a/assets/images/help/projects-v2/access-find-member.png b/assets/images/help/projects-v2/access-find-member.png
new file mode 100644
index 0000000000..42e8dd643e
Binary files /dev/null and b/assets/images/help/projects-v2/access-find-member.png differ
diff --git a/assets/images/help/projects-v2/access-invite.png b/assets/images/help/projects-v2/access-invite.png
new file mode 100644
index 0000000000..e944c7d1ae
Binary files /dev/null and b/assets/images/help/projects-v2/access-invite.png differ
diff --git a/assets/images/help/projects-v2/access-remove-member.png b/assets/images/help/projects-v2/access-remove-member.png
new file mode 100644
index 0000000000..4cbc0cde9e
Binary files /dev/null and b/assets/images/help/projects-v2/access-remove-member.png differ
diff --git a/assets/images/help/projects-v2/access-role.png b/assets/images/help/projects-v2/access-role.png
new file mode 100644
index 0000000000..5ed6e7ea56
Binary files /dev/null and b/assets/images/help/projects-v2/access-role.png differ
diff --git a/assets/images/help/projects-v2/access-search.png b/assets/images/help/projects-v2/access-search.png
new file mode 100644
index 0000000000..e4ba4a5542
Binary files /dev/null and b/assets/images/help/projects-v2/access-search.png differ
diff --git a/assets/images/help/projects-v2/add-bulk-menu-item.png b/assets/images/help/projects-v2/add-bulk-menu-item.png
new file mode 100644
index 0000000000..f7587853de
Binary files /dev/null and b/assets/images/help/projects-v2/add-bulk-menu-item.png differ
diff --git a/assets/images/help/projects-v2/add-bulk-save.png b/assets/images/help/projects-v2/add-bulk-save.png
new file mode 100644
index 0000000000..c9c9e01ee3
Binary files /dev/null and b/assets/images/help/projects-v2/add-bulk-save.png differ
diff --git a/assets/images/help/projects-v2/add-bulk-select-issues.png b/assets/images/help/projects-v2/add-bulk-select-issues.png
new file mode 100644
index 0000000000..17326af6f9
Binary files /dev/null and b/assets/images/help/projects-v2/add-bulk-select-issues.png differ
diff --git a/assets/images/help/projects-v2/add-bulk-select-repo.png b/assets/images/help/projects-v2/add-bulk-select-repo.png
new file mode 100644
index 0000000000..17fe064c6c
Binary files /dev/null and b/assets/images/help/projects-v2/add-bulk-select-repo.png differ
diff --git a/assets/images/help/projects-v2/add-draft-issue.png b/assets/images/help/projects-v2/add-draft-issue.png
new file mode 100644
index 0000000000..3a85f9ba17
Binary files /dev/null and b/assets/images/help/projects-v2/add-draft-issue.png differ
diff --git a/assets/images/help/projects-v2/add-item-select-issue.png b/assets/images/help/projects-v2/add-item-select-issue.png
new file mode 100644
index 0000000000..80bb4eb283
Binary files /dev/null and b/assets/images/help/projects-v2/add-item-select-issue.png differ
diff --git a/assets/images/help/projects-v2/add-item-select-repo.png b/assets/images/help/projects-v2/add-item-select-repo.png
new file mode 100644
index 0000000000..f980aa879d
Binary files /dev/null and b/assets/images/help/projects-v2/add-item-select-repo.png differ
diff --git a/assets/images/help/projects-v2/add-item.png b/assets/images/help/projects-v2/add-item.png
new file mode 100644
index 0000000000..304b27362b
Binary files /dev/null and b/assets/images/help/projects-v2/add-item.png differ
diff --git a/assets/images/help/projects-v2/add-iteration-options.png b/assets/images/help/projects-v2/add-iteration-options.png
new file mode 100644
index 0000000000..277e4e5a60
Binary files /dev/null and b/assets/images/help/projects-v2/add-iteration-options.png differ
diff --git a/assets/images/help/projects-v2/add-iteration.png b/assets/images/help/projects-v2/add-iteration.png
new file mode 100644
index 0000000000..68e0239387
Binary files /dev/null and b/assets/images/help/projects-v2/add-iteration.png differ
diff --git a/assets/images/help/projects-v2/add-to-repo-button.png b/assets/images/help/projects-v2/add-to-repo-button.png
new file mode 100644
index 0000000000..acbfe0b4e0
Binary files /dev/null and b/assets/images/help/projects-v2/add-to-repo-button.png differ
diff --git a/assets/images/help/projects-v2/add-to-repo-search.png b/assets/images/help/projects-v2/add-to-repo-search.png
new file mode 100644
index 0000000000..3f085c06f7
Binary files /dev/null and b/assets/images/help/projects-v2/add-to-repo-search.png differ
diff --git a/assets/images/help/projects-v2/add-to-repo.png b/assets/images/help/projects-v2/add-to-repo.png
new file mode 100644
index 0000000000..11bdb13d77
Binary files /dev/null and b/assets/images/help/projects-v2/add-to-repo.png differ
diff --git a/assets/images/help/projects-v2/archive-item-prompt.png b/assets/images/help/projects-v2/archive-item-prompt.png
new file mode 100644
index 0000000000..96e538f0ab
Binary files /dev/null and b/assets/images/help/projects-v2/archive-item-prompt.png differ
diff --git a/assets/images/help/projects-v2/archive-menu-item.png b/assets/images/help/projects-v2/archive-menu-item.png
new file mode 100644
index 0000000000..1334383c81
Binary files /dev/null and b/assets/images/help/projects-v2/archive-menu-item.png differ
diff --git a/assets/images/help/projects-v2/archived-items-menu-item.png b/assets/images/help/projects-v2/archived-items-menu-item.png
new file mode 100644
index 0000000000..126366ad91
Binary files /dev/null and b/assets/images/help/projects-v2/archived-items-menu-item.png differ
diff --git a/assets/images/help/projects-v2/base-role.png b/assets/images/help/projects-v2/base-role.png
new file mode 100644
index 0000000000..040cfaae67
Binary files /dev/null and b/assets/images/help/projects-v2/base-role.png differ
diff --git a/assets/images/help/projects-v2/column-field-menu-item.png b/assets/images/help/projects-v2/column-field-menu-item.png
new file mode 100644
index 0000000000..c595dbda99
Binary files /dev/null and b/assets/images/help/projects-v2/column-field-menu-item.png differ
diff --git a/assets/images/help/projects-v2/column-field-menu.png b/assets/images/help/projects-v2/column-field-menu.png
new file mode 100644
index 0000000000..42ef78b338
Binary files /dev/null and b/assets/images/help/projects-v2/column-field-menu.png differ
diff --git a/assets/images/help/projects-v2/convert-to-issue-select-repo.png b/assets/images/help/projects-v2/convert-to-issue-select-repo.png
new file mode 100644
index 0000000000..b60dba20ba
Binary files /dev/null and b/assets/images/help/projects-v2/convert-to-issue-select-repo.png differ
diff --git a/assets/images/help/projects-v2/default-workflows.png b/assets/images/help/projects-v2/default-workflows.png
new file mode 100644
index 0000000000..7bd1ad21ab
Binary files /dev/null and b/assets/images/help/projects-v2/default-workflows.png differ
diff --git a/assets/images/help/projects-v2/delete-field.png b/assets/images/help/projects-v2/delete-field.png
new file mode 100644
index 0000000000..06b7d2caba
Binary files /dev/null and b/assets/images/help/projects-v2/delete-field.png differ
diff --git a/assets/images/help/projects-v2/delete-item-prompt.png b/assets/images/help/projects-v2/delete-item-prompt.png
new file mode 100644
index 0000000000..d08b136361
Binary files /dev/null and b/assets/images/help/projects-v2/delete-item-prompt.png differ
diff --git a/assets/images/help/projects-v2/delete-menu-item.png b/assets/images/help/projects-v2/delete-menu-item.png
new file mode 100644
index 0000000000..dc8fa19e29
Binary files /dev/null and b/assets/images/help/projects-v2/delete-menu-item.png differ
diff --git a/assets/images/help/projects-v2/delete-view.png b/assets/images/help/projects-v2/delete-view.png
new file mode 100644
index 0000000000..972c1aa865
Binary files /dev/null and b/assets/images/help/projects-v2/delete-view.png differ
diff --git a/assets/images/help/projects-v2/disable-insights-checkbox.png b/assets/images/help/projects-v2/disable-insights-checkbox.png
new file mode 100644
index 0000000000..8edadc91cb
Binary files /dev/null and b/assets/images/help/projects-v2/disable-insights-checkbox.png differ
diff --git a/assets/images/help/projects-v2/disable-insights-save.png b/assets/images/help/projects-v2/disable-insights-save.png
new file mode 100644
index 0000000000..af9f98cc26
Binary files /dev/null and b/assets/images/help/projects-v2/disable-insights-save.png differ
diff --git a/assets/images/help/projects-v2/duplicate-view.png b/assets/images/help/projects-v2/duplicate-view.png
new file mode 100644
index 0000000000..df93335cf3
Binary files /dev/null and b/assets/images/help/projects-v2/duplicate-view.png differ
diff --git a/assets/images/help/projects-v2/edit-description.png b/assets/images/help/projects-v2/edit-description.png
new file mode 100644
index 0000000000..ac5ce06f97
Binary files /dev/null and b/assets/images/help/projects-v2/edit-description.png differ
diff --git a/assets/images/help/projects-v2/edit-readme.png b/assets/images/help/projects-v2/edit-readme.png
new file mode 100644
index 0000000000..bd56e455d8
Binary files /dev/null and b/assets/images/help/projects-v2/edit-readme.png differ
diff --git a/assets/images/help/projects-v2/features-org-menu.png b/assets/images/help/projects-v2/features-org-menu.png
new file mode 100644
index 0000000000..98b51746c3
Binary files /dev/null and b/assets/images/help/projects-v2/features-org-menu.png differ
diff --git a/assets/images/help/projects-v2/field-options.png b/assets/images/help/projects-v2/field-options.png
new file mode 100644
index 0000000000..c463fab9ce
Binary files /dev/null and b/assets/images/help/projects-v2/field-options.png differ
diff --git a/assets/images/help/projects-v2/field-rename.png b/assets/images/help/projects-v2/field-rename.png
new file mode 100644
index 0000000000..efbd9a5ce4
Binary files /dev/null and b/assets/images/help/projects-v2/field-rename.png differ
diff --git a/assets/images/help/projects-v2/group-menu-item.png b/assets/images/help/projects-v2/group-menu-item.png
new file mode 100644
index 0000000000..69d947b78c
Binary files /dev/null and b/assets/images/help/projects-v2/group-menu-item.png differ
diff --git a/assets/images/help/projects-v2/group-menu.png b/assets/images/help/projects-v2/group-menu.png
new file mode 100644
index 0000000000..16d42272cd
Binary files /dev/null and b/assets/images/help/projects-v2/group-menu.png differ
diff --git a/assets/images/help/projects-v2/hide-field-via-menu.png b/assets/images/help/projects-v2/hide-field-via-menu.png
new file mode 100644
index 0000000000..ee32c7be6d
Binary files /dev/null and b/assets/images/help/projects-v2/hide-field-via-menu.png differ
diff --git a/assets/images/help/projects-v2/insights-button.png b/assets/images/help/projects-v2/insights-button.png
new file mode 100644
index 0000000000..505114ac67
Binary files /dev/null and b/assets/images/help/projects-v2/insights-button.png differ
diff --git a/assets/images/help/projects-v2/insights-configure.png b/assets/images/help/projects-v2/insights-configure.png
new file mode 100644
index 0000000000..d63893cfd1
Binary files /dev/null and b/assets/images/help/projects-v2/insights-configure.png differ
diff --git a/assets/images/help/projects-v2/insights-group.png b/assets/images/help/projects-v2/insights-group.png
new file mode 100644
index 0000000000..5fbee6c061
Binary files /dev/null and b/assets/images/help/projects-v2/insights-group.png differ
diff --git a/assets/images/help/projects-v2/insights-layout.png b/assets/images/help/projects-v2/insights-layout.png
new file mode 100644
index 0000000000..4d1803d920
Binary files /dev/null and b/assets/images/help/projects-v2/insights-layout.png differ
diff --git a/assets/images/help/projects-v2/insights-new-chart.png b/assets/images/help/projects-v2/insights-new-chart.png
new file mode 100644
index 0000000000..002cf007c5
Binary files /dev/null and b/assets/images/help/projects-v2/insights-new-chart.png differ
diff --git a/assets/images/help/projects-v2/insights-rename.png b/assets/images/help/projects-v2/insights-rename.png
new file mode 100644
index 0000000000..06d650d586
Binary files /dev/null and b/assets/images/help/projects-v2/insights-rename.png differ
diff --git a/assets/images/help/projects-v2/insights-save-filter.png b/assets/images/help/projects-v2/insights-save-filter.png
new file mode 100644
index 0000000000..483b2cd843
Binary files /dev/null and b/assets/images/help/projects-v2/insights-save-filter.png differ
diff --git a/assets/images/help/projects-v2/insights-save.png b/assets/images/help/projects-v2/insights-save.png
new file mode 100644
index 0000000000..634b60dca2
Binary files /dev/null and b/assets/images/help/projects-v2/insights-save.png differ
diff --git a/assets/images/help/projects-v2/insights-select-a-chart.png b/assets/images/help/projects-v2/insights-select-a-chart.png
new file mode 100644
index 0000000000..b0a61995ea
Binary files /dev/null and b/assets/images/help/projects-v2/insights-select-a-chart.png differ
diff --git a/assets/images/help/projects-v2/insights-x-axis.png b/assets/images/help/projects-v2/insights-x-axis.png
new file mode 100644
index 0000000000..68133f22e3
Binary files /dev/null and b/assets/images/help/projects-v2/insights-x-axis.png differ
diff --git a/assets/images/help/projects-v2/insights-y-axis.png b/assets/images/help/projects-v2/insights-y-axis.png
new file mode 100644
index 0000000000..07fa9f9147
Binary files /dev/null and b/assets/images/help/projects-v2/insights-y-axis.png differ
diff --git a/assets/images/help/projects-v2/issue-edit-project-sidebar.png b/assets/images/help/projects-v2/issue-edit-project-sidebar.png
new file mode 100644
index 0000000000..4c2033c00d
Binary files /dev/null and b/assets/images/help/projects-v2/issue-edit-project-sidebar.png differ
diff --git a/assets/images/help/projects-v2/issue-index-project-menu.png b/assets/images/help/projects-v2/issue-index-project-menu.png
new file mode 100644
index 0000000000..5f9a806171
Binary files /dev/null and b/assets/images/help/projects-v2/issue-index-project-menu.png differ
diff --git a/assets/images/help/projects-v2/issue-index-select-project.png b/assets/images/help/projects-v2/issue-index-select-project.png
new file mode 100644
index 0000000000..2c4dc91845
Binary files /dev/null and b/assets/images/help/projects-v2/issue-index-select-project.png differ
diff --git a/assets/images/help/projects-v2/issue-sidebar-projects.png b/assets/images/help/projects-v2/issue-sidebar-projects.png
new file mode 100644
index 0000000000..8b898a9009
Binary files /dev/null and b/assets/images/help/projects-v2/issue-sidebar-projects.png differ
diff --git a/assets/images/help/projects-v2/issue-sidebar-select-project.png b/assets/images/help/projects-v2/issue-sidebar-select-project.png
new file mode 100644
index 0000000000..7ecb60f6cb
Binary files /dev/null and b/assets/images/help/projects-v2/issue-sidebar-select-project.png differ
diff --git a/assets/images/help/projects-v2/item-context-menu-button-board.png b/assets/images/help/projects-v2/item-context-menu-button-board.png
new file mode 100644
index 0000000000..8aa8953f85
Binary files /dev/null and b/assets/images/help/projects-v2/item-context-menu-button-board.png differ
diff --git a/assets/images/help/projects-v2/item-context-menu-button-table.png b/assets/images/help/projects-v2/item-context-menu-button-table.png
new file mode 100644
index 0000000000..c58e57b9f2
Binary files /dev/null and b/assets/images/help/projects-v2/item-context-menu-button-table.png differ
diff --git a/assets/images/help/projects-v2/item-convert-to-issue.png b/assets/images/help/projects-v2/item-convert-to-issue.png
new file mode 100644
index 0000000000..2e370d65a2
Binary files /dev/null and b/assets/images/help/projects-v2/item-convert-to-issue.png differ
diff --git a/assets/images/help/projects-v2/iteration-date.png b/assets/images/help/projects-v2/iteration-date.png
new file mode 100644
index 0000000000..785bed72c9
Binary files /dev/null and b/assets/images/help/projects-v2/iteration-date.png differ
diff --git a/assets/images/help/projects-v2/iteration-delete.png b/assets/images/help/projects-v2/iteration-delete.png
new file mode 100644
index 0000000000..4532c93ff9
Binary files /dev/null and b/assets/images/help/projects-v2/iteration-delete.png differ
diff --git a/assets/images/help/projects-v2/iteration-field-duration.png b/assets/images/help/projects-v2/iteration-field-duration.png
new file mode 100644
index 0000000000..18f1bb4ed0
Binary files /dev/null and b/assets/images/help/projects-v2/iteration-field-duration.png differ
diff --git a/assets/images/help/projects-v2/iteration-field-starts.png b/assets/images/help/projects-v2/iteration-field-starts.png
new file mode 100644
index 0000000000..8d3c017718
Binary files /dev/null and b/assets/images/help/projects-v2/iteration-field-starts.png differ
diff --git a/assets/images/help/projects-v2/iteration-rename.png b/assets/images/help/projects-v2/iteration-rename.png
new file mode 100644
index 0000000000..a7a7e97fbf
Binary files /dev/null and b/assets/images/help/projects-v2/iteration-rename.png differ
diff --git a/assets/images/help/projects-v2/iteration-save.png b/assets/images/help/projects-v2/iteration-save.png
new file mode 100644
index 0000000000..d866cdde82
Binary files /dev/null and b/assets/images/help/projects-v2/iteration-save.png differ
diff --git a/assets/images/help/projects-v2/manage-access.png b/assets/images/help/projects-v2/manage-access.png
new file mode 100644
index 0000000000..cd936781dc
Binary files /dev/null and b/assets/images/help/projects-v2/manage-access.png differ
diff --git a/assets/images/help/projects-v2/modify-field-menu.png b/assets/images/help/projects-v2/modify-field-menu.png
new file mode 100644
index 0000000000..9edf9c0084
Binary files /dev/null and b/assets/images/help/projects-v2/modify-field-menu.png differ
diff --git a/assets/images/help/projects-v2/new-field-button.png b/assets/images/help/projects-v2/new-field-button.png
new file mode 100644
index 0000000000..eb6dbfb5e1
Binary files /dev/null and b/assets/images/help/projects-v2/new-field-button.png differ
diff --git a/assets/images/help/projects-v2/new-field-date.png b/assets/images/help/projects-v2/new-field-date.png
new file mode 100644
index 0000000000..528b1e45d6
Binary files /dev/null and b/assets/images/help/projects-v2/new-field-date.png differ
diff --git a/assets/images/help/projects-v2/new-field-iteration.png b/assets/images/help/projects-v2/new-field-iteration.png
new file mode 100644
index 0000000000..f020571335
Binary files /dev/null and b/assets/images/help/projects-v2/new-field-iteration.png differ
diff --git a/assets/images/help/projects-v2/new-field-menu-item.png b/assets/images/help/projects-v2/new-field-menu-item.png
new file mode 100644
index 0000000000..5cddaf95cc
Binary files /dev/null and b/assets/images/help/projects-v2/new-field-menu-item.png differ
diff --git a/assets/images/help/projects-v2/new-field-name.png b/assets/images/help/projects-v2/new-field-name.png
new file mode 100644
index 0000000000..4a6e4d4dea
Binary files /dev/null and b/assets/images/help/projects-v2/new-field-name.png differ
diff --git a/assets/images/help/projects-v2/new-field-number.png b/assets/images/help/projects-v2/new-field-number.png
new file mode 100644
index 0000000000..9ecb3018cb
Binary files /dev/null and b/assets/images/help/projects-v2/new-field-number.png differ
diff --git a/assets/images/help/projects-v2/new-field-save-and-create.png b/assets/images/help/projects-v2/new-field-save-and-create.png
new file mode 100644
index 0000000000..0e19469aef
Binary files /dev/null and b/assets/images/help/projects-v2/new-field-save-and-create.png differ
diff --git a/assets/images/help/projects-v2/new-field-save.png b/assets/images/help/projects-v2/new-field-save.png
new file mode 100644
index 0000000000..09fe39b537
Binary files /dev/null and b/assets/images/help/projects-v2/new-field-save.png differ
diff --git a/assets/images/help/projects-v2/new-field-single-select.png b/assets/images/help/projects-v2/new-field-single-select.png
new file mode 100644
index 0000000000..11d6f14df3
Binary files /dev/null and b/assets/images/help/projects-v2/new-field-single-select.png differ
diff --git a/assets/images/help/projects-v2/new-field-text.png b/assets/images/help/projects-v2/new-field-text.png
new file mode 100644
index 0000000000..85ae6512b1
Binary files /dev/null and b/assets/images/help/projects-v2/new-field-text.png differ
diff --git a/assets/images/help/projects-v2/new-project-button.png b/assets/images/help/projects-v2/new-project-button.png
new file mode 100644
index 0000000000..ebfd1f38a2
Binary files /dev/null and b/assets/images/help/projects-v2/new-project-button.png differ
diff --git a/assets/images/help/projects-v2/new-view.png b/assets/images/help/projects-v2/new-view.png
new file mode 100644
index 0000000000..fd6a93fc13
Binary files /dev/null and b/assets/images/help/projects-v2/new-view.png differ
diff --git a/assets/images/help/projects-v2/no-grouping.png b/assets/images/help/projects-v2/no-grouping.png
new file mode 100644
index 0000000000..81399b8b4a
Binary files /dev/null and b/assets/images/help/projects-v2/no-grouping.png differ
diff --git a/assets/images/help/projects-v2/no-sorting.png b/assets/images/help/projects-v2/no-sorting.png
new file mode 100644
index 0000000000..a572350873
Binary files /dev/null and b/assets/images/help/projects-v2/no-sorting.png differ
diff --git a/assets/images/help/projects-v2/omnibar-add.png b/assets/images/help/projects-v2/omnibar-add.png
new file mode 100644
index 0000000000..6712eb271c
Binary files /dev/null and b/assets/images/help/projects-v2/omnibar-add.png differ
diff --git a/assets/images/help/projects-v2/open-menu.png b/assets/images/help/projects-v2/open-menu.png
new file mode 100644
index 0000000000..c4f2499f8e
Binary files /dev/null and b/assets/images/help/projects-v2/open-menu.png differ
diff --git a/assets/images/help/projects-v2/paste-url-to-add.png b/assets/images/help/projects-v2/paste-url-to-add.png
new file mode 100644
index 0000000000..ae3e122bc7
Binary files /dev/null and b/assets/images/help/projects-v2/paste-url-to-add.png differ
diff --git a/assets/images/help/projects-v2/priority-example.png b/assets/images/help/projects-v2/priority-example.png
new file mode 100644
index 0000000000..af600b55ed
Binary files /dev/null and b/assets/images/help/projects-v2/priority-example.png differ
diff --git a/assets/images/help/projects-v2/rename-view.png b/assets/images/help/projects-v2/rename-view.png
new file mode 100644
index 0000000000..eac8fa3840
Binary files /dev/null and b/assets/images/help/projects-v2/rename-view.png differ
diff --git a/assets/images/help/projects-v2/repo-tab.png b/assets/images/help/projects-v2/repo-tab.png
new file mode 100644
index 0000000000..9ac50b15cb
Binary files /dev/null and b/assets/images/help/projects-v2/repo-tab.png differ
diff --git a/assets/images/help/projects-v2/save-options.png b/assets/images/help/projects-v2/save-options.png
new file mode 100644
index 0000000000..119b6e1675
Binary files /dev/null and b/assets/images/help/projects-v2/save-options.png differ
diff --git a/assets/images/help/projects-v2/save-readme-button.png b/assets/images/help/projects-v2/save-readme-button.png
new file mode 100644
index 0000000000..4fb7911a50
Binary files /dev/null and b/assets/images/help/projects-v2/save-readme-button.png differ
diff --git a/assets/images/help/projects-v2/save-view.png b/assets/images/help/projects-v2/save-view.png
new file mode 100644
index 0000000000..eb1a31a302
Binary files /dev/null and b/assets/images/help/projects-v2/save-view.png differ
diff --git a/assets/images/help/projects-v2/select-field-header.png b/assets/images/help/projects-v2/select-field-header.png
new file mode 100644
index 0000000000..aced6ab291
Binary files /dev/null and b/assets/images/help/projects-v2/select-field-header.png differ
diff --git a/assets/images/help/projects-v2/select-iteration-field.png b/assets/images/help/projects-v2/select-iteration-field.png
new file mode 100644
index 0000000000..b7882249ca
Binary files /dev/null and b/assets/images/help/projects-v2/select-iteration-field.png differ
diff --git a/assets/images/help/projects-v2/select-row-number.png b/assets/images/help/projects-v2/select-row-number.png
new file mode 100644
index 0000000000..58bd09e5c2
Binary files /dev/null and b/assets/images/help/projects-v2/select-row-number.png differ
diff --git a/assets/images/help/projects-v2/select-single-select.png b/assets/images/help/projects-v2/select-single-select.png
new file mode 100644
index 0000000000..93fef4afa3
Binary files /dev/null and b/assets/images/help/projects-v2/select-single-select.png differ
diff --git a/assets/images/help/projects-v2/settings-menu-item.png b/assets/images/help/projects-v2/settings-menu-item.png
new file mode 100644
index 0000000000..ff8e781f87
Binary files /dev/null and b/assets/images/help/projects-v2/settings-menu-item.png differ
diff --git a/assets/images/help/projects-v2/show-hide-fields-menu-item.png b/assets/images/help/projects-v2/show-hide-fields-menu-item.png
new file mode 100644
index 0000000000..386e52f398
Binary files /dev/null and b/assets/images/help/projects-v2/show-hide-fields-menu-item.png differ
diff --git a/assets/images/help/projects-v2/show-hide-fields.png b/assets/images/help/projects-v2/show-hide-fields.png
new file mode 100644
index 0000000000..671af32ea7
Binary files /dev/null and b/assets/images/help/projects-v2/show-hide-fields.png differ
diff --git a/assets/images/help/projects-v2/single-select-create-with-options.png b/assets/images/help/projects-v2/single-select-create-with-options.png
new file mode 100644
index 0000000000..259bc4ca7d
Binary files /dev/null and b/assets/images/help/projects-v2/single-select-create-with-options.png differ
diff --git a/assets/images/help/projects-v2/single-select-delete.png b/assets/images/help/projects-v2/single-select-delete.png
new file mode 100644
index 0000000000..c09b2edfd3
Binary files /dev/null and b/assets/images/help/projects-v2/single-select-delete.png differ
diff --git a/assets/images/help/projects-v2/single-select-edit-options.png b/assets/images/help/projects-v2/single-select-edit-options.png
new file mode 100644
index 0000000000..252361a4cb
Binary files /dev/null and b/assets/images/help/projects-v2/single-select-edit-options.png differ
diff --git a/assets/images/help/projects-v2/sort-menu-item.png b/assets/images/help/projects-v2/sort-menu-item.png
new file mode 100644
index 0000000000..bf700aa784
Binary files /dev/null and b/assets/images/help/projects-v2/sort-menu-item.png differ
diff --git a/assets/images/help/projects-v2/sort-menu.png b/assets/images/help/projects-v2/sort-menu.png
new file mode 100644
index 0000000000..154f3c13a7
Binary files /dev/null and b/assets/images/help/projects-v2/sort-menu.png differ
diff --git a/assets/images/help/projects-v2/sort-order.png b/assets/images/help/projects-v2/sort-order.png
new file mode 100644
index 0000000000..04dcc5952d
Binary files /dev/null and b/assets/images/help/projects-v2/sort-order.png differ
diff --git a/assets/images/help/projects-v2/tab-projects.png b/assets/images/help/projects-v2/tab-projects.png
new file mode 100644
index 0000000000..aa7e13969c
Binary files /dev/null and b/assets/images/help/projects-v2/tab-projects.png differ
diff --git a/assets/images/help/projects-v2/table-or-board.png b/assets/images/help/projects-v2/table-or-board.png
new file mode 100644
index 0000000000..a653cc9aa7
Binary files /dev/null and b/assets/images/help/projects-v2/table-or-board.png differ
diff --git a/assets/images/help/projects-v2/view-menu-icon.png b/assets/images/help/projects-v2/view-menu-icon.png
new file mode 100644
index 0000000000..a2748c5efe
Binary files /dev/null and b/assets/images/help/projects-v2/view-menu-icon.png differ
diff --git a/assets/images/help/projects-v2/visibility-change-checkbox.png b/assets/images/help/projects-v2/visibility-change-checkbox.png
new file mode 100644
index 0000000000..04f72da917
Binary files /dev/null and b/assets/images/help/projects-v2/visibility-change-checkbox.png differ
diff --git a/assets/images/help/projects-v2/visibility.png b/assets/images/help/projects-v2/visibility.png
new file mode 100644
index 0000000000..8083f1b36a
Binary files /dev/null and b/assets/images/help/projects-v2/visibility.png differ
diff --git a/assets/images/help/projects-v2/workflow-enable.png b/assets/images/help/projects-v2/workflow-enable.png
new file mode 100644
index 0000000000..0c15d2b214
Binary files /dev/null and b/assets/images/help/projects-v2/workflow-enable.png differ
diff --git a/assets/images/help/projects-v2/workflow-set.png b/assets/images/help/projects-v2/workflow-set.png
new file mode 100644
index 0000000000..a2dab2f374
Binary files /dev/null and b/assets/images/help/projects-v2/workflow-set.png differ
diff --git a/assets/images/help/projects-v2/workflow-when.png b/assets/images/help/projects-v2/workflow-when.png
new file mode 100644
index 0000000000..486d6967fa
Binary files /dev/null and b/assets/images/help/projects-v2/workflow-when.png differ
diff --git a/assets/images/help/projects-v2/workflows-menu-item.png b/assets/images/help/projects-v2/workflows-menu-item.png
new file mode 100644
index 0000000000..df39c56268
Binary files /dev/null and b/assets/images/help/projects-v2/workflows-menu-item.png differ
diff --git a/assets/images/help/repository/copy-default-branch-only.png b/assets/images/help/repository/copy-default-branch-only.png
new file mode 100644
index 0000000000..41b1ebdab9
Binary files /dev/null and b/assets/images/help/repository/copy-default-branch-only.png differ
diff --git a/assets/images/help/repository/fork-choose-owner.png b/assets/images/help/repository/fork-choose-owner.png
new file mode 100644
index 0000000000..2ddc4087b5
Binary files /dev/null and b/assets/images/help/repository/fork-choose-owner.png differ
diff --git a/assets/images/help/repository/fork-choose-repo-name.png b/assets/images/help/repository/fork-choose-repo-name.png
new file mode 100644
index 0000000000..574716d2b4
Binary files /dev/null and b/assets/images/help/repository/fork-choose-repo-name.png differ
diff --git a/assets/images/help/repository/fork-create-button.png b/assets/images/help/repository/fork-create-button.png
new file mode 100644
index 0000000000..c44357727e
Binary files /dev/null and b/assets/images/help/repository/fork-create-button.png differ
diff --git a/assets/images/help/repository/fork-description.png b/assets/images/help/repository/fork-description.png
new file mode 100644
index 0000000000..935ffad949
Binary files /dev/null and b/assets/images/help/repository/fork-description.png differ
diff --git a/assets/images/help/repository/repo-actions-settings.png b/assets/images/help/repository/repo-actions-settings.png
index 8970b388a1..9e7590c9f4 100644
Binary files a/assets/images/help/repository/repo-actions-settings.png and b/assets/images/help/repository/repo-actions-settings.png differ
diff --git a/components/lib/events.ts b/components/lib/events.ts
index ff2d4104e6..fede96f798 100644
--- a/components/lib/events.ts
+++ b/components/lib/events.ts
@@ -1,8 +1,8 @@
 /* eslint-disable camelcase */
 import { v4 as uuidv4 } from 'uuid'
 import Cookies from 'js-cookie'
-import getCsrf from './get-csrf'
 import parseUserAgent from './user-agent'
+import { getSession, fetchSession } from './get-session'
 
 const COOKIE_NAME = '_docs-events'
 
@@ -83,8 +83,10 @@ function getMetaContent(name: string) {
 }
 
 export function sendEvent({ type, version = '1.0.0', ...props }: SendEventProps) {
+  const session = getSession()
+
   const body = {
-    _csrf: getCsrf(),
+    _csrf: session?.csrfToken,
 
     type,
 
@@ -273,14 +275,16 @@ function initPrintEvent() {
 }
 
 export default function initializeEvents() {
-  initPageAndExitEvent() // must come first
-  initLinkEvent()
-  initClipboardEvent()
-  initCopyButtonEvent()
-  initPrintEvent()
-  // survey event in ./survey.js
-  // experiment event in ./experiment.js
-  // search and search_result event in ./search.js
-  // redirect event in middleware/record-redirect.js
-  // preference event in ./display-tool-specific-content.js
+  fetchSession().then(() => {
+    initPageAndExitEvent() // must come first
+    initLinkEvent()
+    initClipboardEvent()
+    initCopyButtonEvent()
+    initPrintEvent()
+    // survey event in ./survey.js
+    // experiment event in ./experiment.js
+    // search and search_result event in ./search.js
+    // redirect event in middleware/record-redirect.js
+    // preference event in ./display-tool-specific-content.js
+  })
 }
diff --git a/components/lib/get-csrf.ts b/components/lib/get-csrf.ts
deleted file mode 100644
index d98f7da0f4..0000000000
--- a/components/lib/get-csrf.ts
+++ /dev/null
@@ -1,5 +0,0 @@
-export default function getCsrf() {
-  const csrfEl = document.querySelector('meta[name="csrf-token"]')
-  if (!csrfEl) return ''
-  return csrfEl.getAttribute('content')
-}
diff --git a/components/lib/get-session.ts b/components/lib/get-session.ts
new file mode 100644
index 0000000000..5272bf0d4c
--- /dev/null
+++ b/components/lib/get-session.ts
@@ -0,0 +1,51 @@
+import { useState, useEffect } from 'react'
+import { useRouter } from 'next/router'
+
+const MAX_CACHE = 5000 // milliseconds
+const RETRY = 500 // milliseconds
+
+type Session = {
+  isSignedIn: boolean
+  csrfToken: string
+  language: string // en, es, ja, cn
+  userLanguage: string // en, es, ja, cn
+  theme: object // colorMode, nightTheme, dayTheme
+  themeCSS: object // colorMode, nightTheme, dayTheme
+}
+
+let sessionCache: Session | null
+let lastUpdate: number | null
+
+function isCacheValid() {
+  return lastUpdate && Date.now() - lastUpdate < MAX_CACHE
+}
+
+export function getSession() {
+  return sessionCache
+}
+
+// This function must only be called in the browser
+export async function fetchSession(): Promise<Session | null> {
+  if (isCacheValid()) return sessionCache
+  const response = await fetch('/api/session')
+  if (response.ok) {
+    sessionCache = await response.json()
+    lastUpdate = Date.now()
+    return sessionCache as Session
+  }
+  lastUpdate = null
+  sessionCache = null
+  await new Promise((resolve) => setTimeout(resolve, RETRY))
+  return fetchSession()
+}
+
+// React hook version
+export function useSession() {
+  const [session, setSession] = useState<Session | null>(sessionCache)
+  const { asPath } = useRouter()
+  // Only call `fetchSession` on the client
+  useEffect(() => {
+    fetchSession().then((session) => setSession(session))
+  }, [asPath])
+  return session
+}
diff --git a/components/page-header/Header.tsx b/components/page-header/Header.tsx
index a5e3759b6a..93d02312ee 100644
--- a/components/page-header/Header.tsx
+++ b/components/page-header/Header.tsx
@@ -6,7 +6,7 @@ import { useVersion } from 'components/hooks/useVersion'
 
 import { Link } from 'components/Link'
 import { useMainContext } from 'components/context/MainContext'
-import { useAuth } from 'components/context/DotComAuthenticatedContext'
+import { useSession } from 'components/lib/get-session'
 import { LanguagePicker } from './LanguagePicker'
 import { HeaderNotifications } from 'components/page-header/HeaderNotifications'
 import { ProductPicker } from 'components/page-header/ProductPicker'
@@ -26,10 +26,11 @@ export const Header = () => {
   )
   const [scroll, setScroll] = useState(false)
 
-  const { isDotComAuthenticated } = useAuth()
+  const session = useSession()
 
   const signupCTAVisible =
-    !isDotComAuthenticated &&
+    session &&
+    !session.isSignedIn &&
     (currentVersion === 'free-pro-team@latest' || currentVersion === 'enterprise-cloud@latest')
 
   useEffect(() => {
diff --git a/content/actions/learn-github-actions/contexts.md b/content/actions/learn-github-actions/contexts.md
index 166ee64594..da8dc7a8f6 100644
--- a/content/actions/learn-github-actions/contexts.md
+++ b/content/actions/learn-github-actions/contexts.md
@@ -183,7 +183,7 @@ The `github` context contains information about the workflow run and the event t
 | `github.action_ref` | `string` | For a step executing an action, this is the ref of the action being executed. For example, `v2`. |
 | `github.action_repository` | `string` | For a step executing an action, this is the owner and repository name of the action. For example, `actions/checkout`. |
 | `github.action_status` | `string` | For a composite action, the current result of the composite action. |
-| `github.actor` | `string` | The username of the user that initiated the workflow run. |
+| `github.actor` | `string` | {% ifversion actions-stable-actor-ids %}The username of the user that triggered the initial workflow run. If the workflow run is a re-run, this value may differ from `github.triggering_actor`. Any workflow re-runs will use the privileges of `github.actor`, even if the actor initiating the re-run (`github.triggering_actor`) has different privileges.{% else %}The username of the user that initiated the workflow run.{% endif %} |
 | `github.api_url` | `string` | The URL of the {% data variables.product.prodname_dotcom %} REST API. |
 | `github.base_ref` | `string` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. |
 | `github.env` | `string` | Path on the runner to the file that sets environment variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#setting-an-environment-variable)." |
@@ -211,7 +211,8 @@ The `github` context contains information about the workflow run and the event t
 {%- endif %}
 | `github.server_url` | `string` | The URL of the GitHub server. For example: `https://github.com`. |
 | `github.sha` | `string` | The commit SHA that triggered the workflow run. |
-| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."  <br /> Note: This context property is set by the Actions runner, and is only available within the execution `steps` of a job. Otherwise, the value of this property will be `null`. |
+| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."  <br /> Note: This context property is set by the Actions runner, and is only available within the execution `steps` of a job. Otherwise, the value of this property will be `null`. |{% ifversion actions-stable-actor-ids %}
+| `github.triggering_actor` | `string` | The username of the user that initiated the workflow run. If the workflow run is a re-run, this value may differ from `github.actor`. Any workflow re-runs will use the privileges of `github.actor`, even if the actor initiating the re-run (`github.triggering_actor`) has different privileges. |{% endif %}
 | `github.workflow` | `string` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. |
 | `github.workspace` | `string` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
 
diff --git a/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
index e5bf6d5827..4fd7539fc3 100644
--- a/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
+++ b/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -17,7 +17,7 @@ versions:
 
 ## About re-running workflows and jobs
 
-Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see "[Usage limits, billing, and administration](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %}{% ifversion debug-reruns %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see "[Enabling debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."{% endif %}
+Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. {% ifversion actions-stable-actor-ids %}The workflow will use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. {% endif %}You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see "[Usage limits, billing, and administration](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %}{% ifversion debug-reruns %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see "[Enabling debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."{% endif %}
 
 ## Re-running all the jobs in a workflow
 
diff --git a/content/actions/using-workflows/events-that-trigger-workflows.md b/content/actions/using-workflows/events-that-trigger-workflows.md
index 9a4754b54a..4af02f0041 100644
--- a/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -415,7 +415,7 @@ on:
 
 {% data reusables.actions.branch-requirement %}
 
-Runs your workflow when someone pushes to a branch that is the publishing source for {% data variables.product.prodname_pages %}, if {% data variables.product.prodname_pages %} is enabled for the repository. For more information about {% data variables.product.prodname_pages %} publishing sources, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)." For information about the REST API, see "[Pages](/rest/reference/repos#pages)."
+Runs your workflow when someone pushes to a branch that is the publishing source for {% data variables.product.prodname_pages %}, if {% data variables.product.prodname_pages %} is enabled for the repository. For more information about {% data variables.product.prodname_pages %} publishing sources, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the REST API, see "[Pages](/rest/reference/repos#pages)."
 
 For example, you can run a workflow when the `page_build` event occurs.
 
@@ -447,7 +447,7 @@ on:
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note**: This event does not occur for projects (beta). For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)."
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
 
 {% endnote %}
 {% endif %}
@@ -485,7 +485,7 @@ on:
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note**: This event does not occur for projects (beta). For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)."
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
 
 {% endnote %}
 {% endif %}
@@ -523,7 +523,7 @@ on:
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note**: This event does not occur for projects (beta). For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)."
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
 
 {% endnote %}
 {% endif %}
diff --git a/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
index 3f32767170..7cc26a40e1 100644
--- a/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
+++ b/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
@@ -30,16 +30,12 @@ The nameservers you specify must resolve {% data variables.product.product_locat
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 
-2. To edit your nameservers, enter:
+2. To edit your nameservers, use the `ghe-setup-network` command in visual mode. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-setup-network)."
 
   ```shell
-  sudo vim /etc/resolvconf/resolv.conf.d/head
+  ghe-setup-network -v
   ```
 
-{% data reusables.enterprise_installation.preventing-nameservers-change %}
-
-3. Append any `nameserver` entries, then save the file.
-4. After verifying your changes, save the file.
 5. To add your new nameserver entries to {% data variables.product.product_location %}, run the following:
 
   ```shell
diff --git a/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index 71543e2a68..3afde5fc5c 100644
--- a/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -343,6 +343,18 @@ With `ghe-set-password`, you can set a new password to authenticate into the [{%
 ghe-set-password <new_password>
 ```
 
+### ghe-setup-network
+
+This utility allows you to configure the primary network interface.
+
+To enter visual mode, which will guide you through configuration of network settings:
+
+```shell
+$ ghe-setup-network -v
+```
+
+Use the -h flag for additional options.
+
 ### ghe-ssh-check-host-keys
 
 This utility checks the existing SSH host keys against the list of known leaked SSH host keys.
diff --git a/content/admin/guides.md b/content/admin/guides.md
index 41b3562712..08b0727759 100644
--- a/content/admin/guides.md
+++ b/content/admin/guides.md
@@ -119,6 +119,7 @@ includeGuides:
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise
diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
index 6b4137e344..501624f06b 100644
--- a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
+++ b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
@@ -35,7 +35,8 @@ In addition to viewing your audit log, you can monitor activity in your enterpri
 
 As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you can interact with the audit log data for your enterprise in several ways:
 - You can view the audit log for your enterprise. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)."
-- You can search the audit log for specific events{% ifversion ghec %} and export audit log data{% endif %}. For more information, see "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} and "[Exporting the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}.
+- You can search the audit log for specific events{% ifversion ghec %} and export audit log data{% endif %}. For more information, see "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} and "[Exporting the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}.{% ifversion audit-data-retention-tab %}
+- You can configure settings, such as the retention period for audit log events{% ifversion enable-git-events %} and whether Git events are included{% endif %}. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise)."{% endif %}
 {%- ifversion enterprise-audit-log-ip-addresses %}
 - You can display the IP address associated with events in the audit log. For more information, see "[Displaying IP addresses in the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise)."
 {%- endif %}
diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
index 53f6ef7258..33fed05966 100644
--- a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
+++ b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
@@ -392,9 +392,15 @@ Action                        | Description
 | `gist.destroy` | A gist is deleted.
 | `gist.visibility_change` | The visibility of a gist is changed.
 
-{% ifversion ghec or ghes > 3.4 or ghae-issue-6724 %}
+{% ifversion git-events-audit-log %}
 ## `git` category actions
 
+{% ifversion enable-git-events %}
+Before you'll see `git` category actions, you must enable Git events in the audit log. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise#managing-git-events-in-the-audit-log)."
+{% endif %}
+
+{% data reusables.audit_log.git-events-not-in-search-results %}
+
 | Action | Description
 |--------|-------------
 | `git.clone` | A repository was cloned.
@@ -889,20 +895,20 @@ Action                        | Description
 | `project.update_team_permission` | A team's project board permission level was changed or when a team was added or removed from a project board. For more information, see "[Managing team access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board)."
 | `project.update_user_permission` | An organization member or outside collaborator was added to or removed from a project board or had their permission level changed. For more information, see "[Managing an individual’s access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board)."
 
-{%- ifversion fpt or ghec %}
+{%- ifversion projects-v2 %}
 ## `project_field` category actions
 
 | Action | Description
 |--------|-------------
-| `project_field.create` | A field was created in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)."
-| `project_field.delete` | A field was deleted in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)."
+| `project_field.create` | A field was created in a project board. For more information, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)."
+| `project_field.delete` | A field was deleted in a project board. For more information, see "[Deleting fields](/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields)."
 
 ## `project_view` category actions
 
 | Action | Description
 |--------|-------------
-| `project_view.create` | A view was created in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#creating-a-project-view)."
-| `project_view.delete` | A view was deleted in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#deleting-a-saved-view)."
+| `project_view.create` | A view was created in a project board. For more information, see "[Managing your views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)."
+| `project_view.delete` | A view was deleted in a project board. For more information, see "[Managing your views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)."
 {%- endif %}
 
 ## `protected_branch` category actions
diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
new file mode 100644
index 0000000000..855e7c1a15
--- /dev/null
+++ b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
@@ -0,0 +1,56 @@
+---
+title: Configuring the audit log for your enterprise
+intro: "You can configure settings for your enterprise's audit log."
+shortTitle: Configure audit logs
+permissions: 'Enterprise owners can configure the audit log.'
+versions:
+  feature: audit-data-retention-tab
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+---
+
+## About audit log configuration
+
+You can configure a retention period for audit log data and see index storage details.
+
+{% ifversion enable-git-events %}
+After you configure a retention period, you can enable or disable Git-related events from appearing in the audit log.
+{% endif %}
+
+## Configuring a retention period for audit log data
+
+You can configure a retention period for audit log data for {% data variables.product.product_location %}. Data that exceeds the period you configure will be permanently removed from disk.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.audit-log-tab %}
+{% data reusables.audit_log.audit-data-retention-tab %}
+1. Under "Configure audit log retention settings", select the dropdown menu and click a retention period.
+
+   ![Screenshot of the dropdown menu for audit log retention settings](/assets/images/help/enterprises/audit-log-retention-dropdown.png)
+1. Click **Save**.
+
+{% ifversion enable-git-events %}
+## Managing Git events in the audit log
+
+You can enable or disable Git-related events, such as `git.clone` and `git.push`, from appearing in your audit log. For a list of the Git events are are logged, 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)."
+
+If you do enable Git events, due to the large number of Git events that are logged, we recommend monitoring your instance's file storage and reviewing your related alert configurations. For more information, see "[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)."
+
+Before you can enable Git events in the audit log, you must configure a retention period for audit log data other than "infinite." For more information, see "[Configuring a retention period for audit log data](#configuring-a-retention-period-for-audit-log-data)."
+
+{% data reusables.audit_log.git-events-not-in-search-results %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.audit-log-tab %}
+{% data reusables.audit_log.audit-data-retention-tab %}
+1. Under "Git event opt-in", select or deselect **Enable git events in the audit-log**.
+
+   ![Screenshot of the checkbox to enable Git events in the audit log](/assets/images/help/enterprises/enable-git-events-checkbox.png)
+1. Click **Save**.
+
+{% endif %}
\ No newline at end of file
diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
index 7272c8b766..8ee165aa1a 100644
--- a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
+++ b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
@@ -11,6 +11,7 @@ topics:
 children:
   - /about-the-audit-log-for-your-enterprise
   - /accessing-the-audit-log-for-your-enterprise
+  - /configuring-the-audit-log-for-your-enterprise
   - /displaying-ip-addresses-in-the-audit-log-for-your-enterprise
   - /searching-the-audit-log-for-your-enterprise
   - /exporting-audit-log-activity-for-your-enterprise
diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
index e492c057d1..5b3b8bcaef 100644
--- a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
+++ b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
@@ -29,9 +29,11 @@ You can search your enterprise audit log directly from the user interface by usi
 
 For more information about viewing your enterprise audit log, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)." 
 
+{% data reusables.audit_log.git-events-not-in-search-results %}
+
 You can also use the API to retrieve audit log events. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)."
 
-Note that you cannot search for entries using text. You can, however, construct search queries using a variety of filters. Many operators used when querying the log, such as `-`, `>`, or `<`, match the same format as searching across {% data variables.product.product_name %}. For more information, see "[Searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
+You cannot search for entries using text. You can, however, construct search queries using a variety of filters. Many operators used when querying the log, such as `-`, `>`, or `<`, match the same format as searching across {% data variables.product.product_name %}. For more information, see "[Searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
 
 {% note %}
 
diff --git a/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
index bd6c411282..6c4d45b193 100644
--- a/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
+++ b/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
@@ -68,7 +68,7 @@ When you want to use an {% data variables.product.prodname_oauth_app %} that int
 | Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. |
 | Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. Apps can request access for either public or private repositories on a user-wide level. |
 | Repository delete | Apps can request to delete repositories that you administer, but they won't have access to your code. |{% ifversion projects-oauth-scope %}
-| Projects | Access to user and organization projects (beta). Apps can request either read/write or read only access. |{% endif %}
+| Projects | Access to user and organization {% data variables.projects.projects_v2 %}. Apps can request either read/write or read only access. |{% endif %}
 
 ## Requesting updated permissions
 
diff --git a/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md b/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
index ea1c77755e..99c879d934 100644
--- a/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
+++ b/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
@@ -22,6 +22,9 @@ Organization owners and billing managers can view {% data variables.product.prod
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.codespaces-minutes %}
 {% data reusables.dotcom_billing.actions-packages-report-download-org-account %}
+1. Filter the report to show only rows that mention "Codespaces" in the `Product` field.
+
+   ![A usage report filtered for Codespaces](/assets/images/help/codespaces/CSV-usage-report.png)
 
 {% ifversion ghec %}
 ## Viewing {% data variables.product.prodname_codespaces %} usage for your enterprise account
diff --git a/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
index e4f4b8730a..6e0a632ea9 100644
--- a/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
+++ b/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
@@ -43,6 +43,8 @@ For workflows initiated by {% data variables.product.prodname_dependabot %} (`gi
 For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request_target` event, if the base ref of the pull request was created by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`), the `GITHUB_TOKEN` will be read-only and secrets are not available.
 {% endif %}
 
+{% ifversion actions-stable-actor-ids %}These restrictions apply even if the workflow is re-run by a different actor.{% endif %}
+
 For more information, see ["Keeping your GitHub Actions and workflows secure: Preventing pwn requests"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
 
 {% ifversion fpt or ghec or ghes > 3.3 %}
@@ -224,8 +226,16 @@ jobs:
 
 ### Manually re-running a workflow
 
+{% ifversion actions-stable-actor-ids %}
+
+When you manually re-run a Dependabot workflow, it will run with the same privileges as before even if the user who initiated the rerun has different privileges. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+
+{% else %}
+
 You can also manually re-run a failed Dependabot workflow, and it will run with a read-write token and access to secrets. Before manually re-running a failed workflow, you should always check the dependency being updated to ensure that the change doesn't introduce any malicious or unintended behavior.
 
+{% endif %}
+
 ## Common Dependabot automations
 
 Here are several common scenarios that can be automated using {% data variables.product.prodname_actions %}.
@@ -466,7 +476,8 @@ on: pull_request_target
 
 permissions:
   contents: write
-
+  pull-requests: write
+  
 jobs:
   dependabot:
     runs-on: ubuntu-latest
@@ -497,6 +508,7 @@ on: pull_request
 
 permissions:
   contents: write
+  pull-requests: write
 
 jobs:
   dependabot:
diff --git a/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md b/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
index 3c7c3ef44d..bb34ea7f01 100644
--- a/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
+++ b/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
@@ -32,6 +32,8 @@ If a contributor bypasses a push protection block for a secret, {% data variable
 
 {% data variables.product.prodname_secret_scanning_caps %} as a push protection currently scans repositories for secrets issued by the following service providers.
 
+{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
+
 {% data reusables.secret-scanning.secret-list-private-push-protection %}
 
 ## Enabling {% data variables.product.prodname_secret_scanning %} as a push protection
diff --git a/content/code-security/secret-scanning/secret-scanning-patterns.md b/content/code-security/secret-scanning/secret-scanning-patterns.md
index 4400543078..20e716d463 100644
--- a/content/code-security/secret-scanning/secret-scanning-patterns.md
+++ b/content/code-security/secret-scanning/secret-scanning-patterns.md
@@ -34,6 +34,8 @@ Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data
 
 {% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers. For more information about {% data variables.product.prodname_secret_scanning_partner %}, see "[About {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)."
 
+{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
+
 {% data reusables.secret-scanning.partner-secret-list-public-repo %}
 {% endif %}
 
@@ -42,6 +44,8 @@ Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data
 
 When {% data variables.product.prodname_secret_scanning_GHAS %} is enabled, {% data variables.product.prodname_dotcom %} scans for secrets issued by the following service providers. {% ifversion ghec %}For more information about {% data variables.product.prodname_secret_scanning_GHAS %}, see "[About {% data variables.product.prodname_secret_scanning_GHAS %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)."{% endif %}
 
+{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
+
 If you use the REST API for secret scanning, you can use the `Secret type` to report on secrets from specific issuers. For more information, see "[Secret scanning](/enterprise-cloud@latest/rest/secret-scanning)."
  
 {% ifversion ghes or ghae or ghec %}
diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
index ce887407fa..f8d43d3098 100644
--- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
+++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
@@ -52,6 +52,8 @@ The dependency review feature becomes available when you enable the dependency g
 
 The action is available for all {% ifversion fpt or ghec %}public repositories, as well as private {% endif %}repositories that have {% data variables.product.prodname_GH_advanced_security %} enabled.
 
+{% data reusables.dependency-review.action-enterprise %}
+
 You can use the {% data variables.product.prodname_dependency_review_action %} in your repository to enforce dependency reviews on your pull requests. The action scans for vulnerable versions of dependencies introduced by package version changes in pull requests, and warns you about the associated security vulnerabilities. This gives you better visibility of what's changing in a pull request, and helps prevent vulnerabilities being added to your repository. For more information, see [`dependency-review-action`](https://github.com/actions/dependency-review-action).
 
 ![Dependency review action example](/assets/images/help/graphs/dependency-review-action.png)
@@ -61,7 +63,7 @@ By default, the {% data variables.product.prodname_dependency_review_action %} c
 The action uses the Dependency Review REST API to get the diff of dependency changes between the base commit and head commit. You can use the Dependency Review API to get the diff of dependency changes, including vulnerability data, between any two commits on a repository. For more information, see "[Dependency review](/rest/reference/dependency-graph#dependency-review)."
 
 {% ifversion dependency-review-action-configuration %}
-You can configure the {% data variables.product.prodname_dependency_review_action %} to better suit your needs. For example, you can specify the severity level that will make the action fail, or set an allow or deny list for licenses to scan. For more information, see "[Configuring dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review#configuring-the-dependency-review-github-action)." 
+You can configure the {% data variables.product.prodname_dependency_review_action %} to better suit your needs. For example, you can specify the severity level that will make the action fail{% ifversion dependency-review-action-licenses %}, or set an allow or deny list for licenses to scan{% endif %}. For more information, see "[Configuring dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review#configuring-the-dependency-review-github-action)." 
 {% endif %}
 
 {% endif %}
diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
index c18299b4c4..5cf97e5410 100644
--- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
+++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
@@ -62,14 +62,18 @@ The following configuration options are available.
 | Option | Required | Usage |
 |------------------|-------------------------------|--------|
 | `fail-on-severity` | Optional | Defines the threshold for level of severity (`low`, `moderate`, `high`, `critical`).</br>The action will fail on any pull requests that introduce vulnerabilities of the specified severity level or higher. |
-| `allow-licenses` | Optional | Contains a list of allowed licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that do not match the list.|
-| `deny-licenses` | Optional | Contains a list of prohibited licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that match the list.|
+{%- ifversion dependency-review-action-licenses %}
+| `allow-licenses` | Optional | Contains a list of allowed licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that do not match the list.|{% endif %}
+{%- ifversion dependency-review-action-licenses %}
+| `deny-licenses` | Optional | Contains a list of prohibited licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that match the list.|{% endif %}
 
+{% ifversion dependency-review-action-licenses %}
 {% tip %}
 
 **Tip:** The  `allow-licenses` and  `deny-licenses` options are mutually exclusive.
 
 {% endtip %}
+{% endif %}
 
 This {% data variables.product.prodname_dependency_review_action %} example file illustrates how you can use these configuration options.
 
@@ -91,6 +95,7 @@ jobs:
         with:
           # Possible values: "critical", "high", "moderate", "low" 
           fail-on-severity: critical
+{% ifversion dependency-review-action-licenses %}
           # You can only can only include one of these two options: `allow-licenses` and `deny-licences`
           # ([String]). Only allow these licenses (optional)
           # Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses 
@@ -99,6 +104,7 @@ jobs:
           # ([String]). Block the pull request on these licenses (optional)
           # Possible values: Any  `spdx_id` value(s) from https://docs.github.com/en/rest/licenses 
           # deny-licenses: LGPL-2.0, BSD-2-Clause
+{% endif %}
 ```
 
 For further details about the configuration options, see [`dependency-review-action`](https://github.com/actions/dependency-review-action#readme).
diff --git a/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
index 2bfda78214..1cc26083f0 100644
--- a/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
+++ b/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
@@ -82,6 +82,22 @@ You can update the value of an existing secret, and you can change which reposit
 1. Read the warning, then click **OK**.
   ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png)
 
+## Using secrets
+
+A secret is exported as an environment variable into the user's terminal session.
+
+  ![Displaying the value of an exported secret in the terminal](/assets/images/help/codespaces/exported-codespace-secret.png)
+
+You can use secrets in a codespace after the codespace is built and is running. For example, a secret can be used:
+
+* When launching an application from the integrated terminal or ssh session.
+* Within a dev container lifecycle script that is run after the codespace is running. For more information about dev container lifecycle scripts, see the documentation on containers.dev: [Specification](https://containers.dev/implementors/json_reference/#lifecycle-scripts).
+
+Codespace secrets cannot be used during:
+
+* Codespace build time (that is, within a Dockerfile or custom entry point).
+* Within a dev container feature. For more information, see the `features` attribute in the documentation on containers.dev: [Specification](https://containers.dev/implementors/json_reference/#general-properties).
+
 ## Further reading
 
 - "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)"
diff --git a/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md b/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
index 10bc7a92a8..82a0d99505 100644
--- a/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
+++ b/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
@@ -39,7 +39,7 @@ shortTitle: Manage wiki pages
 {% data reusables.repositories.sidebar-wiki %}
 4. Using the wiki sidebar, navigate to the page you want to change. In the upper-right corner of the page, click **Edit**.
    ![Wiki edit page button](/assets/images/help/wiki/wiki_edit_page_button.png)
-5. Use the text editor edit the page's content.
+5. Use the text editor to edit the page's content.
    ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
 6. Type a commit message describing your changes.
    ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
diff --git a/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md b/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
index 19fe8cec31..ab83e4a820 100644
--- a/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
+++ b/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
@@ -34,8 +34,8 @@ When you block a user:
 - You are removed as a collaborator on their repositories
 - Their sponsorship of you is cancelled
 - Any pending repository or account successor invitations to or from the blocked user are cancelled
-- The user is removed as a collaborator from all the Project Boards & Projects (beta) owned by you
-- You are removed as a collaborator from all the Project Boards & Projects (beta) owned by the user
+- The user is removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by you
+- You are removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by the user
 
 After you've blocked a user, they cannot:
 - Send you any notifications, including by [@mentioning](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) your username
@@ -48,8 +48,8 @@ After you've blocked a user, they cannot:
 - Cross-reference your repositories in comments
 - Fork, watch, pin, or star your repositories
 - Sponsor you
-- Add you as a collaborator on their Project Boards & Projects (beta)
-- Make changes to your public Project Boards & Projects (beta)
+- Add you as a collaborator on their projects and {% data variables.projects.projects_v1_boards %}
+- Make changes to your public projects and {% data variables.projects.projects_v1_boards %}
 
 In repositories you own, blocked users also cannot:
 - Open issues
diff --git a/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
index a3d1695958..f834fa013e 100644
--- a/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
+++ b/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
@@ -42,7 +42,7 @@ Name | Description
 -----|-----------|{% ifversion not ghae %}
 **`(no scope)`** | Grants read-only access to public information (including user profile info, repository info, and gists){% endif %}{% ifversion ghes or ghae %}
 **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %}
-**`repo`** | Grants full access to repositories, including private repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for repositories and organizations. Also grants ability to manage user projects.
+**`repo`** | Grants full access to public{% ifversion ghec or ghes or ghae %}, internal,{% endif %} and private repositories including read and write access to code, commit statuses, repository invitations, collaborators, deployment statuses, and repository webhooks. **Note**: In addition to repository related resources, the `repo` scope also grants access to manage organization-owned resources including projects, invitations, team memberships and webhooks. This scope also grants the ability to manage projects owned by users.
 &emsp;`repo:status`| Grants read/write access to commit statuses in {% ifversion fpt %}public and private{% elsif ghec or ghes %}public, private, and internal{% elsif ghae %}private and internal{% endif %} repositories. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code.
 &emsp;`repo_deployment`| Grants access to [deployment statuses](/rest/reference/repos#deployments) for {% ifversion not ghae %}public{% else %}internal{% endif %} and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code.{% ifversion not ghae %}
 &emsp;`public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories.{% endif %}
@@ -64,8 +64,8 @@ Name | Description
 &emsp;`read:user`| Grants access to read a user's profile data.
 &emsp;`user:email`| Grants read access to a user's email addresses.
 &emsp;`user:follow`| Grants access to follow or unfollow other users.{% ifversion projects-oauth-scope %}
-**`project`** | Grants read/write access to user and organization projects (beta).
-&emsp;`read:project`| Grants read only access to user and organization projects (beta).{% endif %}
+**`project`** | Grants read/write access to user and organization {% data variables.projects.projects_v2 %}.
+&emsp;`read:project`| Grants read only access to user and organization {% data variables.projects.projects_v2 %}.{% endif %}
 **`delete_repo`** | Grants access to delete adminable repositories.
 **`write:discussion`** | Allows read and write access for team discussions.
 &emsp;`read:discussion` | Allows read access for team discussions.
diff --git a/content/developers/overview/github-developer-program.md b/content/developers/overview/github-developer-program.md
index 90494c3acb..bd0fb16722 100644
--- a/content/developers/overview/github-developer-program.md
+++ b/content/developers/overview/github-developer-program.md
@@ -27,7 +27,7 @@ Awesome! We'd love to have you be part of the program. Here’s how you can spre
 * Use the [Octocat or GitHub logo](https://github.com/logos) to identify that your product works with GitHub
 * Post a video or a blog on your website about your integration
 
-## Ready to join the GitHub Developer Program?</h3>
+## Ready to join the GitHub Developer Program?
 
 Membership is open to individual developers and companies who have:
 
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 37067da378..a8c23b0b45 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
@@ -891,10 +891,10 @@ Key | Type | Description
 - Organization webhooks
 - {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
 
-{% ifversion fpt or ghec %}
+{% ifversion projects-v2 %}
 {% note %}
 
-**Note**: This event does not occur for Projects (beta).
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
 
 {% endnote %}
 {% endif %}
@@ -923,10 +923,10 @@ Key | Type | Description
 - Organization webhooks
 - {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
 
-{% ifversion fpt or ghec %}
+{% ifversion projects-v2 %}
 {% note %}
 
-**Note**: This event does not occur for Projects (beta).
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
 
 {% endnote %}
 {% endif %}
@@ -953,6 +953,14 @@ Key | Type | Description
 - Organization webhooks
 - {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
 
+{% ifversion projects-v2 %}
+{% note %}
+
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
+
+{% endnote %}
+{% endif %}
+
 ### Webhook payload object
 
 {% data reusables.webhooks.project_column_properties %}
@@ -971,11 +979,11 @@ Key | Type | Description
 
 {% note %}
 
-**Note:** Webhook events for Projects (beta) are currently in beta and subject to change. To share feedback about Projects (beta) webhooks with {% data variables.product.product_name %}, see the [Projects (beta) webhook feedback discussion](https://github.com/community/community/discussions/17405).
+**Note:** Webhook events for {% data variables.projects.projects_v2 %} are currently in beta and subject to change. To share feedback about {% data variables.projects.projects_v2 %} webhooks with {% data variables.product.product_name %}, see the [Projects webhook feedback discussion](https://github.com/community/community/discussions/17405).
 
 {% endnote %}
 
-Activity related to items in a Projects (beta) project. {% data reusables.webhooks.action_type_desc %} For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)."
+Activity related to items in a {% data variables.projects.project_v2 %}. {% data reusables.webhooks.action_type_desc %} For more information, see "[About {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
 
 ### Availability
 
@@ -987,7 +995,7 @@ Activity related to items in a Projects (beta) project. {% data reusables.webhoo
 Key | Type | Description
 ----|------|-------------
 `action`|`string` | The action that was performed on the project item. Can be one of `archived`, `converted`, `created`, `edited`, `restored`, `deleted`, or `reordered`.
-`projects_v2_item`|`object` | The project item itself. To find more information about the project item, you can use `node_id` (the node ID of the project item) and `project_node_id` (the node ID of the project) to query information in the GraphQL API. For more information, see "[Using the API to manage projects (beta)](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
+`projects_v2_item`|`object` | The project item itself. To find more information about the project item, you can use `node_id` (the node ID of the project item) and `project_node_id` (the node ID of the project) to query information in the GraphQL API. For more information, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)."
 `changes`|`object` | The changes to the project item.
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
diff --git a/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md b/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
new file mode 100644
index 0000000000..a4fb01bee5
--- /dev/null
+++ b/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
@@ -0,0 +1,45 @@
+---
+title: Getting started with GitHub Community Exchange
+shortTitle: 'Get started'
+intro: 'Learn how to access {% data variables.product.prodname_community_exchange %} and submit your repository.'
+versions:
+  fpt: '*'
+---
+
+## Introduction
+
+{% data reusables.education.about-github-community-exchange-intro %} {% data variables.product.prodname_community_exchange %} can help you make your first open source contribution or grow your own open source project.
+
+For more information about how {% data variables.product.prodname_community_exchange %} can help you as a student, see "[About {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)."
+
+## Accessing {% data variables.product.prodname_community_exchange %}
+
+{% data reusables.education.access-github-community-exchange %}
+
+## Finding interesting repositories
+
+You can browse repositories submitted to {% data variables.product.prodname_community_exchange %} from the gallery page.
+
+As you think about what open source repositories may be interesting, consider if you're wanting to learn or collaborate, or if there are particular topics or languages that could be a good starting point.
+
+When exploring repositories in the {% data variables.product.prodname_community_exchange %} gallery, you can filter available repositories by purpose, topics, or languages, and search for repositories by name and description. You can sort the list of repositories in the gallery by submission date, or by the number of stars, forks, or issues a repository has.
+
+![Screenshot of Community Exchange search box and dropdown filters](/assets/images/help/education/community-exchange-search-and-filter.png)
+
+## Starring repositories
+
+You can star repositories listed in the {% data variables.product.prodname_community_exchange %} gallery. Starring makes it easy to find a repository in the gallery again later. Starring a repository also shows appreciation to the repository maintainer for their work.
+
+Repository listings in the {% data variables.product.prodname_community_exchange %} gallery can be sorted on the number of stars a repository has.
+
+To star a repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to star, and click {% octicon "star" aria-label="The star icon" %} **Star** button found right by its name.
+
+## Reporting abuse
+
+The {% data variables.product.prodname_community_exchange %} community moderates repository submissions. You can report abusive repositories, spammy, or disruptive content at any time.
+
+To report an abusive repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to report, click the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down right by its name, then click {% octicon "report" aria-label="The report symbol" %} **Report abuse**.
+
+## Further reading
+
+- "[About {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)"
diff --git a/content/education/contribute-with-github-community-exchange/index.md b/content/education/contribute-with-github-community-exchange/index.md
new file mode 100644
index 0000000000..404f038775
--- /dev/null
+++ b/content/education/contribute-with-github-community-exchange/index.md
@@ -0,0 +1,11 @@
+---
+title: Contribute with GitHub Community Exchange
+shortTitle: '{% data variables.product.prodname_community_exchange %}'
+intro: 'With {% data variables.product.prodname_community_exchange %}, you can use {% data variables.product.product_name %} to contribute to open source and build your portfolio.'
+versions:
+  fpt: '*'
+children:
+  - /getting-started-with-github-community-exchange
+  - /submitting-your-repository-to-github-community-exchange
+  - /managing-your-submissions-to-github-community-exchange
+---
diff --git a/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md b/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
new file mode 100644
index 0000000000..ab779aac91
--- /dev/null
+++ b/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
@@ -0,0 +1,25 @@
+---
+title: Managing your submissions to GitHub Community Exchange
+shortTitle: 'Manage your submissions'
+intro: 'You can manage the purpose, topics, and offers assigned to each of your repositories in the {% data variables.product.prodname_community_exchange %} gallery, or delete your repository submissions.'
+versions:
+  fpt: '*'
+---
+
+## About your submissions
+
+During the {% data variables.product.prodname_community_exchange %} submission process, you will choose a purpose, topics, and offers for your repository. Once a repository has been submitted to {% data variables.product.prodname_community_exchange %}, it will be published with these details. For more information, see "[Submitting your repository to GitHub Community Exchange](/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange)."
+
+After you've submitted, you can still edit the topics and offers associated with your repository. You can also update the purpose of your repository by changing the corresponding topic(s). For more information, see "[Classifying your repository with topics](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics)."
+
+The language associated with your repository is the primary language used and is automatically determined by {% data variables.product.prodname_dotcom %}. For more information, see "[About repository languages](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages)."
+
+The {% data variables.product.prodname_community_exchange %} community moderates all repository submissions.
+
+## Managing your submissions
+
+1. From your {% data variables.product.prodname_global_campus %} dashboard, navigate to the {% data variables.product.prodname_community_exchange %} home page.
+1. Above the list of repositories, click the **Submissions** tab.
+  ![Screenshot of the Submissions tab](/assets/images/help/education/community-exchange-submissions-tab.png)
+1. Optionally, edit your submitted repository. To the right of the repository you want to edit, click {% octicon "pencil" aria-label="The edit icon" %} to go directly to your repository homepage. From there, you can update the purpose, topics, and offers assigned to your repository.
+1. Optionally, delete a submitted repository from the gallery. To the right of the repository submission you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
diff --git a/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md b/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
new file mode 100644
index 0000000000..3d371a3079
--- /dev/null
+++ b/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
@@ -0,0 +1,52 @@
+---
+title: Submitting your repository to GitHub Community Exchange
+shortTitle: 'Submit your repository'
+intro: 'You can submit your repository to {% data variables.product.prodname_community_exchange %} for others to view or contribute to.'
+versions:
+  fpt: '*'
+---
+
+## About repository submissions
+
+Only public repositories owned by personal accounts can be submitted to {% data variables.product.prodname_community_exchange %}.
+
+There are three types of repository submissions:
+
+- **Learn.** A repository to share step-by-step instructions to build a project.
+- **Collaborate.** A repository seeking collaborators to work on a project.
+- **Learn and Collaborate.** A repository which is a combination of `Learn` and `Collaborate`.
+
+Consider what the main purpose of your repository is when choosing the type of submission for your repository.
+
+To promote your project and make it more discoverable to other students, you should assign one or more topics and {% data variables.product.prodname_student_pack %} offers to your repository. For more information, see "[Classifying your repository with topics](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics)."
+
+Once a repository has been submitted to {% data variables.product.prodname_community_exchange %}, it will be published immediately with the purpose, topics, and offers you've chosen. The {% data variables.product.prodname_community_exchange %} community moderates all repository submissions.
+
+### Submission requirements
+
+Your repository must meet a minimum set of requirements for a submission to be accepted. During the submission process, if the submission criteria hasn't been met for your selected repository, you will be notified of the missing items.
+
+For a submission with a purpose of `Learn`, your repository must have:
+- A description.
+- A LEARN.md file to provide step-by-step instructions, with text and/or media, on how you built your project. Ideally, your LEARN.md file will deconstruct your project into small components and provide thorough details of each step, so that other students can code their project by following your instructions.
+- A README.md file to provide a detailed description of your project.
+
+For a submission with a purpose of `Collaborate`, your repository must have:
+- A description.
+- A README.md file to provide a detailed description of your project.
+- One or more issues for collaborators to work on.
+
+A good repository submission for both `Learn` and `Collaborate` purposes, is a repository that follows community standards. For more information, see "[About community profiles for public repositories](/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories)."
+
+## Submitting your repository
+
+1. From your {% data variables.product.prodname_global_campus %} dashboard, navigate to the {% data variables.product.prodname_community_exchange %} home page.
+1. Above the list of repositories, to the right of the search and dropdown filters, click **Add repository**.
+  ![Screenshot of the Add repository button](/assets/images/help/education/community-exchange-submission-add-repo.png)
+1. Use the **What is the purpose of your submission?** drop-down menu and select one or more entries matching your submission.
+  ![Screenshot of the purpose dropdown for a repository submission](/assets/images/help/education/community-exchange-repo-submission-purpose.png)
+1. Use the **Which repository would you like to use?** drop-down menu and select the repository for your submission. If the submission criteria hasn't been met, you will be notified of the missing items.
+  ![Screenshot of the repository dropdown for a repository submission](/assets/images/help/education/community-exchange-repo-submission-repo.png)
+1. Use the **Which offers did you use for your project?** drop-down menu and select one or more entries matching your submission.
+  ![Screenshot of the offers dropdown for a repository submission](/assets/images/help/education/community-exchange-repo-submission-offers.png)
+1. Click **Submit the project**.
diff --git a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange.md b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange.md
index ec7a6ca8c8..492a82f2fe 100644
--- a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange.md
+++ b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange.md
@@ -1,14 +1,14 @@
 ---
 title: About GitHub Community Exchange
-intro: 'As a student, learn the skills you need to contribute to open source projects and grow your own portfolio, with {% data variables.product.prodname_community_exchange %}.'
+intro: 'Learn the skills you need to contribute to open source projects and grow your own portfolio, with {% data variables.product.prodname_community_exchange %}.'
 versions:
   fpt: '*'
-shortTitle: Community Exchange
+shortTitle: About Community Exchange
 ---
 
 ## About {% data variables.product.prodname_community_exchange %}
 
-{% data variables.product.prodname_community_exchange %} is a student community within the {% data variables.product.prodname_global_campus %} portal. As a student, it's a place where you can get exposure for your project and discover other student repositories in need of collaborators and maintainers.
+{% data reusables.education.about-github-community-exchange-intro %}
 
 ![Screenshot of Community Exchange page](/assets/images/help/education/community-exchange-page.png)
 
@@ -21,10 +21,10 @@ You can help your peers learn open source skills, become a project maintainer, a
 - Submit a repository to teach new skills
 - Manage your repository submissions
 
-To access {% data variables.product.prodname_community_exchange %}, visit your {% data variables.product.prodname_global_campus %} dashboard at https://education.github.com.
+For more information, see "[Contribute with GitHub Community Exchange](/education/contribute-with-github-community-exchange)."
 
-If you're a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_community_exchange %} within {% data variables.product.prodname_global_campus %}.
+{% data reusables.education.access-github-community-exchange %}
 
-- If you’re a student and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [student application form]( https://education.github.com/discount_requests/student_application). For more information, see "[About GitHub Education for students](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students)."
+## Further reading
 
-- If you’re an educator and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [teacher application form]( https://education.github.com/discount_requests/teacher_application). For more information, see "[About GitHub Education for educators](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount)."
+- "[Getting started with {% data variables.product.prodname_community_exchange %}](/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange)"
diff --git a/content/education/guides.md b/content/education/guides.md
index 0d156ed2fa..21add39f20 100644
--- a/content/education/guides.md
+++ b/content/education/guides.md
@@ -46,3 +46,5 @@ Participate in the community, get training from {% data variables.product.compan
 - [{% data variables.product.prodname_education_community %}]({% data variables.product.prodname_education_forum_link %})
 - [About Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts)
 - [About Campus Advisors](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors)
+- [About {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)
+- [Contribute with GitHub Community Exchange](/education/contribute-with-github-community-exchange)
diff --git a/content/education/index.md b/content/education/index.md
index d4c2ce8d21..55ceb65dab 100644
--- a/content/education/index.md
+++ b/content/education/index.md
@@ -27,6 +27,7 @@ versions:
 children:
   - /quickstart
   - /explore-the-benefits-of-teaching-and-learning-with-github-education
+  - /contribute-with-github-community-exchange
   - /manage-coursework-with-github-classroom
   - /guides
 ---
diff --git a/content/get-started/quickstart/contributing-to-projects.md b/content/get-started/quickstart/contributing-to-projects.md
index a153893217..3e9ad2b298 100644
--- a/content/get-started/quickstart/contributing-to-projects.md
+++ b/content/get-started/quickstart/contributing-to-projects.md
@@ -27,7 +27,22 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
 1. Navigate to the `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife.
 2. Click **Fork**.
    ![Fork button](/assets/images/help/repository/fork_button.png)
-1. {% data variables.product.product_name %} will take you to your copy (your fork) of the Spoon-Knife repository.
+3. Select an owner for the forked repository.
+   ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
+4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. 
+   ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
+5. Optionally, add a description of your fork.
+   ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
+6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied.
+   ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png)
+7. Click **Create fork**.
+   ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png)
+
+{% note %}
+
+**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+
+{% endnote %}
 
 ## Cloning a fork
 
diff --git a/content/get-started/quickstart/fork-a-repo.md b/content/get-started/quickstart/fork-a-repo.md
index 420e0ba023..600c30dca4 100644
--- a/content/get-started/quickstart/fork-a-repo.md
+++ b/content/get-started/quickstart/fork-a-repo.md
@@ -57,7 +57,22 @@ You might fork a project to propose changes to the upstream, or original, reposi
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
 2. In the top-right corner of the page, click **Fork**.
-![Fork button](/assets/images/help/repository/fork_button.png)
+   ![Fork button](/assets/images/help/repository/fork_button.png)
+3. Select an owner for the forked repository.
+   ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
+4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. 
+   ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
+5. Optionally, add a description of your fork.
+   ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
+6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied.
+   ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png)
+7. Click **Create fork**.
+   ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png)
+
+
+{% note %}
+
+**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}
 
 {% endwebui %}
 
diff --git a/content/get-started/using-github/github-command-palette.md b/content/get-started/using-github/github-command-palette.md
index 751f81b7a9..c34ba5f52c 100644
--- a/content/get-started/using-github/github-command-palette.md
+++ b/content/get-started/using-github/github-command-palette.md
@@ -39,8 +39,8 @@ When you open the command palette, it shows your location at the top left and us
 {% note %}
 
 **Notes:**
-- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).
-- If you are working on a project (beta), a project-specific command palette is displayed instead. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).{% ifversion projects-v2 %}
+- If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."{% endif %}
 
 {% endnote %}
 
@@ -151,7 +151,7 @@ These commands are available from all scopes.
 |`Import repository`|Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)."  |
 |`New gist`|Open a new gist. For more information, see "[Creating a gist](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." |
 |`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." |
-|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)."  |
+|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)."  |
 |`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." |
 |`Switch theme to <theme name>`|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)." |
 
diff --git a/content/get-started/using-github/keyboard-shortcuts.md b/content/get-started/using-github/keyboard-shortcuts.md
index cf773a630a..514cc154e7 100644
--- a/content/get-started/using-github/keyboard-shortcuts.md
+++ b/content/get-started/using-github/keyboard-shortcuts.md
@@ -141,7 +141,34 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
 |<kbd>Alt</kbd> and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down <kbd>Alt</kbd> and clicking **Show outdated** or **Hide outdated**.|
 |Click, then <kbd>Shift</kbd> and click | Comment on multiple lines of a pull request by clicking a line number, holding <kbd>Shift</kbd>, then clicking another line number. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|
 
-## Project boards
+{% ifversion projects-v2 %}
+
+## {% data variables.projects.projects_v2_caps %}
+
+### Navigating a project
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>⌘</kbd>+<kbd>f</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>f</kbd> (Windows/Linux) | Focus filter field
+|<kbd>←</kbd> | Move cell focus to the left
+|<kbd>→</kbd> | Move cell focus to the right
+|<kbd>↑</kbd> | Move cell focus up
+|<kbd>↓</kbd> | Move cell focus down
+
+### Manipulating a project
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>Enter</kbd> | Toggle edit mode for the focused cell
+|<kbd>Escape</kbd> | Cancel editing for the focused cell
+|<kbd>⌘</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Windows/Linux) | Open row actions menu
+|<kbd>Shift</kbd>+<kbd>Space</kbd> | Select item
+|<kbd>Space</kbd> | Open selected item
+|<kbd>e</kbd> | Archive selected items
+
+{% endif %}
+
+## {% data variables.product.prodname_projects_v1_caps %}
 
 ### Moving a column
 
diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md b/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
index e269e27e29..ad972bcb42 100644
--- a/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
+++ b/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -16,11 +16,7 @@ topics:
   - Pull requests
 ---
 
-{% warning %}
-
-**Warning:** If you attach a file to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
-
-{% endwarning %}
+{% data reusables.repositories.anyone-can-view-anonymized-url %}
 
 To attach a file to an issue or pull request conversation, drag and drop it into the comment box. Alternatively, you can click the bar at the bottom of the comment box to browse, select, and add a file from your computer.
 
diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md b/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
index 6a28e0fdb7..658fa51f1c 100644
--- a/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
+++ b/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
@@ -44,6 +44,15 @@ Within conversations on {% data variables.product.product_name %}, references to
 If you reference an issue, pull request, or discussion in a list, the reference will unfurl to show the title and state instead. For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
 {% endif %}
 
+## Labels
+When referencing the URL of a label in Markdown, the label is automatically rendered. Only labels of the same repository are rendered, URLs pointing to a label from a different repository are rendered as any [URL](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#urls).
+
+The URL of a label can be found by navigating to the labels page and clicking on a label. For example, the URL of the label "enhancement" in our public [docs repository](https://github.com/github/docs/) is
+
+```md
+https://github.com/github/docs/labels/enhancement
+```
+
 ## Commit SHAs
 
 References to a commit's SHA hash are automatically converted into shortened links to the commit on {% data variables.product.product_name %}.
diff --git a/content/issues/guides.md b/content/issues/guides.md
index a1f73834df..cc1f1221f6 100644
--- a/content/issues/guides.md
+++ b/content/issues/guides.md
@@ -10,11 +10,11 @@ versions:
   ghae: '*'
   ghec: '*'
 includeGuides:
-  - /issues/trying-out-the-new-projects-experience/automating-projects
-  - /issues/trying-out-the-new-projects-experience/creating-a-project
-  - /issues/trying-out-the-new-projects-experience/customizing-your-project-views
-  - /issues/trying-out-the-new-projects-experience/quickstart
-  - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
+  - /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
+  - /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
+  - /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view
+  - /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
+  - /issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects
   - /issues/tracking-your-work-with-issues/quickstart
   - /issues/tracking-your-work-with-issues/creating-an-issue
   - /issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests
diff --git a/content/issues/index.md b/content/issues/index.md
index a6398bee56..9a41b4fc11 100644
--- a/content/issues/index.md
+++ b/content/issues/index.md
@@ -8,18 +8,19 @@ introLinks:
 featuredLinks:
   guides:
     - /issues/tracking-your-work-with-issues/creating-issues/creating-an-issue
-    - /issues/trying-out-the-new-projects-experience/quickstart
-    - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects
+    - /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
+    - /issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects
     - /communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
     - /issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project
   guideCards:
-    - /issues/trying-out-the-new-projects-experience/automating-projects
+    - /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view
     - /issues/tracking-your-work-with-issues/creating-issues/linking-a-pull-request-to-an-issue
     - '{% ifversion ghes or ghae %}/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards{% endif %}'
-    - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
+    - /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
   popular:
     - /issues/tracking-your-work-with-issues/creating-issues/about-issues
-    - /issues/trying-out-the-new-projects-experience/about-projects
+    - /issues/planning-and-tracking-with-projects/learning-about-projects/about-projects
+    - /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
     - /issues/tracking-your-work-with-issues/creating-issues/about-task-lists
     - /communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates
     - /issues/using-labels-and-milestones-to-track-work/managing-labels
@@ -32,8 +33,8 @@ featuredLinks:
       href: 'https://www.youtube-nocookie.com/embed/HwpVvDURHKw'
     - title: Issue Forms for open source – Luke Hefson
       href: 'https://www.youtube-nocookie.com/embed/2Yh8ueUE0oY'
-  videosHeading: GitHub Universe 2021 videos
-product_video: 'https://www.youtube-nocookie.com/embed/uiaLWluYJsA'
+  videosHeading: Videos
+product_video: '{% ifversion projects-v2 %}https://www.youtube-nocookie.com/embed/yFQ-p6wMS_Y{% else %}https://www.youtube-nocookie.com/embed/uiaLWluYJsA{% endif %}'
 layout: product-landing
 beta_product: false
 versions:
@@ -43,7 +44,7 @@ versions:
   ghec: '*'
 children:
   - /tracking-your-work-with-issues
-  - /trying-out-the-new-projects-experience
+  - /planning-and-tracking-with-projects
   - /organizing-your-work-with-project-boards
   - /using-labels-and-milestones-to-track-work
   - /guides
diff --git a/content/issues/organizing-your-work-with-project-boards/index.md b/content/issues/organizing-your-work-with-project-boards/index.md
index a24fa36cc3..4d078aae54 100644
--- a/content/issues/organizing-your-work-with-project-boards/index.md
+++ b/content/issues/organizing-your-work-with-project-boards/index.md
@@ -1,12 +1,10 @@
 ---
-title: Organizing your work with project boards
-shortTitle: Project boards
-intro: 'Use project boards to manage your work on {% data variables.product.prodname_dotcom %}'
+title: 'Organizing your work with {% data variables.product.prodname_projects_v1 %}'
+shortTitle: '{% data variables.product.prodname_projects_v1_caps %}'
+intro: 'Use {% data variables.product.prodname_projects_v1 %} to manage your work on {% data variables.product.prodname_dotcom %}'
+allowTitleToDifferFromFilename: true
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Issues
   - Projects
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
index 900568a794..26f41444fb 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
@@ -1,30 +1,28 @@
 ---
-title: About automation for project boards
-intro: You can configure automatic workflows to keep the status of project board cards in sync with the associated issues and pull requests.
+title: About automation for {% data variables.product.prodname_projects_v1 %}
+intro: You can configure automatic workflows to keep the status of {% data variables.projects.projects_v1_board %} cards in sync with the associated issues and pull requests.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/about-automation-for-project-boards
   - /articles/about-automation-for-project-boards
   - /github/managing-your-work-on-github/about-automation-for-project-boards
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
-shortTitle: Automation for project boards
+shortTitle: Automation for {% data variables.product.prodname_projects_v1 %}
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
-{% data reusables.project-management.automate-project-board-permissions %}  For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
+{% data reusables.project-management.automate-project-board-permissions %}  For more information, see "[{% data variables.product.prodname_projects_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
-You can automate actions based on triggering events for project board columns. This eliminates some of the manual tasks in managing a project board. For example, you can configure a "To do" column, where any new issues or pull requests you add to a project board are automatically moved to the configured column. For more information, see "[Configuring automation for project boards](/articles/configuring-automation-for-project-boards)."  
+You can automate actions based on triggering events for {% data variables.projects.projects_v1_board %} columns. This eliminates some of the manual tasks in managing a {% data variables.projects.projects_v1_board %}. For example, you can configure a "To do" column, where any new issues or pull requests you add to a {% data variables.projects.projects_v1_board %} are automatically moved to the configured column. For more information, see "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)."  
 
 {% data reusables.project-management.use-automated-template %}
 
 {% data reusables.project-management.copy-project-boards %}
 
-Project board automation can also help teams develop a shared understanding of a project board's purpose and the team's development process by creating a standard workflow for certain actions.
+{% data variables.projects.projects_v1_board_caps %} automation can also help teams develop a shared understanding of a {% data variables.projects.projects_v1_board %}'s purpose and the team's development process by creating a standard workflow for certain actions.
 
 {% data reusables.project-management.resync-automation %}
 
@@ -38,10 +36,10 @@ Project board automation can also help teams develop a shared understanding of a
 
 ## Project progress tracking
 
-You can track the progress on your project board. Cards in the "To do", "In progress", or "Done" columns count toward the overall project progress. {% data reusables.project-management.project-progress-locations %}
+You can track the progress on your {% data variables.projects.projects_v1_board %}. Cards in the "To do", "In progress", or "Done" columns count toward the overall project progress. {% data reusables.project-management.project-progress-locations %}
 
-For more information, see "[Tracking progress on your project board](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)."
+For more information, see "[Tracking progress on your {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)."
 
 ## Further reading
-- "[Configuring automation for project boards](/articles/configuring-automation-for-project-boards)"{% ifversion fpt or ghec %}
-- "[Copying a project board](/articles/copying-a-project-board)"{% endif %}
+- "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)"{% ifversion fpt or ghec %}
+- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %}
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
index 833004a4f8..080500a289 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
@@ -1,55 +1,53 @@
 ---
-title: About project boards
-intro: 'Project boards on {% data variables.product.product_name %} help you organize and prioritize your work. You can create project boards for specific feature work, comprehensive roadmaps, or even release checklists. With project boards, you have the flexibility to create customized workflows that suit your needs.'
+title: About {% data variables.product.prodname_projects_v1 %}
+intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/about-project-boards
   - /articles/about-projects
   - /articles/about-project-boards
   - /github/managing-your-work-on-github/about-project-boards
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
-Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop or use keyboard shortcuts to reorder cards within a column, move cards from column to column, and change the order of columns.
+{% data variables.projects.projects_v1_boards_caps %} are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop or use keyboard shortcuts to reorder cards within a column, move cards from column to column, and change the order of columns.
 
-Project board cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %}
+{% data variables.projects.projects_v1_board_caps %} cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %}
 
-You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the project board. You can create a reference card for another project board by adding a link to a note. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting project board notes to issues, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the {% data variables.projects.projects_v1_board %}. You can create a reference card for another {% data variables.projects.projects_v1_board %} by adding a link to a note. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting notes to issues, see "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)."
 
 Types of project boards:
 
-- **User-owned project boards** can contain issues and pull requests from any personal repository.
-- **Organization-wide project boards** can contain issues and pull requests from any repository that belongs to an organization.  {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
-- **Repository project boards** are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories.
+- **User-owned {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any personal repository.
+- **Organization-wide {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any repository that belongs to an organization.  {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)."
+- **Repository {% data variables.projects.projects_v1_board %}** are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories.
 
-## Creating and viewing project boards
+## Creating and viewing {% data variables.projects.projects_v1_boards %}
 
-To create a project board for your organization, you must be an organization member. Organization owners and people with project board admin permissions can customize access to the project board.
+To create a {% data variables.projects.projects_v1_board %} for your organization, you must be an organization member. Organization owners and people with {% data variables.projects.projects_v1_board %} admin permissions can customize access to the {% data variables.projects.projects_v1_board %}.
 
-If an organization-owned project board includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted.  For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
+If an organization-owned {% data variables.projects.projects_v1_board %} includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted.  For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
-The activity view shows the project board's recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down.
+The activity view shows the {% data variables.projects.projects_v1_board %}'s recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down.
 
-To find specific cards on a project board or view a subset of the cards, you can filter project board cards. For more information, see "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)."
+To find specific cards on a {% data variables.projects.projects_v1_board %} or view a subset of the cards, you can filter {% data variables.projects.projects_v1_board %} cards. For more information, see "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)."
 
-To simplify your workflow and keep completed tasks off your project board, you can archive cards. For more information, see "[Archiving cards on a project board](/articles/archiving-cards-on-a-project-board)."
+To simplify your workflow and keep completed tasks off your {% data variables.projects.projects_v1_board %}, you can archive cards. For more information, see "[Archiving cards on a {% data variables.product.prodname_project_v1 %}](/articles/archiving-cards-on-a-project-board)."
 
-If you've completed all of your project board tasks or no longer need to use your project board, you can close the project board. For more information, see "[Closing a project board](/articles/closing-a-project-board)."
+If you've completed all of your {% data variables.projects.projects_v1_board %} tasks or no longer need to use your {% data variables.projects.projects_v1_board %}, you can close the {% data variables.projects.projects_v1_board %}. For more information, see "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)."
 
-You can also [disable project boards in a repository](/articles/disabling-project-boards-in-a-repository) or [disable project boards in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way.
+You can also [disable {% data variables.projects.projects_v1_boards %} in a repository](/articles/disabling-project-boards-in-a-repository) or [disable {% data variables.projects.projects_v1_boards %} in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way.
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## Templates for project boards
+## Templates for {% data variables.projects.projects_v1_boards %}
 
-You can use templates to quickly set up a new project board. When you use a template to create a project board, your new board will include columns as well as cards with tips for using project boards. You can also choose a template with automation already configured.
+You can use templates to quickly set up a new {% data variables.projects.projects_v1_board %}. When you use a template to create a {% data variables.projects.projects_v1_board %}, your new board will include columns as well as cards with tips for using {% data variables.product.prodname_projects_v1 %}. You can also choose a template with automation already configured.
 
 | Template | Description |
 | --- | --- |
@@ -58,17 +56,17 @@ You can use templates to quickly set up a new project board. When you use a temp
 | Automated kanban with review | Cards automatically move between To do, In progress, and Done columns, with additional triggers for pull request review status |
 | Bug triage | Triage and prioritize bugs with To do, High priority, Low priority, and Closed columns |
 
-For more information on automation for project boards, see "[About automation for project boards](/articles/about-automation-for-project-boards)."
+For more information on automation for {% data variables.product.prodname_projects_v1 %}, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
 
-![Project board with basic kanban template](/assets/images/help/projects/project-board-basic-kanban-template.png)
+![{% data variables.product.prodname_project_v1 %} with basic kanban template](/assets/images/help/projects/project-board-basic-kanban-template.png)
 
 {% data reusables.project-management.copy-project-boards %}
 
 ## Further reading
 
-- "[Creating a project board](/articles/creating-a-project-board)"
-- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
-- "[Copying a project board](/articles/copying-a-project-board)"{% endif %}
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+- "[Creating a {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)"
+- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
+- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %}
+- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
 - "[Keyboard shortcuts](/articles/keyboard-shortcuts/#project-boards)"
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
index 39e797a668..43a816a1c4 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
@@ -1,18 +1,16 @@
 ---
-title: Changing project board visibility
-intro: 'As an organization owner or project board admin, you can make a project board {% ifversion ghae %}internal{% else %}public{% endif %} or private.'
+title: Changing {% data variables.product.prodname_project_v1 %} visibility
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can make a {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %} or private.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility
   - /articles/changing-project-board-visibility
   - /github/managing-your-work-on-github/changing-project-board-visibility
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
 shortTitle: Change visibility
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
@@ -20,7 +18,7 @@ shortTitle: Change visibility
 
 {% tip %}
 
-**Tip:** When you make your project board {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
+**Tip:** When you make your {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving access to teams they're on or by adding them to the {% data variables.projects.projects_v1_board %} as a collaborator. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% endtip %}
 
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
index c75fb54ace..23bb9ce219 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
@@ -1,35 +1,33 @@
 ---
-title: Closing a project board
-intro: 'If you''ve completed all the tasks in a project board or no longer need to use a project board, you can close the project board.'
+title: Closing a {% data variables.product.prodname_project_v1 %}
+intro: 'If you''ve completed all the tasks in a {% data variables.projects.projects_v1_board %} or no longer need to use a {% data variables.projects.projects_v1_board %}, you can close the {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/closing-a-project-board
   - /articles/closing-a-project
   - /articles/closing-a-project-board
   - /github/managing-your-work-on-github/closing-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
-When you close a project board, any configured workflow automation will pause by default.
+When you close a {% data variables.projects.projects_v1_board %}, any configured workflow automation will pause by default.
 
-If you reopen a project board, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board. For more information, see "[Reopening a closed project board](/articles/reopening-a-closed-project-board)" or "[About automation for project boards](/articles/about-automation-for-project-boards)."
+If you reopen a {% data variables.projects.projects_v1_board %}, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board. For more information, see "[Reopening a closed {% data variables.product.prodname_project_v1 %}](/articles/reopening-a-closed-project-board)" or "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
 
-1. Navigate to the list of project boards in your repository or organization, or owned by your personal account.
-2. In the projects list, next to the project board you want to close, click {% octicon "chevron-down" aria-label="The chevron icon" %}.
+1. Navigate to the list of {% data variables.projects.projects_v1_boards %} in your repository or organization, or owned by your personal account.
+2. In the projects list, next to the {% data variables.projects.projects_v1_board %} you want to close, click {% octicon "chevron-down" aria-label="The chevron icon" %}.
 ![Chevron icon to the right of the project board's name](/assets/images/help/projects/project-list-action-chevron.png)
 3. Click **Close**.
 ![Close item in the project board's drop-down menu](/assets/images/help/projects/close-project.png)
 
 ## Further reading
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Deleting a project board](/articles/deleting-a-project-board)"
-- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)"
-- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Deleting a {% data variables.product.prodname_project_v1 %}](/articles/deleting-a-project-board)"
+- "[Disabling {% data variables.product.prodname_projects_v1 %} in a repository](/articles/disabling-project-boards-in-a-repository)"
+- "[Disabling {% data variables.product.prodname_projects_v1 %} in your organization](/articles/disabling-project-boards-in-your-organization)"
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
index cccec582e3..bf3817ccec 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
@@ -1,15 +1,12 @@
 ---
-title: Configuring automation for project boards
-intro: You can set up automatic workflows to move issues and pull requests to a project board column when a specified event occurs.
+title: Configuring automation for {% data variables.product.prodname_projects_v1 %}
+intro: You can set up automatic workflows to move issues and pull requests to a {% data variables.projects.projects_v1_board %} column when a specified event occurs.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/configuring-automation-for-project-boards
   - /articles/configuring-automation-for-project-boards
   - /github/managing-your-work-on-github/configuring-automation-for-project-boards
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
   - Projects
@@ -17,10 +14,11 @@ topics:
   - Project management
 shortTitle: Configure automation
 type: how_to
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
-{% data reusables.project-management.automate-project-board-permissions %} For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards)."
+{% data reusables.project-management.automate-project-board-permissions %} For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
 
 {% data reusables.project-management.use-automated-template %}
 
@@ -32,7 +30,7 @@ type: how_to
 
 {% endtip %}
 
-1. Navigate to the project board you want to automate.
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to automate.
 2. In the column you want to automate, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
 ![Edit icon](/assets/images/help/projects/edit-column-button.png)
 3. Click **Manage automation**.
@@ -44,4 +42,4 @@ type: how_to
 6. Click **Update automation**.
 
 ## Further reading
-- "[About automation for project boards](/articles/about-automation-for-project-boards)"
+- "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)"
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
index a2d0358259..77942f76dd 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
@@ -1,6 +1,8 @@
 ---
-title: Copying a project board
-intro: You can copy a project board to quickly create a new project. Copying frequently used or highly customized project boards helps standardize your workflow.
+title: Copying a {% data variables.product.prodname_project_v1 %}
+intro: You can copy a {% data variables.projects.projects_v1_board %}
+ to quickly create a new project. Copying frequently used or highly customized {% data variables.projects.projects_v1_boards %}
+ helps standardize your workflow.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/copying-a-project-board
   - /articles/copying-a-project-board
@@ -10,24 +12,25 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
-Copying a project board allows you to reuse a project board's title, description, and automation configuration. You can copy project boards to eliminate the manual process of creating new project boards for similar workflows.
+Copying a {% data variables.projects.projects_v1_board %} allows you to reuse a {% data variables.projects.projects_v1_board %}'s title, description, and automation configuration. You can copy {% data variables.projects.projects_v1_boards %} to eliminate the manual process of creating new {% data variables.projects.projects_v1_boards %} for similar workflows.
 
-You must have read access to a project board to copy it to a repository or organization where you have write access.
+You must have read access to a {% data variables.projects.projects_v1_board %} to copy it to a repository or organization where you have write access.
 
-When you copy a project board to an organization, the project board's visibility will default to private, with an option to change the visibility. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility/)."
+When you copy a {% data variables.projects.projects_v1_board %} to an organization, the {% data variables.projects.projects_v1_board %}'s visibility will default to private, with an option to change the visibility. For more information, see "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility/)."
 
-A project board's automation is also enabled by default. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards/)."
+A {% data variables.projects.projects_v1_board %}'s automation is also enabled by default. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards/)."
 
-1. Navigate to the project board you want to copy.
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to copy.
 {% data reusables.project-management.click-menu %}
 3. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Copy**.
 ![Copy option in drop-down menu from project board sidebar](/assets/images/help/projects/project-board-copy-setting.png)
 4. Under "Owner", use the drop-down menu and click the repository or organization where you want to copy the project board.
 ![Select owner of copied project board from drop-down menu](/assets/images/help/projects/copied-project-board-owner.png)
-5. Optionally, under "Project board name", type the name of the copied project board.
+5. Optionally, under "Project board name", type the name of the copied {% data variables.projects.projects_v1_board %}.
 ![Field to type a name for the copied project board](/assets/images/help/projects/copied-project-board-name.png)
 6. Optionally, under "Description", type a description of the copied project board that other people will see.
 ![Field to type a description for the copied project board](/assets/images/help/projects/copied-project-board-description.png)
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
index 92610d66c9..c607acad1f 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
@@ -1,22 +1,20 @@
 ---
-title: Creating a project board
-intro: 'Project boards can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.'
+title: Creating a {% data variables.product.prodname_project_v1 %}
+intro: '{% data variables.projects.projects_v1_boards_caps %} can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board
   - /articles/creating-a-project
   - /articles/creating-a-project-board
   - /github/managing-your-work-on-github/creating-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
   - Issues
   - Projects
   - Project management
 type: how_to
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
@@ -24,21 +22,23 @@ type: how_to
 
 {% data reusables.project-management.copy-project-boards %}
 
-{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
+{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}
+](/articles/linking-a-repository-to-a-project-board)."
 
-Once you've created your project board, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+Once you've created your {% data variables.projects.projects_v1_board %}, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)."
 
-You can also configure workflow automations to keep your project board in sync with the status of issues and pull requests. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards)."
+You can also configure workflow automations to keep your {% data variables.projects.projects_v1_board %} in sync with the status of issues and pull requests. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## Creating a user-owned project board
+## Creating a user-owned {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
 {% data reusables.profile.access_profile %}
 2. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
-![Project tab](/assets/images/help/projects/user-projects-tab.png)
+![Project tab](/assets/images/help/projects/user-projects-tab.png){% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
@@ -54,13 +54,14 @@ You can also configure workflow automations to keep your project board in sync w
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Creating an organization-wide project board
+## Creating an organization-wide {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
@@ -76,13 +77,14 @@ You can also configure workflow automations to keep your project board in sync w
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Creating a repository project board
+## Creating a repository {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
 {% data reusables.repositories.navigate-to-repo %}
 2. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
-![Project tab](/assets/images/help/projects/repo-tabs-projects.png)
+![Project tab](/assets/images/help/projects/repo-tabs-projects.png){% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
index 1c13437734..875f1ce7c3 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
@@ -1,28 +1,26 @@
 ---
-title: Deleting a project board
-intro: You can delete an existing project board if you no longer need access to its contents.
+title: Deleting a {% data variables.product.prodname_project_v1 %}
+intro: You can delete an existing {% data variables.projects.projects_v1_board %} if you no longer need access to its contents.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board
   - /articles/deleting-a-project
   - /articles/deleting-a-project-board
   - /github/managing-your-work-on-github/deleting-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Tip**: If you'd like to retain access to a completed or unneeded project board without losing access to its contents, you can [close the project board](/articles/closing-a-project-board) instead of deleting it.
+**Tip**: If you'd like to retain access to a completed or unneeded {% data variables.projects.projects_v1_board %} without losing access to its contents, you can [close the {% data variables.projects.projects_v1_board %}](/articles/closing-a-project-board) instead of deleting it.
 
 {% endtip %}
 
-1. Navigate to the project board you want to delete.
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to delete.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.click-edit-sidebar-menu-project-board %}
 4. Click **Delete project**.
@@ -31,6 +29,6 @@ topics:
 
 ## Further reading
 
-- "[Closing a project board](/articles/closing-a-project-board)"
-- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)"
-- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)"
+- "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)"
+- "[Disabling {% data variables.product.prodname_project_v1_caps %} in a repository](/articles/disabling-project-boards-in-a-repository)"
+- "[Disabling {% data variables.product.prodname_project_v1_caps %} in your organization](/articles/disabling-project-boards-in-your-organization)"
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
index e80b1eec6e..800d88786e 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Editing a project board
-intro: You can edit the title and description of an existing project board.
+title: Editing a {% data variables.product.prodname_project_v1 %}
+intro: You can edit the title and description of an existing {% data variables.projects.projects_v1_board %}.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/editing-a-project-board
   - /articles/editing-a-project
@@ -8,29 +8,27 @@ redirect_from:
   - /articles/editing-a-project-board
   - /github/managing-your-work-on-github/editing-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Tip:** For details on adding, removing, or editing columns in your project board, see "[Creating a project board](/articles/creating-a-project-board)."
+**Tip:** For details on adding, removing, or editing columns in your {% data variables.projects.projects_v1_board %}, see "[Creating a {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)."
 
 {% endtip %}
 
-1. Navigate to the project board you want to edit.
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to edit.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.click-edit-sidebar-menu-project-board %} 
-4. Modify the project board name and description as needed, then click **Save project**.
+4. Modify the {% data variables.projects.projects_v1_board %} name and description as needed, then click **Save project**.
 ![Fields with the project board name and description, and Save project button](/assets/images/help/projects/edit-project-board-save-button.png)
 
 ## Further reading
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Deleting a project board](/articles/deleting-a-project-board)"
+- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[Deleting a {% data variables.product.prodname_project_v1 %}](/articles/deleting-a-project-board)"
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
index ada41ccd40..5959e245db 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
@@ -1,12 +1,9 @@
 ---
-title: Managing project boards
-shortTitle: Managing project boards
-intro: Learn how to create and manage project boards
+title: Managing {% data variables.product.prodname_projects_v1 %}
+shortTitle: Managing {% data variables.product.prodname_projects_v1 %}
+intro: Learn how to create and manage {% data variables.projects.projects_v1_boards %}
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Issues
   - Projects
@@ -24,6 +21,7 @@ children:
   - /deleting-a-project-board
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
index 1c5c663bc8..7e94574247 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
@@ -1,26 +1,24 @@
 ---
-title: Linking a repository to a project board
-intro: You can link a repository to your organization's or personal account's project board.
+title: Linking a repository to a {% data variables.product.prodname_project_v1 %}
+intro: You can link a repository to your organization's or personal account's {% data variables.projects.projects_v1_board %}.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/linking-a-repository-to-a-project-board
   - /articles/linking-a-repository-to-a-project-board
   - /github/managing-your-work-on-github/linking-a-repository-to-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
 shortTitle: Link repository to board
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
-Anyone with write permissions to a project board can link repositories owned by that organization or personal account to the project board. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization/)" or "[Permission levels for user-owned project boards](/articles/permission-levels-for-user-owned-project-boards/)."
+Anyone with write permissions to a {% data variables.projects.projects_v1_board %} can link repositories owned by that organization or personal account to the {% data variables.projects.projects_v1_board %}. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization/)" or "[Permission levels for user-owned {% data variables.product.prodname_projects_v1 %}](/articles/permission-levels-for-user-owned-project-boards/)."
 
-{% data reusables.project-management.link-repos-to-project-board %} You can add issues and pull requests from any unlinked repositories by typing the issue or pull request URL in a card. For more information, see "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)."
+{% data reusables.project-management.link-repos-to-project-board %} You can add issues and pull requests from any unlinked repositories by typing the issue or pull request URL in a card. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)."
 
-1. Navigate to the project board where you want to link a repository.
+1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to link a repository.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
 4. In the left sidebar, click **Linked repositories**.
@@ -34,10 +32,10 @@ Anyone with write permissions to a project board can link repositories owned by
 
 {% note %}
 
-**Note:** In order to link a repository to your organization or user owned project board the repository needs to have issues enabled. That is, the repository has an "Issues" tab (in forked repositories issues are disabled by default).  For information on how to enable or disable issues for a repository, see "[Disabling issues for a repository](/github/managing-your-work-on-github/disabling-issues)."
+**Note:** In order to link a repository to your organization or user owned {% data variables.projects.projects_v1_board %} the repository needs to have issues enabled. That is, the repository has an "Issues" tab (in forked repositories issues are disabled by default).  For information on how to enable or disable issues for a repository, see "[Disabling issues for a repository](/github/managing-your-work-on-github/disabling-issues)."
 
 {% endnote %}
 
 ## Further reading
 
-- "[About projects boards](/articles/about-project-boards)"
+- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
index b290d300bc..56046b8806 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
@@ -1,33 +1,31 @@
 ---
-title: Reopening a closed project board
-intro: You can reopen a closed project board and restart any workflow automation that was configured for the project board.
+title: Reopening a closed {% data variables.product.prodname_project_v1 %}
+intro: You can reopen a closed {% data variables.projects.projects_v1_board %} and restart any workflow automation that was configured for the {% data variables.projects.projects_v1_board %}.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board
   - /articles/reopening-a-closed-project-board
   - /github/managing-your-work-on-github/reopening-a-closed-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
-shortTitle: Reopen project board
+shortTitle: Reopen {% data variables.product.prodname_project_v1 %}
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
-When you close a project board, any workflow automation that was configured for the project board will pause by default. For more information, see "[Closing a project board](/articles/closing-a-project-board)."
+When you close a {% data variables.projects.projects_v1_board %}, any workflow automation that was configured for the {% data variables.projects.projects_v1_board %} will pause by default. For more information, see "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)."
 
-When you reopen a project board, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board.
+When you reopen a {% data variables.projects.projects_v1_board %}, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board.
 
-1. Navigate to the project board you want to reopen.
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to reopen.
 {% data reusables.project-management.click-menu %}
-3. Choose whether to sync automation for your project board or reopen your project board without syncing.
-    - To reopen your project board and sync automation, click **Reopen and sync project**.
+3. Choose whether to sync automation for your {% data variables.projects.projects_v1_board %} or reopen your {% data variables.projects.projects_v1_board %} without syncing.
+    - To reopen your {% data variables.projects.projects_v1_board %} and sync automation, click **Reopen and sync project**.
   ![Select "Reopen and resync project" button](/assets/images/help/projects/reopen-and-sync-project.png)
-    - To reopen your project board without syncing automation, using the reopen drop-down menu, click **Reopen only**. Then, click **Reopen only**.
+    - To reopen your {% data variables.projects.projects_v1_board %} without syncing automation, using the reopen drop-down menu, click **Reopen only**. Then, click **Reopen only**.
   ![Reopen closed project board drop-down menu](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png)
 
 ## Further reading
 
-- "[Configuring automation for project boards](/articles/configuring-automation-for-project-boards)"
+- "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)"
diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
index 6c67376231..445aa3fb86 100644
--- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
@@ -1,26 +1,24 @@
 ---
-title: Adding issues and pull requests to a project board
-intro: You can add issues and pull requests to a project board in the form of cards and triage them into columns.
+title: Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}
+intro: You can add issues and pull requests to a {% data variables.projects.projects_v1_board %} in the form of cards and triage them into columns.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board
   - /articles/adding-issues-and-pull-requests-to-a-project
   - /articles/adding-issues-and-pull-requests-to-a-project-board
   - /github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
-shortTitle: Add issues & PRs to board
+shortTitle: Add issues & PRs to {% data variables.product.prodname_project_v1 %}
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
-You can add issue or pull request cards to your project board by:
+You can add issue or pull request cards to your {% data variables.projects.projects_v1_board %} by:
 - Dragging cards from the **Triage** section in the sidebar.
 - Typing the issue or pull request URL in a card.
-- Searching for issues or pull requests in the project board search sidebar.
+- Searching for issues or pull requests in the {% data variables.projects.projects_v1_board %} search sidebar.
 
 You can put a maximum of 2,500 cards into each project column. If a column has reached the maximum number of cards, no cards can be moved into that column.
 
@@ -28,30 +26,30 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
 
 {% note %}
 
-**Note:** You can also add notes to your project board to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your project board. For more information, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+**Note:** You can also add notes to your project board to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your {% data variables.projects.projects_v1_board %}. For more information, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
 
 {% endnote %}
 
 {% data reusables.project-management.edit-in-project %}
 
-{% data reusables.project-management.link-repos-to-project-board %} When you search for issues and pull requests to add to your project board, the search automatically scopes to your linked repositories. You can remove these qualifiers to search within all organization repositories. For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
+{% data reusables.project-management.link-repos-to-project-board %} When you search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %}, the search automatically scopes to your linked repositories. You can remove these qualifiers to search within all organization repositories. For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
 
-## Adding issues and pull requests to a project board
+## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %}
 
-1. Navigate to the project board where you want to add issues and pull requests.
-2. In your project board, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**.
+1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add issues and pull requests.
+2. In your {% data variables.projects.projects_v1_board %}, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**.
 ![Add cards button](/assets/images/help/projects/add-cards-button.png)
-3. Search for issues and pull requests to add to your project board using search qualifiers. For more information on search qualifiers you can use, see "[Searching issues](/articles/searching-issues)."
+3. Search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %} using search qualifiers. For more information on search qualifiers you can use, see "[Searching issues](/articles/searching-issues)."
   ![Search issues and pull requests](/assets/images/help/issues/issues_search_bar.png)
 
   {% tip %}
 
   **Tips:**
     - You can also add an issue or pull request by typing the URL in a card.
-    - If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your project board by searching for the label name. For more information, see "[Apply labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests)."
+    - If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your {% data variables.projects.projects_v1_board %} by searching for the label name. For more information, see "[Apply labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests)."
 
   {% endtip %}
-4. From the filtered list of issues and pull requests, drag the card you'd like to add to your project board and drop it in the correct column. Alternatively, you can move cards using keyboard shortcuts. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+4. From the filtered list of issues and pull requests, drag the card you'd like to add to your {% data variables.projects.projects_v1_board %} and drop it in the correct column. Alternatively, you can move cards using keyboard shortcuts. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
 
     {% tip %}
 
@@ -59,21 +57,21 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
 
     {% endtip %}
 
-## Adding issues and pull requests to a project board from the sidebar
+## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %} from the sidebar
 
 1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-label="The Gear icon" %}**.
   ![Project board button in sidebar](/assets/images/help/projects/sidebar-project.png)
-2. Click the **Recent**, **Repository**,**User**, or **Organization** tab for the project board you would like to add to.
+2. Click the **Recent**, **Repository**,**User**, or **Organization** tab for the {% data variables.projects.projects_v1_board %} you would like to add to.
   ![Recent, Repository and Organization tabs](/assets/images/help/projects/sidebar-project-tabs.png)
 3. Type the name of the project in **Filter projects** field.
   ![Project board search box](/assets/images/help/projects/sidebar-search-project.png)
-4. Select one or more project boards where you want to add the issue or pull request.
+4. Select one or more {% data variables.projects.projects_v1_boards %} where you want to add the issue or pull request.
   ![Selected project board](/assets/images/help/projects/sidebar-select-project.png)
-5. Click {% octicon "triangle-down" aria-label="The down triangle icon" %}, then click the column where you want your issue or pull request. The card will move to the bottom of the project board column you select.
+5. Click {% octicon "triangle-down" aria-label="The down triangle icon" %}, then click the column where you want your issue or pull request. The card will move to the bottom of the {% data variables.projects.projects_v1_board %} column you select.
   ![Move card to column menu](/assets/images/help/projects/sidebar-select-project-board-column-menu.png)
 
 ## Further reading
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Editing a project board](/articles/editing-a-project-board)"
-- "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)"
+- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"
+- "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)"
diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
index 2cf815d675..c0b1c48945 100644
--- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
@@ -1,19 +1,17 @@
 ---
-title: Adding notes to a project board
-intro: You can add notes to a project board to serve as task reminders or to add information related to the project board.
+title: Adding notes to a {% data variables.product.prodname_project_v1 %}
+intro: You can add notes to a {% data variables.projects.projects_v1_board %} to serve as task reminders or to add information related to the {% data variables.projects.projects_v1_board %}.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board
   - /articles/adding-notes-to-a-project
   - /articles/adding-notes-to-a-project-board
   - /github/managing-your-work-on-github/adding-notes-to-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
-shortTitle: Add notes to board
+shortTitle: Add notes to {% data variables.product.prodname_project_v1 %}
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
@@ -22,17 +20,17 @@ shortTitle: Add notes to board
 **Tips:**
 - You can format your note using Markdown syntax. For example, you can use headings, links, task lists, or emoji. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)."
 - You can drag and drop or use keyboard shortcuts to reorder notes and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
-- Your project board must have at least one column before you can add notes. For more information, see "[Creating a project board](/articles/creating-a-project-board)."
+- Your {% data variables.projects.projects_v1_board %} must have at least one column before you can add notes. For more information, see "[Creating a project board](/articles/creating-a-project-board)."
 
 {% endtip %}
 
-When you add a URL for an issue, pull request, or another project board to a note, you'll see a preview in a summary card below your text.
+When you add a URL for an issue, pull request, or another {% data variables.projects.projects_v1_board %} to a note, you'll see a preview in a summary card below your text.
 
 ![Project board cards showing a preview of an issue and another project board](/assets/images/help/projects/note-with-summary-card.png)
 
-## Adding notes to a project board
+## Adding notes to a {% data variables.projects.projects_v1_board %}
 
-1. Navigate to the project board where you want to add notes.
+1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add notes.
 2. In the column you want to add a note to, click {% octicon "plus" aria-label="The plus icon" %}.
 ![Plus icon in the column header](/assets/images/help/projects/add-note-button.png)
 3. Type your note, then click **Add**.
@@ -52,7 +50,7 @@ When you convert a note to an issue, the issue is automatically created using th
 
 {% tip %}
 
-**Tip:** You can add content in the body of your note to @mention someone, link to another issue or pull request, and add emoji. These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within project board notes, but once your note is converted to an issue, they'll appear correctly. For more information on using these features, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)."
+**Tip:** You can add content in the body of your note to @mention someone, link to another issue or pull request, and add emoji. These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within {% data variables.projects.projects_v1_board %} notes, but once your note is converted to an issue, they'll appear correctly. For more information on using these features, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)."
 
 {% endtip %}
 
@@ -60,12 +58,12 @@ When you convert a note to an issue, the issue is automatically created using th
 {% data reusables.project-management.project-note-more-options %}
 3. Click **Convert to issue**.
   ![Convert to issue button](/assets/images/help/projects/convert-to-issue.png)
-4. If the card is on an organization-wide project board, in the drop-down menu, choose the repository you want to add the issue to.
+4. If the card is on an organization-wide {% data variables.projects.projects_v1_board %}, in the drop-down menu, choose the repository you want to add the issue to.
   ![Drop-down menu listing repositories where you can create the issue](/assets/images/help/projects/convert-note-choose-repository.png)
 5. Optionally, edit the pre-filled issue title, and type an issue body.
   ![Fields for issue title and body](/assets/images/help/projects/convert-note-issue-title-body.png)
 6. Click **Convert to issue**.
-7. The note is automatically converted to an issue. In the project board, the new issue card will be in the same location as the previous note.
+7. The note is automatically converted to an issue. In the {% data variables.projects.projects_v1_board %}, the new issue card will be in the same location as the previous note.
 
 ## Editing and removing a note
 
@@ -78,7 +76,7 @@ When you convert a note to an issue, the issue is automatically created using th
 
 ## Further reading
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Creating a project board](/articles/creating-a-project-board)"
-- "[Editing a project board](/articles/editing-a-project-board)"
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Creating a {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)"
+- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"
+- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
index b7d8e6e244..f232d9d14b 100644
--- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
@@ -1,34 +1,32 @@
 ---
-title: Archiving cards on a project board
-intro: You can archive project board cards to declutter your workflow without losing the historical context of a project.
+title: Archiving cards on a {% data variables.product.prodname_project_v1 %}
+intro: You can archive {% data variables.projects.projects_v1_board %} cards to declutter your workflow without losing the historical context of a project.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/archiving-cards-on-a-project-board
   - /articles/archiving-cards-on-a-project-board
   - /github/managing-your-work-on-github/archiving-cards-on-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
-shortTitle: Archive cards on board
+shortTitle: Archive cards on {% data variables.product.prodname_project_v1 %}
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
-Automation in your project board does not apply to archived project board cards. For example, if you close an issue in a project board's archive, the archived card does not automatically move to the "Done" column. When you restore a card from the project board archive, the card will return to the column where it was archived.
+Automation in your {% data variables.projects.projects_v1_board %} does not apply to archived {% data variables.projects.projects_v1_board %} cards. For example, if you close an issue in a {% data variables.projects.projects_v1_board %}'s archive, the archived card does not automatically move to the "Done" column. When you restore a card from the {% data variables.projects.projects_v1_board %} archive, the card will return to the column where it was archived.
 
-## Archiving cards on a project board
+## Archiving cards on a {% data variables.projects.projects_v1_board %}
 
-1. In a project board, find the card you want to archive, then click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+1. In a {% data variables.projects.projects_v1_board %}, find the card you want to archive, then click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
 ![List of options for editing a project board card](/assets/images/help/projects/select-archiving-options-project-board-card.png)
 2. Click **Archive**.
 ![Select archive option from menu](/assets/images/help/projects/archive-project-board-card.png)
 
-## Restoring cards on a project board from the sidebar
+## Restoring cards on a {% data variables.projects.projects_v1_board %} from the sidebar
 
 {% data reusables.project-management.click-menu %}
 2. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **View archive**.
   ![Select view archive option from menu](/assets/images/help/projects/select-view-archive-option-project-board-card.png)
-3. Above the project board card you want to unarchive, click **Restore**.
+3. Above the {% data variables.projects.projects_v1_board %} card you want to unarchive, click **Restore**.
   ![Select restore project board card](/assets/images/help/projects/restore-card.png)
diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
index df592acef0..2d0aa56149 100644
--- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
@@ -1,24 +1,22 @@
 ---
-title: Filtering cards on a project board
-intro: You can filter the cards on a project board to search for specific cards or view a subset of the cards.
+title: Filtering cards on a {% data variables.product.prodname_project_v1 %}
+intro: You can filter the cards on a {% data variables.projects.projects_v1_board %} to search for specific cards or view a subset of the cards.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/filtering-cards-on-a-project-board
   - /articles/filtering-cards-on-a-project-board
   - /github/managing-your-work-on-github/filtering-cards-on-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
-shortTitle: Filter cards on board
+shortTitle: Filter cards on {% data variables.product.prodname_project_v1 %}
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
-On a card, you can click any assignee, milestone, or label to filter the project board by that qualifier. To clear the search, you can click the same assignee, milestone, or label again.
+On a card, you can click any assignee, milestone, or label to filter the {% data variables.projects.projects_v1_board %} by that qualifier. To clear the search, you can click the same assignee, milestone, or label again.
 
-You can also use the "Filter cards" search bar at the top of each project board to search for cards. You can filter cards using the following search qualifiers in any combination, or by simply typing some text you'd like to search for.
+You can also use the "Filter cards" search bar at the top of each {% data variables.projects.projects_v1_board %} to search for cards. You can filter cards using the following search qualifiers in any combination, or by simply typing some text you'd like to search for.
 
 - Filter cards by author using `author:USERNAME`
 - Filter cards by assignee using `assignee:USERNAME` or `no:assignee`
@@ -30,9 +28,9 @@ You can also use the "Filter cards" search bar at the top of each project board
 - Filter cards by type using `type:issue`, `type:pr`, or `type:note`
 - Filter cards by state and type using `is:open`, `is:closed`, or `is:merged`; and `is:issue`, `is:pr`, or `is:note`
 - Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr`
-- Filter cards by repository in an organization-wide project board using `repo:ORGANIZATION/REPOSITORY`
+- Filter cards by repository in an organization-wide {% data variables.projects.projects_v1_board %} using `repo:ORGANIZATION/REPOSITORY`
 
-1. Navigate to the project board that contains the cards you want to filter.
+1. Navigate to the {% data variables.projects.projects_v1_board %} that contains the cards you want to filter.
 2. Above the project card columns, click into the "Filter cards" search bar and type a search query to filter the cards.
 ![Filter card search bar](/assets/images/help/projects/filter-card-search-bar.png)
 
@@ -44,6 +42,6 @@ You can also use the "Filter cards" search bar at the top of each project board
 
 ## Further reading
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)"
+- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)"
diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
index 563070720c..cc5e8fc2e8 100644
--- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
+++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
@@ -1,12 +1,9 @@
 ---
-title: Tracking progress on your project board
-shortTitle: Tracking projects
-intro: Learn how to track your work on project boards
+title: Tracking progress on your {% data variables.product.prodname_projects_v1 %}
+shortTitle: Tracking {% data variables.product.prodname_projects_v1 %}
+intro: Learn how to track your work on {% data variables.projects.projects_v1_board %}
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Issues
   - Projects
@@ -18,6 +15,7 @@ children:
   - /archiving-cards-on-a-project-board
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
index dde14695ee..1d9ce8bb28 100644
--- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
@@ -1,24 +1,22 @@
 ---
-title: Tracking progress on your project board
-intro: You can see the overall progress of your project in a progress bar.
+title: Tracking progress on your {% data variables.product.prodname_project_v1 %}
+intro: You can see the overall progress of your {% data variables.projects.projects_v1_board %} in a progress bar.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/tracking-progress-on-your-project-board
   - /articles/tracking-progress-on-your-project-board
   - /github/managing-your-work-on-github/tracking-progress-on-your-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: "projects-v1"
 topics:
   - Pull requests
-shortTitle: Track progress on board
+shortTitle: Track progress on {% data variables.product.prodname_project_v1 %}
+allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
 {% data reusables.project-management.project-progress-locations %}
 
-1. Navigate to the project board where you want to enable or disable project progress tracking.  
+1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to enable or disable project progress tracking.  
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.click-edit-sidebar-menu-project-board %}
 4. Select or deselect **Track project progress**.
diff --git a/content/issues/trying-out-the-new-projects-experience/automating-projects.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
similarity index 94%
rename from content/issues/trying-out-the-new-projects-experience/automating-projects.md
rename to content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
index 0fb4d7c983..e58ee7f479 100644
--- a/content/issues/trying-out-the-new-projects-experience/automating-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
@@ -1,33 +1,18 @@
 ---
-title: Automating projects (beta)
-intro: 'You can use built-in workflows or the API and {% data variables.product.prodname_actions %} to manage your projects.'
-allowTitleToDifferFromFilename: true
+title: 'Automating {% data variables.product.prodname_projects_v2 %} using Actions'
+shortTitle: 'Automating with Actions'
+intro: 'You can use {% data variables.product.prodname_actions %} to automate your projects.'
 miniTocMaxHeadingLevel: 3
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/automating-projects
 type: tutorial
 topics:
   - Projects
-  - Workflows
-  - Project management
+allowTitleToDifferFromFilename: true
 ---
 
-{% data reusables.projects.projects-beta %}
-
-{% data reusables.projects.graphql-deprecation %}
-
-## Introduction
-
-You can add automation to help manage your project. Projects (beta) includes built-in workflows that you can configure through the UI. Additionally, you can write custom workflows with the GraphQL API and {% data variables.product.prodname_actions %}.
-
-## Built-in workflows
-
-{% data reusables.projects.about-workflows %}
-
-You can enable or disable the built-in workflows for your project.
-
-{% data reusables.projects.enable-basic-workflow %}
 
 ## {% data variables.product.prodname_actions %} workflows
 
@@ -39,11 +24,13 @@ A project can span multiple repositories, but a workflow is specific to a reposi
 
 This article assumes that you have a basic understanding of {% data variables.product.prodname_actions %}. For more information about {% data variables.product.prodname_actions %}, see "[{% data variables.product.prodname_actions %}](/actions)."
 
-For more information about other changes you can make to your project through the API, see "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
+For more information about other changes you can make to your project through the API, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)."
+
+You may also want to use the **actions/add-to-project** workflow, which is maintained by {% data variables.product.company_short %} and will add the current issue or pull request to the project specified. For more information, see the [actions/add-to-project](https://github.com/actions/add-to-project) repository and README.
 
 {% note %}
 
-**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access projects (beta). To access projects (beta) you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a personal access token (recommended for user projects). Workflow examples for both approaches are shown below.
+**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access {% data variables.projects.projects_v2 %}. To access {% data variables.projects.projects_v2 %} you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a personal access token (recommended for user projects). Workflow examples for both approaches are shown below.
 
 {% endnote %}
 
diff --git a/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
new file mode 100644
index 0000000000..0feea7fef0
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
@@ -0,0 +1,15 @@
+---
+title: 'Automating your {% data variables.projects.project_v2 %}'
+shortTitle: 'Automating {% data variables.projects.projects_v2 %}'
+intro: 'Learn how to use the built-in workflows, {% data variables.product.prodname_actions %}, and the API to automate your projects.'
+versions:
+  feature: "projects-v2"
+topics:
+  - Issues
+  - Projects
+children:
+  - /using-the-built-in-automations
+  - /using-the-api-to-manage-projects
+  - /automating-projects-using-actions
+allowTitleToDifferFromFilename: true
+---
diff --git a/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
similarity index 95%
rename from content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
rename to content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
index 590686dd2a..3f9bead44b 100644
--- a/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
@@ -1,22 +1,22 @@
 ---
-title: Using the API to manage projects (beta)
-intro: You can use the GraphQL API to find information about projects and to update projects.
-versions:
-  fpt: '*'
-  ghec: '*'
+title: 'Using the API to manage {% data variables.product.prodname_projects_v2 %}'
+shortTitle: 'Automating with the API'
+intro: 'You can use the GraphQL API to automate your projects.'
 miniTocMaxHeadingLevel: 3
-allowTitleToDifferFromFilename: true
-type: how_to
+versions:
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
+type: tutorial
 topics:
   - Projects
+allowTitleToDifferFromFilename: true
 ---
 
+This article demonstrates how to use the GraphQL API to manage a project. For more information about how to use the API in a {% data variables.product.prodname_actions %} workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)." For a full list of the available data types, see "[Reference](/graphql/reference)."
+
 {% data reusables.projects.graphql-deprecation %}
 
-This article demonstrates how to use the GraphQL API to manage a project. For more information about how to use the API in a {% data variables.product.prodname_actions %} workflow, see "[Automating projects (beta)](/issues/trying-out-the-new-projects-experience/automating-projects)." For a full list of the available data types, see "[Reference](/graphql/reference)."
-
-{% data reusables.projects.projects-beta %}
-
 ## Authentication
 
 {% curl %}
@@ -714,3 +714,7 @@ gh api graphql -f query='
   }'
 ```
 {% endcli %}
+
+## Using webhooks
+
+You can use webhooks to subscribe to events taking place in your project. For example, when an item is edited, {% data variables.product.product_name %} can send a HTTP POST payload to the webhook's configured URL which can trigger automation on your server. For more information about webhooks, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)." To learn more about the `projects_v2_item` webhook event, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#projects_v2_item)."
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
new file mode 100644
index 0000000000..06e7274342
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
@@ -0,0 +1,23 @@
+---
+title: 'Using the built-in automations'
+shortTitle: 'Using built-in automations'
+intro: 'You can use built-in workflows to automate your projects.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+type: tutorial
+topics:
+  - Projects
+---
+
+{% note %}
+
+**Note:** Built-in workflows are available as part of a limited beta.
+
+{% endnote %}
+
+{% data reusables.projects.about-workflows %}
+
+You can enable or disable the built-in workflows for your project.
+
+{% data reusables.projects.enable-basic-workflow %}
diff --git a/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md b/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
new file mode 100644
index 0000000000..e1e5d6f8a0
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
@@ -0,0 +1,39 @@
+---
+title: 'Creating a {% data variables.projects.project_v2 %}'
+intro: 'Learn how to create an organization or user project.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/creating-a-project
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+{% data variables.product.prodname_projects_v2 %} are an adaptable collection of items that stay up-to-date with {% data variables.product.company_short %} data. Your projects can track issues, pull requests, and ideas that you note down. You can add custom fields and create views for specific purposes.
+
+## Creating a project
+
+### Creating an organization project
+
+Organization projects can track issues and pull requests from the organization's repositories.
+
+{% data reusables.projects.create-project %}
+
+### Creating a user project
+
+User projects can track issues and pull requests from the repositories owned by your personal account.
+
+{% data reusables.projects.create-user-project %}
+
+## Updating your project description and README
+
+{% data reusables.projects.project-description %}
+
+## Further reading
+
+- "[Adding your project to a repository](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository)"
+- "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)"
+- "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)"
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/creating-projects/index.md b/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
new file mode 100644
index 0000000000..5d8b5ba9cd
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
@@ -0,0 +1,15 @@
+---
+title: 'Creating {% data variables.projects.projects_v2 %}'
+shortTitle: 'Creating {% data variables.projects.projects_v2 %}'
+intro: 'Learn about creating projects and migrating your {% data variables.projects.projects_v1_boards %}.'
+versions:
+  feature: "projects-v2"
+topics:
+  - Issues
+  - Projects
+children:
+  - /creating-a-project
+  - /migrating-from-projects-classic
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/content/issues/trying-out-the-new-projects-experience/migrating-your-project.md b/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
similarity index 66%
rename from content/issues/trying-out-the-new-projects-experience/migrating-your-project.md
rename to content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
index a2e2c20537..d36dc4a14f 100644
--- a/content/issues/trying-out-the-new-projects-experience/migrating-your-project.md
+++ b/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
@@ -1,23 +1,24 @@
 ---
-title: Migrating your project to Projects (beta)
-intro: You can migrate your projects from the old projects experience to Projects (beta).
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
+title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
+intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
+miniTocMaxHeadingLevel: 3
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/migrating-your-project
+type: tutorial
 topics:
   - Projects
-  - Organizations
+allowTitleToDifferFromFilename: true
 ---
 
+
 {% note %}
 
 **Notes:**
 
-- Projects (beta) is currently in public beta and subject to change.
 - If the project you are migrating contains more than 1200 items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of 10,000 items is reached, additional items will not be migrated.
-- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#showing-and-hiding-fields)."
+- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
 - Automation will not be migrated.
 - Triage, archive, and activity will not be migrated.
 - After migration, the new migrated project and old project will not be kept in sync.
@@ -26,7 +27,7 @@ topics:
 
 ## About project migration
 
-You can migrate your project boards to the all new projects (beta) experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)."
+You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
 
 ## Migrating an organization project board
 
@@ -52,7 +53,7 @@ You can migrate your project boards to the all new projects (beta) experience an
 
 {% note %}
 
-**Note:** Projects (beta) does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
+**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
 
 {% endnote %}
 
@@ -62,4 +63,4 @@ You can migrate your project boards to the all new projects (beta) experience an
 ![Project tab](/assets/images/help/projects/repo-tabs-projects.png)
 1. Click **Projects (classic)**.
   ![Screenshot showing Projects (classic) menu option}](/assets/images/help/issues/projects-classic-org.png)
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.migrate-project-steps %}
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
new file mode 100644
index 0000000000..c052704e53
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
@@ -0,0 +1,114 @@
+---
+title: 'Customizing a view'
+intro: 'Display the information you need by changing the layout, grouping, sorting in your project.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/customizing-your-project-views
+type: tutorial
+topics:
+  - Projects
+---
+
+
+## Changing the project layout
+
+You can view your project as a table or as a board.
+
+{% data reusables.projects.open-view-menu %}
+1. Under "Layout", click either **Table** or **Board**.
+   ![Screenshot showing layout option](/assets/images/help/projects-v2/table-or-board.png)
+
+ 
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Switch layout."
+
+## Showing and hiding fields
+
+You can show or hide a specific field.
+
+{% data reusables.projects.open-view-menu %}
+1. Under "Configuration", click {% octicon "note" aria-label="the note icon" %} and the list of currently shown fields.
+   ![Screenshot showing show and hide fields menu option](/assets/images/help/projects-v2/show-hide-fields-menu-item.png)
+1. Select or deselect the fields you want to show or hide.
+   ![Screenshot showing show and hide fields menu](/assets/images/help/projects-v2/show-hide-fields.png)
+
+You can also hide individual fields in table view.
+
+1. Next to the field you want to hide, click {% octicon "kebab-horizontal" aria-label="the kebab icon" %}.
+   ![Screenshot showing field menu icon](/assets/images/help/projects-v2/modify-field-menu.png)
+1. Click {% octicon "eye-closed" aria-label="the eye closed icon" %} **Hide field**.
+   ![Screenshot showing hide field menu option](/assets/images/help/projects-v2/hide-field-via-menu.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "show", "hide", or the name of the field.
+
+## Reordering fields
+
+In table layout, you can change the order of fields.
+
+1. Click the field header.
+   ![Screenshot showing the field header](/assets/images/help/projects-v2/select-field-header.png)
+2. While continuing to click, drag the field to the required location.
+
+## Reordering rows
+
+In table layout, you can change the order of rows.
+
+1. Click the number at the start of the row.
+   ![Screenshot showing the row number](/assets/images/help/projects-v2/select-row-number.png)
+2. While continuing to click, drag the row to the required location.
+
+## Sorting by field values
+
+In table layout, you can sort items by a field value.
+
+{% note %}
+
+**Note:** When a table is sorted, you cannot manually reorder rows.
+
+{% endnote %}
+
+{% data reusables.projects.open-view-menu %}
+1. Click **Sort**.
+   ![Screenshot showing the sort menu item](/assets/images/help/projects-v2/sort-menu-item.png)
+1. Click the field you want to sort by.
+   ![Screenshot showing the sort menu](/assets/images/help/projects-v2/sort-menu.png)
+2. Optionally, to change the direction of the sort, click {% octicon "sort-desc" aria-label="the sort icon" %}.
+   ![Screenshot showing sort order option](/assets/images/help/projects-v2/sort-order.png)
+3. Optionally, to remove a sort, click {% octicon "x" aria-label="the x icon" %} **No sorting** at the bottom of the list.
+   ![Screenshot showing "no sorting"](/assets/images/help/projects-v2/no-sorting.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Sort by."
+
+## Grouping by field values in table layout
+
+In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`. Similarly, when you add a new item to a group, the new item is populated with the value of the group.
+
+{% note %}
+
+**Note:** You cannot group by title, labels, reviewers, or linked pull requests.
+
+{% endnote %}
+
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**.
+   ![Screenshot showing the group menu item](/assets/images/help/projects-v2/group-menu-item.png)
+1. Click the field you want to group by.
+   ![Screenshot showing the group menu](/assets/images/help/projects-v2/group-menu.png)
+2. Optionally, to disable grouping, click {% octicon "x" aria-label="the x icon" %} **No grouping** at the bottom of the list.
+   ![Screenshot showing "no grouping"](/assets/images/help/projects-v2/no-grouping.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Group by."
+
+## Setting the column field in board layout
+
+In the board layout, you choose any single select or iteration field for your columns. If you drag an item to a new column, the value of that column is applied to the dragged item. For example, if you use the "Status" field for your board columns and then drag an item with a status of `In progress` to the `Done` column, the status of the item will switch to `Done`.
+
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "columns" aria-label="the columns icon" %} **Column field**.
+   ![Screenshot showing the column field item](/assets/images/help/projects-v2/column-field-menu-item.png)
+1. Click the field you want to use.
+   ![Screenshot showing the column field menu](/assets/images/help/projects-v2/column-field-menu.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Column field by."
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
new file mode 100644
index 0000000000..64b3ecd972
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
@@ -0,0 +1,31 @@
+---
+title: 'Filtering {% data variables.projects.projects_v2 %}'
+intro: "Use filters to choose which items appear in your project's views."
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/filtering-projects
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+You can customize views using filters for item metadata, such as assignees and the labels applied to issues, and by the fields in your project. You can combine filters and save them as views. For more information, see "[Customizing your project views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."
+
+To filter a project, click {% octicon "filter" aria-label="The Filter icon" %} and start typing the fields and values you would like to filter for. As you type, possible values will appear. You can also open the project command palette, by pressing {% data variables.projects.command-palette-shortcut %}, and type "Filter by" to choose from the available filters.
+
+Using multiple filters will act as a logical AND filter. For example, `label:bug status:"In progress"` will return items with the `bug` label with the "In progress" status. {% data variables.product.prodname_projects_v2 %} does not currently support logical OR filters across multiple fields.
+
+The same filters are available for charts you create using insights for {% data variables.product.prodname_projects_v2 %}, allowing you to filter the data used to create your charts. For more information, see "[Using insights with projects](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects)."
+
+## Filtering items
+
+Click {% octicon "filter" aria-label="the filter icon" %} at the top of the table to show the "Filter by keyword or by field" bar. Start typing the field name and value that you want to filter by. As you type, possible values will appear.
+
+{% data reusables.projects.projects-filters %}
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Filter by."
+
+In board layout, you can click on item data to filter for items with that value. For example, click on an assignee to show only items for that assignee. To remove the filter, click the item data again.
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
new file mode 100644
index 0000000000..677d2c49a1
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
@@ -0,0 +1,16 @@
+---
+title: 'Customizing views in your {% data variables.projects.project_v2 %}'
+shortTitle: 'Customizing views'
+intro: 'You can create multiple views to look at your project from different angles, deciding which items to show and how to present them.'
+versions:
+  feature: "projects-v2"
+topics:
+  - Issues
+  - Projects
+children:
+  - /customizing-a-view
+  - /filtering-projects
+  - /managing-your-views
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
new file mode 100644
index 0000000000..d6e908bd48
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
@@ -0,0 +1,73 @@
+---
+title: 'Managing your views'
+intro: 'Learn how to create, save, and manage your project views.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+type: tutorial
+topics:
+  - Projects
+---
+
+
+## Creating a project view
+
+Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project. 
+
+For example, you can have:
+- A view that shows all items not yet started (filter on "Status").
+- A view that shows the workload for each team (group by a custom "Team" field).
+- A view that shows the items with the earliest target ship date (sort by a date field).
+
+To add a new view:
+
+{% data reusables.projects.new-view %}
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "New view."
+
+The new view is automatically saved.
+
+## Duplicating a view
+
+You can duplicate an existing view and use it as a base to make further changes.
+
+1. Switch to the view you want to duplicate.
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "versions" aria-label="the versions icon" %} **Duplicate view**.
+   ![Screenshot showing the duplicate menu item](/assets/images/help/projects-v2/duplicate-view.png)
+
+## Saving changes to a view
+
+When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes. 
+
+![Unsaved changes indicator](/assets/images/help/projects/unsaved-changes.png)
+
+If you don't want to save the changes, you can ignore this indicator. No one else will see your changes.
+
+{% data reusables.projects.save-view %}
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Save view."
+
+## Reordering saved views
+
+To change the order of the tabs that contain your saved views, click and drag a tab to a new location. The new tab order is automatically saved.
+
+## Renaming a saved view
+
+You can rename your saved views. The name change is automatically saved.
+
+1. Switch to the view you want to rename.
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "pencil" aria-label="the pencil icon" %} **Rename view**.
+   ![Screenshot showing the rename menu item](/assets/images/help/projects-v2/rename-view.png)
+1. Type the new name for your view.
+1. To save your changes, press <kbd>Return</kbd>.
+
+## Deleting a saved view
+
+1. Switch to the view you want to delete.
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "trash" aria-label="the trasj icon" %} **Delete view**.
+   ![Screenshot showing the rename delete item](/assets/images/help/projects-v2/delete-view.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Delete view."
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/index.md b/content/issues/planning-and-tracking-with-projects/index.md
new file mode 100644
index 0000000000..c4667ce6f0
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/index.md
@@ -0,0 +1,23 @@
+---
+title: 'Planning and tracking with {% data variables.product.prodname_projects_v2 %}'
+shortTitle: '{% data variables.product.prodname_projects_v2 %}'
+intro: 'Build adaptable projects to track your work on {% data variables.product.company_short %}.'
+versions:
+  feature: "projects-v2"
+topics:
+  - Issues
+  - Projects
+children:
+  - /learning-about-projects
+  - /creating-projects
+  - /managing-items-in-your-project
+  - /understanding-field-types
+  - /customizing-views-in-your-project
+  - /automating-your-project
+  - /viewing-insights-from-your-project
+  - /managing-your-project
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience
+---
+
diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
new file mode 100644
index 0000000000..97f909323a
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
@@ -0,0 +1,49 @@
+---
+title: 'About {% data variables.product.prodname_projects_v2 %}'
+intro: '{% data variables.product.prodname_projects_v2 %} is an adaptable, flexible tool for planning and tracking work on {% data variables.product.company_short %}.'
+allowTitleToDifferFromFilename: true
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/about-projects
+type: overview
+topics:
+  - Projects
+---
+
+## About {% data variables.product.prodname_projects_v2 %}
+
+A project is an adaptable spreadsheet that integrates with your issues and pull requests on {% data variables.product.company_short %} to help you plan and track your work effectively. You can create and customize multiple views by filtering, sorting, grouping your issues and pull requests, adding custom fields to track metadata specific to your team, and visualize work with configurable charts. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes.
+
+### Staying up-to-date
+
+Your projects are built from the issues and pull requests you add, creating direct references between your project and your work. Information is synced automatically to your project as you make changes, updating your views and charts. This integration works both ways, so that when you change information about a pull request or issue in your project, the pull request or issue reflects that information. For example, change an assignee in your project and that change is shown in your issue. You can take this integration even further, group your project by assignee, and make changes to issue assignment by dragging issues into the different groups.
+
+### Adding metadata to your tasks
+
+You can use custom fields to add metadata to your tasks and build a richer view of item attributes. You’re not limited to the built-in metadata (assignee, milestone, labels, etc.) that currently exists for issues and pull requests. For example, you can add the following metadata as custom fields:
+
+- A date field to track target ship dates.
+- A number field to track the complexity of a task.
+- A single select field to track whether a task is Low, Medium, or High priority.
+- A text field to add a quick note.
+- An iteration field to plan work week-by-week, including support for breaks.
+
+### Viewing your project from different perspectives
+
+Quickly answer your most pressing questions by tailoring your project view to give you the information you need. You can save these views, allowing you to quickly return to them as needed and make them available to your team. Views not only let you scope down the items listed but also offer two different layout options.
+
+You can view your project as a high density table layout:
+
+![Project table](/assets/images/help/issues/projects_table.png)
+
+Or as a board:
+
+![Project board](/assets/images/help/issues/projects_board.png)
+
+To help you focus on specific aspects of your project, you can group, sort, or filter items:
+
+![Project view](/assets/images/help/issues/project_view.png)
+
+For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."
diff --git a/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
similarity index 63%
rename from content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
rename to content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
index 042b769958..7cb88aab8c 100644
--- a/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
@@ -1,11 +1,12 @@
 ---
-title: Best practices for managing projects (beta)
-intro: 'Learn tips for managing your projects on {% data variables.product.company_short %}.'
+title: 'Best practices for {% data variables.product.prodname_projects_v2 %}'
+intro: 'Learn tips for managing your projects.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects
 type: overview
 topics:
   - Projects
@@ -13,9 +14,7 @@ topics:
   - Project management
 ---
 
-{% data reusables.projects.projects-beta %}
-
-You can use projects to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. Read on for tips to manage your projects efficiently and effectively. For more information about projects, see "[About projects](/issues/trying-out-the-new-projects-experience/about-projects)."
+You can use {% data variables.product.prodname_projects_v2 %} to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. Read on for tips to manage your projects efficiently and effectively. For more information about {% data variables.product.prodname_projects_v2 %}, see "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
 
 ## Break down large issues into smaller issues
 
@@ -39,7 +38,7 @@ For example:
 
 Project READMEs support Markdown which allows you to use images and advanced formatting such as links, lists, and headers. 
 
-For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#updating-your-project-description-and-readme)."
+For more information, see "[Creating a {% data variables.projects.project_v2 %}](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)."
 
 ## Use views
 
@@ -51,32 +50,32 @@ For example:
 - Group by a custom priority field to monitor the volume of high priority items
 - Sort by a custom date field to view the items with the earliest target ship date
 
-For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."
 
 ## Have a single source of truth
 
 To prevent information from getting out of sync, maintain a single source of truth. For example, track a target ship date in a single location instead of spread across multiple fields. Then, if the target ship date shifts, you only need to update the date in one location.
 
-{% data variables.product.company_short %} projects automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. When one of these fields changes in an issue or pull request, the change is automatically reflected in your project.
+{% data variables.product.prodname_projects_v2 %} automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. When one of these fields changes in an issue or pull request, the change is automatically reflected in your project.
 
 ## Use automation
 
 You can automate tasks to spend less time on busy work and more time on the project itself. The less you need to remember to do manually, the more likely your project will stay up to date.
 
-Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done."
+{% data variables.product.prodname_projects_v2 %} offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done."
 
 Additionally, {% data variables.product.prodname_actions %} and the GraphQL API enable you to automate routine project management tasks. For example, to keep track of pull requests awaiting review, you can create a workflow that adds a pull request to a project and sets the status to "needs review"; this process can be automatically triggered when a pull request is marked as "ready for review."
 
-- For an example workflow, see "[Automating projects](/issues/trying-out-the-new-projects-experience/automating-projects)."
-- For more information about the API, see "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
+- For an example workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)."
+- For more information about the API, see "[Using the API to manage {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)."
 - For more information about {% data variables.product.prodname_actions %}, see ["{% data variables.product.prodname_actions %}](/actions)."
 
 ## Use different field types
 
 Take advantage of the various field types to meet your needs.
 
-Use an iteration field to schedule work or create a timeline. You can group by iteration to see if items are balanced between iterations, or you can filter to focus on a single iteration. Iteration fields also let you view work that you completed in past iterations, which can help with velocity planning and reflecting on your team's accomplishments. Iteration fields also support breaks to show when you and your team are taking time away from their iterations. For more information, see "[Managing iterations in projects](/issues/trying-out-the-new-projects-experience/managing-iterations)."
+Use an iteration field to schedule work or create a timeline. You can group by iteration to see if items are balanced between iterations, or you can filter to focus on a single iteration. Iteration fields also let you view work that you completed in past iterations, which can help with velocity planning and reflecting on your team's accomplishments. Iteration fields also support breaks to show when you and your team are taking time away from their iterations. For more information, see "[About iteration fields](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)."
 
 Use a single select field to track information about a task based on a preset list of values. For example, track priority or project phase. Since the values are selected from a preset list, you can easily group or filter to focus on items with a specific value.
 
-For more information about the different field types, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-custom-fields)."
+For more information about the different field types, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)."
diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
new file mode 100644
index 0000000000..1f09f8557b
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
@@ -0,0 +1,15 @@
+---
+title: 'Learning about {% data variables.product.prodname_projects_v2 %}'
+intro: 'Learn about {% data variables.product.prodname_projects_v2 %} and how to make the very best of this powerful tool.'
+versions:
+  feature: "projects-v2"
+topics:
+  - Issues
+  - Projects
+children:
+  - /about-projects
+  - /quickstart-for-projects
+  - /best-practices-for-projects
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
new file mode 100644
index 0000000000..89abba3ca8
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
@@ -0,0 +1,167 @@
+---
+title: 'Quickstart for {% data variables.product.prodname_projects_v2 %}'
+intro: 'Experience the speed, flexibility, and customization of {% data variables.product.prodname_projects_v2 %} by creating a project in this interactive guide.'
+allowTitleToDifferFromFilename: true
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/quickstart
+type: quick_start
+topics:
+  - Projects
+---
+
+## Introduction
+
+This guide demonstrates how to use {% data variables.product.prodname_projects_v2 %} to plan and track work. In this guide, you will create a new project and add a custom field to track priorities for your tasks. You'll also learn how to create saved views that help you communicate priorities and progress with your collaborators.
+
+## Prerequisites
+
+You can either create an organization project or a user project. To create an organization project, you need a {% data variables.product.prodname_dotcom %} organization. For more information about creating an organization, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+
+In this guide, you will add existing issues from repositories owned by your organization (for organization projects) or by you (for user projects) to your new project. For more information about creating issues, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."
+
+## Creating a project
+
+First, create an organization project or a user project.
+
+### Creating an organization project
+
+{% data reusables.projects.create-project %}
+
+### Creating a user project
+
+{% data reusables.projects.create-user-project %}
+
+## Setting your project description and README
+
+{% data reusables.projects.project-description %}
+
+## Adding issues to your project
+
+Next, add a few issues to your project.
+
+{% data reusables.projects.add-item-via-paste %}
+
+Repeat the above steps a few times to add multiple issues to your project.
+
+For more information and other ways to add issues to your project, or about other items you can add to your project, see "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)."
+
+## Adding draft issues to your project
+
+Next, add a draft issue to your project.
+
+{% data reusables.projects.add-draft-issue %}
+
+## Adding an iteration field
+
+Next, create an iteration field so you can plan and track your work over repeating blocks of time. Iterations can be configured to suit how you and your team works, with customizable lengths and the ability to insert breaks.
+
+{% data reusables.projects.new-field %}
+1. Select **Iteration**
+   ![Screenshot showing the iteration option](/assets/images/help/projects-v2/new-field-iteration.png)
+3. To change the duration of each iteration, type a new number, then select the dropdown and click either **days** or **weeks**.
+   ![Screenshot showing the iteration duration](/assets/images/help/projects-v2/iteration-field-duration.png)
+4. Click **Save**.
+   ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save-and-create.png)
+
+## Creating a field to track priority
+
+Now, create a custom field named `Priority` and containing the values: `High`, `Medium`, or `Low`.
+
+{% data reusables.projects.new-field %}
+1. Select **Single select**
+   ![Screenshot showing the single select option](/assets/images/help/projects-v2/new-field-single-select.png)
+1. Below "Options", type the first option, "High".
+   ![Screenshot showing the single select option](/assets/images/help/projects-v2/priority-example.png)
+1. To add additional fields, for "Medium" and "Low", click **Add option**.
+1. Click **Save**.
+   ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png)
+
+Specify a priority for all issues in your project.
+
+![Example priorities](/assets/images/help/projects/priority_example.png)
+
+## Grouping issues by priority
+
+Next, group all of the items in your project by priority to make it easier to focus on the high priority items.
+
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**.
+   ![Screenshot showing the group menu item](/assets/images/help/projects-v2/group-menu-item.png)
+1. Click **Priority**.
+   ![Screenshot showing the group menu](/assets/images/help/projects-v2/group-menu.png)
+
+Now, move issues between groups to change their priority.
+
+1. Choose an issue.
+2. Drag and drop the issue into a different priority group. When you do this, the priority of the issue will change to be the priority of its new group.
+
+![Move issue between groups](/assets/images/help/projects/move_between_group.gif)
+
+## Saving the priority view
+
+When you grouped your issues by priority in the previous step, your project displayed an indicator to show that the view was modified. Save these changes so that your collaborators will also see the tasks grouped by priority.
+
+{% data reusables.projects.save-view %}
+
+You can share the URL with your team to keep everyone aligned on the project priorities.
+
+When a view is saved, anyone who opens the project will see the saved view. Here, you grouped by priority, but you can also add other modifiers such as sort, filter, or layout. Next, you will create a new view with the layout modified.
+
+## Adding a board layout
+
+To view the progress of your project's issues, you can switch to board layout.
+
+The board layout is based on the status field, so specify a status for each issue in your project.
+
+![Example status](/assets/images/help/projects/status_example.png)
+
+Then, create a new view.
+
+{% data reusables.projects.new-view %}
+
+Next, switch to board layout.
+
+{% data reusables.projects.open-view-menu %}
+1. Under "Layout", click **Board**.
+   ![Screenshot showing layout option](/assets/images/help/projects-v2/table-or-board.png)
+
+![Example priorities](/assets/images/help/projects/example_board.png)
+
+When you changed the layout, your project displayed an indicator to show that the view was modified. Save this view so that you and your collaborators can easily access it in the future.
+
+{% data reusables.projects.save-view %}
+
+To indicate the purpose of the view, give it a descriptive name.
+
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "pencil" aria-label="the pencil icon" %} **Rename view**.
+   ![Screenshot showing the rename menu item](/assets/images/help/projects-v2/rename-view.png)
+1. Type the new name for your view.
+1. To save changes, press <kbd>Return</kbd>.
+
+![Example priorities](/assets/images/help/projects/project-view-switch.gif)
+
+## Configure built-in automation
+
+Finally, add a built in workflow to set the status to **Todo** when an item is added to your project.
+
+1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
+  ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png)
+1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**.
+  ![Screenshot showing the 'Workflows' menu item](/assets/images/help/projects-v2/workflows-menu-item.png)
+1. Under **Default workflows**, click **Item added to project**.
+  ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png)
+1. Next to **When**, ensure that both `issues` and `pull requests` are selected.
+  ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png)
+1. Next to **Set**, select **Status:Todo**.
+  ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png)
+1. Click the **Disabled** toggle to enable the workflow.
+  ![Screenshot showing the "enable" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png)
+
+## Further reading
+
+- "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)"
+- "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)"
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
new file mode 100644
index 0000000000..788796e820
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
@@ -0,0 +1,86 @@
+---
+title: 'Adding items to your {% data variables.projects.project_v2 %}'
+shortTitle: 'Adding items'
+intro: 'Learn how to add pull requests, issues, and draft issues to your projects individually or in bulk.'
+miniTocMaxHeadingLevel: 4
+versions:
+  feature: "projects-v2"
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+Your project can track draft issues, issues, and pull requests. 
+
+{% note %}
+
+**Note:** A project can contain a maximum of 1,200 items and 10,000 archived items. 
+
+{% endnote %}
+
+### Adding issues and pull requests to a project
+
+#### Pasting the URL of an issue or pull request
+
+{% data reusables.projects.add-item-via-paste %}
+
+#### Searching for an issue or pull request
+
+{% data reusables.projects.add-item-bottom-row %}
+2. Enter <kbd>#</kbd>.
+3. Select the repository where the pull request or issue is located. You can type part of the repository name to narrow down your options.
+  ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-repo.png)
+4. Select the issue or pull request. You can type part of the title to narrow down your options.
+  ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-issue.png)
+
+#### Bulk adding issues and pull requests
+
+1. In the bottom row of the project, click {% octicon "plus" aria-label="plus icon" %}.
+  ![Screenshot showing + button at the bottom of the project](/assets/images/help/projects-v2/omnibar-add.png)
+1. Click **Add item from repository**.
+  ![Screenshot showing "add item from repository" menu item](/assets/images/help/projects-v2/add-bulk-menu-item.png)
+{% data reusables.projects.bulk-add %}
+
+#### Adding multiple issues or pull requests from a repository
+
+1. On {% data variables.product.product_location %}, navigate to the repository that contains the issues or pull requests you want to add to your project.
+{% data reusables.repositories.sidebar-issue-pr %}
+1. To the left of each issue title, select the issues that you want to add to your project.
+  ![Screenshot showing checkbox to select issue or pull request](/assets/images/help/issues/select-issue-checkbox.png)
+1. Optionally, to select every issue or pull request on the page, at the top of the list of issues or pull requests, select all. 
+  ![Screenshot showing checkbox to select all on screen](/assets/images/help/issues/select-all-checkbox.png)
+1. Above the list of issues or pull requests, click **Projects**. 
+  ![Screenshot showing projects option](/assets/images/help/projects-v2/issue-index-project-menu.png)
+1. Click the projects you want to add the selected issues or pull requests to.
+  ![Screenshot showing checkbox to select all on screen](/assets/images/help/projects-v2/issue-index-select-project.png)
+
+#### Assigning a project from within an issue or pull request
+
+1. Navigate to the issue or pull request that you want to add to a project.
+2. In the side bar, click **Projects**.
+  ![Screenshot showing "Projects" in the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-projects.png)
+3. Select the project that you want to add the issue or pull request to.
+  ![Screenshot showing selecting a project from the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-select-project.png)
+4. Optionally, populate the custom fields.
+  ![Project sidebar](/assets/images/help/projects-v2/issue-edit-project-sidebar.png)
+
+#### Using the command palette to add an issue or pull request
+
+1. {% data reusables.projects.open-command-palette %}
+1. Start typing "Add items" and press <kbd>Return</kbd>.
+{% data reusables.projects.bulk-add %}
+
+### Creating draft issues
+
+Draft issues are useful to quickly capture ideas. Unlike issues and pull requests that are referenced from your repositories, draft issues exist only in your project.
+
+{% data reusables.projects.add-draft-issue %}
+
+Draft issues can have a title, text body, assignees, and any custom fields from your project. In order to populate the repository, labels, or milestones for a draft issue, you must first convert the draft issue to an issue. For more information, see "[Converting draft issues to issues](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues)."
+
+{% note %}
+
+**Note**: Users will not receive notifications when they are assigned to or mentioned in a draft issue unless the draft issue is converted to an issue.
+
+{% endnote %}
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
new file mode 100644
index 0000000000..10811dd4a7
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
@@ -0,0 +1,48 @@
+---
+title: 'Archiving items from your {% data variables.projects.project_v2 %}'
+shortTitle: 'Archiving items'
+intro: 'You can archive items, keeping them available to restore, or permanently delete them.'
+miniTocMaxHeadingLevel: 2
+versions:
+  feature: "projects-v2"
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+## Archiving items
+
+You can archive an item to keep the context about the item in the project but remove it from the project views. 
+
+{% data reusables.projects.select-an-item %}
+{% data reusables.projects.open-item-menu %}
+1. Click **Archive**.
+   ![Screenshot showing archive option](/assets/images/help/projects-v2/archive-menu-item.png)
+1. When prompted, confirm your choice by clicking **Archive**.
+   ![Screenshot showing archive prompt](/assets/images/help/projects-v2/archive-item-prompt.png)
+
+## Restoring archived items
+
+1. Navigate to your project.
+1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
+  ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png)
+1. In the menu, click {% octicon "archive" aria-label="The archive icon" %} **Archived items**.
+  ![Screenshot showing the 'Archived items' menu item](/assets/images/help/projects-v2/archived-items-menu-item.png)
+1. Optionally, to filter the archived items displayed, type your filter into the text box above the list of items. For more information about the available filters, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
+   ![Screenshot showing field for filtering archived items](/assets/images/help/issues/filter-archived-items.png)   
+1. To the left of each item title, select the items you would like to restore.
+   ![Screenshot showing checkboxes next to archived items](/assets/images/help/issues/select-archived-item.png)   
+1. To restore the selected items, above the list of items, click **Restore**. 
+   ![Screenshot showing the "Restore" button](/assets/images/help/issues/restore-archived-item-button.png)
+
+## Deleting items
+
+You can delete an item to remove it from the project entirely.
+
+{% data reusables.projects.select-an-item %}
+{% data reusables.projects.open-item-menu %}
+1. Click **Delete from project**.
+   ![Screenshot showing delete option](/assets/images/help/projects-v2/delete-menu-item.png)
+1. When prompted, confirm your choice by clicking **Delete**.
+   ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png)
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
new file mode 100644
index 0000000000..189913d052
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
@@ -0,0 +1,33 @@
+---
+title: 'Converting draft issues to issues'
+shortTitle: 'Converting draft issues'
+intro: 'Learn how to convert draft issues into issues.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+type: tutorial
+topics:
+  - Projects
+---
+
+## Converting draft issues in table layout
+
+1. Click the {% octicon "triangle-down" aria-label="the item menu" %} on the draft issue that you want to convert.
+  ![Screenshot showing item menu button](/assets/images/help/projects-v2/item-context-menu-button-table.png)
+2. Select **Convert to issue**.
+  ![Screenshot showing "Convert to issue" option](/assets/images/help/projects-v2/item-convert-to-issue.png)
+3. Select the repository that you want to add the issue to.
+  ![Screenshot showing repository selection](/assets/images/help/projects-v2/convert-to-issue-select-repo.png)
+
+## Converting draft issues in board layout
+
+1. Click the {% octicon "kebab-horizontal" aria-label="the item menu" %} on the draft issue that you want to convert.
+  ![Screenshot showing item menu button](/assets/images/help/projects-v2/item-context-menu-button-board.png)
+2. Select **Convert to issue**.
+  ![Screenshot showing "Convert to issue" option](/assets/images/help/projects-v2/item-convert-to-issue.png)
+3. Select the repository that you want to add the issue to.
+  ![Screenshot showing repository selection](/assets/images/help/projects-v2/convert-to-issue-select-repo.png)
+
+## Further reading
+
+- "[Creating draft issues](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project#creating-draft-issues)"
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
new file mode 100644
index 0000000000..1269334f9f
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
@@ -0,0 +1,16 @@
+---
+title: 'Managing items in your {% data variables.projects.project_v2 %}'
+shortTitle: 'Managing items in your {% data variables.projects.project_v2 %}'
+intro: 'Learn how to add and manage issues, pull requests, and draft issues.'
+versions:
+  feature: "projects-v2"
+topics:
+  - Issues
+  - Projects
+children:
+  - /adding-items-to-your-project
+  - /converting-draft-issues-to-issues
+  - /archiving-items-from-your-project
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
new file mode 100644
index 0000000000..5627189643
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
@@ -0,0 +1,26 @@
+---
+title: 'Adding your {% data variables.projects.project_v2 %} to a repository'
+shortTitle: 'Adding a {% data variables.projects.project_v2 %} to a repo'
+intro: 'You can add your {% data variables.projects.project_v2 %} to a repository to make it accessible from that repository.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+You can list relevant projects in a repository. You can only list projects that are owned by the same user or organization that owns the repository.
+
+In order for repository members to see a project listed in a repository, they must have visibility for the project. For more information, see "[Managing visibility of your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)" and "[Managing access to your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)."
+
+1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository.
+1. Click {% octicon "table" aria-label="the project icon" %} **Projects**.
+   ![Screenshot showing projects tab in a repository](/assets/images/help/projects-v2/repo-tab.png)
+1. Click **Add project**.
+   ![Screenshot showing "Add project" button](/assets/images/help/projects-v2/add-to-repo-button.png)
+1. In the search bar that appears, search for projects that are owned by the same user or organization that owns the repository.
+   ![Screenshot showing searching for a project](/assets/images/help/projects-v2/add-to-repo-search.png)
+1. Click on a project to list it in your repository.
+   ![Screenshot showing "Add project" button](/assets/images/help/projects-v2/add-to-repo.png)
\ No newline at end of file
diff --git a/content/issues/trying-out-the-new-projects-experience/managing-projects.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
similarity index 76%
rename from content/issues/trying-out-the-new-projects-experience/managing-projects.md
rename to content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
index 6389ae9f65..607acea24b 100644
--- a/content/issues/trying-out-the-new-projects-experience/managing-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
@@ -1,16 +1,19 @@
 ---
-title: Managing projects (beta)
-intro: 'You can close and re-open projects, or you can permanently delete projects.'
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
+title: 'Closing and deleting your {% data variables.projects.projects_v2 %}'
+shortTitle: 'Closing and deleting {% data variables.projects.projects_v2 %}'
+intro: 'Learn about closing, re-opening, and permanently deleting a {% data variables.projects.project_v2 %}.'
+miniTocMaxHeadingLevel: 3
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-projects
+type: tutorial
 topics:
   - Projects
-  - Organizations
+allowTitleToDifferFromFilename: true
 ---
 
+
 ## Deleting a project
 
 You can delete a project to permanently remove it.
diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
new file mode 100644
index 0000000000..7d3f535971
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
@@ -0,0 +1,15 @@
+---
+title: 'Managing your {% data variables.projects.project_v2 %}'
+intro: 'Learn how to manage your projects and control visibility and access.'
+versions:
+  feature: "projects-v2"
+topics:
+  - Issues
+  - Projects
+children:
+  - /managing-visibility-of-your-projects
+  - /managing-access-to-your-projects
+  - /closing-and-deleting-your-projects
+  - /adding-your-project-to-a-repository
+allowTitleToDifferFromFilename: true
+---
diff --git a/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
similarity index 64%
rename from content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
rename to content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
index c0e785f37e..275399fd5e 100644
--- a/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
@@ -1,17 +1,18 @@
 ---
-title: Managing access to projects (beta)
-intro: 'You can control who can view, edit, or manage your projects.'
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
+title: 'Managing access to your {% data variables.projects.projects_v2 %}'
+shortTitle: 'Managing {% data variables.projects.project_v2 %} access'
+intro: 'Learn how to manage team and individual access to your {% data variables.projects.project_v2 %}.'
+miniTocMaxHeadingLevel: 3
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-access-to-projects
+type: tutorial
 topics:
   - Projects
-  - Organizations
+allowTitleToDifferFromFilename: true
 ---
 
-{% data reusables.projects.projects-beta %}
 
 ## About project access
 
@@ -29,7 +30,9 @@ The default base role is `write`, meaning that everyone in the organization can
 
 {% data reusables.projects.project-settings %}
 1. Click **Manage access**.
+   ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png)
 2. Under **Base role**, select the default role.
+   ![Screenshot showing the base role menu](/assets/images/help/projects-v2/base-role.png)
    - **No access**: Only organization owners and users granted individual access can see the project. Organization owners are also admins for the project.
    - **Read**: Everyone in the organization can see the project. Organization owners are also admins for the project.
    - **Write**: Everyone in the organization can see and edit the project. Organization owners are also admins for the project.
@@ -43,22 +46,31 @@ You can only invite an individual user to collaborate on your organization-level
 
 {% data reusables.projects.project-settings %}
 1. Click **Manage access**.
+   ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png)
 2. Under **Invite collaborators**, search for the team or individual user that you want to invite.
+   ![Screenshot showing searching for a collaborator](/assets/images/help/projects-v2/access-search.png)
 3. Select the role for the collaborator.
+   ![Screenshot showing selecting a role](/assets/images/help/projects-v2/access-role.png)
    - **Read**: The team or individual can view the project.
    - **Write**: The team or individual can view and edit the project.
    - **Admin**: The team or individual can view, edit, and add new collaborators to the project.
 4. Click **Invite**.
+   ![Screenshot showing the invite button](/assets/images/help/projects-v2/access-invite.png)
 
 ### Managing access of an existing collaborator on your project
 
 {% data reusables.projects.project-settings %}
 1. Click **Manage access**.
+   ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png)
 1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
 
    You can use the **Type** and **Role** drop-down menus to filter the access list.
+   ![Screenshot showing a collaborator](/assets/images/help/projects-v2/access-find-member.png)
 
-1. Edit the role for the collaborator(s) or click {% octicon "trash" aria-label="the trash icon" %} to remove the collaborator(s).
+1. Edit the role for the collaborator(s).
+   ![Screenshot showing changing a collaborator's role](/assets/images/help/projects-v2/access-change-role.png)
+1. Optionally, click **Remove** to remove the collaborator(s).
+   ![Screenshot showing removing a collaborator](/assets/images/help/projects-v2/access-remove-member.png)
 
 ## Managing access for user-level projects
 
@@ -72,19 +84,28 @@ This only affects collaborators for your project, not for repositories in your p
 
 {% data reusables.projects.project-settings %}
 1. Click **Manage access**.
+   ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png)
 2. Under **Invite collaborators**, search for the user that you want to invite.
+   ![Screenshot showing searching for a collaborator](/assets/images/help/projects-v2/access-search.png)
 3. Select the role for the collaborator.
+   ![Screenshot showing selecting a role](/assets/images/help/projects-v2/access-role.png)
    - **Read**: The individual can view the project.
    - **Write**: The individual can view and edit the project.
    - **Admin**: The individual can view, edit, and add new collaborators to the project.
 4. Click **Invite**.
+   ![Screenshot showing the invite button](/assets/images/help/projects-v2/access-invite.png)
 
 ### Managing access of an existing collaborator on your project
 
 {% data reusables.projects.project-settings %}
 1. Click **Manage access**.
+   ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png)
 1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
 
-   You can use the **Role** drop-down menu to filter the access list.
+   You can use the **Type** and **Role** drop-down menus to filter the access list.
+   ![Screenshot showing a collaborator](/assets/images/help/projects-v2/access-find-member.png)
 
-1. Edit the role for the collaborator(s) or click {% octicon "trash" aria-label="the trash icon" %} to remove the collaborator(s).
+1. Edit the role for the collaborator(s).
+   ![Screenshot showing changing a collaborator's role](/assets/images/help/projects-v2/access-change-role.png)
+1. Optionally, click **Remove** to remove the collaborator(s).
+   ![Screenshot showing removing a collaborator](/assets/images/help/projects-v2/access-remove-member.png)
diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
new file mode 100644
index 0000000000..5d8c6bd7ab
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
@@ -0,0 +1,41 @@
+---
+title: 'Managing visibility of your {% data variables.projects.projects_v2 %}'
+shortTitle: 'Managing {% data variables.projects.project_v2 %} visibility'
+intro: 'Learn about setting your {% data variables.projects.project_v2 %} to private or public visibility.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+permissions: 'Organization owners can manage the visibility of project boards in their organization. Organization owners can also allow collaborators with admin permissions to manage project visibility. Visibility of user projects can be managed by the owner of the project and collaborators with admin permissions.'
+---
+
+## About project visibility
+
+Projects can be public or private. For public projects, everyone on the internet can view the project. For private projects, only users granted at least read access can see the project.
+
+Only the project visibility is affected; to view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository.
+
+![Project with hidden item](/assets/images/help/projects/hidden-items.png)
+
+Project admins and organization owners can control project visibility. Organization owners can restrict the ability to change project visibility to just organization owners.
+
+In public and private projects, insights are only visible to users with write permissions for the project.
+
+In private, organization-owned projects, the avatars of users who are current making updates to the project are displayed in the project UI.
+
+Project admins can also manage write and admin access to their project and control read access for individual users. For more information, see "[Managing access to your projects](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)."
+
+## Changing project visibility
+
+{% data reusables.projects.project-settings %}
+1. Next to **Visibility** in the "Danger zone", select **Private** or **Public**.
+   ![Screenshot showing the visibility controls](/assets/images/help/projects-v2/visibility.png)
+
+## Further reading
+
+- [Allowing project visibility changes in your organization](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md
new file mode 100644
index 0000000000..8c5304297d
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md
@@ -0,0 +1,23 @@
+---
+title: 'About date fields'
+shortTitle: 'About date fields'
+intro: 'You can create custom date fields that can be set by typing a date or using a calendar.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+type: tutorial
+topics:
+  - Projects
+---
+
+You can filter for date values using the `YYYY-MM-DD` format, for example: `date:2022-07-01`. You can also use operators, such as `>`, `>=`, `<`, `<=`, and `..`. For example, `date:>2022-07-01` and `date:2022-07-01..2022-07-31`. You can also provide `@today` to represent the current day in your filter. For more information, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
+
+## Adding a date field
+
+{% data reusables.projects.new-field %}
+1. Select **Date**
+   ![Screenshot showing the date option](/assets/images/help/projects-v2/new-field-date.png)
+1. Click **Save**.
+   ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md
new file mode 100644
index 0000000000..5d9587881c
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md
@@ -0,0 +1,76 @@
+---
+title: 'About iteration fields'
+shortTitle: 'About iteration fields'
+intro: 'You can create iterations to plan upcoming work and group items.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-iterations
+type: tutorial
+topics:
+  - Projects
+---
+
+You can create an iteration field to associate items with specific repeating blocks of time. Iterations can be set to any length of time, can include breaks, and can be individually edited to modify name and date range. With projects, you can group by iteration to visualize the balance of upcoming work, use filters to focus on a single iteration, and sort by iteration.
+
+You can filter for iterations by specifying the iteration name or `@current` for the current iteration, `@previous` for the previous iteration, or `@next` for the next iteration. You can also use operators such as `>`, `>=`, `<`, `<=`, and `..`.  For example, `iteration:>"Iteration 4"` and `iteration:<@current`. For more information, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
+
+When you first create an iteration field, three iterations are automatically created.  You can add additional iterations and make other changes on your project's settings page.
+
+![Screenshot showing the settings for an iteration field](/assets/images/help/issues/iterations-example.png)
+
+## Adding an iteration field
+
+{% data reusables.projects.new-field %}
+1. Select **Iteration**
+   ![Screenshot showing the iteration option](/assets/images/help/projects-v2/new-field-iteration.png)
+2. Optionally, if you don't want the iteration to start today, select the calendar dropdown next to "Starts on" and choose a new start date.
+   ![Screenshot showing the iteration start date](/assets/images/help/projects-v2/iteration-field-starts.png)
+3. To change the duration of each iteration, type a new number, then select the dropdown and click either **days** or **weeks**.
+   ![Screenshot showing the iteration duration](/assets/images/help/projects-v2/iteration-field-duration.png)
+4. Click **Save**.
+   ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save-and-create.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
+
+## Adding new iterations
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the iteration field you want to adjust.
+   ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png)
+1. To add a new iteration of the same duration, click **Add iteration**.
+   ![Screenshot the "add iteration" button](/assets/images/help/projects-v2/add-iteration.png)
+1. Optionally, to customize the duration of the new iteration and when it will start, click {% octicon "triangle-down" aria-label="The triangle icon" %} **More options**, select a starting date and duration, and click **Add**.
+   ![Screenshot the add iteration options form](/assets/images/help/projects-v2/add-iteration-options.png)
+1. Click **Save changes**.
+   ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png)
+
+## Editing an iteration
+
+You can edit iterations in your project settings. You can also access the settings for an iteration field by clicking {% octicon "triangle-down" aria-label="The triangle icon" %} in the table header for the field and clicking **Edit values**.
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the iteration field you want to adjust.
+   ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png)
+1. To change the name of an iteration, click on the name and start typing.
+   ![Screenshot an title field to rename an iteration](/assets/images/help/projects-v2/iteration-rename.png)
+1. To change the date or duration of an iteration, click on the date to open the calendar. Click on the start day, then click the end day, and then click **Apply**.
+   ![Screenshot showing iteration dates](/assets/images/help/projects-v2/iteration-date.png)
+1. Optionally, to delete an iteration, click {% octicon "trash" aria-label="The trash icon" %}.
+   ![Screenshot the delete button](/assets/images/help/projects-v2/iteration-delete.png)
+2. Click **Save changes**.
+   ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png)
+
+## Inserting a break
+
+You can insert breaks into your iterations to communicate when you are taking time away from scheduled work. The duration of a new break defaults to the length of the most recently created iteration.
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the iteration field you want to adjust.
+   ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png)
+2. On the dividing line above an iteration and to the right, click **Insert break**.
+   ![Screenshot showing location of "Insert break" button](/assets/images/help/issues/iteration-insert-break.png)
+3. Optionally, to change the duration of the break, click on the date to open the calendar. Click on the start day, then click the end day, and then click **Apply**.
+4. Click **Save changes**.
+   ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png)
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md
new file mode 100644
index 0000000000..b5e1d38cdc
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md
@@ -0,0 +1,40 @@
+---
+title: 'About single select fields'
+shortTitle: 'About single select fields'
+intro: 'You can create single select fields with defined options that can be selected from a dropdown menu.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+type: tutorial
+topics:
+  - Projects
+---
+
+You can filter by your single select fields by specifying the option, for example: `fieldname:option`. You can filter for multiple values by providing a comma-separated list of options, for example: `fieldname:option,option`. For more information, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
+
+Single select fields can contain up to 50 options. 
+
+## Adding a single select field
+
+{% data reusables.projects.new-field %}
+1. Select **Single select**
+   ![Screenshot showing the single select option](/assets/images/help/projects-v2/new-field-single-select.png)
+1. Below "Options", type the first option.
+   ![Screenshot showing the single select option](/assets/images/help/projects-v2/single-select-create-with-options.png)
+   - To add additional options, click **Add option**.
+1. Click **Save**.
+   ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
+
+## Editing a single select field
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the single select field you want to adjust.
+   ![Screenshot showing an single select field](/assets/images/help/projects-v2/select-single-select.png)
+1. Edit existing options or click **Add option**.
+   ![Screenshot showing single select options](/assets/images/help/projects-v2/single-select-edit-options.png)
+1. Optionally, to delete an option, click {% octicon "x" aria-label="The x icon" %}.
+   ![Screenshot showing delete button](/assets/images/help/projects-v2/single-select-delete.png)
+1. Click **Save options**.
+   ![Screenshot showing save button](/assets/images/help/projects-v2/save-options.png)
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md
new file mode 100644
index 0000000000..e2374912d7
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md
@@ -0,0 +1,37 @@
+---
+title: 'About text and number fields'
+shortTitle: 'About text and number fields'
+intro: 'You can add custom text and number fields to your project.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+type: tutorial
+topics:
+  - Projects
+---
+
+You can use text fields to include notes or any other freeform text in your project.
+
+Text fields can be used in filters, for example: `field:"exact text"`. Text fields and item titles will also be used if you filter for text without specifying a field. 
+
+Number fields can also be used in filters. You can use `>`, `>=`, `<`, `<=`, and `..` range queries to filter by a number field. For example: `field:5..15` or `field:>=20`. For more information, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
+
+## Adding a text field
+
+{% data reusables.projects.new-field %}
+1. Select **Text**
+   ![Screenshot showing the text option](/assets/images/help/projects-v2/new-field-text.png)
+1. Click **Save**.
+   ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
+
+## Adding a number field
+
+{% data reusables.projects.new-field %}
+1. Select **Number**
+   ![Screenshot showing the number option](/assets/images/help/projects-v2/new-field-number.png)
+1. Click **Save**.
+   ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md
new file mode 100644
index 0000000000..db07ef00e0
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md
@@ -0,0 +1,18 @@
+---
+title: 'Deleting fields'
+intro: 'Learn how to delete a field from your {% data variables.projects.project_v2 %}.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+type: tutorial
+topics:
+  - Projects
+---
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the field you want to delete.
+   ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-single-select.png)
+1. Next to the field's name, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
+   ![Screenshot showing field name](/assets/images/help/projects-v2/field-options.png)
+1. Click **Delete field**.
+   ![Screenshot showing field name](/assets/images/help/projects-v2/delete-field.png)
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md
new file mode 100644
index 0000000000..a36c492147
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md
@@ -0,0 +1,19 @@
+---
+title: 'Understanding field types'
+shortTitle: 'Understanding field types'
+intro: 'Learn about the different custom field types, how to add custom fields to your project, and how to manage custom fields.'
+versions:
+  feature: "projects-v2"
+topics:
+  - Issues
+  - Projects
+children:
+  - /about-text-and-number-fields
+  - /about-date-fields
+  - /about-single-select-fields
+  - /about-iteration-fields
+  - /renaming-fields
+  - /deleting-fields
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md
new file mode 100644
index 0000000000..e5d9dcee5e
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md
@@ -0,0 +1,17 @@
+---
+title: 'Renaming fields'
+intro: 'Learn about renaming existing fields in your {% data variables.projects.project_v2 %}.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+type: tutorial
+topics:
+  - Projects
+---
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the field you want to rename.
+   ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-single-select.png)
+1. Under "Field name", type the new name for the field.
+   ![Screenshot showing field name](/assets/images/help/projects-v2/field-rename.png)
+1. To save changes, press <kbd>Return</kbd>.
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
new file mode 100644
index 0000000000..eb6a3aa961
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
@@ -0,0 +1,51 @@
+---
+title: 'About insights for {% data variables.product.prodname_projects_v2 %}'
+intro: "You can view and customize charts that are built from your project's data."
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/using-insights-with-projects
+type: tutorial
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+{% ifversion fpt %}
+
+{% note %}
+
+**Note:** Historical charts are currently available as a feature preview for organizations using {% data variables.product.prodname_team %} and are generally available for organizations using {% data variables.product.prodname_ghe_cloud %}.
+
+{% endnote %}
+
+{% endif %}
+
+ You can use insights for {% data variables.product.prodname_projects_v2 %} to view, create, and customize charts that use the items added to your project as their source data. You can apply filters to the default chart and also create your own charts. When you create a chart, you set the filters, chart type, the information displayed, and the chart is available to anyone that can view the project. You can generate two types of chart: current charts and historical charts.
+
+ ### About current charts
+
+You can create current charts to visualize your project items. For example, you can create charts to show how many items are assigned to each individual, or how many issues are assigned to each upcoming iteration.
+
+You can also use filters to manipulate the data used to build your chart. For example, you can create a chart showing how much upcoming work you have, but limit those results to particular labels or assignees. For more information, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
+
+ ![Screenshot showing an stacked column chart showing item types for each iteration](/assets/images/help/issues/column-chart-example.png)
+
+For more information, see "[Creating charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)."
+
+ ### About historical charts
+
+ Historical charts are time-based charts that allow you to view your project's trends and progress. You can view the number of items, grouped by status and other fields, over time.
+ 
+ The default "Burn up" chart shows item status over time, allowing you to visualize progress and spot patterns over time. 
+
+![Screenshot showing an example of the default burn up chart for the current iteration](/assets/images/help/issues/burnup-example.png)
+
+ To create a historical chart, set your chart's X-axis to "Time." For more information, see "[Creating charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)" and "[Configuring charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts)."
+
+## Further reading
+
+- "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)"
+- "[Disabling insights for {% data variables.product.prodname_projects_v2 %} in your organization](/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization)"
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
new file mode 100644
index 0000000000..4a629ecca5
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
@@ -0,0 +1,37 @@
+---
+title: 'Configuring charts'
+intro: 'Learn how to configure your charts and filter data from your project.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+type: tutorial
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+---
+
+{% ifversion fpt %}
+
+{% note %}
+
+**Note:** Historical charts are currently available as a feature preview.
+
+{% endnote %}
+
+{% endif %}
+
+{% data reusables.projects.access-insights %}
+1. In the menu on the left, click on the chart you would like to configure.
+   ![Screenshot showing selecting a custom chart](/assets/images/help/projects-v2/insights-select-a-chart.png)
+1. On the right side of the page, click **Configure**. A panel will open on the right.
+   ![Screenshot showing the configure button](/assets/images/help/projects-v2/insights-configure.png)
+1. To change the type of chart, select the **Layout** dropdown and click on the chart type you want to use.
+   ![Screenshot showing selecting a chart layout](/assets/images/help/projects-v2/insights-layout.png)
+1. To change the field used for your chart's X-axis, select the **X-axis** dropdown and click the field you want to use.
+   ![Screenshot showing selecting what to display on the x axis](/assets/images/help/projects-v2/insights-x-axis.png)
+1. Optionally, to group the items on your X-axis by another field, select **Group by** and click on the field you want to use, or click "None" to disable grouping.
+   ![Screenshot showing selecting a grouping method](/assets/images/help/projects-v2/insights-group.png)
+1. Optionally, if your project contains number fields and you want the Y-axis to display the sum, average, minimum, or maximum of one of those number fields, select **Y-axis** and click an option. Then, select the dropdown that appears beneath and click on the number field you want to use. 
+   ![Screenshot showing selecting what to display on the y axis](/assets/images/help/projects-v2/insights-y-axis.png)
+1. To save your chart, click **Save changes**.
+   ![Screenshot showing the save button](/assets/images/help/projects-v2/insights-save.png)
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
new file mode 100644
index 0000000000..e07534f9f2
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
@@ -0,0 +1,20 @@
+---
+title: 'Creating charts'
+intro: 'Learn how to create new charts to save your configurations.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: "projects-v2"
+type: tutorial
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+---
+
+{% data reusables.projects.access-insights %}
+3. In the menu on the left, click **New chart**.
+   ![Screenshot showing the new chart button](/assets/images/help/projects-v2/insights-new-chart.png)
+4. Optionally, to change the name of the new chart, click {% octicon "triangle-down" aria-label="The triangle icon" %}, type a new name, and press <kbd>Return</kbd>.
+   ![Screenshot showing how to rename a chart](/assets/images/help/projects-v2/insights-rename.png)
+5. Above the chart, type filters to change the data used to build the chart. For more information, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
+6. To the right of the filter text box, click **Save changes**.
+   ![Screenshot showing save button](/assets/images/help/projects-v2/insights-save-filter.png)
\ No newline at end of file
diff --git a/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md
new file mode 100644
index 0000000000..3502718aa5
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md
@@ -0,0 +1,16 @@
+---
+title: 'Viewing insights from your {% data variables.projects.project_v2 %}'
+shortTitle: 'Viewing insights'
+intro: '...'
+versions:
+  feature: "projects-v2"
+topics:
+  - Issues
+  - Projects
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+children:
+  - /about-insights-for-projects
+  - /creating-charts
+  - /configuring-charts
+allowTitleToDifferFromFilename: true
+---
diff --git a/content/issues/tracking-your-work-with-issues/about-issues.md b/content/issues/tracking-your-work-with-issues/about-issues.md
index c54499f21a..7464e07f11 100644
--- a/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -31,7 +31,7 @@ Issues can be created in a variety of ways, so you can choose the most convenien
 
 You can organize and prioritize issues with projects. {% ifversion fpt or ghec %}To track issues as part of a larger issue, you can use task lists.{% endif %} To categorize related issues, you can use labels and milestones.
 
-For more information about projects, see {% ifversion fpt or ghec %}"[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" and {% endif %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)." {% ifversion fpt or ghec %}For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %}For more information about labels and milestones, see "[Using labels and milestones to track work](/issues/using-labels-and-milestones-to-track-work)."
+For more information about projects, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." {% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} {% ifversion fpt or ghec %}For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %}For more information about labels and milestones, see "[Using labels and milestones to track work](/issues/using-labels-and-milestones-to-track-work)."
 
 ## Stay up to date
 
diff --git a/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md b/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
index a25ffa5e3e..c436e96ae1 100644
--- a/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
+++ b/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
@@ -89,24 +89,32 @@ Once you have created a label in a repository, you can apply it on any issue, pu
 Below is an example of a `front-end` label that we created and added to the issue.
 
 ![Adding a label to an issue example](/assets/images/help/issues/quickstart-add-label-to-issue.png)
+
 ## Adding issues to a project board
-{% ifversion fpt or ghec %}You can use projects on {% data variables.product.prodname_dotcom %}, currently in limited public beta, to plan and track the work for your team. A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.prodname_dotcom %}, automatically staying up-to-date with the information on {% data variables.product.prodname_dotcom %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. To get started with projects, see "[Quickstart for projects (beta)](/issues/trying-out-the-new-projects-experience/quickstart)."
-### Project (beta) example
+
+{% ifversion projects-v2 %}
+
+You can use {% data variables.projects.projects_v2 %} on {% data variables.product.prodname_dotcom %} to plan and track the work for your team. A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.prodname_dotcom %}, automatically staying up-to-date with the information on {% data variables.product.prodname_dotcom %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. To get started with projects, see "[Quickstart for projects](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects)."
+### Project example
 Here is the table layout of an example project, populated with the Project Octocat issues we have created.
 
-![Projects (beta) table layout example](/assets/images/help/issues/quickstart-projects-table-view.png)
+![Projects table layout example](/assets/images/help/issues/quickstart-projects-table-view.png)
 
 We can also view the same project as a board.
 
-![Projects (beta) board layout example](/assets/images/help/issues/quickstart-projects-board-view.png)
+![Projects board layout example](/assets/images/help/issues/quickstart-projects-board-view.png)
 
 {% endif %}
+{% ifversion projects-v1 %}
 
-You can {% ifversion fpt or ghec %} also use the existing{% else %} use{% endif %} project boards on {% data variables.product.prodname_dotcom %} to plan and track your or your team's work. Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can create project boards for feature work, high-level roadmaps, or even release checklists. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
+You can {% ifversion projects-v2 %} also use the existing{% else %} use{% endif %} {% data variables.product.prodname_projects_v1 %} on {% data variables.product.prodname_dotcom %} to plan and track your or your team's work. Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can create project boards for feature work, high-level roadmaps, or even release checklists. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
 ### Project board example
 Below is a project board for our example Project Octocat with the issue we created, and the smaller issues we broke it down into, added to it.
 
 ![Project board example](/assets/images/help/issues/quickstart-project-board.png)
+
+{% endif %}
+
 ## Next steps
 
 You have now learned about the tools {% data variables.product.prodname_dotcom %} offers for planning and tracking your work, and made a start in setting up your cross-functional team or project repository! Here are some helpful resources for further customizing your repository and organizing your work.
@@ -116,6 +124,6 @@ You have now learned about the tools {% data variables.product.prodname_dotcom %
 - "[About issues and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)" for learning more about issue templates
 - "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)" for learning how to create, edit and delete labels
 - "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)" for learning more about task lists
-{% ifversion fpt or ghec %} - "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" for learning more about the new projects experience, currently in limited public beta 
-- "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)" for learning how to customize views for projects, currently in limited public beta{% endif %}
-- "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" for learning how to manage project boards
+{% ifversion projects-v2 %} - "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" for learning more about projects
+- "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)" for learning how to customize views for projects{% endif %}
+{% ifversion projects-v1 %}- "[About {% data variables.product.prodname_projects_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" for learning how to manage project boards{% endif %}
diff --git a/content/issues/tracking-your-work-with-issues/quickstart.md b/content/issues/tracking-your-work-with-issues/quickstart.md
index 06fb0055f4..eebf0af0c7 100644
--- a/content/issues/tracking-your-work-with-issues/quickstart.md
+++ b/content/issues/tracking-your-work-with-issues/quickstart.md
@@ -71,7 +71,7 @@ To communicate responsibility, you can assign the issue to a member of your orga
 
 ## Adding the issue to a project
 
-You can add the issue to an existing project. {% ifversion fpt or ghec %}If you are using projects (beta), you can also populate metadata for the project. {% endif %} For more information about projects, see {% ifversion fpt or ghec %}"[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" and {% endif %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)".
+You can add the issue to an existing project{% ifversion projects-v2 %} and populate metadata for the project. {% endif %} For more information about projects, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."{% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %}
 
 ![issue with projects](/assets/images/help/issues/issue-project.png)
 
@@ -97,5 +97,5 @@ You can use issues for a wide range of purposes. For example:
 Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_issues %}:
 
 - To learn more about issues, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)."
-- To learn more about how projects can help you with planning and tracking, see {% ifversion fpt or ghec %}"[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" or {% endif %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)".
+- To learn more about how projects can help you with planning and tracking, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."{% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %}
 - To learn more about using issue templates{% ifversion fpt or ghec %} and issue forms{% endif %} to encourage contributors to provide specific information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
diff --git a/content/issues/trying-out-the-new-projects-experience/about-projects.md b/content/issues/trying-out-the-new-projects-experience/about-projects.md
deleted file mode 100644
index 36a8818678..0000000000
--- a/content/issues/trying-out-the-new-projects-experience/about-projects.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: About projects (beta)
-intro: 'Projects are a customizable, flexible tool for planning and tracking work on {% data variables.product.company_short %}.'
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-type: overview
-topics:
-  - Projects
----
-
-{% data reusables.projects.projects-beta %}
-
-## About projects
-
-A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.company_short %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. You can also add custom fields to track metadata. Projects are flexible so that your team can work in the way that is best for them.
-
-### Staying up-to-date
-
-Your project automatically stays up-to-date with the information on {% data variables.product.company_short %}. When a pull request or issue changes, your project reflects that change. This integration also works both ways, so that when you change information about a pull request or issue from your project, the pull request or issue reflects that information.
-
-### Adding metadata to your tasks
-
-You can use custom fields to add metadata to your tasks. For example, you can track the following metadata:
-
-- a date field to track target ship dates
-- a number field to track the complexity of a task
-- a single select field to track whether a task is Low, Medium, or High priority
-- a text field to add a quick note
-- an iteration field to plan work week-by-week, including support for breaks
-
-### Viewing your project from different perspectives
-
-You can view your project as a high density table layout:
-
-![Project table](/assets/images/help/issues/projects_table.png)
-
-Or as a board:
-
-![Project board](/assets/images/help/issues/projects_board.png)
-
-To help you focus on specific aspects of your project, you can group, sort, or filter items:
-
-![Project view](/assets/images/help/issues/project_view.png)
-
-For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
-
-### Working with the project command palette
-
-You can use the project command palette to quickly change views or add fields. The command palette guides you so that you don't need to memorize custom keyboard shortcuts. For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
-
-### Automating project management tasks
-
-Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." You can also use the GraphQL API and {% data variables.product.prodname_actions %} to automate routine project management tasks. For more information, see "[Automating projects](/issues/trying-out-the-new-projects-experience/automating-projects)" and "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
-
-## Comparing projects (beta) with the non-beta projects
-
-Projects (beta) is a new, customizable version of projects. For more information about the non-beta version of projects, see "[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."
-
-## Sharing feedback
-
-You can share your feedback about projects (beta) with {% data variables.product.company_short %}. To join the conversation, see [the feedback discussion](https://github.com/community/community/discussions/categories/issues).
diff --git a/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
deleted file mode 100644
index f4721a25bc..0000000000
--- a/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
+++ /dev/null
@@ -1,204 +0,0 @@
----
-title: Creating a project (beta)
-intro: 'Learn how to make a project, populate it, and add custom fields.'
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-type: tutorial
-topics:
-  - Projects
----
-
-Projects are a customizable collection of items that stay up-to-date with {% data variables.product.company_short %} data. Your projects can track issues, pull requests, and ideas that you jot down. You can add custom fields and create views for specific purposes.
-
-{% data reusables.projects.projects-beta %}
-
-## Creating a project
-
-### Creating an organization project
-
-{% data reusables.projects.create-project %}
-
-### Creating a user project
-
-{% data reusables.projects.create-user-project %}
-
-## Updating your project description and README
-
-{% data reusables.projects.project-description %}
-
-## Adding items to your project
-
-Your project can track draft issues, issues, and pull requests.
-
-### Creating draft issues
-
-Draft issues are useful to quickly capture ideas.
-
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-1. Type your idea, then press **Enter**.
-1. To add body text, click on the title of the draft issue. In the markdown input box that appears, enter the text for the draft issue body, then click **Save**.
-
-Draft issues can have a title, text body, assignees, and any custom fields from your project. In order to populate the repository, labels, or milestones for a draft issue, you must first convert the draft issue to an issue. For more information, see "[Converting draft issues to issues](#converting-draft-issues-to-issues)."
-
-{% note %}
-
-**Note**: Users will not receive notifications when they are assigned to or mentioned in a draft issue unless the draft issue is converted to an issue.
-
-{% endnote %}
-
-### Issues and pull requests
-
-#### Paste the URL of an issue or pull request
-
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-1. Paste the URL of the issue or pull request.
-
-#### Searching for an issue or pull request
-
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-2. Enter <kbd>#</kbd>.
-3. Select the repository where the pull request or issue is located. You can type part of the repository name to narrow down your options.
-4. Select the issue or pull request. You can type part of the title to narrow down your options.
-
-#### Adding multiple issues or pull requests from a repository
-
-1. On {% data variables.product.product_location %}, navigate to the repository that contains the issues or pull requests you want to add to your project.
-{% data reusables.repositories.sidebar-issue-pr %}
-1. To the left of each issue title, select the issues that you want to add to your project.
-  ![Screenshot showing checkbox to select issue or pull request](/assets/images/help/issues/select-issue-checkbox.png)
-1. Optionally, to select every issue or pull request on the page, at the top of the list of issues or pull requests, select all. 
-  ![Screenshot showing checkbox to select all on screen](/assets/images/help/issues/select-all-checkbox.png)
-1. Above the list of issues or pull requests, click **Projects (beta)**. 
-  ![Screenshot showing checkbox to select all on screen](/assets/images/help/issues/projects-beta-assign-button.png)
-1. Click the projects you want to add the selected issues or pull requests to.
-  ![Screenshot showing checkbox to select all on screen](/assets/images/help/issues/projects-beta-assign-dropdown.png)
-
-#### Assigning a project from within an issue or pull request
-
-1. Navigate to the issue or pull request that you want to add to a project.
-2. In the side bar, click **Projects**.
-3. Select the project that you want to add the issue or pull request to.
-4. Optionally, populate the custom fields.
-
-   ![Project sidebar](/assets/images/help/issues/project_side_bar.png)
-
-## Converting draft issues to issues
-
-In table layout:
-
-1. Click the {% octicon "triangle-down" aria-label="the item menu" %} on the draft issue that you want to convert.
-2. Select **Convert to issue**.
-3. Select the repository that you want to add the issue to.
-4. Alternatively, edit the `labels`, `milestone`, or `repository` fields of the draft issue that you want to convert.
-
-In board layout:
-
-1. Click the {% octicon "kebab-horizontal" aria-label="the item menu" %} on the draft issue that you want to convert.
-2. Select **Convert to issue**.
-3. Select the repository that you want to add the issue to.
-
-## Removing items from your project
-
-You can archive an item to keep the context about the item in the project but remove it from the project views. You can delete an item to remove it from the project entirely.
-
-1. Select the item(s) to archive or delete. To select multiple items, do one of the following:
-     - <kbd>Command</kbd>+Click (Mac) or <kbd>Ctrl</kbd>+Click (Windows/Linux) each item.
-     - Select an item then <kbd>Shift</kbd>+<kbd>↑</kbd> or <kbd>Shift</kbd>+<kbd>↓</kbd> to select additional items above or below the initially selected item.
-     - Select an item then <kbd>Shift</kbd>+Click another item to select all items between the two items.
-     - Enter <kbd>Command</kbd>+<kbd>A</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>A</kbd> (Windows/Linux) to select all items in a column in a board layout or all items in a table layout.
-2. To archive all selected items, enter <kbd>E</kbd>. To delete all selected items, enter <kbd>Del</kbd>. Alternatively, select the {% octicon "triangle-down" aria-label="the item menu" %} (in table layout) or the {% octicon "kebab-horizontal" aria-label="the item menu" %} (in board layout), then select the desired action.
-
-You can restore archived items but not deleted items. For more information, see [Restoring archived items](#restoring-archived-items).
-
-## Restoring archived items
-
-1. Navigate to your project.
-1. In the top-right, click {% octicon "kebab-horizontal" aria-label="the kebab icon" %}.
-1. In the menu, click **Archived items**.
-1. Optionally, to filter the archived items displayed, type your filter into the text box above the list of items. For more information about the available filters, see "[Filtering projects (beta)](/issues/trying-out-the-new-projects-experience/filtering-projects)."
-
-   ![Screenshot showing field for filtering archived items](/assets/images/help/issues/filter-archived-items.png)
-   
-1. To the left of each item title, select the items you would like to restore.
-
-   ![Screenshot showing checkboxes next to archived items](/assets/images/help/issues/select-archived-item.png)
-   
-1. To restore the selected items, above the list of items, click **Restore**. 
-
-   ![Screenshot showing the "Restore" button](/assets/images/help/issues/restore-archived-item-button.png)
-
-## Adding fields
-
-As field values change, they are automatically synced so that your project and the items that it tracks are up-to-date.
-
-### Showing existing fields
-
-Your project tracks up-to-date information about issues and pull requests, including any changes to the title, assignees, labels, milestones, repository, reviewers, and linked pull requests. When your project initializes, "title" and "assignees" are displayed; the other fields are hidden. You can change the visibility of these fields in your project.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing "show".
-3. Select the desired command (for example: "Show: Repository").
-
-Alternatively, you can do this in the UI:
-
-1. Click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear.
-   ![Show or hide fields](/assets/images/help/issues/projects_fields_menu.png)
-2. Select the field(s) that you want to display or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed.
-
-### Adding custom fields
-
-You can add custom fields to your project. Custom fields will display on the side bar of issues and pull requests in the project.
-
-Custom fields can be text, number, date, single select, or iteration:
-
-- Text: The value can be any text.
-- Number: The value must be a number.
-- Date: The value must be a date.
-- Single select: The value must be selected from a set of specified values.
-- Iteration: The value must be selected from a set of date ranges (iterations). Iterations in the past are automatically marked as "completed", and the iteration covering the current date range is marked as "current". For more information, see "[Managing iterations in projects](/issues/trying-out-the-new-projects-experience/managing-iterations)."
-
-1. {% data reusables.projects.open-command-palette %} Start typing any part of "Create new field". When "Create new field" displays in the command palette, select it.
-2. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear. Click **New field**.
-3. A popup will appear for you to enter information about the new field.
-   ![New field](/assets/images/help/issues/projects_new_field.png)
-4. In the text box, enter a name for the new field.
-5. Select the dropdown menu and click the desired type.
-6. If you specified **Single select** as the type, enter the options.
-7. If you specified **Iteration** as the type, enter the start date of the first iteration and the duration of the iteration. Three iterations are automatically created, and you can add additional iterations on the project's settings page.
-
-You can also edit your custom fields.
-
-{% data reusables.projects.project-settings %}
-1. Under **Fields**, select the field that you want to edit.
-1. For single select fields, you can add, delete, or reorder the options.
-1. For iteration fields, you can add or delete iterations, change iteration names, and change the start date and duration of the iteration.
-
-   For more information on modifying iteration fields, see "[Managing iterations in projects](/issues/trying-out-the-new-projects-experience/managing-iterations)."
-
-## Customizing your views
-
-You can view your project as a table or board, group items by field, filter item, and more. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
-
-## Configuring built-in automation
-
-{% data reusables.projects.about-workflows %}
-
-You can enable or disable the built-in workflows for your project.
-
-{% data reusables.projects.enable-basic-workflow %}
-
-## Adding your project to a repository
-
-You can list relevant projects in a repository. You can only list projects that are owned by the same user or organization that owns the repository.
-
-In order for repository members to see a project listed in a repository, they must have visibility for the project. For more information, see "[Managing the visibility of your projects (beta)](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)" and "[Managing access to projects (beta)](/issues/trying-out-the-new-projects-experience/managing-access-to-projects)."
-
-1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository.
-1. Click {% octicon "table" aria-label="the project icon" %} **Projects**.
-1. Click **Projects (Beta)** in the side bar.
-1. Click **Add project**.
-1. In the search bar that appears, search for projects that are owned by the same user or organization that owns the repository.
-1. Click on a project to list it in your repository.
diff --git a/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md b/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
deleted file mode 100644
index 0b689f06e5..0000000000
--- a/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
+++ /dev/null
@@ -1,204 +0,0 @@
----
-title: Customizing your project (beta) views
-intro: 'Display the information you need by changing the layout, grouping, sorting, and filters in your project.'
-allowTitleToDifferFromFilename: true
-versions:
-  fpt: '*'
-  ghec: '*'
-type: reference
-topics:
-  - Projects
----
-
-{% data reusables.projects.projects-beta %}
-
-## Project command palette
-
-Use the project command palette to quickly change settings and run commands in your project.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of a command or navigate through the command palette window to find a command. See the next sections for more examples of commands.
-
-## Changing the project layout
-
-You can view your project as a table or as a board.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Switch layout".
-3. Choose the required command. For example, **Switch layout: Table**.
-
-Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to a view name and click **Table** or **Board**.
-
-## Showing and hiding fields
-
-You can show or hide a specific field.
-
-### Showing and hiding fields in table layout
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing the action you want to take ("show" or "hide") or the name of the field.
-3. Choose the required command. For example, **Show: Milestone**.
-
-Alternatively, click {% octicon "plus" aria-label="the plus icon" %} to the right of the table. In the drop-down menu that appears, indicate which fields to show or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed.
-
-Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the field name and click **Hide field**.
-
-### Showing and hiding fields in board layout
-
-1. Click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the view name.
-2. Under **configuration**, click {% octicon "list-unordered" aria-label="the unordered list icon" %}.
-3. In the menu that's displayed, select fields to add them and deselect fields to remove them from the view.
-
-## Reordering fields
-
-You can change the order of fields.
-
-1. Click the field header.
-2. While clicking, drag the field to the required location.
-
-## Reordering rows
-
-In table layout, you can change the order of rows.
-
-1. Click the number at the start of the row.
-2. While clicking, drag the row to the required location.
-
-## Sorting by field values
-
-In table layout, you can sort items by a field value.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Sort by" or the name of the field you want to sort by.
-3. Choose the required command. For example, **Sort by: Assignees, asc**.
-
-Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the field name that you want to sort by and click **Sort ascending** or **Sort descending**.
-
-{% note %}
-
-**Note:** When a table is sorted, you cannot manually reorder rows.
-
-{% endnote %}
-
-Follow similar steps to remove a sort.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Remove sort-by".
-3. Choose **Remove sort-by**.
-
-Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the view name and click the menu item that indicates the current sort.
-
-## Grouping by field values in table layout
-
-In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`. Similarly, when you add a new item to a group, the new item is populated with the value of the group.
-
-{% note %}
-
-**Note:** Currently, you cannot group by title, labels, reviewers, or linked pull requests.
-
-{% endnote %}
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Group by" or the name of the field you want to group by.
-3. Choose the required command. For example, **Group by: Status**.
-
-Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the field name that you want to group by and click **Group by values**.
-
-Follow similar steps to remove a grouping.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Remove group-by".
-3. Choose **Remove group-by**.
-
-Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the view name and click the menu item that indicates the current grouping.
-
-## Setting the column field in board layout
-
-In the board layout, you choose any single select or iteration field for your columns. If you drag an item to a new column, the value of that column is applied to the dragged item. For example, if you use the "Status" field for your board columns and then drag an item with a status of `In progress` to the `Done` column, the status of the item will switch to `Done`.
-
-1. {% data reusables.projects.open-command-palette %}
-1. Start typing "Column field by" or the name of the field you want to use for your columns.
-1. Choose the required command. For example, **Column field by: Status**.
-
-Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the board view that you want to modify and click {% octicon "columns" aria-label="the column icon" %} **Column field**. Then select the field that you want to use for the board columns.
-
-## Filtering items
-
-Click {% octicon "filter" aria-label="the filter icon" %} at the top of the table to show the "Filter by keyword or by field" bar. Start typing the field name and value that you want to filter by. As you type, possible values will appear.
-
-{% data reusables.projects.projects-filters %}
-
-Alternatively, use the command palette.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Filter by" or the name of the field you want to filter by.
-3. Choose the required command. For example, **Filter by Status**.
-4. Enter the value that you want to filter for. For example: "In progress". You can also filter for the absence of specific values (for example, choose "Exclude status" then choose a status) or the absence of all values (for example, "No status").
-
-In board layout, you can click on item data to filter for items with that value. For example, click on an assignee to show only items for that assignee. To remove the filter, click the item data again.
-
-For more information, see "[Filtering projects](/issues/trying-out-the-new-projects-experience/filtering-projects)."
-
-## Creating a project view
-
-Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project. 
-
-For example, you can have:
-- A view that shows all items not yet started (filter on "Status").
-- A view that shows the workload for each team (group by a custom "Team" field).
-- A view that shows the items with the earliest target ship date (sort by a date field).
-
-To add a new view:
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing "New view" (to create a new view) or "Duplicate view" (to duplicate the current view).
-3. Choose the required command.
-
-Alternatively, click {% octicon "plus" aria-label="the plus icon" %} **New view** next to the rightmost view.
-
-Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to a view name and click **Duplicate view**.
-
-The new view is automatically saved.
-
-## Saving changes to a view
-
-When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes. 
-
-![Unsaved changes indicator](/assets/images/help/projects/unsaved-changes.png)
-
-If you don't want to save the changes, you can ignore this indicator. No one else will see your changes.
-
-To save the current configuration of the view for all project members:
-1. {% data reusables.projects.open-command-palette %}
-1. Start typing "Save view" or "Save changes to new view".
-1. Choose the required command.
-
-Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to a view name and click **Save view** or **Save changes to new view**.
-
-## Reordering saved views
-
-To change the order of the tabs that contain your saved views, click and drag a tab to a new location.
-
-The new tab order is automatically saved.
-
-## Renaming a saved view
-
-To rename a view:
-1. Double click the name in the project tab.
-1. Change the name.
-1. Press Enter, or click outside of the tab.
-
-The name change is automatically saved.
-
-## Deleting a saved view
-
-To delete a view:
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Delete view".
-3. Choose the required command.
-
-Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to a view name and click **Delete view**.
-
-## Further reading
-
-- "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)"
-- "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)"
diff --git a/content/issues/trying-out-the-new-projects-experience/filtering-projects.md b/content/issues/trying-out-the-new-projects-experience/filtering-projects.md
deleted file mode 100644
index db4cdecb95..0000000000
--- a/content/issues/trying-out-the-new-projects-experience/filtering-projects.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Filtering projects (beta)
-intro: You can filter your projects to focus on specific information.
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Projects
-  - Organizations
----
-
-{% data reusables.projects.projects-beta %}
-
-## About filtering projects
-
-You can customize views using filters for item metadata, such as assignees and the labels applied to issues, and by the fields in your project. You can combine filters and save them as views. For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
-
-To filter a project, click {% octicon "filter" aria-label="The Filter icon" %} and start typing the fields and values you would like to filter for. As you type, possible values will appear. You can also open the command pallet and type "Filter by" to choose from the available filters.
-
-The same filters are available for insights, allowing you to filter the data used to create your charts. For more information, see "[Using insights with projects](/issues/trying-out-the-new-projects-experience/using-insights-with-projects)."
-
-## Syntax for filtering projects
-
-{% data reusables.projects.projects-filters %}
diff --git a/content/issues/trying-out-the-new-projects-experience/index.md b/content/issues/trying-out-the-new-projects-experience/index.md
deleted file mode 100644
index 9c5acfe3b4..0000000000
--- a/content/issues/trying-out-the-new-projects-experience/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Trying out the new projects experience
-shortTitle: Projects (beta)
-intro: 'Build customized projects to track your work in {% data variables.product.company_short %}.'
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Issues
-  - Projects
-children:
-  - /about-projects
-  - /quickstart
-  - /creating-a-project
-  - /migrating-your-project
-  - /managing-iterations
-  - /customizing-your-project-views
-  - /filtering-projects
-  - /using-the-api-to-manage-projects
-  - /automating-projects
-  - /managing-projects
-  - /managing-the-visibility-of-your-projects
-  - /managing-access-to-projects
-  - /using-insights-with-projects
-  - /best-practices-for-managing-projects
----
-
diff --git a/content/issues/trying-out-the-new-projects-experience/managing-iterations.md b/content/issues/trying-out-the-new-projects-experience/managing-iterations.md
deleted file mode 100644
index 9a4da9455a..0000000000
--- a/content/issues/trying-out-the-new-projects-experience/managing-iterations.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Managing iterations in projects (beta)
-intro: You can create iterations to plan upcoming work and group items.
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Projects
-  - Organizations
----
-
-{% data reusables.projects.projects-beta %}
-
-## About iterations
-
-You can create an iteration field to associate items with specific repeating blocks of time. Iterations can be set to any length of time, can include breaks, and can be individually edited to modify name and date range. With projects, you can group by iteration to visualize the balance of upcoming work, use filters to focus on a single iteration, and sort by iteration.
-
-When you first create an iteration field, three iterations are automatically created.  You can add additional iterations and make other changes on your project's settings page.
-
-![Screenshot showing the settings for an iteration field](/assets/images/help/issues/iterations-example.png)
-
-## Creating an iteration field
-
-You can create an iteration field using the command palette or the project's interface.
-
-1. {% data reusables.projects.open-command-palette %} Start typing any part of "Create new field". When "Create new field" displays in the command palette, select it.
-
-   Alternatively, click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear. Click **New field**.
-1. In the text box, enter a name for the new iteration field.
-1. Select the dropdown menu below and click **Iteration**.
-1. Optionally, if you want to change the starting date from the current day, select the calendar dropdown next to "Starts on" and click on a new starting date.
-2. To change the duration of each iteration, type a new number, then select the dropdown and click either **days** or **weeks**.
-3. Click **Save & create**.
-  
-## Adding new iterations
-
-{% data reusables.projects.project-settings %}
-1. Click the name of the iteration field you want to adjust.
-1. To add a new iteration of the same duration, click **Add iteration**.
-1. Optionally, to customize the duration of the new iteration and when it will start, click {% octicon "triangle-down" aria-label="The triangle icon" %} next to "Add iteration", select a starting date and duration, and click **Add**.
-1. Click **Save changes**.
-
-## Editing an iteration
-
-You can edit iterations in your project settings. You can also access the settings for an iteration field by clicking {% octicon "triangle-down" aria-label="The triangle icon" %} in the table header for the field and clicking **Edit values**.
-
-{% data reusables.projects.project-settings %}
-1. Click the name of the iteration field you want to adjust.
-1. To change the name of an iteration, click on the name and start typing.
-1. To change the date or duration of an iteration, click on the date to open the calendar. Click on the start day, then click the end day, and then click **Apply**.
-1. Optionally, to delete an iteration, click {% octicon "trash" aria-label="The trash icon" %}.
-1. Click **Save changes**.
-
-## Inserting a break
-
-You can insert breaks into your iterations to communicate when you are taking time away from scheduled work. The duration of a new break defaults to the length of the most recently created iteration.
-
-{% data reusables.projects.project-settings %}
-1. Click the name of the iteration field you want to adjust.
-2. On the dividing line above an iteration and to the right, click **Insert break**.
-   ![Screenshot showing location of "Insert break" button](/assets/images/help/issues/iteration-insert-break.png)
-3. Optionally, to change the duration of the break, click on the date to open the calendar. Click on the start day, then click the end day, and then click **Apply**.
-4. Click **Save changes**.
diff --git a/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md b/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md
deleted file mode 100644
index 147f39eb56..0000000000
--- a/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Managing the visibility of your projects (beta)
-intro: You can control who can view your projects.
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Projects
-  - Organizations
----
-
-{% data reusables.projects.projects-beta %}
-
-## About project visibility
-
-Projects (beta) can be public or private. For public projects, everyone on the internet can view the project. For private projects, only users granted at least read access can see the project.
-
-Only the project visibility is affected; to view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository.
-
-![Project with hidden item](/assets/images/help/projects/hidden-items.png)
-
-Only project admins can control project visibility.
-
-In private, organization-owned projects, the avatars of users who are current making updates to the project are displayed in the project UI.
-
-Project admins can also manage write and admin access to their project and control read access for individual users. For more information, see "[Managing access to projects](/issues/trying-out-the-new-projects-experience/managing-access-to-projects)."
-
-## Changing project visibility
-
-{% data reusables.projects.project-settings %}
-1. Under **Visibility**, select **Private** or **Public**.
diff --git a/content/issues/trying-out-the-new-projects-experience/quickstart.md b/content/issues/trying-out-the-new-projects-experience/quickstart.md
deleted file mode 100644
index c0d5150742..0000000000
--- a/content/issues/trying-out-the-new-projects-experience/quickstart.md
+++ /dev/null
@@ -1,166 +0,0 @@
----
-title: Quickstart for projects (beta)
-intro: 'Experience the speed, flexibility, and customization of projects (beta) by creating a project in this interactive guide.'
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-type: quick_start
-topics:
-  - Projects
----
-
-{% data reusables.projects.projects-beta %}
-
-## Introduction
-
-This guide demonstrates how to use projects (beta) to plan and track work. In this guide, you will create a new project and add a custom field to track priorities for your tasks. You'll also learn how to create saved views that help you communicate priorities and progress with your collaborators.
-
-## Prerequisites
-
-You can either create an organization project or a user project. To create an organization project, you need a {% data variables.product.prodname_dotcom %} organization. For more information about creating an organization, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
-
-In this guide, you will add existing issues from repositories owned by your organization (for organization projects) or by you (for user projects) to your new project. For more information about creating issues, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."
-
-## Creating a project
-
-First, create an organization project or a user project.
-
-### Creating an organization project
-
-{% data reusables.projects.create-project %}
-
-### Creating a user project
-
-{% data reusables.projects.create-user-project %}
-
-## Setting your project description and README
-
-{% data reusables.projects.project-description %}
-
-## Adding issues to your project
-
-Next, add a few issues to your project.
-
-When your new project initializes, it prompts you to add items to your project. If you lose this view or want to add more issues later, place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-
-1. Type `#`.
-2. Select the repository where your issue is located. To narrow down the options, you can start typing a part of the repository name.
-3. Select your issue. To narrow down the options, you can start typing a part of the issue title.
-
-Repeat the above steps a few times to add multiple issues to your project.
-
-For more information about other ways to add issues to your project, or about other items you can add to your project, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-items-to-your-project)."
-
-## Adding draft issues to your project
-
-Next, add a draft issue to your project.
-
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-1. Type your idea, then press **Enter**.
-1. Click on the title of the draft issue. In the markdown input box that appears, enter the some more information about your idea, then click **Save**.
-
-## Creating a field to track priority
-
-Now, create a custom field called `Priority` to contain the values: `High`, `Medium`, or `Low`.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of "Create new field".
-3. Select **Create new field**.
-4. In the resulting pop-up, enter `Priority` in the text box.
-5. In the drop-down, select **Single select**.
-6. Add options for `High`, `Medium`, and `Low`. You can also include emojis in your options.
-   ![New single select field example](/assets/images/help/projects/new-single-select-field.png)
-7. Click **Save**.
-
-Specify a priority for all issues in your project.
-
-![Example priorities](/assets/images/help/projects/priority_example.png)
-
-## Grouping issues by priority
-
-Next, group all of the items in your project by priority to make it easier to focus on the high priority items.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of "Group by".
-3. Select **Group by: Priority**.
-
-Now, move issues between groups to change their priority.
-
-1. Choose an issue.
-2. Drag and drop the issue into a different priority group. When you do this, the priority of the issue will change to be the priority of its new group.
-
-![Move issue between groups](/assets/images/help/projects/move_between_group.gif)
-
-## Saving the priority view
-
-When you grouped your issues by priority in the previous step, your project displayed an indicator to show that the view was modified. Save these changes so that your collaborators will also see the tasks grouped by priority.
-
-1. Select the drop-down menu next to the view name.
-2. Click **Save changes**.
-
-To indicate the purpose of the view, give it a descriptive name.
-
-1. Place your cursor in the current view name, **View 1**.
-2. Replace the existing text with the new name, `Priorities`.
-
-You can share the URL with your team to keep everyone aligned on the project priorities.
-
-When a view is saved, anyone who opens the project will see the saved view. Here, you grouped by priority, but you can also add other modifiers such as sort, filter, or layout. Next, you will create a new view with the layout modified.
-
-## Adding a board layout
-
-To view the progress of your project's issues, you can switch to board layout.
-
-The board layout is based on the status field, so specify a status for each issue in your project.
-
-![Example status](/assets/images/help/projects/status_example.png)
-
-Then, create a new view.
-
-1. Click {% octicon "plus" aria-label="the plus icon" %} **New view** next to the rightmost view.
-
-Next, switch to board layout.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of "Switch layout: Board".
-3. Select **Switch layout: Board**.
-   ![Example priorities](/assets/images/help/projects/example_board.png)
-
-When you changed the layout, your project displayed an indicator to show that the view was modified. Save this view so that you and your collaborators can easily access it in the future.
-
-1. Select the drop-down menu next to the view name.
-2. Click **Save changes**.
-
-To indicate the purpose of the view, give it a descriptive name.
-
-1. Place your cursor in the current view name, **View 2**.
-2. Replace the existing text with the new name, `Progress`.
-
-![Example priorities](/assets/images/help/projects/project-view-switch.gif)
-
-## Configure built-in automation
-
-Finally, add a built in workflow to set the status to **Todo** when an item is added to your project.
-
-1. In your project, click {% octicon "workflow" aria-label="the workflow icon" %}.
-2. Under **Default workflows**, click **Item added to project**.
-3. Next to **When**, ensure that both `issues` and `pull requests` are selected.
-4. Next to **Set**, select **Status:Todo**.
-5. Click the **Disabled** toggle to enable the workflow.
-
-## Next steps
-
-You can use projects for a wide range of purposes. For example:
-
-- Track work for a release
-- Plan a sprint
-- Prioritize a backlog
-
-Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_issues %}:
-
-- To provide feedback about the projects (beta) experience, go to the [GitHub feedback repository](https://github.com/community/community/discussions/categories/issues).
-- To learn more about how projects can help you with planning and tracking, see "[About projects](/issues/trying-out-the-new-projects-experience/about-projects)."
-- To learn more about the fields and items you can add to your project, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)."
-- To learn about more ways to display the information you need, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
diff --git a/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md b/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md
deleted file mode 100644
index c885ea9641..0000000000
--- a/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Using insights with projects (beta)
-intro: You can view and customize charts that are built from your project's data.
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Projects
-  - Organizations
----
-
-{% data reusables.projects.insights-alpha %}
-
-## About insights
-
-You can use insights to view and customize charts that use the items added to your project as their source data. The default "Burn up" chart shows item status over time, allowing you to visualize progress and spot patterns over time. 
-
-![Screenshot showing an example of the default burn up chart for the current iteration](/assets/images/help/issues/burnup-example.png)
-
-You can apply filters to the default chart and also create your own charts. When you create a chart, you set the filters, chart type, and the information displayed, and the chart is available to anyone that can view the project.
-
-![Screenshot showing an stacked column chart showing item types for each iteration](/assets/images/help/issues/column-chart-example.png)
-
-## Creating a chart
-
-{% data reusables.projects.access-insights %}
-3. In the menu on the left, click **New chart**.
-4. Optionally, to change the name of the new chart, click {% octicon "triangle-down" aria-label="The triangle icon" %}, type a new name, and press <kbd>Return</kbd>.
-5. Above the chart, type filters to change the data used to build the chart. For more information, see "[Filtering projects](/issues/trying-out-the-new-projects-experience/filtering-projects)."
-6. To the right of the filter text box, click **Save changes**.
-
-## Configuring a chart
-
-{% data reusables.projects.access-insights %}
-1. In the menu on the left, click on the chart you would like to configure.
-1. On the right side of the page, click **Configure**. A panel will open on the right.
-1. To change the type of chart, select the **Layout** dropdown and click on the chart type you want to use.
-1. To change the field used for your chart's X-axis, select the **X-axis** dropdown and click the field you want to use.
-1. Optionally, to group the items on your X-axis by another field, select **Group by** and click on the field you want to use, or click "None" to disable grouping.
-1. Optionally, if your project contains number fields and you want the Y-axis to display the sum, average, minimum, or maximum of one of those number fields, select **Y-axis** and click an option. Then, select the dropdown that appears beneath and click on the number field you want to use. 
-1. To save your chart, click **Save changes**.
diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
index 219fb4280e..d5cee8b617 100644
--- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
+++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -52,6 +52,7 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes or ghec %}
 | [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. | {% endif %}
 | [`hook`](#hook-category-actions) | Contains all activities related to webhooks.
+| [`integration_installation`](#integration_installation-category-actions)  | Contains activities related to integrations installed in an account. |
 | [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |{% ifversion ghec or ghae %}
 | [`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 %}
@@ -361,6 +362,21 @@ An overview of some of the most common actions that are recorded as events in th
 | `destroy` | Triggered when an existing hook was removed from a repository.
 | `events_changed` | Triggered when the events on a hook have been altered.
 
+### `integration_installation` category actions
+
+| Action | Description
+|--------|-------------
+| `contact_email_changed` | A contact email for an integration was changed.
+| `create` | An integration was installed.
+| `destroy` | An integration was uninstalled.
+| `repositories_added` | Repositories were added to an integration.
+| `repositories_removed` | Repositories were removed from an integration.
+{%- ifversion fpt or ghec %}
+| `suspend` | An integration was suspended.
+| `unsuspend` | An integration was unsuspended.
+{%- endif %}
+| `version_updated` | Permissions for an integration were updated.
+
 ### `integration_installation_request` category actions
 
 | Action | Description
diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
index 32d4aa5a3f..d2ca75bb1b 100644
--- a/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
+++ b/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Adding an outside collaborator to a project board in your organization
-intro: 'As an organization owner or project board admin, you can add an outside collaborator and customize their permissions to a project board.'
+title: Adding an outside collaborator to a {% data variables.product.prodname_project_v1 %} in your organization
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can add an outside collaborator and customize their permissions to a {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization
@@ -13,13 +13,17 @@ topics:
   - Organizations
   - Teams
 shortTitle: Add a collaborator
+allowTitleToDifferFromFilename: true
 ---
 
-An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a project board in your organization.
+{% data reusables.projects.project_boards_old %}
+
+An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a {% data variables.projects.projects_v1_board %} in your organization.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/content/organizations/managing-access-to-your-organizations-project-boards/index.md
index 9606c54fbb..0ea88937f3 100644
--- a/content/organizations/managing-access-to-your-organizations-project-boards/index.md
+++ b/content/organizations/managing-access-to-your-organizations-project-boards/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your organization’s project boards
-intro: 'As an organization owner or project board admin, you can give organization members, teams, and outside collaborators different levels of access to project boards owned by your organization.'
+title: Managing access to your organization’s {% data variables.product.prodname_projects_v1 %}
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give organization members, teams, and outside collaborators different levels of access to {% data variables.projects.projects_v1_boards %} owned by your organization.'
 redirect_from:
   - /articles/managing-access-to-your-organization-s-project-boards
   - /articles/managing-access-to-your-organizations-project-boards
@@ -20,6 +20,7 @@ children:
   - /managing-an-individuals-access-to-an-organization-project-board
   - /adding-an-outside-collaborator-to-a-project-board-in-your-organization
   - /removing-an-outside-collaborator-from-an-organization-project-board
-shortTitle: Manage project board access
+shortTitle: Manage {% data variables.product.prodname_project_v1 %} access
+allowTitleToDifferFromFilename: true
 ---
 
diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
index be34c8beea..d665469a0f 100644
--- a/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
+++ b/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to a project board for organization members
-intro: 'As an organization owner or project board admin, you can set a default permission level for a project board for all organization members.'
+title: Managing access to a {% data variables.product.prodname_project_v1 %} for organization members
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can set a default permission level for a {% data variables.projects.projects_v1_board %} for all organization members.'
 redirect_from:
   - /articles/managing-access-to-a-project-board-for-organization-members
   - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members
@@ -13,21 +13,25 @@ topics:
   - Organizations
   - Teams
 shortTitle: Manage access for members
+allowTitleToDifferFromFilename: true
 ---
 
-By default, organization members have write access to their organization's project boards unless organization owners or project board admins set different permissions for specific project boards.
+{% data reusables.projects.project_boards_old %}
+
+By default, organization members have write access to their organization's {% data variables.projects.projects_v1_boards %} unless organization owners or {% data variables.projects.projects_v1_board %} admins set different permissions for specific {% data variables.projects.projects_v1_boards %}.
 
 ## Setting a baseline permission level for all organization members
 
 {% tip %}
 
-**Tip:** You can give an organization member higher permissions to project board. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
+**Tip:** You can give an organization member higher permissions to {% data variables.projects.projects_v1_board %}. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% endtip %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
@@ -37,6 +41,6 @@ By default, organization members have write access to their organization's proje
 
 ## Further reading
 
-- "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)"
-- "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+- "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)"
+- "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)"
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
index ebafc21d9f..7d5d783f39 100644
--- a/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
+++ b/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Managing an individual’s access to an organization project board
-intro: 'As an organization owner or project board admin, you can manage an individual member''s access to a project board owned by your organization.'
+title: Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can manage an individual member''s access to a {% data variables.projects.projects_v1_board %} owned by your organization.'
 redirect_from:
   - /articles/managing-an-individual-s-access-to-an-organization-project-board
   - /articles/managing-an-individuals-access-to-an-organization-project-board
@@ -14,19 +14,23 @@ topics:
   - Organizations
   - Teams
 shortTitle: Manage individual access
+allowTitleToDifferFromFilename: true
 ---
 
+{% data reusables.projects.project_boards_old %}
+
 {% note %}
 
-**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." 
+**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." 
 
 {% endnote %}
 
-## Giving an organization member access to a project board
+## Giving an organization member access to a {% data variables.projects.projects_v1_board %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
@@ -36,24 +40,26 @@ shortTitle: Manage individual access
 {% data reusables.project-management.add-collaborator %}
 {% data reusables.project-management.collaborator-permissions %}
 
-## Changing an organization member's access to a project board
+## Changing an organization member's access to a {% data variables.projects.projects_v1_board %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
 {% data reusables.project-management.collaborator-option %}
 {% data reusables.project-management.collaborator-permissions %}
 
-## Removing an organization member's access to a project board
+## Removing an organization member's access to a {% data variables.projects.projects_v1_board %}
 
-When you remove a collaborator from a project board, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a project board, you must remove access for each role the person has. For instance, a person may have access to the project board as an organization member or team member. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
+When you remove a collaborator from a {% data variables.projects.projects_v1_board %}, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a {% data variables.projects.projects_v1_board %}, you must remove access for each role the person has. For instance, a person may have access to the {% data variables.projects.projects_v1_board %} as an organization member or team member. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
@@ -62,4 +68,4 @@ When you remove a collaborator from a project board, they may still retain acces
 
 ## Further reading
 
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index e495605761..7aa452326b 100644
--- a/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Managing team access to an organization project board
-intro: 'As an organization owner or project board admin, you can give a team access to a project board owned by your organization.'
+title: Managing team access to an organization {% data variables.product.prodname_project_v1 %}
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.'
 redirect_from:
   - /articles/managing-team-access-to-an-organization-project-board
   - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board
@@ -13,29 +13,33 @@ topics:
   - Organizations
   - Teams
 shortTitle: Manage team access
+allowTitleToDifferFromFilename: true
 ---
 
+{% data reusables.projects.project_boards_old %}
+
 {% warning %}
 
 **Warnings:**
-- You can change a team's permission level if the team has direct access to a project board. If the team's access to the project board is inherited from a parent team, you must change the parent team's access to the project board.
-- If you add or remove project board access for a parent team, each of that parent's child teams will also receive or lose access to the project board. For more information, see "[About teams](/articles/about-teams)."
+- You can change a team's permission level if the team has direct access to a {% data variables.projects.projects_v1_board %}. If the team's access to the {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %}.
+- If you add or remove {% data variables.projects.projects_v1_board %} access for a parent team, each of that parent's child teams will also receive or lose access to the {% data variables.projects.projects_v1_board %}. For more information, see "[About teams](/articles/about-teams)."
 
 {% endwarning %}
 
-## Giving a team access to a project board
+## Giving a team access to a {% data variables.projects.projects_v1_board %}
 
-You can give an entire team the same permission level to a project board.
+You can give an entire team the same permission level to a {% data variables.projects.projects_v1_board %}.
 
 {% note %}
 
-**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a project board, and a project board admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the project board. For more information see, "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
+**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a {% data variables.projects.projects_v1_board %}, and a {% data variables.projects.projects_v1_board %} admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the {% data variables.projects.projects_v1_board %}. For more information see, "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% endnote %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
@@ -45,14 +49,14 @@ You can give an entire team the same permission level to a project board.
 10. Next to the team name, use the drop-down menu to select the desired permission level: **Read**, **Write**, or **Admin**.
  ![Team permissions drop-down menu with read, write, and admin options](/assets/images/help/projects/org-project-team-choose-permissions.png)
 
-## Configuring a team's access to a project board
+## Configuring a team's access to a {% data variables.projects.projects_v1_board %}
 
-If a team's access to a project board is inherited from a parent team, you must change the parent team's access to the project board to update access to the child teams.
+If a team's access to a {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %} to update access to the child teams.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
 4. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**.
   ![The team repositories tab](/assets/images/help/organizations/team-project-board-button.png)
-5. To change permissions levels, to the right of the project board you want to update, use the drop-down. To remove a project board, click **{% octicon "trash" aria-label="The trash icon" %}**.
+5. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the drop-down. To remove a {% data variables.projects.projects_v1_board %}, click **{% octicon "trash" aria-label="The trash icon" %}**.
   ![Remove a project board from your team trash button](/assets/images/help/organizations/trash-button.png)
diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md
index 2123ca4ac1..cdb23eca2e 100644
--- a/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md
+++ b/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Project board permissions for an organization
-intro: 'Organization owners and people with project board admin permissions can customize who has read, write, and admin permissions to your organization’s project boards.'
+title: '{% data variables.product.prodname_project_v1_caps %} permissions for an organization'
+intro: 'Organization owners and people with {% data variables.projects.projects_v1_board %} admin permissions can customize who has read, write, and admin permissions to your organization’s {% data variables.projects.projects_v1_boards %}.'
 redirect_from:
   - /articles/project-board-permissions-for-an-organization
   - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization
@@ -12,35 +12,38 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Project board permissions
+shortTitle: '{% data variables.product.prodname_project_v1_caps %} permissions'
+allowTitleToDifferFromFilename: true
 ---
 
+{% data reusables.projects.project_boards_old %}
+
 ## Permissions overview
 
-There are three levels of permissions to a project board for people and teams:
+There are three levels of permissions to a {% data variables.projects.projects_v1_board %} for people and teams:
 
 {% data reusables.project-management.project-board-permissions %}
 
-Organization owners and people with admin permissions can give a person access to an organization project board individually, as an outside collaborator or organization member, or through their membership in a team or organization. An outside collaborator is someone who is not an organization member but given permissions to collaborate in your organization.
+Organization owners and people with admin permissions can give a person access to an organization {% data variables.projects.projects_v1_board %} individually, as an outside collaborator or organization member, or through their membership in a team or organization. An outside collaborator is someone who is not an organization member but given permissions to collaborate in your organization.
 
-Organization owners and people with admin permissions to a project board can also:
+Organization owners and people with admin permissions to a {% data variables.projects.projects_v1_board %} can also:
 - Set default project board permissions for all organization members.
-- Manage access to the project board for organization members, teams, and outside collaborators. For more information, see "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)", "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)", or "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)."
-- Manage project board visibility. For more information, see "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)."
+- Manage access to the project board for organization members, teams, and outside collaborators. For more information, see "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)", "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)", or "[Managing access to a {% data variables.product.prodname_project_v1 %} for organization members](/articles/managing-access-to-a-project-board-for-organization-members)."
+- Manage project board visibility. For more information, see "[Managing access to a {% data variables.product.prodname_project_v1 %} for organization members](/articles/managing-access-to-a-project-board-for-organization-members)."
 
-## Cascading permissions for project boards
+## Cascading permissions for {% data variables.projects.projects_v1_boards %}
 
 {% data reusables.project-management.cascading-permissions %}
 
-For example, if an organization owner has given all organization members read permissions to a project board, and a project board admin gives an organization member write permissions to that board as an individual collaborator, that person would have write permissions to the project board.
+For example, if an organization owner has given all organization members read permissions to a {% data variables.projects.projects_v1_board %}, and a {% data variables.projects.projects_v1_board %} admin gives an organization member write permissions to that board as an individual collaborator, that person would have write permissions to the {% data variables.projects.projects_v1_board %}.
 
-## Project board visibility
+## {% data variables.projects.projects_v1_board_caps %} visibility
 
-{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to {% ifversion ghae %}internal{% else %}public{% endif %} and back again. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)."
+{% data reusables.project-management.project-board-visibility %} You can change the {% data variables.projects.projects_v1_board %}'s visibility from private to {% ifversion ghae %}internal{% else %}public{% endif %} and back again. For more information, see "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility)."
 
 ## Further reading
 
-- "[Changing project board visibility](/articles/changing-project-board-visibility)"
-- "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)"
-- "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)"
-- "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)"
+- "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility)"
+- "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)"
+- "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)"
+- "[Managing access to a {% data variables.product.prodname_project_v1 %} for organization members](/articles/managing-access-to-a-project-board-for-organization-members)"
diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
index b0f09b56ed..1ced0b0208 100644
--- a/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
+++ b/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Removing an outside collaborator from an organization project board
-intro: 'As an organization owner or project board admin, you can remove an outside collaborator''s access to a project board.'
+title: Removing an outside collaborator from an organization {% data variables.product.prodname_project_v1 %}
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can remove an outside collaborator''s access to a {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /articles/removing-an-outside-collaborator-from-an-organization-project-board
   - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board
@@ -13,11 +13,15 @@ topics:
   - Organizations
   - Teams
 shortTitle: Remove outside collaborator
+allowTitleToDifferFromFilename: true
 ---
 
+{% data reusables.projects.project_boards_old %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
diff --git a/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md b/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
new file mode 100644
index 0000000000..0db3747d40
--- /dev/null
+++ b/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
@@ -0,0 +1,27 @@
+---
+title: 'Allowing project visibility changes in your organization'
+intro: 'Organization owners can allow members with admin permissions to adjust the visibility of projects in their organization.'
+versions:
+  feature: "projects-v2"
+topics:
+  - Organizations
+  - Projects
+shortTitle: 'Project visibility permissions'
+allowTitleToDifferFromFilename: true
+permissions: Organization owners can allow project visibility changes for an organization.
+---
+
+You can restrict who has the ability to change the visibility of projects in your organization, such as restricting members from changing a project from private to public. 
+
+You can limit the ability to change project visibility to just organization owners, or you can allow anyone with admin permissions on a project to change the visibility.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
+1. To allow members to adjust project visibility, select **Allow members to change project visibilities for this organization**.
+  ![Screenshot showing checkbox to set visibility changes](/assets/images/help/projects-v2/visibility-change-checkbox.png)
+1. Click **Save**.
+
+## Further reading
+
+- "[Managing visibility of your projects](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)"
\ No newline at end of file
diff --git a/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md b/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
new file mode 100644
index 0000000000..f67fa5df99
--- /dev/null
+++ b/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
@@ -0,0 +1,28 @@
+---
+title: 'Disabling insights for {% data variables.projects.projects_v2 %} in your organization'
+intro: Organization owners can turn off insights for {% data variables.product.prodname_projects_v2 %} in their organization.
+versions:
+  feature: "projects-v2"
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+shortTitle: Disable {% data variables.product.prodname_projects_v2 %} insights
+allowTitleToDifferFromFilename: true
+---
+
+After you disable insights for projects in your organization, it won't be possible to access insights for any projects owned by the organization.
+
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the sidebar, click **{% octicon "sliders" aria-label="The sliders icon" %} Features**.
+   ![Screenshot showing features menu item](/assets/images/help/projects-v2/features-org-menu.png)
+1. Under "Insights", deselect **Enable Insights for the organization**.
+   ![Screenshot showing Enable Insights for the organization checkbox](/assets/images/help/projects-v2/disable-insights-checkbox.png)
+1. Click **Save**.
+   ![Screenshot showing save button](/assets/images/help/projects-v2/disable-insights-save.png)
+
+## Further reading
+
+- "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)"
+- "[About insights for {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects)"
diff --git a/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
index c83355b58f..01bd82747c 100644
--- a/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
+++ b/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Disabling project boards in your organization
-intro: Organization owners can turn off organization-wide project boards and repository project boards in an organization.
+title: 'Disabling {% ifversion projects-v2 %}projects{% else %}project boards{% endif %} in your organization'
+intro: 'Organization owners can turn off {% ifversion projects-v2 %}organization-wide {% data variables.projects.projects_v2 %}, organization-wide {% data variables.projects.projects_v1_boards %}, and repository-level {% data variables.projects.projects_v1_boards %}{% else %}organization-wide project boards and repository project boards{% endif %} in an organization.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-your-organization
   - /articles/disabling-project-boards-in-your-organization
@@ -12,12 +12,14 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Disable project boards
+shortTitle: Disable projects
+allowTitleToDifferFromFilename: true
 ---
-After you disable organization-wide project boards, it won’t be possible to create new project boards at the organization level, and any existing organization-level project boards will become inaccessible at their previous URLs. Project boards in repositories in the organization are not affected.
+After you disable organization-wide project boards, it won’t be possible to create new project boards at the organization level, and any existing organization-level project boards will become inaccessible at their previous URLs. Project boards in repositories in the organization are not affected. {% ifversion projects-v2 %}These settings apply to {% data variables.projects.projects_v2 %} and {% data variables.projects.projects_v1_boards %}.{% endif %}
 
 After you disable repository project boards in an organization, it won't be possible to create new project boards in any repositories in the organization, and any existing project boards in repositories in the organization will become inaccessible at their previous URLs. Project boards at the organization level are not affected.
 
+
 When you disable project boards, you will no longer see project board information in timelines or [audit logs](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization).
 
 
@@ -36,7 +38,8 @@ When you disable project boards, you will no longer see project board informatio
 
 ## Further reading
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Closing a project board](/articles/closing-a-project-board)"
-- "[Deleting a project board](/articles/deleting-a-project-board)"
-- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)"
+{% ifversion projects-v2 %}- "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)"{% endif %}
+- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Closing a {% data variables.projects.projects_v1_board %}](/articles/closing-a-project-board)"
+- "[Deleting a {% data variables.projects.projects_v1_board %}](/articles/deleting-a-project-board)"
+- "[Disabling {% data variables.projects.projects_v1_boards %} in a repository](/articles/disabling-project-boards-in-a-repository)"
diff --git a/content/organizations/managing-organization-settings/index.md b/content/organizations/managing-organization-settings/index.md
index 8a5e001da1..e5818036d4 100644
--- a/content/organizations/managing-organization-settings/index.md
+++ b/content/organizations/managing-organization-settings/index.md
@@ -41,6 +41,8 @@ children:
   - /integrating-jira-with-your-organization-project-board
   - /upgrading-to-the-corporate-terms-of-service
   - /disabling-project-boards-in-your-organization
+  - /disabling-insights-for-projects-in-your-organization
+  - /allowing-project-visibility-changes-in-your-organization
 shortTitle: Manage organization settings
 ---
 {% ifversion fpt or ghec %}
diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
index bfe116aa3a..b844e2251b 100644
--- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
+++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
@@ -40,12 +40,12 @@ The `dig` command, which can be used to verify correct configuration of DNS reco
 
 ## Configuring a subdomain
 
-To set up a `www` or custom subdomain, such as `www.example.com` or `blog.example.com`, you must add your domain in the repository settings, which will create a CNAME file in your site’s repository. After that, configure a CNAME record with your DNS provider.
+To set up a `www` or custom subdomain, such as `www.example.com` or `blog.example.com`, you must add your domain in the repository settings. After that, configure a CNAME record with your DNS provider.
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-4. Under "Custom domain", type your custom domain, then click **Save**. This will create a commit that adds a _CNAME_ file in the root of your publishing source.
+4. Under "Custom domain", type your custom domain, then click **Save**. If you are publishing your site from a branch, this will create a commit that adds a `CNAME` file to the root of your source branch. If you are publishing your site with a custom {% data variables.product.prodname_actions %} workflow , no `CNAME` file is created. For more information about your publishing source, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
   ![Save custom domain button](/assets/images/help/pages/save-custom-subdomain.png)
 5. Navigate to your DNS provider and create a `CNAME` record that points your subdomain to the default domain for your site. For example, if you want to use the subdomain `www.example.com` for your user site, create a `CNAME` record that points `www.example.com` to `<user>.github.io`. If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `<organization>.github.io`. The `CNAME` record should always point to `<user>.github.io` or `<organization>.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
 
@@ -64,14 +64,14 @@ To set up a `www` or custom subdomain, such as `www.example.com` or `blog.exampl
 
 ## Configuring an apex domain
 
-To set up an apex domain, such as `example.com`, you must configure a _CNAME_ file  in your {% data variables.product.prodname_pages %} repository and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider.
+To set up an apex domain, such as `example.com`, you must configure a custom domain in your repository settings and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider.
 
 {% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)."
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-4. Under "Custom domain", type your custom domain, then click **Save**. This will create a commit that adds a _CNAME_ file in the root of your publishing source.
+4. Under "Custom domain", type your custom domain, then click **Save**. If you are publishing your site from a branch, this will create a commit that adds a `CNAME` file to the root of your source branch. If you are publishing your site with a custom {% data variables.product.prodname_actions %} workflow , no `CNAME` file is created. For more information about your publishing source, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
   ![Save custom domain button](/assets/images/help/pages/save-custom-apex-domain.png)
 5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. You can also create `AAAA` records for IPv6 support. {% data reusables.pages.contact-dns-provider %}
     - To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %}
diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
index 892a5af812..754f259468 100644
--- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
+++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
@@ -18,7 +18,9 @@ shortTitle: Troubleshoot a custom domain
 
 ## _CNAME_ errors
 
-Custom domains are stored in a _CNAME_ file in the root of your publishing source. You can add or update this file through your repository settings or manually. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
+{% ifversion pages-custom-workflow %}If you are publishing from a custom {% data variables.product.prodname_actions %} workflow, any _CNAME_ file is ignored and is not required.{% endif %}
+
+If you are publishing from a branch, custom domains are stored in a _CNAME_ file in the root of your publishing source. You can add or update this file through your repository settings or manually. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
 
 For your site to render at the correct domain, make sure your _CNAME_ file still exists in the repository. For example, many static site generators force push to your repository, which can overwrite the _CNAME_ file that was added to your repository when you configured your custom domain. If you build your site locally and push generated files to {% data variables.product.product_name %}, make sure to pull the commit that added the _CNAME_ file to your local repository first, so the file will be included in the build.
 
diff --git a/content/pages/getting-started-with-github-pages/about-github-pages.md b/content/pages/getting-started-with-github-pages/about-github-pages.md
index 6e8072ac21..765d90a90f 100644
--- a/content/pages/getting-started-with-github-pages/about-github-pages.md
+++ b/content/pages/getting-started-with-github-pages/about-github-pages.md
@@ -71,15 +71,11 @@ For more information, see "[Enabling subdomain isolation](/enterprise/admin/inst
 
 ## Publishing sources for {% data variables.product.prodname_pages %} sites
 
-The publishing source for your {% data variables.product.prodname_pages %} site is the branch and folder where the source files for your site are stored.
-
 {% data reusables.pages.private_pages_are_public_warning %}
 
-If the default publishing source exists in your repository, {% data variables.product.prodname_pages %} will automatically publish a site from that source. The default publishing source for user and organization sites is the root of the default branch for the repository. The default publishing source for project sites is the root of the `gh-pages` branch.
+{% data reusables.pages.pages-about-publishing-source %}
 
-If you want to keep the source files for your site in a different location, you can change the publishing source for your site. You can publish your site from any branch in the repository, either from the root of the repository on that branch, `/`, or from the `/docs` folder on that branch. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)."
-
-If you choose the `/docs` folder of any branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% ifversion fpt or ghec %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% ifversion fpt or ghec %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. For more information about _CNAME_ files, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}
+For more information, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
 
 {% ifversion ghec %}
 ## Limitations for {% data variables.product.prodname_emus %}
@@ -93,10 +89,22 @@ For more information about {% data variables.product.prodname_emus %}, see "[Abo
 
 ## Static site generators
 
-{% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. We recommend Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
+{% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server.
+
+{% ifversion pages-custom-workflow %}
+
+If you use a custom build process or a static site generator other than Jekyll, you can write a {% data variables.product.prodname_actions %} to build and publish your site. {% data variables.product.product_name %} provides starter workflows for several static site generators. For more information, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
+
+If you publish your site from a source branch, {% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, we recommend that you write a {% data variables.product.prodname_actions %} to build and publish your site instead. Otherwise, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally.
+
+{% else %}
+
+We recommend Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
 
 {% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally.
 
+{% endif %}
+
 {% data variables.product.prodname_pages %} does not support server-side languages such as PHP, Ruby, or Python.
 
 ## Limits on use of {% data variables.product.prodname_pages %}
@@ -117,7 +125,7 @@ In addition, your use of {% data variables.product.prodname_pages %} is subject
   - Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB.
 {% ifversion fpt or ghec %}
   - {% data variables.product.prodname_pages %} sites have a *soft* bandwidth limit of 100 GB per month.
-  - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour.
+  - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour.{% ifversion pages-custom-workflow %} This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow {% endif %}
 
 If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.contact_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs.
 
diff --git a/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
index 6f568026a7..af19845c4e 100644
--- a/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
+++ b/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
@@ -13,12 +13,21 @@ versions:
 topics:
   - Pages
 shortTitle: Add theme to a Pages site
+permissions: People with admin permissions for a repository can use the theme chooser to add a theme to a {% data variables.product.prodname_pages %} site.
 ---
 
-People with admin permissions for a repository can use the theme chooser to add a theme to a {% data variables.product.prodname_pages %} site.
-
 ## About the theme chooser
 
+{% ifversion pages-custom-workflow %}
+
+{% note %}
+
+**Note**: The Jekyll theme chooser is not supported for {% data variables.product.prodname_pages %} sites that are published with a custom {% data variables.product.prodname_actions %} workflow. If you build your site with Jekyll and publish your site with a custom {% data variables.product.prodname_actions %} workflow, you can add a theme by editing the `_config.yml` file. For more information, 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)."
+
+{% endnote %}
+
+{% endif %}
+
 The theme chooser adds a Jekyll theme to your repository. For more information about Jekyll, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
 
 How the theme chooser works depends on whether your repository is public or private.
diff --git a/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
index 6b64409e5d..bf76deca2f 100644
--- a/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
+++ b/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
 title: Configuring a publishing source for your GitHub Pages site
-intro: 'If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your site from a different branch or folder.'
+intro: '{% ifversion pages-custom-workflow %}You can configure your {% data variables.product.prodname_pages %} site to publish when changes are pushed to a specific branch, or you can write a {% data variables.product.prodname_actions %} workflow to publish your site.{% else%}If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your site from a different branch or folder.{% endif %}'
 redirect_from:
   - /articles/configuring-a-publishing-source-for-github-pages
   - /articles/configuring-a-publishing-source-for-your-github-pages-site
@@ -17,23 +17,33 @@ topics:
 shortTitle: Configure publishing source
 ---
 
-For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)."
+## About publishing sources
 
-## Choosing a publishing source
+{% data reusables.pages.pages-about-publishing-source %}
 
-Before you configure a publishing source, make sure the branch you want to use as your publishing source already exists in your repository.
+{% data reusables.pages.private_pages_are_public_warning %}
 
+## Publishing from a branch
+
+1. Make sure the branch you want to use as your publishing source already exists in your repository.
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
+{% ifversion pages-custom-workflow %}
+1. Under "Build and deployment", under "Source", select **Deploy from a branch**.
+1. Under "Build and deployment", under "Branch", use the **None** or **Branch** drop-down menu and select a publishing source.
+
+   ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
+{% else %}
 3. Under "{% data variables.product.prodname_pages %}", use the **None** or **Branch** drop-down menu and select a publishing source.
   ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
+{% endif %}
 4. Optionally, use the drop-down menu to select a folder for your publishing source.
   ![Drop-down menu to select a folder for publishing source](/assets/images/help/pages/publishing-source-folder-drop-down.png)
 5. Click **Save**.
   ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png)
 
-## Troubleshooting publishing problems with your {% data variables.product.prodname_pages %} site
+### Troubleshooting publishing from a branch
 
 {% data reusables.pages.admin-must-push %}
 
@@ -52,3 +62,45 @@ To find potential errors with either the build or deployment, you can check the
 {% endnote %}
 
 {% endif %}
+
+{% ifversion pages-custom-workflow %}
+
+## Publishing with a custom {% data variables.product.prodname_actions %} workflow
+
+{% data reusables.pages.pages-custom-workflow-beta %}
+
+To configure your site to publish with {% data variables.product.prodname_actions %}:
+
+{% data reusables.pages.navigate-site-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+1. Under "Build and deployment", under "Source", select **GitHub Actions**.
+1. {% data variables.product.product_name %} will suggest several starter workflows. If you already have a workflow to publish your site, you can skip this step. Otherwise, choose one of the options to create a {% data variables.product.prodname_actions %} workflow. For more information about creating your custom workflow, see "[Creating a custom {% data variables.product.prodname_actions %} workflow to publish your site](#creating-a-custom-github-actions-workflow-to-publish-your-site)."
+
+   {% data variables.product.prodname_pages %} does not associate a specific workflow to the {% data variables.product.prodname_pages %} settings. However, the {% data variables.product.prodname_pages %} settings will link to the workflow run that most recently deployed your site.
+
+### Creating a custom {% data variables.product.prodname_actions %} workflow to publish your site
+
+For more information about {% data variables.product.prodname_actions %}, see "[Actions](/actions)."
+
+When you configure your site to publish with {% data variables.product.prodname_actions %}, {% data variables.product.product_name %} will suggest starter workflows for common publishing scenarios. The general flow of a workflow is to:
+
+1. Trigger whenever there is a push to the default branch of the repository or whenever a pull request that targets the default branch is opened, reopened, or updated.
+1. Use the [`actions/checkout`](https://github.com/actions/checkout) action to check out the repository contents.
+1. If required by your site, build any static site files.
+1. Use the [`actions/upload-pages-artifact`](https://github.com/actions/upload-pages-artifact) action to upload the static files as an artifact.
+1. If the workflow was triggered by a push to the default branch, use the [`actions/deploy-pages`](https://github.com/actions/deploy-pages) action to deploy the artifact. This step is skipped if the workflow was triggered by a pull request.
+
+The starter workflows use a deployment environment called `github-pages`. If your repository does not already include an environment called `github-pages`, the environment will be created automatically. We recommend that you add an environment protection rule so that only the default branch can deploy to this environment. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment)."
+
+{% note %}
+
+**Note**: A `CNAME` file in your repository file does not automatically add or remove a custom domain. Instead, you must configure the custom domain through your repository settings or through the API. For more information, see "[Managing a custom domain for your GitHub Pages site](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" and the [Pages API reference documentation](/rest/pages#update-information-about-a-github-pages-site).
+
+{% endnote %}
+
+### Troubleshooting publishing with a custom {% data variables.product.prodname_actions %} workflow
+
+For information about how to troubleshoot your {% data variables.product.prodname_actions %} workflow, see "[About monitoring and troubleshooting](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)."
+
+{% endif %}
diff --git a/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
index aa9f174bf4..4c6ebdd4e5 100644
--- a/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
+++ b/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
@@ -41,14 +41,12 @@ shortTitle: Create a GitHub Pages site
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.decide-publishing-source %}
-3. If your chosen publishing source already exists, navigate to the publishing source. If your chosen publishing source doesn't exist, create the publishing source.
-4. In the root of the publishing source, create a new file called `index.md` that contains the content you want to display on the main page of your site.
+1. Create the entry file for your site. {% data variables.product.prodname_pages %} will look for an `index.html`, `index.md`, or `README.md` file as the entry file for your site.
 
-  {% tip %}
+   {% ifversion pages-custom-workflow %}If your publishing source is a branch and folder, the entry file must be at the top level of the source folder on the source branch. For example, if your publishing source is the `/docs` folder on the `main` branch, your entry file must be located in the `/docs` folder on a branch called `main`.
 
-  **Tip:** If `index.html` is present, this will be used instead of `index.md`. If neither `index.html` nor `index.md` are present, `README.md` will be used.
-
-  {% endtip %}
+   If your publishing source is a {% data variables.product.prodname_actions %} workflow, the artifact that you deploy must include the entry file at the top level of the artifact. Instead of adding the entry file to your repository, you may choose to have your {% data variables.product.prodname_actions %} workflow generate your entry file when the workflow runs.{% else %}
+   The entry file must be at the top level of your chosen publishing source. For example, if your publishing source is the `/docs` folder on the `main` branch, your entry file must be located in the `/docs` folder on a branch called `main`.{% endif %}
 {% data reusables.pages.configure-publishing-source %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
diff --git a/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
index bcc60251c3..372f4d6627 100644
--- a/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
+++ b/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
@@ -20,6 +20,18 @@ topics:
 shortTitle: Unpublish Pages site
 ---
 
+{% ifversion pages-custom-workflow %}
+
+When you unpublish your site, the site will no longer be available. Any existing repository settings or content will not be affected.
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Under **{% data variables.product.prodname_pages %}**, next to the **Your site is live at** message, click {% octicon "kebab-horizontal" aria-label="the horizontal kebab icon" %}.
+1. In the menu that appears, select **Unpublish site**.
+
+   ![Drop down menu to unpublish site](/assets/images/help/pages/unpublish-site.png)
+
+{% else %}
+
 ## Unpublishing a project site
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -36,3 +48,5 @@ shortTitle: Unpublish Pages site
 {% data reusables.repositories.navigate-to-repo %}
 2. Delete the branch that you're using as a publishing source, or delete the entire repository. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" and "[Deleting a repository](/articles/deleting-a-repository)."
 {% data reusables.pages.update_your_dns_settings %}
+
+{% endif %}
\ No newline at end of file
diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
index c5b53d6108..b76538436f 100644
--- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
+++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
@@ -19,7 +19,7 @@ shortTitle: Jekyll build errors for Pages
 
 ## About Jekyll build errors
 
-Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% ifversion fpt or ghec %}
+{% ifversion pages-custom-workflow %}If you are publishing from a branch, sometimes{% else %}Sometimes,{% endif %} {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% ifversion fpt or ghec %}
 - The person who pushed the changes hasn't verified their email address. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %}
 - You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#machine-users)."
 - You're using a CI service that isn't configured to build your publishing source. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safe list. For more information, see "[Customizing the build](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" on Travis CI, or your CI service's documentation.
@@ -57,11 +57,15 @@ We recommend testing your site locally, which allows you to see build error mess
 
 ## Viewing Jekyll build error messages in your pull request
 
-When you create a pull request to update your publishing source on {% data variables.product.product_name %}, you can see build error messages on the **Checks** tab of the pull request. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
+{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you create a pull request to update your publishing source on {% data variables.product.product_name %}, you can see build error messages on the **Checks** tab of the pull request. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
+
+{% ifversion pages-custom-workflow %}If you are publishing with a custom {% data variables.product.prodname_actions %} workflow, in order to see build error messages in your pull request, you must configure your workflow to run on the `pull_request` trigger. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the `pull_request` event. This will allow you to see any build errors without deploying the changes from your pull request to your site. For more information, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows#pull_request)" and "[Expressions](/actions/learn-github-actions/expressions)."{% endif %}
 
 ## Viewing Jekyll build errors by email
 
-When you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %}
+{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %}
+
+{% ifversion pages-custom-workflow %}If you are publishing with a custom {% data variables.product.prodname_actions %} workflow, in order to receive emails about build errors in your pull request, you must configure your workflow to run on the `pull_request` trigger. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the `pull_request` event. This will allow you to see any build errors without deploying the changes from your pull request to your site. For more information, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows#pull_request)" and "[Expressions](/actions/learn-github-actions/expressions)."{% endif %}
 
 ## Viewing Jekyll build error messages in your pull request with a third-party CI service
 
diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
index 6f54aa966b..6db0e57c9e 100644
--- a/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
+++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
@@ -43,12 +43,12 @@ If Jekyll encounters an error building your {% data variables.product.prodname_p
 If you received a generic error message, check for common issues.
 - You're using unsupported plugins. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#plugins)."{% ifversion fpt or ghec %}
 - Your repository has exceeded our repository size limits. For more information, see "[What is my disk quota?](/articles/what-is-my-disk-quota)"{% endif %}
-- You changed the `source` setting in your *_config.yml* file. {% data variables.product.prodname_pages %} overrides this setting during the build process.
-- A filename in your publishing source contains a colon (`:`) which is not supported.
+- You changed the `source` setting in your *_config.yml* file. {% ifversion pages-custom-workflow %}If you publish your site from a branch, {% endif %}{% data variables.product.prodname_pages %} overrides this setting during the build process.
+- A filename in your published files contains a colon (`:`) which is not supported.
 
 If you received a specific error message, review the troubleshooting information for the error message below.
 
-After you've fixed any errors, push the changes to your site's publishing source to trigger another build on {% data variables.product.product_name %}.
+{% ifversion pages-custom-workflow %}After you've fixed any errors, trigger another build by pushing the changes to your site's source branch (if you are publishing from a branch) or by triggering your custom {% data variables.product.prodname_actions %} workflow (if you are publishing with {% data variables.product.prodname_actions %}).{% else %}After you've fixed any errors, push the changes to your site's publishing source to trigger another build on {% data variables.product.product_name %}.{% endif %}
 
 ## Config file error
 
@@ -74,7 +74,7 @@ This error means that your code references a file that doesn't exist in your *_i
 
 ## File is a symlink
 
-This error means that your code references a symlinked file that does not exist in the publishing source for your site.
+This error means that your code references a symlinked file that does not exist in the published files for your site.
 
 {% data reusables.pages.search-for-includes %} If any of the files you've referenced are symlinked, copy or move the files into the *_includes* directory.
 
@@ -162,9 +162,9 @@ To troubleshoot, remove the `relative_permalinks` line from your *_config.yml* f
 
 ## Symlink does not exist within your site's repository
 
-This error means that your site includes a symbolic link (symlink) that does not exist in the publishing source for your site. For more information about symlinks, see "[Symbolic link](https://en.wikipedia.org/wiki/Symbolic_link)" on Wikipedia.
+This error means that your site includes a symbolic link (symlink) that does not exist in the published files for your site. For more information about symlinks, see "[Symbolic link](https://en.wikipedia.org/wiki/Symbolic_link)" on Wikipedia.
 
-To troubleshoot, determine if the file in the error message is used to build your site. If not, or if you don't want the file to be a symlink, delete the file. If the symlinked file is necessary to build your site, make sure the file or directory the symlink references is in the publishing source for your site. To include external assets, consider using {% ifversion fpt or ghec %}`git submodule` or {% endif %}a third-party package manager such as [Bower](https://bower.io/).{% ifversion fpt or ghec %} For more information, see "[Using submodules with {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)."{% endif %}
+To troubleshoot, determine if the file in the error message is used to build your site. If not, or if you don't want the file to be a symlink, delete the file. If the symlinked file is necessary to build your site, make sure the file or directory the symlink references is in the published files for your site. To include external assets, consider using {% ifversion fpt or ghec %}`git submodule` or {% endif %}a third-party package manager such as [Bower](https://bower.io/).{% ifversion fpt or ghec %} For more information, see "[Using submodules with {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)."{% endif %}
 
 ## Syntax error in 'for' loop
 
diff --git a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
index 8c66c8d326..1f2a9126d6 100644
--- a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
+++ b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Disabling project boards in a repository
-intro: Repository administrators can turn off project boards for a repository if you or your team manages work differently.
+title: Disabling {% data variables.projects.projects_v1_boards %} in a repository
+intro: Repository administrators can turn off {% data variables.projects.projects_v1_boards %} for a repository if you or your team manages work differently.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-a-repository
   - /articles/disabling-project-boards-in-a-repository
@@ -13,13 +13,14 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Disable project boards
+shortTitle: Disable {% data variables.projects.projects_v1_boards %}
+allowTitleToDifferFromFilename: true
 ---
-When you disable project boards, you will no longer see project board information in timelines or [audit logs](/articles/reviewing-your-security-log/).
+When you disable {% data variables.projects.projects_v1_boards %}, you will no longer see {% data variables.projects.projects_v1_board %} information in timelines or [audit logs](/articles/reviewing-your-security-log/).
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 3. Under "Features," unselect the **Projects** checkbox.
   ![Remove Projects checkbox](/assets/images/help/projects/disable-projects-checkbox.png)
 
-After project boards are disabled, existing project boards are inaccessible at their previous URLs. {% data reusables.organizations.disable_project_board_results %}
+After {% data variables.projects.projects_v1_boards %} are disabled, existing {% data variables.projects.projects_v1_boards %} are inaccessible at their previous URLs. {% data reusables.organizations.disable_project_board_results %}
diff --git a/content/rest/projects/cards.md b/content/rest/projects/cards.md
index fb5bef027c..93276cffe8 100644
--- a/content/rest/projects/cards.md
+++ b/content/rest/projects/cards.md
@@ -1,8 +1,8 @@
 ---
-title: Project board cards
+title: '{% data variables.product.prodname_project_v1_caps %} cards'
 shortTitle: Cards
 allowTitleToDifferFromFilename: true
-intro: The Project board cards API lets you create and manage cards on a project board.
+intro: 'The {% data variables.product.prodname_project_v1 %} cards API lets you create and manage cards on a {% data variables.projects.projects_v1_board %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/content/rest/projects/collaborators.md b/content/rest/projects/collaborators.md
index cfb1772eca..381ae8e2db 100644
--- a/content/rest/projects/collaborators.md
+++ b/content/rest/projects/collaborators.md
@@ -1,8 +1,8 @@
 ---
-title: Project board collaborators
+title: '{% data variables.product.prodname_project_v1_caps %} collaborators'
 shortTitle: Collaborators
 allowTitleToDifferFromFilename: true
-intro: The Project board collaborators API lets you manage collaborators on a project board.
+intro: 'The {% data variables.product.prodname_project_v1 %} collaborators API lets you manage collaborators on a {% data variables.projects.projects_v1_board %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/content/rest/projects/columns.md b/content/rest/projects/columns.md
index 9d33009069..2f343bc7f7 100644
--- a/content/rest/projects/columns.md
+++ b/content/rest/projects/columns.md
@@ -1,8 +1,8 @@
 ---
-title: Project board columns
+title: '{% data variables.product.prodname_project_v1_caps %} columns'
 shortTitle: Columns
 allowTitleToDifferFromFilename: true
-intro: The Project board columns API lets you create and manage columns on a project board.
+intro: 'The {% data variables.product.prodname_project_v1 %} columns API lets you create and manage columns on a {% data variables.projects.projects_v1_board %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/content/rest/projects/index.md b/content/rest/projects/index.md
index 629b117bec..7064fbb384 100644
--- a/content/rest/projects/index.md
+++ b/content/rest/projects/index.md
@@ -1,6 +1,6 @@
 ---
-title: Projects
-intro: 'The Projects API lets you create, list, update, delete and customize projects in a repository.'
+title: '{% data variables.product.prodname_projects_v1_caps %}'
+intro: 'The {% data variables.product.prodname_projects_v1 %} API lets you create, list, update, delete and customize {% data variables.projects.projects_v1_boards %}.'
 redirect_from:
   - /v3/projects
   - /rest/reference/projects
@@ -12,6 +12,7 @@ versions:
 topics:
   - API
 miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
 children:
   - /projects
   - /cards
diff --git a/content/rest/projects/projects.md b/content/rest/projects/projects.md
index f8af74a412..79c2aaa6b1 100644
--- a/content/rest/projects/projects.md
+++ b/content/rest/projects/projects.md
@@ -1,8 +1,8 @@
 ---
-title: Project boards
+title: '{% data variables.product.prodname_projects_v1_caps %}'
 shortTitle: Boards
 allowTitleToDifferFromFilename: true
-intro: The Project boards API lets you create and manage projects in a repository.
+intro: 'The {% data variables.product.prodname_projects_v1 %} API lets you create and manage {% data variables.projects.projects_v1_boards %} in a repository.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/content/search-github/searching-on-github/finding-files-on-github.md b/content/search-github/searching-on-github/finding-files-on-github.md
index 2ea84afa2e..e247b94543 100644
--- a/content/search-github/searching-on-github/finding-files-on-github.md
+++ b/content/search-github/searching-on-github/finding-files-on-github.md
@@ -17,11 +17,13 @@ topics:
 
 **Tips:**
 
-- File finder results exclude some directories like `build`, `log`, `tmp`, and `vendor`. To search for files within these directories, use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename).
+- By default, file finder results exclude some directories like `build`, `log`, `tmp`, and `vendor`. To search for files in these directories, use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename).{% ifversion file-finder-exclusion-controls %} Alternatively, you can customize which directories are excluded by default [using a `.gitattributes` file](#customizing-excluded-files).{% endif %}
 - You can also open the file finder by pressing `t` on your keyboard. For more information, see "[Keyboard shortcuts](/articles/keyboard-shortcuts)."
 
 {% endtip %}
 
+## Using the file finder
+
 {% data reusables.repositories.navigate-to-repo %}
 2. Above the list of files, click **Go to file**.
 ![Find file button](/assets/images/help/search/find-file-button.png)
@@ -29,6 +31,38 @@ topics:
 ![Find file search field](/assets/images/help/search/find-file-search-field.png)
 4. In the list of results, click the file you wanted to find.
 
+{% ifversion file-finder-exclusion-controls %}
+
+## Customizing excluded files
+
+By default, file finder results do not include files in the following directories if they exist at your repository root:
+
+ - `.git`
+ - `.hg`
+ - `.sass-cache`
+ - `.svn`
+ - `build`
+ - `dot_git`
+ - `log`
+ - `tmp`
+ - `vendor`
+
+You can override these default exclusions using a `.gitattributes` file.
+
+To do this, create or update a file called `.gitattributes` in your repository root, setting the [`linguist-generated`](https://github.com/github/linguist/blob/master/docs/overrides.md) attribute to `false` for each directory that should be included in file finder results.
+
+For example, the following `.gitattributes` file would cause files in the `build/` directory to be available to the file finder:
+
+```
+build/** linguist-generated=false
+```
+
+Note that this override requires the use of the recursive glob pattern (`**`). For more information, see "[pattern format](https://git-scm.com/docs/gitignore#_pattern_format)" in the Git documentation. More complex overrides of subdirectories within excluded-by-default directories are not supported.
+
+{% endif %}
+
 ## Further reading
 
-- "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)"
+- "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)"{% ifversion file-finder-exclusion-controls %}
+- "[Customizing how changed files appear on GitHub](/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github)"
+- [`.gitattributes`](https://git-scm.com/docs/gitattributes) in the Git documentation{% endif %}
diff --git a/data/features/actions-stable-actor-ids.yml b/data/features/actions-stable-actor-ids.yml
new file mode 100644
index 0000000000..14ab57db8e
--- /dev/null
+++ b/data/features/actions-stable-actor-ids.yml
@@ -0,0 +1,7 @@
+# Issue 7387
+# Differentiating triggering actor from executing actor
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7387'
diff --git a/data/features/audit-data-retention-tab.yml b/data/features/audit-data-retention-tab.yml
new file mode 100644
index 0000000000..ae60adc527
--- /dev/null
+++ b/data/features/audit-data-retention-tab.yml
@@ -0,0 +1,5 @@
+# Reference #5104
+# Documentation for the "Audit data retention" tab in the enterprise audit log
+versions:
+  ghes: '>=3.4'
+  ghae: 'issue-5104'
diff --git a/data/features/dependency-review-action-licenses.yml b/data/features/dependency-review-action-licenses.yml
new file mode 100644
index 0000000000..ec85ab9be0
--- /dev/null
+++ b/data/features/dependency-review-action-licenses.yml
@@ -0,0 +1,4 @@
+# Reference: Issue #7486 Configuring the dependency review action - [Public Beta] for GHES
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/data/features/enable-git-events.yml b/data/features/enable-git-events.yml
new file mode 100644
index 0000000000..29ac43099f
--- /dev/null
+++ b/data/features/enable-git-events.yml
@@ -0,0 +1,5 @@
+# Reference: #7283
+# Documentation for enabling Git events in the audit log
+versions:
+  ghes: '>=3.5'
+  ghae: 'issue-7283'
diff --git a/data/features/file-finder-exclusion-controls.yml b/data/features/file-finder-exclusion-controls.yml
new file mode 100644
index 0000000000..3c23123536
--- /dev/null
+++ b/data/features/file-finder-exclusion-controls.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #7579 - Improved file finder exclusion controls
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7579'
diff --git a/data/features/git-events-audit-log.yml b/data/features/git-events-audit-log.yml
new file mode 100644
index 0000000000..1c2fba042a
--- /dev/null
+++ b/data/features/git-events-audit-log.yml
@@ -0,0 +1,6 @@
+# Reference: #6724
+# Documentation for Git events in the audit log
+versions:
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6724'
diff --git a/data/features/pages-custom-workflow.yml b/data/features/pages-custom-workflow.yml
new file mode 100644
index 0000000000..94ab08b480
--- /dev/null
+++ b/data/features/pages-custom-workflow.yml
@@ -0,0 +1,5 @@
+# Issue 7066
+# Publishing Pages via custom Actions workflow
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/data/features/projects-v1.yml b/data/features/projects-v1.yml
new file mode 100644
index 0000000000..c217fc003d
--- /dev/null
+++ b/data/features/projects-v1.yml
@@ -0,0 +1,8 @@
+# Issue 6980
+# Projects (classic)
+# n.b. /managing-project-boards/copying-a-project-board.md retains ghec/fpt versioning.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
diff --git a/data/features/projects-v2.yml b/data/features/projects-v2.yml
new file mode 100644
index 0000000000..54ea4f28ad
--- /dev/null
+++ b/data/features/projects-v2.yml
@@ -0,0 +1,6 @@
+# Issue 6980
+# ProjectV2 GA
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-6980'
diff --git a/data/release-notes/enterprise-server/3-5/0-rc1.yml b/data/release-notes/enterprise-server/3-5/0-rc1.yml
index f7658099b3..378a8b6706 100644
--- a/data/release-notes/enterprise-server/3-5/0-rc1.yml
+++ b/data/release-notes/enterprise-server/3-5/0-rc1.yml
@@ -291,7 +291,7 @@ sections:
           - `git.fetch`
           - `git.push`
           
-          Due 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)."
+          Due 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 "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise#managing-git-events-in-the-audit-log)."
 
     - heading: Improvements to CODEOWNERS
       notes:
diff --git a/data/release-notes/enterprise-server/3-5/0.yml b/data/release-notes/enterprise-server/3-5/0.yml
index 99a5a712c5..d4c9329d37 100644
--- a/data/release-notes/enterprise-server/3-5/0.yml
+++ b/data/release-notes/enterprise-server/3-5/0.yml
@@ -284,8 +284,8 @@ sections:
           - `git.fetch`
           - `git.push`
           
-          Due 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)."
-
+          Due 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 "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise#managing-git-events-in-the-audit-log)."
+          
     - heading: Improvements to CODEOWNERS
       notes:
         # https://github.com/github/releases/issues/1994
diff --git a/data/reusables/audit_log/audit-data-retention-tab.md b/data/reusables/audit_log/audit-data-retention-tab.md
new file mode 100644
index 0000000000..2f1850c4ef
--- /dev/null
+++ b/data/reusables/audit_log/audit-data-retention-tab.md
@@ -0,0 +1,3 @@
+1. Under "Audit log", click **Audit Data Retention**.
+
+   ![Screenshot of the "Audit Data Retention" tab](/assets/images/help/enterprises/audit-data-retention-tab.png)
\ No newline at end of file
diff --git a/data/reusables/audit_log/audit-log-action-categories.md b/data/reusables/audit_log/audit-log-action-categories.md
index 48be014db5..50e40c031d 100644
--- a/data/reusables/audit_log/audit-log-action-categories.md
+++ b/data/reusables/audit_log/audit-log-action-categories.md
@@ -61,7 +61,6 @@
 | `external_identity` | Contains activities related to a user in an Okta group.
 {%- endif %}
 | `gist` | Contains activities related to Gists.
-| `git` | Contains activities related to Git events.
 | `hook` | Contains activities related to webhooks.
 | `integration` | Contains activities related to integrations in an account.
 | `integration_installation` | Contains activities related to integrations installed in an account.
diff --git a/data/reusables/audit_log/git-events-not-in-search-results.md b/data/reusables/audit_log/git-events-not-in-search-results.md
new file mode 100644
index 0000000000..7f54d1e816
--- /dev/null
+++ b/data/reusables/audit_log/git-events-not-in-search-results.md
@@ -0,0 +1,7 @@
+{% ifversion git-events-audit-log %}
+{% note %}
+
+**Note:** Git events are not included in search results.
+
+{% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/data/reusables/audit_log/retention-periods.md b/data/reusables/audit_log/retention-periods.md
index dbed08d376..5d47a7424c 100644
--- a/data/reusables/audit_log/retention-periods.md
+++ b/data/reusables/audit_log/retention-periods.md
@@ -1,3 +1,3 @@
-The audit log lists events triggered by activities that affect your enterprise{% ifversion not ghec %}. Audit logs for {% data variables.product.product_name %} are retained indefinitely.{% else %} within the current month and up to the previous six months. The audit log retains Git events for seven days.{% endif %}
+The audit log lists events triggered by activities that affect your enterprise{% ifversion not ghec %}. Audit logs for {% data variables.product.product_name %} are retained indefinitely{% ifversion audit-data-retention-tab %}, unless an enterprise owner configured a different retention period. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise)."{% else %}.{% endif %}{% else %} within the current month and up to the previous six months. The audit log retains Git events for seven days.{% endif %}
 
 {% data reusables.audit_log.only-three-months-displayed %}
diff --git a/data/reusables/copilot/dotcom-settings.md b/data/reusables/copilot/dotcom-settings.md
index 49c4afdfd7..1ec55e6348 100644
--- a/data/reusables/copilot/dotcom-settings.md
+++ b/data/reusables/copilot/dotcom-settings.md
@@ -2,7 +2,9 @@
 
 Once you have an active {% data variables.product.prodname_copilot %} trial or subscription, you can adjust {% data variables.product.prodname_copilot %} settings for your personal account on {% data variables.product.prodname_dotcom %} in the [{% data variables.product.prodname_copilot %} settings](https://github.com/settings/copilot). The settings apply anywhere that you use {% data variables.product.prodname_copilot %}. You can configure the suggestions that {% data variables.product.prodname_copilot %} offers and how {% data variables.product.company_short %} uses your telemetry data.
 
-### Enabling or disabling duplication detection
+## Enabling or disabling duplication detection
+
+{% data variables.product.prodname_copilot %} includes a filter which detects code suggestions matching public code on {% data variables.product.prodname_dotcom %}. You can choose to enable or disable the filter. When the filter is enabled, {% data variables.product.prodname_copilot %} checks code suggestions with their surrounding code of about 150 characters against public code on {% data variables.product.prodname_dotcom %}. If there is a match or near match, the suggestion will not be shown to you.
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.copilot-settings %}
@@ -10,12 +12,16 @@ Once you have an active {% data variables.product.prodname_copilot %} trial or s
   ![Screenshot of duplication detection option](/assets/images/help/copilot/duplication-detection.png)
 {% data reusables.copilot.save-settings %}
 
-### Enabling or disabling telemetry
+## Enabling or disabling telemetry
 
-You can configure how {% data variables.product.prodname_copilot %} uses your data. For more information about data that {% data variables.product.prodname_copilot %} may collect depending on your telemetry settings, see "[{% data variables.product.company_short %} Terms for Additional Products and Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)."
+You can choose whether your code snippets are collected and retained by GitHub and further processed and shared with Microsoft and OpenAI by adjusting your user settings. For more information about data that {% data variables.product.prodname_copilot %} may collect depending on your telemetry settings, see "[{% data variables.product.company_short %} Terms for Additional Products and Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)" and the [{% data variables.product.prodname_copilot %} privacy FAQ](https://github.com/features/copilot/#faq-privacy).
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.copilot-settings %}
 1. To allow or prevent {% data variables.product.prodname_dotcom %} using your telemetry data, select or deselect **Allow {% data variables.product.prodname_dotcom %} to use my code snippets for product improvements**.
   ![Screenshot of telemetry option](/assets/images/help/copilot/telemetry-option.png)
 {% data reusables.copilot.save-settings %}
+
+## Further reading
+
+- [{% data variables.product.prodname_copilot %} FAQ](https://github.com/features/copilot/#faq)
\ No newline at end of file
diff --git a/data/reusables/dependency-review/action-enterprise.md b/data/reusables/dependency-review/action-enterprise.md
new file mode 100644
index 0000000000..93908578c8
--- /dev/null
+++ b/data/reusables/dependency-review/action-enterprise.md
@@ -0,0 +1,3 @@
+{% ifversion ghes or ghae %}
+Enterprise owners and people with admin access to a repository can add the {% data variables.product.prodname_dependency_review_action %} to their enterprise and repository, respectively.
+{% endif %}
\ No newline at end of file
diff --git a/data/reusables/education/about-github-community-exchange-intro.md b/data/reusables/education/about-github-community-exchange-intro.md
new file mode 100644
index 0000000000..0371445ce6
--- /dev/null
+++ b/data/reusables/education/about-github-community-exchange-intro.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_community_exchange %} is a student community within the {% data variables.product.prodname_global_campus %} portal. As a student, it's a place where you can get exposure for your project and discover other student repositories in need of collaborators and maintainers.
\ No newline at end of file
diff --git a/data/reusables/education/about-github-education-link.md b/data/reusables/education/about-github-education-link.md
index c94fca9898..59d776a16f 100644
--- a/data/reusables/education/about-github-education-link.md
+++ b/data/reusables/education/about-github-education-link.md
@@ -1,3 +1,3 @@
-As a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_global_campus %}. {% data variables.product.prodname_global_campus %} is a portal that allows the GitHub Education Community to access their education benefits—all in one place! The {% data variables.product.prodname_global_campus %} portal includes access to {% data variables.product.prodname_education_community_with_url %}, industry tools used by professional developers, events, [Campus TV](https://www.twitch.tv/githubeducation) content, {% data variables.product.prodname_classroom_with_url %}, and other exclusive features to help students and teachers shape the next generation of software development.
+As a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_global_campus %}. {% data variables.product.prodname_global_campus %} is a portal that allows the GitHub Education Community to access their education benefits—all in one place! The {% data variables.product.prodname_global_campus %} portal includes access to {% data variables.product.prodname_education_community_with_url %}, industry tools used by professional developers, events, [Campus TV](https://www.twitch.tv/githubeducation) content, {% data variables.product.prodname_classroom_with_url %}, {% data variables.product.prodname_community_exchange %}, and other exclusive features to help students and teachers shape the next generation of software development.
 
 Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_campus_program %} school. For more information, see "[About {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)."
diff --git a/data/reusables/education/access-github-community-exchange.md b/data/reusables/education/access-github-community-exchange.md
new file mode 100644
index 0000000000..b482e8be96
--- /dev/null
+++ b/data/reusables/education/access-github-community-exchange.md
@@ -0,0 +1,7 @@
+To access {% data variables.product.prodname_community_exchange %}, visit your {% data variables.product.prodname_global_campus %} dashboard at https://education.github.com.
+
+If you're a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_community_exchange %} within {% data variables.product.prodname_global_campus %}.
+
+- If you’re a student and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [student application form]( https://education.github.com/discount_requests/student_application). For more information, see "[About GitHub Education for students](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students)."
+
+- If you’re an educator and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [teacher application form]( https://education.github.com/discount_requests/teacher_application). For more information, see "[About GitHub Education for educators](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount)."
diff --git a/data/reusables/gated-features/code-scanning.md b/data/reusables/gated-features/code-scanning.md
index a42ea0458d..247c6f564a 100644
--- a/data/reusables/gated-features/code-scanning.md
+++ b/data/reusables/gated-features/code-scanning.md
@@ -1,7 +1,13 @@
-{% ifversion fpt %} {% data variables.product.prodname_code_scanning_capc %} is available for all public repositories. {% data variables.product.prodname_code_scanning_capc %} is also available in private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}.
-{%- elsif ghec %} {% data variables.product.prodname_code_scanning_capc %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
-{%- elsif ghes %}{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- ifversion fpt %}
+{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_code_scanning_capc %} is also available for private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghec %}
+{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. To use {% data variables.product.prodname_code_scanning %} in a private repository owned by an organization, you must have a license for {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghes %}
+{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories in {% data variables.product.product_name %}. This feature requires a license for {% data variables.product.prodname_GH_advanced_security %}.
+
 {%- elsif ghae %}
-{% data variables.product.prodname_code_scanning_capc %} is available as part of {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release.
-{%- else %}
-{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
+{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories in {% data variables.product.product_name %}. This is a {% data variables.product.prodname_GH_advanced_security %} feature (free during the beta release).
+
+{%- endif %} For more information, see "[GitHub's products](/articles/githubs-products)."
\ No newline at end of file
diff --git a/data/reusables/gated-features/copilot.md b/data/reusables/gated-features/copilot.md
index 012cabe648..4acb15a9e0 100644
--- a/data/reusables/gated-features/copilot.md
+++ b/data/reusables/gated-features/copilot.md
@@ -1 +1 @@
-{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_copilot %} is free to use for verified students and open source maintainers. If you are not a student or open source maintainer, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
+{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_copilot %} is free to use for verified students and maintainers of popular open source projects. If you are not a student or maintainer of a popular open source project, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
diff --git a/data/reusables/gated-features/historical-insights-for-projects.md b/data/reusables/gated-features/historical-insights-for-projects.md
new file mode 100644
index 0000000000..07502e255f
--- /dev/null
+++ b/data/reusables/gated-features/historical-insights-for-projects.md
@@ -0,0 +1 @@
+Historical charts are available with {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} for organizations. You can save unlimited charts in private projects with {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} for organizations and {% data variables.product.prodname_pro %} for users. Users and organizations using a public project can also save unlimited charts. Users and organizations using {% data variables.product.prodname_free_team %} or a legacy plan can save two charts in private projects.  {% data reusables.gated-features.more-info %}
\ No newline at end of file
diff --git a/data/reusables/pages/admin-must-push.md b/data/reusables/pages/admin-must-push.md
index 51bffec7fa..79f244c85a 100644
--- a/data/reusables/pages/admin-must-push.md
+++ b/data/reusables/pages/admin-must-push.md
@@ -1,5 +1,5 @@
 {% tip %}
 
-**Note**: If your site has not published automatically, make sure someone with admin permissions and a verified email address has pushed to the publishing source.
+**Note**: {% ifversion pages-custom-workflow %}If you are publishing from a branch and{% else %}If{% endif %} your site has not published automatically, make sure someone with admin permissions and a verified email address has pushed to the publishing source.
 
 {% endtip %}
diff --git a/data/reusables/pages/check-workflow-run.md b/data/reusables/pages/check-workflow-run.md
index f405c66434..f4f66b6f9f 100644
--- a/data/reusables/pages/check-workflow-run.md
+++ b/data/reusables/pages/check-workflow-run.md
@@ -1,5 +1,5 @@
 {% ifversion fpt %} 
-1. If your {% data variables.product.prodname_pages %} site is built from a public repository, it is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. For more information about how to view the workflow status, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+1. Unless your {% data variables.product.prodname_pages %} site is built from a private or internal repository and published from a branch, your site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information about how to view the workflow status, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
 
 {% note %}
 
diff --git a/data/reusables/pages/configure-publishing-source.md b/data/reusables/pages/configure-publishing-source.md
index c4b7859307..3ff7e4b4fd 100644
--- a/data/reusables/pages/configure-publishing-source.md
+++ b/data/reusables/pages/configure-publishing-source.md
@@ -1 +1 @@
-1. Configure your publishing source. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)."
+1. Configure your publishing source. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/articles/configuring-a-publishing-source-for-your-github-pages-site)."
diff --git a/data/reusables/pages/decide-publishing-source.md b/data/reusables/pages/decide-publishing-source.md
index 879cfc458d..0c62f3071d 100644
--- a/data/reusables/pages/decide-publishing-source.md
+++ b/data/reusables/pages/decide-publishing-source.md
@@ -1 +1 @@
-1. Decide which publishing source you want to use.  For more information, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)."
+1. Decide which publishing source you want to use. For more information, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
diff --git a/data/reusables/pages/navigate-publishing-source.md b/data/reusables/pages/navigate-publishing-source.md
index 674fc377b7..bf894dc49f 100644
--- a/data/reusables/pages/navigate-publishing-source.md
+++ b/data/reusables/pages/navigate-publishing-source.md
@@ -1 +1 @@
-1. Navigate to the publishing source for your site. For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)."
+1. Navigate to the publishing source for your site. For more information, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
diff --git a/data/reusables/pages/new-or-existing-repo.md b/data/reusables/pages/new-or-existing-repo.md
index 3555859b77..7c6738b6d8 100644
--- a/data/reusables/pages/new-or-existing-repo.md
+++ b/data/reusables/pages/new-or-existing-repo.md
@@ -1,4 +1,6 @@
-If your site is an independent project, you can create a new repository to store your site's source code. If your site is associated with an existing project, you can add the source code to that project's repository, in a `/docs` folder on the default branch or on a different branch. For example, if you're creating a site to publish documentation for a project that's already on {% data variables.product.product_name %}, you may want to store the source code for the site in the same repository as the project.
+You can either create a repository or choose an existing repository for your site.
+
+If you want to create a {% data variables.product.prodname_pages %} site for a repository where not all of the files in the repository are related to the site, you will be able to configure a publishing source for your site. For example, you can have a dedicated branch and folder to hold your site source files{% ifversion pages-custom-workflow %}, or you can use a custom {% data variables.product.prodname_actions %} workflow to build and deploy your site source files{% endif %}.
 
 {% ifversion fpt or ghec %}If the account that owns the repository uses {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_free_team %} for organizations, the repository must be public.{% endif %}
 
diff --git a/data/reusables/pages/pages-about-branch-source.md b/data/reusables/pages/pages-about-branch-source.md
new file mode 100644
index 0000000000..e84fc9f3ca
--- /dev/null
+++ b/data/reusables/pages/pages-about-branch-source.md
@@ -0,0 +1 @@
+You can specify which branch and folder to use as your publishing source. The source branch can be any branch in your repository, and the source folder can either be the root of the repository (`/`) on the source branch or a `/docs` folder on the source branch. Whenever changes are pushed to the source branch, the changes in the source folder will be published to your {% data variables.product.prodname_pages %} site.
diff --git a/data/reusables/pages/pages-about-publishing-source.md b/data/reusables/pages/pages-about-publishing-source.md
new file mode 100644
index 0000000000..a5ea80617b
--- /dev/null
+++ b/data/reusables/pages/pages-about-publishing-source.md
@@ -0,0 +1,13 @@
+{% ifversion pages-custom-workflow %}
+
+You can publish your site when changes are pushed to a specific branch, or you can write a {% data variables.product.prodname_actions %} workflow to publish your site.
+
+If you do not need any control over the build process for your site, we recommend that you publish your site when changes are pushed to a specific branch. {% data reusables.pages.pages-about-branch-source %}
+
+If you want to use a build process other than Jekyll or you do not want a dedicated branch to hold your compiled static files, we recommend that you write a {% data variables.product.prodname_actions %} workflow to publish your site. {% data variables.product.product_name %} provides starter workflows for common publishing scenarios to help you write your workflow.
+
+{% else %}
+
+Your {% data variables.product.prodname_pages %} site will publish whenever changes are pushed to a specific branch. {% data reusables.pages.pages-about-branch-source %}
+
+{% endif %}
diff --git a/data/reusables/pages/pages-custom-workflow-beta.md b/data/reusables/pages/pages-custom-workflow-beta.md
new file mode 100644
index 0000000000..5f5ce32eef
--- /dev/null
+++ b/data/reusables/pages/pages-custom-workflow-beta.md
@@ -0,0 +1,9 @@
+{% ifversion pages-custom-workflow %}
+
+{% note %}
+
+Note: Publishing your {% data variables.product.prodname_pages %} site with a custom {% data variables.product.prodname_actions %} workflow is in beta and subject to change.
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/data/reusables/pages/test-locally.md b/data/reusables/pages/test-locally.md
index f9ea9564dd..97781b816c 100644
--- a/data/reusables/pages/test-locally.md
+++ b/data/reusables/pages/test-locally.md
@@ -1 +1 @@
-Changes to your site are published automatically when the changes are merged into your site's publishing source. If you want to preview your changes first, you can make the changes locally instead of on {% data variables.product.product_name %}. Then, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)."
+{% ifversion pages-custom-workflow %}If you are publishing from a branch, changes{% else %}Changes{% endif %} to your site are published automatically when the changes are merged into your site's publishing source. {% ifversion pages-custom-workflow %}If you are publishing from a custom {% data variables.product.prodname_actions %} workflow, changes are published whenever your workflow is triggered (typically by a push to the default branch). {% endif %}If you want to preview your changes first, you can make the changes locally instead of on {% data variables.product.product_name %}. Then, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)."
diff --git a/data/reusables/project-management/automate-project-board-permissions.md b/data/reusables/project-management/automate-project-board-permissions.md
index 525f140e73..b6de4865ba 100644
--- a/data/reusables/project-management/automate-project-board-permissions.md
+++ b/data/reusables/project-management/automate-project-board-permissions.md
@@ -1 +1 @@
-To set up automatic workflows for a repository project board, you must have write access to the repository. Organization owners and members can configure automatic workflows on an organization-wide project board.
+To set up automatic workflows for a repository {% data variables.projects.projects_v1_board %}, you must have write access to the repository. Organization owners and members can configure automatic workflows on an organization-wide {% data variables.projects.projects_v1_board %}.
diff --git a/data/reusables/project-management/cascading-permissions.md b/data/reusables/project-management/cascading-permissions.md
index 8b84f9e394..d45274e43c 100644
--- a/data/reusables/project-management/cascading-permissions.md
+++ b/data/reusables/project-management/cascading-permissions.md
@@ -1 +1 @@
-If a person has multiple avenues of access to an organization project board (individually, through a team, or as an organization member), the highest project board permission level overrides lower permission levels.
+If a person has multiple avenues of access to an organization {% data variables.projects.projects_v1_board %} (individually, through a team, or as an organization member), the highest {% data variables.projects.projects_v1_board %} permission level overrides lower permission levels.
diff --git a/data/reusables/project-management/click-menu.md b/data/reusables/project-management/click-menu.md
index 0fd91f018d..e95bfdceb8 100644
--- a/data/reusables/project-management/click-menu.md
+++ b/data/reusables/project-management/click-menu.md
@@ -1 +1 @@
-1. On the top-right side of the project board, click {% octicon "three-bars" aria-label="The three-bars octicon" %} **Menu**.
+1. On the top-right side of the {% data variables.projects.projects_v1_board %}, click {% octicon "three-bars" aria-label="The three-bars octicon" %} **Menu**.
diff --git a/data/reusables/project-management/copy-project-boards.md b/data/reusables/project-management/copy-project-boards.md
index ce3a80ab6c..118eb3c599 100644
--- a/data/reusables/project-management/copy-project-boards.md
+++ b/data/reusables/project-management/copy-project-boards.md
@@ -1,3 +1,3 @@
 {% ifversion fpt or ghec %}
-You can also copy a project board to reuse its customizations for similar projects. For more information, see "[Copying a project board](/articles/copying-a-project-board)."
+You can also copy a {% data variables.projects.projects_v1_board %} to reuse its customizations for similar projects. For more information, see "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)."
 {% endif %}
diff --git a/data/reusables/project-management/edit-in-project.md b/data/reusables/project-management/edit-in-project.md
index 1c83261282..112ef81842 100644
--- a/data/reusables/project-management/edit-in-project.md
+++ b/data/reusables/project-management/edit-in-project.md
@@ -1 +1 @@
-You can view and make lightweight edits to issues and pull requests within your project board by clicking on the issue or pull request's title.
+You can view and make lightweight edits to issues and pull requests within your {% data variables.projects.projects_v1_board %} by clicking on the issue or pull request's title.
diff --git a/data/reusables/project-management/link-repos-to-project-board.md b/data/reusables/project-management/link-repos-to-project-board.md
index 0a72db53b6..6bce91fd71 100644
--- a/data/reusables/project-management/link-repos-to-project-board.md
+++ b/data/reusables/project-management/link-repos-to-project-board.md
@@ -1 +1 @@
-You can link up to twenty-five repositories to your organization or user-owned project board. Linking repositories makes it easier to add issues and pull requests from those repositories to your project board using **{% octicon "plus" aria-label="The Plus icon" %} Add cards** or from the issue or pull requests sidebar.
+You can link up to twenty-five repositories to your organization or user-owned {% data variables.projects.projects_v1_board %}. Linking repositories makes it easier to add issues and pull requests from those repositories to your {% data variables.projects.projects_v1_board %} using **{% octicon "plus" aria-label="The Plus icon" %} Add cards** or from the issue or pull requests sidebar.
diff --git a/data/reusables/project-management/project-board-permissions.md b/data/reusables/project-management/project-board-permissions.md
index 47552a0bd3..cbb4e53a66 100644
--- a/data/reusables/project-management/project-board-permissions.md
+++ b/data/reusables/project-management/project-board-permissions.md
@@ -1,3 +1,3 @@
-- **Read**, which gives people permission to view a project board.
-- **Write**, which gives people permission to view a project board, link repositories to a project board, and interact with a project board. For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
-- **Admin**, which gives people permission to view a project board, interact with a project board, manage project board settings, and manage other people's access to the project board.
+- **Read**, which gives people permission to view a {% data variables.projects.projects_v1_board %}.
+- **Write**, which gives people permission to view a {% data variables.projects.projects_v1_board %}, link repositories to a {% data variables.projects.projects_v1_board %}, and interact with a {% data variables.projects.projects_v1_board %}. For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)."
+- **Admin**, which gives people permission to view a {% data variables.projects.projects_v1_board %}, interact with a {% data variables.projects.projects_v1_board %}, manage {% data variables.projects.projects_v1_board %} settings, and manage other people's access to the {% data variables.projects.projects_v1_board %}.
diff --git a/data/reusables/project-management/project-board-visibility.md b/data/reusables/project-management/project-board-visibility.md
index 7fb24ae2e5..5021c82faf 100644
--- a/data/reusables/project-management/project-board-visibility.md
+++ b/data/reusables/project-management/project-board-visibility.md
@@ -1 +1 @@
-By default, user-owned and organization-wide project boards are private and only visible to people with read, write, or admin permissions to the project board. {% ifversion ghae %}An internal{% else %}A public{% endif %} project board is visible to {% ifversion ghae %}anyone with access to your enterprise on {% data variables.product.prodname_ghe_managed %}{% elsif ghes %}anyone with access to your {% data variables.product.prodname_ghe_server %} instance{% else %}anyone with the project board's URL{% endif %}. Repository-level project boards share the visibility of their repository. That is, a private repository will have a private board, and this visibility cannot be changed.
+By default, user-owned and organization-wide {% data variables.projects.projects_v1_boards %} are private and only visible to people with read, write, or admin permissions to the {% data variables.projects.projects_v1_board %}. {% ifversion ghae %}An internal{% else %}A public{% endif %} {% data variables.projects.projects_v1_board %} is visible to {% ifversion ghae %}any with access to your enterprise{% else %}anyone{% endif %} with the {% data variables.projects.projects_v1_board %}'s URL. Repository-level {% data variables.projects.projects_v1_boards %} share the visibility of their repository. That is, a private repository will have a private project, and this visibility cannot be changed.
diff --git a/data/reusables/project-management/project-progress-locations.md b/data/reusables/project-management/project-progress-locations.md
index 9ac6c41be9..1df5983464 100644
--- a/data/reusables/project-management/project-progress-locations.md
+++ b/data/reusables/project-management/project-progress-locations.md
@@ -1 +1 @@
-If progress tracking is enabled, a progress bar appears above the project board, on the project listing page, in the issue sidebar, and in references to the project on other project boards.
+If progress tracking is enabled, a progress bar appears above the {% data variables.projects.projects_v1_board %}, on the project listing page, in the issue sidebar, and in references to the project on other {% data variables.projects.projects_v1_boards %}.
diff --git a/data/reusables/project-management/resync-automation.md b/data/reusables/project-management/resync-automation.md
index 38b2f7a9e8..25880d2441 100644
--- a/data/reusables/project-management/resync-automation.md
+++ b/data/reusables/project-management/resync-automation.md
@@ -1 +1 @@
-When you close a project board, any workflow automation configured for the project board will pause. If you reopen a project board, you have the option to sync automation, which updates the position of the cards on the board according to the automation settings configured for the board. For more information, see "[Reopening a closed project board](/articles/reopening-a-closed-project-board)" or "[Closing a project board](/articles/closing-a-project-board)."
+When you close a {% data variables.projects.projects_v1_board %}, any workflow automation configured for the {% data variables.projects.projects_v1_board %} will pause. If you reopen a {% data variables.projects.projects_v1_board %}, you have the option to sync automation, which updates the position of the cards on the board according to the automation settings configured for the project. For more information, see "[Reopening a closed {% data variables.product.prodname_project_v1 %}](/articles/reopening-a-closed-project-board)" or "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)."
diff --git a/data/reusables/project-management/select-project.md b/data/reusables/project-management/select-project.md
index 2460ba9441..20b4b10488 100644
--- a/data/reusables/project-management/select-project.md
+++ b/data/reusables/project-management/select-project.md
@@ -1,2 +1,2 @@
-1. In the projects list, click the name of the project board.
+1. In the projects list, click the name of the {% data variables.projects.projects_v1_board %}.
 ![Select project](/assets/images/help/projects/select-project.png)
diff --git a/data/reusables/project-management/use-automated-template.md b/data/reusables/project-management/use-automated-template.md
index 889f232af9..851220db4c 100644
--- a/data/reusables/project-management/use-automated-template.md
+++ b/data/reusables/project-management/use-automated-template.md
@@ -1 +1 @@
-You can use a project board template to create a project board with automation already configured. For more information, see "[About project boards](/articles/about-project-boards#templates-for-project-boards)."
+You can use a {% data variables.projects.projects_v1_board %} template to create a {% data variables.projects.projects_v1_board %} with automation already configured. For more information, see "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards#templates-for-project-boards)."
diff --git a/data/reusables/projects/about-workflows.md b/data/reusables/projects/about-workflows.md
index 5c78c53bc5..d2472004a5 100644
--- a/data/reusables/projects/about-workflows.md
+++ b/data/reusables/projects/about-workflows.md
@@ -1,3 +1,3 @@
-Projects (beta) includes built-in workflows that you can use to update the **Status** of items based on certain events. For example, you can automatically set the status to **Todo** when an item is added to your project or set the status to **Done** when an issue is closed.
+{% data variables.product.prodname_projects_v2 %} includes built-in workflows that you can use to update the **Status** of items based on certain events. For example, you can automatically set the status to **Todo** when an item is added to your project or set the status to **Done** when an issue is closed.
 
 When your project initializes, two workflows are enabled by default: When issues or pull requests in your project are closed, their status is set to **Done**, and when pull requests in your project are merged, their status is set to **Done**.
diff --git a/data/reusables/projects/access-insights.md b/data/reusables/projects/access-insights.md
index baa180aa23..e211db1d89 100644
--- a/data/reusables/projects/access-insights.md
+++ b/data/reusables/projects/access-insights.md
@@ -1,8 +1,3 @@
 1. Navigate to your project.
 2. In the top-right, to access insights, click {% octicon "graph" aria-label="the graph icon" %}.
-
-    {% note %}
-
-   **Note:** This feature is currently in a private preview and only available for some organizations. If the {% octicon "graph" aria-label="the graph icon" %} icon is not displayed in your project, insights is not yet enabled for your organization.
-
-   {% endnote %} 
+   ![Screenshot showing the insights icon](/assets/images/help/projects-v2/insights-button.png)
diff --git a/data/reusables/projects/add-draft-issue.md b/data/reusables/projects/add-draft-issue.md
new file mode 100644
index 0000000000..1daf1f11d3
--- /dev/null
+++ b/data/reusables/projects/add-draft-issue.md
@@ -0,0 +1,4 @@
+{% data reusables.projects.add-item-bottom-row %}
+1. Type your idea, then press **Enter**.
+  ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-draft-issue.png)
+1. To add body text, click on the title of the draft issue. In the markdown input box that appears, enter the text for the draft issue body, then click **Save**.
\ No newline at end of file
diff --git a/data/reusables/projects/add-item-bottom-row.md b/data/reusables/projects/add-item-bottom-row.md
new file mode 100644
index 0000000000..2a9b0070b6
--- /dev/null
+++ b/data/reusables/projects/add-item-bottom-row.md
@@ -0,0 +1,2 @@
+1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
+  ![Screenshot showing the bottom row to add an item](/assets/images/help/projects-v2/add-item.png)
\ No newline at end of file
diff --git a/data/reusables/projects/add-item-via-paste.md b/data/reusables/projects/add-item-via-paste.md
new file mode 100644
index 0000000000..b2da1184db
--- /dev/null
+++ b/data/reusables/projects/add-item-via-paste.md
@@ -0,0 +1,4 @@
+{% data reusables.projects.add-item-bottom-row %}
+1. Paste the URL of the issue or pull request.
+  ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/paste-url-to-add.png)
+3. To add the issue or pull request, press <kbd>Return</kbd>.
\ No newline at end of file
diff --git a/data/reusables/projects/bulk-add.md b/data/reusables/projects/bulk-add.md
new file mode 100644
index 0000000000..a29d71e942
--- /dev/null
+++ b/data/reusables/projects/bulk-add.md
@@ -0,0 +1,6 @@
+1. Optionally, to change the repository, click the dropdown and select a repository. You can also search for specific issues and pull requests.
+  ![Screenshot showing repository dropdown](/assets/images/help/projects-v2/add-bulk-select-repo.png)
+1. Select the issues and pull requests you want to add.
+  ![Screenshot showing selecting issues and pull requests to add](/assets/images/help/projects-v2/add-bulk-select-issues.png)
+1. Click **Add selected items**.
+  ![Screenshot showing "add selected items" button](/assets/images/help/projects-v2/add-bulk-save.png)
\ No newline at end of file
diff --git a/data/reusables/projects/create-project.md b/data/reusables/projects/create-project.md
index 7aba696394..21895e063e 100644
--- a/data/reusables/projects/create-project.md
+++ b/data/reusables/projects/create-project.md
@@ -1,8 +1,9 @@
-1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your organization.
-1. Click {% octicon "table" aria-label="The project icon" %} **Projects**.
-1. Select the **New project** drop-down menu and click **New project (Beta)**.
-
-   ![New project](/assets/images/help/issues/new_project_beta.png)
-1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**.
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+1. Under your organization name, click {% octicon "table" aria-label="The project icon" %} **Projects**.
+  ![Screenshot showing the 'Projects' tab](/assets/images/help/projects-v2/tab-projects.png)
+1. Click **New project**.
+   ![Screenshot showing New project button](/assets/images/help/projects-v2/new-project-button.png)
+1. When prompted to select a template, click a template or, to start with an empty project, click **Table** or **Board**. Then, click **Create**.
 
    ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png)
diff --git a/data/reusables/projects/create-user-project.md b/data/reusables/projects/create-user-project.md
index 1273840d38..1589d98fa5 100644
--- a/data/reusables/projects/create-user-project.md
+++ b/data/reusables/projects/create-user-project.md
@@ -1,7 +1,8 @@
-1. On any {% data variables.product.product_name %} page, click on your avatar, then select **Your projects**.
-1. Select the **New project** drop-down menu and click **New project (Beta)**.
-
-   ![New project](/assets/images/help/issues/new_project_beta.png)
-1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**.
+{% data reusables.profile.access_profile %}
+1. On your profile, click {% octicon "table" aria-label="The project icon" %} **Projects**.
+  ![Screenshot showing the 'Projects' tab](/assets/images/help/projects-v2/tab-projects.png)
+1. Click **New project**.
+   ![New project](/assets/images/help/projects-v2/new-project-button.png)
+1. When prompted to select a template, click a template or, to start with an empty project, click **Table** or **Board**. Then, click **Create**.
 
    ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png)
diff --git a/data/reusables/projects/enable-basic-workflow.md b/data/reusables/projects/enable-basic-workflow.md
index 92bb137381..48742816af 100644
--- a/data/reusables/projects/enable-basic-workflow.md
+++ b/data/reusables/projects/enable-basic-workflow.md
@@ -1,7 +1,13 @@
 1. Navigate to your project.
 1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
+  ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png)
 1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**.
+  ![Screenshot showing the 'Workflows' menu item](/assets/images/help/projects-v2/workflows-menu-item.png)
 1. Under **Default workflows**, click on the workflow that you want to edit.
+  ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png)
 1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on.
+  ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png)
 1. Next to **Set**, choose the value that you want to set the status to.
+  ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png)
 1. If the workflow is disabled, click the toggle next to **Disabled** to enable the workflow.
+  ![Screenshot showing the "enable" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png)
diff --git a/data/reusables/projects/migrate-project-steps.md b/data/reusables/projects/migrate-project-steps.md
index d1cacc98ee..8a09fb41d1 100644
--- a/data/reusables/projects/migrate-project-steps.md
+++ b/data/reusables/projects/migrate-project-steps.md
@@ -1,7 +1,7 @@
 1. Next to the project you want to migrate, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
-1. In the menu, click **Migrate to beta**.
-  ![Screenshot showing migrate to beta option](/assets/images/help/issues/migrate-to-beta.png)
+1. In the menu, click **Migrate**.
+  ![Screenshot showing migrate option](/assets/images/help/issues/migrate-menu-item.png)
 1. In the the popup, select what you want to happen to the project after it is migrated. We recommend selecting "Close the old project" so it's clear which project is in use.
-  ![Screenshot showing migrate to beta option](/assets/images/help/issues/migrate-option.png)
+  ![Screenshot showing migrate modal](/assets/images/help/issues/migrate-option.png)
 1. In the bottom right of the popup, click **Start migration**.
-  ![Screenshot showing migrate to beta option](/assets/images/help/issues/migrate-start.png)
+  ![Screenshot showing start migration button](/assets/images/help/issues/migrate-start.png)
diff --git a/data/reusables/projects/new-field.md b/data/reusables/projects/new-field.md
new file mode 100644
index 0000000000..60284f6dc2
--- /dev/null
+++ b/data/reusables/projects/new-field.md
@@ -0,0 +1,6 @@
+1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}.
+   ![Screenshot showing new field button](/assets/images/help/projects-v2/new-field-button.png)
+1. Click **New field**.
+   ![Screenshot showing new field menu item](/assets/images/help/projects-v2/new-field-menu-item.png)
+1. Type the name of your new field.
+   ![Screenshot showing the field name](/assets/images/help/projects-v2/new-field-name.png)
\ No newline at end of file
diff --git a/data/reusables/projects/new-view.md b/data/reusables/projects/new-view.md
new file mode 100644
index 0000000000..cf52a8ce1a
--- /dev/null
+++ b/data/reusables/projects/new-view.md
@@ -0,0 +1,2 @@
+1. To the right of your existing views, click **New view**
+   ![Screenshot showing the column field menu](/assets/images/help/projects-v2/new-view.png)
\ No newline at end of file
diff --git a/data/reusables/projects/open-item-menu.md b/data/reusables/projects/open-item-menu.md
new file mode 100644
index 0000000000..5c9c7fc258
--- /dev/null
+++ b/data/reusables/projects/open-item-menu.md
@@ -0,0 +1 @@
+1.  Select the {% octicon "triangle-down" aria-label="the item menu" %} (in table layout) or the {% octicon "kebab-horizontal" aria-label="the item menu" %} (in board layout).
\ No newline at end of file
diff --git a/data/reusables/projects/open-view-menu.md b/data/reusables/projects/open-view-menu.md
new file mode 100644
index 0000000000..6cf3045784
--- /dev/null
+++ b/data/reusables/projects/open-view-menu.md
@@ -0,0 +1,2 @@
+1. Click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the name of the currently open view.
+  ![Screenshot showing the view menu icon](/assets/images/help/projects-v2/view-menu-icon.png)
\ No newline at end of file
diff --git a/data/reusables/projects/project-description.md b/data/reusables/projects/project-description.md
index 47c4f2e4fb..832430e468 100644
--- a/data/reusables/projects/project-description.md
+++ b/data/reusables/projects/project-description.md
@@ -2,9 +2,12 @@ You can set your project's description and README to share the purpose of your p
 
 {% data reusables.projects.project-settings %}
 1. To add a short description to your project, under "Add a description", type your description in the text box  and click **Save**.
+  ![Screenshot showing the 'Add my description' settings](/assets/images/help/projects-v2/edit-description.png)
 1. To update your project's README, under "README", type your content in the text box.
    - You can format your README using Markdown. For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)."
    - To toggle between the text box and a preview of your changes, click {% octicon "eye" aria-label="The preview icon" %} or {% octicon "pencil" aria-label="The edit icon" %}.
+  ![Screenshot showing editing a project's README](/assets/images/help/projects-v2/edit-readme.png)
 1. To save changes to your README, click **Save**.
+  ![Screenshot showing the 'Save' button for a project's README](/assets/images/help/projects-v2/save-readme-button.png)
 
 You can view and make quick changes to your project description and README by navigating to your project and clicking {% octicon "sidebar-expand" aria-label="The sidebar icon" %} in the top right.
diff --git a/data/reusables/projects/project-settings.md b/data/reusables/projects/project-settings.md
index 4c244857b3..7b23c69d75 100644
--- a/data/reusables/projects/project-settings.md
+++ b/data/reusables/projects/project-settings.md
@@ -1,3 +1,5 @@
 1. Navigate to your project.
 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.
+  ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png)
+2. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings.
+  ![Screenshot showing the 'Settings' menu item](/assets/images/help/projects-v2/settings-menu-item.png)
diff --git a/data/reusables/projects/project_boards_old.md b/data/reusables/projects/project_boards_old.md
index 48f8e3c287..4eed540e87 100644
--- a/data/reusables/projects/project_boards_old.md
+++ b/data/reusables/projects/project_boards_old.md
@@ -3,9 +3,8 @@
 {% note %}
 
 **Notes:**
-
-* Projects (beta), the all-new projects experience, is now available. For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" and "[Migrating your project to Projects (beta)](/issues/trying-out-the-new-projects-experience/migrating-your-project)."
-* You can only create a new classic project board for an organization, user, or repository that already has at least one classic project board. If you're unable to create a classic project board, create a beta project board instead.
+* {% data variables.product.prodname_projects_v2 %}, the all-new projects experience, is now available. For more information about {% data variables.product.prodname_projects_v2 %}, see "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" and for information about migrating your {% data variables.projects.projects_v1_board %}, see "[Migrating from {% data variables.product.prodname_projects_v1_caps %}](/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic)."
+* You can only create a new classic project board for an organization, user, or repository that already has at least one classic project board. If you're unable to create a classic project board, create a project board instead.
 
 {% endnote %}
 
diff --git a/data/reusables/projects/projects-api.md b/data/reusables/projects/projects-api.md
index 885e6f0683..c04b944049 100644
--- a/data/reusables/projects/projects-api.md
+++ b/data/reusables/projects/projects-api.md
@@ -3,8 +3,8 @@
 
 **Notes:** 
 
-* This API only applies to project boards. Projects (beta) can be managed with the GraphQL API. For more information, see "[Using the API to manage projects (beta)](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
-* You can only create a new classic project board for an organization, user, or repository that already has at least one classic project board.
+* This API only applies to {% data variables.product.prodname_projects_v1 %}. {% data variables.product.prodname_projects_v2 %} can be managed with the GraphQL API. For more information, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)."
+* You can only create a new {% data variables.projects.projects_v1_board %} for an organization, user, or repository that already has at least one {% data variables.projects.projects_v1_board %}.
 
 {% endnote %}
 {% endif %}
diff --git a/data/reusables/projects/reopen-a-project.md b/data/reusables/projects/reopen-a-project.md
index 916b1bcea1..c827c47e93 100644
--- a/data/reusables/projects/reopen-a-project.md
+++ b/data/reusables/projects/reopen-a-project.md
@@ -4,6 +4,8 @@
    ![Screenshot showing project close button](/assets/images/help/issues/closed-projects-tab.png)
 1. Click the project you want to reopen.
 1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
-1. In the menu, to access the project settings, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
+  ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png)
+1. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings.
+  ![Screenshot showing the 'Settings' menu item](/assets/images/help/projects-v2/settings-menu-item.png)
 1. At the bottom of the page, click **Re-open project**.
    ![Screenshot showing project re-open button](/assets/images/help/issues/reopen-project-button.png)
diff --git a/data/reusables/projects/save-view.md b/data/reusables/projects/save-view.md
new file mode 100644
index 0000000000..8183c5054f
--- /dev/null
+++ b/data/reusables/projects/save-view.md
@@ -0,0 +1,3 @@
+{% data reusables.projects.open-view-menu %}
+1. Click **Save changes**.
+   ![Screenshot showing the save menu item](/assets/images/help/projects-v2/save-view.png)
\ No newline at end of file
diff --git a/data/reusables/projects/select-an-item.md b/data/reusables/projects/select-an-item.md
new file mode 100644
index 0000000000..898a752d46
--- /dev/null
+++ b/data/reusables/projects/select-an-item.md
@@ -0,0 +1,5 @@
+1. Select the item. To select multiple items, do one of the following:
+     - Hold <kbd>Command</kbd> (Mac) or <kbd>Ctrl</kbd> (Windows/Linux) and click each item.
+     - Select an item then press <kbd>Shift</kbd>+<kbd>↑</kbd> or <kbd>Shift</kbd>+<kbd>↓</kbd> to select additional items above or below the selected item.
+     - Select an item then press <kbd>Shift</kbd> and click another item to select all items between the two items.
+     - With a row or item already selected, press <kbd>Command</kbd>+<kbd>A</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>A</kbd> (Windows/Linux) to select all items in a column in a board layout or all items in a table layout.
\ No newline at end of file
diff --git a/data/reusables/repositories/anyone-can-view-anonymized-url.md b/data/reusables/repositories/anyone-can-view-anonymized-url.md
new file mode 100644
index 0000000000..df6bf85408
--- /dev/null
+++ b/data/reusables/repositories/anyone-can-view-anonymized-url.md
@@ -0,0 +1,5 @@
+{% warning %}
+
+**Warning:** If you attach a file to a pull request, issue comment, or ticket in the {% data variables.contact.support_portal %}, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
+
+{% endwarning %}
diff --git a/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index d57a99a27e..d0755a641d 100644
--- a/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -5,18 +5,12 @@ Adobe | Adobe Device Token | adobe_device_token
 Adobe | Adobe Service Token | adobe_service_token
 Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token
 Adobe | Adobe JSON Web Token | adobe_jwt
-Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id
-Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret
+Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret| alibaba_cloud_access_key_id </br>alibaba_cloud_access_key_secret
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
-Amazon | Amazon OAuth Client ID | amazon_oauth_client_id{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
-Amazon | Amazon OAuth Client Secret | amazon_oauth_client_secret{% endif %}
-Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id
-Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key
+Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id </br>amazon_oauth_client_secret{% endif %}
+Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id </br>aws_secret_access_key
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %}
+Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token </br>aws_temporary_access_key_id </br>aws_secret_access_key{% endif %}
 Asana | Asana Personal Access Token | asana_personal_access_token
 Atlassian | Atlassian API Token | atlassian_api_token
 Atlassian | Atlassian JSON Web Token | atlassian_jwt
@@ -79,19 +73,15 @@ GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %}
 Google | Google API Key | google_api_key
-Google | Google Cloud Private Key ID | google_cloud_private_key_id
+Google | Google Cloud Private Key ID | 
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %}
+Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %}
+Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
 Google | Google OAuth Access Token | google_oauth_access_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
-Google | Google OAuth Client ID | google_oauth_client_id{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
-Google | Google OAuth Client Secret | google_oauth_client_secret{% endif %}
+Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id </br>google_oauth_client_secret{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
 Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
 Grafana | Grafana API Key | grafana_api_key
@@ -149,9 +139,7 @@ PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Plivo | Plivo Auth ID | plivo_auth_id{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Plivo | Plivo Auth Token | plivo_auth_token{% endif %}
+Plivo | Plivo Auth ID with Plivo Auth Token | plivo_auth_id </br>plivo_auth_token{% endif %}
 Postman | Postman API Key | postman_api_key
 Proctorio | Proctorio Consumer Key | proctorio_consumer_key
 Proctorio | Proctorio Linkage Key | proctorio_linkage_key
diff --git a/data/reusables/secret-scanning/secret-list-private-push-protection.md b/data/reusables/secret-scanning/secret-list-private-push-protection.md
index 4b7d4ba3e3..fd323a2dd4 100644
--- a/data/reusables/secret-scanning/secret-list-private-push-protection.md
+++ b/data/reusables/secret-scanning/secret-list-private-push-protection.md
@@ -1,14 +1,10 @@
 Provider | Supported secret | Secret type
 --- | --- | ---
 Adafruit IO | Adafruit IO Key | adafruit_io_key
-Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id
-Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret
-Amazon | Amazon OAuth Client ID | amazon_oauth_client_id
-Amazon | Amazon OAuth Client Secret | amazon_oauth_client_secret
-Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id
-Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key
-Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token
-Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id
+Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret| alibaba_cloud_access_key_id </br>alibaba_cloud_access_key_secret
+Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id </br>amazon_oauth_client_secret
+Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id </br>aws_secret_access_key
+Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token </br>aws_temporary_access_key_id </br>aws_secret_access_key
 Asana | Asana Personal Access Token | asana_personal_access_token
 Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token
 Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret
@@ -37,9 +33,9 @@ GitHub | GitHub OAuth Access Token | github_oauth_access_token
 GitHub | GitHub Refresh Token | github_refresh_token
 GitHub | GitHub App Installation Access Token | github_app_installation_access_token
 GitHub | GitHub SSH Private Key | github_ssh_private_key
-Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret
-Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id
-Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id
+Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret
+Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret
+Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id </br>google_oauth_client_secret
 Grafana | Grafana API Key | grafana_api_key
 Hubspot | Hubspot API Key | hubspot_api_key
 Intercom | Intercom Access Token | intercom_access_token
diff --git a/data/reusables/secret-scanning/secret-scanning-pattern-pair-matches.md b/data/reusables/secret-scanning/secret-scanning-pattern-pair-matches.md
new file mode 100644
index 0000000000..d664036275
--- /dev/null
+++ b/data/reusables/secret-scanning/secret-scanning-pattern-pair-matches.md
@@ -0,0 +1 @@
+If access to a resource requires paired credentials, then secret scanning will create an alert only when both parts of the pair are detected in the same file. This ensures that the most critical leaks are not hidden behind information about partial leaks.
diff --git a/data/reusables/support/submit-a-ticket.md b/data/reusables/support/submit-a-ticket.md
index 996722fd36..6418a84693 100644
--- a/data/reusables/support/submit-a-ticket.md
+++ b/data/reusables/support/submit-a-ticket.md
@@ -36,6 +36,8 @@
     - Steps to reproduce the issue
     - Any special circumstances surrounding the discovery of the issue (for example, the first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem, and suggested urgency)
     - Exact wording of error messages
+{% indented_data_reference reusables.repositories.anyone-can-view-anonymized-url spaces=3 %}
+
 {%- ifversion ghes %}
 1. Optionally, attach diagnostics files and other files by dragging and dropping, uploading, or pasting from the clipboard.
 {%- endif %}
diff --git a/data/reusables/webhooks/project_card_short_desc.md b/data/reusables/webhooks/project_card_short_desc.md
index 6fe2904d9e..2e2ca0cf90 100644
--- a/data/reusables/webhooks/project_card_short_desc.md
+++ b/data/reusables/webhooks/project_card_short_desc.md
@@ -1 +1 @@
-Activity related to project cards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/rest/reference/projects#cards)" REST API.
+Activity related to cards in a {% data variables.projects.projects_v1_board %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/rest/reference/projects#cards)" REST API.
diff --git a/data/reusables/webhooks/project_column_short_desc.md b/data/reusables/webhooks/project_column_short_desc.md
index 35d38e4101..a45a7e5759 100644
--- a/data/reusables/webhooks/project_column_short_desc.md
+++ b/data/reusables/webhooks/project_column_short_desc.md
@@ -1 +1 @@
-Activity related to columns in a project board. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/rest/reference/projects#columns)" REST API.
+Activity related to columns in a {% data variables.projects.projects_v1_board %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/rest/reference/projects#columns)" REST API.
diff --git a/data/reusables/webhooks/project_short_desc.md b/data/reusables/webhooks/project_short_desc.md
index 2ae5d8be21..fe9313b6f4 100644
--- a/data/reusables/webhooks/project_short_desc.md
+++ b/data/reusables/webhooks/project_short_desc.md
@@ -1 +1 @@
-Activity related to project boards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/rest/reference/projects)" REST API.
+Activity related to {% data variables.projects.projects_v1_boards %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/rest/reference/projects)" REST API.
diff --git a/data/variables/product.yml b/data/variables/product.yml
index b497ed3b50..fd2f506ac6 100644
--- a/data/variables/product.yml
+++ b/data/variables/product.yml
@@ -85,6 +85,17 @@ prodname_codeql_cli: 'CodeQL CLI'
 codeql_cli_ghes_recommended_version: >-
   {% ifversion ghes < 3.3 %}2.6.3{% elsif ghes < 3.5 %}2.7.6{% elsif ghes = 3.5 %}2.8.5{% elsif ghes = 3.6 %}2.9.4{% elsif ghae-issue-7470 %}2.8.5{% elsif ghae %}2.7.6{% endif %}
 
+# Projects v2
+prodname_projects_v2: 'Projects'
+prodname_projects_v1: >-
+  {% ifversion ghes or ghae %}project boards{% else %}projects (classic){% endif %}
+prodname_projects_v1_caps: >-
+  {% ifversion ghes or ghae %}Project boards{% else %}Projects (classic){% endif %}
+prodname_project_v1: >-
+  {% ifversion ghes or ghae %}project board{% else %}project (classic){% endif %}
+prodname_project_v1_caps: >-
+  {% ifversion ghes or ghae %}Project board{% else %}Project (classic){% endif %}
+
 # Apps, GitHub Marketplace, and integrations
 prodname_marketplace: 'GitHub Marketplace'
 prodname_github_app: 'GitHub App'
@@ -188,7 +199,7 @@ prodname_code_scanning_capc: 'Code scanning'
 prodname_codeql_runner: 'CodeQL runner'
 prodname_advisory_database: 'GitHub Advisory Database'
 prodname_codeql_workflow: 'CodeQL analysis workflow'
-prodname_dependency_review_action: 'Dependency Review GitHub Action'
+prodname_dependency_review_action: 'dependency review action'
 
 # Visual Studio
 prodname_vs: 'Visual Studio'
diff --git a/data/variables/projects.yml b/data/variables/projects.yml
new file mode 100644
index 0000000000..a34fe3d8b4
--- /dev/null
+++ b/data/variables/projects.yml
@@ -0,0 +1,15 @@
+projects_v2: 'projects'
+projects_v2_caps: 'Projects'
+project_v2: 'project'
+project_v2_caps: 'Project'
+
+projects_v1_board: >-
+  {% ifversion ghes or ghae %}project board{% else %}classic project{% endif %}
+projects_v1_board_caps: >-
+  {% ifversion ghes or ghae %}Project board{% else %}Classic project{% endif %}
+projects_v1_boards: >-
+  {% ifversion ghes or ghae %}project boards{% else %}classic projects{% endif %}
+projects_v1_boards_caps: >-
+  {% ifversion ghes or ghae %}Project boards{% else %}Classic projects{% endif %}
+
+command-palette-shortcut: '<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)'
diff --git a/lib/get-mini-toc-items.js b/lib/get-mini-toc-items.js
index 537ea5cd12..73152536e6 100644
--- a/lib/get-mini-toc-items.js
+++ b/lib/get-mini-toc-items.js
@@ -1,6 +1,8 @@
 import cheerio from 'cheerio'
 import { range } from 'lodash-es'
 
+import renderContent from './render-content/index.js'
+
 export default function getMiniTocItems(html, maxHeadingLevel = 2, headingScope = '') {
   const $ = cheerio.load(html, { xmlMode: true })
 
@@ -123,3 +125,25 @@ function minimalMiniToc(toc) {
     return minimal
   })
 }
+
+export async function getAutomatedPageMiniTocItems(
+  items,
+  context,
+  depth = 2,
+  markdownHeading = ''
+) {
+  const titles =
+    markdownHeading +
+    items
+      .map((item) => {
+        let title = ''
+        for (let i = 0; i < depth; i++) {
+          title += '#'
+        }
+        return title + ` ${item}\n`
+      })
+      .join('')
+
+  const toc = await renderContent(titles, context)
+  return getMiniTocItems(toc, depth, '')
+}
diff --git a/lib/rest/index.js b/lib/rest/index.js
index 5b0fa4bc0c..0c0dc8db11 100644
--- a/lib/rest/index.js
+++ b/lib/rest/index.js
@@ -3,8 +3,7 @@ import fs from 'fs'
 import path from 'path'
 
 import { readCompressedJsonFileFallback } from '../read-json-file.js'
-import renderContent from '../render-content/index.js'
-import getMiniTocItems from '../get-mini-toc-items.js'
+import { getAutomatedPageMiniTocItems } from '../get-mini-toc-items.js'
 import { allVersions } from '../all-versions.js'
 import languages from '../languages.js'
 
@@ -98,12 +97,8 @@ export async function getRestMiniTocItems(
 
   if (!restOperationData.get(language).get(version).get(category).get(subCategory)) {
     const languageTree = restOperationData.get(language)
-    let toc = ''
-    // only a string with the raw HTML of each heading level 3
-    // is needed to generate the toc
-    const titles = restOperations.map((operation) => `### ${operation.title}\n`).join('')
-    toc += await renderContent(titles, context)
-    const restOperationsMiniTocItems = getMiniTocItems(toc, 3, '')
+    const titles = restOperations.map((operation) => operation.title)
+    const restOperationsMiniTocItems = await getAutomatedPageMiniTocItems(titles, context, 3)
     languageTree.get(version).get(category).set(subCategory, {
       restOperationsMiniTocItems,
     })
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 b11184d97e..f9103a3714 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:54a0f7592de5adee7529ef385e7cf723f37c5b11dbaccc3cdf1acc6557c4c77d
-size 787099
+oid sha256:f711b42b1081da3233261307b8a359be1ef42246f9dc73f7eb4e595a6dc06dfa
+size 789453
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 ad1d1de702..6de364869f 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:34d68d879d3478def239fe596a45b1b311e91fb9d6afec19ca166b8e21f466a7
-size 1585078
+oid sha256:33eddabb74ee352f5f2753dd4d919a7d2a5ec029b742a0452fa4578f3612c163
+size 1589798
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 de80319028..efb3086540 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:57cb327e593c9434896315bbcbaef86ca9486cc38b9eafb7a0b304023c10c644
-size 1083709
+oid sha256:ab4d33a271566972aaaaaa9e2cd6de23ce4f45b0b5627106cbdb3c0d1dbb4b50
+size 1086977
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 0f98457c6a..27062d2fb5 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:44af2decba4b4fa6a9f3a2788309ca2e870650138dc9cfb4c5fc17f3ac755b02
-size 4375443
+oid sha256:6b7cf1eaa1b1ec0e8233b66e00df1394fb45da5772762841de4d6dbfd2e54584
+size 4393205
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 5f5910284c..e97e0be585 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:e2dc7c5cf5c8fab723f42e3aa3b1089df0bd2a9762d3b881f902a986806b38be
-size 728261
+oid sha256:eb72541b0faee0a90a44e12954b982dea5aa9584895acc9eba3cbf27267a1b79
+size 730467
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 2395933ff2..d2752c75cd 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:5dde62961772a12aacdebe8c3adfb7e85e3b8510840629425f77fb8b76274edf
-size 3080474
+oid sha256:de60b7c2a84c8f011d1e918b1516ec31c55f26b35db9e8302311ca7384762e9c
+size 3091033
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 2d666c9f76..9ef0d932ba 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:23dceda8eed56763fa3fb6a3358a90bd173660931cb053a0bb399137fdf9cfad
-size 802255
+oid sha256:d85b645ce0f6029bf4f7ac26ec1c4d8d9571b57ecc851154d2f2f9c6d4eb5d35
+size 804669
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 18126e83d1..00673cf146 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:e51bcb206245a529459a23657cf293477dbcc89020668b0a928e4383b2a3326e
-size 4386697
+oid sha256:bd7daa79efdbfda83ef5620252ca440cf40757557347cc03b6de20aa9d62ff9a
+size 4404738
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 7e51f7faa4..5e52eef953 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:5dd7024bed7716e6822aa7c7a00000027d923f5b37bd6485bff444b566c1568d
-size 718030
+oid sha256:0e34e871f6b97ef462696e9e86abe84a6c55d5326bae87ed1ba674f9abfc922e
+size 719013
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 59c12140d6..88ac2873c9 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:a674b639f464fe9cca2f0b465483a1b02c2cb8a0d80fa6611a225563d563f4d0
-size 2983928
+oid sha256:141324c66bd26c8d7e3127934d0a83db19731be142aacd5471801f42b182ee48
+size 2982224
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 b35abe317a..7c64fad2a5 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:27ee4b9b67f4f097a5e7d075b4319403d9f63e0d6941f53ba392c6b6f7f5d342
-size 812363
+oid sha256:5120133cf21b2a60fd27d645f9ae88a0d0c97be14a14e0ad7cb1507b6a189632
+size 814648
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 3dd66ac203..ba6b164e44 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:6ca0924ccd5fd6d3773fbc9c24dabd154a98cc36b87515a78a8f8041675d594a
-size 1631171
+oid sha256:cf146a685816d72c533ec93398ce34c2d8fe6c9180b650eda1c8d33888fd30fd
+size 1637218
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 320105f908..02dec284bb 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:64bd4fde7823a3b54cb362cbe602cd2fa3f43c2f55746b1a524fcd8aba7667c6
-size 1119165
+oid sha256:4c9c8c4b19eb6000ced80252ab04413404997d699f8c0e034975213fd2dd134b
+size 1122426
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 8eed5f750e..2faf895195 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:c497feb7ec25167a0f47428ffb0981e1250f9c22e42ffdc1cd26e29ef7902912
-size 4481473
+oid sha256:848602869d316adba495a4df39bf47bd8c130d82743996df2506537adf8cbf69
+size 4498102
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 4d2c711639..d330104fbf 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:495e7601d1ddde82a7040c06912203c1ffa7769be54a9943cfcfacf6401120ae
-size 749240
+oid sha256:7940cf2874f2fea00834593b28011a29819aa02957f7582b5fbf33cf0e2829c5
+size 751408
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 0c9cf2673d..859e2a9d3c 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:ec3cf516c95303f8067a3c249a8d8c0ca002d91d931b4046930181c5b3879937
-size 3165414
+oid sha256:661c940347f93c3128e72c9b1a1bd7c25474e335d1405b2aa4afcc855a3d9d3a
+size 3175856
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 1ecafc5e85..6a3a8b593a 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:4c3096bac37eef5d857675b0c795db719bd430603ea4390a866dcb10df3c4b9c
-size 827209
+oid sha256:458b78ce215e697494a56659ad038bcf4174413c48866c8dcebd6a62440ae9e0
+size 829996
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 762ac31909..a83055c751 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:d0c2b9a5593d0de20e92fccd679b3a1aea152da71d5ab191815e983cd56d6800
-size 4520398
+oid sha256:259aa0379b061b389fcb57c0296b173980da971cd75a9b924d70c4b4b8ee199b
+size 4538215
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 0f8d77d31c..92ad5030a3 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:f87862ffdcc303b33ad29c3a00d7cff01b4afe3852bd933cb7f1f032a25ee78f
-size 739397
+oid sha256:679e2e6c701fb9ebfb70acb8ae69671f2512f4c3abc41611cb61382245995a94
+size 740261
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 e7c53f0d18..5f1c5c618a 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:22d7c0a90d7642458727dcf4b096afaef69fe6fc8ae5b1b6f006669b4b4ce999
-size 3069373
+oid sha256:2fdda81d71e1d99aae1d93a494124cbbe6b1fc25af6f397e5405e99f52364878
+size 3065815
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 8f375e48d8..02982c532b 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:dca1aa79ff72376f752353d841f5d94897b719bf7192eb624d621248b7d90a9f
-size 814654
+oid sha256:069443e74f755ed4283c7b679839825c8b9c46ddeaa1f99df90d0c048744290a
+size 817059
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 2589aebd58..08fe14ac20 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:34b65fe54a96f665d7bdb6554eb60c29a9d979958698a743249c219d1f07af45
-size 1643790
+oid sha256:f7dcf2b948f77f878d5b085f5b544a2373fa68de53609e641689a8d1cf6a3f70
+size 1650641
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 9c0fcef4ad..0ca6d65fab 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:6876ad3bb07b6cb2b6dec051765eb53f8371acc78c9732f498afacd92de44b26
-size 1129170
+oid sha256:316ff12226201f554dc92b393991eb122caef4a14c630a8d6767706f72241545
+size 1132201
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 27f457240a..142291f0b0 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:627219ee300a96f3056c306e584104cf63ffee76bec569be4f6568aae149bc97
-size 4532000
+oid sha256:29483ac19935b1976e1ad784a649259c37aa698f10c29fb57283a4e231dcd4c3
+size 4550368
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 a14278d01b..4b96cec1e9 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:d95ca2c84529015f692dd26a16461d5d0513f1f3c664a6a98f555414b03f3c90
-size 753518
+oid sha256:37f08068668027fea7dafe95b9803905bb971474b2fa9ec8d38644658ed2b576
+size 755597
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 d525536f55..95ffffa985 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:91c67db70f9c143129786b6e3ab1738330f298dd0f1daf9055adaa7b9e324936
-size 3183804
+oid sha256:94ca745d00f081ade1ab2cf80003b935e61be517ca48bdf8df5f1f4a469e5536
+size 3195264
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 0569c848d6..58bbd5a062 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:5ea8a279ebabcea75551b77bdf86ceb0c5a1c6888c7d1b0c213fce508d188345
-size 830589
+oid sha256:8bb1cea873951d568f643e70618374640124edbdc2c1f884501376ad6a0511e9
+size 833256
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 963bdb88c6..a95ddaf181 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:2f08dd2c159f675541d027ba7ffaa5dfeae9b5c97baf5dc949e0606c2da27de7
-size 4549877
+oid sha256:c77240c0a030bdd2fa7e4b45aa8d01877339be7ef148c476acb924ae9686c4d0
+size 4569290
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 b4cad3b865..5f83e3ce21 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:919e224fdad4efca237f4dc626713d61be9db45162248cade4106021f585d84b
-size 743198
+oid sha256:1d53c2f25b1213ed8996c94639b256f73f8c067ee06137eec59d90d42abe2473
+size 744238
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 8587790f50..66f1291e48 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:3755d0def96d7d0622e0e8b16fdb4da27c53a00837337a219408a1c034956599
-size 3090460
+oid sha256:21c38a7c5ef9e29c95cea4a3bf4dbde4b4da843d1135eab7f0a7d1c367fc54f1
+size 3088524
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 a4e6ea510a..ca58902796 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:7bd03976147001388ecee0ea2847a9a10538c75129427740f8f7e640631cc23b
-size 843811
+oid sha256:b84cd7054f150a4f97fdac15ba2f4b3f7496c9166309c11e4cc415c1e2504cc9
+size 846425
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 8c13e9235b..07c47e1e4d 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:eac83a2439132cdef57adadee851b05456a1108473ac9f218ce8b8bedb4e8ebf
-size 1702853
+oid sha256:22e99daa7dbbff53031a0f53c578bb9547ed44e445c60fd1e80faf4f68da617c
+size 1709591
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 1bbbf59b5a..20d9aaa7fc 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:5ed15068a52c54f0e74561250e886ec48f54d796200c5e608250d25408657c59
-size 1166938
+oid sha256:aa20c81844f722cbdea88c6943a531ecfd142a2f33e7c8d2011de99522ccb5a7
+size 1170037
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 a56b44a637..9f3b0d0597 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:7cd9818935b3885cb504ae8e1a93d2b5083bcfaac19c4b82dd90409d3db4e249
-size 4688918
+oid sha256:32ed311bf270ce7e2ff788f46812d31e88a98de13ab12122f7969e07848dee37
+size 4707166
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 17c3c5c758..fc27e112f3 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:2ae7a59e75646e6af0b3c4e8538d66fb3e1fc0ef4a43ae915e8816b8a7ae379e
-size 776529
+oid sha256:e4cf3c430011c6d742317486d3459fb715b7ade91a6dd22e0ad677b3361fd997
+size 778645
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 f255209e3f..1279157fd2 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:61c596577898b039001b24b7385ba940a326e55b7c5d22a96a45ee8f26b761fb
-size 3293612
+oid sha256:eb3e508a44fa67bcc9a946ab253d1fc2720e5216ef5f3aea9ef035a42c0125cd
+size 3305130
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 02e074fb7c..3d24592e64 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:c4c3b6c92d2e6087cd532224ca18cb38d116898bc1856d10b17f7cd6666b0bee
-size 857186
+oid sha256:a2a9f6654b0d68aa16627c34aa824d5560464eaad5bc1523777baed1c5109271
+size 859902
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 977ae4f477..918a1af37e 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:58afa330021e4dd578b91fa18620594353c843eb41127d38f9397741ec5f8625
-size 4713315
+oid sha256:75176c5b01eda8b4cbe1f7ec8eddd6ce4b0e898135876fa22a506065a75ddb08
+size 4731257
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 84a943ca77..f0abc36d2f 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:df385efc34b3e9d80eaba1ca990fffe2477366fcbddff5d262054671b1e62d2f
-size 765822
+oid sha256:810b5521831be7f14a57768f1600c4a556df1e3653ec2da462f37ff52833313a
+size 766747
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 7b14c6e918..fa059dd6ef 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:6491876a58c7cf7e510f27f60fba3b5681ba193223035fff17d1ef13560852e1
-size 3195658
+oid sha256:6f5aa93c82fee99ed96e9741b4f7975cac2b92cfc78671f8523f4adf56e6d09c
+size 3193786
diff --git a/lib/search/indexes/github-docs-3.6-cn-records.json.br b/lib/search/indexes/github-docs-3.6-cn-records.json.br
new file mode 100644
index 0000000000..2a531c8cba
--- /dev/null
+++ b/lib/search/indexes/github-docs-3.6-cn-records.json.br
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79049f160f59d47c53f014144a50f2dc97be5fa496cbc85351c246c9d34ec805
+size 869608
diff --git a/lib/search/indexes/github-docs-3.6-cn.json.br b/lib/search/indexes/github-docs-3.6-cn.json.br
new file mode 100644
index 0000000000..805e08a4f3
--- /dev/null
+++ b/lib/search/indexes/github-docs-3.6-cn.json.br
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d348a2f9bdbc6d6a5fb42a9f099959a43b82ba80439e62d184def40086dba885
+size 1757671
diff --git a/lib/search/indexes/github-docs-3.6-en-records.json.br b/lib/search/indexes/github-docs-3.6-en-records.json.br
index 95b6892710..502349a859 100644
--- a/lib/search/indexes/github-docs-3.6-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.6-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:55cb79faa2b0bd6d4b67576a20a31a9f0915f485b9c06869f08d1f9a1e61efad
-size 1205367
+oid sha256:95abb46c1003de4cea9a57d0d51e88f46d326c88f6a6309d96928d53e5bf914c
+size 1199251
diff --git a/lib/search/indexes/github-docs-3.6-en.json.br b/lib/search/indexes/github-docs-3.6-en.json.br
index 0779e401b4..1655549e6b 100644
--- a/lib/search/indexes/github-docs-3.6-en.json.br
+++ b/lib/search/indexes/github-docs-3.6-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ba4d9662828539297e8b561631563c2b2fdce1e0dfaa75becade1eed13cdeca7
-size 4816689
+oid sha256:1e82146e44ea4861306a6025d711a74419d3a7d7450bc6d972e0006a37b13f05
+size 4823947
diff --git a/lib/search/indexes/github-docs-3.6-es-records.json.br b/lib/search/indexes/github-docs-3.6-es-records.json.br
new file mode 100644
index 0000000000..efc15c0be7
--- /dev/null
+++ b/lib/search/indexes/github-docs-3.6-es-records.json.br
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af9a07c3fe71a636843899597d97642ebc5439666f5fb38fc6ed37718da02240
+size 798954
diff --git a/lib/search/indexes/github-docs-3.6-es.json.br b/lib/search/indexes/github-docs-3.6-es.json.br
new file mode 100644
index 0000000000..71ee060f18
--- /dev/null
+++ b/lib/search/indexes/github-docs-3.6-es.json.br
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:17e112c3bafe3536eea4b4aef73b2f0a83fa37b0dd1f9d0ddd3acd0f9f6ec231
+size 3406036
diff --git a/lib/search/indexes/github-docs-3.6-ja-records.json.br b/lib/search/indexes/github-docs-3.6-ja-records.json.br
new file mode 100644
index 0000000000..e4d260b85c
--- /dev/null
+++ b/lib/search/indexes/github-docs-3.6-ja-records.json.br
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:756430c330eefb31cf8def08e4a6081b9b389a347722f6b2893cacdf3ea309b3
+size 882610
diff --git a/lib/search/indexes/github-docs-3.6-ja.json.br b/lib/search/indexes/github-docs-3.6-ja.json.br
new file mode 100644
index 0000000000..ef20c3b6f5
--- /dev/null
+++ b/lib/search/indexes/github-docs-3.6-ja.json.br
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ea35cb5fdb2963b3ea5c2294639271225c1a963747acb3ca103beaf0d78618a
+size 4863610
diff --git a/lib/search/indexes/github-docs-3.6-pt-records.json.br b/lib/search/indexes/github-docs-3.6-pt-records.json.br
new file mode 100644
index 0000000000..f81926e89a
--- /dev/null
+++ b/lib/search/indexes/github-docs-3.6-pt-records.json.br
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:38ea98e3639aa490a424fbd740691216c7816073e07d9ee083ce09fa66670bd2
+size 787340
diff --git a/lib/search/indexes/github-docs-3.6-pt.json.br b/lib/search/indexes/github-docs-3.6-pt.json.br
new file mode 100644
index 0000000000..0fca8c6258
--- /dev/null
+++ b/lib/search/indexes/github-docs-3.6-pt.json.br
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3700f5e4075c092914dbd6773611475c7a2654f80218b6a0f3ac7251fdee36c6
+size 3293746
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 ac68c059de..40da402c79 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:d1dab451e30c26665d980e157efbe1d41156d38815ed5db4d4ccb5e60f12f7a3
-size 1021698
+oid sha256:6273e6599ee4e018dec7de559bea3fcb1eab32763eea585c37c74d5b583bc54b
+size 1023991
diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br
index d647ed5f53..56ef305702 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:1fd5f6ce1e46dd78dac3c8a8b4dea99628428f9d98fcf9d40b928e345ebcea23
-size 1733380
+oid sha256:4aa8096645afc8eeb0fe2873fd099ecb2d35a367fa6b752e30976562415d4f09
+size 1740631
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 1cd313f586..a833564d53 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:3732f9aef7a48dfee8d6f9769897ed0d271526d04a4772d9db1d745a1e32a7f0
-size 1435461
+oid sha256:7ce7ea2e9adb4628a850aa4ef242a011a6794948c7a6f7b2498ab2b58b986c5b
+size 1442042
diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br
index d86713db57..5cde1b22c1 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:073ba675f23f36269b42d1ac65d1ef6d2f59ddcad05ffed13eda872c3ba3d609
-size 5488283
+oid sha256:2bf2cb72f82ad9a85c5dca3d166870a14c01e9282546fc01cb181f0d8db72887
+size 5526839
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 2322b3e0cd..6bc5c1b55c 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:b663df57be8d3b0ebbea0a32d3064d976e14ab1de1e27a250ff9bd65725140c5
-size 919342
+oid sha256:c97264eb062569cf9df8a0d93acd7395f4076a3e661b81c08d8693c36cbd7933
+size 920415
diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br
index 8cb10f1ff1..1899dd925a 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:36818a5876e3ef4eeafab55cf49d33920142f2bfdf96414e2d56f52203402769
-size 3756995
+oid sha256:34a4380d1708ea9e3b890593f6f16e63ef95923b6ce6be4ee137be34f5a78b9f
+size 3766639
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 617b65c946..4bd99c1f82 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:038027b0919aee41179d7c39b8abdb2eee28c0432faf0d1a5f093485ce537f66
-size 1027514
+oid sha256:142cdfc32cdbdcf829908a43b13dd1fd200e1c80fbcac69ede81091e3580092d
+size 1031444
diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br
index 6f558d00b0..05035792b9 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:048a1a1aae31a448d6f231ce13fe991df21d26162ce4c779446542d712f46527
-size 5478831
+oid sha256:3e19e5957513918b2fbc2cdf544dcfefc39028db4e02e69356e5fc47884c9247
+size 5498840
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 ed7377706f..262a628f55 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:15c465d9fcb5dcc21bb4203b4641058246cbb50937e467c9b1c28ade5d69275e
-size 908724
+oid sha256:66c182f1b21a1fe35ba2c5c6ebcca55e9b80625cc231e6752bb4c588afdd59ff
+size 909601
diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br
index 92165320dd..3ea73854b3 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:8e9376f4022b718e99e1afc30666b16e0c9505692d264befca270c8700de358d
-size 3673363
+oid sha256:df4d8b4dea7a9d2277b5707db1b12adfbaa0d67b0cf30ba13f344eee814a276f
+size 3678036
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 eb4dff3915..a7d1dd0f9c 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:50a4ac69d3025b32de397bdd9e17cf35992dd8a1ec3ed8c92846c0f38548e3f2
-size 652854
+oid sha256:8e13ee44f9de7b863ce42fb10040ef6365b182dded3fcedd57d237b46dfaa7cb
+size 655317
diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br
index a5fe5a1e03..3ead45d7ce 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:e752b1688d5627f7ee4f56760ea47a64f96aa099b50cbbdf6f6f69a3a9e078a6
-size 1265640
+oid sha256:888a864c30c7e6680f9a28715959f7745d30e597b97b59be05cec419c262d576
+size 1267482
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 3b9ba79e8d..e4e1b7bceb 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:7394094bc60afe1ff220d134f2c8c34715a3590394f7d32fb6ead4326b013c20
-size 927375
+oid sha256:ce3b88883c7d325ab01a3d20da9c0b5c78479e5f715a5d563e5bd04ff0d92079
+size 929987
diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br
index bba756bdee..f553a31a14 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:476b3df967827e6b1560245b911d18f038a35b8e89df95f6b4d205f315f6d7d9
-size 3661890
+oid sha256:f21bebc073f2c573d3310f8f13006cb34fd952cd81faf30af3b2bba97612bdf9
+size 3676746
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 0d8fc3e8af..7d95be6f43 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:d57dcaf169a0ba4562de9b7d4272658130fc6c593701b0fb4ebfd614b87e0166
-size 608383
+oid sha256:c77c93e262cb3df34dd3d16564ff5b1d22133691efa375b4d968f1fccffa689d
+size 610421
diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br
index c1d5ee44b7..b986202e5b 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:428e477b3a2b28d3491ff46b7a80be439330c851918305af61c50329b9040361
-size 2490526
+oid sha256:fe4d0a3761249840c7ff29f5fa4005c55b807be1ebf7374172fdc433becef75b
+size 2498311
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 1e64c3d378..8f7d54c563 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:667dcfea29d9a8ebdd11a5a58b57cff1d347d9ead4b303e41aa15e6b0adb663c
-size 667149
+oid sha256:5635c06c58ae6d51cc8b51f6ac778dc4ead9a5019ef374dcab0e00fd4eb0220d
+size 669474
diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br
index 674098684b..8f96a1e610 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:3067a40cbbc8876e0b7edc982cc1132f42ec45d4bd8af0cf94f9a8df568e5fa0
-size 3546321
+oid sha256:6fbf043efbdc6f76d6e630de0a8523f1e8751bdcba18b9b8ee9cc1b61afceb0d
+size 3559575
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 afea05e0c1..2602459d24 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:b25679f5a3dca3edf36fc884b35179b701b3d463b7192e028744d50117a444a3
-size 600552
+oid sha256:8f8ed8595d04279bcadb14cd7d964d6cd0da8b9a3e14adee59e729cb714b21d5
+size 601601
diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br
index c2fe5d02c6..5397a960ef 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:116c5cd0e41ddf3d2847cf42fb0c8fc23d9c61d874f9ff651db514be92ee40cf
-size 2396565
+oid sha256:253c16f34c9c3f691e1fa6cb723eb6c22cf3ca0fb4e84aa5c6004fd6255c6006
+size 2392421
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 14d62a5810..21b36a5031 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:30b43753050421de3ba98fd7e7048353bb89858e2052a87adf978beccc22252b
-size 992178
+oid sha256:3fce6a71ec5290507e4f158d2b25cbefa883a76c597e6055c5bea27c7d4b9caf
+size 994329
diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br
index fd2ddd1533..cf2c206c37 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:cdf812aa7e127f59a72ab6eb6137c2772848238533276ec3ffcde9ea08c38885
-size 1860298
+oid sha256:950851c0a8f6742b3eed5388c1b4d2a5985393cc6630e168c26cfa30b350b066
+size 1868449
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 f9ccd39453..e004266d99 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:95b17aa71cc131e07531502b203be3a414358c645acc236a5a96236f2438bf3d
-size 1359160
+oid sha256:dbcfd1cbbac1bf42d7dae3b7a908ed9c8eb13bc6fced5921bbab687e5138047e
+size 1361698
diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br
index c3d538dc19..9a8024b53a 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:b9fa8f0dc5f44969d694b19d371d7976105bdea8e9f3d7113804a8d80c7cac5c
-size 5494641
+oid sha256:213fa9d7e4ed577455f737c41ec5d89cca1cc4c42911dda935b52025b67f1268
+size 5511526
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 d5827179a9..3b99c78f03 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:f4e59125a297226613693f77356b2694285584a0971f7b896ecf8c77751b0b08
-size 917344
+oid sha256:7090d00428e328e67ec799255e92ccfaa0450552e8ae341a14ff621ce14f6a6c
+size 918367
diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br
index 5bfbab048c..87d3979807 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:35e98ff4bf9d93fd520f2d96933a7b1e95a6f3195a6ef9d9ed644c9bac57c2e3
-size 3900444
+oid sha256:2d49cc8be4ca250ebbb75ddfe0f7599cc344b2079fb85a3a534d4f31f9e80f9a
+size 3906763
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 e889fbb3d9..e0533f635b 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:28af9cbff2889103fff61ee8cde44029e247009d2bc789ea1d8921288b1644f6
-size 1004096
+oid sha256:0c04a452e02dd6552d61686923a1f8127f597393cd55d7f3758aa92ff49d67b7
+size 1007403
diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br
index 42ab3ec499..49cade7615 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:28a011cd1177b178266ba64cf075af797a3448763d5d75d293088d431df125ac
-size 5567067
+oid sha256:f6e93aff93582c6f0351c2ba7ad13285c81cd20b89df2c5c4de443f8f246d936
+size 5588466
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 01f479aeb3..1dd24b136e 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:eec146a09f0f00b2d4b6dc82a13107bfb74eb9e339c100c80feb76fb9bdc94c3
-size 906112
+oid sha256:ae2380d03729261801f0d4d4fdc20880c33530e23b073bd149a02e631a008af2
+size 906223
diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br
index 971f91045b..44c4ee6db9 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:f44c2aa6de5b991a72f97d6b77143d018f2365d21d429885def612a19f4e0d9d
-size 3806691
+oid sha256:dffbeb56b61e333b7c911a6fe66a28da5b98f0fcff8a2017ebd204c13b275b44
+size 3803575
diff --git a/middleware/cache-full-rendering.js b/middleware/cache-full-rendering.js
index fe737de374..70c3934d61 100644
--- a/middleware/cache-full-rendering.js
+++ b/middleware/cache-full-rendering.js
@@ -127,10 +127,6 @@ function setHeaders(headers, res) {
 }
 
 function mutateCheeriobodyByRequest($, req) {
-  // A fresh CSRF token into the <meta> tag
-  const freshCsrfToken = req.csrfToken()
-  $('meta[name="csrf-token"]').attr('content', freshCsrfToken)
-
   // Populate if you have the `dotcom_user` user cookie and it's truthy
   const isDotComAuthenticated = Boolean(req.cookies?.dotcom_user)
 
@@ -153,7 +149,6 @@ function mutateCheeriobodyByRequest($, req) {
   // See https://github.com/cheeriojs/cheerio/releases/tag/v1.0.0-rc.11
   // and https://github.com/cheeriojs/cheerio/pull/2509
   const parsedNextData = JSON.parse(nextData.get()[0].children[0].data)
-  parsedNextData.props.csrfToken = freshCsrfToken
   parsedNextData.props.dotComAuthenticatedContext.isDotComAuthenticated = isDotComAuthenticated
   parsedNextData.props.languagesContext.userLanguage = req.context.userLanguage
   parsedNextData.props.themeProps = {
diff --git a/package-lock.json b/package-lock.json
index c2841535b4..81963eb03d 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -18949,9 +18949,9 @@
       }
     },
     "node_modules/terser": {
-      "version": "5.14.0",
-      "resolved": "https://registry.npmjs.org/terser/-/terser-5.14.0.tgz",
-      "integrity": "sha512-JC6qfIEkPBd9j1SMO3Pfn+A6w2kQV54tv+ABQLgZr7dA3k/DL/OBoYSWxzVpZev3J+bUHXfr55L8Mox7AaNo6g==",
+      "version": "5.14.2",
+      "resolved": "https://registry.npmjs.org/terser/-/terser-5.14.2.tgz",
+      "integrity": "sha512-oL0rGeM/WFQCUd0y2QrWxYnq7tfSuKBiqTjRPWrRgB46WD/kiwHwF8T23z78H6Q6kGCuuHcPB+KULHRdxvVGQA==",
       "dev": true,
       "peer": true,
       "dependencies": {
@@ -33755,9 +33755,9 @@
       }
     },
     "terser": {
-      "version": "5.14.0",
-      "resolved": "https://registry.npmjs.org/terser/-/terser-5.14.0.tgz",
-      "integrity": "sha512-JC6qfIEkPBd9j1SMO3Pfn+A6w2kQV54tv+ABQLgZr7dA3k/DL/OBoYSWxzVpZev3J+bUHXfr55L8Mox7AaNo6g==",
+      "version": "5.14.2",
+      "resolved": "https://registry.npmjs.org/terser/-/terser-5.14.2.tgz",
+      "integrity": "sha512-oL0rGeM/WFQCUd0y2QrWxYnq7tfSuKBiqTjRPWrRgB46WD/kiwHwF8T23z78H6Q6kGCuuHcPB+KULHRdxvVGQA==",
       "dev": true,
       "peer": true,
       "requires": {
diff --git a/package.json b/package.json
index f5a8fdd5f0..b9b4123ab1 100644
--- a/package.json
+++ b/package.json
@@ -186,7 +186,7 @@
     "browser-test": "cross-env BROWSER=1 NODE_OPTIONS=--experimental-vm-modules JEST_PUPPETEER_CONFIG=jest-puppeteer.config.cjs jest tests/browser/browser.js",
     "build": "next build",
     "debug": "cross-env NODE_ENV=development ENABLED_LANGUAGES='en,ja' nodemon --inspect server.js",
-    "dev": "npm start",
+    "dev": "cross-env DISABLE_RENDERING_CACHE=true npm start",
     "lint": "eslint '**/*.{js,mjs,ts,tsx}'",
     "lint-translation": "cross-env NODE_OPTIONS=--experimental-vm-modules TEST_TRANSLATION=true jest tests/linting/lint-files.js",
     "prepare": "husky install",
diff --git a/pages/_app.tsx b/pages/_app.tsx
index bd7ea96b57..3ee87f43b8 100644
--- a/pages/_app.tsx
+++ b/pages/_app.tsx
@@ -16,7 +16,6 @@ import {
 import { defaultComponentTheme } from 'lib/get-theme.js'
 
 type MyAppProps = AppProps & {
-  csrfToken: string
   isDotComAuthenticated: boolean
   themeProps: typeof defaultComponentTheme & Pick<ThemeProviderProps, 'colorMode'>
   languagesContext: LanguagesContextT
@@ -25,7 +24,6 @@ type MyAppProps = AppProps & {
 const MyApp = ({
   Component,
   pageProps,
-  csrfToken,
   themeProps,
   languagesContext,
   dotComAuthenticatedContext,
@@ -59,8 +57,6 @@ const MyApp = ({
           name="google-site-verification"
           content="c1kuD-K2HIVF635lypcsWPoD4kilo5-jA_wBFyT4uMY"
         />
-
-        <meta name="csrf-token" content={csrfToken} />
       </Head>
       <SSRProvider>
         <ThemeProvider
@@ -95,7 +91,6 @@ MyApp.getInitialProps = async (appContext: AppContext) => {
   return {
     ...appProps,
     themeProps: getTheme(req),
-    csrfToken: req?.csrfToken?.() || '',
     languagesContext: { languages: req.context.languages, userLanguage: req.context.userLanguage },
     dotComAuthenticatedContext: { isDotComAuthenticated: Boolean(req.cookies?.dotcom_user) },
   }
diff --git a/tests/README.md b/tests/README.md
index 6a78f59bb2..980e5ac734 100644
--- a/tests/README.md
+++ b/tests/README.md
@@ -1,26 +1,26 @@
 ## Tests
 
-It's not strictly necessary to run tests locally while developing: You can
+It's not strictly necessary to run tests locally while developing. You can
 always open a pull request and rely on the CI service to run tests for you,
-but sometimes it's helpful to run tests locally before pushing your changes to
+but it's helpful to run tests locally before pushing your changes to
 GitHub.
 
-Test are written using [jest](https://ghub.io/jest), a framework maintained
-by Facebook and used by many teams at GitHub. Jest is convenient in that it
-provides everything: a test runner, an assertion library, code coverage analysis,
+Tests are written using [jest](https://ghub.io/jest), a framework maintained
+by Facebook and used by many teams at GitHub. 
+Jest provides everything: a test runner, an assertion library, code coverage analysis,
 custom reporters for different types of test output, etc.
 
 ### Install optional dependencies
 
-We typically rely on CI to run our tests, so we consider some large test-only
-dependencies **optional** (for example, puppeteer). In order to run the tests locally you'll
+We typically rely on CI to run our tests, so some large test-only
+dependencies are considered **optional** (for example, puppeteer). To run the tests locally, you'll
 need to make sure optional dependencies are installed by running:
 
 ```sh
 npm ci --include=optional
 ```
 
-If you run into the error "Could not find expected browser (chrome) locally" you may need to manually install the expected chromium version with:
+If you run into the error "Could not find expected browser (chrome) locally", you may need to install the expected chromium version manually with:
 ```
 node node_modules/puppeteer/install.js
 ```
@@ -36,10 +36,10 @@ script/test # or `npm test`
 
 ### Watching all the tests
 
-You can also run a script that will continually watch for changes and
-re-run the tests any time a change is made. This command will notify you
-when tests change to and from a passing or failing state, and will also print
-out a test coverage report, so you can see what files are in need of tests.
+You can run a script that continually watches for changes and
+re-runs the tests whenever a change is made. This command notifies you
+when tests change to and from a passing or failing state, and it prints
+out a test coverage report so you can see what files need testing.
 
 ```sh
 npm run test-watch
@@ -47,7 +47,7 @@ npm run test-watch
 
 ### Running individual tests
 
-You can run specific tests in one of these two ways:
+You can run specific tests in two ways:
 
 ```sh
 # The TEST_NAME can be a filename, partial filename, or path to a file or directory
@@ -79,25 +79,26 @@ npm run lint
 
 ### Keeping the server running
 
-When you run `jest` tests, that depend on making real HTTP requests
+When you run `jest` tests that depend on making real HTTP requests
 to `localhost:4000`, the `jest` tests have a hook that starts the
-server before running all/any tests, and stops the server when it's done.
+server before running all/any tests and stops the server when done.
 
-You can disable that, which might make it easier when debugging tests
+You can disable this, which might make it easier when debugging tests
 since the server won't need to start and stop every time you run tests.
 
-In one terminal type:
+In one terminal, type:
 
 ```sh
 NODE_ENV=test PORT=4000 node server.js
 ```
 
-and then, in another terminal type:
+In another terminal, type:
 
 ```sh
 START_JEST_SERVER=false jest tests/rendering/foo/bar.js
 ```
 
-Or whatever the testing command you use. Note the `START_JEST_SERVER=false`
-environment variable that needs to be set or else, `jest` will try to start
+Or whatever the testing command you use is. 
+
+The `START_JEST_SERVER` environment variable needs to be set to `false`, or else `jest` will try to start
 a server on `:4000` too.
diff --git a/tests/browser/browser.js b/tests/browser/browser.js
index ace2eac45f..871ae2b226 100644
--- a/tests/browser/browser.js
+++ b/tests/browser/browser.js
@@ -165,15 +165,6 @@ describe('survey', () => {
   })
 })
 
-describe('csrf meta', () => {
-  it('should have a csrf-token meta tag on the page', async () => {
-    await page.goto(
-      'http://localhost:4000/en/actions/getting-started-with-github-actions/about-github-actions'
-    )
-    await page.waitForSelector('meta[name="csrf-token"]')
-  })
-})
-
 describe('platform picker', () => {
   // from tests/javascripts/user-agent.js
   const userAgents = [
diff --git a/tests/rendering/render-caching.js b/tests/rendering/render-caching.js
index 49c0a2442d..91622f541a 100644
--- a/tests/rendering/render-caching.js
+++ b/tests/rendering/render-caching.js
@@ -17,28 +17,6 @@ const serializeTheme = (theme) => {
 describe('in-memory render caching', () => {
   jest.setTimeout(30 * 1000)
 
-  test('second render should be a cache hit with different csrf-token', async () => {
-    const res = await get('/en')
-    // Because these are effectively end-to-end tests, you can't expect
-    // the first request to be a cache miss because another end-to-end
-    // test might have "warmed up" this endpoint.
-    expect(res.headers['x-middleware-cache']).toBeTruthy()
-    const $1 = cheerio.load(res.text)
-    const res2 = await get('/en')
-    expect(res2.headers['x-middleware-cache']).toBe('hit')
-    const $2 = cheerio.load(res2.text)
-    const csrfTokenHTML1 = $1('meta[name="csrf-token"]').attr('content')
-    const csrfTokenHTML2 = $2('meta[name="csrf-token"]').attr('content')
-    expect(csrfTokenHTML1).not.toBe(csrfTokenHTML2)
-    // The HTML is one thing, we also need to check that the
-    // __NEXT_DATA__ serialized (JSON) state is different.
-    const csrfTokenNEXT1 = getNextData($1).props.csrfToken
-    const csrfTokenNEXT2 = getNextData($2).props.csrfToken
-    expect(csrfTokenHTML1).toBe(csrfTokenNEXT1)
-    expect(csrfTokenHTML2).toBe(csrfTokenNEXT2)
-    expect(csrfTokenNEXT1).not.toBe(csrfTokenNEXT2)
-  })
-
   test('second render should be a cache hit with different dotcom-auth', async () => {
     // Anonymous first
     const res = await get('/en')
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
index 6230ff75ff..a18a2a3a48 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
@@ -1,21 +1,50 @@
 ---
 title: Administrar los ajustes de accesibilidad
-intro: 'Puedes inhabilitar las teclas de atajo de {% data variables.product.prodname_dotcom %} en tus ajustes de accesibilidad.'
+shortTitle: Manage accessibility settings
+intro: '{% data variables.product.product_name %}''s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs.'
 versions:
   feature: keyboard-shortcut-accessibility-setting
 redirect_from:
   - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings
+type: how_to
+miniTocMaxHeadingLevel: 3
 ---
 
 ## Acerca de los ajustes de accesibilidad
 
-{% data variables.product.product_name %} incluye varios atajaos de teclado para que puedas realizar acciones en todo el sitio sin utilizar tu mouse para navegar. Si bien los atajos son útiles para ahorrar tiempo, algunas veces estos pueden hacer que {% data variables.product.prodname_dotcom %} sea más difícil de utilizar y menos accesible.
+To accommodate your vision, hearing, motor, cognitive, or learning needs, you can customize the user interface for {% data variables.product.product_location %}.
 
-Todos los atajos de teclado se habilitan predeterminadamente en {% data variables.product.product_name %}, pero puedes elegir inhabilitar los atajos con teclas de caracteres en tus ajustes de accesibilidad. Este ajuste no afecta los atajos de teclado que proporciona tu buscador web o los atajos de {% data variables.product.prodname_dotcom %} que utilizan una tecla modificadora, tal como <kbd>Control</kbd> o <kbd>Command</kbd>.
+## Administrar los ajustes de accesibilidad
 
-## Administrar los atajos de tecla de carácter
+You can decide whether you want to use some or all keyboard shortcuts on {% ifversion fpt or ghec %}{% data variables.product.product_location %}{% elsif ghes or ghae %}the website for {% data variables.product.product_location %}{% endif %}, and you can control the display of animated images.
+
+### Managing keyboard shortcuts
+
+You can perform actions across the {% data variables.product.product_name %} website without using your mouse by using your keyboard instead. Keyboard shortcuts can be useful to save time for some people, but may interfere with accessibility if you don't intend to use the shortcuts.
+
+By default, all keyboard shortcuts are enabled on {% data variables.product.product_name %}. Para obtener más información, consulta "[Atajos del teclado](/get-started/using-github/keyboard-shortcuts)".
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.accessibility_settings %}
-1. Selecciona o deselecciona la casilla de verificación **Habilitar las teclas de atajo**. ![Captura de pantalla de la casilla de verificación de 'Habilitar los atajos de tecla de carácter'](/assets/images/help/settings/disable-character-key-shortcuts.png)
-2. Haz clic en **Save ** (guardar).
+1. Under "Keyboard shortcuts", manage settings for your keyboard shortcuts.
+
+   - Optionally, to disable or enable shortcut keys that don't use modifiers keys like <kbd>Control</kbd> or <kbd>Command</kbd>, under "General", deselect **Character keys**. If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key.
+{%- ifversion command-palette %}
+   - Optionally, to customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)."
+   {%- endif %}
+
+{% ifversion motion-management %}
+
+### Managing motion
+
+You can control how {% data variables.product.product_name %} displays animated images.
+
+By default, {% data variables.product.product_name %} syncs with your system-level preference for reduced motion. For more information, see the documentation or settings for your operating system.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.accessibility_settings %}
+1. Under "Motion", manage settings for motion.
+
+   - Optionally, to control how {% data variables.product.product_name %} displays animaged images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**.
+
+{% endif %}
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 078cdc100e..111bc5221c 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
@@ -185,7 +185,7 @@ on:
   deployment_status
 ```
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 ### `debate`
 
 | Carga del evento Webhook                                                                     | Tipos de actividad                                                                                                                                                                                                                                                                                      | `GITHUB_SHA`                                  | `GITHUB_REF`        |
diff --git a/translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md b/translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md
index 39a8450186..2b08a53f79 100644
--- a/translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md
+++ b/translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md
@@ -57,7 +57,7 @@ El conjunto de instrucciones de las SSSE3 se requiere porque el {% data variable
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.advanced-security-tab %}
-1. Under "Security," click **{% data variables.product.prodname_secret_scanning_caps %}**. ![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png)
+1. Debajo de "Seguridad", haz clic en **{% data variables.product.prodname_secret_scanning_caps %}**. ![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 ## Inhabilitar las {% data variables.product.prodname_secret_scanning %}
@@ -67,5 +67,5 @@ El conjunto de instrucciones de las SSSE3 se requiere porque el {% data variable
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.advanced-security-tab %}
-1. Under "Security," unselect **{% data variables.product.prodname_secret_scanning_caps %}**. ![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png)
+1. Debajo de "Seguridad", deselecciona **{% data variables.product.prodname_secret_scanning_caps %}**. ![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
index 2c3f645f37..a9c9b79a9a 100644
--- a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
@@ -10,8 +10,6 @@ topics:
 shortTitle: Estadísticas del servidor
 ---
 
-{% data reusables.server-statistics.release-phase %}
-
 ## Acerca de las {% data variables.product.prodname_server_statistics %}
 
 {% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.product.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index a5122d52e4..71543e2a68 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -737,6 +737,20 @@ This utility rewrites the imported repository. This gives you a chance to rename
 git-import-rewrite
 ```
 
+{% ifversion ghes > 3.3 %}
+
+## Security
+
+### ghe-find-insecure-git-operations
+
+This utility searches your instance's logs and identifies Git operations over SSH that use insecure algorithms or hash functions, including DSA, RSA-SHA-1, HMAC-SHA-1, and CBC ciphers. You can use the output to support each client's transition to a more secure SSH connection. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server){% ifversion ghes < 3.6 %}.{% elsif ghes > 3.5 %} and "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."{% endif %}
+
+```shell
+ghe-find-insecure-git-operations
+```
+
+{% endif %}
+
 ## Support
 
 ### ghe-diagnostics
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 9c35c7e42b..e9c33c84ef 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
@@ -73,6 +73,18 @@ Los propietarios de las empresas pueden configurar los correos electrónicos par
 5. Cuando el correo electrónico de prueba es exitoso, en la parte inferior de la página, haz clic en **Guardar parámetros**. ![Botón Guardar parámetros](/assets/images/enterprise/management-console/save-settings.png)
 {% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
 
+{% ifversion require-tls-for-smtp %}
+## Enforcing TLS for SMTP connections
+
+You can enforce TLS encryption for all incoming SMTP connections, which can help satisfy an ISO-27017 certification requirement.
+
+{% data reusables.enterprise_site_admin_settings.email-settings %}
+1. Under "Authentication," select **Enforce TLS auth (recommended)**.
+
+   ![Screenshot of the "Enforce TLS auth (recommended)" checkbox](/assets/images/enterprise/configuration/enforce-tls-for-smtp-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+{% endif %}
+
 ## Configurar DNS y parámetros de firewall para permitir correos electrónicos entrantes
 
 Si quieres permitir respuestas de correo electrónico para las notificaciones, debes configurar los parámetros de tu DNS.
@@ -80,7 +92,7 @@ Si quieres permitir respuestas de correo electrónico para las notificaciones, d
 1. Asegúrate de que el puerto 25 en la instancia esté accesible para tu servidor SMTP.
 2. Crea un registro A que apunte a `reply.[hostname]`. Dependiendo de tu proveedor DNS y de la configuración del host de instancia, es posible que puedas crear un registro A único que apunte a `*.[hostname]`.
 3. Crea un registro MX que apunte a `reply.[hostname]` para que los correos electrónicos para ese dominio sean enrutados a la instancia.
-4. Crea un registro MX que apunte a `noreply.[hostname]` para `[hostname]` para que las respuestas a la dirección `cc` en los correos electrónicos para notificación sean enrutados a la instancia. Para obtener más información, consulta la sección {% ifversion ghes %}"[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[Acerca de las notificaciones por correo electrónico](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}".
+4. Crea un registro MX que apunte a `noreply.[hostname]` para `[hostname]` para que las respuestas a la dirección `cc` en los correos electrónicos para notificación sean enrutados a la instancia. For more information, see {% ifversion ghes %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."
 
 ## Solución de problemas de entrega de correo electrónico
 
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
new file mode 100644
index 0000000000..dd05637a5b
--- /dev/null
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
@@ -0,0 +1,47 @@
+---
+title: Configuring host keys for your instance
+shortTitle: Configure host keys
+intro: 'You can increase the security of {% data variables.product.product_location %} by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections.'
+permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.'
+versions:
+  ghes: '>= 3.6'
+type: how_to
+topics:
+  - Authentication
+  - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
+  - SSH
+---
+
+## About host keys for your instance
+
+Servers that accept SSH connections advertise one or more cryptographic host keys to securely identify the server to SSH clients. To confirm the server's identity during the initialization of a connection, clients store and verify the host key. For more information, see [SSH Host Key - What, Why, How](https://ssh.com/academy/ssh/host-key) on the SSH Academy website.
+
+{% data reusables.enterprise.about-ssh-ports %}
+
+By default, {% data variables.product.product_location %} generates and advertises host keys with OpenSSH-style host key rotation. To increase the security of SSH in your environment, you can enable additional algorithms for the generation of host keys.
+
+{% note %}
+
+**Note**: If you enable additional host key algorithms, clients that do not use OpenSSH for SSH connections may experience warnings during connection, or fail to connect entirely. Some SSH implementations can ignore unsupported algorithms and fall back to a different algorithm. If the client does not support fallback, the connection will fail. For example, the SSH library for Go does not support fallback to a different algorithm.
+
+{% endnote %}
+
+## Managing an Ed25519 host key
+
+To improve security for clients that connect to {% data variables.product.product_location %}, you can enable the generation and advertisement of an Ed25519 host key. Ed25519 is immune to some attacks that target older signature algorithms, without sacrificing speed. Older SSH clients may not support Ed25519. By default, {% data variables.product.product_name %} instances do not generate or advertise an Ed25519 host key. For more information, see [the Ed25519 website](https://ed25519.cr.yp.to).
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+1. To enable generation and advertisement of the Ed25519 host key, enter the following command.
+
+   ```shell
+   ghe-config app.babeld.host-key-ed25519 true
+   ```
+1. Optionally, enter the following command to disable generation and advertisement of the Ed25519 host key.
+
+   ```shell
+   ghe-config app.babeld.host-key-ed25519 false
+   ```
+{% data reusables.enterprise.apply-configuration %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
new file mode 100644
index 0000000000..a4a9f29fe1
--- /dev/null
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
@@ -0,0 +1,53 @@
+---
+title: Configuring SSH connections to your instance
+shortTitle: Configure SSH connections
+intro: 'You can increase the security of {% data variables.product.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.'
+permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.'
+versions:
+  ghes: '>= 3.6'
+type: how_to
+topics:
+  - Authentication
+  - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
+  - SSH
+---
+
+## About SSH connections to your instance
+
+{% data reusables.enterprise.about-ssh-ports %}
+
+To accommodate the SSH clients in your environment, you can configure the types of connections that {% data variables.product.product_location %} will accept.
+
+## Configuring SSH connections with RSA keys
+
+When users perform Git operations on {% data variables.product.product_location %} via SSH over port 22, the client can authenticate with an RSA key. The client may sign the attempt using the SHA-1 hash function. In this context, the SHA-1 hash function is no longer secure. For more information, see [SHA-1](https://en.wikipedia.org/wiki/SHA-1) on Wikipedia.
+
+By default{% ifversion ghes < 3.7 %} on {% data variables.product.product_name %} 3.6 and later{% endif %}, SSH connections that satisfy **both** of the following conditions will fail.
+
+{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %}
+
+You can adjust the cutoff date. If the user uploaded the RSA key before the cutoff date, the client can continue to connect successfuly using SHA-1 as long as the key remains valid. Alternatively, you can reject all SSH connections authenticated with an RSA key if the client signs the connection using the SHA-1 hash function.
+
+Regardless of the setting you choose for your instance, clients can continue to connect using any RSA key signed with a SHA-2 hash function.
+
+If you use an SSH certificate authority, connections will fail if the certificate's `valid_after` date is after the cutoff date. Para obtener más información, consulta la sección [Acerca de las autoridades de certificados SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)".
+
+Para obtener más información, consulta [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server).
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+1. Audit your instance's logs for connections that use unsecure algorithms or hash functions using the `ghe-find-insecure-git-operations` utility. Para obtener más información, consulta la sección "[Utilidades de línea de comandos](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-find-insecure-git-operations)".
+1. To configure a cutoff date after which {% data variables.product.product_location %} will deny connections from clients that use an RSA key uploaded after the date if the connection is signed by the SHA-1 hash function, enter the following command. Replace _**RFC-3399-UTC-TIMESTAMP**_ with a valid RFC 3399 UTC timestamp. For example, the default value, August 1, 2022, would be represented as `2022-08-01T00:00:00Z`. For more information, see [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) on the IETF website.
+
+   <pre>
+   $ ghe-config app.gitauth.rsa-sha1 <em>RFC-3339-UTC-TIMESTAMP</em>
+   </pre>
+
+1. Alternatively, to completely disable SSH connections using RSA keys that are signed with the SHA-1 hash function, enter the following command.
+
+   ```shell
+   ghe-config app.gitauth.rsa-sha1 false
+   ```
+{% data reusables.enterprise.apply-configuration %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md
index fbd9346b17..04e24543f3 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md
@@ -25,6 +25,7 @@ children:
   - /site-admin-dashboard
   - /enabling-private-mode
   - /managing-github-mobile-for-your-enterprise
+  - /configuring-ssh-connections-to-your-instance
   - /configuring-email-for-notifications
   - /verifying-or-approving-a-domain-for-your-enterprise
   - /configuring-rate-limits
@@ -34,6 +35,7 @@ children:
   - /command-line-utilities
   - /restricting-network-traffic-to-your-enterprise
   - /configuring-github-pages-for-your-enterprise
+  - /configuring-host-keys-for-your-instance
   - /configuring-the-referrer-policy-for-your-enterprise
   - /configuring-custom-footers
   - /configuring-web-commit-signing
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 076efb9082..783e674d3f 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
@@ -40,7 +40,7 @@ Después, {% else %}Primero,{% endif %} decide si permitirás acciones {% ifvers
 Considera combinar OpenID Connect (OIDC) con los flujos de trabajo reutilizables para requerir despliegues continuos a lo largo de tu repositorio, organización o empresa. Puedes hacerlo si defines las condiciones de confianza en los roles de la nube con base en los flujos reutilizables. Para obtener más información, consulta la sección "[Utilizar OpenID Connect con flujos de trabajo reutilizables](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)".
 {% endif %}
 
-Puedes acceder a la información sobre la actividad relacionada con las {% data variables.product.prodname_actions %} en las bitácoras de auditoría de tu empresa. Si tus necesidades de negocio requieren que retengas bitácoras de auditoría por más de seis meses, planea cómo exportarás y almacenarás estos datos fuera de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta las secciones {% ifversion ghec %}"[Transmitir la bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)" y "[Exportar la actividad de tu bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)".{% else %}"[Reenvío de bitácoras](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)".{% endif %}
+Puedes acceder a la información sobre la actividad relacionada con las {% data variables.product.prodname_actions %} en las bitácoras de auditoría de tu empresa. If your business needs require retaining this information longer than audit log data is retained, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)" and "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."{% else %}{% ifversion audit-log-streaming %}"[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)" and {% endif %}"[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."{% endif %}
 
 ![Entradas de la bitácora de auditoría](/assets/images/help/repository/audit-log-entries.png)
 
diff --git a/translations/es-ES/content/admin/guides.md b/translations/es-ES/content/admin/guides.md
index 8888ce5416..41b3562712 100644
--- a/translations/es-ES/content/admin/guides.md
+++ b/translations/es-ES/content/admin/guides.md
@@ -52,6 +52,8 @@ includeGuides:
   - /admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise
   - /admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise
   - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud
+  - /admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance
+  - /admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance
   - /admin/configuration/enabling-and-scheduling-maintenance-mode
   - /admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise
   - /admin/configuration/enabling-private-mode
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 f09ca16359..ed71174e55 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
@@ -19,113 +19,113 @@ topics:
 
 {% ifversion ghec %}
 
-Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources.
+Los propietarios de empresa en {% data variables.product.product_name %} pueden controlar los requisitos para la autenticación y el acceso a los recursos empresariales.
 
-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.
+Puedes elegir permitir que los miembros creen y administren cuentas de usuarios o tu empresa puede crear y administrar cuentas para los miembros con las {% data variables.product.prodname_emus %}. Si permites que los miembros administren sus propias cuentas, también puedes configurar la autenticación de SAML tanto para incrementar la seguridad como para centralizar la identidad y el acceso para las aplicaciones web que utiliza tu equipo.
 
-After learning more about these options, to determine which method is best for your enterprise, see "[Identifying the best authentication method for your enterprise](#identifying-the-best-authentication-method-for-your-enterprise)."
+Después de aprender más sobre estas opciones, para determinar el mejor método para tu empresa, consulta la sección "[Identificar el mejor método de autenticación para tu empresa](#identifying-the-best-authentication-method-for-your-enterprise)".
 
 ## 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 %}.
+Las siguientes opciones están disponibles para la administración y autenticación de cuentas en {% data variables.product.product_name %}.
 
 - [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)
-- [Authentication with {% data variables.product.prodname_emus %} and federation](#authentication-with-enterprise-managed-users-and-federation)
+- [Autenticación con {% data variables.product.prodname_emus %} y federación](#authentication-with-enterprise-managed-users-and-federation)
 
 ### Autenticación mediante {% data variables.product.product_location %}
 
-By default, each member must create a personal account on {% data variables.product.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after signing into the account on {% data variables.product.product_location %}. The member manages the account, and can contribute to other enterprises, organizations, and repositories on {% data variables.product.product_location %}.
+Predeterminadamente, cada miembro debe crear una cuenta personal en {% data variables.product.product_location %}. Otorgarás acceso a tu empresa y el miembro podrá acceder a los recursos de ella después de iniciar sesión en la cuenta de {% data variables.product.product_location %}. El miembro administra la cuenta y puede contribuir con otras empresas, organizaciones y repositorios en {% data variables.product.product_location %}.
 
 ### Autenticación mediante {% data variables.product.product_location %} con restricción de acceso adicional de SAML
 
-If you configure additional SAML access restriction, each member must create and manage a personal account on {% data variables.product.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after both signing into the account on {% data variables.product.product_location %} and successfully authenticating with your SAML identity provider (IdP). The member can contribute to other enterprises, organizations, and repositories on {% data variables.product.product_location %} using their personal account. For more information about requiring SAML authentication for all access your enterprise's resources, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)."
+Si configuras una restricción adicional de acceso de SAML, cada miembro debe crear y administrar una cuenta personal en {% data variables.product.product_location %}. Otorgarás acceso a tu empresa y el miembro podrá acceder a los recursos de ella después de que ambos inicien sesión en la cuenta de {% data variables.product.product_location %} y se autentiquen exitosamente con tu proveedor de identidad de SAML (IdP). El miembro puede contribuir con otras empresas, organizaciones y repositorios en {% data variables.product.product_location %} utilizando su cuenta personal. Para obtener más información sobre cómo requerir la autenticación de SAML para todo el acceso a los recursos de tu empresa, consulta la sección "[Acerca de SAML para la IAM empresarial](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)".
 
-If you use a standalone organization with {% data variables.product.product_name %}, or if you don't want to use SAML authentication for every organization in your enterprise, you can configure SAML for an individual organization. Para obtener más información, consulta la sección "[Acerca de la administración de identidad y accesos con el inicio de sesión único de SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)".
+Si utilizas una organización independiente con {% data variables.product.product_name %} o si no quieres utilizar la autenticación de SAML para cada organización de tu empresa, puedes configurar SAML para una organización individual. Para obtener más información, consulta la sección "[Acerca de la administración de identidad y accesos con el inicio de sesión único de SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)".
 
-### Authentication with {% data variables.product.prodname_emus %} and federation
+### Autenticación con {% data variables.product.prodname_emus %} y federación
 
-If you need more control of the accounts for your enterprise members on {% data variables.product.product_location %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.product.product_location %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)".
+Si necesitas más control sobre las cuentas para tus miembros empresariales en {% data variables.product.product_location %}, puedes utilizar las {% data variables.product.prodname_emus %}. Con las {% data variables.product.prodname_emus %}, puedes aprovisionar y administrar cuentas para los miembros de tu empresa en {% data variables.product.product_location %} utilizando tu IdP. Cada miembro inicia sesión en una cuenta que tú creas y tu empresa la administra. Las contribuciones con el resto de {% data variables.product.prodname_dotcom_the_website %} se restringen. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)".
 
-## Identifying the best authentication method for your enterprise
+## Identificar el mejor método de autenticación para tu empresa
 
-Both SAML SSO and {% data variables.product.prodname_emus %} increase security for your enterprise's resources. {% data variables.product.prodname_emus %} additionally allows you to control the user accounts for your enterprise members and restricts what the accounts are able to do. However, those restrictions may be unacceptable for your enterprise if they obstruct your developers' workflows.
+Tanto el SSO de SAML como las {% data variables.product.prodname_emus %} aumentan la seguridad para los recursos de tu empresa. {% data variables.product.prodname_emus %} te permite adicionalmente controlar las cuentas de usuario de tus miembros empresariales y restringe lo que las cuentas pueden hacer. Sin embargo, dichas restricciones podrían ser inaceptables para tu empresa si obstruyen los flujos de trabajo de tus desarrolladores.
 
-To determine whether your enterprise would benefit more from SAML SSO or {% data variables.product.prodname_emus %}, ask yourself these questions.
+Para determinar si tu empresa se beneficiaría más del SSO de SAML o de {% data variables.product.prodname_emus %}, hazte estas preguntas.
 
-- [Do you want to control the user accounts for your users?](#do-you-want-to-control-the-user-accounts-for-your-users)
-- [Which identity provider does your enterprise use?](#which-identity-provider-does-your-enterprise-use)
-- [Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites?](#do-your-developers-work-in-public-repositories-gists-or-github-pages-sites)
-- [Do your developers rely on collaboration outside of your enterprise?](#do-your-developers-rely-on-collaboration-outside-of-your-enterprise)
-- [Does your enterprise rely on outside collaborators?](#does-your-enterprise-rely-on-outside-collaborators)
-- [Can your enterprise tolerate migration costs?](#can-your-enterprise-tolerate-migration-costs)
+- [¿Quieres controlar las cuentas de usuario de tus usuarios?](#do-you-want-to-control-the-user-accounts-for-your-users)
+- [¿Qué proveedor de identidad utiliza tu empresa?](#which-identity-provider-does-your-enterprise-use)
+- [¿Tus desarrolladores trabajan en repositorios públicos, gists, o sitios de {% data variables.product.prodname_pages %}?](#do-your-developers-work-in-public-repositories-gists-or-github-pages-sites)
+- [¿Tus desarrolladores confían en la colaboración fuera de tu empresa?](#do-your-developers-rely-on-collaboration-outside-of-your-enterprise)
+- [¿Tu empresa depende de colaboradores externos?](#does-your-enterprise-rely-on-outside-collaborators)
+- [¿Tu empresa puede tolerar los costos de migración?](#can-your-enterprise-tolerate-migration-costs)
 
-### Do you want to control the user accounts for your users?
+### ¿Quieres controlar las cuentas de usuario de tus usuarios?
 
-{% data variables.product.prodname_emus %} may be right for your enterprise if you don't want enterprise members to use their own personal accounts on {% data variables.product.prodname_dotcom_the_website %} to access your enterprise's resources.
+Es posible que {% data variables.product.prodname_emus %} sea correcto para tu empresa si no quieres que los miembros empresariales utilicen sus propias cuentas en {% data variables.product.prodname_dotcom_the_website %} para acceder a los recursos de esta.
 
-With SAML SSO, developers create and manage their own personal accounts, and each account is linked to a SAML identity in your IdP. {% data variables.product.prodname_emus %} functions more like other familiar SSO solutions, as you will provision the accounts for your users. You can also ensure user accounts conform with your company identity, by controlling usernames and the email addresses associated with the accounts.
+Con el SSO de SAML, los desarrolladores crean y administran sus propias cuentas personales y cada una de ellas se enlaza con una identidad de SAML en tu IdP. {% data variables.product.prodname_emus %} funciona similar a otras soluciones de SSO comunes, ya que aprovisonarás las cuentas para tus usuarios. También puedes asegurarte de que las cuentas de usuario se adecuen a la identidad de tu empresa al controlar los nombres de usuario y las direcciones de correo electrónico asociadas con las cuentas.
 
-If you currently require your users to create a new account on {% data variables.product.prodname_dotcom_the_website %} to use with your enterprise only, {% data variables.product.prodname_emus %} might be right for you. However, SAML SSO may be a better option if using your IdP as the source of truth for your user and access management would add too much complexity. For example, perhaps your enterprise does not have an established process for onboarding new users in your IdP.
+Si actualmente requieres que tus usuarios creen una cuenta nueva en {% data variables.product.prodname_dotcom_the_website %} para utilizarla únicamente con tu empresa, {% data variables.product.prodname_emus %} podría ser lo correcto para ti. Sin embargo, el SSO de SAML podría ser una mejor opción si utilizas tu IdP como la fuente de verdad para tu usuario y la administración de accesos agregaría demasiada complejidad. Por ejemplo, tal vez tu empresa no tenga un proceso establecido para integrar a los usuarios nuevos en tu IdP.
 
-### Which identity provider does your enterprise use?
+### ¿Qué proveedor de identidad utiliza tu empresa?
 
-{% data variables.product.prodname_emus %} is supported for a limited number of IdPs, while SAML SSO offers full support for a larger number of IdPs, plus limited support for all IdPs that implement the SAML 2.0 standard. Para obtener la lista de IdP compatibles para cada opción, consulta las secciones "[Acerca de las {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#identity-provider-support)" y "[Acerca de SAML para el IAM empresarial](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam#supported-idps)".
+{% data variables.product.prodname_emus %} es compatible para una cantidad limitada de IdP, mientras que el SSO de SAML ofrece compatibilidad total para una cantidad más grande de IdP además de la compatibilidad limitada para todos los IdP que implementan el estándar de SAML 2.0. Para obtener la lista de IdP compatibles para cada opción, consulta las secciones "[Acerca de las {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#identity-provider-support)" y "[Acerca de SAML para el IAM empresarial](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam#supported-idps)".
 
-You can use {% data variables.product.prodname_emus %} with an unsupported IdP only if you federate the unsupported IdP to a supported IdP to use as an integration point. If you wish to avoid this extra complexity, SAML SSO may be a better solution for you.
+Puedes utilizar las {% data variables.product.prodname_emus %} con un IdP no compatible únicamente si federas el IdP incompatible hacia un IdP compatible para utilizarlo como punto de integración. Si quieres evitar esta complejidad adicional, el SSO de SAML podría ser una mejor solución para ti.
 
-### Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites?
+### ¿Tus desarrolladores trabajan en repositorios públicos, gists, o sitios de {% data variables.product.prodname_pages %}?
 
-To prevent enterprise members from accidentally leaking corporate-owned content to the public on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} imposes strong restrictions on what users can do. For example, {% data variables.product.prodname_managed_users %} cannot create public repositories, gists of any visibility, or {% data variables.product.prodname_pages %} sites that are visible outside the enterprise. For a full list of restrictions, see "[Abilities and restrictions of {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)."
+Para prevenir que los miembros de la empresa filtren accidentalmente contenido que le pertenezca a ella al público en {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} impone restricciones fuertes sobre lo que pueden hacer los usuarios. Por ejemplo, los {% data variables.product.prodname_managed_users %} no pueden crear repositorios públicos, gists de ningún tipo de visibilidad, ni sitios de {% data variables.product.prodname_pages %} que puedan verse desde fuera de la empresa. Para ver una lista completa de restricciones, consulta la sección "[Capacidades y restricciones de los {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)".
 
-These restrictions are unacceptable for some enterprises. To determine whether {% data variables.product.prodname_emus %} will work for you, review the restrictions with your developers, and confirm whether any of the restrictions will hinder your existing workflows. If so, SAML SSO may be a better choice for your enterprise.
+Estas restricciones no son aceptables para algunas empresas. Para determinar si {% data variables.product.prodname_emus %} te funcionará, revisa las restricciones con tus desarrolladores y confirma si cualquiera de ellas dificultará los flujos de trabajo existentes. En este caso, el SSO de SAML podría ser una mejor elección para tu empresa.
 
-### Do your developers rely on collaboration outside of your enterprise?
+### ¿Tus desarrolladores confían en la colaboración fuera de tu empresa?
 
-{% data variables.product.prodname_managed_users_caps %} can only contribute to repositories within your enterprise. If your developers need to collaborate in repositories outside your enterprise, even private repositories, to complete their work, {% data variables.product.prodname_emus %} may not be right for your enterprise, and SAML SSO may be a better solution.
+{% data variables.product.prodname_managed_users_caps %} solo puede contribuir con los repositorios dentro de tu empresa. Si tus desarrolladores necesitan colaborar en repositorios externos a tu empresa, incluso si estos son privados, para completar su trabajo, {% data variables.product.prodname_emus %} podría no ser lo correcto para tu empresa y el SSO de SAML podría ser una mejor solución.
 
-### Does your enterprise rely on outside collaborators?
+### ¿Tu empresa depende de colaboradores externos?
 
-With SAML SSO, you can give access to specific repositories to people who are not members of your IdP's directory, by using the outside collaborator role. This can be especially useful for collaborators that are external to your business, such as contractors. For more information, see "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."
+Con el SSO de SAML puedes otorgar acceso a repositorios específicos para las personas que no sean miembros del directorio de tu IdP si utilizas el rol de colaborador externo. Esto puede ser especialmente útil para los colaboradores que son externos a tu negocio, tal como los contratistas. Para obtener más información, consulta la sección "[Agregar colaboradores externos a los repositorios de tu organización](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)".
 
-With {% data variables.product.prodname_emus %}, the outside collaborator role does not exist. Your enterprise's resources can only be accessed by {% data variables.product.prodname_managed_users %}, which are always provisioned by your IdP. To give external collaborators access to your enterprise, you would have to use guest accounts in your IdP. If you're interested in {% data variables.product.prodname_emus %}, confirm with your developers whether this will hinder any of their existing workflows. If so, SAML SSO may be a better solution.
+Con {% data variables.product.prodname_emus %}, el rol de colaborador externo no existe. Solo se puede acceder a los recursos de tu empresa mediante {% data variables.product.prodname_managed_users %}, lo cual siempre se aprovisiona en tu IdP. Para dar acceso a tu empresa a los colaboradores externos, necesitarás utilizar cuentas de invitado en tu IdP. Si te interesa {% data variables.product.prodname_emus %}, confirma con tus desarrolladores si esto dificultará cualquiera de sus flujos de trabajo existentes. En este caso, el SSO de SAML podría ser una mejor solución.
 
-### Can your enterprise tolerate migration costs?
+### ¿Tu empresa puede tolerar los costos de migración?
 
-If your enterprise is new to {% data variables.product.prodname_dotcom_the_website %}, SAML SSO and {% data variables.product.prodname_emus %} are equally easy to adopt.
+Si tu empresa es nueva en {% data variables.product.prodname_dotcom_the_website %}, el SSO de SAML y {% data variables.product.prodname_emus %} se pueden adoptar con la misma facilidad.
 
-If you're already using {% data variables.product.prodname_dotcom_the_website %} with developers managing their own user accounts, adopting {% data variables.product.prodname_emus %} requires migrating to a new enterprise account. For more information, see "[About enterprises with {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)."
+Si ya estás utilizando {% data variables.product.prodname_dotcom_the_website %} con los desarrolladores que administran sus propias cuentas de usuario, el adoptar {% data variables.product.prodname_emus %} requerirá una migración a una cuenta empresarial nueva. Para obtener más información, consulta la sección "[Acerca de las empresas con {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)".
 
-Although {% data variables.product.prodname_emus %} is free, the migration process may require time or cost from your team. Confirm that this migration process is acceptable to your business and your developers. If not, SAML SSO may be the better choice for you.
+Aunque {% data variables.product.prodname_emus %} es gratuito, el proceso de migración podría requerir tiempo o costos para tu equipo. Confirma que este proceso de migración es aceptable para tu negocio y tus desarrolladores. De lo contrario, el SSO de SAML podría ser una mejor opción para ti.
 
 {% elsif ghes %}
 
-Site administrators can decide how people authenticate to access a {% data variables.product.product_name %} instance. You can use {% data variables.product.product_name %}'s built-in authentication, or, if you want to centralize identity and access management for the web applications that your team uses, you can configure an external authentication method.
+Los administradores de sitio pueden decidir cómo se autentican las personas para acceder a la instancia de {% data variables.product.product_name %}. Puedes utilizar la autenticación integrada de {% data variables.product.product_name %} o, si quieres centralizar la administración de acceso e identidad para las aplicaciones web que utiliza tu equipo, puedes configurar un método de autenticación externo.
 
 ## Métodos de autenticación para {% data variables.product.product_name %}
 
-The following authentication methods are available for {% data variables.product.product_name %}.
+Los siguientes métodos de autenticación están disponibles para {% data variables.product.product_name %}.
 
 - [Autenticación incorporada](#built-in-authentication)
 - [Autenticación externa](#external-authentication)
 
 ### Autenticación incorporada
 
-{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} To access your instance, people authenticate with the credentials for the account. Para obtener más información, consulta la sección "[Configurar la autenticación incorporada](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)".
+{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} Para acceder a tu instancia, las personas se autenticarán con las credenciales para la cuenta. Para obtener más información, consulta la sección "[Configurar la autenticación incorporada](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)".
 
 ### Autenticación externa
 
-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.
+Si utilizas un directorio o proveedor de identidad (IdP) externos para centralizar el acceso a varias aplicaciones web, es posible que puedas configurar la autenticación externa para {% data variables.product.product_location %}. Para obtener más información, consulta lo siguiente.
 
 - "[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)".
+Si eliges utilizar la autenticación externa, también puedes configurar la autenticación reversible para las personas que no tiene una cuenta en tu proveedor de autenticación externo. Por ejemplo, podrías querer otorgar acceso a un usuario máquina o a un contratista. 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)".
 
 {% elsif ghae %}
 
-{% data variables.product.product_name %} uses SAML SSO for authentication. Enterprise owners must configure SAML SSO with a SAML identity provider (IdP) during initialization. For more information, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)."
+{% data variables.product.product_name %} utiliza el SSO de SAML para la autenticación. Los propietarios de empresas deben configurar el SSO de SAML con un proveedor de identidad (IdP) de SAML durante la inicialización. Para obtener más información, consulta la sección "[Acerca de SAML para la IAM empresarial](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)".
 
 {% endif %}
 
@@ -134,5 +134,5 @@ If you choose to use external authentication, you can also configure fallback au
 - [Tipos de cuentas de {% data variables.product.company_short %}](/get-started/learning-about-github/types-of-github-accounts)"
 - "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)"
 {%- ifversion ghec %}
-- "[Can I create accounts for people in my organization?](/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization)"
+- "[¿Puedo crear cuentas para las personas en mi organización?](/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization)"
 {% endif %}
diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md
index 117bebab2b..6f121e93c9 100644
--- a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md
+++ b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md
@@ -32,7 +32,7 @@ Support for OIDC is in public beta and available for customers using Azure Activ
 
 Each Azure AD tenant can support only one OIDC integration with {% data variables.product.prodname_emus %}. If you want to connect Azure AD to more than one enterprise on {% data variables.product.prodname_dotcom %}, use SAML instead. For more information, see "[Configuring SAML single sign-on for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)."
 
-## Configuring OIDC for Enterprise Managed Users
+## Configurar el OIDC para los usuarios administrados empresariales
 
 1. Inicia sesión en {% data variables.product.prodname_dotcom_the_website %} como el usuario configurador para tu empresa nueva con el nombre de usuario **@<em>SHORT-CODE</em>_admin**.
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
index 4fae3b8ff6..bf573eb516 100644
--- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
+++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
@@ -10,8 +10,6 @@ topics:
   - Enterprise
 ---
 
-{% data reusables.server-statistics.release-phase %}
-
 ## About the benefits of {% data variables.product.prodname_server_statistics %}
 
 {% data variables.product.prodname_server_statistics %} 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 %}.
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 9221e339bd..bb181164ec 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
@@ -8,8 +8,6 @@ redirect_from:
   - /early-access/github/analyze-how-your-team-works-with-server-statistics/exploring-server-statistics
 ---
 
-{% 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. 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/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
index aa5aa2503d..12e72822cf 100644
--- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
+++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
@@ -8,8 +8,6 @@ redirect_from:
   - /early-access/github/analyze-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api
 ---
 
-{% data reusables.server-statistics.release-phase %}
-
 You can request up to 365 days of metrics in a single {% data variables.product.prodname_server_statistics %} REST API request. 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 %}. For a list of the metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)."
 
 Before you can use the {% data variables.product.prodname_server_statistics %} REST API, 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/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md
index d88073aa78..7b0136d77e 100644
--- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md
+++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md
@@ -1,6 +1,6 @@
 ---
-title: Exploring user activity in your enterprise
-intro: 'You can view user and system activity by leveraging dashboards, webhooks and log forwarding.'
+title: Explorar la actividad de los usuarios en tu empresa
+intro: 'Puedes ver la actividad de sistema y de usuario si aprovechas los tableros, webhooks y el reenvío de bitácoras.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -12,6 +12,6 @@ children:
   - /viewing-push-logs
   - /log-forwarding
   - /managing-global-webhooks
-shortTitle: Explore user activity
+shortTitle: Explorar la actividad de los usuarios
 ---
 
diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
index 28438c4d17..258773ead1 100644
--- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
@@ -39,9 +39,10 @@ Como propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif
 {%- ifversion enterprise-audit-log-ip-addresses %}
 - Puedes mostrar la dirección IP asociada con los eventos en la bitácora de auditoría. Para obtener más información, consulta la sección "[Mostrar las direcciones IP en la bitácora de auditoría de tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise)".
 {%- endif %}
-{%- ifversion ghec %}
+{%- ifversion audit-log-streaming %}
 - Puedes trasmitir datos de eventos de Git y de auditorías desde {% data variables.product.prodname_dotcom %} hacia un sistema externo de administración de datos. Para obtener más información, consulta la sección "[Transmitir la bitácora de auditoría de tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)".
-{%- else %}
+{%- endif %}
+{%- ifversion ghes %}
 - Puedes reenviar bitácoras de auditoría y de sistema desde tu empresa hacia un sistema de monitoreo hospedado de terceros. Para obtener más información, consulta la sección "[Reenvío de bitácoras](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)".
 {%- endif %}
 {%- ifversion ghec or ghes > 3.2 or ghae-issue-6648 %}
@@ -50,13 +51,6 @@ Como propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif
 
 Para obtener una lista completa de acciones de bitácora de auditoría que pudieran aparecer en la bitácora de auditoría de tu empresa, consulta la sección "[Acciones de la bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)".
 
-{% ifversion ghec %}
-## Eventos de git
-
-Los datos de eventos de Git que se registran son los de clonar, recuperar y subir. Para obtener más información, consulta la sección "[Transmitir la bitácora de auditoría de tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)".
-
-{% endif %}
-
 ## Leer más
 - "[Revisar el registro 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)"
 {%- ifversion ghes %}
diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
index be40fce103..de74e278e7 100644
--- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
@@ -23,12 +23,12 @@ topics:
 ---
 
 {% ifversion ghec%}
-## About audit log events for your enterprise
+## Acerca de los eventos de bitácora de auditoría para tu empresa
 
-The scope of the events that appear in your enterprise's audit log depend on whether your enterprise uses {% data variables.product.prodname_emus %}. Para obtener más información sobre las {% data variables.product.prodname_emus %}, consulta la sección "[Acerca de las {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)".
+El alcance de los eventos que se muestran en la bitácora de auditoría de tu empresa dependen de si esta utiliza {% data variables.product.prodname_emus %}. Para obtener más información sobre las {% data variables.product.prodname_emus %}, consulta la sección "[Acerca de las {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)".
 
-- If your enterprise does not use {% data variables.product.prodname_emus %}, the audit log only includes events related to the enterprise account and the organizations within the enterprise account, which are listed in this article.
-- If your enterprise uses {% data variables.product.prodname_emus %}, the audit log also includes user events for {% data variables.product.prodname_managed_users %}, such as each time the user logs in to {% data variables.product.product_name %}. For a list of these events, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)."
+- Si tu empresa no utiliza {% data variables.product.prodname_emus %}, la bitácora de auditoría solo incluirá eventos relacionados con la cuenta empresarial y con las organizaciones dentro de esta, lo cuál se lista en este artículo.
+- Si tu empresa utiliza {% data variables.product.prodname_emus %}, la bitácora de auditoría también incluirá eventos de usuario para {% data variables.product.prodname_managed_users %}, tal como cada vez que el usuario inicia sesión en {% data variables.product.product_name %}. Para encontrar una lista de estos eventos, consulta la sección "[Revisar tu bitácora de auditoría](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)".
 {% endif %}
 
 {%- ifversion fpt or ghec %}
@@ -59,7 +59,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 | ------------------ | ------------------------------------------------------------------- |
 | `artifact.destroy` | Un artefacto de ejecución de flujo de trabajo se borró manualmente. |
 
-{%- ifversion ghec %}
+{%- ifversion audit-log-streaming %}
 ## Acciones de la categoría `audit_log_streaming`
 
 | Acción                        | Descripción                                                                                                                                 |
@@ -73,34 +73,34 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 {%- ifversion fpt or ghec %}
 ## acciones de la categoría `billing`
 
-| Acción                        | Descripción                                                                                                                                                                                                                                             |
-| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `billing.change_billing_type` | An organization changed how it paid for {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Agregar o editar un método de pago](/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method)". |
-| `billing.change_email`        | An organization's billing email address changed. Para obtener más información, consulta "[Establecer tu correo electrónico de facturación](/billing/managing-your-github-billing-settings/setting-your-billing-email)".                                 |
+| Acción                        | Descripción                                                                                                                                                                                                                                                          |
+| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `billing.change_billing_type` | Una organización cambió la forma en la cual paga por {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Agregar o editar un método de pago](/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method)". |
+| `billing.change_email`        | Cambió la dirección de correo electrónico para facturación de una organización. Para obtener más información, consulta "[Establecer tu correo electrónico de facturación](/billing/managing-your-github-billing-settings/setting-your-billing-email)".               |
 {%- endif %}
 
 ## Acciones de la categoría `business`
 
-| Acción               | Descripción                                                                                          |
-| -------------------- | ---------------------------------------------------------------------------------------------------- |
-| `business.add_admin` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} was added to an enterprise. |
+| Acción               | Descripción                                                                                                |
+| -------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `business.add_admin` | Un propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif %} se agregó a una empresa. |
 {%- ifversion ghec %}
-| `business.add_billing_manager` | A billing manager was added to an enterprise.
+| `business.add_billing_manager` | Se agregó un gerente de facturación a una empresa.
 {%- endif %}
-| `business.add_organization` | An organization was added to an enterprise.
+| `business.add_organization` | Se agregó una organización a una empresa.
 {%- ifversion ghec %}
-| `business.add_support_entitlee` | A support entitlement was added to a member of an enterprise. Para obtener más información, consulta la sección "[Administrar la titularidad de soporte para tu empresa](/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)".
+| `business.add_support_entitlee` | Se agregó un derecho de soporte a un miembro de una empresa. Para obtener más información, consulta la sección "[Administrar la titularidad de soporte para tu empresa](/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)".
 {%- endif %}
 {%- ifversion ghes or ghae %}
-| `business.advanced_security_policy_update` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} created, updated, or removed a policy for {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)".
+| `business.advanced_security_policy_update` | Un propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif %} creó, actualizó o eliminó una política para la {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)".
 {%- endif %}
 {%- ifversion ghec %}
-| `business.cancel_admin_invitation` | An invitation for someone to be an owner{% ifversion ghes %} or site administrator{% endif %} of an enterprise was canceled. | `business.cancel_billing_manager_invitation` | An invitation for someone to be an billing manager of an enterprise was canceled.
+| `business.cancel_admin_invitation` | Se canceló una invitación para que alguien se convirtiera en propietario{% ifversion ghes %} o administrador de sitio{% endif %} de una empresa. | `business.cancel_billing_manager_invitation` | Se canceló una invitación para que alguien se convirtiera en gerente de facturación de una empresa.
 {%- endif %}
 {%- ifversion ghes %}
-| `business.clear_actions_settings` | An enterprise owner or site administrator cleared {% data variables.product.prodname_actions %} policy settings for an enterprise. Para obtener más información, consulta la sección "[Requerir políticas para las GitHub Actions en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)".
+| `business.clear_actions_settings` | Un propietario de empresa o administrador de sitio quitó los ajustes de política de {% data variables.product.prodname_actions %} para una empresa. Para obtener más información, consulta la sección "[Requerir políticas para las GitHub Actions en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)".
 {%- endif %}
-| `business.clear_default_repository_permission` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the base repository permission policy setting for an enterprise. Para obtener más información, consulta la sección "[Requerir una política para los permisos de los repositorios base](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-base-repository-permissions)". | `business.clear_members_can_create_repos`      | Un propietario de empresa{% ifversion ghes %} o adminsitrador de sitio{% endif %} quitó una restricción sobre la creación de repositorios en las organizaciones de la empresa. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)". | `business.create`                              | Se creó una empresa.
+| `business.clear_default_repository_permission` | Un propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif %} quitó el ajuste de política de permiso del repositorio base para una empresa. Para obtener más información, consulta la sección "[Requerir una política para los permisos de los repositorios base](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-base-repository-permissions)". | `business.clear_members_can_create_repos`      | Un propietario de empresa{% ifversion ghes %} o adminsitrador de sitio{% endif %} quitó una restricción sobre la creación de repositorios en las organizaciones de la empresa. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)". | `business.create`                              | Se creó una empresa.
 {%- ifversion ghec %}
 | `business.disable_saml` | El inicio de sesión único de SAML se inhabilito para una empresa.
 {%- endif %}
@@ -174,12 +174,12 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 | `codespaces.attempted_to_create_from_prebuild` | Se realizó un intento de crear un codespace desde una precompilación.                                                                                                                                                                                |
 | `codespaces.create_an_org_secret`              | Un usuario canceló un [secreto para {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel organizacional    |
 | `codespaces.update_an_org_secret`              | Un usuario actualizó un [secreto para {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel organizacional. |
-| `codespaces.remove_an_org_secret`              | A user removed an organization-level [secret for {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces).             |
-| `codespaces.manage_access_and_security`        | A user updated [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                                                                   |
+| `codespaces.remove_an_org_secret`              | Un usuario eliminó un [secreto para {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel organizacional.   |
+| `codespaces.manage_access_and_security`        | Un usuario actualizó [los repositorios a los cuales puede acceder un codespace](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                                              |
 {%- endif %}
 
 {%- ifversion fpt or ghec %}
-## `commit_comment` category actions
+## Acciones de la categoría `commit_comment`
 
 | Acción                   | Descripción                   |
 | ------------------------ | ----------------------------- |
@@ -408,28 +408,28 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 | `integration.transfer`             | Se transfirió la propiedad de una integración a otro usuario u organización.            |
 | `integration.remove_client_secret` | A client secret for an integration was removed.                                         |
 | `integration.revoke_all_tokens`    | All user tokens for an integration were requested to be revoked.                        |
-| `integration.revoke_tokens`        | Token(s) for an integration were revoked.                                               |
+| `integration.revoke_tokens`        | Se revocaron los tokens para una integración.                                           |
 
-## `integration_installation`category actions
+## Acciones de la categoría `integration_installation`
 
-| Acción                                           | Descripción                                     |
-| ------------------------------------------------ | ----------------------------------------------- |
-| `integration_installation.contact_email_changed` | A contact email for an integration was changed. |
-| `integration_installation.create`                | An integration was installed.                   |
-| `integration_installation.destroy`               | An integration was uninstalled.                 |
-| `integration_installation.repositories_added`    | Repositories were added to an integration.      |
-| `integration_installation.repositories_removed`  | Repositories were removed from an integration.  |
+| Acción                                           | Descripción                                                       |
+| ------------------------------------------------ | ----------------------------------------------------------------- |
+| `integration_installation.contact_email_changed` | Se cambió un correo electrónico de contacto para una integración. |
+| `integration_installation.create`                | Se instaló una integración.                                       |
+| `integration_installation.destroy`               | Se desinstaló una integración.                                    |
+| `integration_installation.repositories_added`    | Se agregaron repositorios a una integración.                      |
+| `integration_installation.repositories_removed`  | Se eliminaron repositorios de una integración.                    |
 {%- ifversion fpt or ghec %}
-| `integration_installation.suspend` | An integration was suspended. | `integration_installation.unsuspend` | An integration was unsuspended.
+| `integration_installation.suspend` | Se suspendió una integración. | `integration_installation.unsuspend` | Se dejó de suspender una integración.
 {%- endif %}
-| `integration_installation.version_updated` | Permissions for an integration were updated.
+| `integration_installation.version_updated` | Se actualizaron los permisos para una integración.
 
 ## Acciones de la categoría`integration_installation_request`
 
-| Acción                                    | Descripción                                                                                                                                                               |
-| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `integration_installation_request.create` | An member requested that an owner install an integration for use in an enterprise or organization.                                                                        |
-| `integration_installation_request.close`  | A request to install an integration for use in an enterprise or organization was either approved or denied by an owner, or canceled by the member who opened the request. |
+| Acción                                    | Descripción                                                                                                                                                                        |
+| ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `integration_installation_request.create` | Un miembro solicitó que un propietario instalara una integración para utilizar en una empresa u organización.                                                                      |
+| `integration_installation_request.close`  | Un propietario aprobó o rechazó una solicitud para instalar una integración para utilizarla en una empresa u organización o el miembro que había abierto la solicitud, la canceló. |
 
 {%- ifversion ghec or ghae %}
 ## `ip_allow_list` category actions
@@ -455,75 +455,75 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 | Acción           | Descripción                                                                                                                                                                                                                 |
 | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `issue.destroy`  | Se eliminó un problema del repositorio. Para obtener más información, consulta la sección "[Borrar una propuesta](/issues/tracking-your-work-with-issues/deleting-an-issue)".                                               |
-| `issue.pinned`   | An issue was pinned to a repository. Para obtener más información, consulta "[Anclar una propuesta a tu repositorio](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)".                          |
-| `issue.transfer` | An issue was transferred to another repository. Para obtener más información, consulta "[Transferir una propuesta a otro repositorio](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." |
-| `issue.unpinned` | An issue was unpinned from a repository. Para obtener más información, consulta "[Anclar una propuesta a tu repositorio](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)".                      |
+| `issue.pinned`   | Se fijó una propuesta a un repositorio. Para obtener más información, consulta "[Anclar una propuesta a tu repositorio](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)".                       |
+| `issue.transfer` | Se transfirió una propuesta a otro repositorio. Para obtener más información, consulta "[Transferir una propuesta a otro repositorio](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." |
+| `issue.unpinned` | Se dejó de fijar una propuesta a un repositorio. Para obtener más información, consulta "[Anclar una propuesta a tu repositorio](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)".              |
 
-## `issue_comment` category actions
+## Acciones de la categoría `issue_comment`
 
-| Acción                   | Descripción                                                    |
-| ------------------------ | -------------------------------------------------------------- |
-| `issue_comment.destroy`  | A comment on an issue was deleted from the repository.         |
-| `issue_comment.pinned`   | A comment on an issue was pinned to a repository.              |
-| `issue_comment.unpinned` | A comment on an issue was unpinned from a repository.          |
-| `issue_comment.update`   | Cambió un comentario sobre un problema (diferente al inicial). |
+| Acción                   | Descripción                                                        |
+| ------------------------ | ------------------------------------------------------------------ |
+| `issue_comment.destroy`  | Se borró un comentario de una propuesta en el repositorio.         |
+| `issue_comment.pinned`   | Se fijó un comentario de una propuesta en el repositorio.          |
+| `issue_comment.unpinned` | Se dejó de fijar un comentario de una propuesta en el repositorio. |
+| `issue_comment.update`   | Cambió un comentario sobre un problema (diferente al inicial).     |
 
-## `issues` category actions
+## Acciones de la categoría `issues`
 
-| Acción                          | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `issues.deletes_disabled`       | The ability for enterprise members to delete issues was disabled. Members cannot delete issues in any organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para borrar las propuestas](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)".                       |
-| `issues.deletes_enabled`        | The ability for enterprise members to delete issues was enabled. Members can delete issues in any organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para borrar las propuestas](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)".                           |
-| `issues.deletes_policy_cleared` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for allowing members to delete issues in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para borrar las propuestas](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)". |
+| Acción                          | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `issues.deletes_disabled`       | Se inhabilitó la capacidad para que los miembros de la empresa borren propuestas. Los miembros no pueden borrar propuestas en ninguna organización de una empresa. Para obtener más información, consulta la sección "[Requerir una política para borrar las propuestas](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)".             |
+| `issues.deletes_enabled`        | Se habilitó la capacidad para que los miembros de una empresa borren propuestas. Los miembros pueden borrar propuestas en cualquier organización de una empresa. Para obtener más información, consulta la sección "[Requerir una política para borrar las propuestas](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)".               |
+| `issues.deletes_policy_cleared` | Un propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif %} quitó el ajuste de política para permitir que los miembros borren propuestas en una empresa. Para obtener más información, consulta la sección "[Requerir una política para borrar las propuestas](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)". |
 
 {%- ifversion fpt or ghec %}
 ## acciones de la categoría `marketplace_agreement_signature`
 
-| Acción                                   | Descripción                                                                                                           |
-| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
-| `marketplace_agreement_signature.create` | A user signed the {% data variables.product.prodname_marketplace %} Developer Agreement on behalf of an organization. |
+| Acción                                   | Descripción                                                                                                                      |
+| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `marketplace_agreement_signature.create` | Un usuario firmó el Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %} en nombre de una organización. |
 
 ## acciones de la categoría `marketplace_listing`
 
-| Acción                                | Descripción                                                                                           |
-| ------------------------------------- | ----------------------------------------------------------------------------------------------------- |
-| `marketplace_listing.approve`         | A listing was approved for inclusion in {% data variables.product.prodname_marketplace %}.            |
-| `marketplace_listing.change_category` | A category for a listing for an app in {% data variables.product.prodname_marketplace %} was changed. |
-| `marketplace_listing.create`          | A listing for an app in {% data variables.product.prodname_marketplace %} was created.                |
-| `marketplace_listing.delist`          | A listing was removed from {% data variables.product.prodname_marketplace %}.                         |
-| `marketplace_listing.redraft`         | A listing was sent back to draft state.                                                               |
-| `marketplace_listing.reject`          | A listing was not accepted for inclusion in {% data variables.product.prodname_marketplace %}.        |
+| Acción                                | Descripción                                                                                              |
+| ------------------------------------- | -------------------------------------------------------------------------------------------------------- |
+| `marketplace_listing.approve`         | Se aprobó una lista para inclusión en {% data variables.product.prodname_marketplace %}.                 |
+| `marketplace_listing.change_category` | Se cambió una categoría de un listado para una app en {% data variables.product.prodname_marketplace %}. |
+| `marketplace_listing.create`          | Se creó un listado para una app en {% data variables.product.prodname_marketplace %}.                    |
+| `marketplace_listing.delist`          | Se eliminó un listado de {% data variables.product.prodname_marketplace %}.                              |
+| `marketplace_listing.redraft`         | Se regresó un listado a su estado de borrador.                                                           |
+| `marketplace_listing.reject`          | No se aceptó un listado para su inclusión en {% data variables.product.prodname_marketplace %}.          |
 {%- endif %}
 
 ## Acciones de la categoría `members_can_create_pages`
 
-| Acción                             | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `members_can_create_pages.disable` | The ability for members to publish {% data variables.product.prodname_pages %} was disabled. Members cannot publish {% data variables.product.prodname_pages %} in an organization. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". |
-| `members_can_create_pages.enable`  | The ability for members to publish {% data variables.product.prodname_pages %} was enabled. Members can publish {% data variables.product.prodname_pages %} in an organization. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)".     |
+| Acción                             | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `members_can_create_pages.disable` | Se inhabilitó la capacidad para que los miembros publiquen {% data variables.product.prodname_pages %}. Los miembros no pueden publicar {% data variables.product.prodname_pages %} en una organización. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". |
+| `members_can_create_pages.enable`  | Se habilitó la capacidad para que los miembros publiquen {% data variables.product.prodname_pages %}. Los miembros pueden publicar {% data variables.product.prodname_pages %} en una organización. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)".      |
 
-## `members_can_create_private_pages` category actions
+## Acciones de la categoría `members_can_create_private_pages`
 
-| Acción                                     | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `members_can_create_private_pages.disable` | The ability for members to publish private {% data variables.product.prodname_pages %} was disabled. Members cannot publish private {% data variables.product.prodname_pages %} in an organization. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". |
-| `members_can_create_private_pages.enable`  | The ability for members to publish private {% data variables.product.prodname_pages %} was enabled. Members can publish private {% data variables.product.prodname_pages %} in an organization. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)".     |
+| Acción                                     | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `members_can_create_private_pages.disable` | Se inhabilitó la capacidad para que los miembros publiquen {% data variables.product.prodname_pages %} privadas. Los miembros no pueden publicar {% data variables.product.prodname_pages %} privadas en una organización. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". |
+| `members_can_create_private_pages.enable`  | Se habilitó la capacidad para que los miembros publiquen {% data variables.product.prodname_pages %} privadas. Los miembros pueden publicar {% data variables.product.prodname_pages %} privadas en una organización. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)".      |
 
-## `members_can_create_public_pages` category actions
+## Acciones de la categoría `members_can_create_public_pages`
 
-| Acción                                    | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `members_can_create_public_pages.disable` | The ability for members to publish public {% data variables.product.prodname_pages %} was disabled. Members cannot publish public {% data variables.product.prodname_pages %} in an organization. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". |
-| `members_can_create_public_pages.enable`  | The ability for members to publish public {% data variables.product.prodname_pages %} was enabled. Members can publish public {% data variables.product.prodname_pages %} in an organization. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)".     |
+| Acción                                    | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `members_can_create_public_pages.disable` | Se inhabilitó la capacidad para que los miembros publiquen {% data variables.product.prodname_pages %} públicas. Los miembros no pueden publicar {% data variables.product.prodname_pages %} públicas en una organización. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". |
+| `members_can_create_public_pages.enable`  | Se habilitó la capacidad para que los miembros publiquen {% data variables.product.prodname_pages %} públicas. Los miembros pueden publicar {% data variables.product.prodname_pages %} públicas en una organización. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)".      |
 
 {%- ifversion ghec or ghes or ghae %}
-## `members_can_delete_repos` category actions
+## Acciones de la categoría `members_can_delete_repos`
 
-| Acción                             | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `members_can_delete_repos.clear`   | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for deleting or transfering repositories in any organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para el borrado y transferencia de repositorios](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)".   |
-| `members_can_delete_repos.disable` | Se inhabilitó la capacidad para que los miembros de una empresa borren repositorios. Los miembros no pueden borrar ni transferir repositorios en ninguna organización de una empresa. Para obtener más información, consulta la sección "[Requerir una política para el borrado y transferencia de repositorios](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)". |
-| `members_can_delete_repos.enable`  | Se habilitó la capacidad para que los miembros de un empresa borren repositorios. Los miembros pueden borrar o transferir repositorios en cualquier organización de una empresa. Para obtener más información, consulta la sección "[Requerir una política para el borrado y transferencia de repositorios](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)".      |
+| Acción                             | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `members_can_delete_repos.clear`   | Un propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif %} quitó el ajuste de política para borrar o transferir los repositorios en cualquier organización de una empresa. Para obtener más información, consulta la sección "[Requerir una política para el borrado y transferencia de repositorios](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)". |
+| `members_can_delete_repos.disable` | Se inhabilitó la capacidad para que los miembros de una empresa borren repositorios. Los miembros no pueden borrar ni transferir repositorios en ninguna organización de una empresa. Para obtener más información, consulta la sección "[Requerir una política para el borrado y transferencia de repositorios](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)".             |
+| `members_can_delete_repos.enable`  | Se habilitó la capacidad para que los miembros de un empresa borren repositorios. Los miembros pueden borrar o transferir repositorios en cualquier organización de una empresa. Para obtener más información, consulta la sección "[Requerir una política para el borrado y transferencia de repositorios](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)".                  |
 
 ## Acciones de la categoría `members_can_view_dependency_insights`
 
@@ -599,7 +599,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 {%- ifversion ghec %}
 | `org.audit_log_export` | Un propietario de organización creó una exportación de la bitácora de auditoría de la organización. 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. Para obtener más información, consulta la sección "[Exportar la actividad de las bitácoras de auditoría de tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)".
 {%- endif %}
-| `org.block_user` | Un propietario de organización bloqueó a un usuario para que no accediera a los repositorios de la organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Bloquear a un usuario de tu organización](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."{% endif %}| | `org.cancel_business_invitation` | Se revocó una invitación para que una organización se uniera a una empresa. |{% ifversion ghec %}Para obtener más información, consulta la sección "[Invitar a una organización para que se una a tu cuenta empresarial](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.cancel_invitation` | Se revocó una invitación que se envió a un usuario para que se una a una organización. | `org.clear_actions_settings` |  Un propietario de organización quitó los ajustes de política de {% data variables.product.prodname_actions %} para una organización. For more information, see "[Managing GitHub Actions permissions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)." | `org.clear_default_repository_permission` | An organization owner cleared the base repository permission policy setting for an organization. For more information, see "[Setting base permissions](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)." | `org.clear_member_team_creation_permission` | An organization owner cleared the new teams creation setting for an organization. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)." | `org.clear_reader_discussion_creation_permission` | An organization owner cleared the new discussion creation setting for an organization. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Permitir o dejar de permitir que los usuarios con acceso de lectura creen debates](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %}| | `org.clear_members_can_create_repos`                 | Un propietario de organización libró una restricción de creación de repositorios en una organización. Para obtener más información, consulta "[Restringir la creación de repositorios en tu organización](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization)". | `org.clear_members_can_invite_outside_collaborators` | An organization owner cleared the outside collaborators invitation policy for an organization. Para obtener más información, consulta la sección "[Establecer permisos para agregar colaboradores externos](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)". | `org.clear_new_repository_default_branch_setting`    | An organization owner cleared the default branch name for new repositories setting for an organization. For more information, see "[Setting the default branch name](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization#setting-the-default-branch-name)."
+| `org.block_user` | Un propietario de organización bloqueó a un usuario para que no accediera a los repositorios de la organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Bloquear a un usuario de tu organización](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."{% endif %}| | `org.cancel_business_invitation` | Se revocó una invitación para que una organización se uniera a una empresa. |{% ifversion ghec %}Para obtener más información, consulta la sección "[Invitar a una organización para que se una a tu cuenta empresarial](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.cancel_invitation` | Se revocó una invitación que se envió a un usuario para que se una a una organización. | `org.clear_actions_settings` |  Un propietario de organización quitó los ajustes de política de {% data variables.product.prodname_actions %} para una organización. Para obtener más información, consulta la sección "[Administrar los permisos de GitHub Actions para tu organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)". | `org.clear_default_repository_permission` | Un propietario de una organización quitó el ajuste de política de permiso de un repositorio base para una organización. Para obtener más información, consulta la sección "[Configurar los permisos base](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)". | `org.clear_member_team_creation_permission` | Un propietario de una organización quitó el ajuste de creación de equipos nuevos en una organización. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)." | `org.clear_reader_discussion_creation_permission` | Un propietario de una organización quitó el ajuste de creación de debates nuevos en una organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Permitir o dejar de permitir que los usuarios con acceso de lectura creen debates](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %}| | `org.clear_members_can_create_repos`                 | Un propietario de organización libró una restricción de creación de repositorios en una organización. Para obtener más información, consulta "[Restringir la creación de repositorios en tu organización](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization)". | `org.clear_members_can_invite_outside_collaborators` | Un propietario de una organización quitó la política de invitación de colaboradores externos en una organización. Para obtener más información, consulta la sección "[Establecer permisos para agregar colaboradores externos](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)". | `org.clear_new_repository_default_branch_setting`    | Un propietario de una organización quitó el ajuste de nombre de rama predeterminado para repositorios nuevos en una organización. For more information, see "[Setting the default branch name](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization#setting-the-default-branch-name)."
 {%- ifversion fpt or ghec %}
 | `org.codespaces_trusted_repo_access_granted`         | {% data variables.product.prodname_github_codespaces %} was granted trusted repository access to all other repositories in an organization. Para obtener más información, consulta la sección "[Administrar el acceso de un repositorio a los codespces de tu organización](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)". | `org.codespaces_trusted_repo_access_revoked`         | {% data variables.product.prodname_github_codespaces %} trusted repository access to all other repositories in an organization was revoked. Para obtener más información, consulta la sección "[Administrar el acceso de un repositorio a los codespces de tu organización](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)".
 {%- endif %}
@@ -631,7 +631,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 {%- ifversion fpt or ghec %}
 | `org.oauth_app_access_approved` | An owner [granted organization access to an {% data variables.product.prodname_oauth_app %}](/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization). | `org.oauth_app_access_denied` | An owner [disabled a previously approved {% data variables.product.prodname_oauth_app %}'s access](/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to an organization. | `org.oauth_app_access_requested` | An organization member requested that an owner grant an {% data variables.product.prodname_oauth_app %} access to an organization.
 {%- endif %}
-| `org.recreate` | An organization was restored. | `org.register_self_hosted_runner` | A new self-hosted runner was registered. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | `org.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was removed. | `org.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was removed from an organization. | `org.remove_billing_manager` | An owner removed a billing manager from an organization. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Eliminar a un gerente de factguración de tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} o cuando se requiera [la autenticación bifactorial en una organización](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) y un gerente de facturación no haya usado la 2FA o la haya inhabilitado.{% endif %}| | `org.remove_member` | Un [propietario eliminó a un miembro de una organización](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} o cuando [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) un miembro de la organización no utiliza 2FA o la inhabilita{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. | `org.remove_outside_collaborator` | Un propietario eliminó a un colaborador externo de una organización{% ifversion not ghae %} o cuando [se requirió la autenticación bifactorial en una organización](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) y un colaborador externo no la utilizó o la inhabilitó{% endif %}. | `org.remove_self_hosted_runner` | A self-hosted runner was removed. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de una organización](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)". | `org.rename` | An organization was renamed. | `org.restore_member` | An organization member was restored. Para obtener más información, consulta la sección "[Reinstaurar a un miembro anterior de tu organización](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization)".
+| `org.recreate` | An organization was restored. | `org.register_self_hosted_runner` | Se registró un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | `org.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was removed. | `org.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was removed from an organization. | `org.remove_billing_manager` | An owner removed a billing manager from an organization. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Eliminar a un gerente de factguración de tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} o cuando se requiera [la autenticación bifactorial en una organización](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) y un gerente de facturación no haya usado la 2FA o la haya inhabilitado.{% endif %}| | `org.remove_member` | Un [propietario eliminó a un miembro de una organización](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} o cuando [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) un miembro de la organización no utiliza 2FA o la inhabilita{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. | `org.remove_outside_collaborator` | Un propietario eliminó a un colaborador externo de una organización{% ifversion not ghae %} o cuando [se requirió la autenticación bifactorial en una organización](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) y un colaborador externo no la utilizó o la inhabilitó{% endif %}. | `org.remove_self_hosted_runner` | A self-hosted runner was removed. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de una organización](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)". | `org.rename` | An organization was renamed. | `org.restore_member` | An organization member was restored. Para obtener más información, consulta la sección "[Reinstaurar a un miembro anterior de tu organización](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization)".
 {%- ifversion ghec %}
 | `org.revoke_external_identity` | Un propietario de organización revocó la identidad vinculada de un miembro. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". | `org.revoke_sso_session` | Un propietario de organización revocó la sesión de SAML de un miembro. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)".
 {%- endif %}
@@ -707,91 +707,91 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 
 | Acción                        | Descripción                                                                                                                                                                                                                                                                                           |
 | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `organization_domain.approve` | An enterprise domain was approved for an organization. For more information, see "[Approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#approving-a-domain-for-your-organization)."                          |
-| `organization_domain.create`  | An enterprise domain was added to an organization. Para obtener más información, consulta la sección "[Verificar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)".     |
-| `organization_domain.destroy` | An enterprise domain was removed from an organization. For more information, see "[Removing an approved or verified domain](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#removing-an-approved-or-verified-domain)."                            |
-| `organization_domain.verify`  | An enterprise domain was verified for an organization. Para obtener más información, consulta la sección "[Verificar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)". |
+| `organization_domain.approve` | An enterprise domain was approved for an organization. Para obtener más información, consulta la sección "[Aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#approving-a-domain-for-your-organization)".   |
+| `organization_domain.create`  | Se agregó un dominio de empresa a una organización. Para obtener más información, consulta la sección "[Verificar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)".    |
+| `organization_domain.destroy` | Se eliminó un dominio de empresa de una organización. Para obtener más información, consulta la sección "[Eliminar un dominio verificado o aprobado](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#removing-an-approved-or-verified-domain)".   |
+| `organization_domain.verify`  | Se verificó un dominio de empresa en una organización. Para obtener más información, consulta la sección "[Verificar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)". |
 
-## `organization_projects_change` category actions
+## Acciones de la categoría `organization_projects_change`
 
-| Acción                                 | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `organization_projects_change.clear`   | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for organization-wide project boards in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para los tableros de proyecto en toda la organización](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)". |
-| `organization_projects_change.disable` | Organization projects were disabled for all organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para los tableros de proyecto en toda la organización](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)".                                                                                |
-| `organization_projects_change.enable`  | Organization projects were enabled for all organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para los tableros de proyecto en toda la organización](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)".                                                                                 |
+| Acción                                 | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `organization_projects_change.clear`   | Un propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif %} quitó el ajuste de política para los tableros de proyecto de toda la organización en una empresa. Para obtener más información, consulta la sección "[Requerir una política para los tableros de proyecto en toda la organización](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)". |
+| `organization_projects_change.disable` | Se inhabilitaron los proyectos de organización para todas las organizaciones en una empresa. Para obtener más información, consulta la sección "[Requerir una política para los tableros de proyecto en toda la organización](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)".                                                                                        |
+| `organization_projects_change.enable`  | Se habilitaron los proyectos de organización para todas las organizaciones en una empresa. Para obtener más información, consulta la sección "[Requerir una política para los tableros de proyecto en toda la organización](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)".                                                                                          |
 {%- endif %}
 
 ## Acciones de la categoría `packages`
 
 | Acción                               | Descripción                                                                                                                                                                                                                                           |
 | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `packages.insecure_hash`             | Maven published an insecure hash for a specific package version.                                                                                                                                                                                      |
-| `packages.package_deleted`           | A package was deleted from an organization.{% ifversion fpt or ghec or ghes %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
-| `packages.package_published`         | A package was published or republished to an organization.                                                                                                                                                                                            |
-| `packages.package_restored`          | An entire package was restored.{% ifversion fpt or ghec or ghes %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `packages.insecure_hash`             | Maven publicó un hash inseguro para una versión de paquete específica.                                                                                                                                                                                |
+| `packages.package_deleted`           | Se borró un paquete de una organización.{% ifversion fpt or ghec or ghes %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %}
+| `packages.package_published`         | Se publicó o se volvió a publicar un paquete en una organización.                                                                                                                                                                                     |
+| `packages.package_restored`          | Se restableció un paquete completo.{% ifversion fpt or ghec or ghes %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %}
 | `packages.package_version_deleted`   | Se borró una versión específica de un paquete.{% ifversion fpt or ghec or ghes %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %}
-| `packages.package_version_published` | A specific package version was published or republished to a package.                                                                                                                                                                                 |
+| `packages.package_version_published` | Se publicó o se volvió a publicar una versión de paquete específica para un paquete.                                                                                                                                                                  |
 | `packages.package_version_restored`  | Se borró una versión específica de un paquete.{% ifversion fpt or ghec or ghes %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %}
-| `packages.part_upload`               | A specific package version was partially uploaded to an organization.                                                                                                                                                                                 |
-| `packages.upstream_package_fetched`  | A specific package version was fetched from the npm upstream proxy.                                                                                                                                                                                   |
-| `packages.version_download`          | A specific package version was downloaded.                                                                                                                                                                                                            |
-| `packages.version_upload`            | A specific package version was uploaded.                                                                                                                                                                                                              |
+| `packages.part_upload`               | Se cargó parcialmente una versión de paquete específica en una organización.                                                                                                                                                                          |
+| `packages.upstream_package_fetched`  | Se recuperó una versión de paquete específica desde el proxy ascendente de npm.                                                                                                                                                                       |
+| `packages.version_download`          | Se descargó una versión de paquete específica.                                                                                                                                                                                                        |
+| `packages.version_upload`            | Se cargó una versión de paquete específica.                                                                                                                                                                                                           |
 
 {%- ifversion fpt or ghec %}
-## `pages_protected_domain` category actions
+## Acciones de la categoría `pages_protected_domain`
 
 | Acción                          | Descripción                                                                                                                                                                                                                                                                                                                                                           |
 | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `pages_protected_domain.create` | A {% data variables.product.prodname_pages %} verified domain was created for an organization or enterprise. Para obtener más información, consulta la sección "[Verificar tu dominio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)".  |
-| `pages_protected_domain.delete` | A {% data variables.product.prodname_pages %} verified domain was deleted from an organization or enterprise. Para obtener más información, consulta la sección "[Verificar tu dominio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)". |
-| `pages_protected_domain.verify` | A {% data variables.product.prodname_pages %} domain was verified for an organization or enterprise. Para obtener más información, consulta la sección "[Verificar tu dominio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)".          |
+| `pages_protected_domain.create` | Se creó un dominio verificado de {% data variables.product.prodname_pages %} para una organización o empresa. Para obtener más información, consulta la sección "[Verificar tu dominio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)". |
+| `pages_protected_domain.delete` | Se borró un dominio verificado de {% data variables.product.prodname_pages %} de una organización o empresa. Para obtener más información, consulta la sección "[Verificar tu dominio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)".  |
+| `pages_protected_domain.verify` | Se verificó un dominio de {% data variables.product.prodname_pages %} para una organización o empresa. Para obtener más información, consulta la sección "[Verificar tu dominio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)".        |
 
 ## acciones de la categoría `payment_method`
 
-| Acción                  | Descripción                                                                  |
-| ----------------------- | ---------------------------------------------------------------------------- |
-| `payment_method.create` | A new payment method was added, such as a new credit card or PayPal account. |
-| `payment_method.remove` | A payment method was removed.                                                |
-| `payment_method.update` | An existing payment method was updated.                                      |
+| Acción                  | Descripción                                                                                   |
+| ----------------------- | --------------------------------------------------------------------------------------------- |
+| `payment_method.create` | Se agregó un método de pago nuevo, tal como una tarjeta de crédito o cuenta de PayPal nuevas. |
+| `payment_method.remove` | Se eliminó un método de pago.                                                                 |
+| `payment_method.update` | Se actualizó un método de pago existente.                                                     |
 
-## `prebuild_configuration` category actions
+## Acciones de la categoría ` prebuild_configuration`
 
-| Acción                                 | Descripción                                                                                                                                                                                                                                                                                                                                                |
-| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `prebuild_configuration.create`        | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was created. Para obtener más información, consulta la sección "[Acerca de las precompilaciones de {% data variables.product.prodname_github_codespaces %}](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)".                      |
-| `prebuild_configuration.destroy`       | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was deleted. Para obtener más información, consulta la sección "[Acerca de las precompilaciones de {% data variables.product.prodname_github_codespaces %}](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)".                      |
-| `prebuild_configuration.run_triggered` | A user initiated a run of a {% data variables.product.prodname_codespaces %} prebuild configuration for a repository branch. Para obtener más información, consulta la sección "[Acerca de las precompilaciones de {% data variables.product.prodname_github_codespaces %}](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)". |
-| `prebuild_configuration.update`        | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was edited. Para obtener más información, consulta la sección "[Acerca de las precompilaciones de {% data variables.product.prodname_github_codespaces %}](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)".                       |
+| Acción                                 | Descripción                                                                                                                                                                                                                                                                                                                                                                            |
+| -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `prebuild_configuration.create`        | Se creó una configuración de precompilación de {% data variables.product.prodname_codespaces %} para un repositorio. Para obtener más información, consulta la sección "[Acerca de las precompilaciones de {% data variables.product.prodname_github_codespaces %}](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)".                                     |
+| `prebuild_configuration.destroy`       | Se borró una configuración de precompilación de {% data variables.product.prodname_codespaces %} para un repositorio. Para obtener más información, consulta la sección "[Acerca de las precompilaciones de {% data variables.product.prodname_github_codespaces %}](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)".                                    |
+| `prebuild_configuration.run_triggered` | Un usuario inició una ejecución de una configuración de precompilación de {% data variables.product.prodname_codespaces %} para una rama de repositorio. Para obtener más información, consulta la sección "[Acerca de las precompilaciones de {% data variables.product.prodname_github_codespaces %}](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)". |
+| `prebuild_configuration.update`        | Se editó una configuración de precompilación de {% data variables.product.prodname_codespaces %} para un repositorio. Para obtener más información, consulta la sección "[Acerca de las precompilaciones de {% data variables.product.prodname_github_codespaces %}](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)".                                    |
 {%- endif %}
 
 {%- ifversion ghes %}
-## `pre_receive_environment` category actions
+## Acciones de la categoría `pre_receive_environment`
 
-| Acción                             | Descripción                                                                                                                                                                                                                                         |
-| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `pre_receive_environment.create`   | A pre-receive hook environment was created. Para obtener más información, consulta la sección "[Crear un ambiente de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)".    |
-| `pre_receive_environment.destroy`  | A pre-receive hook environment was deleted. Para obtener más información, consulta la sección "[Crear un ambiente de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)".    |
-| `pre_receive_environment.download` | A pre-receive hook environment was downloaded. Para obtener más información, consulta la sección "[Crear un ambiente de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)". |
-| `pre_receive_environment.update`   | A pre-receive hook environment was updated. Para obtener más información, consulta la sección "[Crear un ambiente de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)".    |
+| Acción                             | Descripción                                                                                                                                                                                                                                               |
+| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `pre_receive_environment.create`   | Se creó un ambiente de gancho de pre-recepción. Para obtener más información, consulta la sección "[Crear un ambiente de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)".      |
+| `pre_receive_environment.destroy`  | Se borró un ambiente de gancho de pre-recepción. Para obtener más información, consulta la sección "[Crear un ambiente de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)".     |
+| `pre_receive_environment.download` | Se descargó un ambiente de gancho de pre-recepción. Para obtener más información, consulta la sección "[Crear un ambiente de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)".  |
+| `pre_receive_environment.update`   | Se actualizó un ambiente de gancho de pre-recepción. Para obtener más información, consulta la sección "[Crear un ambiente de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)". |
 
-## `pre_receive_hook` category actions
+## Acciones de la categoría `pre_receive_hook`
 
-| Acción                           | Descripción                                                                                                                                                                                                                                                                                                                                                                              |
-| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `pre_receive_hook.create`        | Se creó un gancho de pre-recepción. For more information, see "[Creating pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#creating-pre-receive-hooks)."                                                                                                                                   |
-| `pre_receive_hook.destroy`       | A pre-receive hook was deleted. For more information, see "[Deleting pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#deleting-pre-receive-hooks)."                                                                                                                                       |
-| `pre_receive_hook.enforcement`   | A pre-receive hook enforcement setting allowing repository and organization administrators to override the hook configuration was enabled or disabled. For more information, see "[Managing pre-receive hooks on the GitHub Enterprise Server appliance](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance)." |
-| `pre_receive_hook.rejected_push` | A pre-receive hook rejected a push.                                                                                                                                                                                                                                                                                                                                                      |
-| `pre_receive_hook.update`        | Se creó un gancho de pre-recepción. For more information, see "[Editing pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#editing-pre-receive-hooks)."                                                                                                                                     |
-| `pre_receive_hook.warned_push`   | A pre-receive hook warned about a push.                                                                                                                                                                                                                                                                                                                                                  |
+| Acción                           | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `pre_receive_hook.create`        | Se creó un gancho de pre-recepción. Para obtener más información, consulta la sección "[Crear ganchos de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#creating-pre-receive-hooks)".                                                                                                                                                                          |
+| `pre_receive_hook.destroy`       | Se borró un gancho de pre-recepción. Para obtener más información, consulta la sección "[Borrar ganchos de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#deleting-pre-receive-hooks)".                                                                                                                                                                        |
+| `pre_receive_hook.enforcement`   | Se habilitó o inhabilitó el ajuste para requerir un gancho de pre-recepción que permite que los administradores de organizaciones y repositorios anulen la configuración del gancho. Para obtener más información, consulta la sección "[Administrar ganchos de pre-recepción en el aplicativo de GitHub Enterprise Server](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance)". |
+| `pre_receive_hook.rejected_push` | Un gancho de pre-recepción rechazó una subida.                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `pre_receive_hook.update`        | Se creó un gancho de pre-recepción. Para obtener más información, consulta la sección "[Editar ganchos de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#editing-pre-receive-hooks)".                                                                                                                                                                          |
+| `pre_receive_hook.warned_push`   | Un gancho de pre-recepción advirtió sobre una subida.                                                                                                                                                                                                                                                                                                                                                                                                       |
 {%- endif %}
 
-## `private_repository_forking` category actions
+## Acciones de la categoría `private_repository_forking`
 
 | Acción                               | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `private_repository_forking.clear`   | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for allowing forks of private and internal repositories, for a repository, organization or enterprise. Para obtener más información, consulta las secciones "[Administrar la política de bifurcación para tu repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Administrar la política de bifurcación para tu organización](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) y, para empresas: "[Requerir una política para bifurcar los repositorios privados o internos](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)".                                                                                                       |
-| `private_repository_forking.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled the policy setting for allowing forks of private and internal repositories, for a repository, organization or enterprise. Jamás se permite que los repositorios privados e internos se bifurquen. Para obtener más información, consulta las secciones "[Administrar la política de bifurcación para tu repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Administrar la política de bifurcación para tu organización](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) y, para empresas: "[Requerir una política para bifurcar los repositorios privados o internos](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)".                              |
+| `private_repository_forking.clear`   | Un propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif %} quitó el ajuste de política para permitir las bifurcaciones de los repositorios privados e internos, para un repositorio, organización o empresa. Para obtener más información, consulta las secciones "[Administrar la política de bifurcación para tu repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Administrar la política de bifurcación para tu organización](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) y, para empresas: "[Requerir una política para bifurcar los repositorios privados o internos](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)".                                                                              |
+| `private_repository_forking.disable` | Un propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif %} inhabilitó el ajuste de política para permitir las bifurcaciones de los repositorios privados e internos, para un repositorio, organización o empresa. Jamás se permite que los repositorios privados e internos se bifurquen. Para obtener más información, consulta las secciones "[Administrar la política de bifurcación para tu repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Administrar la política de bifurcación para tu organización](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) y, para empresas: "[Requerir una política para bifurcar los repositorios privados o internos](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)". |
 | `private_repository_forking.enable`  | Un propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif %} habilitó el ajuste de política para permitir las bifurcaciones de los repositorios privados e internos, para un repositorio, organización o empresa. Siempre se permite que los repositorios privados e internos se bifurquen. Para obtener más información, consulta las secciones "[Administrar la política de bifurcación para tu repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Administrar la política de bifurcación para tu organización](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) y, para empresas: "[Requerir una política para bifurcar los repositorios privados o internos](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)". |
 
 {%- ifversion fpt or ghec %}
@@ -848,14 +848,14 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 {%- ifversion ghes %}
 | `protected_branch.update_allow_deletions_enforcement_level` | Se actualizó el requisito de permitir que los usuarios con acceso de subida borren ramas coincidentes en una rama. | `protected_branch.update_allow_force_pushes_enforcement_level` | Se actualizó el requisito de permitir subidas forzadas para todos los usuarios con acceso de subida en una rama. | `protected_branch.update_linear_history_requirement_enforcement_level` | Se actualizó el requisito de tener un historial de confirmaciones linear en una rama.
 {%- endif %}
-| `protected_branch.update_pull_request_reviews_enforcement_level` | Se actualizó el requisito de tener revisiones de solicitudes de cambio en una rama. Puede ser una de entre `0`(desactivado), `1`(no adminsitradores), `2`(todos). | `protected_branch.update_require_code_owner_review` | Se actualizó el requisito de tener revisiones de propietarios de código en una rama. | `protected_branch.update_required_approving_review_count` | Se actualizó el requisito de tener una cantidad de aprobaciones antes de fusionar en una rama. | `protected_branch.update_required_status_checks_enforcement_level` | Se actualizó el requisito de tener verificaciones de estado en una rama. | `protected_branch.update_signature_requirement_enforcement_level` | Se actualizó el requisito de tener firmas de confirmaciones en una rama. | `protected_branch.update_strict_required_status_checks_policy` | Enforcement of required status checks was updated on a branch. | `protected_branch.update_name` | A branch name pattern was updated for a branch.
+| `protected_branch.update_pull_request_reviews_enforcement_level` | Se actualizó el requisito de tener revisiones de solicitudes de cambio en una rama. Puede ser una de entre `0`(desactivado), `1`(no adminsitradores), `2`(todos). | `protected_branch.update_require_code_owner_review` | Se actualizó el requisito de tener revisiones de propietarios de código en una rama. | `protected_branch.update_required_approving_review_count` | Se actualizó el requisito de tener una cantidad de aprobaciones antes de fusionar en una rama. | `protected_branch.update_required_status_checks_enforcement_level` | Se actualizó el requisito de tener verificaciones de estado en una rama. | `protected_branch.update_signature_requirement_enforcement_level` | Se actualizó el requisito de tener firmas de confirmaciones en una rama. | `protected_branch.update_strict_required_status_checks_policy` | Se actualizó el requisito de verificaciones de estado en una rama. | `protected_branch.update_name` | Se actualizó un patrón de nombre de rama para una rama.
 
 ## acciones de la categoría `public_key`
 
 | Acción                              | Descripción                                                                                                          |
 | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
 | `public_key.create`                 | Una llave SSH se [agregó][add key] a una cuenta de usuario o una [llave de despliegue][] se agregó a un repositorio. |
-| `public_key.delete`                 | An SSH key was removed from a user account or a [deploy key][] was removed from a repository.                        |
+| `public_key.delete`                 | Una clave SSH se eliminó de una cuenta de usuario o una [llave de implementación][] se eliminó de un repositorio.    |
 | `public_key.update`                 | A user account's SSH key or a repository's [deploy key][] was updated.                                               |
 | `public_key.unverification_failure` | A user account's SSH key or a repository's [deploy key][] was unable to be unverified.                               |
 | `public_key.unverify`               | A user account's SSH key or a repository's [deploy key][] was unverified.                                            |
@@ -919,53 +919,53 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 {%- ifversion ghes %}
 | `repo.config.disable_anonymous_git_access`| Anonymous Git read access was disabled for a repository. Para obtener más información, consulta "[Habilitar acceso de lectura anónimo de Git para un repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." | `repo.config.enable_anonymous_git_access` | Anonymous Git read access was enabled for a repository. Para obtener más información, consulta "[Habilitar acceso de lectura anónimo de Git para un repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." | `repo.config.lock_anonymous_git_access` | A repository's anonymous Git read access setting was locked, preventing repository administrators from changing (enabling or disabling) this setting. Para obtener más información, consulta "[Evitar que los usuarios cambien el acceso de lectura anónimo de Git](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)." | `repo.config.unlock_anonymous_git_access` | A repository's anonymous Git read access setting was unlocked, allowing repository administrators to change (enable or disable) this setting. Para obtener más información, consulta "[Evitar que los usuarios cambien el acceso de lectura anónimo de Git](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."
 {%- endif %}
-| `repo.create` | A repository was created. | `repo.create_actions_secret` | A {% data variables.product.prodname_actions %} secret was created for a repository. Para obtener más información, consulta la sección "[Crear secretos cifrados para un repositorio](/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository)". | `repo.create_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was created for a repository. | `repo.destroy` | A repository was deleted.
+| `repo.create` | A repository was created. | `repo.create_actions_secret` | A {% data variables.product.prodname_actions %} secret was created for a repository. Para obtener más información, consulta la sección "[Crear secretos cifrados para un repositorio](/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository)". | `repo.create_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was created for a repository. | `repo.destroy` | Se borró un repositorio.
 {%- ifversion ghes %}
-| `repo.disk_archive`  | A repository was archived on disk. Para obtener más información, consulta la sección "[Archivar los repositorios](/repositories/archiving-a-github-repository/archiving-repositories)".
+| `repo.disk_archive`  | Se archivó un repositorio en disco. Para obtener más información, consulta la sección "[Archivar los repositorios](/repositories/archiving-a-github-repository/archiving-repositories)".
 {%- endif %}
-| `repo.download_zip` | A source code archive of a repository was downloaded as a ZIP file. | `repo.pages_cname` | A {% data variables.product.prodname_pages %} custom domain was modified in a repository. | `repo.pages_create` | A {% data variables.product.prodname_pages %} site was created. | `repo.pages_destroy` | A {% data variables.product.prodname_pages %} site was deleted. | `repo.pages_https_redirect_disabled` | HTTPS redirects were disabled for a {% data variables.product.prodname_pages %} site. | `repo.pages_https_redirect_enabled` | HTTPS redirects were enabled for a {% data variables.product.prodname_pages %} site. | `repo.pages_source` | A {% data variables.product.prodname_pages %} source was modified. | `repo.pages_private` | A {% data variables.product.prodname_pages %} site visibility was changed to private. | `repo.pages_public` | A {% data variables.product.prodname_pages %} site visibility was changed to public. | `repo.register_self_hosted_runner` | A new self-hosted runner was registered. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a un repositorio](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)". | `repo.remove_self_hosted_runner` | A self-hosted runner was removed. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de un repositorio](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)". | `repo.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was deleted for a repository. | `repo.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was deleted for a repository. | `repo.remove_member` | A collaborator was removed from a repository. | `repo.remove_topic` | A topic was removed from a repository. | `repo.rename` | A repository was renamed.
+| `repo.download_zip` | Se descargó un archivo de código fuente de un repositorio como archivo ZIP. | `repo.pages_cname` | Se modificó un dominio personalizado de {% data variables.product.prodname_pages %} en un repositorio. | `repo.pages_create` | Se creó un sitio de {% data variables.product.prodname_pages %}. | `repo.pages_destroy` | Se borró un sitio de {% data variables.product.prodname_pages %}. | `repo.pages_https_redirect_disabled` | Se inhabilitaron los redireccionamientos HTTPS para un sitio de {% data variables.product.prodname_pages %}. | `repo.pages_https_redirect_enabled` | Se habilitaron los redireccionamientos HTTPS para un sitio de {% data variables.product.prodname_pages %}. | `repo.pages_source` | Se modificó el código fuente de un sitio de {% data variables.product.prodname_pages %}. | `repo.pages_private` | Se cambió la visibilidad de un sitio de {% data variables.product.prodname_pages %} a privado. | `repo.pages_public` | Se cambió la visibilidad de un sitio de {% data variables.product.prodname_pages %} a público. | `repo.register_self_hosted_runner` | Se registró un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a un repositorio](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)". | `repo.remove_self_hosted_runner` | Se eliminó un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de un repositorio](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)". | `repo.remove_actions_secret` | Se borró un secreto de {% data variables.product.prodname_actions %} en un repositorio. | `repo.remove_integration_secret` | Un secreto de integración del {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} o de {% data variables.product.prodname_codespaces %}{% endif %} se borró en un repositorio. | `repo.remove_member` | Se eliminó a un colaborador de un repositorio. | `repo.remove_topic` | Se eliminó un tema de un repositorio. | `repo.rename` | Se renombró un repositorio.
 {%- ifversion fpt or ghec %}
-| `repo.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for a repository. Para obtener más información, consulte la sección "[Configurar la aprobación requerida para los flujos de trabajo desde las bifurcaciones públicas](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)".
+| `repo.set_actions_fork_pr_approvals_policy` | Se cambió el ajuste para requerir aprobaciones de los flujos de trabajo de las bifurcaciones públicas para un repositorio. Para obtener más información, consulte la sección "[Configurar la aprobación requerida para los flujos de trabajo desde las bifurcaciones públicas](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)".
 {%- endif %}
-| `repo.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs in a repository was changed. Para obtener más información, consulta la sección "[Configurar el periodo de retención de los artefactos de las {% data variables.product.prodname_actions %} y las bitácoras en tu repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)". | `repo.self_hosted_runner_online` | The runner application was started. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `repo.self_hosted_runner_offline` | The runner application was stopped. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `repo.self_hosted_runner_updated` | The runner application was updated. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | `repo.staff_unlock` | An enterprise administrator or GitHub staff (with permission from a repository administrator) temporarily unlocked the repository. | `repo.transfer` | A user accepted a request to receive a transferred repository. | `repo.transfer_outgoing` | A repository was transferred to another repository network. | `repo.transfer_start` | A user sent a request to transfer a repository to another user or organization. | `repo.unarchived` | A repository was unarchived. Para obtener más información, consulta la sección "[Archivar un repositorio de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | `repo.update_actions_settings` | A repository administrator changed {% data variables.product.prodname_actions %} policy settings for a repository. | `repo.update_actions_secret` | A {% data variables.product.prodname_actions %} secret was updated. | `repo.update_actions_access_settings` | The setting to control how a repository was used by {% data variables.product.prodname_actions %} workflows in other repositories was changed. | `repo.update_default_branch` | The default branch for a repository was changed. | `repo.update_integration_secret` | A {% data variables.product.prodname_dependabot %} or {% data variables.product.prodname_codespaces %} integration secret was updated for a repository. | `repo.update_member` | A user's permission to a repository was changed.
+| `repo.set_actions_retention_limit` | Se cambió el periodo de retención para artefactos y bitácoras de {% data variables.product.prodname_actions %} en un repositorio. Para obtener más información, consulta la sección "[Configurar el periodo de retención de los artefactos de las {% data variables.product.prodname_actions %} y las bitácoras en tu repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)". | `repo.self_hosted_runner_online` | Se inició la aplicación ejecutora. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `repo.self_hosted_runner_offline` | Se detuvo la aplicación ejecutora. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `repo.self_hosted_runner_updated` | Se actualizó la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | `repo.staff_unlock` | Un administrador de empresa o miembro del personal de GitHub (con permiso de un administrador de repositorio) bloqueó el repositorio temporalmente. | `repo.transfer` | Un usuario aceptó una solicitud para recibir un repositorio transferido. | `repo.transfer_outgoing` | Se transfirió un repositorio a la red de otro repositorio. | `repo.transfer_start` | Un usuario envió una solicitud para transferir un repositorio a otra organización de usuario. | `repo.unarchived` | Se dejó de archivar un repositorio. Para obtener más información, consulta la sección "[Archivar un repositorio de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | `repo.update_actions_settings` | Un administrador de repositorio cambió los ajustes de política de {% data variables.product.prodname_actions %} para un repositorio. | `repo.update_actions_secret` | Se actualizó un secreto de {% data variables.product.prodname_actions %}. | `repo.update_actions_access_settings` | Se cambió el ajuste para controlar la forma en la que los flujos de trabajo de {% data variables.product.prodname_actions %} utilizaron un repositorio en otros repositorios. | `repo.update_default_branch` | Se cambió la rama predeterminada de un repositorio. | `repo.update_integration_secret` | Se actualizó un secreto de integración del {% data variables.product.prodname_dependabot %} o de {% data variables.product.prodname_codespaces %} en un repositorio. | `repo.update_member` | Se cambió el permiso de un usuario en un repositorio.
 
 {%- ifversion fpt or ghec %}
 ## acciones de la categoría `repository_advisory`
 
-| Acción                                 | Descripción                                                                                                                                                                                                                                                 |
-| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `repository_advisory.close`            | Someone closed a security advisory. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". |
-| `repository_advisory.cve_request`      | Someone requested a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory.                                                                                                      |
-| `repository_advisory.github_broadcast` | {% data variables.product.prodname_dotcom %} made a security advisory public in the {% data variables.product.prodname_advisory_database %}.                                                                                                              |
-| `repository_advisory.github_withdraw`  | {% data variables.product.prodname_dotcom %} withdrew a security advisory that was published in error.                                                                                                                                                      |
-| `repository_advisory.open`             | Someone opened a draft security advisory.                                                                                                                                                                                                                   |
-| `repository_advisory.publish`          | Someone publishes a security advisory.                                                                                                                                                                                                                      |
-| `repository_advisory.reopen`           | Someone reopened as draft security advisory.                                                                                                                                                                                                                |
-| `repository_advisory.update`           | Someone edited a draft or published security advisory.                                                                                                                                                                                                      |
+| Acción                                 | Descripción                                                                                                                                                                                                                                                      |
+| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repository_advisory.close`            | Alguien cerró una asesoría de seguridad. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". |
+| `repository_advisory.cve_request`      | Alguien solicitó un número de CVE (Exposiciones y Vulnerabilidades Comunes) de {% data variables.product.prodname_dotcom %} para un borrador de asesoría de seguridad.                                                                                           |
+| `repository_advisory.github_broadcast` | {% data variables.product.prodname_dotcom %} hizo pública una asesoría de seguridad en la {% data variables.product.prodname_advisory_database %}.                                                                                                             |
+| `repository_advisory.github_withdraw`  | {% data variables.product.prodname_dotcom %} retiró una asesoría de seguridad que se publicó erróneamente.                                                                                                                                                       |
+| `repository_advisory.open`             | Alguien abrió un borrador de asesoría de seguridad.                                                                                                                                                                                                              |
+| `repository_advisory.publish`          | Alguien publicó una asesoría de seguridad.                                                                                                                                                                                                                       |
+| `repository_advisory.reopen`           | Alguien volvió a abrir una asesoría de seguridad como borrador.                                                                                                                                                                                                  |
+| `repository_advisory.update`           | Alguien editó una asesoría de seguridad en borrador o publicada.                                                                                                                                                                                                 |
 
 ## Acciones de la categoría `repository_content_analysis`
 
-| Acción                                | Descripción                                                                                                                                                                                     |
-| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `repository_content_analysis.enable`  | An organization owner or repository administrator [enabled data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).  |
-| `repository_content_analysis.disable` | An organization owner or repository administrator [disabled data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository). |
+| Acción                                | Descripción                                                                                                                                                                                                                |
+| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repository_content_analysis.enable`  | Un propietario de organización o administrador de repositorio [habilitó los ajustes de uso de datos en un repositorio privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).     |
+| `repository_content_analysis.disable` | Un propietario de organización o administrador de repositorio [inhabilitó los ajustes de uso de datos para un repositorio privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository). |
 
 ## Acciones de la categoría `repository_dependency_graph`
 
-| Acción                                | Descripción                                                                                                                                                                                                                                                         |
-| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `repository_dependency_graph.disable` | A repository owner or administrator disabled the dependency graph for a private repository. 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)". |
-| `repository_dependency_graph.enable`  | A repository owner or administrator enabled the dependency graph for a private repository.                                                                                                                                                                          |
+| Acción                                | Descripción                                                                                                                                                                                                                                                                              |
+| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repository_dependency_graph.disable` | Un propietario o administrador de repositorio inhabilitó la gráfica de dependencias para un repositorio privado. 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)". |
+| `repository_dependency_graph.enable`  | Un propietario o administrador de repositorio habilitó la gráfica de dependencias para un repositorio privado.                                                                                                                                                                           |
 {%- endif %}
 
-## `repository_image` category actions
+## Acciones de la categoría `repository_image`
 
-| Acción                     | Descripción                                      |
-| -------------------------- | ------------------------------------------------ |
-| `repository_image.create`  | An image to represent a repository was uploaded. |
-| `repository_image.destroy` | An image to represent a repository was deleted.  |
+| Acción                     | Descripción                                            |
+| -------------------------- | ------------------------------------------------------ |
+| `repository_image.create`  | Se cargó una imagen para representar a un repositorio. |
+| `repository_image.destroy` | Se borró una imagen para representar un repositorio.   |
 
-## `repository_invitation` category actions
+## Acciones de la categoría `repository_invitation`
 
 | Acción                         | Descripción                                      |
 | ------------------------------ | ------------------------------------------------ |
@@ -1095,91 +1095,91 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 {%- ifversion ghec or ghes or ghae %}
 ## `security_key` category actions
 
-| Acción                  | Descripción                                   |
-| ----------------------- | --------------------------------------------- |
-| `security_key.register` | A security key was registered for an account. |
-| `security_key.remove`   | A security key was removed from an account.   |
+| Acción                  | Descripción                                      |
+| ----------------------- | ------------------------------------------------ |
+| `security_key.register` | A security key was registered for an account.    |
+| `security_key.remove`   | Se eliminó una llave de seguridad de una cuenta. |
 {%- endif %}
 
 {%- ifversion fpt or ghec %}
 ## acciones de la categoría `sponsors`
 
-| Acción                                                 | Descripción                                                                                                                                                                                                                                                                                                                                    |
-| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `sponsors.agreement_sign`                              | A {% data variables.product.prodname_sponsors %} agreement was signed on behalf of an organization.                                                                                                                                                                                                                                            |
-| `sponsors.custom_amount_settings_change`               | Custom amounts for {% data variables.product.prodname_sponsors %} were enabled or disabled, or the suggested custom amount was changed. Para obtener más información, consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)".                 |
-| `sponsors.fiscal_host_change`                          | The fiscal host for a {% data variables.product.prodname_sponsors %} listing was updated.                                                                                                                                                                                                                                                      |
-| `sponsors.withdraw_agreement_signature`                | A signature was withdrawn from a {% data variables.product.prodname_sponsors %} agreement that applies to an organization.                                                                                                                                                                                                                     |
-| `sponsors.repo_funding_links_file_action`              | The FUNDING file in a repository was changed. Para obtener más información, consulta "[Mostrar un botón de patrocinador en tu repositorio](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository)".                                                         |
-| `sponsors.sponsor_sponsorship_cancel`                  | A sponsorship was canceled. For more information, see "[Downgrading a sponsorship](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)."                                                                                                                                                                                  |
-| `sponsors.sponsor_sponsorship_create`                  | A sponsorship was created, by sponsoring an account. Para obtener más información, consulta la sección "[Patrocinar a un contribuyente de código libre](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)".                                                                                                 |
-| `sponsors.sponsor_sponsorship_payment_complete`        | After you sponsor an account and a payment has been processed, the sponsorship payment was marked as complete. Para obtener más información, consulta la sección "[Patrocinar a un contribuyente de código libre](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)".                                       |
-| `sponsors.sponsor_sponsorship_preference_change`       | The option to receive email updates from a sponsored account was changed. Para obtener más información, consulta "[Administar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)".                                                                                                                        |
-| `sponsors.sponsor_sponsorship_tier_change`             | A sponsorship was upgraded or downgraded. Para obtener más información, consulta "[Actualizar un patrocinio](/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)."                                          |
-| `sponsors.sponsored_developer_approve`                 | A {% data variables.product.prodname_sponsors %} account was approved. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)".                        |
-| `sponsors.sponsored_developer_create`                  | A {% data variables.product.prodname_sponsors %} account was created. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)".                         |
-| `sponsors.sponsored_developer_disable`                 | A {% data variables.product.prodname_sponsors %} account was disabled.                                                                                                                                                                                                                                                                         |
-| `sponsors.sponsored_developer_profile_update`          | You edit a sponsored organization profile. For more information, see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)."                                                                           |
-| `sponsors.sponsored_developer_redraft`                 | A {% data variables.product.prodname_sponsors %} account was returned to draft state from approved state.                                                                                                                                                                                                                                      |
-| `sponsors.sponsored_developer_request_approval`        | An application for {% data variables.product.prodname_sponsors %} was submitted for approval. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)". |
-| `sponsors.sponsored_developer_tier_description_update` | The description for a sponsorship tier was changed. Para obtener más información, consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)".                                                                                                     |
-| `sponsors.update_tier_welcome_message`                 | The welcome message for a {% data variables.product.prodname_sponsors %} tier for an organization was updated.                                                                                                                                                                                                                                 |
-| `sponsors.update_tier_repository`                      | A {% data variables.product.prodname_sponsors %} tier changed access for a repository.                                                                                                                                                                                                                                                         |
+| Acción                                                 | Descripción                                                                                                                                                                                                                                                                                                                                         |
+| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `sponsors.agreement_sign`                              | Se firmó un acuerdo de {% data variables.product.prodname_sponsors %} en nombre de una organización.                                                                                                                                                                                                                                                |
+| `sponsors.custom_amount_settings_change`               | Se habilitaron o inhabilitaron cantidades personalizadas para {% data variables.product.prodname_sponsors %} o la cantidad personalizada sugerida se cambió. Para obtener más información, consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)". |
+| `sponsors.fiscal_host_change`                          | Se actualizó el host fiscal para un listado de {% data variables.product.prodname_sponsors %}.                                                                                                                                                                                                                                                      |
+| `sponsors.withdraw_agreement_signature`                | Se retiró una firma de un acuerdo de {% data variables.product.prodname_sponsors %} que aplica a una organización.                                                                                                                                                                                                                                  |
+| `sponsors.repo_funding_links_file_action`              | Se cambió el archivo de "FUNDING" en un repositorio. Para obtener más información, consulta "[Mostrar un botón de patrocinador en tu repositorio](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository)".                                                       |
+| `sponsors.sponsor_sponsorship_cancel`                  | Se canceló un patrocinio. Para obtener más información, consulta la sección "[Degradar un patrocinio](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)".                                                                                                                                                                    |
+| `sponsors.sponsor_sponsorship_create`                  | Se creó un patrocinio al patrocinar una cuenta. Para obtener más información, consulta la sección "[Patrocinar a un contribuyente de código libre](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)".                                                                                                           |
+| `sponsors.sponsor_sponsorship_payment_complete`        | Después de haber patrocinado una cuenta y de que se procesó el pago de dicho patrocinio, este se marcó como completo. Para obtener más información, consulta la sección "[Patrocinar a un contribuyente de código libre](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)".                                     |
+| `sponsors.sponsor_sponsorship_preference_change`       | Se cambió la opción para recibir actualizaciones por correo electrónico de una cuenta patrocinada. Para obtener más información, consulta "[Administar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)".                                                                                                    |
+| `sponsors.sponsor_sponsorship_tier_change`             | Se mejoró o degradó un patrocinio. Para obtener más información, consulta "[Actualizar un patrocinio](/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)."                                                      |
+| `sponsors.sponsored_developer_approve`                 | Se aprobó una cuenta de {% data variables.product.prodname_sponsors %}. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)".                            |
+| `sponsors.sponsored_developer_create`                  | Se creó una cuenta de {% data variables.product.prodname_sponsors %}. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)".                              |
+| `sponsors.sponsored_developer_disable`                 | Se inhabilitó una cuenta de {% data variables.product.prodname_sponsors %}.                                                                                                                                                                                                                                                                         |
+| `sponsors.sponsored_developer_profile_update`          | Editaste un perfil de organización patrocinada. Para obtener más información, consulta la sección "[Editar los detalles de tu perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)".                                              |
+| `sponsors.sponsored_developer_redraft`                 | Se devolvió una cuenta de {% data variables.product.prodname_sponsors %} a su estado de borrador desde un estado aprobado.                                                                                                                                                                                                                          |
+| `sponsors.sponsored_developer_request_approval`        | Se emitió una aplicación de {% data variables.product.prodname_sponsors %} para su aprobación. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)".     |
+| `sponsors.sponsored_developer_tier_description_update` | Se cambió la descripción para un nivel de patrocinio. Para obtener más información, consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)".                                                                                                        |
+| `sponsors.update_tier_welcome_message`                 | Se actualizó el mensaje para un nivel de {% data variables.product.prodname_sponsors %} en una organización.                                                                                                                                                                                                                                        |
+| `sponsors.update_tier_repository`                      | Cambió el acceso de un nivel de {% data variables.product.prodname_sponsors %} para un repositorio.                                                                                                                                                                                                                                                 |
 {%- endif %}
 
 {%- ifversion ghec or ghes or ghae %}
-## `ssh_certificate_authority` category actions
+## Acciones de la categoría `ssh_certificate_authority`
 
 | Acción                              | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
 | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `ssh_certificate_authority.create`  | An SSH certificate authority for an organization or enterprise was created. Para obtener más información, consulta las secciones "[Administrar las autoridades de certificados SSH de tu organización](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" y "[Administrar las autoridades de certificados SSH para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)". |
-| `ssh_certificate_authority.destroy` | An SSH certificate authority for an organization or enterprise was deleted. Para obtener más información, consulta las secciones "[Administrar las autoridades de certificados SSH de tu organización](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" y "[Administrar las autoridades de certificados SSH para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)". |
+| `ssh_certificate_authority.create`  | Se creó una autoridad de certificados SSH para una organización o empresa. Para obtener más información, consulta las secciones "[Administrar las autoridades de certificados SSH de tu organización](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" y "[Administrar las autoridades de certificados SSH para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)".  |
+| `ssh_certificate_authority.destroy` | Se borró una autoridad de certificados SSH para una organización o empresa. Para obtener más información, consulta las secciones "[Administrar las autoridades de certificados SSH de tu organización](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" y "[Administrar las autoridades de certificados SSH para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)". |
 
-## `ssh_certificate_requirement` category actions
+## Acciones de la categoría `ssh_certificate_requirement`
 
-| Acción                                | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ssh_certificate_requirement.enable`  | The requirement for members to use SSH certificates to access an organization resources was enabled. Para obtener más información, consulta las secciones "[Administrar las autoridades de certificados SSH de tu organización](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" y "[Administrar las autoridades de certificados SSH para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)".  |
-| `ssh_certificate_requirement.disable` | The requirement for members to use SSH certificates to access an organization resources was disabled. Para obtener más información, consulta las secciones "[Administrar las autoridades de certificados SSH de tu organización](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" y "[Administrar las autoridades de certificados SSH para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)". |
+| Acción                                | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `ssh_certificate_requirement.enable`  | Se habilitó el requisito para que los miembros utilicen certificados SSH para acceder a los recursos de una organización. Para obtener más información, consulta las secciones "[Administrar las autoridades de certificados SSH de tu organización](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" y "[Administrar las autoridades de certificados SSH para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)".   |
+| `ssh_certificate_requirement.disable` | Se inhabilitó el requisito para que los miembros utilicen certificados SSH para acceder a los recursos de una organización. Para obtener más información, consulta las secciones "[Administrar las autoridades de certificados SSH de tu organización](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" y "[Administrar las autoridades de certificados SSH para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)". |
 {%- endif %}
 
-## `staff` category actions
+## Acciones de la categoría `staff`
 
-| Acción               | Descripción                                                                                                                                                      |
-| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `staff.disable_repo` | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator disabled access to a repository and all of its forks.   |
-| `staff.enable_repo`  | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator re-enabled access to a repository and all of its forks. |
+| Acción               | Descripción                                                                                                                                                                             |
+| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `staff.disable_repo` | Un administrador de organización{% ifversion ghes %}, repositorio o sitio{% else %} o repositorio{% endif %} inhabilitó el acceso a un repositorio y a todas sus bifurcaciones.         |
+| `staff.enable_repo`  | Un administrador de organización{% ifversion ghes %}, repositorio o sitio{% else %} o repositorio{% endif %} volvió a habilitar el acceso a un repositorio y a todas sus bifurcaciones. |
 {%- ifversion ghes > 3.2 or ghae %}
-| `staff.exit_fake_login`       | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} ended an impersonation session on {% data variables.product.product_name %}. | `staff.fake_login`            | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} signed into {% data variables.product.product_name %} as another user.
+| `staff.exit_fake_login`       | Un propietario de una empresa{% ifversion ghes %} o administrador de sitio{% endif %} finalizó una sesión de suplantación en {% data variables.product.product_name %}. | `staff.fake_login`            | Un propietario de empresa{% ifversion ghes %} o administrador de sitio{% endif %} inició sesión en {% data variables.product.product_name %} como otro usuario.
 {%- endif %}
-| `staff.repo_lock`             | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator locked (temporarily gained full access to) a user's private repository. | `staff.repo_unlock`           | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator unlocked (ended their temporary access to) a user's private repository.
+| `staff.repo_lock`             | Un administrador de organización{% ifversion ghes %}, repositorio o sitio{% else %} o repositorio{% endif %} bloqueó (obtuvo acceso total y temporal a) el repositorio privado de un usuario. | `staff.repo_unlock`             | Un administrador de organización{% ifversion ghes %}, repositorio o sitio{% else %} o repositorio{% endif %} desbloqueó (finalizó su acceso total y temporal a) el repositorio privado de un usuario.
 {%- ifversion ghes %}
-| `staff.search_audit_log` | A site administrator performed a search of the site admin audit log.
+| `staff.search_audit_log` | Un administrador de sitió llevó a cabo la búsqueda de la bitácora de auditoría del administrador de sitio.
 {%- endif %}
-| `staff.set_domain_token_expiration` | {% ifversion ghes %}A site administrator or {% endif %}GitHub staff set the verification code expiry time for an organization or enterprise domain. {% ifversion ghec or ghes %}Para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" y "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}
+| `staff.set_domain_token_expiration` | {% ifversion ghes %}Un administrador de sitio o {% endif %}miembro del personal de GitHub configuró el tiempo de vencimiento del código de verificación para un dominio de organización o de empresa. {% ifversion ghec or ghes %}Para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" y "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}
 {%- ifversion ghes %}
-| `staff.unlock`                | A site administrator unlocked (temporarily gained full access to) all of a user's private repositories.
+| `staff.unlock`                | Un administrador de sitio desbloqueó (obtuvo acceso total y temporal a) todos los repositorios privados de un usuario.
 {%- endif %}
-| `staff.unverify_domain` | |{% ifversion ghes %}A site administrator or {% endif %}GitHub staff unverified an organization or enterprise domain. {% ifversion ghec or ghes %}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)" y "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}| | `staff.verify_domain` | {% ifversion ghes %}Un administrador de sitio o {% endif %}el personal de GitHub verificó un dominio de empresa u organización. {% ifversion ghec or ghes %}Para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" y "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}
+| `staff.unverify_domain` | |{% ifversion ghes %}Un administrador de sitio o {% endif %}miembro del personal de GitHub dejó de verificar un dominio de organización o de empresa. {% ifversion ghec or ghes %}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)" y "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}| | `staff.verify_domain` | {% ifversion ghes %}Un administrador de sitio o {% endif %}el personal de GitHub verificó un dominio de empresa u organización. {% ifversion ghec or ghes %}Para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" y "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}
 {%- ifversion ghes %}
-| `staff.view_audit_log` | A site administrator viewed the site admin audit log.
+| `staff.view_audit_log` | Un administrador de sitio vio la bitácora de auditoría para administradores de sitio.
 {%- endif %}
 
 ## acciones de la categoría `team`
 
-| Acción                    | Descripción                                                                                                                                                                                                                               |
-| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `team.add_member`         | A member of an organization was added to a team. Para obtener más información, consulta la sección "[Agregar miembros organizacionales a un equipo](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)". |
-| `team.add_repository`     | A team was given access and permissions to a repository.                                                                                                                                                                                  |
-| `team.change_parent_team` | A child team was created or a child team's parent was changed. For more information, see "[Moving a team in your organization’s hierarchy](/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy)."  |
-| `team.change_privacy`     | A team's privacy level was changed. For more information, see "[Changing team visibility](/organizations/organizing-members-into-teams/changing-team-visibility)."                                                                        |
-| `team.create`             | Se agregó una cuenta de usuario o repositorio a un equipo.                                                                                                                                                                                |
-| `team.delete`             | Se eliminó una cuenta de usuario o repositorio de un equipo.                                                                                                                                                                              |
-| `team.destroy`            | Se eliminó un equipo.                                                                                                                                                                                                                     |
+| Acción                    | Descripción                                                                                                                                                                                                                                                            |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `team.add_member`         | Se agregó a un miembro de una organización a un equipo. Para obtener más información, consulta la sección "[Agregar miembros organizacionales a un equipo](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)".                       |
+| `team.add_repository`     | Se otorgó acceso y permisos a un repositorio a un equipo.                                                                                                                                                                                                              |
+| `team.change_parent_team` | Se creó un equipo hijo o se cambió el padre de un equipo hijo. Para obtener más información, consulta la sección "[Mover a un equipo en la jerarquía de tu organización](/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy)". |
+| `team.change_privacy`     | Se cambió el nivel de privacidad de un equipo. Para obtener más información, consulta la sección "[Cambiar la visibilidad de un equipo](/organizations/organizing-members-into-teams/changing-team-visibility)".                                                       |
+| `team.create`             | Se agregó una cuenta de usuario o repositorio a un equipo.                                                                                                                                                                                                             |
+| `team.delete`             | Se eliminó una cuenta de usuario o repositorio de un equipo.                                                                                                                                                                                                           |
+| `team.destroy`            | Se eliminó un equipo.                                                                                                                                                                                                                                                  |
 {%- ifversion ghec or ghes or ghae %}
-| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member. | `team.promote_maintainer` | A user was promoted from a team member to a team maintainer. For more information, see "[Promoting an organization member to team maintainer](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member#promoting-an-organization-member-to-team-maintainer)."
+| `team.demote_maintainer` | Se bajó de categoría a un usuario de mantenedor de equipo a miembro de equipo. | `team.promote_maintainer` | Se promovió a un usuario de miembro a mantenedor de equipo. Para obtener más información, consulta la sección "[Promover a un miembro de la organización a mantenedor de equipo](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member#promoting-an-organization-member-to-team-maintainer)".
 {%- endif %}
-| `team.remove_member` | A member of an organization was removed from a team. For more information, see "[Removing organization members from a team](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team)." | `team.remove_repository` | A repository was no longer under a team's control. | `team.rename` | A team's name was changed. | `team.update_permission` | A team's access was changed. | `team.update_repository_permission` | A team's permission to a repository was changed.
+| `team.remove_member` | Se eliminó a un miembro de una organización de un equipo. For more information, see "[Removing organization members from a team](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team)." | `team.remove_repository` | A repository was no longer under a team's control. | `team.rename` | A team's name was changed. | `team.update_permission` | A team's access was changed. | `team.update_repository_permission` | A team's permission to a repository was changed.
 
 ## acciones de la categoría `team_discussions`
 
@@ -1236,17 +1236,17 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 {%- ifversion ghes %}
 | `user.promote`                    | An ordinary user account was promoted to a site administrator.
 {%- endif %}
-| `user.recreate` | A user's account was restored. | `user.remove_email`               | An email address was removed from a user account. | `user.remove_large_scale_contributor_flag` | A user account was no longer flagged as a large scale contributor. | `user.rename`                     | A username was changed. | `user.reset_password` | A user reset their account password. | `user.show_private_contributions_count` | A user changed the visibility of their private contributions. The number of contributions to private repositories on the user's profile are now shown. Para obtener más información, consulta la sección "[Publicar u ocultar tus contribuciones privadas en tu perfil](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile)". | `user.sign_in_from_unrecognized_device` | A user signed in from an unrecognized device. | `user.sign_in_from_unrecognized_device_and_location` | A user signed in from an unrecognized device and location. | `user.sign_in_from_unrecognized_location` | A user signed in from an unrecognized location. | `user.suspend`                    | A user account was suspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}. | `user.two_factor_challenge_failure` | A 2FA challenge issued for a user account failed. | `user.two_factor_challenge_success` | A 2FA challenge issued for a user account succeeded. | `user.two_factor_recover` | A user used their 2FA recovery codes. | `user.two_factor_recovery_codes_downloaded` | A user downloaded 2FA recovery codes for their account. | `user.two_factor_recovery_codes_printed` | A user printed 2FA recovery codes for their account. | `user.two_factor_recovery_codes_viewed` | A user viewed 2FA recovery codes for their account. | `user.two_factor_requested`       | A user was prompted for a two-factor authentication code. | `user.unblock_user` | A user was unblocked another user{% ifversion ghes %} or a site administrator{% endif %}. | `user.unminimize_comment` | A comment made by a user was unminimized. | `user.unsuspend` | A user account was unsuspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}.
+| `user.recreate` | A user's account was restored. | `user.remove_email`               | An email address was removed from a user account. | `user.remove_large_scale_contributor_flag` | A user account was no longer flagged as a large scale contributor. | `user.rename`                     | A username was changed. | `user.reset_password` | A user reset their account password. | `user.show_private_contributions_count` | A user changed the visibility of their private contributions. The number of contributions to private repositories on the user's profile are now shown. Para obtener más información, consulta la sección "[Publicar u ocultar tus contribuciones privadas en tu perfil](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile)". | `user.sign_in_from_unrecognized_device` | A user signed in from an unrecognized device. | `user.sign_in_from_unrecognized_device_and_location` | A user signed in from an unrecognized device and location. | `user.sign_in_from_unrecognized_location` | A user signed in from an unrecognized location. | `user.suspend`                    | A user account was suspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}. | `user.two_factor_challenge_failure` | A 2FA challenge issued for a user account failed. | `user.two_factor_challenge_success` | A 2FA challenge issued for a user account succeeded. | `user.two_factor_recover` | A user used their 2FA recovery codes. | `user.two_factor_recovery_codes_downloaded` | Un usuario descargó los códigos de recuperación de 2FA para su cuenta. | `user.two_factor_recovery_codes_printed` | Un usuario imprimió los códigos de recuperación de 2FA para su cuenta. | `user.two_factor_recovery_codes_viewed` | Un usuario vio los códigos de recuperación de 2FA para su cuenta. | `user.two_factor_requested`       | Se solicitó a un usuario el código de autenticación bifactorial. | `user.unblock_user` | Un usuario {% ifversion ghes %} o un administrador de sitio{% endif %}desbloqueó a otro usuario. | `user.unminimize_comment` | Se dejó de minimizar un comentario que hizo un usuario. | `user.unsuspend` | Un propietario de empresa {% ifversion ghes %} o administrador de sitio{% endif %} dejó de suspender una cuenta de usuario.
 {%- endif %}
 
 {%- ifversion ghec or ghes %}
-## `user_license` category actions
+## Acciones de la categoría `user_license`
 
-| Acción                 | Descripción                                                  |
-| ---------------------- | ------------------------------------------------------------ |
-| `user_license.create`  | A seat license for a user in an enterprise was created.      |
-| `user_license.destroy` | A seat license for a user in an enterprise was deleted.      |
-| `user_license.update`  | A seat license type for a user in an enterprise was changed. |
+| Acción                 | Descripción                                                    |
+| ---------------------- | -------------------------------------------------------------- |
+| `user_license.create`  | Se creó una licencia de plaza para un usuario en una empresa.  |
+| `user_license.destroy` | Se borró una licencia de plaza para un usuario en una empresa. |
+| `user_license.update`  | Se cambió un tipo de licencia para un usuario en una empresa.  |
 {%- endif %}
 
 ## Acciones de la categoría `workflows`
@@ -1263,6 +1263,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 
   [add key]: /authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account
   [llave de despliegue]: /developers/overview/managing-deploy-keys#deploy-keys
+  [llave de implementación]: /developers/overview/managing-deploy-keys#deploy-keys
   [deploy key]: /developers/overview/managing-deploy-keys#deploy-keys
 
   [2fa]: /authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication
diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
index 7d8821d229..be7eed45d7 100644
--- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: Exporting audit log activity for your enterprise
-intro: You can export audit and Git events data to a file for offline analysis.
-shortTitle: Export audit logs
+title: Exportar la actividad de la bitácora de auditoría para tu empresa
+intro: Puedes exportar los datos de eventos de Git y de auditoría a un archivo para su análisis sin conexión.
+shortTitle: Exportar bitácoras de auditoría
 permissions: Enterprise owners can export the audit log.
 miniTocMaxHeadingLevel: 3
 versions:
@@ -13,40 +13,40 @@ topics:
   - Logging
 ---
 
-## About exports of audit log and Git events data
+## Acerca de las exportaciones de los datos de eventos de Git y de bitácoras de auditoría
 
-You can export the audit log by downloading a JSON or CSV file from your enterprise on {% data variables.product.product_name %}. When you export audit log events, you can query by one or more of these supported qualifiers to filter for specific log events to export. For more information about search qualifiers, see "[Search based on the action performed](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise#search-based-on-the-action-performed)."
+Puedes exportar la bitácora de auditoría si descargas un archivo JSON o CSV de tu empresa en {% data variables.product.product_name %}. Cuando exportas eventos de bitácoras de auditoría, puedes hacer consultas por uno o más de estos calificadores compatibles para filtrar por eventos de bitácora específicos para exportar. Para obtener más información sobre los calificadores de búsqueda, consulta la sección "[Búsqueda con base en la acción realizada](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise#search-based-on-the-action-performed)".
 
-You can export Git events data by downloading a JSON file from your enterprise audit log. Unlike audit log data, you cannot query for specific Git events to filter and export in the audit log user interface.
+Puedes exportar datos de eventos de Git si descargas un archivo JSON desde la bitácora de auditoría de tu empresa. A diferencia de los datos de bitácora de auditoría, no puedes consultar los eventos específicos de Git para filtrarlos y exportarlos en la interfaz de usuario de la bitácora de auditoría.
 
 {% data reusables.audit_log.git-events-export-limited %}
 
 {% data reusables.audit_log.exported-log-keys-and-values %}
 
-As an alternative to exporting log events, you can use the API to retrieve audit log events, or set up {% data variables.product.product_name %} to stream audit data as events are logged. Para obtener más información, consulta las secciones "[Utilizar la API de bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)" y "[Transmitir la bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)".
+Como alternativa para exportar los eventos de bitácora, puedes utilizar la API para recuperar los eventos de bitácora de auditoría o configurar a {% data variables.product.product_name %} para transmitir datos de auditoría conforme se registren los eventos. Para obtener más información, consulta las secciones "[Utilizar la API de bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)" y "[Transmitir la bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)".
 
-## Exporting audit log data
+## Exportar datos de bitácora de auditoría
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.audit-log-tab %}
-1. Optionally, to only export filtered results, search by one or more supported qualifiers or log filters.
-2. Select the {% octicon "download" aria-label="The Download icon" %} **Export** dropdown menu, and choose the file format (JSON or CSV) to export log events in.
+1. Opcionalmente, para solo exportar los resultados filtrados, busca por uno o mas de los calificadores o filtros de bitácora compatibles.
+2. Selecciona {% octicon "download" aria-label="The Download icon" %} el menú desplegable de **Exportar** y elige el formato de archivo (JSON o CSV) para exportar eventos de bitácora.
 
     ![Botón de exportar](/assets/images/help/organizations/org-audit-log-export.png)
 
-## Exporting Git events data
+## Exportar los datos de eventos de Git
 
-You can also export Git events data by date range.
+También puedes exportar datos de eventos de Git por rango de fechas.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.audit-log-tab %}
-1. Select the {% octicon "download" aria-label="The Download icon" %} **Export Git Events** dropdown menu and choose a date range to export log events for.
+1. Selecciona el {% octicon "download" aria-label="The Download icon" %} menú desplegable de **Exportar eventos de Git** y elige un rango de fechas de las cuales quieras exportar las bitácoras.
 
-    ![Export Git events button](/assets/images/help/organizations/org-audit-log-export-git-events.png)
-1. Click {% octicon "file-zip" aria-label="The File-zip icon" %} **Download Results** to download the file.
-1. The data is exported as a compressed JSON file. To extract the JSON data, uncompress the file using an archive utility client or command. Por ejemplo:
+    ![Botón de exportar eventos de Git](/assets/images/help/organizations/org-audit-log-export-git-events.png)
+1. Haz clic en {% octicon "file-zip" aria-label="The File-zip icon" %} **Descargar resultados** para descargar el archivo.
+1. Se exportarán los datos como un archivo JSON comprimido. Para extraer los datos de JSON, descomprime el archivo utilizando un comando o cliente de utilidad de archivo. Por ejemplo:
 
     ```
     gunzip export-avocado-corp-1642896556.json.gz
diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
index 7272c8b766..38ddcf03e8 100644
--- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
+++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
@@ -1,7 +1,7 @@
 ---
-title: Reviewing audit logs for your enterprise
-intro: You can view user and system activity in the audit logs for your enterprise.
-shortTitle: Review audit logs
+title: Revisa las bitácoras de auditoría para tu empresa
+intro: Puedes ver la actividad de sistema y de usuario en las bitácoras de auditoría para tu empresa.
+shortTitle: Revisar las bitácoras de auditoría
 versions:
   ghec: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
index 22c135cb9c..1a170702ca 100644
--- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
@@ -41,47 +41,47 @@ Nota que no puedes buscar entradas utilizando texto. Sin embargo, puedes constru
 
 ## Filtros de consulta de búsqueda
 
-|                                Filtrar | Descripción                                                                                                                                                                                                                           |
-| --------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|                    `Actividad de ayer` | Todas las acciones que se crearon en el día anterior.                                                                                                                                                                                 |
-| `Adminsitración de cuenta empresarial` | All actions in the `business` category.                                                                                                                                                                                               |
-|         `Membresía de la organización` | All actions for when a new user was invited to join an organization.                                                                                                                                                                  |
-|                      `Team management` | All actions related to team management.<br/>- When a user account or repository was added or removed from a team<br/>- When a team maintainer was promoted or demoted<br/>-  When a team was deleted                |
-|                `Repository management` | All actions for repository management.<br/>- When a repository was created or deleted<br/>- When the repository visibility was changed<br/>- When a team was added or removed from a repository{% ifversion ghec %}
-|                      `Billing updates` | All actions concerning how your enterprise pays for {% data variables.product.prodname_dotcom %} and for when your billing email address was changed.{% endif %}
-|                        `Hook activity` | All actions for webhooks and pre-receive hooks.                                                                                                                                                                                       |
-|                  `Security management` | All actions concerning SSH keys, deploy keys, security keys, 2FA, and SAML single sign-on credential authorization, and vulnerability alerts for repositories.                                                                        |
+|                                Filtrar | Descripción                                                                                                                                                                                                                                                          |
+| --------------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|                    `Actividad de ayer` | Todas las acciones que se crearon en el día anterior.                                                                                                                                                                                                                |
+| `Adminsitración de cuenta empresarial` | Todas las acciones en la categoría `business`.                                                                                                                                                                                                                       |
+|         `Membresía de la organización` | Todas las acciones para cuando se haya invitado a un usuario nuevo a una organización.                                                                                                                                                                               |
+|             `Administración de equipo` | Todas las acciones relacionadas con la administración de equipos.<br/>- Cuando una cuenta de usuario o repositorio se agrega o elimina de un equipo<br/>- Cuando se promueve o degrada a un mantenedor de equipo<br/>- Cuando se borra a un equipo |
+|       `Administración de repositorios` | Todas las acciones para la administración de repositorios.<br/>- Cuando se crea o borra un repositorio<br/>- Cuando se cambia la visibilidad del repositorio<br/>- Cuando se agrega o elimina a un equipo del repositorio{% ifversion ghec %}
+|       `Actualizaciones de facturación` | Todas las acciones con respecto a cómo tu empresa paga por {% data variables.product.prodname_dotcom %} y para cuando cambia tu dirección de correo electrónico para facturación.{% endif %}
+|                 `Actividad de ganchos` | Todas las acciones para los webhooks y ganchos de prerecepción.                                                                                                                                                                                                      |
+|          `Administración de seguridad` | Todas las acciones que tienen que ver con llaves SSH, llaves de despliegue, llaves de seguridad, 2FA, y autorización de credenciales para inicio de sesión único de SAML y alertas de vulnerabilidades para repositorios.                                            |
 
 ## Buscar sintaxis de consultas
 
-You can compose a search query from one or more `key:value` pairs, separated by AND/OR logical operators. Por ejemplo, para ver todas las acciones que afectaron el repositorio `octocat/Spoon-Knife` desde el inicio de 2017:
+Puedes componer una consulta de búsqueda desde uno o más pares `key:value`, separados por operadores lógicos AND/OR. Por ejemplo, para ver todas las acciones que afectaron el repositorio `octocat/Spoon-Knife` desde el inicio de 2017:
 
   `repo:"octocat/Spoon-Knife" AND created:>=2017-01-01`
 
-The `key:value` pairs that can be used in a search query are:
+Los pares `key:value` que pueden utilizarse en una consulta de búsqueda son:
 
-|           Clave | Valor                                                                                                                                               |
-| ---------------:| --------------------------------------------------------------------------------------------------------------------------------------------------- |
-|      `actor_id` | ID de la cuenta de usuario que inició la acción                                                                                                     |
-| `actor (actor)` | Nombre de la cuenta de usuario que inició la acción                                                                                                 |
-|  `oauth_app_id` | ID de la aplicación OAuth asociada con la acción                                                                                                    |
-|        `Acción` | Nombre de la acción auditada                                                                                                                        |
-|       `user_id` | ID del usuario afectado por la acción                                                                                                               |
-|       `usuario` | Nombre del usuario afectado por la acción                                                                                                           |
-|       `repo_id` | ID del repositorio afectado por la acción (si corresponde)                                                                                          |
-|          `repo` | Nombre del repositorio afectado por la acción (si corresponde)                                                                                      |
-|      `actor_ip` | Dirección IP desde donde se inició la acción                                                                                                        |
-|       `created` | Time at which the action occurred{% ifversion ghes %}. If querying the audit log from the site admin dashboard, use `created_at` instead{% endif %}
-|          `from` | Vista desde donde se inició la acción                                                                                                               |
-|          `note` | Información variada de evento específico (en texto simple o en formato JSON)                                                                        |
-|           `org` | Nombre de la organización afectada por la acción (si corresponde)                                                                                   |
-|        `org_id` | ID de la organización afectada por la acción (si corresponde)                                                                                       |
-|      `business` | Name of the enterprise affected by the action (if applicable)                                                                                       |
-|   `business_id` | ID of the enterprise affected by the action (if applicable)                                                                                         |
+|           Clave | Valor                                                                                                                                                                                           |
+| ---------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|      `actor_id` | ID de la cuenta de usuario que inició la acción                                                                                                                                                 |
+| `actor (actor)` | Nombre de la cuenta de usuario que inició la acción                                                                                                                                             |
+|  `oauth_app_id` | ID de la aplicación OAuth asociada con la acción                                                                                                                                                |
+|        `Acción` | Nombre de la acción auditada                                                                                                                                                                    |
+|       `user_id` | ID del usuario afectado por la acción                                                                                                                                                           |
+|       `usuario` | Nombre del usuario afectado por la acción                                                                                                                                                       |
+|       `repo_id` | ID del repositorio afectado por la acción (si corresponde)                                                                                                                                      |
+|          `repo` | Nombre del repositorio afectado por la acción (si corresponde)                                                                                                                                  |
+|      `actor_ip` | Dirección IP desde donde se inició la acción                                                                                                                                                    |
+|       `created` | Hora en la que ocurrió la acción{% ifversion ghes %}. Si se está consultando la bitácora de auditoría desde el tablero administrativo del proyecto, utiliza `created_at` en su lugar{% endif %}
+|          `from` | Vista desde donde se inició la acción                                                                                                                                                           |
+|          `note` | Información variada de evento específico (en texto simple o en formato JSON)                                                                                                                    |
+|           `org` | Nombre de la organización afectada por la acción (si corresponde)                                                                                                                               |
+|        `org_id` | ID de la organización afectada por la acción (si corresponde)                                                                                                                                   |
+|      `business` | Nombre de la empresa afectada por la acción (si aplica)                                                                                                                                         |
+|   `business_id` | ID de la empresa afectada por la acción (si aplica)                                                                                                                                             |
 
-To see actions grouped by category, you can also use the action qualifier as a `key:value` pair. For more information, see "[Search based on the action performed](#search-based-on-the-action-performed)."
+Para ver las acciones agrupadas por categoría, también puedes utilizar el calificador de acción como un par `key:value`. Para obtener más información, consulta la sección "[Búsqueda basada en la acción realizada](#search-based-on-the-action-performed)".
 
-For a full list of actions in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
+Para ver una lista completa de acciones en la bitácora de auditoría de tu empresa, consulta la sección "[Acciones de la bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)".
 
 ## Buscar el registro de auditoría
 
@@ -103,7 +103,7 @@ Cada categoría tiene un conjunto de acciones asociadas que puedes filtrar. Por
   * `action:team.create` encuentra todos los eventos donde se creó un equipo.
   * `-action:hook.events_changed` excluye todos los eventos en que se modificaron los eventos sobre un webhook.
 
-Actions that can be found in your enterprise audit log are grouped within the following categories:
+Las acciones que se pueden encontrar en la bitácora de auditoría de tu empresa se agrupan dentro de las siguientes categorías:
 
 {% data reusables.audit_log.audit-log-action-categories %}
 ### Búsqueda basada en el momento de la acción
@@ -123,7 +123,7 @@ Por ejemplo:
 
 ### Búsqueda basada en la ubicación
 
-Al utilizar el calificador `country`, puedes filtrar los eventos en la bitácora de auditoría con base en el país en donde se originaron. You can use a country's two-letter short code or full name. Countries with spaces in their name will need to be wrapped in quotation marks. Por ejemplo:
+Al utilizar el calificador `country`, puedes filtrar los eventos en la bitácora de auditoría con base en el país en donde se originaron. Puedes utilizar el código corto de dos letras de un país o el nombre completo. Los países con espacios en sus nombres tendrán que encerrarse entre comillas. Por ejemplo:
 
   * `country:de` encuentra todos los eventos ocurridos en Alemania.
   * `country:Mexico` encuentra todos los eventos ocurridos en México.
diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
index 4a8e5882a1..1f1e11af76 100644
--- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
@@ -3,7 +3,7 @@ title: Transmitir la bitácora de auditoría para tu empresa
 intro: 'Puedes trasmitir datos de eventos de Git y de auditorías desde {% data variables.product.prodname_dotcom %} hacia un sistema externo de administración de datos.'
 miniTocMaxHeadingLevel: 3
 versions:
-  ghec: '*'
+  feature: audit-log-streaming
 type: tutorial
 topics:
   - Auditing
@@ -17,6 +17,14 @@ redirect_from:
 permissions: Enterprise owners can configure audit log streaming.
 ---
 
+{% ifversion ghes %}
+{% note %}
+
+**Note:** Audit log streaming is currently in beta for {% data variables.product.product_name %} and is subject to change.
+
+{% endnote %}
+{% endif %}
+
 ## Acerca de la transmisión de bitácoras de auditoría
 
 Para ayudarte a proteger tu propiedad intelectual y mantener el cumplimiento en tu organización, puedes utilizar la transmisión para mantener copias de tus datos de bitácoras de auditoría y monitorear:
@@ -24,11 +32,11 @@ Para ayudarte a proteger tu propiedad intelectual y mantener el cumplimiento en
 
 Los beneficios de transmitir datos de auditoría incluyen:
 
-* **Exploración de datos**. Puedes examinar los eventos transmitidos utilizando tu herramienta preferida para consultar cantidades grandes de datos. La transmisión contiene tanto los eventos de auditoría como los de Git a lo largo de toda la cuenta empresarial.
-* **Continuidad de datos**. Puedes pausar la transmisión por hasta siete días sin perder datos de auditoría.
+* **Exploración de datos**. Puedes examinar los eventos transmitidos utilizando tu herramienta preferida para consultar cantidades grandes de datos. The stream contains both audit events and Git events across the entire enterprise account.{% ifversion pause-audit-log-stream %}
+* **Continuidad de datos**. You can pause the stream for up to seven days without losing any audit data.{% endif %}
 * **Retención de datos**. Puedes mantener tus bitácoras de auditoría y datos de eventos de Git exportados siempre que lo necesites.
 
-Los propietrios de empresas pueden configurar, pausar o borrar una transmisión en cualquier momento. La transmisión exporta los datos de auditoría de todas las organizaciones en tu empresa.
+Enterprise owners can set up{% ifversion pause-audit-log-stream %}, pause,{% endif %} or delete a stream at any time. The stream exports the audit and Git events data for all of the organizations in your enterprise.
 
 ## Configurar la transmisión de bitácoras de auditoría
 
@@ -272,6 +280,7 @@ Para transmitir bitácoras de auditoría a la terminal del Recolector de Eventos
 1. Haz clic en **Verificar terminal** para verificar que {% data variables.product.prodname_dotcom %} puede conectarse y escribir en la terminal de Splunk. ![Verificar la terminal](/assets/images/help/enterprises/audit-stream-check-splunk.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
+{% ifversion pause-audit-log-stream %}
 ## Pausar la transmisión de bitácoras de auditoría
 
 El pausar la transmisión te permite realizar el mantenimiento de la aplicación receptora sin perder datos de auditoría. Las bitácoras de auditoría se almacenan por hasta siete días en {% data variables.product.product_location %} y luego se exportan cuando dejas de pausar la transmisión.
@@ -284,6 +293,7 @@ El pausar la transmisión te permite realizar el mantenimiento de la aplicación
 1. Se mostrará un mensaje de confirmación. Haz clic en **Pausar transmisión** para confirmar.
 
 Cuando la aplicación esté lista para recibir bitácoras de auditoría nuevamente, haz clic en **Reanudar transmisión** para reiniciar la transmisión de bitácoras de auditoría.
+{% endif %}
 
 ## Borrar la transmisión de bitácoras de auditoría
 
diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
index 9f3210ec45..84e1baaabf 100644
--- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: Using the audit log API for your enterprise
-intro: 'You can programmatically retrieve enterprise events with the{% ifversion ghec or ghes > 3.2 %} REST or{% endif %} GraphQL API.'
-shortTitle: Audit log API
+title: Utilizar la API de bitácora de auditoría para tu empresa
+intro: 'Puedes recuperar los eventos de empresa con programación utilizando la API de {% ifversion ghec or ghes > 3.2 %} REST o de{% endif %} GraphQL.'
+shortTitle: API de bitácora de auditoría
 permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can use the audit log API.'
 miniTocMaxHeadingLevel: 3
 versions:
@@ -20,22 +20,22 @@ topics:
 
 Puedes interactuar con la bitácora de audotaría si utilizas la API de GraphQL{% ifversion ghec or ghes > 3.2 or ghae-issue-6648 %} o la API de REST{% endif %}.
 
-Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time).
+Las marcas de tiempo y campos de fecha en la respuesta de la API se miden en [milisegundos de época UTC](http://en.wikipedia.org/wiki/Unix_time).
 
-## Querying the audit log GraphQL API
+## Consultar la API de bitácora de auditoría de GraphQL
 
-To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log GraphQL API to keep copies of your audit log data and monitor:
+Para garantizar que tu propiedad intelectual está segura y que mantienes el cumplimiento para tu empresa, puedes utilizar la API de GraphQL para bitácoras de auditoría para mantener copias de tus datos de bitácoras de auditoría y monitorear:
 {% data reusables.audit_log.audit-log-api-info %}
 
-Note that you can't retrieve Git events using the {% ifversion not ghec %}audit log API.{% else %}GraphQL API. Para recuperar eventos de Git, utiliza mejor la API de REST. Para obtener más información, consulta las acciones de la categoría `git` en la sección "[Acciones de bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)" y también las terminales de bitácoras de auditoría de [Administración de empresas](/rest/reference/enterprise-admin#audit-log)" y "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization) en la documentación de la API de REST".{% endif %}
+Toma en cuenta que no puedes recuperar eventos de Git utilizando la {% ifversion not ghec %}API de bitácora de auditoría.{% else %}API de GraphQL. Para recuperar eventos de Git, utiliza mejor la API de REST. Para obtener más información, consulta las acciones de la categoría `git` en la sección "[Acciones de bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)" y también las terminales de bitácoras de auditoría de [Administración de empresas](/rest/reference/enterprise-admin#audit-log)" y "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization) en la documentación de la API de REST".{% endif %}
 
 La respuesta de GraphQL puede incluir datos de hasta 90 a 120 días.
 
-### Example 1: Members added to or removed from organizations in an enterprise
+### Ejemplo 1: Los miembros que se agregaron o eliminaron de las organizaciones en una empresa
 
-The query below fetches the audit logs for the `avocado-corp` enterprise and returns the first 10 organizations in the enterprise, where the only actions performed were adding or removing a member from an organization. The first 20 audit log entries for each organization are returned.
+La siguiente consulta recupera las bitácoras de auditoría para la empresa `avocado-corp` y devuelve a las primeras 10 organizaciones en ella, en donde las únicas acciones que se llevaron a cabo fue la adición o eliminación de un miembro de una organización. Se devuelven las primeras 20 entradas de bitácora de auditoría para cada organización.
 
-This query uses the [auditlog](/graphql/reference/objects) field from the Organization object, and the [OrgAddMemberAuditEntry](/graphql/reference/objects#orgaddmemberauditentry) and [OrgRemoveMemberAuditEntry](/graphql/reference/objects#orgremovememberauditentry) objects. The  {% data variables.product.prodname_dotcom %} account querying the enterprise audit log must be an organization owner for each organization within the enterprise.
+Esta consulta utiliza el campo [auditlog](/graphql/reference/objects) del objeto de organización y los objetos [OrgAddMemberAuditEntry](/graphql/reference/objects#orgaddmemberauditentry) y [OrgRemoveMemberAuditEntry](/graphql/reference/objects#orgremovememberauditentry). La cuenta de {% data variables.product.prodname_dotcom %} que está consultando la bitácora de auditoría empresarial debe ser un propietario de organización para cada organización dentro de la empresa.
 
 ```shell
 {
@@ -69,10 +69,10 @@ This query uses the [auditlog](/graphql/reference/objects) field from the Organi
 }
 ```
 
-The GraphQL API will return at most 100 nodes per query. To retrieve additional results, you'll need to implement pagination. For more information, see "[Resource limitations](/graphql/overview/resource-limitations#node-limit)" in the GraphQL API documentation and [Pagination](https://graphql.org/learn/pagination/) in the official GraphQL documentation.
-### Example 2: Events in an organization, for a specific date and actor
+La API de GraphQL devolverá por mucho 100 nodos por consulta. Para recuperar los resultados adicionales, necesitarás implementar la paginación. Para obtener más información, consulta la sección "[Limitaciones de recursos](/graphql/overview/resource-limitations#node-limit)" en la documentación de la API de GraphQL y [Paginación](https://graphql.org/learn/pagination/) en la documentación oficial de GraphQL.
+### Ejemplo 2: Eventos en una organización para una fecha y actor específicos
 
-You can specify multiple search phrases, such as `created` and `actor`, by separating them in your query string with a space.
+Puedes especificar frases de búsqueda múltiples, tales como `created` y `actor`, si las separas en tu secuencia de consulta con un espacio.
 
 The query below fetches all the audit logs for the `avocado-corp` enterprise that relate to the `octo-org` organization, where the actions were performed by the `octocat` user on or after the 1 Jan, 2022. The first 20 audit log entries are returned, with the newest log entry appearing first.
 
diff --git a/translations/es-ES/content/admin/packages/index.md b/translations/es-ES/content/admin/packages/index.md
index ead93cdf09..b1d51bdae9 100644
--- a/translations/es-ES/content/admin/packages/index.md
+++ b/translations/es-ES/content/admin/packages/index.md
@@ -14,6 +14,7 @@ children:
   - /enabling-github-packages-with-minio
   - /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
   - /configuring-package-ecosystem-support-for-your-enterprise
+  - /migrating-your-enterprise-to-the-container-registry-from-the-docker-registry
 shortTitle: Admnistrar los GitHub Packages
 ---
 
diff --git a/translations/es-ES/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/translations/es-ES/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..d65d3dc020
--- /dev/null
+++ b/translations/es-ES/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,85 @@
+---
+title: Migrating your enterprise to the Container registry from the Docker registry
+intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.product.product_location %} to the {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.'
+versions:
+  feature: docker-ghcr-enterprise-migration
+shortTitle: Migrarse al registro de contenedores
+topics:
+  - Containers
+  - Docker
+  - Migration
+---
+
+{% data reusables.package_registry.container-registry-ghes-beta %}
+
+## Acerca de {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+
+For more information about configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+
+## About migration from the Docker registry
+
+{% data reusables.package_registry.container-registry-replaces-docker-registry %} If the Docker registry on {% data variables.product.product_location %} contains images, you must manually migrate the images to the {% data variables.product.prodname_container_registry %}.
+
+{% ifversion ghes %}
+
+{% note %}
+
+**Nota**: {% data reusables.package_registry.container-registry-ghes-migration-availability %}
+
+{% endnote %}
+
+{% endif %}
+
+{% data reusables.package_registry.container-registry-migration-namespaces %} For more information about the impact of migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the  {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry#about-migration-from-the-docker-registry)."
+
+## Migrating organizations to the {% data variables.product.prodname_container_registry %}
+
+You can start a migration of all your organizations' Docker images to the {% data variables.product.prodname_container_registry %}. The duration of the migration operation depends on the total number of images to migrate, and the overall load on {% ifversion ghes %}your instance{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. After a successful migration, {% data variables.product.product_name %} will display a summary, and all future uploads of Docker images will use the {% data variables.product.prodname_container_registry %}.
+
+If {% ifversion ghes %}a site administrator{% elsif ghae %}an enterprise owner{% endif %} has configured email notifications for {% data variables.product.product_location %}, you will receive an email after the migration is complete. Para obtener más información, consulta la sección "[Configurar las notificaciones de correo electrónico](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)".
+
+{% note %}
+
+**{% ifversion ghes %}Notas{% elsif ghae %}Nota{% endif %}**:
+
+{%- ifversion ghes %}
+- During the migration, the CPU and memory usage for your instance will increase. To ensure the performance of the instance for your users, {% data variables.product.company_short %} recommends that you begin a migration during a period of reduced activity.
+{%- endif %}
+{% ifversion ghes %}- {% endif %}During the migration, do not modify settings for your enterprise{% ifversion ghes %} or run `ghe-config-apply` from an administrative SSH session{% endif %}. {% ifversion ghes %}These actions will trigger a configuration run, which can restart services and {% elsif ghae %}Modifying these settings {% endif %} may interrupt the migration.
+{%- ifversion ghes %}
+- After the migration, storage pressure on your instance will increase due to the duplication of image files in the Docker registry and the {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.product_name %} will remove the duplicated files when all migrations are complete.
+
+For more information about monitoring the performance and storage of {% data variables.product.product_location %}, see "[Accessing the monitor dashboard](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)."
+{% endif %}
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+1. En la barra lateral izquierda, da clic en **Paquetes**.
+1. To the right of the number of packages to migrate, click **Start migration**. During the migration, {% data variables.product.product_name %} will display progress on this page.
+
+After the migration completes, the page will display the results. If a migration fails, the page will show the organizations that own the package that caused the failure.
+
+## Re-running a failed organization migration
+
+Prior to migration, if a user has created a package in the {% data variables.product.prodname_container_registry %} that has an identical name to an existing package in the Docker registry, the migration will fail.
+
+1. Delete the affected container in the {% data variables.product.prodname_container_registry %}. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package#deleting-a-version-of-an-organization-scoped-package-on-github)".
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.packages-tab %}
+1. To the right of the number of packages to migrate, click **Re-run migration**. During the migration, {% data variables.product.product_name %} will display progress on this page.
+1. If the migration fails again, start from step 1 and re-run the migration.
+
+{% ifversion ghes %}
+
+## Monitoring traffic to the registries
+
+You can use visualize traffic to the Docker registry and {% data variables.product.prodname_container_registry %} from {% data variables.product.product_location %}'s monitor dashboard. The "GitHub Container Package Registry" graph can help you confirm that you've successfully migrated all images to the {% data variables.product.prodname_container_registry %}. In the graph, "v1" represents traffic to the Docker registry, and "v2" represents traffic to the {% data variables.product.prodname_container_registry %}. Para obtener más información, consulta la sección "[Acceder al tablero de monitoreo](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)".
+
+{% endif %}
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 3cdc0ebbb5..f5a69d2482 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -203,6 +203,28 @@ Cuando impones límites de carga a los repositorios, la configuración predeterm
 4. Dentro de "Repository upload limit (Límite de subida del repositorio)", utiliza el menú desplegable y haz clic en un tamaño máximo de objeto. ![Menú desplegable con opciones de tamaño máximo de objeto](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
 5. Opcionalmente, para requerir un límite de carga máximo para todos los repositorios en tu empresa, selecciona **Requerir en todos los repositorios** ![Opción para imponer tamaño máximo de objetos en todos los repositorios](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
 
+{% ifversion profile-name-enterprise-setting %}
+
+## Enforcing a policy for the display of member names in your repositories
+
+Across all organizations owned by your enterprise, you can allow members to see a comment author's profile name, in addition to their username, in issues and pull requests for public and internal repositories.
+
+![Nombre del perfil del autor del comentario que se muestra en un comentario](/assets/images/help/issues/commenter-full-name.png)
+
+{% note %}
+
+**Note:** When this policy is enforced for all repositories in the enterprise, it overrides the organization setting for private repositories. Para obtener más información, consulta "[Administrar cómo se ven los nombres de los miembros en tu organización](/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization)".
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.options-tab %}
+4. Under "Allow members to see the comment author's profile name in public and internal repositories", select the dropdown menu and click a policy. ![Screenshot of Options page with policy drop down emphasized](/assets/images/enterprise/site-admin-settings/comment-authors-profile-name-drop-down.png)
+5. Optionally, to enforce the display of profile names for all repositories in your enterprise, select **Enforce for all repositories on the instance**. ![Screenshot of "Enforce for all repositories" option emphasized](/assets/images/enterprise/site-admin-settings/enforce-for-all-repositories-option.png)
+
+{% endif %}
+
 ## Configurar el editor de fusión de conflictos para solicitudes de extracción entre repositorios
 
 Solicitarles a los usuarios que resuelvan los conflictos de fusión en forma local desde sus computadoras puede evitar que las personas escriban inadvertidamente un repositorio ascendente desde una bifurcación.
@@ -265,10 +287,22 @@ Puedes sustituir los parámetros predeterminados heredados al configurar los par
 
 {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
 
-{% ifversion ghes %}Si [habilitaste el modo privado](/enterprise/admin/configuration/enabling-private-mode) en tu empresa, puedes {% else %}Puedes {% endif %}permitir a los administradores de repositorio habilitar el acceso de lectura de Git a los repositorios públicos.
+If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) for {% data variables.product.product_location %}, you can allow repository administrators to enable anonymous Git read access to public repositories.
 
 Habilitar el acceso anónimo de lectura de Git permite a los usuarios saltar la autenticación para las herramientas personalizadas en tu empresa. Cuando tú o un administrador de repositorio activan esta configuración de acceso a un repositorio, las operaciones Git no autenticadas (y cualquiera con acceso de red a {% data variables.product.product_name %}) tendrán acceso de lectura al repositorio sin autenticación.
 
+Anonymous Git read access is disabled by default.{% ifversion ghes = 3.4 or ghes = 3.5 or ghes = 3.6 or ghes = 3.7 %} When you upgrade to {% data variables.product.product_name %} 3.6 or later, anonymous Git read access is automatically disabled at the application level, and `git://` connections on port 9418 will return the following error.
+
+```
+The unauthenticated git protocol on port 9418 is no longer supported.
+```
+
+If you wish to support the unathenticated Git protocol in your environment, you must manually re-enable the feature. {% data variables.product.company_short %} recommends using SSH instead of the Git protocol. Para obtener más información, consulta [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server).
+
+{% endif %}
+
+
+
 De ser necesario, puedes prevenir que los administradores de repositorio cambien la configuración de acceso anónimo de Git para los repositorios de tu empresa si bloqueas la configuración de acceso de los mismos. Una vez que bloqueas los parámetros de acceso de lectura Git de un repositorio, solo un administrador del sitio puede modificar los parámetros.
 
 {% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
index 2be428403f..b9e4605730 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -25,6 +25,10 @@ You can see all current enterprise members and enterprise administrators{% ifver
 
 You can view all the current enterprise owners{% ifversion ghec %} and billing managers{% endif %} for your enterprise.{% ifversion enterprise-membership-view-improvements %} You can see useful information about each administrator{% ifversion ghec %} and filter the list by role{% endif %}.{% endif %} You can find a specific person by searching for their username or display name.
 
+{% ifversion ghes > 3.5 %}
+Enterprise owners whose accounts are suspended are included in the list of enterprise administrators, and are identified as suspended. You should consider demoting any suspended owners you see. For more information, see "[Promoting or demoting a site administrator](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator#demoting-a-site-administrator-from-the-enterprise-settings)."
+{% endif %}
+
 {% ifversion not ghae %}
 You can also remove an administrator. For more information. see "[Inviting people to manage your enterprise](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise#removing-an-enterprise-administrator-from-your-enterprise-account)."
 {% endif %}
diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md
index 4b1fcf0011..fd1373c949 100644
--- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md
+++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md
@@ -14,7 +14,11 @@ topics:
   - SSH
 ---
 
-Cuando configures SSH, necesitarás generar una llave SSH nuevo y agregarla al agente ssh. Debes agregar la llave SSH a tu cuenta en {% data variables.product.product_name %} antes de utilizarla para autenticarte. Para obtener más información, consulta las secciones "[Generar una llave SSH nueva y agregarla al ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" y "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
+## Acerca de SSH
+
+{% data reusables.ssh.about-ssh %} For more information about SSH, see [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) on Wikipedia.
+
+When you set up SSH, you will need to generate a new private SSH key and add it to the SSH agent. You must also add the public SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. Para obtener más información, consulta las secciones "[Generar una llave SSH nueva y agregarla al ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" y "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
 
 Puedes asegurar tu llave SSH aún más si utilizas una llave de seguridad de hardware, la cual requiere que esta última se conecte físicamente a tu computadora cuando se utilice el par de llaves para autenticarte con SSH. También puedes asegurar tu llave SSH si la agregas al ssh-agent y utiliza una contraseña. Para obtener más información, consulta la sección "[Trabajar con frases de acceso con llave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)".
 
diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
index 826dfd019d..859c855779 100644
--- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
@@ -14,9 +14,21 @@ topics:
   - SSH
 shortTitle: Add a new SSH key
 ---
-Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you should have:
-* [Checked for existing SSH keys](/articles/checking-for-existing-ssh-keys)
-* [Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)
+
+## About addition of SSH keys to your account
+
+{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+
+After you generate an SSH key pair, you must add the public key to {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable SSH access for your account.
+
+## Prerequisites
+
+Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, complete the following steps.
+
+1. Check for existing SSH keys. For more information, see "[Checking for existing SSH keys](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)."
+1. Generate a new SSH key and add it to your machine's SSH agent. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
+
+## Adding a new SSH key to your account
 
 After adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you can reconfigure any local repositories to use SSH. For more information, see "[Switching remote URLs from HTTPS to SSH](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)."
 
diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
index 759d070755..9c7bb7d3cb 100644
--- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
+++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
@@ -15,6 +15,16 @@ topics:
 shortTitle: Verificar la llave SSH existente
 ---
 
+## About SSH keys
+
+You can use SSH to perform Git operations in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. Para obtener más información, consulta la sección "[Acerca de SSH](/authentication/connecting-to-github-with-ssh/about-ssh)".
+
+If you have an existing SSH key, you can use the key to authenticate Git operations over SSH.
+
+## Comprobar tus claves SSH existentes
+
+Before you generate a new SSH key, you should check your local machine for existing keys.
+
 {% data reusables.ssh.key-type-support %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index 7e1a11e52b..6f75638fa1 100644
--- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -16,72 +16,79 @@ topics:
   - SSH
 shortTitle: Generate new SSH key
 ---
-## About SSH key generation
+
+## About SSH key passphrases
+
+{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+
+When you generate an SSH key, you can add a passphrase to further secure the key. Whenever you use the key, you must enter the passphrase. If your key has a passphrase and you don't want to enter the passphrase every time you use the key, you can add your key to the SSH agent. The SSH agent manages your SSH keys and remembers your passphrase.
 
 If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)."
 
 If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2).
 
-If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.
-
 ## Generating a new SSH key
 
+You can generate a new SSH key on your local machine. After you generate the key, you can add the key to your account on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable authentication for Git operations over SSH.
+
+{% data reusables.ssh.key-type-support %}
+
 {% data reusables.command_line.open_the_multi_os_terminal %}
 2. Paste the text below, substituting in your {% data variables.product.product_name %} email address.
-    {% ifversion ghae %}
+   {%- ifversion ghae %}
     <!-- GitHub AE is FIPS 140-2 compliant. FIPS does not yet permit keys that use the ed25519 algorithm. -->
-  ```shell
-  $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>" 
-  ```
-    {% else %}
-  ```shell
-  $ ssh-keygen -t ed25519 -C "<em>your_email@example.com</em>"
-  ```
-  {% note %}
+   ```shell
+   $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>" 
+   ```
+   {%- else %}
+   ```shell
+   $ ssh-keygen -t ed25519 -C "<em>your_email@example.com</em>"
+   ```
+   {% note %}
+   
+   **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use:
+   ```shell
+    $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
+   ```
 
-  **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use:
-  ```shell
-   $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
-  ```
+   {% endnote %}
+   {%- endif %}
 
-  {% endnote %}
-  {% endif %}
-
-  This creates a new SSH key, using the provided email as a label.
-  ```shell
-  > Generating public/private <em>algorithm</em> key pair.
-  ```
+   This creates a new SSH key, using the provided email as a label.
+   ```shell
+   > Generating public/private <em>algorithm</em> key pair.
+   ```
 3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.
 
-  {% mac %}
+   {% mac %}
+   
+   ```shell
+   > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_<em>algorithm</em>): <em>[Press enter]</em>
+   ```
+   
+   {% endmac %}
+   
+   {% windows %}
+   
+   ```shell
+   > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_<em>algorithm</em>):<em>[Press enter]</em>
+   ```
 
-  ```shell
-  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_<em>algorithm</em>): <em>[Press enter]</em>
-  ```
-
-  {% endmac %}
-
-  {% windows %}
-
-  ```shell
-  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_<em>algorithm</em>):<em>[Press enter]</em>
-  ```
-
-  {% endwindows %}
-
-  {% linux %}
-
-  ```shell
-  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/<em>algorithm</em>): <em>[Press enter]</em>
-  ```
-
-  {% endlinux %}
+   {% endwindows %}
+   
+   {% linux %}
+   
+   ```shell
+   > Enter a file in which to save the key (/home/<em>you</em>/.ssh/<em>algorithm</em>): <em>[Press enter]</em>
+   ```
+   
+   {% endlinux %}
 
 4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
-  ```shell
-  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
-  > Enter same passphrase again: <em>[Type passphrase again]</em>
-  ```
+   ```shell
+   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+   > Enter same passphrase again: <em>[Type passphrase again]</em>
+   ```
 
 ## Adding your SSH key to the ssh-agent
 
@@ -93,66 +100,55 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 2. If you're using macOS Sierra 10.12.2 or later, you will need to modify your `~/.ssh/config` file to automatically load keys into the ssh-agent and store passphrases in your keychain.
 
-    * First, check to see if your `~/.ssh/config` file exists in the default location.
+   * First, check to see if your `~/.ssh/config` file exists in the default location.
 
-      ```shell
-      $ open ~/.ssh/config
-      > The file /Users/<em>you</em>/.ssh/config does not exist.
-      ```
+     ```shell
+     $ open ~/.ssh/config
+     > The file /Users/<em>you</em>/.ssh/config does not exist.
+     ```
 
-    * If the file doesn't exist, create the file.
+   * If the file doesn't exist, create the file.
 
-      ```shell
-      $ touch ~/.ssh/config
-      ```
+     ```shell
+     $ touch ~/.ssh/config
+     ```
 
-    * Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup. 
+   * Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup. 
 
-      ```
-      Host *
-        AddKeysToAgent yes
-        UseKeychain yes
-        IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}
-      ```
+     ```
+     Host *
+       AddKeysToAgent yes
+       UseKeychain yes
+       IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}
+     ```
 
      {% note %}
 
-     **Note:** If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
-  
-     {% endnote %}
+     **Notes:**
      
-      {% mac %}
-      {% note %}
-
-      **Note:** If you see an error like this
-
-      ```
-      /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain
-      ```
-
-      add an additional config line to your `Host *` section:
-
-      ```
-      Host *
-        IgnoreUnknown UseKeychain
-      ```
-
-      {% endnote %}
-      {% endmac %}
+     - If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
   
+     - If you see a `Bad configuration option: usekeychain` error, add an additional line to the configuration's' `Host *` section.
+
+       ```
+       Host *
+         IgnoreUnknown UseKeychain
+       ```
+     {% endnote %}
+
 3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
-  ```
-  {% note %}
+   ```
+   {% note %}
 
-  **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `-K` option. 
+   **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `-K` option. 
 
-  If you don't have Apple's standard version installed, you may receive an error. For more information on resolving this error, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)."
+   If you don't have Apple's standard version installed, you may receive an error. For more information on resolving this error, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)."
   
-  In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively. 
+   In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively. 
 
-  {% endnote %}
+   {% endnote %}
 
 4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
@@ -163,11 +159,11 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 {% data reusables.desktop.windows_git_bash %}
 
 1. Ensure the ssh-agent is running. You can use the "Auto-launching the ssh-agent" instructions in "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)", or start it manually:
-  ```shell
-  # start the ssh-agent in the background
-  $ eval "$(ssh-agent -s)"
-  > Agent pid 59566
-  ```
+   ```shell
+   # start the ssh-agent in the background
+   $ eval "$(ssh-agent -s)"
+   > Agent pid 59566
+   ```
 
 2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
@@ -194,59 +190,50 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
 1. Insert your hardware security key into your computer.
 {% data reusables.command_line.open_the_multi_os_terminal %}
 3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
-  ```shell
-  $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
-  ```
+   ```shell
+   $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
+   ```
   
-  {% ifversion not ghae %}
-  {% note %}
+   {%- ifversion not ghae %}
+   {% note %}
 
-  **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
-  ```shell
-   $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
-  ```
-
-  {% endnote %}
-  {% endif %}
+   **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
+   ```shell
+    $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
+   ```
+   
+   {% endnote %}
+   {%- endif %}
 4. When you are prompted, touch the button on your hardware security key.
 5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
 
-  {% mac %}
+   {% mac %}
+   
+   ```shell
+   > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
+   ```
 
-  ```shell
-  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
-  ```
+   {% endmac %}
+   
+   {% windows %}
+   
+   ```shell
+   > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):<em>[Press enter]</em>
+   ```
 
-  {% endmac %}
-
-  {% windows %}
-
-  ```shell
-  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):<em>[Press enter]</em>
-  ```
-
-  {% endwindows %}
-
-  {% linux %}
-
-  ```shell
-  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
-  ```
-
-  {% endlinux %}
+   {% endwindows %}
+   
+   {% linux %}
+   
+   ```shell
+   > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
+   ```
+   
+   {% endlinux %}
 
 6. When you are prompted to type a passphrase, press **Enter**.
-  ```shell
-  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
-  > Enter same passphrase again: <em>[Type passphrase again]</em>
-  ```
+   ```shell
+   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+   > Enter same passphrase again: <em>[Type passphrase again]</em>
+   ```
 7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
-
-
-## Further reading
-
-- "[About SSH](/articles/about-ssh)"
-- "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)"
-{%- ifversion fpt or ghec %}
-- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
-{%- endif %}
diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
index fb9da0359b..729d257272 100644
--- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
+++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
@@ -17,7 +17,9 @@ topics:
 shortTitle: Frases de acceso de llave SSH
 ---
 
-Con las claves SSH, si alguien obtiene acceso a tu computadora, también tiene acceso a cada sistema que usa esa clave. Para agregar una capa extra de seguridad, puedes incluir una contraseña a tu clave SSH. Puedes usar `ssh-agent` para guardar tu contraseña de forma segura y no tener que volver a ingresarla.
+## About passphrases for SSH keys
+
+With SSH keys, if someone gains access to your computer, the attacker can gain access to every system that uses that key. Para agregar una capa extra de seguridad, puedes incluir una contraseña a tu clave SSH. To avoid entering the passphrase every time you connect, you can securely save your passphrase in the SSH agent.
 
 ## Agregar o cambiar una contraseña
 
@@ -103,7 +105,3 @@ La primera vez que usas tu clave, se te pedirá que ingreses tu contraseña. Si
 De lo contrario, puedes almacenar tu contraseña en la keychain cuando agregues tu clave a ssh-agent. Para obtener más información, consulta "[Agregar tu clave SSH a ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)."
 
 {% endmac %}
-
-## Leer más
-
-- "[Acerca de SSH](/articles/about-ssh)"
diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
index 6f05b9af2a..adb05a61f9 100644
--- a/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
+++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
@@ -28,6 +28,8 @@ Commits and tags have the following verification statuses, depending on whether
 
 {% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
 
+Signing commits differs from signing off on a commit. For more information about signing off on commits, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
 ### Default statuses
 
 | Status         | Description |
diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
index 775260d616..5668159af2 100644
--- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
+++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
@@ -11,6 +11,8 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Security advisories
@@ -24,7 +26,7 @@ topics:
 
 ## Acerca de {% data variables.product.prodname_advisory_database %}
 
-The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities and malware, grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
+The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
 
 {% data reusables.repositories.tracks-vulnerabilities %}
 
@@ -32,20 +34,24 @@ The {% data variables.product.prodname_advisory_database %} contains a list of k
 
 {% data reusables.advisory-database.beta-malware-advisories %}
 
-Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects or for malicious open source software.
+Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}.
 
 {% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
 
+{% ifversion GH-advisory-db-supports-malware %}
+
 In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
 
+{% endif %}
+
 ### {% data variables.product.company_short %}-reviewed advisories
 
-{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities or malware that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
+{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
 
 Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
 
-- Composer (registry: https://packagist.org/)
-- Erlang (registry: https://hex.pm/)
+- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
+- Erlang (registry: https://hex.pm/){% endif %}
 - Go (registry: https://pkg.go.dev/)
 - Maven (registry: https://repo1.maven.org/maven2/org/)
 - npm (registry: https://www.npmjs.com/)
@@ -56,7 +62,7 @@ Generally, we name our supported ecosystems after the software programming langu
 
 If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
 
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability or malware for a package you depend on. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)".
+If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)".
 
 ### Unreviewed advisories
 
@@ -66,7 +72,7 @@ El {% data variables.product.prodname_dependabot %} no crea {% data variables.pr
 
 ## About information in security advisories
 
-Cada asesoría de seguridad contiene información sobre la vulnerabilidad o el malware, la cual puede incluir la descripción, gravedad, paquete afectado, ecosistema del paquete, versiones afectadas y versiones parchadas, impacto e información opcional, tal como referencias, soluciones alternas y créditos. Adicionalmente, las asesorías de la National Vulnerability Database contiene un enlace al registro de CVE, en donde puedes leer más sobre los detalles de la vulnerabilidad, su puntuación de CVSS y su nivel de severidad cualitativo. Para obtener más información, consulta la "[National Vulnerability Database](https://nvd.nist.gov/)" del Instituto Nacional de Estándares y Tecnología.
+Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. Adicionalmente, las asesorías de la National Vulnerability Database contiene un enlace al registro de CVE, en donde puedes leer más sobre los detalles de la vulnerabilidad, su puntuación de CVSS y su nivel de severidad cualitativo. Para obtener más información, consulta la "[National Vulnerability Database](https://nvd.nist.gov/)" del Instituto Nacional de Estándares y Tecnología.
 
 El nivel de gravedad es uno de cuatro niveles posibles que se definen en el [Sistema de clasificación de vulnerabilidades comunes (CVSS), Sección 5](https://www.first.org/cvss/specification-document)".
 - Bajo
@@ -87,12 +93,12 @@ La {% data variables.product.prodname_advisory_database %} utiliza los niveles d
    **Tip:** Puedes utilizar la barra lateral a la izquierda para explorar las asesorías que revisa {% data variables.product.company_short %} y aquellas sin revisar, por separado.
 
    {% endtip %}
-3. Da clic en cualquier asesoría para ver los detalles. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.
+3. Click an advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %}
 
 
 {% note %}
 
-También se puede acceder a la base de datos utilizando la API de GraphQL. By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`. Para obtener más información, consulta la sección "[evento de webhook de `security_advisory`](/webhooks/event-payloads/#security_advisory)".
+También se puede acceder a la base de datos utilizando la API de GraphQL. {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
 
 {% endnote %}
 
@@ -107,29 +113,16 @@ Puedes buscar la base de datos y utilizar los calificadores para definir más tu
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier             | Ejemplo                                                                                                                                                                             |
-| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `type:reviewed`       | [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities.     |
-| `type:malware`        | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware.                        |
-| `type:unreviewed`     | [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) mostrará las asesorías sin revisar.                                                                    |
-| `GHSA-ID`             | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) mostrará la asesoría con esta ID de {% data variables.product.prodname_advisory_database %}.   |
-| `CVE-ID`              | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) mostrará la asesoría con este número de ID de CVE.                                                         |
-| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) mostrará únicamente asesorías que afecten paquetes NPM.                                     |
-| `severity:LEVEL`      | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) mostrará únicamente asesorías con nivel de gravedad alto.                                   |
-| `affects:LIBRARY`     | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) mostrará únicamente asesorías que afecten la biblioteca lodash.                           |
-| `cwe:ID`              | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) mostrará únicamente las asesorías con este número de CWE.                                                              |
-| `credit:USERNAME`     | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) mostrará únicamente las asesorías que se atribuyen a la cuenta de usuario "octocat".                     |
-| `sort:created-asc`    | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) organizará los resultados para mostrar las asesorías más viejas primero.              |
-| `sort:created-desc`   | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) organizará los resultados para mostrar las asesorías más nuevas primero.            |
-| `sort:updated-asc`    | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) organizará los resultados para mostrar aquellos actualizados menos recientemente.     |
-| `sort:updated-desc`   | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) organizará los resultados para mostrar los aquellos actualizados más recientemente. |
-| `is:withdrawn`        | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) mostrará únicamente las asesorías que se han retirado.                                        |
-| `created:YYYY-MM-DD`  | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) mostrará únicamente las asesorías creadas en esta fecha.                          |
-| `updated:YYYY-MM-DD`  | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) mostrará únicamente asesorías actualizadas en esta fecha.                         |
+| Qualifier       | Ejemplo                                                                                                                                                                         |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `type:reviewed` | [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. |
+{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
+{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
+| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | | `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | | `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | | `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | | `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | | `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | | `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | | `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | | `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | | `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | | `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | | `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | | `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | | `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
 
 ## Visualizar tus repositorios vulnerables
 
-For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability or malware. Para ver un repositorio vulnerable, debes tener acceso a las {% data variables.product.prodname_dependabot_alerts %} de este. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)".
+For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. Para ver un repositorio vulnerable, debes tener acceso a las {% data variables.product.prodname_dependabot_alerts %} de este. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)".
 
 1. Navega hasta https://github.com/advisories.
 2. Haz clic en una asesoría.
@@ -137,6 +130,38 @@ For any {% data variables.product.company_short %}-reviewed advisory in the {% d
 4. Opcionalmente, para filtrar la lista, utiliza la barra de búsqueda o los menús desplegables. El menú desplegable de "Organización" te permite filtrar las {% data variables.product.prodname_dependabot_alerts %} por propietario (organización o usuario). ![Barra de búsqueda y menús desplegables para filtrar alertas](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
 5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
 
+{% ifversion security-advisories-ghes-ghae %}
+## Accessing the local advisory database on {% data variables.product.product_location %}
+
+If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.product.product_location %}, you can also browse reviewed advisories locally. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
+
+You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories.
+
+1. Navigate to `https://HOSTNAME/advisories`.
+2. Opcionalmente, para filtrar la lista, utiliza cualquiera de los menúes desplegables. ![Filtros desplegables](/assets/images/help/security/advisory-database-dropdown-filters.png)
+   {% note %}
+
+   **Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)".
+
+   {% endnote %}
+3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %}
+
+You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.product.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)".
+
+### Viewing vulnerable repositories for {% data variables.product.product_location %}
+
+{% data reusables.repositories.enable-security-alerts %}
+
+In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. Para ver un repositorio vulnerable, debes tener acceso a las {% data variables.product.prodname_dependabot_alerts %} de este. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)".
+
+1. Navigate to `https://HOSTNAME/advisories`.
+2. Haz clic en una asesoría.
+3. En la parte superior de la página de la asesoría, haz clic en **Alertas del dependabot**. ![Las alertas del dependabot](/assets/images/help/security/advisory-database-dependabot-alerts.png)
+4. Opcionalmente, para filtrar la lista, utiliza la barra de búsqueda o los menús desplegables. El menú desplegable de "Organización" te permite filtrar las {% data variables.product.prodname_dependabot_alerts %} por propietario (organización o usuario). ![Barra de búsqueda y menús desplegables para filtrar alertas](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
+5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
+
+{% endif %}
+
 ## Leer más
 
 - [Definición de MITRE de "vulnerabilidad"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
index c8b4b5d2a2..f935a42a90 100644
--- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
+++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
@@ -7,6 +7,8 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Security advisories
@@ -19,8 +21,9 @@ shortTitle: Editar la base de datos de asesorías
 
 ## Acerca de editar las asesorías en la {% data variables.product.prodname_advisory_database %}
 Las asesorías de seguridad en la {% data variables.product.prodname_advisory_database %} en [github.com/advisories](https://github.com/advisories) se consideran asesorías globales. Cualquiera puede sugerir mejoras en cualquier asesoría de seguridad en la {% data variables.product.prodname_advisory_database %}. Puedes editar o agregar cualquier detalle, incluyendo los ecosistemas adicionales afectados, el nivel de severidad o la descripción de quién se vio impactado. El equipo de selección de {% data variables.product.prodname_security %} revisará las mejoras enviadas y las publicará en la {% data variables.product.prodname_advisory_database %} en caso de que se acepten.
+{% ifversion fpt or ghec %}
+Solo los propietarios y adminsitradores de repositorios pueden editar las asesorías de seguridad a nivel de repositorio. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
 
-Solo los propietarios y adminsitradores de repositorios pueden editar las asesorías de seguridad a nivel de repositorio. Para obtener más información, consulta la sección "[Editar una asesoría de seguridad de repositorio](/code-security/security-advisories/editing-a-security-advisory)".
 ## Editar las asesorías en la base de datos de asesorías de GitHub
 
 1. Navega hasta https://github.com/advisories.
@@ -30,4 +33,15 @@ Solo los propietarios y adminsitradores de repositorios pueden editar las asesor
 5. Cuand terminas de editar la asesoría, haz clic en **Enviar mejoras**.
 6. Una vez que emites tus mejoras, el equipo de selección de {% data variables.product.prodname_security %} creará una solicitud de cambios en [github/advisory-database](https://github.com/github/advisory-database), la cuál contendrá tus cambios para revisarlos. Si la asesoría se originó desde un repositorio de {% data variables.product.prodname_dotcom %}, también etiquetaremos al publicador original para que pueda agregar un comentario opcional. Puedes ver la solicitud de cambios y obtener notificaciones cuando se actualice o cierre.
 
-También puedes abrir una solicitud de cambios directamente en un archivo de asesoría en el repositorio [github/advisory-database](https://github.com/github/advisory-database). Para obtener más información, consulta los [lineamientos de contribución](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). 
+También puedes abrir una solicitud de cambios directamente en un archivo de asesoría en el repositorio [github/advisory-database](https://github.com/github/advisory-database). Para obtener más información, consulta los [lineamientos de contribución](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md).
+
+{% ifversion security-advisories-ghes-ghae %}
+## Editing advisories from {% data variables.product.product_location %}
+
+If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.product.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url.
+
+1. Navigate to `https://HOSTNAME/advisories`.
+2. Selecciona la asesoría de seguridad a la cual te gustaría contribuir.
+3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on Github.com.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}. ![Enlace para sugerir mejoras](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png)
+4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above.
+{% endif %}
diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
index 01f1908cf9..1af433b3b7 100644
--- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
+++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
@@ -150,32 +150,32 @@ Para los lenguajes compatibles, el {% data variables.product.prodname_dependabot
 
 {% tip %}
 
-**Tip:** You can only dismiss open alerts.
+**Tip:** Solo puedes descartar las alertas abiertas.
 {% endtip %}
 
-If you schedule extensive work to upgrade a dependency, or decide that an alert does not need to be fixed, you can dismiss the alert. Dismissing alerts that you have already assessed makes it easier to triage new alerts as they appear.
+Si programas mucho trabajo para actualizar una dependencias o decides que una alerta no necesita corregirse, puedes descartar la alerta. El descartar alertas que ya valoraste facilita clasificar las nuevas que aparecen.
 
 1. Ver los detalles de una alerta. Para obtener más información, consulta la sección "[Ver las dependencias vulnerables](#viewing-dependabot-alerts)" (anteriormente).
-1. Select the "Dismiss" dropdown, and click a reason for dismissing the alert.{% ifversion reopen-dependabot-alerts %} Unfixed dismissed alerts can be reopened later.{% endif %} ![Elegir una razón para descartar la alerta a través del menú desplegable de "Descartar"](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png)
+1. Selecciona el menú desplegable de "Descartar" y haz clic en una razón para descartar la alerta.{% ifversion reopen-dependabot-alerts %} Las alertas descartadas sin fijar pueden volverse a abrir posteriormente.{% endif %} ![Elegir una razón para descartar la alerta a través del menú desplegable de "Descartar"](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png)
 {% ifversion dependabot-bulk-alerts %}
 
 ### Descartar varias alertas al mismo tiempo
 
-1. View the open {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Viewing {% data variables.product.prodname_dependabot_alerts %}](/en/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-dependabot-alerts)".
-2. Optionally, filter the list of alerts by selecting a dropdown menu, then clicking the filter that you would like to apply. También puedes teclear filtros en la barra de búsqueda.
-3. To the left of each alert title, select the alerts that you want to dismiss. ![Screenshot of open alerts with checkboxes emphasized](/assets/images/help/graphs/select-multiple-alerts.png)
-4. Optionally, at the top of the list of alerts, select all alerts on the page. ![Screenshot of all open alerts selected](/assets/images/help/graphs/select-all-alerts.png)
-5. Select the "Dismiss alerts" dropdown, and click a reason for dismissing the alerts. ![Screenshot of open alerts page with "Dismiss alerts" drop-down emphasized](/assets/images/help/graphs/dismiss-multiple-alerts.png)
+1. Mira las {% data variables.product.prodname_dependabot_alerts %} abiertas. Para obtener más información, consulta la sección "[Ver las {% data variables.product.prodname_dependabot_alerts %}](/en/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-dependabot-alerts)".
+2. Opcionalmente, filtra la lista de alertas seleccionado un menú desplegable y haciendo clic en el filtro que te gustaría aplicar. También puedes teclear filtros en la barra de búsqueda.
+3. A la izquierda de cada título de alerta, selecciona aquellas que quieras descartar. ![Captura de pantalla de las alertas abiertas con énfasis en las casillas de verificación](/assets/images/help/graphs/select-multiple-alerts.png)
+4. Opcionalmente, en la parte superior de la lista de alertas, selecciona todas en la página. ![Captura de pantalla de todas las alertas abiertas seleccionadas](/assets/images/help/graphs/select-all-alerts.png)
+5. Selecciona el menú desplegable de "Descartar alertas" y haz clic en una razón para hacerlo. ![Captura de pantalla de la página con alertas abiertas y énfasis en el menú desplegable de "Descartar alertas"](/assets/images/help/graphs/dismiss-multiple-alerts.png)
 
 {% endif %}
 
 {% ifversion reopen-dependabot-alerts %}
 
-## Viewing and updating closed alerts
+## Ver y actualziar las alertas cerradas
 
 {% tip %}
 
-**Tip:** You can only reopen alerts that have been previously dismissed. Closed alerts that have already been fixed cannot be reopened.
+**Tip:** Solo puedes volver a abrir alertas que se hayan descartado previamente. Las alertas cerradas que ya se hayan corregido no se pueden volver a abrir.
 {% endtip %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -185,17 +185,17 @@ If you schedule extensive work to upgrade a dependency, or decide that an alert
 ![Screenshot showing the "Closed" option](/assets/images/help/repository/dependabot-alerts-closed.png){% endif %}
 1. Haz clic en la alerta que te gustaría ver o actualizar.{% ifversion dependabot-bulk-alerts %} ![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert-checkbox.png){% else %}
 ![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert.png){% endif %}
-2. Optionally, if the alert was dismissed and you wish to reopen it, click **Reopen**. Alerts that have already been fixed cannot be reopened. ![Screenshot showing the "Reopen" button](/assets/images/help/repository/reopen-dismissed-alert.png)
+2. Opcionalmente, si se descartó la alerta y quieres volver a abrirla, haz clic en **Reabrir**. Las alertas que ya se hayan corregido no pueden volverse a abrir. ![Captura de pantalla que muestra el botón "Reabrir"](/assets/images/help/repository/reopen-dismissed-alert.png)
 
 {% endif %}
 
 {% ifversion dependabot-bulk-alerts %}
 
-### Reopening multiple alerts at once
+### Reabrir alertas múltiples al mismo tiempo
 
-1. View the closed {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Viewing and updating closed alerts](/en/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-and-updating-closed-alerts)" (above).
-2. To the left of each alert title, select the alerts that you want to reopen. ![Screenshot of closed alerts with checkboxes emphasized](/assets/images/help/repository/dependabot-alerts-open-checkbox.png)
-3. Optionally, at the top of the list of alerts, select all closed alerts on the page. ![Screenshot of closed alerts with all alerts selected](/assets/images/help/graphs/select-all-closed-alerts.png)
-4. Click **Reopen** to reopen the alerts. Alerts that have already been fixed cannot be reopened. ![Screenshot of closed alerts with "Reopen" button emphasized](/assets/images/help/graphs/reopen-multiple-alerts.png)
+1. Ver las {% data variables.product.prodname_dependabot_alerts %} cerradas. Para obtener más información, consulta la sección "[Ver y actualizar las alertas cerradas](/en/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-and-updating-closed-alerts)" (anteriormente).
+2. A la izquierda de cada título de alerta, selecciona aquellas que quieras reabrir. ![Captura de pantalla de las alertas cerradas con énfasis en las casillas de verificación](/assets/images/help/repository/dependabot-alerts-open-checkbox.png)
+3. Opcionalmente, en la parte superior de la lista de alertas, selecciona todas las alertas cerradas en la página. ![Captura de pantalla de las alertas cerradas con todas las alertas seleccionadas](/assets/images/help/graphs/select-all-closed-alerts.png)
+4. Haz clic en **Reabrir** para reabrir las alertas. Las alertas que ya se hayan corregido no pueden volverse a abrir. ![Captura de pantalla de las alertas cerradas con énfasis en el botón "Reabrir"](/assets/images/help/graphs/reopen-multiple-alerts.png)
 
 {% endif %}
diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/es-ES/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
index 700c159f89..882f325b33 100644
--- a/translations/es-ES/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
+++ b/translations/es-ES/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
@@ -33,7 +33,7 @@ topics:
 
 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, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)".
 
-You can disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository or for all repositories owned by your personal account or organization. Para obtener más información, consulta la sección "[Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tus repositorios](#managing-dependabot-security-updates-for-your-repositories)" acontinuación.
+Puedes inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual o para todos los repositorios que pertenezcan a tu organización o cuenta personal. Para obtener más información, consulta la sección "[Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tus repositorios](#managing-dependabot-security-updates-for-your-repositories)" acontinuación.
 
 {% ifversion fpt or ghec %}{% data reusables.dependabot.dependabot-tos %}{% endif %}
 
@@ -63,7 +63,7 @@ Si no se habilitan las actualizaciones de seguridad para tu repositorio y no sab
 Puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual (ver a continuación).
 
 
-You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your personal account or organization. Para obtener más información, consulta la sección "[Administrar los ajustes de seguridad y análisis de tu cuenta personal](/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 los ajustes de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)".
+También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios que pertenezcan a tu cuenta de usuario personal. Para obtener más información, consulta la sección "[Administrar los ajustes de seguridad y análisis de tu cuenta personal](/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 los ajustes de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)".
 
 Las {% data variables.product.prodname_dependabot_security_updates %} requieren de configuraciones de repositorio específicas. Para obtener más información, consulta "[Repositorios soportados](#supported-repositories)".
 
@@ -72,7 +72,7 @@ Las {% data variables.product.prodname_dependabot_security_updates %} requieren
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-code-security-and-analysis %}
-1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** to enable the feature or **Disable** to disable it. {% ifversion fpt or ghec %}Para repositorios públicos, el botón está inhabilitado si la característica siempre está habilitada.{% endif %}
+1. Debajo de "Análisis y seguridad del código", a la derecha de "Actualizaciones de seguridad del {% data variables.product.prodname_dependabot %}", haz clic en **Habilitar** para habilitar la característica o en **Inhabilitar** para inhabilitarla. {% ifversion fpt or ghec %}Para repositorios públicos, el botón está inhabilitado si la característica siempre está habilitada.{% endif %}
   {% ifversion fpt or ghec %}![Screenshot of "Code security and analysis" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghes > 3.6 or ghae-issue-7044 %}<!--Insertar captura de pantalla de GHES 3.7 cuando esté disponible-->{% else %}![Screenshot of "Code security and analysis" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
 
 ## Anular el comportamiento predeterminado con un archivo de configuración
diff --git a/translations/es-ES/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
index f09d41f793..850f9ff0c1 100644
--- a/translations/es-ES/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
+++ b/translations/es-ES/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
@@ -32,9 +32,9 @@ El {% data variables.product.prodname_secret_scanning_caps %} como protección c
 
 Para que puedas utilizar el {% data variables.product.prodname_secret_scanning %} como protección contra subidas, el repositorio u organización necesita tener habilitados tanto la {% data variables.product.prodname_GH_advanced_security %} como el {% data variables.product.prodname_secret_scanning %}. Para obtener más información, consulta las secciones "[Administrar los ajustes de seguridad y análisis de tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)", "[Administrar los ajustes de seguridad y análisis de tu repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" y "[Acerca de la {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)".
 
-Organization owners, security managers, and repository administrators can enable push protection for {% data variables.product.prodname_secret_scanning %} via the UI and API. Para obtener más información, consulta la sección "[Repositorios](/rest/reference/repos#update-a-repository)" y expande la sección de "Propiedades del objeto `security_and_analysis`" en la documentación de la API de REST.
+Los propietarios de las organizaciones, administradores de seguridad y administradores de repositorio pueden habilitar la protección de subida para {% data variables.product.prodname_secret_scanning %} a través de la IU y de la API. Para obtener más información, consulta la sección "[Repositorios](/rest/reference/repos#update-a-repository)" y expande la sección de "Propiedades del objeto `security_and_analysis`" en la documentación de la API de REST.
 
-### Enabling {% data variables.product.prodname_secret_scanning %} as a push protection for an organization
+### Habilitar el {% data variables.product.prodname_secret_scanning %} como protección contra subida para una organización
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
@@ -42,7 +42,7 @@ Organization owners, security managers, and repository administrators can enable
 {% data reusables.repositories.navigate-to-ghas-settings %}
 {% data reusables.advanced-security.secret-scanning-push-protection-org %}
 
-### Enabling {% data variables.product.prodname_secret_scanning %} as a push protection for a repository
+### Habilitar el {% data variables.product.prodname_secret_scanning %} como protección de subida para un repositorio
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -51,13 +51,13 @@ Organization owners, security managers, and repository administrators can enable
 {% data reusables.advanced-security.secret-scanning-push-protection-repo %}
 
 
-## Using {% data variables.product.prodname_secret_scanning %} as a push protection from the command line
+## Utilizar el {% data variables.product.prodname_secret_scanning %} como protección de subida desde la línea de comandos
 
-When you attempt to push a supported secret to a repository or organization with {% data variables.product.prodname_secret_scanning %} as a push protection enabled, {% data variables.product.prodname_dotcom %} will block the push. You can remove the secret from your commit or follow a provided URL to allow the push.
+Cuando intentas subir un secreto compatible a un repositorio u organización con {% data variables.product.prodname_secret_scanning %} como una protección contra subida habilitada, {% data variables.product.prodname_dotcom %} bloqueará la subida. Puedes eliminar el secreto desde tu confirmación o seguir una URL proporcionada para permitir la subida.
 
-Up to five detected secrets will be displayed at a time on the command line. Si ya se detectó un secreto en particular en el repositorio y la alerta ya existe, {% data variables.product.prodname_dotcom %} no lo bloqueará.
+Se mostrarán hasta cinco secretos detectados a la vez en la línea de comandos. Si ya se detectó un secreto en particular en el repositorio y la alerta ya existe, {% data variables.product.prodname_dotcom %} no lo bloqueará.
 
-![Screenshot showing that a push is blocked when a user attempts to push a secret to a repository](/assets/images/help/repository/secret-scanning-push-protection-with-link.png)
+![Captura de pantalla que muestra que una subida está bloqueada cuando un usuario intenta subir un secreto a un repositorio](/assets/images/help/repository/secret-scanning-push-protection-with-link.png)
 
 Si necesitas eliminar el secreto de tu última confirmación (es decir, `HEAD`) en la rama que se está subiendo y cualquier confirmación anterior que lo contenga, puedes eliminarlo de `HEAD` y luego combinar las confirmaciones que haya entre ellos cuando la confirmación se introdujo y la primera versión de `HEAD` para la cual se eliminó el secreto.
 
@@ -65,34 +65,34 @@ Si necesitas eliminar el secreto de tu última confirmación (es decir, `HEAD`)
 
 **Notas**:
 
-* If your git configuration supports pushes to multiple branches, and not only to the default branch, your push may be blocked due to additional and unintended refs being pushed. For more information, see the [`push.default` options](https://git-scm.com/docs/git-config#Documentation/git-config.txt-pushdefault) in the Git Docs.
-* If {% data variables.product.prodname_secret_scanning %} upon a push times out, {% data variables.product.prodname_dotcom %} will still run a scan after the push.
+* Si tu configuración de git es compatible con las subidas a ramas múltiples y no solo a la rama predeterminada, tu subida podría bloquearse debido a que se están subiendo refs imprevistos y adicionales. Para obtener más información, consulta las [opciones de `push.default`](https://git-scm.com/docs/git-config#Documentation/git-config.txt-pushdefault) en los documentos de Git.
+* Si el {% data variables.product.prodname_secret_scanning %} excede el tiempo cuando se hace una subida, {% data variables.product.prodname_dotcom %} aún ejecutará el escaneo después de dicha subida.
 
 {% endnote %}
 
-### Allowing a blocked secret to be pushed
+### Permitir que se suba un secreto bloqueado
 
 Si {% data variables.product.prodname_dotcom %} bloquea un secreto que piensas se puede subir con seguridad, puedes permitirlo y especificar la razón por la cual se debería de permitir.
 
-Si confirmas que un secreto es real y que pretendes corregirlo después, debes intentar remediarlo tan pronto como sea posible. For example, you might revoke the secret and remove the secret from the repository's commit history. For more information, see "[Removing sensitive data from a repository](/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)."
+Si confirmas que un secreto es real y que pretendes corregirlo después, debes intentar remediarlo tan pronto como sea posible. Por ejemplo, podrías revocar el secreto y eliminarlo del historial de confirmaciones del repositorio. Para obtener más información, consulta la sección "[Eliminar datos confidenciales de un repositorio](/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)".
 
 {% data reusables.secret-scanning.push-protection-allow-secrets-alerts %}
 
-1. Visit the URL returned by {% data variables.product.prodname_dotcom %} when your push was blocked. ![Captura de pantalla que muestra un formulario con opciones para desbloquear la subida de un secreto](/assets/images/help/repository/secret-scanning-unblock-form.png)
+1. Visita la URL que devolvió {% data variables.product.prodname_dotcom %} cuando se bloqueó tu subida. ![Captura de pantalla que muestra un formulario con opciones para desbloquear la subida de un secreto](/assets/images/help/repository/secret-scanning-unblock-form.png)
 {% data reusables.secret-scanning.push-protection-choose-allow-secret-options %}
-1. Click **Allow me to push this secret**.
-2. Reattempt the push on the command line within three hours. If you have not pushed within three hours, you will need to repeat this process.
+1. Haz clic en **Permitirme subir este secreto**.
+2. Vuelve a intentar la subida en la línea de comandos al cabo de tres horas. Si no has realizado una subida a cabo de tres horas, necesitarás repetir este proceso.
 
 {% ifversion secret-scanning-push-protection-web-ui %}
-## Using secret scanning as a push protection from the web UI
+## Utilizar el escaneo de secretos como una protección de subida desde la IU web
 
-When you use the web UI to attempt to commit a supported secret to a repository or organization with secret scanning as a push protection enabled, {% data variables.product.prodname_dotcom %} will block the commit. You will see a banner at the top of the page with information about the secret's location, and the secret will also be underlined in the file so you can easily find it.
+Cuando utilizas la IU web para intentar confirmar un secreto compatible en un repositorio u organización con el escaneo de secretos como protección contra subidas habilitada, {% data variables.product.prodname_dotcom %} la bloqueará. Puedes ver un letrero en la parte superior de la página con información sobre la ubicación del secreto y este también se subrayará en el archivo para que lo puedas encontrar con facilidad.
 
-  ![Screenshot showing commit in web ui blocked because of secret scanning push protection](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner.png)
+  ![Captura de pantalla que muestra una confirmación bloqueada en la IU web debido a la protección contra subidas del escaneo de secretos](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner.png)
 
-{% data variables.product.prodname_dotcom %} will only display one detected secret at a time in the web UI. Si ya se detectó un secreto en particular en el repositorio y la alerta ya existe, {% data variables.product.prodname_dotcom %} no lo bloqueará.
+{% data variables.product.prodname_dotcom %} solo mostrará un secreto detectado a la vez en la IU web. Si ya se detectó un secreto en particular en el repositorio y la alerta ya existe, {% data variables.product.prodname_dotcom %} no lo bloqueará.
 
-You can remove the secret from the file using the web UI. Una vez que elimines el secreto, el letrero en la parte superior de la página cambiará y te dirá que ahora puedes confirmar tus cambios.
+Puedes eliminar el secreto del archivo utilizando la IU web. Una vez que elimines el secreto, el letrero en la parte superior de la página cambiará y te dirá que ahora puedes confirmar tus cambios.
 
   ![Captura de pantalla que muestra la confirmación en la Iu web después de que se corrigió un secreto](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-allowed.png)
 
diff --git a/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md b/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
index 1be7377e30..d90dd8335f 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
@@ -57,7 +57,7 @@ Para valorar el impacto de una vulnerabilidad en tu código, también necesitas
 
 ## Asegurar tus tokens de comunicación
 
-A menudo, el código necesita comunicarse con otros sistemas a través de una red y requiere secretos (como una contrasella o llave de API) para autenticarse. Tu sistema necesita acceso a estos secretos para ejecutarse, pero es la mejor práctica el no incluirlos en tu código fuente. Esto es especialmente importante en el caso de los repositorios públicos, pero también para los repositorios privados a los cuales tienen acceso muchas personas.
+A menudo, el código necesita comunicarse con otros sistemas a través de una red y requiere secretos (como una contrasella o llave de API) para autenticarse. Tu sistema necesita acceso a estos secretos para ejecutarse, pero es la mejor práctica el no incluirlos en tu código fuente. Esto es especialmente importante para los repositorios a los cuales tienen acceso muchas personas{% ifversion not ghae %} y es crítico para los repositorios públicos{% endif %}.
 
 ### Detección automática de secretos confirmados a un repositorio
 
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 11efae4d56..f04fc26158 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
@@ -58,7 +58,7 @@ Si agregas una política a nivel organizacional, deberías configurarla en la el
 
 {% data reusables.codespaces.codespaces-policy-targets %}
 1. Si quieres agregar otra restricción a la política, haz clic en **Agregar restricción** y elige otra de ellas. Para obtener 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)", "[Restringir el periodo de tiempo de espera inactivo](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)" y "[Restringir el periodo de retención para los codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)".
-1. After you've finished adding constraints to your policy, click **Save**.
+1. Después de que termines de agregar restricciones a tu política, haz clic en **Guardar**.
 ## Editar una política
 
 You can edit an existing policy. Por ejemplo, puede que quieras agregar o eliminar restricciones hacia o desde una política.
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
index 616a1129ea..0423976756 100644
--- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
@@ -59,7 +59,7 @@ If you add an organization-wide policy with a timeout constraint, you should set
 
 {% data reusables.codespaces.codespaces-policy-targets %}
 1. Si quieres agregar otra restricción a la política, haz clic en **Agregar restricción** y elige otra de ellas. Para obtener información sobre otras restricciones, consulta las secciones "[Restringir el acceso a los tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)", "[Restringir la visibilidad de los puertos reenviados](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" y "[Restringir el periodo de retención para los codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)".
-1. After you've finished adding constraints to your policy, click **Save**.
+1. Después de que termines de agregar restricciones a tu política, haz clic en **Guardar**.
 
 The policy will be applied to all new codespaces that are created, and to existing codespaces the next time they are started.
 
@@ -73,7 +73,7 @@ You can edit an existing policy. Por ejemplo, puede que quieras agregar o elimin
 
 ## Borrar una política
 
-1. Muestra la página de "Políticas del Codespace". For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)."
+1. Muestra la página de "Políticas del Codespace". Para obtener más información, consulta la sección "[Agregar una política para configurar un periodo de tiempo de inactividad máximo](#adding-a-policy-to-set-a-maximum-idle-timeout-period)".
 1. Haz clic en el botón de borrar a la derecha de la política que quieras borrar.
 
    ![El botón de borrar para una política](/assets/images/help/codespaces/policy-delete.png)
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
index 05ee7c6467..7fd329e263 100644
--- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
@@ -55,7 +55,7 @@ Si agregas una política de toda la organización, deberías configurarla para q
 
 {% data reusables.codespaces.codespaces-policy-targets %}
 1. Si quieres agregar otra restricción a la política, haz clic en **Agregar restricción** y elige otra de ellas. Para obtener más información sobre otras restricciones, consulta las secciones "[Restringir el acceso a los tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)", "[Restringir el periodo de tiempo de inactividad](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)" y "[Restringir el periodo de detección para los codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)".
-1. After you've finished adding constraints to your policy, click **Save**.
+1. Después de que termines de agregar restricciones a tu política, haz clic en **Guardar**.
 ## Editar una política
 
 You can edit an existing policy. Por ejemplo, puede que quieras agregar o eliminar restricciones hacia o desde una política.
diff --git a/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-a-jetbrains-ide.md b/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-a-jetbrains-ide.md
index 995459a64a..a1c8df2e36 100644
--- a/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-a-jetbrains-ide.md
+++ b/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-a-jetbrains-ide.md
@@ -25,7 +25,7 @@ You can use the default keyboard shortcuts for inline suggestions in your JetBra
 
 | Acción                                                                                       | Shortcut                                       |
 |:-------------------------------------------------------------------------------------------- |:---------------------------------------------- |
-| Accept an inline suggestion                                                                  | <kbd>Tab</kbd>                                 |
+| Aceptar una sugerencia en una línea                                                          | <kbd>Tab</kbd>                                 |
 | Dismiss an inline suggestion                                                                 | <kbd>Esc</kbd>                                 |
 | Show next inline suggestion                                                                  | <kbd>Option (⌥) or Alt</kbd>+<kbd>]</kbd>      |
 | Show previous inline suggestion                                                              | <kbd>Option (⌥) or Alt</kbd>+<kbd>[</kbd>      |
@@ -38,7 +38,7 @@ You can use the default keyboard shortcuts for inline suggestions in your JetBra
 
 | Acción                                                                                       | Shortcut                        |
 |:-------------------------------------------------------------------------------------------- |:------------------------------- |
-| Accept an inline suggestion                                                                  | <kbd>Tab</kbd>                  |
+| Aceptar una sugerencia en una línea                                                          | <kbd>Tab</kbd>                  |
 | Dismiss an inline suggestion                                                                 | <kbd>Esc</kbd>                  |
 | Show next inline suggestion                                                                  | <kbd>Alt</kbd>+<kbd>]</kbd>     |
 | Show previous inline suggestion                                                              | <kbd>Alt</kbd>+<kbd>[</kbd>     |
@@ -51,7 +51,7 @@ You can use the default keyboard shortcuts for inline suggestions in your JetBra
 
 | Acción                                                                                       | Shortcut                        |
 |:-------------------------------------------------------------------------------------------- |:------------------------------- |
-| Accept an inline suggestion                                                                  | <kbd>Tab</kbd>                  |
+| Aceptar una sugerencia en una línea                                                          | <kbd>Tab</kbd>                  |
 | Dismiss an inline suggestion                                                                 | <kbd>Esc</kbd>                  |
 | Show next inline suggestion                                                                  | <kbd>Alt</kbd>+<kbd>]</kbd>     |
 | Show previous inline suggestion                                                              | <kbd>Alt</kbd>+<kbd>[</kbd>     |
diff --git a/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code.md b/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code.md
index 71ad993d92..37b92581e4 100644
--- a/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code.md
+++ b/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code.md
@@ -37,9 +37,9 @@ You can use the default keyboard shortcuts in {% data variables.product.prodname
 
 {% windows %}
 
-| Acción                                                                                       | Shortcut                         | Command name                             |
+| Acción                                                                                       | Shortcut                         | Nombre del comando                       |
 |:-------------------------------------------------------------------------------------------- |:-------------------------------- |:---------------------------------------- |
-| Accept an inline suggestion                                                                  | <kbd>Tab</kbd>                   | editor.action.inlineSuggest.commit       |
+| Aceptar una sugerencia en una línea                                                          | <kbd>Tab</kbd>                   | editor.action.inlineSuggest.commit       |
 | Dismiss an inline suggestion                                                                 | <kbd>Esc</kbd>                   | editor.action.inlineSuggest.hide         |
 | Show next inline suggestion                                                                  | <kbd>Alt</kbd>+<kbd>]</kbd>      | editor.action.inlineSuggest.showNext     |
 | Show previous inline suggestion                                                              | <kbd>Alt</kbd>+<kbd>[</kbd>      | editor.action.inlineSuggest.showPrevious |
@@ -52,9 +52,9 @@ You can use the default keyboard shortcuts in {% data variables.product.prodname
 
 {% linux %}
 
-| Acción                                                                                       | Shortcut                         | Command name                             |
+| Acción                                                                                       | Shortcut                         | Nombre del comando                       |
 |:-------------------------------------------------------------------------------------------- |:-------------------------------- |:---------------------------------------- |
-| Accept an inline suggestion                                                                  | <kbd>Tab</kbd>                   | editor.action.inlineSuggest.commit       |
+| Aceptar una sugerencia en una línea                                                          | <kbd>Tab</kbd>                   | editor.action.inlineSuggest.commit       |
 | Dismiss an inline suggestion                                                                 | <kbd>Esc</kbd>                   | editor.action.inlineSuggest.hide         |
 | Show next inline suggestion                                                                  | <kbd>Alt</kbd>+<kbd>]</kbd>      | editor.action.inlineSuggest.showNext     |
 | Show previous inline suggestion                                                              | <kbd>Alt</kbd>+<kbd>[</kbd>      | editor.action.inlineSuggest.showPrevious |
diff --git a/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio.md b/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio.md
index dfaae40163..1f4f33078c 100644
--- a/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio.md
+++ b/translations/es-ES/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio.md
@@ -21,7 +21,7 @@ To configure {% data variables.product.prodname_copilot %} in {% data variables.
 
 You can use the default keyboard shortcuts in {% data variables.product.prodname_vs %} when using {% data variables.product.prodname_copilot %}. Alternatively, you can rebind the shortcuts in the Tools settings for {% data variables.product.prodname_vs %} using your preferred keyboard shortcuts for each specific command. You can search for each keyboard shortcut by its command name in the Keyboard Shortcuts editor.
 
-| Acción                          | Shortcut                                     | Command name                         |
+| Acción                          | Shortcut                                     | Nombre del comando                   |
 |:------------------------------- |:-------------------------------------------- |:------------------------------------ |
 | Show next inline suggestion     | <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>]</kbd>  | Tools.Nextsuggestion                 |
 | Show previous inline suggestion | <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>[</kbd>  | Tools.Previoussuggestion             |
diff --git a/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md b/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md
index 77cee19fab..9468908ea7 100644
--- a/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md
+++ b/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md
@@ -75,7 +75,7 @@ To use {% data variables.product.prodname_copilot %}, you must first install the
 1. To open a new tab with multiple additional options, press <kbd>Ctrl</kbd>+<kbd>Enter</kbd>.
 1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab.
 
-## Generating code suggestions from comments
+## Generar sugerencias de código desde los comentarios
 
 {% data reusables.copilot.generating-suggestions-from-comments %}
 
diff --git a/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md b/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md
index 03563c76b6..14093103a2 100644
--- a/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md
+++ b/translations/es-ES/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md
@@ -64,7 +64,7 @@ To use {% data variables.product.prodname_copilot %}, you must first install the
 1. Optionally, you can hover over the suggestion to see the {% data variables.product.prodname_copilot %} command palette for choosing suggestions.
 {% data reusables.copilot.accept-or-reject-suggestion %}
 
-## Generating code suggestions from comments
+## Generar sugerencias de código desde los comentarios
 
 {% data reusables.copilot.generating-suggestions-from-comments %}
 
diff --git a/translations/es-ES/content/copilot/quickstart.md b/translations/es-ES/content/copilot/quickstart.md
index 55fc76a076..8b5e1de729 100644
--- a/translations/es-ES/content/copilot/quickstart.md
+++ b/translations/es-ES/content/copilot/quickstart.md
@@ -30,7 +30,7 @@ This guide will show you how to sign up for {% data variables.product.prodname_c
 To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vscode %} extension.
 
 1. En el mercado de {% data variables.product.prodname_vscode %}, dirígete a la página de la [Extensión del {% data variables.product.prodname_copilot %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) y haz clic en **Instalar**. ![Install {% data variables.product.prodname_copilot %} extension {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/install-copilot-extension-visual-studio-code.png)
-1. A popup will appear, asking to open {% data variables.product.prodname_vscode %}. Click **Open {% data variables.product.prodname_vscode %}**.
+1. A popup will appear, asking to open {% data variables.product.prodname_vscode %}. Haz clic en **Abrir {% data variables.product.prodname_vscode %}**.
 1. In the "Extension: {% data variables.product.prodname_copilot %}" tab in {% data variables.product.prodname_vscode %}, click **Install**. ![Install button in {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/in-visual-studio-code-install-button.png)
 1. Si no has autorizado a {% data variables.product.prodname_vscode %} previamente en tu cuenta de {% data variables.product.prodname_dotcom %}, se te pedirá iniciar sesión en {% data variables.product.prodname_dotcom %} en {% data variables.product.prodname_vscode %}.
    - If you have previously authorized {% data variables.product.prodname_vscode %} in your {% data variables.product.prodname_dotcom %} account, {% data variables.product.prodname_copilot %} will be automatically authorized. ![Screen shot of {% data variables.product.prodname_vscode %} authorization screen](/assets/images/help/copilot/vsc-copilot-authorize.png)
diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md
index 51414b71ee..6254c0cb52 100644
--- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md
+++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md
@@ -126,7 +126,7 @@ Una vez que estés satisfecho con los cambios que elegiste incluir en tu confirm
 
 6. Si tienes una solicitud de cambios basada en la rama sobre la cual estás trabajando, {% data variables.product.prodname_desktop %} mostrará el estado de las verificaciones que se han ejecutado para dicha solicitud. Para obtener más información sobre las verificaciones, 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)".
 
- ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png)
+ ![Las verificaciones se muestran junto al nombre de rama](/assets/images/help/desktop/checks-dialog.png)
 
  Si no se ha creado una solicitud de cambios para la rama actual, {% data variables.product.prodname_desktop %} te dará la opción de crear una. Para obtener más información, consulta la sección "[Crear un informe de problemas o solicitud de extracción](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request)."
 
diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
index 47752c3597..4432e05746 100644
--- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
+++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
@@ -2,8 +2,7 @@
 title: Acerca de los debates
 intro: 'Utiliza los debates para preguntar y responder preguntas, compartir información, hacer anuncios y moderar o participar en una conversación sobre un proyecto en {% data variables.product.product_name %}.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
@@ -22,7 +21,7 @@ Puedes utilizar los debates del repositorio para hablar sobre temas que sean esp
 
 No necesitas cerrar un debate de la misma forma en que cierras una propuesta o una solicitud de cambios.
 
-Si un administrador de repositorio o mantenedor de proyecto habilita los {% data variables.product.prodname_discussions %} para un repositorio, cualquiera que visite el repositorio podrá crear y participar en los debates de este. Si un propietario de organización habilita los {% data variables.product.prodname_discussions %} para esta, cualquiera que pueda ver el repositorio origen puede crear un debate de organización.
+If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who has access to the repository can create and participate in discussions for the repository. Si un propietario de organización habilita los {% data variables.product.prodname_discussions %} para esta, cualquiera que pueda ver el repositorio origen puede crear un debate de organización.
 
 Los administradores del repositorio y los mantenedores del proyecto pueden administrar los debates y las categorías de los mismos en un repositorio y fijarlos para incrementar la visibilidad de éstos. Los moderadores y colaboradores pueden marcar los comentarios como respuestas, fijar debates, y convertir las propuestas en debates. Del mismo modo, para los debates organizacionales, el rol de un usuario en el repositorio origen determinará cómo puede interactuar dicho usuario con los debates de la organización. Para obtener más información, consulta la sección "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
@@ -30,7 +29,7 @@ Para obtener más información sobre la administración de debates, consulta la
 
 ## Acerca de las encuestas
 
-Puedes crear encuestas en la categoría de encuestas para medir el interés en las ideas nuevas y la dirección de los proyectos. Cualquiera con acceso de lectura en tu repositorio puede crear encuestas, votar en ellas y ver sus resultados. Los usuarios que hayan cerrado sesión pueden ver los resultados de las encuestas en los repositorios públicos.
+Puedes crear encuestas en la categoría de encuestas para medir el interés en las ideas nuevas y la dirección de los proyectos. Anyone with read access to your repository can create polls, vote in polls, and view their results.{% ifversion fpt or ghec %} Signed out users can view the results of polls in public repositories.{% endif %}
 
 Las encuestas requieren una pregunta y por lo menos dos opciones. Puedes agregar un máximo de ocho opciones y estas pueden contener un máximo de 128 caracteres.
 
@@ -71,5 +70,5 @@ Puedes compartir tu retroalimentación sobre los {% data variables.product.prodn
 - "[Acerca de escribir y dar formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)"
 - "[Buscar debates](/search-github/searching-on-github/searching-discussions)"
 - "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
-- "[Moderar comentarios y conversaciones](/communities/moderating-comments-and-conversations)"
-- "[Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"
+- "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)"{% ifversion fpt or ghec %}
+- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"{% endif %}
diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
index ec1f076818..1378836013 100644
--- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
+++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
@@ -4,8 +4,7 @@ shortTitle: Colaborar con los mantenedores
 intro: 'Puedes contribuir a las metas, planes, salud y comunidad de un proyecto en {% data variables.product.product_name %} si te comunicas con los mantenedores del proyecto en un debate.'
 permissions: 'People with read access to a repository can start and participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can start and participate in discussions and polls in the organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
@@ -53,4 +52,6 @@ Puedes buscar debates y filtrar la lista de estos en un repositorio u organizaci
 ## Leer más
 
 - "[Acerca de escribir y dar formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)"
+{%- ifversion fpt or ghec %}
 - "[Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"
+{%- endif %}
diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/index.md
index ddc777aef7..22e3e449da 100644
--- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/index.md
+++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/index.md
@@ -3,8 +3,7 @@ title: Colaborar con tu comunidad utilizando los debates
 shortTitle: Colaborar utilizando debates
 intro: Recopila y debate tu proyecto con los miembros de la comunidad y con otros mantenedores.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 children:
   - /about-discussions
   - /participating-in-a-discussion
diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index d97640f3e1..6b6c96c423 100644
--- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -3,8 +3,7 @@ title: Participar en un debate
 intro: 'Puedes conversar con la comunidad y con los mantenedores en un foro dentro del repositorio de un proyecto en {% data variables.product.product_name %}.'
 permissions: 'People with read access to a repository can participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can participate in discussions and polls in that organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Participa en un debate
 ---
 
@@ -15,7 +14,7 @@ shortTitle: Participa en un debate
 
 Adicionalmente a comenzar a ver los debates y encuestas, puedes comentar como respuesta al comentario original del autor de dicho debate. También puedes crear un hilo de comentarios si respondes a un comentario individual que otro miembro de la comunidad haya hecho dentro del debate, y reaccionar a los comentarios con emojis.
 
-Puedes bloquear usuarios y reportar el contenido perjudicial para mantener un ambiente placentero y seguro en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)".
+{% ifversion fpt or ghec %}You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)."{% endif %}
 
 ## Prerrequisitos
 
diff --git a/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md
index 8a88856db6..a358039e75 100644
--- a/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md
+++ b/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md
@@ -3,8 +3,7 @@ title: Best practices for community conversations on GitHub
 shortTitle: Best practices for community conversations
 intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to an issue when you are ready to scope out the work.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
@@ -22,7 +21,7 @@ For more information about opening an issue and cross-referencing a discussion,
 
 You can create and participate in discussions, issues, and pull requests, depending on the type of conversation you'd like to have.
 
-You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and develop a project's specific details before committing it to an issue, which can then be scoped. {% data variables.product.prodname_discussions %} is useful for teams if:
+You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and develop a project's specific details before committing it to an issue, which can then be scoped. {% data variables.product.prodname_discussions %} is useful for teams in a number of scenarios.
 - You are in the discovery phase of a project and are still learning which direction your team wants to go in
 - You want to collect feedback from a wider community about a project
 - You want to keep bug fixes, feature requests, and general conversations separate
@@ -34,7 +33,7 @@ Issues are useful for discussing specific details of a project such as bug repor
 
 ## Following contributing guidelines
 
-Before you open a discussion in an open source repository, check to see if the repository has contributing guidelines. The CONTRIBUTING file includes information about how the repository maintainer would like you to contribute ideas to the project.
+Before you open a discussion in a repository, check to see if the repository has contributing guidelines. The CONTRIBUTING file includes information about how the repository maintainer would like you to contribute ideas to the project.
 
 For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
 
diff --git a/translations/es-ES/content/discussions/guides/finding-your-discussions.md b/translations/es-ES/content/discussions/guides/finding-your-discussions.md
index 23808bf6e4..f1e0921c99 100644
--- a/translations/es-ES/content/discussions/guides/finding-your-discussions.md
+++ b/translations/es-ES/content/discussions/guides/finding-your-discussions.md
@@ -2,8 +2,7 @@
 title: Finding your discussions
 intro: You can easily access every discussion you've created or participated in.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Encontrar debates
 redirect_from:
   - /discussions/guides/finding-discussions-across-multiple-repositories
@@ -12,8 +11,7 @@ redirect_from:
 
 ## Encontrar debates
 
-1. Ve a {% data variables.product.prodname_dotcom_the_website %}.
-1. En la esquina superior derecha de {% data variables.product.prodname_dotcom_the_website %}, da clic en tu foto de perfil y luego en **Tus debates**. !["Tus debates" en el menú desplegable de la foto de perfil en {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png)
+1. En la esquina superior derecha de {% data variables.product.product_location %}, da clic en tu foto de perfil y luego en **Tus debates**. !["Tus debates" en el menú desplegable de la foto de perfil en {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png)
 1. Alterna entre **Creados** y **Comentados** para ver los debates que creaste o en los que has participado.
 
 ## Leer más
diff --git a/translations/es-ES/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/es-ES/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
index 1bff73165e..1d9b4f3e54 100644
--- a/translations/es-ES/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
+++ b/translations/es-ES/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
@@ -2,8 +2,7 @@
 title: Otorgar permisos superiores a los contribuyentes principales
 intro: Los administradores de repositorio pueden promover a cualquier miembro de la comunidad para que sea un moderador o un mantenedor.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Otorgar permisos mayores
 ---
 
@@ -16,11 +15,11 @@ Los colaboradores más útiles en los últimos 30 días se resaltarán en el tab
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
-1. Compare la lista de contribuyentes con sus permisos de acceso al repositorio o, para los debates de organización, al repositorio origen para ver quién califica para moderarlos.
+1. Compare the list of contributors with their access permissions to the repository or, for organization discussions, to the source repository to see who qualifies to moderate the discussion. ![Screenshot of most helpful contributors](/assets/images/help/discussions/most-helpful.png)
 
 ## Paso 2: Revisa los niveles de permiso de los {% data variables.product.prodname_discussions %}
 
-Las personas con permisos de clasificación en un repositorio pueden ayudar a moderar los debates de este al marcar los comentarios como respuestas, bloquear los debates que ya no sean útiles o que estén dañando a la comunidad y convertir las propuestas en debates cuando alguna idea aún se encuentre en las primeras etapas de desarrollo. De forma similar, las personas con permisos de clasificación en el repositorio origen para los debates de organización pueden moderar dichos debates. Para obtener más información, consulta la sección "[Moderar los debates](/discussions/managing-discussions-for-your-community/moderating-discussions)".
+People with triage permissions for a repository can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. De forma similar, las personas con permisos de clasificación en el repositorio origen para los debates de organización pueden moderar dichos debates. Para obtener más información, consulta la sección "[Moderar los debates](/discussions/managing-discussions-for-your-community/moderating-discussions)".
 
 Para obtener más información sobre los niveles de permiso y los {% data variables.product.prodname_discussions %} de un repositorio, consulta la sección "[Niveles de permiso de un repositorio en una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)".
 
diff --git a/translations/es-ES/content/discussions/guides/index.md b/translations/es-ES/content/discussions/guides/index.md
index 7dad98131f..f8dbce5539 100644
--- a/translations/es-ES/content/discussions/guides/index.md
+++ b/translations/es-ES/content/discussions/guides/index.md
@@ -3,8 +3,7 @@ title: Guías de los debates
 shortTitle: Guías
 intro: Descubre las trayectorias para iniciar o aprende las mejores prácticas para participar o monitorear los debates de tu comunidad.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 children:
   - /best-practices-for-community-conversations-on-github
   - /finding-your-discussions
diff --git a/translations/es-ES/content/discussions/index.md b/translations/es-ES/content/discussions/index.md
index feb1df7a42..817f73eab1 100644
--- a/translations/es-ES/content/discussions/index.md
+++ b/translations/es-ES/content/discussions/index.md
@@ -1,7 +1,7 @@
 ---
 title: GitHub Discussions Documentation
 shortTitle: GitHub Discussions
-intro: '{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source project. Community members can ask and answer questions, share updates, have open-ended conversations, and follow along on decisions affecting the community''s way of working.'
+intro: '{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an{% ifversion fpt or ghec %} open source or{% endif %} internal project. Community members can ask and answer questions, share updates, have open-ended conversations, and follow along on decisions affecting the community''s way of working.'
 introLinks:
   quickstart: /discussions/quickstart
 featuredLinks:
@@ -27,8 +27,7 @@ examples_source: data/product-examples/discussions/community-examples.yml
 product_video: 'https://www.youtube-nocookie.com/embed/IpBw2SJkFyk'
 layout: product-landing
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 communityRedirect:
   name: Provide GitHub Feedback
   href: 'https://github.com/github/feedback/discussions/categories/discussions-feedback'
diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md
index acf3c13816..e0b2c3651a 100644
--- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md
@@ -3,8 +3,7 @@ title: Administrar los debates para tu comunidad
 shortTitle: Administrar los debates
 intro: 'Puedes habilitar y configurar los {% data variables.product.prodname_discussions %} en tu repositorio y puedes utilizar herramientas en {% data variables.product.product_name %} para moderar conversaciones entre los miembros de la comunidad.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 children:
   - /managing-discussions
   - /managing-categories-for-discussions
diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
index a6c8bbf306..122c96066c 100644
--- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
+++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
@@ -3,8 +3,7 @@ title: Managing categories for discussions
 intro: 'You can categorize discussions to organize conversations for your community members, and you can choose a format for each category.'
 permissions: Repository administrators and people with write or greater access to a repository can manage categories for discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage categories for discussions in the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Administrar las categorías
 redirect_from:
   - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository
@@ -32,7 +31,7 @@ Cada categoría debe tener un nombre único y un emoji distintivo, y se le puede
 
 ## Crear una categoría
 
-1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to create a category.
+1. En {% data variables.product.product_location %}, navega a la página principal del repositorio u organización en donde quieres crear una categoría.
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.edit-categories %}
 1. Da clic en **Categoría nueva**. ![Botón de "Categoría nueva" sobre la lista de categorías de debate para un repositorio](/assets/images/help/discussions/click-new-category-button.png)
@@ -43,7 +42,7 @@ Cada categoría debe tener un nombre único y un emoji distintivo, y se le puede
 
 Puedes editar una categoría para cambiar el emoji, título, descripción y formato de debate de la misma.
 
-1. En {% data variables.product.product_location %}, navega a la página principal del repositorio u organización en donde quieres crear una categoría.
+1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to edit a category.
 {% data reusables.discussions.discussions-tab %}
 1. A la derecha de la categoría en la lista, da clic en {% octicon "pencil" aria-label="The pencil icon" %}. ![Botón de editar a la derecha de la categoría en la lista de categorías de un repositorio](/assets/images/help/discussions/click-edit-for-category.png)
 1. {% data reusables.discussions.edit-category-details %}
@@ -54,7 +53,7 @@ Puedes editar una categoría para cambiar el emoji, título, descripción y form
 
 Cuando borras una categoría, {% data variables.product.product_name %} enviará todos los debates en la categoría que se borró a una categoría existente que elijas.
 
-1. En {% data variables.product.product_location %}, navega a la página principal del repositorio u organización en donde quieres crear una categoría.
+1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to delete a category.
 {% data reusables.discussions.discussions-tab %}
 1. A la derecha de la categoría en la lista, da clic en {% octicon "trash" aria-label="The trash icon" %}. ![Botón de cesto de basura a la derecha de la categoría en la lista de categorías de un repositorio](/assets/images/help/discussions/click-delete-for-category.png)
 1. Utiliza el menú desplegable y elige una categoría nueva para cualquier debate en la categoría que estás eliminando. ![Menú desplegable para elegir una categoría nueva cuando se borra una categoría existente](/assets/images/help/discussions/choose-new-category.png)
diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md
index 143caba10e..efa57aa20d 100644
--- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md
+++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -3,8 +3,7 @@ title: Administrar los debates
 intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
 permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Administrar los debates
 redirect_from:
   - /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
@@ -17,7 +16,7 @@ redirect_from:
 
 Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. Para obtener más información, consulta la sección "[Administrar la creación de debates para los repositorios de tu organización](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)".
 
-Como mantenedor de debates, puedes crear recursos comunitarios para impulsar los debates que se alinien con la meta general del proyecto y mantener así un foro abierto y amistoso para los colaboradores. El crear un código de conducta o lineamientos de contribución para que los colaboradores los sigan te ayudará a proporcionar un foro colaborativo y productivo. Para obtener más información sobre cómo crear recursos comunitarios, consulta las secciones "[Agregar un código de conducta a tu proyecto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" y "[Configurar los lineamientos para los contribuyentes de un repositorio](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)".
+Como mantenedor de debates, puedes crear recursos comunitarios para impulsar los debates que se alinien con la meta general del proyecto y mantener así un foro abierto y amistoso para los colaboradores. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and{% endif %} "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
 
 Cuando un debate produce una idea o error que está listo para solucionarse, puedes crear una propuesta nueva desde un debate. Para obtener más información, consulta la sección "[Crear una propuesta](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)".
 
@@ -29,11 +28,11 @@ Para obtener más información sobre cómo proporcionar un debate sano, consulta
 
 Para administrar los debates en un repositorio, debes habilitar los {% data variables.product.prodname_discussions %} en este. Para obtener más información, consulta la sección "[Habilitar o inhabilitar los {% data variables.product.prodname_discussions %} para un repositorio](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)".
 
-To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. Para obtener más información, consulta la sección "[Habilitar o inhabilitar los {% data variables.product.prodname_discussions %} para una organización](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)".
 
 ## Cambiar la categoría de un debate
 
-Puedes categorizar los debates para ayudar a que los miembros de la comunidad encuentren aquellos que tengan alguna relación. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+Puedes categorizar los debates para ayudar a que los miembros de la comunidad encuentren aquellos que tengan alguna relación. Para obtener más información, consulta la sección "[Administrar las categorías de los debates](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)".
 
 También puedes migrar un debate a una categoría diferente. It's not possible to move a discussion to or from the polls category.
 
@@ -75,7 +74,7 @@ Editar un debate que se ha fijado no cambiará la categoría del mismo. Para obt
 
 ## Transferir un debate
 
-Para transferir un debate, debes tener permisos para crear debates en el repositorio a donde quieras trasnferirlo. If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. Solo puedes transferir debates entre los repositorios que pertenezcan a la misma cuenta de organización o de usuario. No puedes transferir un debate desde un repositorio privado hacia uno público.
+Para transferir un debate, debes tener permisos para crear debates en el repositorio a donde quieras trasnferirlo. If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. Solo puedes transferir debates entre los repositorios que pertenezcan a la misma cuenta de organización o de usuario. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository.
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
index bc3b88968d..7c892d87e3 100644
--- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
+++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
@@ -1,16 +1,15 @@
 ---
 title: Moderar los debates
-intro: 'Puedes promover una colaboración sana si marcas los comentarios como respuestas, bloqueando y desbloqueando debates, convirtiendo propuestas en debates y editando o borrando los comentarios, debates y categorías que no se alineen con el código de conducta de tu comunidad.'
+intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.'
 permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
 ## Acerca de moderar los debates
 
-{% data reusables.discussions.about-discussions %} Si tienes permisos de clasificación para un repositorio, puedes ayudar a moderar los debates de este marcando los comentarios como respuestas, bloqueando debates que ya no sean útiles o que dañen a la comunidad y convirtiendo las propuestas en debates cuando una idea aún está en las etapas tempranas de desarrollo. De forma similar, si tienes permisos de clasificación para el repositorio origen para los debates de la organización, puedes moderarlos en esta.
+{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. De forma similar, si tienes permisos de clasificación para el repositorio origen para los debates de la organización, puedes moderarlos en esta.
 
 ## Marcar un comentario como una respuesta
 
diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
index ce8bce92b1..64144d88b2 100644
--- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
+++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
@@ -3,8 +3,7 @@ title: Ver las perspectivas de tus debates
 intro: 'Las perspectivas de los debates proporcionan datos de la actividad, vistas y contribuciones de los mismos.'
 permissions: Repository administrators and people with maintain access to a repository can view the insights dashboard for discussions in that repository. Repository administrators and people with maintain access to the source repository for organization discussions can view the insights dashboard for discussions in that organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Discussions
 shortTitle: Ver las perspectivas de los debates
diff --git a/translations/es-ES/content/discussions/quickstart.md b/translations/es-ES/content/discussions/quickstart.md
index 7dc934485f..3e783568fe 100644
--- a/translations/es-ES/content/discussions/quickstart.md
+++ b/translations/es-ES/content/discussions/quickstart.md
@@ -3,21 +3,20 @@ title: Guía de inicio rápido para los debates de GitHub
 intro: 'Habilita los {% data variables.product.prodname_discussions %} en un repositorio u organización e inicia conversaciones con tu comunidad.'
 allowTitleToDifferFromFilename: true
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Inicio Rápido
 ---
 
 
 ## Introducción
 
-{% data variables.product.prodname_discussions %} es un foro de comunicación colaborativa para la comunidad que circunda un proyecto de código abierto. Los debates existen para las conversaciones que necesitan ser transparentes y accesibles pero no necesitan rastrearse en un tablero de proyecto y no se relacionan con el código, a diferencia de los {% data variables.product.prodname_github_issues %}. Los debates habilitan las conversaciones abiertas y fluídas en un foro público.
+{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source or internal project. Los debates existen para las conversaciones que necesitan ser transparentes y accesibles pero no necesitan rastrearse en un tablero de proyecto y no se relacionan con el código, a diferencia de los {% data variables.product.prodname_github_issues %}. Los debates habilitan las conversaciones abiertas y fluídas en un foro público.
 
 Los debates proporcionan un espacio para que existan conversaciones colaborativas al conectar y asignar un área más centralizada para conectarse y encontrar información.
 
 ## Habilitar los {% data variables.product.prodname_discussions %} en tu repositorio
 
-Los propietarios de los repositorios y las personas con acceso de escritura pueden habilitar los {% data variables.product.prodname_discussions %} para una comunidad en sus repositorios privados o públicos.
+Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public{% ifversion ghes > 3.5 %}, internal{% endif %} and private repositories. The visibility of a discussion is inherited from the repository the discussion is created in.
 
 Cuando habilitas los {% data variables.product.prodname_discussions %} por primera vez, se te invitará a configurar una publicación de bienvenida.
 
@@ -42,7 +41,7 @@ Puedes darles la bienvenida a tu comunidad y presentarles una forma nueva de com
 
 ## Configurar los lineamientos comunitarios para los contribuyentes
 
-En el caso de los debates de repositorio, puedes configurar lineamientos de contribución para fomentar que los colaboradores tengan conversaciones útiles y significativas que sean relevantes para el repositorio. También puedes actualizar el archivo de README del repositorio para comunicar tus expectativas de cuándo deberían los colaboradores abrir una propuesta o un debate. Para obtener más información sobre proporcionar lineamientos para tu proyecto, consulta las secciones "[Agregar un código de conducta a tu proyecto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" y "[Configurar tu proyecto para que tegan contribuciones sanas](/communities/setting-up-your-project-for-healthy-contributions)".
+En el caso de los debates de repositorio, puedes configurar lineamientos de contribución para fomentar que los colaboradores tengan conversaciones útiles y significativas que sean relevantes para el repositorio. También puedes actualizar el archivo de README del repositorio para comunicar tus expectativas de cuándo deberían los colaboradores abrir una propuesta o un debate. For more information about providing guidelines for your project, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and{% endif %} "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
 
 Para el caso de los debates, puedes compartir información sobre cómo participar en tu organización al crear un README de perfil para ella. 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)".
 
@@ -62,7 +61,7 @@ Cualquier usuario no autenticado que pueda ver un repositorio podrá crear una e
 
 Los propietarios de los repositorios y las personas con acceso de escritura en estos pueden crear categorías nuevas para mantener los debates organizados. De la misma manera, ya que los debates de las organizaciones se basan en un repositorio origen, los propietarios de los repositorios y las personas con acceso de escritura con acceso de escritura en el repositorio origen pueden crear categorías nuevas para estos debates.
 
-Los colaboradores que participen y creen debates nuevos pueden agruparlos en las categorías existentes más relevantes. Los debates también pueden volver a categorizarse después de su creación. Para obtener más información, consulta la sección "[Administrar las categorías de los debates](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)".
+Collaborators participating in and creating new discussions can group discussions into the most relevant existing categories. Los debates también pueden volver a categorizarse después de su creación. Para obtener más información, consulta la sección "[Administrar las categorías de los debates](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)".
 
 {% data reusables.discussions.you-can-label-discussions %}
 
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md
index 4d286ac1a8..107648719a 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md
@@ -20,7 +20,7 @@ For assignments with complex setup environments, teachers can customize the dev
 
 {% note %}
 
-**Note**: Individual codespaces are automatically deleted if they are stopped and left unused for a prolonged period. For more information, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
+**Note**: Individual codespaces are automatically deleted if they are stopped and left unused for a prolonged period. Para obtener más información, consulta la sección "[Configurar el borrado automático de tus codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)".
 
 {% endnote %}
 
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 e489674246..1f79859fa4 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
@@ -136,7 +136,7 @@ Las notificaciones proporcionan actualizaciones sobre la actividad en {% data va
 ### 8. Trabajar con {% data variables.product.prodname_pages %}
 Puedes utilizar {% data variables.product.prodname_pages %} para crear y hospedar un sitio web directamente desde un repositorio de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)".
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 ### 9. Uso de {% data variables.product.prodname_discussions %}
 Puedes habilitar los {% data variables.product.prodname_discussions %} en tu repositorio para ayudar a crear una comunidad al rededor de tu proyecto. Los mantenedores, contribuyentes y visitantes pueden utilizar los debates para compartir anuncios, hacer y responder preguntas y participar en conversaciones sobre las metas. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
 {% endif %}
diff --git a/translations/es-ES/content/get-started/quickstart/communicating-on-github.md b/translations/es-ES/content/get-started/quickstart/communicating-on-github.md
index 30cfaa7b24..7b1d06033e 100644
--- a/translations/es-ES/content/get-started/quickstart/communicating-on-github.md
+++ b/translations/es-ES/content/get-started/quickstart/communicating-on-github.md
@@ -24,10 +24,9 @@ topics:
 
 {% data variables.product.product_name %} proporciona herramientas de comunicación colaborativas que te permiten interactuar de cerca con tu comunidad. Esta guía de inicio rápido te mostrará cómo escoger la herramienta correcta para tus necesidades.
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 Puedes crear y participar en propuestas, solicitudes de cambios, {% data variables.product.prodname_discussions %} y debates de equipo, dependiendo del tipo de conversación que te gustaría tener.
-{% endif %}
-{% ifversion ghes or ghae %}
+{% else %}
 Puedes crear y participar de propuestas, solicitudes de extracción y debates de equipos, dependiendo del tipo de conversación que quieras tener.
 {% endif %}
 
@@ -100,7 +99,7 @@ La pestaña **Archivos que cambiaron** de la solicitud de cambios muestra la sol
 - El usuario crea una solicitud de cambios con la solución.
 - Un mantenedor de repositorio revisa la solicitud de cambios, la comenta y la fusiona.
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 ### Casos para los {% data variables.product.prodname_discussions %}
 
 - Tengo una pregunta que no se relaciona necesariamente con los archivos específicos del repositorio.
@@ -145,10 +144,10 @@ Estos ejemplos te muestran cómo decidir cuál es la mejor herramienta para tus
 
 Para las propuestas, por ejemplo, puedes etiquetarlas con etiquetas para buscarlas más rápidamente y crear plantillas de propuesta para ayudar a los contribuyentes a abrir propuestas significativas. Para obtener más información, consulta la sección "[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues#working-with-issues)" y "[Acerca de las plantillas de propuestas y solicitudes de cambio](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)".
 
-Para las solicitudes de cambio, puedes crear borradores de estas si los cambios que propones aún están en curso. Los borradores de solicitudes de cambios no pueden fusionarse hasta que se marquen como listos para revisión. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)."
+Para las solicitudes de cambio, puedes crear borradores de estas si los cambios que propones aún están en curso. Los borradores de solicitudes de cambios no pueden fusionarse hasta que se marquen como listos para revisión. Para obtener más información, consulta la sección "[Acerca de las solicitudes de cambios](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)".
 
-{% ifversion fpt or ghec %}
-Para el caso de los {% data variables.product.prodname_discussions %}, puedes configurar un código de conducta y fijar los debates que contengan información importante de tu comunidad. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
+{% ifversion discussions %}
+For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt or ghec %} set up a code of conduct and{% endif %} pin discussions that contain important information for your community. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
 {% endif %}
 
 Para el caso de los debates de equipo, puedes editarlos o borrarlos en la página del equipo y puedes configurar las notificaciones para estos. Para obtener más información, consulta [Acerca de los debates del equipo](/organizations/collaborating-with-your-team/about-team-discussions)".
diff --git a/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md b/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md
index 7340b142cf..cf773a630a 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
@@ -43,7 +43,7 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
 |<kbd>G</kbd> <kbd>P</kbd> | Go to the **Pull requests** tab. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
 |<kbd>G</kbd> <kbd>A</kbd> | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %}
 |<kbd>G</kbd> <kbd>B</kbd> | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)."
-|<kbd>G</kbd> <kbd>W</kbd> | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %}
+|<kbd>G</kbd> <kbd>W</kbd> | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion discussions %}
 |<kbd>G</kbd> <kbd>G</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
 
 ## Source code editing
diff --git a/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md
index 8502bc9ab8..a0b5e7d6f9 100644
--- a/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md
+++ b/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -2,8 +2,7 @@
 title: Utilizar la API de GraphQL para los debates
 intro: 'Aprende a utilizar la API de GraphQL de los {% data variables.product.prodname_discussions %}.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Utilizar GraphQL para los debates
 ---
 
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md
index aa93f1927e..d5d112fa1b 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -48,7 +48,8 @@ Para ayudar a que los colaboradores abran propuestas significativas que proporci
 
 Puedes @mencionar colaboradores que tengan acceso a tu repositorio en una propuesta para dirigir su atención a un cometnario. Para enlazar las propuestas relacionadas en el mismo repositorio, puedes teclear `#` seguido de parte del título de la propuesta y luego hacer clic en la propueta que quieras enlazar. Para comunicar la responsabilidad, puedes asignar propuestas. Si frecuentemente te encuentras tecleando el mismo comentario, puedes utilizar las respuestas guardadas.
 {% ifversion fpt or ghec %} Para obtener más información, consulta las secciones "[Sintaxis básica para escritura y formato](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)" y "[Asignar propuestas y solicitudes de cambio a otros usuarios de GitHub](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)".
-
+{% endif %}
+{% ifversion discussions %}
 ## Comparar propuestas y debates
 
 Algunas conversaciones son más adecuadas para los {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} Para orientarte sobre cuándo utilizar una propuesta o debate, consulta la sección "[Comuinicarte en GitHub](/github/getting-started-with-github/quickstart/communicating-on-github)".
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index ae88b7642f..9f37c4d124 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -99,7 +99,7 @@ You can open a new issue from a specific line or lines of code in a file or pull
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 
 ## Creating an issue from discussion
 
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 9dae7b0195..8d550324ce 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
@@ -818,4 +818,6 @@ Para obtener más información, consulta la sección "[Administrar la publicaci
 ## Leer más
 
 - "[Mantener tu organización segura](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %}
+{%- ifversion fpt or ghec %}
 - "[Exportar la información de miembro para tu organización](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
+{%- endif %}
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
index 73b01a362f..9017551439 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
@@ -134,7 +134,7 @@ Some of the features listed below are limited to organizations using {% data var
 | [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** |
 | [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %}
 | Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %}
-| Create autolink references to external resources, like Jira or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt or ghec %}
+| Create autolink references to external resources, like Jira or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion discussions %}
 | [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** |
 | [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** |
 | [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** |
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
index 2d0462cebf..3b91834c36 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
@@ -3,8 +3,7 @@ title: Enabling or disabling GitHub Discussions for an organization
 intro: 'You can use {% data variables.product.prodname_discussions %} in a organization as a place for your organization to have conversations that aren''t specific to a single repository within your organization.'
 permissions: 'Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Organizations
 shortTitle: Debates de organización
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/index.md b/translations/es-ES/content/organizations/managing-organization-settings/index.md
index 2e5f8cd0e2..b875dc951a 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/index.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/index.md
@@ -27,6 +27,7 @@ children:
   - /allowing-people-to-delete-issues-in-your-organization
   - /enabling-or-disabling-github-discussions-for-an-organization
   - /managing-discussion-creation-for-repositories-in-your-organization
+  - /managing-the-commit-signoff-policy-for-your-organization
   - /setting-team-creation-permissions-in-your-organization
   - /managing-scheduled-reminders-for-your-organization
   - /managing-the-default-branch-name-for-repositories-in-your-organization
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index 3f9a838fd9..d8ccd6e141 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -5,8 +5,7 @@ redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization
 permissions: Organization owners can manage discussion creation for repositories owned by the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Organizations
   - Teams
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
new file mode 100644
index 0000000000..66928608d1
--- /dev/null
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
@@ -0,0 +1,25 @@
+---
+title: Managing the commit signoff policy for your organization
+intro: 'You can require users to automatically sign off all commits they make in {% data variables.product.product_name %}''s web interface to repositories owned by your organization.'
+versions:
+  feature: commit-signoffs
+permissions: Organization owners can require all commits to repositories owned by the organization be signed off by the commit author.
+topics:
+  - Organizations
+shortTitle: Manage the commit signoff policy
+---
+
+## About commit signoffs
+
+To affirm that a commit complies with the rules and licensing governing a repository, many organizations require developers to sign off on every commit. If your organization requires commit signoffs, you can make signing off a seamless part of the commit process by enabling compulsory commit signoffs for users committing through {% data variables.product.product_name %}'s web interface. After you enable compulsory commit signoffs for an organization, every commit made to repositories in that organization through {% data variables.product.product_name %}'s web interface will automatically be signed off on by the commit author.
+
+People with admin access to a repository can also enable compulsory commit signoffs at the repository level. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
+{% data reusables.repositories.commit-signoffs %}
+
+## Managing compulsory commit signoffs for your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.repository-defaults %}
+1. Select or deselect **Require contributors to sign off on web-based commits**. ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/organizations/require-signoffs.png)
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index ee9196524b..c6217d52e1 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -22,6 +22,9 @@ Los propietarios de la organización pueden administrar la visualización de los
 
 Cada miembro de la organización elige su propio nombre de perfil en sus configuraciones. Para obtener más información, consulta la sección "[Personalizar tu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)."
 
+{% ifversion profile-name-enterprise-setting %}
+You may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)".{% endif %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
index 586acb6af8..8a123551a6 100644
--- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
+++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -49,7 +49,7 @@ After choosing an inherited role, you can select additional permissions for your
 
 You can only choose an additional permission if it's not already included in the inherited role. For example, if the inherited role offers **Write** access to a repository, then the "Close a pull request" permission will already be included in the inherited role.
 
-{% ifversion ghec %}
+{% ifversion discussions %}
 ### Discussions
 
 - **Create a discussion category**: Ability to create a new discussion category. For more information, see "[Creating a new discussion category](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)".
diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md
index acba6e6df0..c50b182c9a 100644
--- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Managing moderators in your organization
-intro: 'You can give an individual or team in your organization the ability to block and limit access, by assigning them to the moderator role.'
+title: Administrar moderadores en tu organización
+intro: Puedes proporcionar a un individuo o equipo de tu organización la capacidad de bloquear y limitar el acceso si les asignas el rol de moderador.
 permissions: Organization owners can assign the moderator role.
 versions:
   fpt: '*'
@@ -9,10 +9,10 @@ topics:
   - Organizations
   - Teams
   - Community
-shortTitle: Managing moderators
+shortTitle: Administrar moderadores
 ---
 
-## About organization moderators
+## Acerca de los moderadores de las organizaciones
 
 Algunas veces es necesario bloquear a un contribuyente o configurar los límites de interacción de tu organización o para los repositorios individuales. Como propietario de organización, puedes llevar a cabo estas tareas, pero podrías necesitar delegar estas tareas a otros miembros de tu organización. Puedes hacer esto asignando el rol de moderador a un miembro de la organización o a un equipo.
 
diff --git a/translations/es-ES/content/packages/index.md b/translations/es-ES/content/packages/index.md
index 495a8e992d..a486e6d606 100644
--- a/translations/es-ES/content/packages/index.md
+++ b/translations/es-ES/content/packages/index.md
@@ -12,10 +12,11 @@ featuredLinks:
     - /packages/learn-github-packages/installing-a-package
   popular:
     - /packages/working-with-a-github-packages-registry/working-with-the-npm-registry
-    - '{% ifversion fpt or ghec or ghes > 3.4 %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}'
+    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
     - /packages/learn-github-packages
     - /packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry
   guideCards:
+    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
     - '{% ifversion fpt or ghec or ghes > 3.4 %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}'
     - /packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry
 changelog:
diff --git a/translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
index 507071754a..9a7c035065 100644
--- a/translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
+++ b/translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -16,7 +16,7 @@ shortTitle: Visibilidad & control de accesos
 
 Los paquetes con permisos granulares tienen un alcance de una cuenta personal o de organización. Puedes cambiar la visibilidad y el control de accesos de un paquete por separado desde el repositorio al cual está conectado (o enlazado).
 
-Actualmente, solo puedes utilizar permisos granulares con el {% data variables.product.prodname_container_registry %}. Los permisos granulares no son compatibles en nuestros otros registros de paquetes, tales como el registro de npm.
+Actualmente, solo puedes utilizar permisos granulares con el {% data variables.product.prodname_container_registry %}. Granular permissions are not supported in our other package registries, such as the npm registry.{% ifversion docker-ghcr-enterprise-migration %} For more information about migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."{% endif %}
 
 Para obtener más información sobre los permisos de los paquetes con alcance de repositorio, los alcances relacionados con paquetes para los PAT o para administrar permisos para los flujos de trabajo de tus acciones, consulta la sección "[Acerca de los permisos para los Paquetes de GitHub](/packages/learn-github-packages/about-permissions-for-github-packages)".
 
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
index a5b06828ca..f86f160f8a 100644
--- a/translations/es-ES/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -1,6 +1,6 @@
 ---
 title: Migrarse al registro del contenedor desde el registro de Docker
-intro: 'Las imágenes de Docker que se almacenaron previamente en el registro de Docker se están migrando automáticamente al {% data variables.product.prodname_container_registry %}.'
+intro: '{% ifversion docker-ghcr-enterprise-migration %}An enterprise owner can{% else %}{% data variables.product.company_short %} will{% endif %} migrate Docker images previously stored in the Docker registry on {% data variables.product.product_location %} to the {% data variables.product.prodname_container_registry %}.'
 product: '{% data reusables.gated-features.packages %}'
 redirect_from:
   - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
@@ -9,35 +9,61 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Migrarse al registro de contenedores
+  feature: docker-ghcr-enterprise-migration
+shortTitle: Migration to Container registry
+topics:
+  - Containers
+  - Docker
+  - Migration
 ---
 
-El registro de Docker de {% data variables.product.prodname_dotcom %} se ha reemplazado con el {% data variables.product.prodname_container_registry %}. Si almacenaste imágenes de Docker en el registro de Docker, se migrarán automáticamente al {% data variables.product.prodname_container_registry %}. No necesitas hacer nada. Cualquier script o flujo de trabajo de {% data variables.product.prodname_actions %} que utilice el designador de nombre para el registro de Docker (`docker.pkg.github.com`) seguirá funcionando después de la migración al {% data variables.product.prodname_container_registry %} (`ghcr.io`).
+{% data reusables.package_registry.container-registry-ghes-beta %}
 
-La migración se está llevando a cabo gradualmente, en vez de hacerla toda al unísono. Si aún no se migraron tus imágenes, llegaremos a ellas pronto.
+## Acerca de {% data variables.product.prodname_container_registry %}
 
-## ¿Cómo puedes saber si ya se migraron tus imágenes?
+{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
 
-Después de que migraste las imágenes al {% data variables.product.prodname_container_registry %}, verás los siguientes cambios en la página de detalles de un paquete:
+## About migration from the Docker registry
 
-* El icono ahora es el logo del {% data variables.product.prodname_container_registry %}, previamente, era un logo de Docker.
-* El dominio en la URL de extracción ahora es `ghcr.io`, anteriormente, fue `docker.pkg.github.com`.
+{% data reusables.package_registry.container-registry-replaces-docker-registry %} If you've stored Docker images in the Docker registry, {% ifversion docker-ghcr-enterprise-migration %}an enterprise owner{% else %}{% data variables.product.company_short %}{% endif %} will gradually migrate the images to the {% data variables.product.prodname_container_registry %}. No action is required on your part.
 
-![Página de detalles del {% data variables.product.prodname_container_registry %}](/assets/images/help/package-registry/container-registry-details-page.png)
+{% ifversion docker-ghcr-enterprise-migration %}
 
-## Diferencias clave entre el {% data variables.product.prodname_container_registry %} y el registro de Docker
+{% note %}
 
-El {% data variables.product.prodname_container_registry %} se optimiza para ser compatible con algunas de las necesidades únicas de los contenedores.
+**Note**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
 
-Con el {% data variables.product.prodname_container_registry %} puedes:
-- Almacena las imágenes de contenedor dentro de cuenta personal y de organización o conéctalas a un repositorio.
-- Elige si quieres heredar permisos desde un repositorio o si quieres configurar permisos granulares independientemente de un repositorio.
-- Acceder a imágenes de contenedores públicos anónimamente.
+{% endnote %}
 
-### Consultas a la API para detalles de las imágenes de Docker
+{% endif %}
 
-Después de la migración, ya no podrás utilizar la API de GraphQL para consultar los paquetes del `PackageType` "DOCKER". En vez de esto, puedes utilizar la API de REST para consultar los paquetes con el `package_type` "container". Para obtener más información, consulta el artículo "[Packages](/rest/reference/packages)" de la API de REST.
+After a Docker image has been migrated to the {% data variables.product.prodname_container_registry %}, you'll see the following changes to the details for the package.
 
-## Facturación
+- The icon will be the {% data variables.product.prodname_container_registry %} logo instead of the Docker logo.
+- The domain in the pull URL will be {% data variables.product.prodname_container_registry_namespace %} instead of {% data variables.product.prodname_docker_registry_namespace %}.
 
-Para obtener más información sobre la facturación del {% data variables.product.prodname_container_registry %}, consulta la sección "[Acerca de la facturación para el {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)".
+{% ifversion fpt or ghec %}
+
+![Screenshot of a Docker image migrated to the {% data variables.product.prodname_container_registry %}](/assets/images/help/package-registry/container-registry-details-page.png)
+
+{% endif %}
+
+{% data reusables.package_registry.container-registry-migration-namespaces %}
+
+{% ifversion fpt or ghec %}
+
+After migration, you'll no longer be able to use the GraphQL API to query for packages with a `PackageType` of "DOCKER". Instead, you can use the REST API to query for packages with a `package_type` of "container". For more information, see "[Packages](/rest/reference/packages)" in the REST API documentation.
+
+## Acerca de la facturación para {% data variables.product.prodname_container_registry %}
+
+For more information about billing for the {% data variables.product.prodname_container_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+
+{% endif %}
+
+{% ifversion docker-ghcr-enterprise-migration %}
+
+## Leer más
+
+- "[Migrating your enterprise to the {% data variables.product.prodname_container_registry %} from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)"
+
+{% endif %}
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
index a1989efc54..482e118420 100644
--- a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -19,19 +19,18 @@ versions:
 shortTitle: Registro de contenedores
 ---
 
-{% ifversion ghes > 3.4 %}
-{% note %}
+{% data reusables.package_registry.container-registry-ghes-beta %}
 
-**Nota:**: {% data variables.product.prodname_container_registry %} se encuentra actualmente en beta para {% data variables.product.product_name %} y está sujeto a cambios.
+## Acerca de {% data variables.product.prodname_container_registry %}
 
-{% endnote %}
-{% endif %}
+{% data reusables.package_registry.container-registry-benefits %}
 
 {% ifversion ghes > 3.4 %}
-## Prerrequisitos
 
-Para configurar y utilizar el {% data variables.product.prodname_container_registry %} en {% data variables.product.prodname_ghe_server %}, tu administrador de sitio primero debe habilitar el {% data variables.product.prodname_registry %} **y** el aislamiento de subdominios. Para obtener más información, consulta las secciones "[Iniciar con GitHub Packages para tu empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" y "[Habilitar el aislamiento de subdominios](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)".
+To use the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, your site administrator must first configure {% data variables.product.prodname_registry %} for your instance **and** enable subdomain isolation. Para obtener más información, consulta las secciones "[Iniciar con GitHub Packages para tu empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" y "[Habilitar el aislamiento de subdominios](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)".
+
 {% endif %}
+
 ## Acerca del soporte para el {% data variables.product.prodname_container_registry %}
 
 El {% data variables.product.prodname_container_registry %} es actualmente compatible con los siguientes formatos de contenedores de imagen:
diff --git a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
index 91eb2e5b3c..f0b3fe8f25 100644
--- a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
+++ b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
@@ -17,6 +17,9 @@ versions:
 
 {% data reusables.commits.about-commits %}
 
+{% ifversion commit-signoffs %}
+If the repository you are committing to has compulsory commit signoffs enabled, and you are committing via the web interface, you will automatically sign off on the commit as part of the commit process. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)." {% endif %}
+
 You can add a co-author on any commits you collaborate on. For more information, see "[Creating a commit with multiple authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)."
 
 {% ifversion fpt or ghec %}
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
index 6256d9253a..5c0d0ad309 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
@@ -1,11 +1,9 @@
 ---
 title: Habilita o inhabilita los debates de GitHub para un repositorio
 intro: 'Puedes utilizar los {% data variables.product.prodname_discussions %} en un repositorio como un lugar para que tu comunidad tenga conversaciones, haga preguntas y publique respuestas sin dimensionar el trabajo en una propuesta.'
-product: '{% data reusables.gated-features.discussions %}'
 permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_discussions %} for the repository.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Repositories
 redirect_from:
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
index a364ef9e68..22d5f3d484 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
@@ -13,6 +13,7 @@ children:
   - /managing-teams-and-people-with-access-to-your-repository
   - /managing-the-forking-policy-for-your-repository
   - /managing-pull-request-reviews-in-your-repository
+  - /managing-the-commit-signoff-policy-for-your-repository
   - /managing-git-lfs-objects-in-archives-of-your-repository
   - /enabling-anonymous-git-read-access-for-a-repository
   - /about-email-notifications-for-pushes-to-your-repository
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
new file mode 100644
index 0000000000..0e76db15bc
--- /dev/null
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
@@ -0,0 +1,24 @@
+---
+title: Managing the commit signoff policy for your repository
+intro: 'You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}''s web interface.'
+versions:
+  feature: commit-signoffs
+permissions: Organization owners and repository administrators can require all commits to a repository to be signed off by the commit author.
+topics:
+  - Repositories
+shortTitle: Manage the commit signoff policy
+---
+
+## About commit signoffs
+
+Commit signoffs enable users to affirm that a commit complies with the rules and licensing governing a repository. You can enable compulsory commit signoffs on individual repositories for users committing through {% data variables.product.product_location %}'s web interface, making signing off on a commit a seemless part of the commit process. Once compulsory commit signoffs are enabled for a repository, every commit made to that repository through {% data variables.product.product_location %}'s web interface will automatically be signed off on by the commit author.
+
+Organization owners can also enable compulsory commit signoffs at the organization level. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)."
+
+{% data reusables.repositories.commit-signoffs %}
+
+## Enabling or disabling compulsory commit signoffs for your repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Select **Require contributors to sign off on web-based commits**. ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png)
diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index 66180a5c45..3c3716db6f 100644
--- a/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -64,7 +64,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
    ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif)
 2. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
    ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png)
-{%- ifversion fpt or ghec %}
+{%- ifversion discussions %}
 1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion.
   ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png)
 {%- endif %}
diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-discussions.md b/translations/es-ES/content/search-github/searching-on-github/searching-discussions.md
index ad00931354..8c342f2377 100644
--- a/translations/es-ES/content/search-github/searching-on-github/searching-discussions.md
+++ b/translations/es-ES/content/search-github/searching-on-github/searching-discussions.md
@@ -2,8 +2,7 @@
 title: Buscar debates
 intro: 'Puedes buscar debates en {% data variables.product.product_name %} y reducir los resultados utilizando calificadores.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - GitHub search
 redirect_from:
diff --git a/translations/es-ES/content/site-policy/github-terms/github-corporate-terms-of-service.md b/translations/es-ES/content/site-policy/github-terms/github-corporate-terms-of-service.md
index 502f481456..64c73868c5 100644
--- a/translations/es-ES/content/site-policy/github-terms/github-corporate-terms-of-service.md
+++ b/translations/es-ES/content/site-policy/github-terms/github-corporate-terms-of-service.md
@@ -10,7 +10,7 @@ topics:
   - Legal
 ---
 
-_These terms apply to GitHub.com customers who have executed agreements in place referencing the Corporate Terms of Service. All other business or institution customers are directed to [github.com/customer-terms](https://github.com/customer-terms) for current terms._
+_Estos términos aplican a los clientes de GitHub.com que hayan ejecutado acuerdos vigentes que referencien los Términos de Servicio Corporativo. Se dirigirá al resto de los negocios o clientes institucionales a [github.com/customer-terms](https://github.com/customer-terms) para ver los términos actuales._
 
 ## Términos de servicio corporativos de GitHub
 Fecha de entrada en vigencia de la versión: 16 de noviembre de 2020
@@ -27,11 +27,11 @@ El presente Acuerdo se aplica a las siguientes ofertas de GitHub, como se define
 
 **"Acuerdo"** significa, colectivamente, todos los términos, condiciones, avisos contenidos o referenciados en este documento y todas las demás reglas operativas. políticas y procedimientos que GitHub puede publicar periódicamente en el Servicio. Las políticas de sitio de GitHub están disponibles en [https://docs.github.com/categories/site-policy](/categories/site-policy).
 
-**“All Users”** means, collectively, Customer’s Users and External Users who use the Service.
+**“Todos los usuarios”** se refiere, colectivamente, a los usuarios externos y del cliente quienes utilizan el servicio.
 
-**“Americas”** means the United States, Canada, Mexico, or a country in Central or South America or the Caribbean.
+**“Las Américas”** se refiere a los Estados Unidos, Canadá, México o a los países de América Central o del Sur o del Caribe.
 
-**"Beta Previews"** mean software, services, or features identified as alpha, beta, preview, early access, or evaluation, or words or phrases with similar meanings.
+**"Vistas Previas Beta"** se refiere al software, servicios o características identificadas como alfa, beta, vista previa, acceso temprano o palabras y frases con significados similares.
 
 **"Información confidencial"** se refiere a toda la información no pública divulgada por cualquiera de las Partes a otros, ya sea por escrito, en forma oral o por otros medios, designada como confidencial o que la Parte receptora sabe o razonablemente debe saber, conforme a las circunstancias en torno a la divulgación y la naturaleza de la información, que es confidencial para la Parte reveladora. Para evitar dudas, ningún Contenido publicado en el Servicio se considerará Información confidencial excepto el Contenido del Cliente almacenado únicamente en los Repositorios privados del Cliente. La Información confidencial no incluye ninguna información que (i) era de conocimiento público o se dio a conocer públicamente por motivos ajenos a la parte receptora; (ii) era legítimamente conocida o se dio a conocer en forma legítima a la Parte receptora sin restricciones de propiedad o confidencialidad por parte de una fuente que no es la parte reveladora y que tiene derecho a divulgarla; (iii) es aprobada por la Parte reveladora para su divulgación sin restricciones en un documento escrito firmado por un funcionario debidamente autorizado de dicha Parte reveladora; (iv) la Parte receptora desarrolla independientemente sin el acceso a la Información confidencial de la otra Parte ni el uso de esta; o (v) está o estuvo almacenada o publicada en el Servicio y fuera de los Repositorios privados del Cliente.
 
@@ -112,7 +112,7 @@ El Cliente es responsable de: (i) todo el Contenido publicado y la actividad que
 En algunas situaciones, pueden aplicarse términos de terceros al uso del Cliente de GitHub. Por ejemplo, el Cliente puede ser miembro de una Organización con sus propios términos o acuerdos de licencia; el Cliente puede descargar una aplicación que se integre con el Servicio; o el Cliente puede usar el Servicio para autenticarse a otro servicio. Aunque este Acuerdo es el acuerdo completo de GitHub con el Cliente, los términos de otras partes rigen sus relaciones con el Cliente.
 
 ### 5. Feriado en Términos del Gobierno federal de los EE.⁰UU
-Si el cliente es una government entity or otherwise accessing or using the Service in a government capacity, the [U.S. Federal Government Amendment](/articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users) applies, and Customer agrees to its provisions.
+Si el cliente es una entidad gubernamental de los EE.UU. o accede o utiliza de otra manera el servicio en calidad de gobierno, aplicará la [Enmienda del Gobierno Federal de los EE.UU., ](/articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users)y el cliente acordará con estas disposiciones.
 
 ### 6. Acuerdo sobre los Niveles de Servicio de Enterprise Cloud
 El compromiso de tiempo activo trimestral de Github para Github Enterprise Cloud se proporciona en el [Acuerdo de Nivel de Servicio Empresarial](/github/site-policy/github-enterprise-service-level-agreement). Si el cliente se registra para GitHub Enterprise Cloud, entonces éste será acreedor a un crédito de servicio en caso de que GitHub no cumpla con sus niveles de servicio.
diff --git a/translations/es-ES/content/site-policy/other-site-policies/github-and-trade-controls.md b/translations/es-ES/content/site-policy/other-site-policies/github-and-trade-controls.md
index e7c38a9a5e..d6c150b9ae 100644
--- a/translations/es-ES/content/site-policy/other-site-policies/github-and-trade-controls.md
+++ b/translations/es-ES/content/site-policy/other-site-policies/github-and-trade-controls.md
@@ -48,7 +48,7 @@ GitHub Enterprise Server no podrá venderse, exportarse o re-exportarse a cualqu
 
 ### ¿En qué países y territorios se aplican las sanciones del gobierno estadounidense ?
 
-Crimea, the separatist areas of Donetsk and Luhansk, Cuba, Iran, North Korea, and Syria. Sin embargo, en lo que corresponde a Iran, GitHub ahora tiene una licencia de la Oficina de Control de Bienes Extranjeros (OFAC) del Departamento del Tesoro de los EE.UU. para proporcionar servicios en la nube a los desarrolladores que residen o se ubican de otra forma en este país. Tanto las versiones de paga como las gratuitas de los servicios de la nube de GitHub se encuentran habitualmente disponibles también para los desarrolladores que se ubican en Cuba.
+Crimea, las áreas separatistas de Donetsk y Luhansk, Cuba, Irán, Corea del Norte y Siria. Sin embargo, en lo que corresponde a Iran, GitHub ahora tiene una licencia de la Oficina de Control de Bienes Extranjeros (OFAC) del Departamento del Tesoro de los EE.UU. para proporcionar servicios en la nube a los desarrolladores que residen o se ubican de otra forma en este país. Tanto las versiones de paga como las gratuitas de los servicios de la nube de GitHub se encuentran habitualmente disponibles también para los desarrolladores que se ubican en Cuba.
 
 ### ¿Cómo garantiza GitHub que las personas que no viven o que tienen vínculos profesionales con los países y territorios sancionados continúan teniendo acceso o capacidad de solicitud?
 
diff --git a/translations/es-ES/data/features/GH-advisory-db-erlang-support.yml b/translations/es-ES/data/features/GH-advisory-db-erlang-support.yml
new file mode 100644
index 0000000000..bfb6aa0a58
--- /dev/null
+++ b/translations/es-ES/data/features/GH-advisory-db-erlang-support.yml
@@ -0,0 +1,7 @@
+#Reference: Issue #6207.
+#We have added support for Elixir advisories to the Advisory Database.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-6207'
diff --git a/translations/es-ES/data/features/audit-log-streaming.yml b/translations/es-ES/data/features/audit-log-streaming.yml
new file mode 100644
index 0000000000..1ff0517353
--- /dev/null
+++ b/translations/es-ES/data/features/audit-log-streaming.yml
@@ -0,0 +1,5 @@
+#Reference: #7055
+#Documentation for audit log streaming
+versions:
+  ghec: '*'
+  ghes: '>= 3.6'
diff --git a/translations/es-ES/data/features/commit-signoffs.yml b/translations/es-ES/data/features/commit-signoffs.yml
new file mode 100644
index 0000000000..26fe611963
--- /dev/null
+++ b/translations/es-ES/data/features/commit-signoffs.yml
@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6049'
diff --git a/translations/es-ES/data/features/discussions.yml b/translations/es-ES/data/features/discussions.yml
new file mode 100644
index 0000000000..66a3bb8592
--- /dev/null
+++ b/translations/es-ES/data/features/discussions.yml
@@ -0,0 +1,4 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
diff --git a/translations/es-ES/data/features/docker-ghcr-enterprise-migration.yml b/translations/es-ES/data/features/docker-ghcr-enterprise-migration.yml
new file mode 100644
index 0000000000..48c1b97cc9
--- /dev/null
+++ b/translations/es-ES/data/features/docker-ghcr-enterprise-migration.yml
@@ -0,0 +1,4 @@
+#Reference: #7360
+#Documentation for migration from Docker registry to Container registry for enterprise products
+versions:
+  ghes: '>= 3.6'
diff --git a/translations/es-ES/data/features/ghas-enablement-webhook.yml b/translations/es-ES/data/features/ghas-enablement-webhook.yml
index cbb4509714..83f8a995bc 100644
--- a/translations/es-ES/data/features/ghas-enablement-webhook.yml
+++ b/translations/es-ES/data/features/ghas-enablement-webhook.yml
@@ -2,5 +2,5 @@
 #docs-content 7314. GHAS enablement webhook
 versions:
   ghec: '*'
-  ghes: '>3.6'
+  ghes: '>= 3.6'
   ghae: 'issue-7314'
diff --git a/translations/es-ES/data/features/motion-management.yml b/translations/es-ES/data/features/motion-management.yml
new file mode 100644
index 0000000000..573307aac2
--- /dev/null
+++ b/translations/es-ES/data/features/motion-management.yml
@@ -0,0 +1,7 @@
+#Issue 6523
+#Support for customizing the automatic playback of animated images in the web interface
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6523'
diff --git a/translations/es-ES/data/features/pause-audit-log-stream.yml b/translations/es-ES/data/features/pause-audit-log-stream.yml
new file mode 100644
index 0000000000..59bcda81d5
--- /dev/null
+++ b/translations/es-ES/data/features/pause-audit-log-stream.yml
@@ -0,0 +1,4 @@
+#Reference #4640
+#Documentation for pausing an audit log stream
+versions:
+  ghec: '*'
diff --git a/translations/es-ES/data/features/require-tls-for-smtp.yml b/translations/es-ES/data/features/require-tls-for-smtp.yml
new file mode 100644
index 0000000000..dd1f0d2c78
--- /dev/null
+++ b/translations/es-ES/data/features/require-tls-for-smtp.yml
@@ -0,0 +1,4 @@
+#Reference 7394
+#Documentation for the option to enforce TLS encryption for incoming SMTP connections
+versions:
+  ghes: '>=3.6'
diff --git a/translations/es-ES/data/features/security-advisories-ghes-ghae.yml b/translations/es-ES/data/features/security-advisories-ghes-ghae.yml
new file mode 100644
index 0000000000..c4d8f488a5
--- /dev/null
+++ b/translations/es-ES/data/features/security-advisories-ghes-ghae.yml
@@ -0,0 +1,4 @@
+#Reference: Issue #6982 Community Contributions to Security Advisories - Enterprise 3.6
+versions:
+  ghes: '>=3.6'
+  ghae: 'issue-6982'
diff --git a/translations/es-ES/data/graphql/ghes-3.6/graphql_previews.enterprise.yml b/translations/es-ES/data/graphql/ghes-3.6/graphql_previews.enterprise.yml
new file mode 100644
index 0000000000..781f7b1b7e
--- /dev/null
+++ b/translations/es-ES/data/graphql/ghes-3.6/graphql_previews.enterprise.yml
@@ -0,0 +1,123 @@
+- 
+  title: Acceso al borrado de versiones de paquetes
+  description: >-
+    Esta vista previa agrega soporte para la mutación DeletePackageVersion, la cual habilita el borrado de versiones de paquetes privados.
+  toggled_by: ':package-deletes-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.deletePackageVersion
+  owning_teams:
+    - '@github/pe-package-registry'
+- 
+  title: Implementaciones
+  description: >-
+    Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue.
+  toggled_by: ':flash-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - DeploymentStatus.environment
+    - Mutation.createDeploymentStatus
+    - CreateDeploymentStatusInput
+    - CreateDeploymentStatusPayload
+    - Mutation.createDeployment
+    - CreateDeploymentInput
+    - CreateDeploymentPayload
+  owning_teams:
+    - '@github/c2c-actions-service'
+- 
+  title: >-
+    >- MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción.
+  description: >-
+    Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción.
+  toggled_by: ':merge-info-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - PullRequest.canBeRebased
+    - PullRequest.mergeStateStatus
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: UpdateRefsPreview - Actualiza varias refs en una sola operación.
+  description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación.
+  toggled_by: ':update-refs-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateRefs
+    - GitRefname
+    - RefUpdate
+    - UpdateRefsInput
+    - UpdateRefsPayload
+  owning_teams:
+    - '@github/reponauts'
+- 
+  title: Detalles de Eventos del Proyecto
+  description: >-
+    Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto.
+  toggled_by: ':starfox-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - AddedToProjectEvent.project
+    - AddedToProjectEvent.projectCard
+    - AddedToProjectEvent.projectColumnName
+    - ConvertedNoteToIssueEvent.project
+    - ConvertedNoteToIssueEvent.projectCard
+    - ConvertedNoteToIssueEvent.projectColumnName
+    - MovedColumnsInProjectEvent.project
+    - MovedColumnsInProjectEvent.projectCard
+    - MovedColumnsInProjectEvent.projectColumnName
+    - MovedColumnsInProjectEvent.previousProjectColumnName
+    - RemovedFromProjectEvent.project
+    - RemovedFromProjectEvent.projectColumnName
+  owning_teams:
+    - '@github/github-projects'
+- 
+  title: Vista Previa de Etiquetas
+  description: >-
+    Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas.
+  toggled_by: ':bane-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createLabel
+    - CreateLabelPayload
+    - CreateLabelInput
+    - Mutation.deleteLabel
+    - DeleteLabelPayload
+    - DeleteLabelInput
+    - Mutation.updateLabel
+    - UpdateLabelPayload
+    - UpdateLabelInput
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: Importar Proyecto
+  description: Esta vista previa agrega soporte para importar proyectos.
+  toggled_by: ':slothette-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.importProject
+  owning_teams:
+    - '@github/pe-issues-projects'
+- 
+  title: Vista Previa de las Tareas de Revisión del Equipo
+  description: >-
+    Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo.
+  toggled_by: ':stone-crop-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateTeamReviewAssignment
+    - UpdateTeamReviewAssignmentInput
+    - TeamReviewAssignmentAlgorithm
+    - Team.reviewRequestDelegationEnabled
+    - Team.reviewRequestDelegationAlgorithm
+    - Team.reviewRequestDelegationMemberCount
+    - Team.reviewRequestDelegationNotifyTeam
+  owning_teams:
+    - '@github/pe-pull-requests'
diff --git a/translations/es-ES/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml b/translations/es-ES/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml
new file mode 100644
index 0000000000..718abf97a7
--- /dev/null
+++ b/translations/es-ES/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml
@@ -0,0 +1,86 @@
+---
+upcoming_changes:
+  - 
+    location: LegacyMigration.uploadUrlTemplate
+    description: 'Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución.'
+    reason: 'Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario.'
+    date: '2019-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: AssignedEvent.user
+    description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.'
+    reason: Los asignados ahora pueden ser maniquíes.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: UnassignedEvent.user
+    description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.'
+    reason: Los asignados ahora pueden ser maniquíes.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: Issue.timeline
+    description: 'Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución.'
+    reason: 'Se eliminará a `timeline`'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: PullRequest.timeline
+    description: 'Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución.'
+    reason: 'Se eliminará a `timeline`'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: MergeStateStatus.DRAFT
+    description: 'El `DRAFT` se eliminará. Utiliza PullRequest.isDraft en su lugar.'
+    reason: El estado del DRAFT se eliminará de esta enumeración y se deberá utilizar `isDraft` en su lugar
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: nplasterer
+  - 
+    location: PackageType.DOCKER
+    description: 'Se eliminará a `DOCKER`.'
+    reason: Se eliminará a DOCKER de esta enumeración, ya que este tipo se migrará para que solo lo utilice la API de REST de paquetes.
+    date: '21-06-2021'
+    criticality: breaking
+    owner: reybard
+  - 
+    location: ReactionGroup.users
+    description: 'Se eliminará a `users`. Utiliza el campo de `reactors` en su lugar.'
+    reason: Los reactores ahora pueden ser maniquíes, bots y organizaciones.
+    date: '2021-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: synthead
+  - 
+    location: Repository.defaultMergeQueue
+    description: 'Se eliminará a `defaultMergeQueue`. Utiliza `Repository.mergeQueue` en su lugar.'
+    reason: 'Se eliminará `defaultMergeQueue`.'
+    date: '01-04-2022'
+    criticality: breaking
+    owner: colinshum
+  - 
+    location: AddPullRequestToMergeQueueInput.branch
+    description: 'Se eliminará la `branch`.'
+    reason: Las solicitudes de cambio se agregan a la cola de fusión para la rama base, el argumento `branch` ahora es un no-op
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jhunschejones
+  - 
+    location: Enterprise.userAccounts
+    description: 'Se eliminarán las `userAccounts`. Utilice el campo `Enterprise.members` en su lugar.'
+    reason: Se eliminará el campo de `Enterprise.userAccounts`.
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
+  - 
+    location: RemovePullRequestFromMergeQueueInput.branch
+    description: 'Se eliminará la `branch`.'
+    reason: Las solicitudes de cambio se eliminan de la cola de fusión para la rama base, el argumento `branch` ahora es un no-op
+    date: '2022-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jhunschejones
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/15.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/15.yml
index f5dfc63ee1..f966c3b514 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-2/15.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/15.yml
@@ -8,7 +8,7 @@ sections:
     - In some cases, site administrators were not automatically added as enterprise owners.
     - After merging a branch into the default branch, the "History" link for a file would still link to the previous branch instead of the target branch.
   changes:
-    - Creating or updating check runs or check suites could return `500 Internal Server Error` if the value for certain fields, like the name, was too long.
+    - El crear o actualizar ejecuciones de verificación o suites de verificación pudo devolver un `500 Internal Server Error` si el valor para campos específicos, como el de nombre, era demasiado largo.
   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/release-notes/enterprise-server/3-2/16.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/16.yml
index 6c7e2778c7..4e2adf6fe1 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-2/16.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/16.yml
@@ -8,9 +8,9 @@ sections:
     - 'Se corrigió un problema en donde los archivos dentro de los archivos zip de los artefactos tenían permisos de 000 cuando se desempacaban utilizando una herramienta de descompresión. Ahora los archivos tenían el permiso configurado en 644, de la misma forma que funciona en GitHub.com.'
     - 'In some cases, the collectd daemon could consume excess memory.'
     - 'In some cases, backups of rotated log files could accumulate and consume excess storage.'
-    - 'After an upgrade to a new feature release and subsequent configuration run, Elasticsearch could log excessive exceptions while rebuilding indices.'
+    - 'Después de actualizar a un lanzamiento de característica nuevo y a una ejecución de configuración posterior, Elastichsearch pudo haber registrado excepciones excesivas de bitácoras mientras recompilaba los índices.'
     - 'In some cases where a protected branch required more than one approving review, a pull request could be merged with fewer than the required number of approving reviews.'
-    - 'On instances using LDAP authentication, the authentication prompt for sudo mode incorrectly placed the cursor within the password field by default when text fields for both a username and password were visible.'
+    - 'En las instancias que utilizan autenticación de LDAP, el mensaje de autenticación para modo sudo colocó incorrectamente el cursor dentro del campo de contraseña predeterminadamente cuando los campos de texto tanto para el nombre de usuario como par ala contraseña estaban visibles.'
   changes:
     - 'The `ghe-set-password` command-line utility starts required services automatically when the instance is booted in recovery mode.'
     - 'Metrics for `aqueduct` background processes are gathered for Collectd forwarding and display in the Management Console.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/10.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/10.yml
index bcff668dd6..77c3532f6c 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-3/10.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/10.yml
@@ -6,9 +6,9 @@ sections:
     - Los paquetes se actualizaron a las últimas versiones de seguridad.
   bugs:
     - In some cases, site administrators were not automatically added as enterprise owners.
-    - After merging a branch into the default branch, the "History" link for a file would still link to the previous branch instead of the target branch.
+    - Después de fusionar una rama en la rama predeterminada, el enlace de "Historial" de un archivo aún enlazaba con la rama anterior en vez de con la rama destino.
   changes:
-    - Creating or updating check runs or check suites could return `500 Internal Server Error` if the value for certain fields, like the name, was too long.
+    - El crear o actualizar ejecuciones de verificación o suites de verificación pudo devolver un `500 Internal Server Error` si el valor para campos específicos, como el de nombre, era demasiado largo.
   known_issues:
     - Después de haber actualizado a {% data variables.product.prodname_ghe_server %} 3.3, podría que las {% data variables.product.prodname_actions %} no inicien automáticamente. Para resolver este problema, conéctate al aplicativo a través de SSH y ejecuta el comando `ghe-actions-start`.
     - 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.
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 9a0828719b..85356f5c19 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
@@ -8,7 +8,7 @@ sections:
     - 'En algunas topologías de clúster, el comando `ghe-cluster-status` dejó directorios vacíos en `/tmp`.'
     - 'El SNMP registró una cantidad alta de mensajes de error de `Cannot statfs` incorrectamente en syslog'
     - '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`.'
+    - 'Los intentos pra ver la salida de `git fsck` de la página `/stafftools/repositories/:owner/:repo/disk` fallaron con un `500 Internal Server Error`.'
     - 'Al utilizar aserciones cifradas de SAML, algunas de ellas no estaban marcando correctamente a las llaves SSH como verificadas.'
     - 'Los videos que se suben a los comentarios de las propuestas no se representaron adecuadamente.'
     - 'When using the file finder on a repository page, typing the backspace key within the search field would result in search results being listed multiple times and cause rendering problems.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/9.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/9.yml
index 67a108e5d5..56406a2ac4 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-3/9.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/9.yml
@@ -6,7 +6,7 @@ sections:
   bugs:
     - Un script interno para validar nombres de host en el archivo de configuración de {% data variables.product.prodname_ghe_server %} devolvió un error cuando la secuencia de nombre de host iniciaba con un "." (punto).
     - In HA configurations where the primary node's hostname was longer than 60 characters, MySQL would fail to be configured
-    - The `--gateway` argument was added to the `ghe-setup-network` command, to allow passing the gateway address when configuring network settings using the command line.
+    - El argumento `--gateway` se agergó al comando `ghe-setup-network`, para permitir que pasara la dirección de puerta de enlace al configurar los ajustes de red utilizando la línea de comandos.
     - Image attachments that were deleted would return a `500 Internal Server Error` instead of a `404 Not Found` error.
     - The calculation of "maximum committers across entire instance" reported in the site admin dashboard was incorrect.
     - Una entrada incorrecta en la base de datos para las réplicas de repositorio ocasionó que dicha base de datos se corrompiera al realizar una restauración utilizando {% data variables.product.prodname_enterprise_backup_utilities %}.
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-4/4.yml b/translations/es-ES/data/release-notes/enterprise-server/3-4/4.yml
index 8bfcda1d00..d6d223fb0e 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-4/4.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-4/4.yml
@@ -7,11 +7,11 @@ sections:
     - Un script interno para validar nombres de host en el archivo de configuración de {% data variables.product.prodname_ghe_server %} devolvió un error cuando la secuencia de nombre de host iniciaba con un "." (punto).
     - In HA configurations where the primary node's hostname was longer than 60 characters, MySQL would fail to be configured.
     - When {% data variables.product.prodname_actions %} was enabled but TLS was disabled on {% data variables.product.prodname_ghe_server %} 3.4.1 and later, applying a configuration update would fail.
-    - The `--gateway` argument was added to the `ghe-setup-network` command, to allow passing the gateway address when configuring network settings using the command line.
+    - El argumento `--gateway` se agergó al comando `ghe-setup-network`, para permitir que pasara la dirección de puerta de enlace al configurar los ajustes de red utilizando la línea de comandos.
     - 'Las terminales de la [API de facturación para {% data variables.product.prodname_GH_advanced_security %}](/rest/enterprise-admin/billing#get-github-advanced-security-active-committers-for-an-enterprise) no se habilitaron y no se puede acceder a ellas.'
     - Image attachments that were deleted would return a `500 Internal Server Error` instead of a `404 Not Found` error.
     - In environments configured with a repository cache server, the `ghe-repl-status` command incorrectly showed gists as being under-replicated.
-    - The "Get a commit" and "Compare two commits" endpoints in the [Commit API](/rest/commits/commits) would return a `500` error if a file path in the diff contained an encoded and escaped unicode character.
+    - Las terminales de "Obtén una confirmación" y "Compara dos confirmaciones" en la [API de confirmaciones](/rest/commits/commits) devolvieron un error `500` si una ruta de archivo en el diff contenía un carácter de unicode cifrado y escapado.
     - The calculation of "maximum committers across entire instance" reported in the site admin dashboard was incorrect.
     - Una entrada incorrecta en la base de datos para las réplicas de repositorio ocasionó que dicha base de datos se corrompiera al realizar una restauración utilizando {% data variables.product.prodname_enterprise_backup_utilities %}.
     - The activity timeline for secret scanning alerts wasn't displayed.
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-4/5.yml b/translations/es-ES/data/release-notes/enterprise-server/3-4/5.yml
index fb3b2ea6c9..83ac707d2a 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-4/5.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-4/5.yml
@@ -8,13 +8,13 @@ sections:
   bugs:
     - Files inside an artifact archive were unable to be opened after decompression due to restrictive permissions.
     - Redis timeouts no longer halt database migrations while running `ghe-config-apply`.
-    - Background job processors would get stuck in a partially shut-down state, resulting in certain kinds of background jobs (like code scanning) appearing stuck.
+    - Los procesadores de jobs en segundo plano se atoraron en un estado de cierre parcial, lo cuál dio como resultado que algunos tipos de jobs en segundo plano (como el escaneo de código) se mostrarán atorados.
     - In some cases, site administrators were not automatically added as enterprise owners.
     - A rendering issue could affect the dropdown list for filtering secret scanning alerts in a repository.
   changes:
     - Improved the performance of Dependabot version updates after first enabled.
     - The GitHub Pages build and synchronization timeouts are now configurable in the Management Console.
-    - Creating or updating check runs or check suites could return `500 Internal Server Error` if the value for certain fields, like the name, was too long.
+    - El crear o actualizar ejecuciones de verificación o suites de verificación pudo devolver un `500 Internal Server Error` si el valor para campos específicos, como el de nombre, era demasiado largo.
     - 'Cuando [despliegas nodos de servidor caché](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache#configuring-a-repository-cache), ahora es obligatorio describir la topología del centro de datos (utilizando el argumento `--datacenter`) para cada nodo en el sistema. Este requisito previene situaciones en donde el dejar una membrecía del centro de datos configurada como "default" ocasiona que las cargas de trabajo se balanceen inadecuadamente a lo largo de varios centros de datos.'
   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.
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-4/6.yml b/translations/es-ES/data/release-notes/enterprise-server/3-4/6.yml
index e542b56851..616f06e430 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-4/6.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-4/6.yml
@@ -8,9 +8,9 @@ sections:
   bugs:
     - 'In some cases, the collectd daemon could consume excess memory.'
     - 'In some cases, backups of rotated log files could accumulate and consume excess storage.'
-    - 'After an upgrade to a new feature release and subsequent configuration run, Elasticsearch could log excessive exceptions while rebuilding indices.'
+    - 'Después de actualizar a un lanzamiento de característica nuevo y a una ejecución de configuración posterior, Elastichsearch pudo haber registrado excepciones excesivas de bitácoras mientras recompilaba los índices.'
     - 'In some cases where a protected branch required more than one approving review, a pull request could be merged with fewer than the required number of approving reviews.'
-    - 'On instances using LDAP authentication, the authentication prompt for sudo mode incorrectly placed the cursor within the password field by default when text fields for both a username and password were visible.'
+    - 'En las instancias que utilizan autenticación de LDAP, el mensaje de autenticación para modo sudo colocó incorrectamente el cursor dentro del campo de contraseña predeterminadamente cuando los campos de texto tanto para el nombre de usuario como par ala contraseña estaban visibles.'
     - 'In some cases, scheduled GitHub Actions workflows could become disabled.'
     - 'The Billing API''s "[Get GitHub Advanced Security active committers for an organization](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)" endpoint now returns `Link` headers to provide information about pagination.'
     - 'The Billing API''s "[Get GitHub Advanced Security active committers for an organization](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)" endpoint now returns the correct number of total committers.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-5/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-5/0.yml
index b5c05eb6f3..7e8c44508b 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-5/0.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-5/0.yml
@@ -22,7 +22,7 @@ sections:
 
           Los 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.
     - 
-      heading: GitHub Container registry in public beta
+      heading: El registro de contenedores de GitHub está en beta público
       notes:
         - |
           El registro de contenedores de GitHub (GHCR) está ahora disponible en GitHub Enterprise Server 3.5 como un beta público. Este ofrece a los desarrolladores la capacidad de publicar, descargar y administrar contenedores. La compatibilidad de contenedores de GitHub Packages implementa los estándares OCI para hospedar imágenes de Docker. Para obtener más información, consulta la sección "[Registro de contenedores de GitHub](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)".
@@ -37,7 +37,7 @@ sections:
         - |
           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.
     - 
-      heading: GitHub Actions rate limiting is now configurable
+      heading: El límite de tasa de GitHub Actions ahora se puede configurar
       notes:
         - |
           Los administradores de sitio ahora pueden habilitar y configurar un limite de tasa para las GitHub Actions. Predeterminadamente, el límite de tasa se inhabilita. Cuando los jobs de los flujos de trabajo no se pueden asignar inmediatamente a un ejecutor disponible, esperarán en cola hasta que un ejecutor esté disponible. Sin embargo, si las GitHub Actions sufren una carga alta sostenida, la cola puede respaldarse más rápido de lo que puede drenarse y el rendimiento de la instancia de GitHub Enterprise Server podría degradarse. Para evitar esto, un administrador puede configurar un límite de tasa. Cuando dicho límite se exceda, las ejecuciones de flujo de trabajo adicionales fallarán de inmediato en vez de ponerse en cola. Una vez que la tasa se haya estabilizado debajo del umbral, las ejecuciones nuevas se pueden poner en cola nuevamente. Para obtener más información, consulta la sección "[Configurar los límites de tasa](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions)".
@@ -57,7 +57,7 @@ sections:
         - |
           La compatibilidad para las GitHub Actions en los repositorios internos ahora está disponible al público en general para las organizaciones de tu instancia de GitHub Enterprise Server. Puedes hacer innersourcing de automatización si compartes las acciones en los repositorios internos. Puedes administrar los ajustes de un repositorio o utilizar la API de REST para permitir el acceso a los flujos de trabajo en otros repositorios dentro de la organización o en cualquier organización de la instancia. Para obtener más información, consulta las secciones "[Compartir las acciones y los flujos de trabajo con tu empresa](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)", "[Administrar los ajustes de las GitHub Actions para 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)" y "[Permisos de las acciones](/rest/actions/permissions#get-the-level-of-access-for-workflows-outside-of-the-repository)" en la documentación de la API de REST.
     - 
-      heading: Cache support for GitHub Actions on GitHub Enterprise Server is now generally available
+      heading: El soporte de caché para GitHub Actions en GitHub Enterprise Server ahora está disponible en general
       notes:
         - |
           Ahora puedes utilizar el almacenamiento de dependencias en caché para acelerar tus flujos de trabajo de GitHub Actions. Para almacenar las dependencias en caché para un job, puedes incluir la acción [actions/cache](https://github.com/actions/cache) para crear un caché con una llave única. Puedes compartir cachés en todos los flujos de trabajo del mismo repositorio. Estos flujos de trabajo pueden restablecer el caché y ejecutarse más rápido.
@@ -71,7 +71,7 @@ sections:
 
           El almacenamiento externo de blobs que se configura con tu cuenta empresarial ahora se compartirá entre los artefactos de flujo de trabajo, bitácoras y también con los cachés. Para obtener más información, consulta la sección "[Almacenar las dependencias en caché para acelerar los flujos de trabajo](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".
     - 
-      heading: Automatically sign commits made in the web UI
+      heading: Firma automáticamente las confirmaciones que se hagan en la IU web
       notes:
         - |
           Ahora puedes configurar GitHub Enterprise Server para que firme automáticamente las confirmaciones que se hacen en la interfaz web, tal como las de editar un archivo o fusionar una solicitud de cambios. Las confirmaciones firmadas aumentan la seguridad de que los cambios vengan de fuentes confiables. Esta característica permite que el ajuste de protección de rama [Requerir confirmaciones firmadas](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-signed-commits) bloquee las confirmaciones sin firmar para que no ingresen a un repositorio, mientras que permite la entrada de confirmaciones firmadas; incluso aquellas que se hacen en la interfaz web. Para obtener más información, consulta la sección "[Configurar el firmado de las confirmaciones web](/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing)".
@@ -128,7 +128,7 @@ sections:
         - |
           El resumen de alertas de seguridad a nivel organizacional ahora está disponible en general. Los clientes de GitHub Advanced Security pueden utilizar el resumen de seguridad para obtener una vista centrada en el repositorio de los riesgos de seguridad de las aplicaciones o una vista centrada en las alertas de todo el escaneo de código, el Dependabot y las alertas de escaneo para todos los repositorios en una organización. Para obtener más información, consulta la sección "[Acerca de la revisión de seguridad](/code-security/security-overview/about-the-security-overview)".
     - 
-      heading: Code scanning detects more security issues, supports new language versions
+      heading: El escaneo de código detecta más problemas de seguridad y es compatible con versiones nuevas de los lenguajes
       notes:
         - |
           El escaneo de código ahora detecta una cantidad mayor de CWE y el escaneo de código de CodeQL es totalmente compatible con las características de lenguaje en los lanzamientos de los siguientes lenguajes.
@@ -162,7 +162,7 @@ sections:
         - |
           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)".
     - 
-      heading: Configure permissions for secret scanning with custom repository roles
+      heading: Configurar permisos para el escaneo de código con roles de repositorio personalizados
       notes:
         - |
           Ahora puedes configurar dos permisos nuevos para el escaneo de secretos cuando administras roles de repositorio personalizados.
@@ -187,7 +187,7 @@ sections:
         - |
           Los clientes de GitHub Advanced Security ahora pueden ver las alertas del Dependabot en la pestaña de **Seguridad** de una organización. Esta vista está disponible para los propietarios de las organizaciones y miembros de los equipos con el [rol de gerente de seguridad](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). Para obtener más información, consulta la sección "[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)".
     - 
-      heading: Configure permissions for Dependabot alerts with custom repository roles
+      heading: Configurar los permisos para las alertas del Dependabot con roles de repositorio personalizados
       notes:
         - |
           Ahora puedes configurar dos permisos nuevos para las alertas del Dependabot cuando administres roles de repositorio personalizados.
@@ -223,7 +223,7 @@ sections:
         - |
           El nuevo objeto de GraphQL `DependabotUpdate` te permite ver la información sobre lo que le pasa a las actualizaciones de seguridad de tu repositorio. Cuando GitHub Enterprise Server detecta que una dependencia de tu repositorio está vulnerable, el Dependabot intentará abrir la solicitud de cambios para actualizar la dependencia a una versión no vulnerable. Ahora puedes ver la solicitud de cambios que corrige la vulnerabilidad. En algunos casos, el Dependabot no puede abrir una solicitud de cambios. Anteriormente, el mensaje de error que generaba el Dependabot solo se podía ver en la sección de "Alertas del Dependabot" en la pestaña de **Seguridad**. Ahora, si el Dependabot se encuentra con un error al intentar abrir la solicitud de cambios de una alerta de seguridad, puedes determinar la razón de esto utilizando la API de GraphQL. Para obtener más información, consulta la sección "[Objects](/graphql/reference/objects#dependabotupdate)" en la documentación de la API de GraphQL.
     - 
-      heading: Access more information about Dependabot alerts via GraphQL API
+      heading: Accede a más información sobre las alertas del Dependabot a través de la API de GraphQL
       notes:
         - |
           Ahora puedes ver las alertas fijas del Dependabot con la API de GraphQL. También puedes acceder y filtrar por estado y por identificador numérico único y puedes filtrar por estado en el objeto de alerta de la vulnerabilidad. Ahora existen los siguientes campos para una `RepositoryVulnerabilityAlert`.
@@ -235,7 +235,7 @@ sections:
 
           Para obtener más información, consulta la sección "[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)" en la documentación de la API de GraphQL.
     - 
-      heading: Git events in the enterprise audit log
+      heading: Los eventos de Git en la bitácora de auditoría empresarial
       notes:
         - |
           Los siguientes eventos relacionados con Git ahora pueden aparecer en la bitácora de auditoría empresarial. Si habilitas la característica y configuras un periodo de retención de bitácora de auditoría, los eventos nuevos estarán disponibles para su búsqueda a través de la IU y la API o para exportar en JSON o en CSV.
@@ -266,7 +266,7 @@ sections:
 
           - 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)".
     - 
-      heading: Configure custom HTTP headers for GitHub Pages sites
+      heading: Configurar los encabezados personalizados de HTTP para los sitios de GitHub Pages
       notes:
         - |
           Ahora puedes configurar los encabezados HTTP personalizados que aplican a todos los sitios de GitHub Pages que se sirven desde tu instancia de GitHub Enterprise Server. Para obtener más información, consulta la sección "[Configurar GitHub Pages para tu empresa](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)".
@@ -327,7 +327,7 @@ sections:
         - |
           GitHub Connect ya no funcionará después del 3 de junio para las instancias que ejecuten GitHub Enterprise Server 3.1 o anterior, debido al cambio en el formato de los tokens de autenticación de GitHub. Para seguir utilizando GitHub Connect, mejora a GitHub Enterprise Server 3.2 o posterior. Para obtener más información, consulta el [Blog de GitHub](https://github.blog/2022-05-20-action-needed-by-github-connect-customers-using-ghes-3-1-and-older-to-adopt-new-authentication-token-format-updates/). [Actualizado: 2022-06-14]
     - 
-      heading: CodeQL runner deprecated in favor of CodeQL CLI
+      heading: El ejecutor de CodeQL se obsoletizó para favorecer al CLI de CodeQL
       notes:
         - |
           El ejecutor de CodeQL es obsoleto para favorecer al CLI de CodeQL. GitHub Enterprise Server 3.4 y posterior ya no incluyen al ejecutor de CodeQL. Esta obsoletización solo afecta a los usuarios que utilizan el escaneo de código de CodeQL en sistemas de IC/DC de terceros. No se afecta a los usuarios de GitHub Actions. GitHub recomienda fuertemente que los clientes se migren al CLI de CodeQL, lo que es un reemplazo completo de características para el ejecutor de CodeQL y tiene muchas características adicionales. Para obtener más información, consulta la sección "[Migrarse del ejecutor de CodeQL al CLI de CodeQL](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)".
@@ -344,6 +344,6 @@ sections:
     - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.
     - 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.
-    - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+    - Los servicios de las acciones necesitan reiniciarse después de restablecer un aplicativo de un respaldo que se llevó a un host diferente.
     - 'Deleted repositories will not be purged from disk automatically after the 90-day retention period ends. [Updated: 2022-06-08]'
     - 'Management Console may appear stuck on the _Starting_ screen after upgrading an under-provisioned instance to GitHub Enterprise Server 3.5. [Updated: 2022-06-20]'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-5/1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-5/1.yml
index a12aa468bb..5d6fa2d640 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-5/1.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-5/1.yml
@@ -7,7 +7,7 @@ sections:
     - Un script interno para validar nombres de host en el archivo de configuración de {% data variables.product.prodname_ghe_server %} devolvió un error cuando la secuencia de nombre de host iniciaba con un "." (punto).
     - In HA configurations where the primary node's hostname was longer than 60 characters, MySQL would fail to be configured.
     - When {% data variables.product.prodname_actions %} was enabled but TLS was disabled on {% data variables.product.prodname_ghe_server %} 3.4.1 and later, applying a configuration update would fail.
-    - The `--gateway` argument was added to the `ghe-setup-network` command, to allow passing the gateway address when configuring network settings using the command line.
+    - El argumento `--gateway` se agergó al comando `ghe-setup-network`, para permitir que pasara la dirección de puerta de enlace al configurar los ajustes de red utilizando la línea de comandos.
     - 'The [{% data variables.product.prodname_GH_advanced_security %} billing API](/rest/enterprise-admin/billing#get-github-advanced-security-active-committers-for-an-enterprise) endpoints were not enabled and accessible.'
     - Image attachments that were deleted would return a `500 Internal Server Error` instead of a `404 Not Found` error.
     - In environments configured with a repository cache server, the `ghe-repl-status` command incorrectly showed gists as being under-replicated.
@@ -28,6 +28,6 @@ sections:
     - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.
     - 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.
-    - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+    - Los servicios de las acciones necesitan reiniciarse después de restablecer un aplicativo de un respaldo que se llevó a un host diferente.
     - 'Deleted repositories will not be purged from disk automatically after the 90-day retention period ends. This issue is resolved in the 3.5.1 release. [Updated: 2022-06-10]'
     - 'Management Console may appear stuck on the _Starting_ screen after upgrading an under-provisioned instance to GitHub Enterprise Server 3.5. [Updated: 2022-06-20]'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-5/2.yml b/translations/es-ES/data/release-notes/enterprise-server/3-5/2.yml
index ffce5e4eb4..642b8d3a6d 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-5/2.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-5/2.yml
@@ -31,5 +31,5 @@ sections:
     - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.
     - 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.
-    - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+    - Los servicios de las acciones necesitan reiniciarse después de restablecer un aplicativo de un respaldo que se llevó a un host diferente.
     - 'Deleted repositories will not be purged from disk automatically after the 90-day retention period ends. This issue is resolved in the 3.5.1 release. [Updated: 2022-06-10]'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-5/3.yml b/translations/es-ES/data/release-notes/enterprise-server/3-5/3.yml
index 0e7b22e8d7..e95c4a2e8a 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-5/3.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-5/3.yml
@@ -8,10 +8,10 @@ sections:
   bugs:
     - 'In some cases, the collectd daemon could consume excess memory.'
     - 'In some cases, backups of rotated log files could accumulate and consume excess storage.'
-    - 'After an upgrade to a new feature release and subsequent configuration run, Elasticsearch could log excessive exceptions while rebuilding indices.'
+    - 'Después de actualizar a un lanzamiento de característica nuevo y a una ejecución de configuración posterior, Elastichsearch pudo haber registrado excepciones excesivas de bitácoras mientras recompilaba los índices.'
     - 'In some cases where a protected branch required more than one approving review, a pull request could be merged with fewer than the required number of approving reviews.'
     - 'The GitHub Enterprise Importer did not correctly migrate settings for projects within repositories.'
-    - 'On instances using LDAP authentication, the authentication prompt for sudo mode incorrectly placed the cursor within the password field by default when text fields for both a username and password were visible.'
+    - 'En las instancias que utilizan autenticación de LDAP, el mensaje de autenticación para modo sudo colocó incorrectamente el cursor dentro del campo de contraseña predeterminadamente cuando los campos de texto tanto para el nombre de usuario como par ala contraseña estaban visibles.'
     - 'The site admin dashboard erroneously included an option to export a report listing dormant users.'
     - 'La terminal de la API de facturación de "[Obtener los confirmantes activos de GitHub Advanced Security para una organización](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)" ahora devuelve encabezados de `Link` para proporcionar información sobre la paginación.'
     - 'La terminal de la API de facturación de "[Obtener los confirmantes activos de GitHub Advanced Security para una organización](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)" ahora devuelve la cantidad correcta de confirmantes totales.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-6/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-6/0-rc1.yml
new file mode 100644
index 0000000000..5a197a4297
--- /dev/null
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-6/0-rc1.yml
@@ -0,0 +1,301 @@
+date: '2022-07-26'
+release_candidate: true
+deprecated: false
+intro: |
+  {% note %}
+
+  **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend that you only run release candidates in a test environment.
+
+  {% endnote %}
+
+  For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+sections:
+  features:
+    - heading: Infrastructure
+      notes:
+        # https://github.com/github/releases/issues/2002
+        - |
+          Repository caching is generally available. Repository caching increases Git read performance for distributed developers, providing the data locality and convenience of geo-replication without impact on push workflows. With the general availability release, GitHub Enterprise Server caches both Git and Git LFS data. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+
+    - heading: Instance security
+      notes:
+        # https://github.com/github/releases/issues/1569
+        - |
+          GitHub has changed the supported algorithms and hash functions for all SSH connections to GitHub Enterprise Server, disabled the unencrypted and unauthenticated Git protocol, and optionally allowed the advertisement of an Ed25519 host key. For more information, see the [GitHub Blog](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server/) and the following articles.
+
+          - "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)"
+          - "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)"
+          - "[Configuring host keys for your instance](/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance)"
+
+        # https://github.com/github/releases/issues/2341
+        - |
+          You can require TLS encryption for incoming SMTP connections to your instance. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)."
+
+    - heading: Audit logs
+      notes:
+        # https://github.com/github/releases/issues/1438
+        - |
+          You can stream audit log and Git events for your instance to Amazon S3, Azure Blob Storage, Azure Event Hubs, Google Cloud Storage, or Splunk. Audit log streaming is in public beta and subject to change. For more information, see "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
+
+    - heading: GitHub Connect
+      notes:
+        # https://github.com/github/releases/issues/2306
+        - |
+          Server Statistics is now generally available. Server Statistics collects aggregate usage data from your GitHub Enterprise Server instance, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from GitHub Enterprise Server. For more information, see "[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+
+    - heading: Administrator experience
+      notes:
+        # https://github.com/github/releases/issues/2351
+        - |
+          Enterprise owners can join organizations on the instance as a member or owner from the enterprise account's **Organizations** page. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."
+
+        # https://github.com/github/releases/issues/2221
+        - |
+          Enterprise owners can allow users to dismiss the configured global announcement banner. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
+
+    - heading: GitHub Advanced Security
+      notes:
+        # https://github.com/github/releases/issues/2321
+        - |
+          Users on an instance with a GitHub Advanced Security license can opt to receive a webhook event that triggers when an organization owner or repository administrator enables or disables a code security or analysis feature. For more information, see the following documentation.
+          
+          - "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#security_and_analysis)" in the webhook documentation
+          - "[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)"
+          - "[Managing security and analysis features for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)"
+
+        # https://github.com/github/releases/issues/2191
+        - |
+          Users on an instance with a GitHub Advanced Security license can optionally add a comment when dismissing a code scanning alert in the web UI or via the REST API. Dismissal comments appear in the event timeline. Users can also add or retrieve a dismissal comment via the REST API. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests#dismissing-an-alert-on-your-pull-request)" and "[Code Scanning](/rest/code-scanning#update-a-code-scanning-alert)" in the REST API documentation.
+
+        # https://github.com/github/releases/issues/2228
+        - |
+          On instances with a GitHub Advanced Security license, secret scanning prevents the leak of secrets in the web editor. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-web-ui)."
+
+        # https://github.com/github/releases/issues/2318
+        # https://github.com/github/releases/issues/2277
+        - |
+          Enterprise owners and users on an instance with a GitHub Advanced Security license can view secret scanning alerts and bypasses of secret scanning's push protection in the enterprise and organization audit logs, and via the REST API. For more information, see the following documentation.
+          
+          - "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)"
+          - "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#secret_scanning_push_protection-category-actions)"
+          - "[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#secret_scanning_push_protection-category-actions)"
+          - "[Secret Scanning](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)" in the REST API documentation
+
+        # https://github.com/github/releases/issues/2230
+        # https://github.com/github/releases/issues/2317
+        - |
+          Enterprise owners on an instance with a GitHub Advanced Security license can perform dry runs of custom secret scanning patterns for the enterprise, and all users can perform dry runs when editing a pattern. Dry runs allow you to understand a pattern's impact across the entire instance and hone the pattern before publication and generation of alerts. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+
+        # https://github.com/github/releases/issues/2236
+        - |
+          Users on an instance with a GitHub Advanced Security license can use `sort` and `direction` parameters in the REST API when retrieving secret scanning alerts, and sort based on the alert’s `created` or `updated` fields. The new parameters are available for the entire instance, or for individual organizations or repositories. For more information, see the following documentation.
+          
+          - "[List secret scanning alerts for an enterprise](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)"
+          - "[List secret scanning alerts for an organization](/rest/secret-scanning#list-secret-scanning-alerts-for-an-organization)"
+          - "[List secret scanning alerts for a repository](/rest/secret-scanning#list-secret-scanning-alerts-for-a-repository)"
+          - "[Secret Scanning](/rest/secret-scanning)" in the REST API documentation
+
+        # https://github.com/github/releases/issues/2263
+        - |
+          The contents of the `github/codeql-go` repository have moved to the `github/codeql` repository, to live alongside similar libraries for all other programming languages supported by CodeQL. The open-source CodeQL queries, libraries, and extractor for analyzing codebases written in the Go programming language with GitHub's CodeQL code analysis tools can now be found in the new location. For more information, including guidance on migrating your existing workflows, see [github/codeql-go#741](https://github.com/github/codeql-go/issues/741).
+
+    - heading: Dependabot
+      notes:
+        # https://github.com/github/releases/issues/2256
+        - |
+          Enterprise owners on instances with a GitHub Advanced Security license can see an overview of Dependabot alerts for the entire instance, including a repository-centric view of application security risks, and an alert-centric view of all secret scanning and Dependabot alerts. The views are in beta and subject to change, and alert-centric views for code scanning are planned for a future release of GitHub Enterprise Server. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview#viewing-the-security-overview-for-an-enterprise)."
+
+        # https://github.com/github/releases/issues/1993
+        - |
+          Dependabot alerts show users if repository code calls vulnerable functions. Individual alerts display a "vulnerable call" label and code snippet, and users can filter search by `has:vulnerable-calls`. Vulnerable functions are curated during publication to the [GitHub Advisory Database](https://github.com/advisories). New incoming Python advisories will be supported, and GitHub is backfilling known vulnerable functions for historical Python advisories. After beta testing with Python, GitHub will add support for other ecosystems. For more information, see "[Viewing and updating Dependabot alerts](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)."
+
+        # https://github.com/github/releases/issues/2160
+        - |
+          Users can select multiple Dependabot alerts, then dismiss or reopen or dismiss the alerts. For example, from the **Closed alerts** tab, you can select multiple alerts that have been previously dismissed, and then reopen them all at once. For more information, see "[About Dependabot alerts](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."
+
+        # https://github.com/github/releases/issues/2232
+        - |
+          Dependabot updates `@types` dependencies alongside corresponding packages in TypeScript projects. Before this change, users would see separate pull requests for a package and the corresponding `@types` package. This feature is automatically enabled for repositories containing `@types` packages in the project's `devDependencies` within the _package.json_ file. You can disable this behavior by setting the [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore) field in your `dependabot.yml` file to `@types/*`. For more information, see "[About Dependabot version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)" and "[Configuration options for the _dependabot.yml_ file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file)."
+
+    - heading: Code security
+      notes:
+        # https://github.com/github/releases/issues/2098
+        # https://github.com/github/releases/issues/2282
+        - |
+          GitHub Actions can enforce dependency reviews on users' pull requests by scanning for dependencies, and will warn users about associated security vulnerabilities. The `dependency-review-action` action is supported by a new API endpoint that diffs the dependencies between any two revisions. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)."
+
+        # https://github.com/github/releases/issues/2243
+        - |
+          The dependency graph detects _Cargo.toml_ and _Cargo.lock_ files for Rust. These files will be displayed in the **Dependency graph** section of the **Insights** tab. Users will receive Dependabot alerts and updates for vulnerabilities associated with their Rust dependencies. Package metadata, including mapping packages to repositories, will be added at a later date. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
+
+        # https://github.com/github/releases/issues/1766
+        - |
+          If GitHub Connect is enabled for your instance, users can contribute an improvement to a security advisory in the [GitHub Advisory Database](https://github.com/advisories). To contribute, click **Suggest improvements for this vulnerability** while viewing an advisory's details. For more information, see the following articles.
+          
+          - "[Managing GitHub Connect](/admin/configuration/configuring-github-connect/managing-github-connect)"
+          - "[Browsing security vulnerabilities in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+          - "[About GitHub Security Advisories for repositories](/enterprise-cloud@latest/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)" in the GitHub Enterprise Cloud documentation
+          - "[Editing security advisories in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+
+    - heading: GitHub Actions
+      notes:
+        # https://github.com/github/releases/issues/2159
+        - |
+          Within a workflow that calls a reusable workflow, users can pass the secrets to the reusable workflow with `secrets: inherit`. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow)."
+
+        # https://github.com/github/releases/issues/2102
+        - |
+          When using GitHub Actions, to reduce the risk of merging a change that was not reviewed by another person into a protected branch, enterprise owners and repository administrators can prevent Actions from creating pull requests. Organization owners could previously enable this restriction. For more information, see the following articles.
+
+          - "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)"
+          - "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-creating-or-approving-pull-requests)"
+          - "[Managing GitHub 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)"
+
+        # https://github.com/github/releases/issues/2155
+        - |
+          Users can write a single workflow triggered by `workflow_dispatch` and `workflow_call`, and use the `inputs` context to access input values. Previously, `workflow_dispatch` inputs were in the event payload, which increased difficulty for workflow authors who wanted to write one workflow that was both reusable and manually triggered. For workflows triggered by `workflow_dispatch`, inputs are still available in the `github.event.inputs` context to maintain compatibility.  For more information, see "[Contexts](/actions/learn-github-actions/contexts#inputs-context)."
+
+        # https://github.com/github/releases/issues/2103
+        - |
+          To summarize the result of a job, users can generate Markdown and publish the contents as a job summary. For example, after running tests with GitHub Actions, a summary can provide an overview of passed, failed, or skipped tests, potentially reducing the need to review the full log output. For more information, see "[Workflow commands for GitHub Actions](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)."
+
+        # https://github.com/github/releases/issues/2161
+        - |
+          To more easily diagnose job execution failures during a workflow re-run, users can enable debug logging, which outputs information about a job's execution and environment. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)" and "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
+
+        # https://github.com/github/releases/issues/2140
+        - |
+          If you manage self-hosted runners for GitHub Actions, you can ensure a consistent state on the runner itself before and after a workflow run by defining scripts to execute. By using scripts, you no longer need to require that users manually incorporate these steps into workflows. Pre- and post-job scripts are in beta and subject to change. For more information, see "[Running scripts before or after a job](/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job)."
+
+    - heading: GitHub Packages
+      notes:
+        # https://github.com/github/releases/issues/2334
+        - |
+          Enterprise owners can migrate container images from the GitHub Docker registry to the GitHub Container registry. The Container registry provides the following benefits.
+          
+          - Improves the sharing of containers within an organization
+          - Allows the application of granular access permissions
+          - Permits the anonymous sharing of public container images
+          - Implements OCI standards for hosting Docker images
+          
+          The Container registry is in beta and subject to change. For more information, see "[Migrating your enterprise to the Container registry from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)."
+
+    - heading: Community experience
+      notes:
+        # https://github.com/github/releases/issues/2113
+        - |
+          GitHub Discussions is available for GitHub Enterprise Server. GitHub Discussions provides a central gathering space to ask questions, share ideas, and build connections. For more information, see "[GitHub Discussions](/discussions)."
+
+        # https://github.com/github/releases/issues/2259
+        - |
+          Enterprise owners can configure a policy to control whether people's usernames or full names are displayed within internal or public repositories. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-display-of-member-names-in-your-repositories)."
+
+    - heading: Organizations
+      notes:
+        # https://github.com/github/releases/issues/2019
+        - |
+          Users can create member-only READMEs for an organization. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."
+
+        # https://github.com/github/releases/issues/2234
+        - |
+          Organization owners can pin a repository to an organization's profile directly from the repository via the new **Pin repository** dropdown. Pinned public repositories appear to all users of your instance, while public, private, and internal repositories are only visible to organization members.
+
+    - heading: Repositories
+      notes:
+        # https://github.com/github/releases/issues/2214
+        - |
+          While creating a fork, users can customize the fork's name. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
+
+        # https://github.com/github/releases/issues/1973
+        - |
+          Users can block creation of branches that match a configured name pattern with the **Restrict pushes that create matching branches** branch protection rule. For example, if a repository's default branch changes from `master` to `main`, a repository administrator can prevent any subsequent creation or push of the `master` branch. For more information, see 
+          "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#restrict-who-can-push-to-matching-branches)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)."
+
+        # https://github.com/github/releases/issues/2179
+        - |
+          Users can create a branch directly from a repository's **Branches** page by clicking the **New branch**. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+
+        # https://github.com/github/releases/issues/2220
+        - |
+          Users can delete a branch that's associated with an open pull request. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+
+        # https://github.com/github/releases/issues/2118
+        - |
+          Repositories with multiple licenses display all of the licenses in the "About" sidebar on the {% octicon "code" aria-label="The code icon" %} **Code** tab. For more information, see "[Licensing a repository](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository)."
+
+        # https://github.com/github/releases/issues/2233
+        - When a user renames or moves a file to a new directory, if at least half of the file's contents are identical, the commit history indicates that the file was renamed, similar to `git log --follow`. For more information, see the [GitHub Blog](https://github.blog/changelog/2022-06-06-view-commit-history-across-file-renames-and-moves/).
+
+        # https://github.com/github/releases/issues/2093
+        - |
+          Users can require a successful deployment of a branch before anyone can merge the pull request associated with the branch. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-deployments-to-succeed-before-merging)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+        # https://github.com/github/releases/issues/2073
+        - |
+          Enterprise owners can prevent organization owners from inviting collaborators to repositories on the instance. For more information, see "[Enforcing a policy for inviting collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)."
+
+        # https://github.com/github/releases/issues/2173
+        - |
+          Users can grant exceptions to GitHub Apps for any branch protection rule that supports exceptions. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+    - heading: Commits
+      notes:
+        # https://github.com/github/releases/issues/2306
+        - |
+          For public GPG signing keys that are expired or revoked, GitHub Enterprise Server verifies Git commit signatures and show commits as verified if the user made the commit while the key was still valid. Users can also upload expired or revoked GPG keys. For more information, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
+
+        # https://github.com/github/releases/issues/1977
+        - |
+          To affirm that a commit complies with the rules and licensing governing a repository, organization owners and repository administrators can now require developers to sign off on commits made through the web interface. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)" and "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
+    - heading: Pull requests
+      notes:
+        # https://github.com/github/releases/issues/2261
+        - |
+          Using the file tree located in the **Files changed** tab of a pull request, users can navigate modified files, understand the size and scope of changes, and focus reviews. The file tree appears if a pull request modifies at least two files, and the browser window is sufficiently wide. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" and "[Filtering files in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+
+        # https://github.com/github/releases/issues/2167
+        - |
+          Users can default to using pull requests titles as the commit message for all squash merges. For more information, see "[Configuring commit squashing for pull requests](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)."
+
+    - heading: Releases
+      notes:
+        # https://github.com/github/releases/issues/2281
+        - |
+          When viewing the details for a particular release, users can see the creation date for each release asset. For more information, see "[Viewing your repository's releases and tags](/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
+
+        # https://github.com/github/releases/issues/2279
+        - While creating a release with automatically generated release notes, users can see the tag identified as the previous release, then choose to select a different tag to specify as the previous release. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
+
+    - heading: Markdown
+      notes:
+        # https://github.com/github/releases/issues/2260
+        - |
+          Editing Markdown in the web interface has been improved.
+          
+          - After a user selects text and pastes a URL, the selected text will become a Markdown link to the pasted URL.
+          - When a user pastes spreadsheet cells or HTML tables, the resulting text will render as a table.
+          - When a user copies text containing links, the pasted text will include the link as a Markdown link.
+
+          For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#links)."
+
+        # https://github.com/github/releases/issues/2258
+        - |
+          When editing a Markdown file in the web interface, clicking the **Preview** tab will automatically scroll to the place in the preview that you were editing. The scroll location is based on the position of your cursor before you clicked the **Preview** tab.
+
+  changes:
+    - Interactive elements in the web interface such as links and buttons show a visible outline when focused with a keyboard, to help users find the current position on a page. In addition, when focused, form fields have a higher contrast outline.
+    - If a user refreshes the page while creating a new issue or pull request, the assignees, reviewers, labels and projects will all be preserved.
+
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+    - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+    - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+    - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+    - In some cases, users cannot convert existing issues to discussions.
+    - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
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 dbea6d921e..0521e3dd4a 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,4 +1,4 @@
-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`.
+Predeterminadamente, {% data variables.product.product_name %} maximizará la cantidad de jobs que se ejecutan en paralelo, dependiendo de la disponibilidad del ejecutor. 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`.
 
 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.
 
diff --git a/translations/es-ES/data/reusables/actions/publish-to-packages-workflow-step.md b/translations/es-ES/data/reusables/actions/publish-to-packages-workflow-step.md
index f7b7c88a46..b477b3efb9 100644
--- a/translations/es-ES/data/reusables/actions/publish-to-packages-workflow-step.md
+++ b/translations/es-ES/data/reusables/actions/publish-to-packages-workflow-step.md
@@ -1 +1 @@
-Ejecuta el comando `mvn --batch-mode deploy` para publicar a {% data variables.product.prodname_registry %}. La variable de ambiente `GITHUB_TOKEN` se configurará con el contenido del secreto `GITHUB_TOKEN`. The `permissions` key specifies the access granted to the `GITHUB_TOKEN`.
+Ejecuta el comando `mvn --batch-mode deploy` para publicar a {% data variables.product.prodname_registry %}. La variable de ambiente `GITHUB_TOKEN` se configurará con el contenido del secreto `GITHUB_TOKEN`. La clave `permissions` especifica el acceso otorgado al `GITHUB_TOKEN`.
diff --git a/translations/es-ES/data/reusables/actions/self-hosted-runner-list.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-list.md
index 6e53ef0e5b..59de8c675d 100644
--- a/translations/es-ES/data/reusables/actions/self-hosted-runner-list.md
+++ b/translations/es-ES/data/reusables/actions/self-hosted-runner-list.md
@@ -1 +1 @@
-1. Locate the list of runners under "Runners".
+1. Ubica el reto de los ejecutores debajo de "Ejecutores".
diff --git a/translations/es-ES/data/reusables/actions/self-hosted-runner-removing-a-runner.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-removing-a-runner.md
index ea0d946b8e..612b01600d 100644
--- a/translations/es-ES/data/reusables/actions/self-hosted-runner-removing-a-runner.md
+++ b/translations/es-ES/data/reusables/actions/self-hosted-runner-removing-a-runner.md
@@ -1,4 +1,4 @@
-1. Under "Runners", locate the runner in the list. Si tu ejecutor está en un grupo, da clic en {% octicon "chevron-down" aria-label="The downwards chevron" %} para expandir la lista.
+1. Debajo de "Ejecutores", ubica el ejecutor en la lista. Si tu ejecutor está en un grupo, da clic en {% octicon "chevron-down" aria-label="The downwards chevron" %} para expandir la lista.
 1. Da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al ejecutor que quieres eliminar, y luego da clic en **Eliminar**.
 
     ![Eliminar una configuración de ejecutor autoalojado](/assets/images/help/settings/actions-runner-remove.png)
diff --git a/translations/es-ES/data/reusables/actions/supported-github-runners.md b/translations/es-ES/data/reusables/actions/supported-github-runners.md
index 36607897ca..edd94968e7 100644
--- a/translations/es-ES/data/reusables/actions/supported-github-runners.md
+++ b/translations/es-ES/data/reusables/actions/supported-github-runners.md
@@ -84,7 +84,7 @@ macOS Catalina 10.15 <sup>[deprecated]</sup>
 <code>macos-10.15</code>
 </td>
 <td>
-Migrate to <code>macOS-11</code> or <code>macOS-12</code>. For more information, see <A href="https://github.blog/changelog/2022-07-20-github-actions-the-macos-10-15-actions-runner-image-is-being-deprecated-and-will-be-removed-by-8-30-22/">this GitHub blog post</A>.
+Migra a <code>macOS-11</code> o <code>macOS-12</code>. Para obtener más información, consulta <A href="https://github.blog/changelog/2022-07-20-github-actions-the-macos-10-15-actions-runner-image-is-being-deprecated-and-will-be-removed-by-8-30-22/">esta publicación del blog de GitHub</A>.
 </td>
 </tr>
 </tbody>
diff --git a/translations/es-ES/data/reusables/advisory-database/beta-malware-advisories.md b/translations/es-ES/data/reusables/advisory-database/beta-malware-advisories.md
index 94fc49a4c6..3c274857bb 100644
--- a/translations/es-ES/data/reusables/advisory-database/beta-malware-advisories.md
+++ b/translations/es-ES/data/reusables/advisory-database/beta-malware-advisories.md
@@ -1,5 +1,5 @@
-{% note %}
+{% ifversion GH-advisory-db-supports-malware %}{% note %}
 
 **Note:** Advisories for malware are currently in beta and subject to change.
 
-{% endnote %}
+{% endnote %}{% endif %}
diff --git a/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md b/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md
index 6b720eba4e..3d916a4ce7 100644
--- a/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md
+++ b/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md
@@ -5,7 +5,7 @@
 | `account` | Contains activities related to an organization account. | `advisory_credit`   | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".
 {%- endif %}
 | `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts.
-{%- ifversion ghec %}
+{%- ifversion audit-log-streaming %}
 | `audit_log_streaming`  | Contains activities related to streaming audit logs for organizations in an enterprise account.
 {%- endif %}
 {%- ifversion fpt or ghec %}
@@ -42,17 +42,17 @@
 | `dotcom_connection` | Contains activities related to {% data variables.product.prodname_github_connect %}. | `enterprise` | Contains activities related to enterprise settings.
 {%- endif %}
 {%- ifversion ghec %}
-| `enterprise_domain` | Contains activities related to verified enterprise domains. | `enterprise_installation` | Contains activities related to {% data variables.product.prodname_github_app %}s associated with an {% data variables.product.prodname_github_connect %} enterprise connection.
+| `enterprise_domain` | Contains activities related to verified enterprise domains. | `enterprise_installation` | Contiene actividades relacionadas con las {% data variables.product.prodname_github_app %}asociadas con una conexión de empresa de {% data variables.product.prodname_github_connect %}.
 {%- endif %}
 {%- ifversion fpt or ghec %}
-| `environment` | Contains activities related to {% data variables.product.prodname_actions %} environments.
+| `environment` | Contiene actividades relacionadas con ambientes de {% data variables.product.prodname_actions %}.
 {%- endif %}
 {%- ifversion ghae %}
-| `external_group` | Contains activities related to Okta groups. | `external_identity` | Contains activities related to a user in an Okta group.
+| `external_group` | Contiene actividades relacionadas con grupos de Okta. | `external_identity` | Contiene actividades relacionadas con un usuario en un grupo de Okta.
 {%- endif %}
-| `gist` | Contains activities related to Gists. | `git` | Contains activities related to Git events. | `hook` | Contains activities related to webhooks. | `integration` | Contains activities related to integrations in an account. | `integration_installation` | Contains activities related to integrations installed in an account. | `integration_installation_request`  | Contains activities related to organization member requests for owners to approve integrations for use in the organization.
+| `gist` | Contiene actividades relacionadas con Gists. | `git` | Contiene actividades relacionadas con eventos de Git. | `hook` | Contiene actividades relacionadas con webhooks. | `integration` | Contiene actividades relacionadas con integraciones en una cuenta. | `integration_installation` | Contiene actividades relacionadas con integraciones instaladas en una cuenta. | `integration_installation_request`  | Contiene actividades relacionadas con solicitudes de miembros organizacionales para que los propietarios aprueben integraciones para su uso en la organización.
 {%- ifversion ghec or ghae %}
-| `ip_allow_list`   | Contains activities related to enabling or disabling the IP allow list for an organization. | `ip_allow_list_entry`   | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.
+| `ip_allow_list`   | Contiene actividades relacionadas con habilitar o inhabilitar la lista de direcciones IP permitidas en una organización. | `ip_allow_list_entry`   | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.
 {%- endif %}
 | `issue`  | Contains activities related to pinning, transferring, or deleting an issue in a repository. | `issue_comment` | Contains activities related to pinning, transferring, or deleting issue comments. | `issues` | Contains activities related to enabling or disabling issue creation for an organization.
 {%- ifversion fpt or ghec %}
diff --git a/translations/es-ES/data/reusables/code-scanning/about-analysis-origins-link.md b/translations/es-ES/data/reusables/code-scanning/about-analysis-origins-link.md
index 6226acfa4c..d5e08bf318 100644
--- a/translations/es-ES/data/reusables/code-scanning/about-analysis-origins-link.md
+++ b/translations/es-ES/data/reusables/code-scanning/about-analysis-origins-link.md
@@ -1 +1 @@
-If you run code scanning using multiple configurations, then sometimes an alert will have multiple analysis origins. If an alert has multiple analysis origins, you can view the status of the alert for each analysis origin on the alert page. Para obtener más información, consulta la sección "[Acerca de los orígenes de análisis](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)".
+Si ejecutas el escaneo de código utilizando configuraciones múltiples, entonces algunas veces una alerta tendrá varios orígenes de análisis. Si una alerta tiene varios orígenes de análisis, puedes ver el estado de la alerta para cada uno de ellos en la página de alertas. Para obtener más información, consulta la sección "[Acerca de los orígenes de análisis](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)".
diff --git a/translations/es-ES/data/reusables/discussions/about-organization-discussions.md b/translations/es-ES/data/reusables/discussions/about-organization-discussions.md
index c9964a9b33..08628cb121 100644
--- a/translations/es-ES/data/reusables/discussions/about-organization-discussions.md
+++ b/translations/es-ES/data/reusables/discussions/about-organization-discussions.md
@@ -1,5 +1,5 @@
 When you enable organization discussions, you will choose a repository in the organization to be the source repository for your organization discussions. You can use an existing repository or create a repository specifically to hold your organization discussions. Discussions will appear both on the discussions page for the organization and on the discussion page for the source repository.
 
-Permission to participate in or manage discussion in your organization is based on permission in the source repository. For example, a user needs write permission to the source repository in order to delete an organization discussion. This is identical to how a user needs write permission in a repository in order to delete a repository discussion.
+Permission to participate in or manage discussions in your organization is based on permission in the source repository. For example, a user needs write permission to the source repository in order to delete an organization discussion. This is identical to how a user needs write permission in a repository in order to delete a repository discussion.
 
 You can change the source repository at any time. If you change the source repository, discussions are not transferred to the new source repository.
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/packages-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/packages-tab.md
new file mode 100644
index 0000000000..33b2a48ea9
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise-accounts/packages-tab.md
@@ -0,0 +1 @@
+1. En la barra lateral izquierda, da clic en **Paquetes**.
diff --git a/translations/es-ES/data/reusables/enterprise/about-ssh-ports.md b/translations/es-ES/data/reusables/enterprise/about-ssh-ports.md
new file mode 100644
index 0000000000..8c1324e355
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise/about-ssh-ports.md
@@ -0,0 +1,5 @@
+Each {% data variables.product.product_name %} instance accepts SSH connections over two ports. Site administrators can access the administrative shell via SSH, then run command-line utilities, troubleshoot, and perform maintenance. Users can connect via SSH to access and write Git data in the instance's repositories. Users do not have shell access to your instance. Para obtener más información, consulta los siguientes artículos.
+
+- "[Puertos de red](/admin/configuration/configuring-network-settings/network-ports)"
+- "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)"
+- "[Acerca de SSH](/authentication/connecting-to-github-with-ssh/about-ssh)"
diff --git a/translations/es-ES/data/reusables/enterprise/apply-configuration.md b/translations/es-ES/data/reusables/enterprise/apply-configuration.md
new file mode 100644
index 0000000000..b3069f0be9
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise/apply-configuration.md
@@ -0,0 +1,12 @@
+1. To apply the configuration, enter the following command.
+
+   {% note %}
+
+   **Note**: During a configuration run, services on {% data variables.product.product_location %} may restart, which can cause brief downtime for users.
+
+   {% endnote %}
+
+    ```shell
+    ghe-config-apply
+    ```
+1. Espera a que la configuración se ejecute por completo.
diff --git a/translations/es-ES/data/reusables/enterprise/repository-caching-release-phase.md b/translations/es-ES/data/reusables/enterprise/repository-caching-release-phase.md
index d70f2915de..4b0171d090 100644
--- a/translations/es-ES/data/reusables/enterprise/repository-caching-release-phase.md
+++ b/translations/es-ES/data/reusables/enterprise/repository-caching-release-phase.md
@@ -1,5 +1,7 @@
+{% ifversion ghes < 3.6 %}
 {% note %}
 
 **Nota:** El almacenamiento en caché del repositorio se encuentra actualmente en beta y está sujeto a cambios.
 
 {% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md
index cc637934c0..f194257ff4 100644
--- a/translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md
+++ b/translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md
@@ -1,4 +1,5 @@
-1. SSH en {% data variables.product.product_location %}. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
-```shell
-$ ssh -p 122 admin@<em>HOSTNAME</em>
-```
+1. SSH en {% data variables.product.product_location %}. If your instance comprises multiple nodes, for example if high availability or geo-replication are configured, SSH into the primary node. If you use a cluster, you can SSH into any node. For more information about SSH access, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+
+   ```shell
+   $ ssh -p 122 admin@<em>HOSTNAME</em>
+   ```
diff --git a/translations/es-ES/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md b/translations/es-ES/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
index dc896f8db4..0c777ed144 100644
--- a/translations/es-ES/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
+++ b/translations/es-ES/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
@@ -1,5 +1,9 @@
 {% warning %}
 
-**Nota:** Si habilitas al acceso de lectura anónimo de Git, eres responsable de todos los accesos y usos de esta característica. {% data variables.product.company_short %} no será responsable de ningún acceso no deseado o uso indebido de la función. También puede que no utilices esta característica para violar tu licencia desde {% data variables.product.company_short %}, incluyendo el límite de la cantidad de licencias de usuario que has comprado con nosotros.
+**Advertencias:**
+
+- The Git protocol is unauthenticated and unencrypted. An attacker could intercept repository data transferred over connections using this protocol.
+- If you enable anonymous Git read access, you're responsible for all access and use of the feature. {% data variables.product.company_short %} is not responsible for any unintended access, security risks, or misuse of the feature.
+- You may not use this feature to violate your license from {% data variables.product.company_short %}, including the limit on the number of user licenses for {% data variables.product.product_location %}.
 
 {% endwarning %}
diff --git a/translations/es-ES/data/reusables/gated-features/copilot.md b/translations/es-ES/data/reusables/gated-features/copilot.md
index 22bff59ff4..d5cec1f417 100644
--- a/translations/es-ES/data/reusables/gated-features/copilot.md
+++ b/translations/es-ES/data/reusables/gated-features/copilot.md
@@ -1 +1 @@
-{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_copilot %} is free to use for verified students and open source maintainers. If you are not a student or open source maintainer, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. Para obtener más información, consulta la sección "[Acerca de la facturación para el {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)".
+{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_copilot %} is free to use for verified students and open source maintainers. If you are not a student or open source maintainer, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. Después del periodo de prueba gratuito, necesitarás una suscripción de pago para uso continuo. Para obtener más información, consulta la sección "[Acerca de la facturación para el {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)".
diff --git a/translations/es-ES/data/reusables/gated-features/discussions.md b/translations/es-ES/data/reusables/gated-features/discussions.md
deleted file mode 100644
index 618609343f..0000000000
--- a/translations/es-ES/data/reusables/gated-features/discussions.md
+++ /dev/null
@@ -1 +0,0 @@
-Los {% data variables.product.prodname_discussions %} están disponibles para los repositorios públicos y privados en {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %}
diff --git a/translations/es-ES/data/reusables/package_registry/container-registry-benefits.md b/translations/es-ES/data/reusables/package_registry/container-registry-benefits.md
new file mode 100644
index 0000000000..079a514846
--- /dev/null
+++ b/translations/es-ES/data/reusables/package_registry/container-registry-benefits.md
@@ -0,0 +1 @@
+The {% data variables.product.prodname_container_registry %} stores container images within your organization or personal account, and allows you to associate an image with a repository. You can choose whether to inherit permissions from a repository, or set granular permissions independently of a repository. You can also access public container images anonymously.
diff --git a/translations/es-ES/data/reusables/package_registry/container-registry-ghes-migration-availability.md b/translations/es-ES/data/reusables/package_registry/container-registry-ghes-migration-availability.md
new file mode 100644
index 0000000000..5d685d5f4f
--- /dev/null
+++ b/translations/es-ES/data/reusables/package_registry/container-registry-ghes-migration-availability.md
@@ -0,0 +1 @@
+{% data variables.product.product_name %} 3.6 supports migration for Docker images stored in organizations. A future release will support migration of user-owned images.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/package_registry/container-registry-migration-namespaces.md b/translations/es-ES/data/reusables/package_registry/container-registry-migration-namespaces.md
new file mode 100644
index 0000000000..9d7d0dc5e0
--- /dev/null
+++ b/translations/es-ES/data/reusables/package_registry/container-registry-migration-namespaces.md
@@ -0,0 +1 @@
+Any scripts or {% data variables.product.prodname_actions %} workflows that use the namespace for the Docker registry, {% data variables.product.prodname_docker_registry_namespace %}, will continue to work after migration to the {% data variables.product.prodname_container_registry %} at {% data variables.product.prodname_container_registry_namespace %}.
diff --git a/translations/es-ES/data/reusables/package_registry/container-registry-replaces-docker-registry.md b/translations/es-ES/data/reusables/package_registry/container-registry-replaces-docker-registry.md
new file mode 100644
index 0000000000..5b6ed35c4f
--- /dev/null
+++ b/translations/es-ES/data/reusables/package_registry/container-registry-replaces-docker-registry.md
@@ -0,0 +1 @@
+The {% data variables.product.prodname_container_registry %} replaces {% data variables.product.company_short %}'s Docker registry.
diff --git a/translations/es-ES/data/reusables/package_registry/verify_repository_field.md b/translations/es-ES/data/reusables/package_registry/verify_repository_field.md
index c29ac87889..c2f7adbdf5 100644
--- a/translations/es-ES/data/reusables/package_registry/verify_repository_field.md
+++ b/translations/es-ES/data/reusables/package_registry/verify_repository_field.md
@@ -1 +1 @@
-1. Verifica el campo `repository` en el *package.json*. de tu proyecto. El campo `repository` debe coincidir con la URL de tu repositorio de {% data variables.product.prodname_dotcom %}. Por ejemplo, si la URL de tu repositorio es `github.com/my-org/test`, entonces el campo de repositorio debe ser `git://github.com/my-org/test.git`.
+1. Verifica el campo `repository` en el *package.json*. de tu proyecto. El campo `repository` debe coincidir con la URL de tu repositorio de {% data variables.product.prodname_dotcom %}. For example, if your repository URL is `github.com/my-org/test` then the repository field should be `https://github.com/my-org/test.git`.
diff --git a/translations/es-ES/data/reusables/projects/access-insights.md b/translations/es-ES/data/reusables/projects/access-insights.md
index 37c219cc26..43241b2368 100644
--- a/translations/es-ES/data/reusables/projects/access-insights.md
+++ b/translations/es-ES/data/reusables/projects/access-insights.md
@@ -1,8 +1,8 @@
 1. Navegar a tu proyecto.
-2. In the top-right, to access insights, click {% octicon "graph" aria-label="the graph icon" %}.
+2. Para acceder a las perspectivas, en la parte superior derecha, haz clic en {% octicon "graph" aria-label="the graph icon" %}.
 
     {% note %}
 
-   **Note:** This feature is currently in a private preview and only available for some organizations. If the {% octicon "graph" aria-label="the graph icon" %} icon is not displayed in your project, insights is not yet enabled for your organization.
+   **Nota:** Esta característica se encuentra actualmente en vista previa privada y solo está disponible para algunas organizaciones. Si el icono de {% octicon "graph" aria-label="the graph icon" %} no se muestra en tu proyecto, significa que las perspectivas aún no están habilitadas para tu organización.
 
    {% endnote %} 
diff --git a/translations/es-ES/data/reusables/repositories/commit-signoffs.md b/translations/es-ES/data/reusables/repositories/commit-signoffs.md
new file mode 100644
index 0000000000..1de17f89af
--- /dev/null
+++ b/translations/es-ES/data/reusables/repositories/commit-signoffs.md
@@ -0,0 +1,10 @@
+Compulsory commit signoffs only apply to commits made via the web interface. For commits made via the Git command line interface, the commit author must sign off on the commit using the `--signoff` option. For more information, see the [Git documentation](https://git-scm.com/docs/git-commit).
+
+
+You can determine whether a repository you are contributing to has compulsory commit signoffs enabled by checking the header of the commit form at the bottom of the file you are editing. After compulsory commit signoff has been enabled, the header will read "Sign off and commit changes."
+
+![Screenshot of commit commit form with compulsory signoff enabled](/assets/images/help/commits/commit-form-with-signoff-enabled.png)
+
+Before signing off on a commit, you should ensure that your commit is in compliance with the rules and licensing governing the repository you're committing to. The repository may use a sign off agreement, such as the Developer Certificate of Origin from the Linux Foundation. For more information, see the [Developer Certificate of Origin](https://developercertificate.org/).
+
+Signing off on a commit differs from signing a commit. For more information about signing a commit, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md
index 6cdb0be73c..8e297d7bdd 100644
--- a/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md
+++ b/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md
@@ -1,48 +1,48 @@
-| Proveedor                 | Secreto compatible                                               | Tipo de secreto                                          |
-| ------------------------- | ---------------------------------------------------------------- | -------------------------------------------------------- |
-| Adafruit IO               | Clave de IO de Adafruit                                          | adafruit_io_key                                        |
-| Alibaba Cloud             | ID de Clave de Acceso a la Nube de Alibaba                       | alibaba_cloud_access_key_id                          |
-| Alibaba Cloud             | Secreto de Clave de Acceso a la Nube de Alibaba                  | alibaba_cloud_access_key_secret                      |
-| Amazon                    | ID de cliente de Amazon OAuth                                    | amazon_oauth_client_id                                 |
-| Amazon                    | Secreto de Cliente OAuth de Amazon                               | amazon_oauth_client_secret                             |
-| Amazon Web Services (AWS) | ID de Clave de Acceso de AWS de Amazon                           | aws_access_key_id                                      |
-| Amazon Web Services (AWS) | Clave de Acceso Secreta de AWS de Amazon                         | aws_secret_access_key                                  |
-| Amazon Web Services (AWS) | TOken de Sesión de Amazon AWS                                    | aws_session_token                                      |
-| Amazon Web Services (AWS) | ID de Llave de Acceso Temporal de Amazon AWS                     | aws_temporary_access_key_id                          |
-| Asana                     | Token de Acceso Personal de Asana                                | asana_personal_access_token                            |
-| Atlassian                 | Token de Acceso Personal a Bitbucket Server                      | bitbucket_server_personal_access_token               |
-| Azure                     | Secreto de aplicación de Azure Active Directory                  | azure_active_directory_application_secret            |
-| Azure                     | Caché de Azure para la Llave de Acceso A Redis                   | azure_cache_for_redis_access_key                     |
-| Azure                     | Token de Acceso Personal de Azure DevOps                         | azure_devops_personal_access_token                   |
-| Checkout.com              | Clave secreta de productión de Checkout.com                      | checkout_production_secret_key                         |
-| Clojars                   | Token de Despliegue de Clojars                                   | clojars_deploy_token                                   |
-| Databricks                | Token de Acceso de Databricks                                    | databricks_access_token                                |
-| DigitalOcean              | Token de Acceso Personal de DigitalOcean                         | digitalocean_personal_access_token                     |
-| DigitalOcean              | Token OAuth de DigitalOcean                                      | digitalocean_oauth_token                               |
-| DigitalOcean              | Token de Actualización de DigitalOcean                           | digitalocean_refresh_token                             |
-| DigitalOcean              | Token de Sistema de DigitalOcean                                 | digitalocean_system_token                              |
-| Discord                   | Token de Bot de Discord                                          | discord_bot_token                                      |
-| Doppler                   | Token Personal de Doppler                                        | doppler_personal_token                                 |
-| Doppler                   | Token de Servicio de Doppler                                     | doppler_service_token                                  |
-| Doppler                   | Token de CLI de Doppler                                          | doppler_cli_token                                      |
-| Doppler                   | Token de SCIM de Doppler                                         | doppler_scim_token                                     |
-| Doppler                   | Token de auditoría de Doppler                                    | doppler_audit_token                                    |
-| Dropbox                   | Token de Acceso de Vida Corta de Dropbox                         | dropbox_short_lived_access_token                     |
-| Duffel                    | Token de Acceso En Vivo para Duffel                              | duffel_live_access_token                               |
-| EasyPost                  | Llave de la API de Producción de EasyPost                        | easypost_production_api_key                            |
-| Flutterwave               | Llave de Secreto de la API En Vivo de Flutterwave                | flutterwave_live_api_secret_key                      |
-| Fullstory                 | Llave de la API de FullStory                                     | fullstory_api_key                                      |
-| GitHub                    | Token de Acceso Personal de GitHub                               | github_personal_access_token                           |
-| GitHub                    | Token de Acceso de OAuth para GitHub                             | github_oauth_access_token                              |
-| GitHub                    | Token de Actualización de GitHub                                 | github_refresh_token                                   |
-| GitHub                    | Token de Acceso a la Instalación de GitHub App                   | github_app_installation_access_token                 |
-| GitHub                    | Clave Privada de SSH de GitHub                                   | github_ssh_private_key                                 |
-| Google                    | Secreto de la Llave de Acceso del Almacenamiento de Google Cloud | google_cloud_storage_access_key_secret               |
-| Google                    | Google Cloud Storage Service Account Access Key ID               | google_cloud_storage_service_account_access_key_id |
-| Google                    | Google Cloud Storage User Access Key ID                          | google_cloud_storage_user_access_key_id            |
-| Grafana                   | Clave de la API de Grafana                                       | grafana_api_key                                        |
-| Hubspot                   | Clave de API de Hubspot                                          | hubspot_api_key                                        |
-| Intercom                  | Token de Acceso de Intercom                                      | intercom_access_token                                  |
+| Proveedor                 | Secreto compatible                                                               | Tipo de secreto                                          |
+| ------------------------- | -------------------------------------------------------------------------------- | -------------------------------------------------------- |
+| Adafruit IO               | Clave de IO de Adafruit                                                          | adafruit_io_key                                        |
+| Alibaba Cloud             | ID de Clave de Acceso a la Nube de Alibaba                                       | alibaba_cloud_access_key_id                          |
+| Alibaba Cloud             | Secreto de Clave de Acceso a la Nube de Alibaba                                  | alibaba_cloud_access_key_secret                      |
+| Amazon                    | ID de cliente de Amazon OAuth                                                    | amazon_oauth_client_id                                 |
+| Amazon                    | Secreto de Cliente OAuth de Amazon                                               | amazon_oauth_client_secret                             |
+| Amazon Web Services (AWS) | ID de Clave de Acceso de AWS de Amazon                                           | aws_access_key_id                                      |
+| Amazon Web Services (AWS) | Clave de Acceso Secreta de AWS de Amazon                                         | aws_secret_access_key                                  |
+| Amazon Web Services (AWS) | TOken de Sesión de Amazon AWS                                                    | aws_session_token                                      |
+| Amazon Web Services (AWS) | ID de Llave de Acceso Temporal de Amazon AWS                                     | aws_temporary_access_key_id                          |
+| Asana                     | Token de Acceso Personal de Asana                                                | asana_personal_access_token                            |
+| Atlassian                 | Token de Acceso Personal a Bitbucket Server                                      | bitbucket_server_personal_access_token               |
+| Azure                     | Secreto de aplicación de Azure Active Directory                                  | azure_active_directory_application_secret            |
+| Azure                     | Caché de Azure para la Llave de Acceso A Redis                                   | azure_cache_for_redis_access_key                     |
+| Azure                     | Token de Acceso Personal de Azure DevOps                                         | azure_devops_personal_access_token                   |
+| Checkout.com              | Clave secreta de productión de Checkout.com                                      | checkout_production_secret_key                         |
+| Clojars                   | Token de Despliegue de Clojars                                                   | clojars_deploy_token                                   |
+| Databricks                | Token de Acceso de Databricks                                                    | databricks_access_token                                |
+| DigitalOcean              | Token de Acceso Personal de DigitalOcean                                         | digitalocean_personal_access_token                     |
+| DigitalOcean              | Token OAuth de DigitalOcean                                                      | digitalocean_oauth_token                               |
+| DigitalOcean              | Token de Actualización de DigitalOcean                                           | digitalocean_refresh_token                             |
+| DigitalOcean              | Token de Sistema de DigitalOcean                                                 | digitalocean_system_token                              |
+| Discord                   | Token de Bot de Discord                                                          | discord_bot_token                                      |
+| Doppler                   | Token Personal de Doppler                                                        | doppler_personal_token                                 |
+| Doppler                   | Token de Servicio de Doppler                                                     | doppler_service_token                                  |
+| Doppler                   | Token de CLI de Doppler                                                          | doppler_cli_token                                      |
+| Doppler                   | Token de SCIM de Doppler                                                         | doppler_scim_token                                     |
+| Doppler                   | Token de auditoría de Doppler                                                    | doppler_audit_token                                    |
+| Dropbox                   | Token de Acceso de Vida Corta de Dropbox                                         | dropbox_short_lived_access_token                     |
+| Duffel                    | Token de Acceso En Vivo para Duffel                                              | duffel_live_access_token                               |
+| EasyPost                  | Llave de la API de Producción de EasyPost                                        | easypost_production_api_key                            |
+| Flutterwave               | Llave de Secreto de la API En Vivo de Flutterwave                                | flutterwave_live_api_secret_key                      |
+| Fullstory                 | Llave de la API de FullStory                                                     | fullstory_api_key                                      |
+| GitHub                    | Token de Acceso Personal de GitHub                                               | github_personal_access_token                           |
+| GitHub                    | Token de Acceso de OAuth para GitHub                                             | github_oauth_access_token                              |
+| GitHub                    | Token de Actualización de GitHub                                                 | github_refresh_token                                   |
+| GitHub                    | Token de Acceso a la Instalación de GitHub App                                   | github_app_installation_access_token                 |
+| GitHub                    | Clave Privada de SSH de GitHub                                                   | github_ssh_private_key                                 |
+| Google                    | Secreto de la Llave de Acceso del Almacenamiento de Google Cloud                 | google_cloud_storage_access_key_secret               |
+| Google                    | ID de Llave de Acceso a la Cuenta del Servicio de Almacenamiento de Google Cloud | google_cloud_storage_service_account_access_key_id |
+| Google                    | ID de Llave de Acceso de Usuario al Almacenamiento de Google Cloud               | google_cloud_storage_user_access_key_id            |
+| Grafana                   | Clave de la API de Grafana                                                       | grafana_api_key                                        |
+| Hubspot                   | Clave de API de Hubspot                                                          | hubspot_api_key                                        |
+| Intercom                  | Token de Acceso de Intercom                                                      | intercom_access_token                                  |
 {%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
 JFrog | Token de Acceso a la Plataforma de JFrog | jfrog_platform_access_token JFrog | Llave de la API de la Plataforma de JFrog | jfrog_platform_api_key{% endif %} Ionic | Token de Acceso personal a Ionic | ionic_personal_access_token Ionic | Token de Actualización de Ionic | ionic_refresh_token Linear | Llave de la API de Linear | linear_api_key Linear | Token de Acceso OAuth de Linear | linear_oauth_access_token Midtrans | Llave del Servidor de Producción de Midtrans | midtrans_production_server_key New Relic | Llave de la API Personal de New Relic | new_relic_personal_api_key New Relic | Llave de la API de REST de New Relic | new_relic_rest_api_key New Relic | Llave de Consulta de Perspectivas de New Relic | new_relic_insights_query_key npm | Token de Acceso a npm | npm_access_token NuGet | Llave de la API de NuGet | nuget_api_key Onfido | Token de la API en Vivo de Onfido | onfido_live_api_token OpenAI | Llave de la API de OpenAI | openai_api_key PlanetScale | Contraseña de la Base de Datos de PlanetScale | planetscale_database_password PlanetScale | Token OAuth de PlanetScale | planetscale_oauth_token PlanetScale | Token de Servicio de PlanetScale | planetscale_service_token Postman | Llave de la API de Postman | postman_api_key Proctorio | Llave del Secreto de Proctorio | proctorio_secret_key
 {%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %}
diff --git a/translations/es-ES/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/es-ES/data/reusables/security-advisory/link-browsing-advisory-db.md
index 73d35d1fcf..927dd04cf7 100644
--- a/translations/es-ES/data/reusables/security-advisory/link-browsing-advisory-db.md
+++ b/translations/es-ES/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -1,5 +1 @@
-{% ifversion fpt or ghec %}
-Para obtener más información, consulta la sección "[Buscar asesorías de seguridad en la {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)".
-{% else %}
-Para obtener más información sobre los datos de la asesoría, consulta la sección "[Buscar asesorías de seguridad en la {% data variables.product.prodname_advisory_database %}](/free-pro-team@latest/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)" en la documentación de {% data variables.product.prodname_dotcom_the_website %}.
-{% endif %}
+Para obtener más información, consulta la sección "[Buscar asesorías de seguridad en la {% data variables.product.prodname_advisory_database %}](/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database)".
diff --git a/translations/es-ES/data/reusables/server-statistics/release-phase.md b/translations/es-ES/data/reusables/server-statistics/release-phase.md
deleted file mode 100644
index 17f100fd26..0000000000
--- a/translations/es-ES/data/reusables/server-statistics/release-phase.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note:** {% data variables.product.prodname_server_statistics %} is in public beta and subject to change.
-
-{% endnote %}
diff --git a/translations/es-ES/data/reusables/ssh/about-ssh.md b/translations/es-ES/data/reusables/ssh/about-ssh.md
new file mode 100644
index 0000000000..b4c0c5361a
--- /dev/null
+++ b/translations/es-ES/data/reusables/ssh/about-ssh.md
@@ -0,0 +1 @@
+You can access and write data in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} using SSH (Secure Shell Protocol). When you connect via SSH, you authenticate using a private key file on your local machine.
diff --git a/translations/es-ES/data/reusables/ssh/key-type-support.md b/translations/es-ES/data/reusables/ssh/key-type-support.md
index 54d7a12d90..7975e0efea 100644
--- a/translations/es-ES/data/reusables/ssh/key-type-support.md
+++ b/translations/es-ES/data/reusables/ssh/key-type-support.md
@@ -8,4 +8,21 @@ Desde esta fecha, las llaves DSA (`ssh-dss`) ya no son compatibles. No puedes ag
 Las llaves RSA (`ssh-rsa`) con un `valid_after` anterior al 2 de noviembre de 2021 podrán continuar utilizando cualquier algoritmo de firma. Las llaves RSA que se generaron después de esta fecha deberán utilizar un algoritmo de firma de tipo SHA-2. Algunos clientes más angituos podrían necesitar actualizarse para poder utilizar firmas de tipo SHA-2.
 
 {% endnote %}
-{% endif %}
+
+{% elsif ghes = 3.6 or ghes = 3.7 or ghes = 3.8 %}
+
+{% note %}
+
+**Note**: By default with {% data variables.product.product_name %} 3.6 and later, as of the cutoff date of midnight UTC on August 1, 2022, SSH connections that satisfy **both** of the following conditions will fail.
+
+<br/>
+
+{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %}
+
+{% data variables.product.product_name %} 3.6 and later also does not support SSH connections that use DSA, HMAC-SHA-1, or CBC ciphers. RSA SSH keys uploaded before the cutoff date can continue to authenticate using the SHA-1 hash function as long as the key remains valid. For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
+
+Your site administrator can adjust the cutoff date for connections using RSA-SHA-1, and may block all connections using RSA-SHA-1. For more information, contact your site administrator or see "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md b/translations/es-ES/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md
new file mode 100644
index 0000000000..d2c95da8a5
--- /dev/null
+++ b/translations/es-ES/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md
@@ -0,0 +1,2 @@
+- The RSA key was added to a user account on {% data variables.product.product_location %} after the cutoff date of midnight UTC on August 1, 2022.
+- The SSH client signs the connection attempt with the SHA-1 hash function.
diff --git a/translations/es-ES/data/reusables/user-settings/removes-personal-access-tokens.md b/translations/es-ES/data/reusables/user-settings/removes-personal-access-tokens.md
index d7802bca75..34d3db4707 100644
--- a/translations/es-ES/data/reusables/user-settings/removes-personal-access-tokens.md
+++ b/translations/es-ES/data/reusables/user-settings/removes-personal-access-tokens.md
@@ -1 +1 @@
-As a security precaution, {% data variables.product.company_short %} automatically removes personal access tokens that haven't been used in a year. To provide additional security, we highly recommend adding an expiration to your personal access tokens.
+Como medida de precaución en seguridad, {% data variables.product.company_short %} elimina automáticamente los tokens de acceso personal que no se hayan utilizando en un año. Para proporcionar seguridad adicional, te recomendamos ampliamente que agregues una fecha de vencimiento a tus tokens de acceso personal.
diff --git a/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_location_event_properties.md b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_location_event_properties.md
index b1f98c807e..930910a229 100644
--- a/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_location_event_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_location_event_properties.md
@@ -1,5 +1,5 @@
-| Clave       | Tipo        | Descripción                                                                                                       |
-| ----------- | ----------- | ----------------------------------------------------------------------------------------------------------------- |
-| `Acción`    | `secuencia` | La acción que se realizó. Currently, can only be `created`.                                                       |
-| `ubicación` | `objeto`    | The location involved in the event.                                                                               |
-| `alerta`    | `objeto`    | The [`secret scanning alert`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) involved in the event. |
+| Clave       | Tipo        | Descripción                                                                                                                  |
+| ----------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `Acción`    | `secuencia` | La acción que se realizó. Actualmente, solo puede ser `created`.                                                             |
+| `ubicación` | `objeto`    | La ubicación que se involucra en el evento.                                                                                  |
+| `alerta`    | `objeto`    | La [`alerta del escaneo de secretos`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) involucrada en el evento. |
diff --git a/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md
index 03f31c39f7..3f8d244d6f 100644
--- a/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md
+++ b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md
@@ -1 +1 @@
-Activity related to secret scanning alert locations in a repository. El tipo de actividad se especifica en la propiedad de la acción del objeto de la carga útil. For more information, see the "[secret scanning](/rest/reference/secret-scanning)" REST API.
+La actividad relacionada con las ubicaciones de las alertas del escaneo de secretos en un repositorio. El tipo de actividad se especifica en la propiedad de la acción del objeto de la carga útil. Para obtener más información, consulta API de REST de "[escaneo de secretos](/rest/reference/secret-scanning)".
diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml
index 18a72fb0fb..d956a7ce49 100644
--- a/translations/es-ES/data/ui.yml
+++ b/translations/es-ES/data/ui.yml
@@ -179,7 +179,7 @@ product_landing:
   try_another: Inténtalo con otro archivo o agrega tu ejemplo de código.
   no_result: Lo sentimos, no hay guías que coincidan con tu filtro.
   learn: Aprende cómo agregar un ejemplo de código
-  communities_using_discussions: Comunidades que utilizan debates
+  communities_using_discussions: Communities on GitHub.com using discussions
   add_your_community: Agrega tu comunidad
   sponsor_community: Comunidad de GitHub Sponsors
   supported_releases: Lanzamientos compatibles
diff --git a/translations/es-ES/data/variables/product.yml b/translations/es-ES/data/variables/product.yml
index 2c654e62fb..6ec585da29 100644
--- a/translations/es-ES/data/variables/product.yml
+++ b/translations/es-ES/data/variables/product.yml
@@ -100,6 +100,8 @@ prodname_github_issues: 'Propuestas de GitHub'
 #GitHub Packages
 prodname_registry: 'Registro del paquete de GitHub'
 prodname_container_registry: 'Registro de contenedores'
+prodname_docker_registry_namespace: '{% ifversion fpt or ghec %}`docker.pkg.github.com`{% elsif ghes or ghae %}<code>docker.<em>HOSTNAME</em></code>{% endif %}'
+prodname_container_registry_namespace: '{% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes or ghae %}<code>containers.<em>HOSTNAME</em></code>{% endif %}'
 #GitHub Insights
 prodname_insights: 'GitHub Insights'
 #GitHub Sponsors
diff --git a/translations/es-ES/data/variables/release_candidate.yml b/translations/es-ES/data/variables/release_candidate.yml
index ec65ef6f94..d39e7c0f8d 100644
--- a/translations/es-ES/data/variables/release_candidate.yml
+++ b/translations/es-ES/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
 ---
-version: ''
+version: enterprise-server@3.6
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
index 72c2a7feb7..29c5772885 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
@@ -1,21 +1,50 @@
 ---
 title: Managing accessibility settings
-intro: 'You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.'
+shortTitle: Manage accessibility settings
+intro: '{% data variables.product.product_name %}''s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs.'
 versions:
   feature: keyboard-shortcut-accessibility-setting
 redirect_from:
   - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings
+type: how_to
+miniTocMaxHeadingLevel: 3
 ---
 
 ## About accessibility settings
 
-{% data variables.product.product_name %} includes a variety of keyboard shortcuts so that you can perform actions across the site without using your mouse to navigate. While shortcuts are useful to save time, they can sometimes make {% data variables.product.prodname_dotcom %} harder to use and less accessible.
+To accommodate your vision, hearing, motor, cognitive, or learning needs, you can customize the user interface for {% data variables.product.product_location %}.
 
-All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as <kbd>Control</kbd> or <kbd>Command</kbd>.
+## Managing accessibility settings
 
-## Managing character key shortcuts
+You can decide whether you want to use some or all keyboard shortcuts on {% ifversion fpt or ghec %}{% data variables.product.product_location %}{% elsif ghes or ghae %}the website for {% data variables.product.product_location %}{% endif %}, and you can control the display of animated images.
+
+### Managing keyboard shortcuts
+
+You can perform actions across the {% data variables.product.product_name %} website without using your mouse by using your keyboard instead. Keyboard shortcuts can be useful to save time for some people, but may interfere with accessibility if you don't intend to use the shortcuts.
+
+By default, all keyboard shortcuts are enabled on {% data variables.product.product_name %}. 詳細は「[キーボードのショートカット](/get-started/using-github/keyboard-shortcuts)」を参照してください。
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.accessibility_settings %}
-1. Select or deselect the **Enable character key shortcuts** checkbox. ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png)
-2. [**Save**] をクリックします。
+1. Under "Keyboard shortcuts", manage settings for your keyboard shortcuts.
+
+   - Optionally, to disable or enable shortcut keys that don't use modifiers keys like <kbd>Control</kbd> or <kbd>Command</kbd>, under "General", deselect **Character keys**. If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key.
+{%- ifversion command-palette %}
+   - Optionally, to customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)."
+   {%- endif %}
+
+{% ifversion motion-management %}
+
+### Managing motion
+
+You can control how {% data variables.product.product_name %} displays animated images.
+
+By default, {% data variables.product.product_name %} syncs with your system-level preference for reduced motion. For more information, see the documentation or settings for your operating system.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.accessibility_settings %}
+1. Under "Motion", manage settings for motion.
+
+   - Optionally, to control how {% data variables.product.product_name %} displays animaged images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**.
+
+{% endif %}
diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index bbdcf5a7d3..eb6456168e 100644
--- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -87,12 +87,12 @@ While the job runs, the logs and output can be viewed in the {% data variables.p
 ## サポートされているランナーとハードウェアリソース
 
 Windows および Linux 仮想マシンのハードウェア仕様:
-- 2コアCPU
+- 2-core CPU (x86_64)
 - 7 GB of RAM
 - 14 GB of SSD space
 
 macOS 仮想マシンのハードウェア仕様:
-- 3-core CPU
+- 3-core CPU (x86_64)
 - 14 GB of RAM
 - 14 GB of SSD space
 
diff --git a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md
index dca8e2341d..e68c00e3bc 100644
--- a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -18,7 +18,7 @@ shortTitle: ワークフローをトリガーするイベント
 
 ## About events that trigger workflows
 
-Workflow triggers are events that cause a workflow to run. For more information about how to use workflow triggers, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)."
+ワークフロートリガーは、ワークフローの実行を引き起こすイベントです。 For more information about how to use workflow triggers, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)."
 
 ## Available events
 
@@ -185,7 +185,7 @@ on:
   deployment_status
 ```
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 ### `ディスカッション`
 
 | webhook イベントのペイロード                                                                             | アクティビティタイプ                                                                                                                                                                                                                                                                                              | `GITHUB_SHA`      | `GITHUB_REF` |
diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
index a4bb148ac0..928ee92616 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
@@ -10,8 +10,6 @@ topics:
 shortTitle: Server Statistics
 ---
 
-{% data reusables.server-statistics.release-phase %}
-
 ## {% data variables.product.prodname_server_statistics %}について
 
 {% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.product.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index 07e7034a3b..59f1280ecb 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -737,6 +737,20 @@ git-import-tfs-raw
 git-import-rewrite
 ```
 
+{% ifversion ghes > 3.3 %}
+
+## セキュリティ
+
+### ghe-find-insecure-git-operations
+
+This utility searches your instance's logs and identifies Git operations over SSH that use insecure algorithms or hash functions, including DSA, RSA-SHA-1, HMAC-SHA-1, and CBC ciphers. You can use the output to support each client's transition to a more secure SSH connection. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server){% ifversion ghes < 3.6 %}.{% elsif ghes > 3.5 %} and "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."{% endif %}
+
+```shell
+ghe-find-insecure-git-operations
+```
+
+{% endif %}
+
 ## サポート
 
 ### ghe-diagnostics
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
index 364cbc347c..4c539b1e05 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -73,6 +73,18 @@ Enterprise オーナーは、通知用のメールを設定できます。
 5. テストメールが成功したなら、ページの下部で**Save settings（設定の保存）**をクリックしてください。 ![設定保存のボタン](/assets/images/enterprise/management-console/save-settings.png)
 {% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
 
+{% ifversion require-tls-for-smtp %}
+## Enforcing TLS for SMTP connections
+
+You can enforce TLS encryption for all incoming SMTP connections, which can help satisfy an ISO-27017 certification requirement.
+
+{% data reusables.enterprise_site_admin_settings.email-settings %}
+1. Under "Authentication," select **Enforce TLS auth (recommended)**.
+
+   ![Screenshot of the "Enforce TLS auth (recommended)" checkbox](/assets/images/enterprise/configuration/enforce-tls-for-smtp-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+{% endif %}
+
 ## メール着信を許可する DNS とファイアウォールの設定
 
 通知へのメールでの返信を許可したいなら、DNSを設定しなければなりません。
@@ -80,7 +92,7 @@ Enterprise オーナーは、通知用のメールを設定できます。
 1. インスタンスのポート25がSMTPサーバにアクセスできることを確認してください。
 2. `reply.[hostname]`を指すAレコードを作成してください。 DNSプロバイダとインスタンスのホスト設定によっては、 `*.[hostname]`を指す単一のAレコードを作成できる場合があります。
 3. `reply.[hostname]`を指すMXレコードを作成して、このドメインへのメールがインスタンスにルーティングされるようにしてください。
-4. `noreply.[hostname]` が `[hostname]` を指すようにする MX レコードを作成し、 通知メールの `cc` アドレスへの返信がインスタンスにルーティングされるようにしてください。 詳しい情報については、{% ifversion ghes %}「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}「[メール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}」を参照してください。
+4. `noreply.[hostname]` が `[hostname]` を指すようにする MX レコードを作成し、 通知メールの `cc` アドレスへの返信がインスタンスにルーティングされるようにしてください。 For more information, see {% ifversion ghes %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."
 
 ## メール配信のトラブルシューティング
 
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
new file mode 100644
index 0000000000..dd05637a5b
--- /dev/null
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
@@ -0,0 +1,47 @@
+---
+title: Configuring host keys for your instance
+shortTitle: Configure host keys
+intro: 'You can increase the security of {% data variables.product.product_location %} by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections.'
+permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.'
+versions:
+  ghes: '>= 3.6'
+type: how_to
+topics:
+  - Authentication
+  - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
+  - SSH
+---
+
+## About host keys for your instance
+
+Servers that accept SSH connections advertise one or more cryptographic host keys to securely identify the server to SSH clients. To confirm the server's identity during the initialization of a connection, clients store and verify the host key. For more information, see [SSH Host Key - What, Why, How](https://ssh.com/academy/ssh/host-key) on the SSH Academy website.
+
+{% data reusables.enterprise.about-ssh-ports %}
+
+By default, {% data variables.product.product_location %} generates and advertises host keys with OpenSSH-style host key rotation. To increase the security of SSH in your environment, you can enable additional algorithms for the generation of host keys.
+
+{% note %}
+
+**Note**: If you enable additional host key algorithms, clients that do not use OpenSSH for SSH connections may experience warnings during connection, or fail to connect entirely. Some SSH implementations can ignore unsupported algorithms and fall back to a different algorithm. If the client does not support fallback, the connection will fail. For example, the SSH library for Go does not support fallback to a different algorithm.
+
+{% endnote %}
+
+## Managing an Ed25519 host key
+
+To improve security for clients that connect to {% data variables.product.product_location %}, you can enable the generation and advertisement of an Ed25519 host key. Ed25519 is immune to some attacks that target older signature algorithms, without sacrificing speed. Older SSH clients may not support Ed25519. By default, {% data variables.product.product_name %} instances do not generate or advertise an Ed25519 host key. For more information, see [the Ed25519 website](https://ed25519.cr.yp.to).
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+1. To enable generation and advertisement of the Ed25519 host key, enter the following command.
+
+   ```shell
+   ghe-config app.babeld.host-key-ed25519 true
+   ```
+1. Optionally, enter the following command to disable generation and advertisement of the Ed25519 host key.
+
+   ```shell
+   ghe-config app.babeld.host-key-ed25519 false
+   ```
+{% data reusables.enterprise.apply-configuration %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
new file mode 100644
index 0000000000..88bb5ce695
--- /dev/null
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
@@ -0,0 +1,53 @@
+---
+title: Configuring SSH connections to your instance
+shortTitle: Configure SSH connections
+intro: 'You can increase the security of {% data variables.product.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.'
+permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.'
+versions:
+  ghes: '>= 3.6'
+type: how_to
+topics:
+  - Authentication
+  - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
+  - SSH
+---
+
+## About SSH connections to your instance
+
+{% data reusables.enterprise.about-ssh-ports %}
+
+To accommodate the SSH clients in your environment, you can configure the types of connections that {% data variables.product.product_location %} will accept.
+
+## Configuring SSH connections with RSA keys
+
+When users perform Git operations on {% data variables.product.product_location %} via SSH over port 22, the client can authenticate with an RSA key. The client may sign the attempt using the SHA-1 hash function. In this context, the SHA-1 hash function is no longer secure. For more information, see [SHA-1](https://en.wikipedia.org/wiki/SHA-1) on Wikipedia.
+
+By default{% ifversion ghes < 3.7 %} on {% data variables.product.product_name %} 3.6 and later{% endif %}, SSH connections that satisfy **both** of the following conditions will fail.
+
+{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %}
+
+You can adjust the cutoff date. If the user uploaded the RSA key before the cutoff date, the client can continue to connect successfuly using SHA-1 as long as the key remains valid. Alternatively, you can reject all SSH connections authenticated with an RSA key if the client signs the connection using the SHA-1 hash function.
+
+Regardless of the setting you choose for your instance, clients can continue to connect using any RSA key signed with a SHA-2 hash function.
+
+If you use an SSH certificate authority, connections will fail if the certificate's `valid_after` date is after the cutoff date. 詳しい情報については「[SSH認証局について](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)」を参照してください。
+
+詳細は [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server) を参照してください。
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+1. Audit your instance's logs for connections that use unsecure algorithms or hash functions using the `ghe-find-insecure-git-operations` utility. 詳しい情報については、「[コマンドラインユーティリティ](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-find-insecure-git-operations)」を参照してください。
+1. To configure a cutoff date after which {% data variables.product.product_location %} will deny connections from clients that use an RSA key uploaded after the date if the connection is signed by the SHA-1 hash function, enter the following command. Replace _**RFC-3399-UTC-TIMESTAMP**_ with a valid RFC 3399 UTC timestamp. For example, the default value, August 1, 2022, would be represented as `2022-08-01T00:00:00Z`. For more information, see [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) on the IETF website.
+
+   <pre>
+   $ ghe-config app.gitauth.rsa-sha1 <em>RFC-3339-UTC-TIMESTAMP</em>
+   </pre>
+
+1. Alternatively, to completely disable SSH connections using RSA keys that are signed with the SHA-1 hash function, enter the following command.
+
+   ```shell
+   ghe-config app.gitauth.rsa-sha1 false
+   ```
+{% data reusables.enterprise.apply-configuration %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md
index 74891cb4a8..b59bf2c78b 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md
@@ -25,6 +25,7 @@ children:
   - /site-admin-dashboard
   - /enabling-private-mode
   - /managing-github-mobile-for-your-enterprise
+  - /configuring-ssh-connections-to-your-instance
   - /configuring-email-for-notifications
   - /verifying-or-approving-a-domain-for-your-enterprise
   - /configuring-rate-limits
@@ -34,6 +35,7 @@ children:
   - /command-line-utilities
   - /restricting-network-traffic-to-your-enterprise
   - /configuring-github-pages-for-your-enterprise
+  - /configuring-host-keys-for-your-instance
   - /configuring-the-referrer-policy-for-your-enterprise
   - /configuring-custom-footers
   - /configuring-web-commit-signing
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md
index 40f97d05e0..a3c095be52 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md
@@ -8,6 +8,7 @@ topics:
   - Enterprise
 redirect_from:
   - /admin/configuration/initializing-github-ae
+  - /enterprise-server@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae
 ---
 ## About initialization
 
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index f425311c63..5368353b1d 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -40,7 +40,7 @@ Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions
 Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see "[Using OpenID Connect with reusable workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)."
 {% endif %}
 
-You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)" and "[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)."{% else %}"[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."{% endif %}
+You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining this information longer than audit log data is retained, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)" and "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."{% else %}{% ifversion audit-log-streaming %}"[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)" and {% endif %}"[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."{% endif %}
 
 ![監査ログのエントリ](/assets/images/help/repository/audit-log-entries.png)
 
diff --git a/translations/ja-JP/content/admin/guides.md b/translations/ja-JP/content/admin/guides.md
index 4724e3deb3..67e3be6efe 100644
--- a/translations/ja-JP/content/admin/guides.md
+++ b/translations/ja-JP/content/admin/guides.md
@@ -52,6 +52,8 @@ includeGuides:
   - /admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise
   - /admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise
   - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud
+  - /admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance
+  - /admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance
   - /admin/configuration/enabling-and-scheduling-maintenance-mode
   - /admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise
   - /admin/configuration/enabling-private-mode
diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
index 35436eba62..2bd37c0db0 100644
--- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
+++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
@@ -10,8 +10,6 @@ topics:
   - Enterprise
 ---
 
-{% data reusables.server-statistics.release-phase %}
-
 ## About the benefits of {% data variables.product.prodname_server_statistics %}
 
 {% data variables.product.prodname_server_statistics %} 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 %}.
diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
index 74f6367abd..02ce06f5c7 100644
--- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
+++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
@@ -8,8 +8,6 @@ redirect_from:
   - /early-access/github/analyze-how-your-team-works-with-server-statistics/exploring-server-statistics
 ---
 
-{% 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 %}.
 
 Before you can download this data, you must enable {% data variables.product.prodname_server_statistics %}. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_server_statistics %}の有効化](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)」を参照してください。
@@ -20,7 +18,7 @@ To download these metrics, you must be an enterprise owner or organization owner
   - If {% data variables.product.product_location %} is connected to an enterprise account on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your enterprise account](#downloading-metrics-from-your-enterprise-account)."
   - If {% data variables.product.product_location %} is connected to an organization on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your organization](#downloading-metrics-from-your-organization)."
 
-To learn more about {% data variables.product.prodname_github_connect %}, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)."
+{% data variables.product.prodname_github_connect %}についてさらに学ぶには、「[{% data variables.product.prodname_github_connect %}について](/admin/configuration/configuring-github-connect/about-github-connect)」を参照してください。
 
 ## Downloading metrics from your enterprise account
 
diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
index 5bb42fb99d..5b18a392c4 100644
--- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
+++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
@@ -8,8 +8,6 @@ redirect_from:
   - /early-access/github/analyze-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api
 ---
 
-{% data reusables.server-statistics.release-phase %}
-
 You can request up to 365 days of metrics in a single {% data variables.product.prodname_server_statistics %} REST API request. 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 %}. For a list of the metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)."
 
 Before you can use the {% data variables.product.prodname_server_statistics %} REST API, you must enable {% data variables.product.prodname_server_statistics %}. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_server_statistics %}の有効化](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)」を参照してください。
diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
index 28afdf0355..5b072d3d57 100644
--- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
@@ -39,9 +39,10 @@ As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you
 {%- ifversion enterprise-audit-log-ip-addresses %}
 - You can display the IP address associated with events in the audit log. For more information, see "[Displaying IP addresses in the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise)."
 {%- endif %}
-{%- ifversion ghec %}
+{%- ifversion audit-log-streaming %}
 - You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
-{%- else %}
+{%- endif %}
+{%- ifversion ghes %}
 - You can forward audit and system logs, from your enterprise to an third-party hosted monitoring system. 詳しい情報については、「[ログの転送](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)」を参照してください。
 {%- endif %}
 {%- ifversion ghec or ghes > 3.2 or ghae-issue-6648 %}
@@ -50,13 +51,6 @@ As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you
 
 For a full list of audit log actions that may appear in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
 
-{% ifversion ghec %}
-## Git events
-
-Git events data, such as cloning, fetching, and pushing is logged. For more information, see "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
-
-{% endif %}
-
 ## 参考リンク
 - 「[Organization の Audit log をレビューする](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)」
 {%- ifversion ghes %}
diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
index da858662b4..04345ecf20 100644
--- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
@@ -59,7 +59,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 | ------------------ | --------------------------------------------- |
 | `artifact.destroy` | A workflow run artifact was manually deleted. |
 
-{%- ifversion ghec %}
+{%- ifversion audit-log-streaming %}
 ## `audit_log_streaming` category actions
 
 | アクション                         | 説明                                                                                                                  |
@@ -756,12 +756,12 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 
 ## `prebuild_configuration` category actions
 
-| アクション                                  | 説明                                                                                                                                                                                                                                                                                                               |
-| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `prebuild_configuration.create`        | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was created. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."                      |
-| `prebuild_configuration.destroy`       | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was deleted. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."                      |
-| `prebuild_configuration.run_triggered` | A user initiated a run of a {% data variables.product.prodname_codespaces %} prebuild configuration for a repository branch. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)." |
-| `prebuild_configuration.update`        | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was edited. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."                       |
+| アクション                                  | 説明                                                                                                                                                                                                                                                                                                  |
+| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `prebuild_configuration.create`        | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was created. 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の事前ビルドについて](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)」を参照してください。                      |
+| `prebuild_configuration.destroy`       | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was deleted. 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の事前ビルドについて](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)」を参照してください。                      |
+| `prebuild_configuration.run_triggered` | A user initiated a run of a {% data variables.product.prodname_codespaces %} prebuild configuration for a repository branch. 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の事前ビルドについて](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)」を参照してください。 |
+| `prebuild_configuration.update`        | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was edited. 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の事前ビルドについて](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)」を参照してください。                       |
 {%- endif %}
 
 {%- ifversion ghes %}
diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
index 26668f9a20..817fb15c5f 100644
--- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
@@ -3,7 +3,7 @@ title: Streaming the audit log for your enterprise
 intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
 miniTocMaxHeadingLevel: 3
 versions:
-  ghec: '*'
+  feature: audit-log-streaming
 type: tutorial
 topics:
   - Auditing
@@ -17,6 +17,14 @@ redirect_from:
 permissions: Enterprise owners can configure audit log streaming.
 ---
 
+{% ifversion ghes %}
+{% note %}
+
+**Note:** Audit log streaming is currently in beta for {% data variables.product.product_name %} and is subject to change.
+
+{% endnote %}
+{% endif %}
+
 ## About audit log streaming
 
 To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor:
@@ -24,11 +32,11 @@ To help protect your intellectual property and maintain compliance for your orga
 
 The benefits of streaming audit data include:
 
-* **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account.
-* **Data continuity**. You can pause the stream for up to seven days without losing any audit data.
+* **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account.{% ifversion pause-audit-log-stream %}
+* **Data continuity**. You can pause the stream for up to seven days without losing any audit data.{% endif %}
 * **Data retention**. You can keep your exported audit logs and Git events data as long as you need to.
 
-Enterprise owners can set up, pause, or delete a stream at any time. The stream exports the audit data for all of the organizations in your enterprise.
+Enterprise owners can set up{% ifversion pause-audit-log-stream %}, pause,{% endif %} or delete a stream at any time. The stream exports the audit and Git events data for all of the organizations in your enterprise.
 
 ## Setting up audit log streaming
 
@@ -170,7 +178,7 @@ To configure the stream in {% data variables.product.prodname_dotcom %} you need
 
 1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Blob Storage endpoint.
 
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+   ![エンドポイントのチェック](/assets/images/help/enterprises/audit-stream-check.png)
 
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
@@ -213,7 +221,7 @@ You need two pieces of information about your event hub: its instance name and t
 
 1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Events Hub endpoint.
 
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+   ![エンドポイントのチェック](/assets/images/help/enterprises/audit-stream-check.png)
 
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
@@ -269,9 +277,10 @@ To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must ma
 1. Leave the **Enable SSL verification** check box selected.
 
     Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled.
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Splunk endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png)
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Splunk endpoint. ![エンドポイントのチェック](/assets/images/help/enterprises/audit-stream-check-splunk.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
+{% ifversion pause-audit-log-stream %}
 ## Pausing audit log streaming
 
 Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream.
@@ -284,6 +293,7 @@ Pausing the stream allows you to perform maintenance on the receiving applicatio
 1. A confirmation message is displayed. Click **Pause stream** to confirm.
 
 When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs.
+{% endif %}
 
 ## Deleting the audit log stream
 
diff --git a/translations/ja-JP/content/admin/packages/index.md b/translations/ja-JP/content/admin/packages/index.md
index 47935bee18..66f2d55667 100644
--- a/translations/ja-JP/content/admin/packages/index.md
+++ b/translations/ja-JP/content/admin/packages/index.md
@@ -14,6 +14,7 @@ children:
   - /enabling-github-packages-with-minio
   - /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
   - /configuring-package-ecosystem-support-for-your-enterprise
+  - /migrating-your-enterprise-to-the-container-registry-from-the-docker-registry
 shortTitle: Manage GitHub Packages
 ---
 
diff --git a/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..5b6feb7966
--- /dev/null
+++ b/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,85 @@
+---
+title: Migrating your enterprise to the Container registry from the Docker registry
+intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.product.product_location %} to the {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.'
+versions:
+  feature: docker-ghcr-enterprise-migration
+shortTitle: コンテナレジストリへの移行
+topics:
+  - Containers
+  - Docker
+  - Migration
+---
+
+{% data reusables.package_registry.container-registry-ghes-beta %}
+
+## {% data variables.product.prodname_container_registry %} について
+
+{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+
+For more information about configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+
+## About migration from the Docker registry
+
+{% data reusables.package_registry.container-registry-replaces-docker-registry %} If the Docker registry on {% data variables.product.product_location %} contains images, you must manually migrate the images to the {% data variables.product.prodname_container_registry %}.
+
+{% ifversion ghes %}
+
+{% note %}
+
+**注釈**: {% data reusables.package_registry.container-registry-ghes-migration-availability %}
+
+{% endnote %}
+
+{% endif %}
+
+{% data reusables.package_registry.container-registry-migration-namespaces %} For more information about the impact of migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the  {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry#about-migration-from-the-docker-registry)."
+
+## Migrating organizations to the {% data variables.product.prodname_container_registry %}
+
+You can start a migration of all your organizations' Docker images to the {% data variables.product.prodname_container_registry %}. The duration of the migration operation depends on the total number of images to migrate, and the overall load on {% ifversion ghes %}your instance{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. After a successful migration, {% data variables.product.product_name %} will display a summary, and all future uploads of Docker images will use the {% data variables.product.prodname_container_registry %}.
+
+If {% ifversion ghes %}a site administrator{% elsif ghae %}an enterprise owner{% endif %} has configured email notifications for {% data variables.product.product_location %}, you will receive an email after the migration is complete. 詳しい情報については、「[通知のためのメールを設定する](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)」を参照してください。
+
+{% note %}
+
+**{% ifversion ghes %}注釈{% elsif ghae %}注釈{% endif %}**:
+
+{%- ifversion ghes %}
+- During the migration, the CPU and memory usage for your instance will increase. To ensure the performance of the instance for your users, {% data variables.product.company_short %} recommends that you begin a migration during a period of reduced activity.
+{%- endif %}
+{% ifversion ghes %}- {% endif %}During the migration, do not modify settings for your enterprise{% ifversion ghes %} or run `ghe-config-apply` from an administrative SSH session{% endif %}. {% ifversion ghes %}These actions will trigger a configuration run, which can restart services and {% elsif ghae %}Modifying these settings {% endif %} may interrupt the migration.
+{%- ifversion ghes %}
+- After the migration, storage pressure on your instance will increase due to the duplication of image files in the Docker registry and the {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.product_name %} will remove the duplicated files when all migrations are complete.
+
+For more information about monitoring the performance and storage of {% data variables.product.product_location %}, see "[Accessing the monitor dashboard](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)."
+{% endif %}
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+1. 左のサイドバーで**Packages**をクリックしてください。
+1. To the right of the number of packages to migrate, click **Start migration**. During the migration, {% data variables.product.product_name %} will display progress on this page.
+
+After the migration completes, the page will display the results. If a migration fails, the page will show the organizations that own the package that caused the failure.
+
+## Re-running a failed organization migration
+
+Prior to migration, if a user has created a package in the {% data variables.product.prodname_container_registry %} that has an identical name to an existing package in the Docker registry, the migration will fail.
+
+1. Delete the affected container in the {% data variables.product.prodname_container_registry %}. 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package#deleting-a-version-of-an-organization-scoped-package-on-github)」を参照してください。
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.packages-tab %}
+1. To the right of the number of packages to migrate, click **Re-run migration**. During the migration, {% data variables.product.product_name %} will display progress on this page.
+1. If the migration fails again, start from step 1 and re-run the migration.
+
+{% ifversion ghes %}
+
+## Monitoring traffic to the registries
+
+You can use visualize traffic to the Docker registry and {% data variables.product.prodname_container_registry %} from {% data variables.product.product_location %}'s monitor dashboard. The "GitHub Container Package Registry" graph can help you confirm that you've successfully migrated all images to the {% data variables.product.prodname_container_registry %}. In the graph, "v1" represents traffic to the Docker registry, and "v2" represents traffic to the {% data variables.product.prodname_container_registry %}. 詳しい情報については、「[モニターダッシュボードへのアクセス](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)」を参照してください。
+
+{% endif %}
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index dbca32c4a6..31b5f31638 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -13,6 +13,7 @@ redirect_from:
   - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise
   - /github/setting-up-and-managing-your-enterprise-account/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account
 versions:
   ghec: '*'
   ghes: '*'
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 78eafe20e7..4edafc779b 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -203,6 +203,28 @@ Across all organizations owned by your enterprise, you can allow members with ad
 4. [Repository upload limit] で、ドロップダウンメニューを使用して最大オブジェクトサイズをクリックします。 ![最大オブジェクトサイズのオプションを備えたドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
 5. 必要に応じて、すべてのリポジトリにアップロードの最大制限を適用するには [**Enforce on all repositories**] を選択します。 ![すべてのリポジトリにオブジェクトの最大サイズを適用するオプション](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
 
+{% ifversion profile-name-enterprise-setting %}
+
+## Enforcing a policy for the display of member names in your repositories
+
+Across all organizations owned by your enterprise, you can allow members to see a comment author's profile name, in addition to their username, in issues and pull requests for public and internal repositories.
+
+![コメントに表示されたコメント作者の名前](/assets/images/help/issues/commenter-full-name.png)
+
+{% note %}
+
+**Note:** When this policy is enforced for all repositories in the enterprise, it overrides the organization setting for private repositories. For more information, see "[Managing the display of member names in your organization](/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization)".
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.options-tab %}
+4. Under "Allow members to see the comment author's profile name in public and internal repositories", select the dropdown menu and click a policy. ![Screenshot of Options page with policy drop down emphasized](/assets/images/enterprise/site-admin-settings/comment-authors-profile-name-drop-down.png)
+5. Optionally, to enforce the display of profile names for all repositories in your enterprise, select **Enforce for all repositories on the instance**. ![Screenshot of "Enforce for all repositories" option emphasized](/assets/images/enterprise/site-admin-settings/enforce-for-all-repositories-option.png)
+
+{% endif %}
+
 ## リポジトリ間のプルリクエストのためのマージコンフリクトエディタを設定する
 
 ユーザが自分のコンピュータ上でローカルにマージコンフリクトを解決するように要求すれば、うっかりフォークから上流のリポジトリに書き込んでしまうことを回避できます。
@@ -265,10 +287,22 @@ Each repository inherits a default force push setting from the settings of the u
 
 {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
 
-{% ifversion ghes %} Enterprise で[プライベートモードを有効化](/enterprise/admin/configuration/enabling-private-mode)している場合は、{% else %}{% endif %}リポジトリ管理者がパブリックリポジトリへの匿名 Git 読み取りアクセスを有効化できるようにすることができます。
+If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) for {% data variables.product.product_location %}, you can allow repository administrators to enable anonymous Git read access to public repositories.
 
 匿名 Git 読み取りアクセスを有効化すると、ユーザは Enterprise 上のカスタムツールの認証をバイパスできるようになります。 あなたもしくはリポジトリ管理者がこのアクセス設定をリポジトリで有効化すると、認証を受けていない Git の操作 (そして {% data variables.product.product_name %} へのネットワークアクセスができる人はだれでも) は、認証なしでリポジトリに読み取りアクセスできることになります。
 
+Anonymous Git read access is disabled by default.{% ifversion ghes = 3.4 or ghes = 3.5 or ghes = 3.6 or ghes = 3.7 %} When you upgrade to {% data variables.product.product_name %} 3.6 or later, anonymous Git read access is automatically disabled at the application level, and `git://` connections on port 9418 will return the following error.
+
+```
+The unauthenticated git protocol on port 9418 is no longer supported.
+```
+
+If you wish to support the unathenticated Git protocol in your environment, you must manually re-enable the feature. {% data variables.product.company_short %} recommends using SSH instead of the Git protocol. 詳細は [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server) を参照してください。
+
+{% endif %}
+
+
+
 必要に応じて、リポジトリのアクセス設定をロックすることで、リポジトリ管理者が Enterprise のリポジトリの匿名 Git アクセス設定を変更不可にすることができます。 リポジトリのGit読み取りアクセス設定をロックすると、サイト管理者だけがこの設定を変更できるようになります。
 
 {% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
diff --git a/translations/ja-JP/content/admin/policies/index.md b/translations/ja-JP/content/admin/policies/index.md
index b716198582..5c358faa49 100644
--- a/translations/ja-JP/content/admin/policies/index.md
+++ b/translations/ja-JP/content/admin/policies/index.md
@@ -4,7 +4,6 @@ intro: '{% data variables.product.product_name %} でポリシーを設定する
 redirect_from:
   - /enterprise/admin/developer-workflow
   - /enterprise/admin/policies
-  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account
 versions:
   ghec: '*'
   ghes: '*'
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index a5784ea28a..2341764599 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -9,6 +9,9 @@ redirect_from:
   - /github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account
   - /admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account
 intro: 'Organizationは企業内で、部署や同様のプロジェクトで作業を行うグループなど、個別のユーザグループを作成する素晴らしい手段です。 {% ifversion ghae %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to members of other organizations in the enterprise, while private repositories are inaccessible to anyone but members of the organization that are granted access.'
 versions:
   ghec: '*'
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
index 831c946e65..707e3121e6 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -25,6 +25,10 @@ You can see all current enterprise members and enterprise administrators{% ifver
 
 You can view all the current enterprise owners{% ifversion ghec %} and billing managers{% endif %} for your enterprise.{% ifversion enterprise-membership-view-improvements %} You can see useful information about each administrator{% ifversion ghec %} and filter the list by role{% endif %}.{% endif %} You can find a specific person by searching for their username or display name.
 
+{% ifversion ghes > 3.5 %}
+Enterprise owners whose accounts are suspended are included in the list of enterprise administrators, and are identified as suspended. You should consider demoting any suspended owners you see. 詳細は「[サイト管理者の昇格あるいは降格](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator#demoting-a-site-administrator-from-the-enterprise-settings)」を参照してください。
+{% endif %}
+
 {% ifversion not ghae %}
 You can also remove an administrator. 詳しい情報について。 see "[Inviting people to manage your enterprise](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise#removing-an-enterprise-administrator-from-your-enterprise-account)."
 {% endif %}
diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md
index 0c9d480028..e64b6f397c 100644
--- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md
+++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md
@@ -14,7 +14,11 @@ topics:
   - SSH
 ---
 
-When you set up SSH, you will need to generate a new SSH key and add it to the ssh-agent. You must add the SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+## SSH について
+
+{% data reusables.ssh.about-ssh %} For more information about SSH, see [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) on Wikipedia.
+
+When you set up SSH, you will need to generate a new private SSH key and add it to the SSH agent. You must also add the public SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. 詳しい情報については[SSH キーのパスフレーズを使う](/github/authenticating-to-github/working-with-ssh-key-passphrases)を参照してください。
 
diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
index 8fff34f4e4..e00b4bd018 100644
--- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
@@ -15,9 +15,20 @@ topics:
 shortTitle: Add a new SSH key
 ---
 
-Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you should have:
-* [既存の SSH キーの確認](/articles/checking-for-existing-ssh-keys)
-* [新しい SSH キーを生成して ssh-agent に追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)
+## About addition of SSH keys to your account
+
+{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+
+After you generate an SSH key pair, you must add the public key to {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable SSH access for your account.
+
+## 必要な環境
+
+Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, complete the following steps.
+
+1. Check for existing SSH keys. For more information, see "[Checking for existing SSH keys](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)."
+1. Generate a new SSH key and add it to your machine's SSH agent. 詳しい情報については、「[新しい SSH キーを生成して ssh-agent に追加する](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)」を参照してください。
+
+## Adding a new SSH key to your account
 
 After adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you can reconfigure any local repositories to use SSH. 詳しい情報については[リモート URL の HTTPS から SSH への切り替え](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)を参照してください。
 
@@ -45,7 +56,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.ssh %}
 4. [**New SSH key**] または [**Add SSH key**] をクリックします。 ![SSH キーボタン](/assets/images/help/settings/ssh-add-ssh-key.png)
-5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば個人の Mac を使っている場合、このキーを "Personal MacBook Air" などと呼ぶことが考えられます。
+5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば、個人のMacを使っているなら、このキーを「Personal MacBook Air」とすることができるでしょう。
 6. キーを [Key] フィールドに貼り付けます。 ![キーフィールド](/assets/images/help/settings/ssh-key-paste.png)
 7. **[Add SSH key]** をクリックしてください。 ![キーの追加ボタン](/assets/images/help/settings/ssh-add-key.png)
 {% data reusables.user-settings.sudo-mode-popup %}
@@ -76,7 +87,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.ssh %}
 4. [**New SSH key**] または [**Add SSH key**] をクリックします。 ![SSH キーボタン](/assets/images/help/settings/ssh-add-ssh-key.png)
-5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば個人の Mac を使っている場合、このキーを "Personal MacBook Air" などと呼ぶことが考えられます。
+5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば、個人のMacを使っているなら、このキーを「Personal MacBook Air」とすることができるでしょう。
 6. キーを [Key] フィールドに貼り付けます。 ![キーフィールド](/assets/images/help/settings/ssh-key-paste.png)
 7. **[Add SSH key]** をクリックしてください。 ![キーの追加ボタン](/assets/images/help/settings/ssh-add-key.png)
 8. {% data variables.product.product_name %} パスワードの確認を促された場合は、確認します。 ![sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png)
@@ -108,7 +119,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.ssh %}
 4. [**New SSH key**] または [**Add SSH key**] をクリックします。 ![SSH キーボタン](/assets/images/help/settings/ssh-add-ssh-key.png)
-5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば個人の Mac を使っている場合、このキーを "Personal MacBook Air" などと呼ぶことが考えられます。
+5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば、個人のMacを使っているなら、このキーを「Personal MacBook Air」とすることができるでしょう。
 6. キーを [Key] フィールドに貼り付けます。 ![キーフィールド](/assets/images/help/settings/ssh-key-paste.png)
 7. **[Add SSH key]** をクリックしてください。 ![キーの追加ボタン](/assets/images/help/settings/ssh-add-key.png)
 8. {% data variables.product.product_name %} パスワードの確認を促された場合は、確認します。 ![sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png)
@@ -146,5 +157,5 @@ gh ssh-key add ~/.ssh/id_ed25519.pub
 {% ifversion fpt or ghec %}
 ## 参考リンク
 
-- [SAML シングルサインオンで使うためにSSHキーを認可する](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)
+- [SAMLシングルサインオンで使うためにSSHキーを認可する](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)
 {% endif %}
diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
index 4a430ae839..1939f7202a 100644
--- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
+++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
@@ -15,6 +15,16 @@ topics:
 shortTitle: Check for existing SSH key
 ---
 
+## About SSH keys
+
+You can use SSH to perform Git operations in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. 詳しい情報については「[SSHについて](/authentication/connecting-to-github-with-ssh/about-ssh)」を参照してください。
+
+If you have an existing SSH key, you can use the key to authenticate Git operations over SSH.
+
+## 既存の SSH キーの確認
+
+Before you generate a new SSH key, you should check your local machine for existing keys.
+
 {% data reusables.ssh.key-type-support %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index de0b97d03e..25cbb1a35f 100644
--- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -17,72 +17,78 @@ topics:
 shortTitle: Generate new SSH key
 ---
 
-## About SSH key generation
+## About SSH key passphrases
+
+{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+
+When you generate an SSH key, you can add a passphrase to further secure the key. Whenever you use the key, you must enter the passphrase. If your key has a passphrase and you don't want to enter the passphrase every time you use the key, you can add your key to the SSH agent. The SSH agent manages your SSH keys and remembers your passphrase.
 
 If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)."
 
 If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2).
 
-If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.
-
 ## 新しい SSH キーを生成する
 
+You can generate a new SSH key on your local machine. After you generate the key, you can add the key to your account on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable authentication for Git operations over SSH.
+
+{% data reusables.ssh.key-type-support %}
+
 {% data reusables.command_line.open_the_multi_os_terminal %}
 2. 以下のテキストを貼り付けます。メールアドレスは自分の {% data variables.product.product_name %} メールアドレスに置き換えてください。
-    {% ifversion ghae %}
+   {%- ifversion ghae %}
     <!-- GitHub AE is FIPS 140-2 compliant. FIPS does not yet permit keys that use the ed25519 algorithm. -->
-  ```shell
-  $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>" 
-  ```
-    {% else %}
-  ```shell
-  $ ssh-keygen -t ed25519 -C "<em>your_email@example.com</em>"
-  ```
-  {% note %}
+   ```shell
+   $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>" 
+   ```
+   {%- else %}
+   ```shell
+   $ ssh-keygen -t ed25519 -C "<em>your_email@example.com</em>"
+   ```
+   {% note %}
 
-  **注釈:** Ed25519 アルゴリズムをサポートしないレガシーシステムを使用している場合は、以下を使用します。
-  ```shell
-   $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
-  ```
+   **注釈:** Ed25519 アルゴリズムをサポートしないレガシーシステムを使用している場合は、以下を使用します。
+   ```shell
+    $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
+   ```
 
-  {% endnote %}
-  {% endif %}
+   {% endnote %}
+   {%- endif %}
 
-  This creates a new SSH key, using the provided email as a label.
-  ```shell
-  > Generating public/private <em>algorithm</em> key pair.
-  ```
+   This creates a new SSH key, using the provided email as a label.
+   ```shell
+   > Generating public/private <em>algorithm</em> key pair.
+   ```
 3. 「Enter a file in which to save the key」というメッセージが表示されたら、Enter キーを押します。 これにより、デフォルトのファイル場所が受け入れられます。
 
-  {% mac %}
+   {% mac %}
 
-  ```shell
-  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_<em>algorithm</em>): <em>[Press enter]</em>
-  ```
+   ```shell
+   > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_<em>algorithm</em>): <em>[Press enter]</em>
+   ```
 
-  {% endmac %}
+   {% endmac %}
 
-  {% windows %}
+   {% windows %}
 
-  ```shell
-  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_<em>algorithm</em>):<em>[Press enter]</em>
-  ```
+   ```shell
+   > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_<em>algorithm</em>):<em>[Press enter]</em>
+   ```
 
-  {% endwindows %}
+   {% endwindows %}
 
-  {% linux %}
+   {% linux %}
 
-  ```shell
-  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/<em>algorithm</em>): <em>[Press enter]</em>
-  ```
+   ```shell
+   > Enter a file in which to save the key (/home/<em>you</em>/.ssh/<em>algorithm</em>): <em>[Press enter]</em>
+   ```
 
-  {% endlinux %}
+   {% endlinux %}
 
 4. プロンプトで、安全なパスフレーズを入力します。 For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
-  ```shell
-  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
-  > Enter same passphrase again: <em>[Type passphrase again]</em>
-  ```
+   ```shell
+   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+   > Enter same passphrase again: <em>[Type passphrase again]</em>
+   ```
 
 ## SSH キーを ssh-agent に追加する
 
@@ -94,66 +100,55 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 2. macOS Sierra 10.12.2 以降を使用している場合は、`~/.ssh/config` ファイルを修正して、キーが自動で ssh-agent に読み込まれ、キーチェーンにパスフレーズが記憶されるようにする必要があります。
 
-    * まず、`~/.ssh/config` ファイルがデフォルトの場所にあるかどうかを確認します。
+   * まず、`~/.ssh/config` ファイルがデフォルトの場所にあるかどうかを確認します。
 
-      ```shell
-      $ open ~/.ssh/config
-      > The file /Users/<em>you</em>/.ssh/config does not exist.
-      ```
+     ```shell
+     $ open ~/.ssh/config
+     > The file /Users/<em>you</em>/.ssh/config does not exist.
+     ```
 
-    * ファイルがない場合は、ファイルを作成します。
+   * ファイルがない場合は、ファイルを作成します。
 
-      ```shell
-      $ touch ~/.ssh/config
-      ```
+     ```shell
+     $ touch ~/.ssh/config
+     ```
 
-    * `~/.ssh/config` ファイルを開き、以下の行が含まれるようにファイルを変更します。 SSH キーファイルの名前またはパスがサンプルコードと異なる場合は、現在の設定に一致するようにファイル名またはパスを変更してください。
+   * `~/.ssh/config` ファイルを開き、以下の行が含まれるようにファイルを変更します。 SSH キーファイルの名前またはパスがサンプルコードと異なる場合は、現在の設定に一致するようにファイル名またはパスを変更してください。
 
-      ```
-      Host *
-        AddKeysToAgent yes
-        UseKeychain yes
-        IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}
-      ```
+     ```
+     Host *
+       AddKeysToAgent yes
+       UseKeychain yes
+       IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}
+     ```
 
      {% note %}
 
-     **注釈:** キーにパスフレーズを追加しない場合は、`UseKeychain` 行を省略してください。
+     **ノート:**
 
+     - If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
+
+     - If you see a `Bad configuration option: usekeychain` error, add an additional line to the configuration's' `Host *` section.
+
+       ```
+       Host *
+         IgnoreUnknown UseKeychain
+       ```
      {% endnote %}
 
-      {% mac %}
-      {% note %}
-
-      **Note:** If you see an error like this
-
-      ```
-      /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain
-      ```
-
-      add an additional config line to your `Host *` section:
-
-      ```
-      Host *
-        IgnoreUnknown UseKeychain
-      ```
-
-      {% endnote %}
-      {% endmac %}
-
 3. SSH 秘密鍵を ssh-agent に追加して、パスフレーズをキーチェーンに保存します。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
-  ```
-  {% note %}
+   ```
+   {% note %}
 
-  **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. キーにパスフレーズを追加しない場合は、`-K` オプションを指定せずにコマンドを実行します。
+   **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. キーにパスフレーズを追加しない場合は、`-K` オプションを指定せずにコマンドを実行します。
 
-  Apple の標準バージョンをインストールしていない場合は、エラーが発生する場合があります。 このエラーの解決方法についての詳細は、「[エラー: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)」を参照してください。
+   Apple の標準バージョンをインストールしていない場合は、エラーが発生する場合があります。 このエラーの解決方法についての詳細は、「[エラー: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)」を参照してください。
 
-  In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively.
+   In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively.
 
-  {% endnote %}
+   {% endnote %}
 
 4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
@@ -164,11 +159,11 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 {% data reusables.desktop.windows_git_bash %}
 
 1. ssh-agent が実行されていることを確認します. 「[SSH キーパスフレーズで操作する](/articles/working-with-ssh-key-passphrases)」の「ssh-agent を自動起動する」の手順を使用するか、手動で開始できます。
-  ```shell
-  # start the ssh-agent in the background
-  $ eval "$(ssh-agent -s)"
-  > Agent pid 59566
-  ```
+   ```shell
+   # start the ssh-agent in the background
+   $ eval "$(ssh-agent -s)"
+   > Agent pid 59566
+   ```
 
 2. SSH プライベートキーを ssh-agent に追加します。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
@@ -195,59 +190,50 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
 1. Insert your hardware security key into your computer.
 {% data reusables.command_line.open_the_multi_os_terminal %}
 3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
-  ```shell
-  $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
-  ```
+   ```shell
+   $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
+   ```
 
-  {% ifversion not ghae %}
-  {% note %}
+   {%- ifversion not ghae %}
+   {% note %}
 
-  **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
-  ```shell
-   $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
-  ```
+   **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
+   ```shell
+    $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
+   ```
 
-  {% endnote %}
-  {% endif %}
+   {% endnote %}
+   {%- endif %}
 4. When you are prompted, touch the button on your hardware security key.
 5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
 
-  {% mac %}
+   {% mac %}
 
-  ```shell
-  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
-  ```
+   ```shell
+   > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
+   ```
 
-  {% endmac %}
+   {% endmac %}
 
-  {% windows %}
+   {% windows %}
 
-  ```shell
-  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):<em>[Press enter]</em>
-  ```
+   ```shell
+   > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):<em>[Press enter]</em>
+   ```
 
-  {% endwindows %}
+   {% endwindows %}
 
-  {% linux %}
+   {% linux %}
 
-  ```shell
-  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
-  ```
+   ```shell
+   > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
+   ```
 
-  {% endlinux %}
+   {% endlinux %}
 
 6. When you are prompted to type a passphrase, press **Enter**.
-  ```shell
-  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
-  > Enter same passphrase again: <em>[Type passphrase again]</em>
-  ```
+   ```shell
+   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+   > Enter same passphrase again: <em>[Type passphrase again]</em>
+   ```
 7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
-
-
-## 参考リンク
-
-- 「[SSHについて](/articles/about-ssh)」
-- [SSH キーのパスフレーズを使う](/articles/working-with-ssh-key-passphrases)
-{%- ifversion fpt or ghec %}
-- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
-{%- endif %}
diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
index 62764f2a15..8b2b0784c7 100644
--- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
+++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
@@ -17,7 +17,9 @@ topics:
 shortTitle: SSH key passphrases
 ---
 
-SSH キーにより、誰かがあなたのコンピュータにアクセスすると、そのキーを使用するすべてのシステムにもアクセスすることになります。 セキュリティをさらに強化するには、SSH キーにパスフレーズを追加します。 パスフレーズを安全に保存するために `ssh-agent` を使用すると、パスフレーズを再入力する必要がありません。
+## About passphrases for SSH keys
+
+With SSH keys, if someone gains access to your computer, the attacker can gain access to every system that uses that key. セキュリティをさらに強化するには、SSH キーにパスフレーズを追加します。 To avoid entering the passphrase every time you connect, you can securely save your passphrase in the SSH agent.
 
 ## パスフレーズを追加または変更する
 
@@ -105,7 +107,3 @@ OS X El Capitan を介する Mac OS X Leopard では、これらのデフォル
 それ以外の場合は、鍵を ssh-agent に追加するときに、パスフレーズをキーチェーンに格納できます。 詳細は「[SSH キーを ssh-agent に追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)」を参照してください。
 
 {% endmac %}
-
-## 参考リンク
-
-- 「[SSHについて](/articles/about-ssh)」
diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
index 6f05b9af2a..adb05a61f9 100644
--- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
+++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
@@ -28,6 +28,8 @@ Commits and tags have the following verification statuses, depending on whether
 
 {% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
 
+Signing commits differs from signing off on a commit. For more information about signing off on commits, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
 ### Default statuses
 
 | Status         | Description |
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
index a8a23d4df4..da469b1639 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
@@ -1,7 +1,7 @@
 ---
-title: Browsing security advisories in the GitHub Advisory Database
-intro: 'You can browse the {% data variables.product.prodname_advisory_database %} to find advisories for security risks in open source projects that are hosted on {% data variables.product.company_short %}.'
-shortTitle: Browse Advisory Database
+title: GitHub Advisory Databaseのセキュリティアドバイザリの閲覧
+intro: '{% data variables.product.prodname_advisory_database %}を閲覧して、{% data variables.product.company_short %}でホストされているオープンソースプロジェクトのセキュリティリスクに対するアドバイザリを見つけることができます。'
+shortTitle: Advisory Databaseの参照
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
@@ -11,6 +11,8 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Security advisories
@@ -19,126 +21,147 @@ topics:
   - Vulnerabilities
   - CVEs
 ---
+
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
 
-## About the {% data variables.product.prodname_advisory_database %}
+## {% data variables.product.prodname_advisory_database %} について
 
-The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities and malware, grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
+The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
 
 {% data reusables.repositories.tracks-vulnerabilities %}
 
-## About types of security advisories
+## セキュリティアドバイザリのタイプについて
 
 {% data reusables.advisory-database.beta-malware-advisories %}
 
-Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects or for malicious open source software. 
+Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}.
 
-{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
+通常、コード内の{% data reusables.repositories.a-vulnerability-is %}の脆弱性は、偶然に導入され、発見されるとすぐに修正されます。 依存関係の修正されたバージョンを使うよう、コードはできるかぎり早く更新しなければなりません。
 
-In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
+{% ifversion GH-advisory-db-supports-malware %}
 
-### {% data variables.product.company_short %}-reviewed advisories
+対照的に、悪意のあるソフトウェア、またはマルウェアは、意図的に望ましくない、もしくは有害な機能を実行するように設計されたものです。 マルウェアは、ハードウェア、ソフトウェア、機密データ、あるいはマルウェアを使うアプリケーションのユーザを標的にする可能性があります。 マルウェアはプロジェクトから取り除き、その依存関係の安全な代替物を見つけなければなりません。
 
-{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities or malware that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
+{% endif %}
 
-Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
+### {% data variables.product.company_short %}がレビューしたアドバイザリ
 
-- Composer (registry: https://packagist.org/)
-- Erlang (registry: https://hex.pm/)
-- Go (registry: https://pkg.go.dev/)
-- Maven (registry: https://repo1.maven.org/maven2/org/)
-- npm (registry: https://www.npmjs.com/)
-- NuGet (registry: https://www.nuget.org/)
-- pip (registry: https://pypi.org/)
-- RubyGems (registry: https://rubygems.org/)
-- Rust (registry: https://crates.io/)
+{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. 各アドバイザリの有効性は慎重にレビューされ、完全な説明が成されており、エコシステムとパッケージの両方の情報が含まれていることが保証されています。
 
-If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
+一般的に、サポートされているエコシステムはソフトウェアプログラミング言語の関連するパッケージレジストリにちなんで名付けられています。 アドバイザリは、サポートされているレジストリから来たパッケージ内の脆弱性に対するものであれば、レビューが行われます。
 
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability or malware for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
+- Erlang (registry: https://hex.pm/){% endif %}
+- Go (レジストリ: https://pkg.go.dev/)
+- Maven (レジストリ: https://repo1.maven.org/maven2/org/)
+- npm (レジストリ: https://www.npmjs.com/)
+- NuGet (レジストリ: https://www.nuget.org/)
+- pip (レジストリ: https://pypi.org/)
+- RubyGems (レジストリ: https://rubygems.org/)
+- Rust (レジストリ: https://crates.io/)
 
-### Unreviewed advisories
+サポートすべき新しいエコシステムの提案がある場合は、議論のための[Issue](https://github.com/github/advisory-database/issues)をオープンしてください。
 
-Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
+If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. 詳しい情報については「[{% data variables.product.prodname_dependabot_alerts %}について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。
 
-{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
+### レビューされていないアドバイザリ
 
-## About information in security advisories
+レビューされていないアドバイザリは、自動的にNational Vulnerability Databaseフィードから直接{% data variables.product.prodname_advisory_database %}へ展開されたセキュリティ脆弱性です。
 
-Each security advisory contains information about the vulnerability or malware, which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
+この種のアドバイザリは妥当性あるいは完全性がチェックされていないので、レビューされていないアドバイザリに対して{% data variables.product.prodname_dependabot %}は{% data variables.product.prodname_dependabot_alerts %}を生成しません。
 
-The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
+## セキュリティアドバイザリ内の情報について
+
+Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. さらに、National Vulnerability Database リストのアドバイザリには、CVE レコードへのリンクが含まれており、脆弱性、その CVSS スコア、その定性的な重要度レベルの詳細を確認できます。 詳しい情報については、アメリカ国立標準技術研究所の「[National Vulnerability Database](https://nvd.nist.gov/)"」を参照してください。
+
+重大度レベルは「[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)」で定義されている 4 つのレベルのいずれかです。
 - Low
 - Medium/Moderate
 - High
 - Critical
 
-The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
+{% data variables.product.prodname_advisory_database %} は、上記の CVSS レベルを使用します。 {% data variables.product.company_short %} が CVE を取得した場合、{% data variables.product.prodname_advisory_database %} は CVSS バージョン 3.1 を使用します。 CVE がインポートされた場合、{% data variables.product.prodname_advisory_database %} は CVSS バージョン 3.0 と 3.1 の両方をサポートします。
 
 {% data reusables.repositories.github-security-lab %}
 
-## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
+## {% data variables.product.prodname_advisory_database %} のアドバイザリにアクセスする
 
-1. Navigate to https://github.com/advisories.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
+1. Https://github.com/advisories にアクセスします。
+2. 必要に応じて、リストをフィルタするには、ドロップダウンメニューを使用します。 ![ドロップダウンフィルタ](/assets/images/help/security/advisory-database-dropdown-filters.png)
    {% tip %}
 
-   **Tip:** You can use the sidebar on the left to explore  {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
+   **参考:** 左側のサイドバーを使って、{% data variables.product.company_short %}がレビューしたアドバイザリとレビューされていないアドバイザリを個別に調べることができます。
 
    {% endtip %}
-3. Click on any advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.
+3. Click an advisory to view details. デフォルトでは、セキュリティ脆弱性に対する{% data variables.product.company_short %}がレビューしたアドバイザリが表示されます。 {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %}
 
 
 {% note %}
 
-The database is also accessible using the GraphQL API. By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`. For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
+データベースは、GraphQL API を使用してアクセスすることもできます。 {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
 
 {% endnote %}
 
-## Editing an advisory in the {% data variables.product.prodname_advisory_database %}
-You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)."
+## {% data variables.product.prodname_advisory_database %}中のアドバイザリの編集
+{% data variables.product.prodname_advisory_database %}のアドバイザリには、改善を提案できます。 詳しい情報については「[{% data variables.product.prodname_advisory_database %}中のセキュリティアドバイザリの編集](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)」を参照してください。
 
-## Searching the {% data variables.product.prodname_advisory_database %}
+## {% data variables.product.prodname_advisory_database %} を検索する
 
-You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
+データベースを検索し、修飾子を使用して検索を絞り込むことができます。 たとえば、特定の日付、特定のエコシステム、または特定のライブラリで作成されたアドバイザリを検索できます。
 
 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example |
-| ------------- | ------------- |
-| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. |
-| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
-| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
-| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
-| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
-| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
-| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
-| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
-| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
-| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
-| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
-| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
-| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
-| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
-| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
-| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
-| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
+| 修飾子             | サンプル                                                                                                                                                  |
+| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `type:reviewed` | [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed)は、セキュリティ脆弱性に対する{% data variables.product.company_short %}がレビューしたアドバイザリを表示します。 |
+{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
+{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
+| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | | `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | | `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | | `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | | `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | | `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | | `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | | `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | | `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | | `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | | `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | | `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | | `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | | `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
 
-## Viewing your vulnerable repositories
+## 脆弱性のあるリポジトリを表示する
 
-For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability or malware. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
+For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. 脆弱性のあるリポジトリを確認するには、そのリポジトリの {% data variables.product.prodname_dependabot_alerts %} にアクセスできる必要があります。 詳しい情報については「[{% data variables.product.prodname_dependabot_alerts %}について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)」を参照してください。
 
-1. Navigate to https://github.com/advisories.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
+1. Https://github.com/advisories にアクセスします。
+2. アドバイザリをクリックします。
+3. アドバイザリページの上部にある [**Dependabot alerts**] をクリックします。 ![Dependabotアラート](/assets/images/help/security/advisory-database-dependabot-alerts.png)
+4. 必要に応じて、リストをフィルタするには、検索バーまたはドロップダウンメニューを使用します。 [Organization] ドロップダウンメニューを使用すると、オーナー（Organization またはユーザ）ごとに {% data variables.product.prodname_dependabot_alerts %} をフィルタできます。 ![アラートをフィルタするための検索バーとドロップダウンメニュー](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
+5. アドバイザリに関する詳細、そして脆弱性のあるリポジトリの修正方法に関するアドバイスについては、リポジトリ名をクリックしてください。
 
-## Further reading
+{% ifversion security-advisories-ghes-ghae %}
+## Accessing the local advisory database on {% data variables.product.product_location %}
 
-- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
+If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.product.product_location %}, you can also browse reviewed advisories locally. 詳しい情報については「[{% data variables.product.prodname_github_connect %}について](/admin/configuration/configuring-github-connect/about-github-connect)」を参照してください。
+
+You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories.
+
+1. Navigate to `https://HOSTNAME/advisories`.
+2. 必要に応じて、リストをフィルタするには、ドロップダウンメニューを使用します。 ![ドロップダウンフィルタ](/assets/images/help/security/advisory-database-dropdown-filters.png)
+   {% note %}
+
+   **Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)".
+
+   {% endnote %}
+3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %}
+
+You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.product.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)".
+
+### Viewing vulnerable repositories for {% data variables.product.product_location %}
+
+{% data reusables.repositories.enable-security-alerts %}
+
+In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. 脆弱性のあるリポジトリを確認するには、そのリポジトリの {% data variables.product.prodname_dependabot_alerts %} にアクセスできる必要があります。 詳しい情報については「[{% data variables.product.prodname_dependabot_alerts %}について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)」を参照してください。
+
+1. Navigate to `https://HOSTNAME/advisories`.
+2. アドバイザリをクリックします。
+3. アドバイザリページの上部にある [**Dependabot alerts**] をクリックします。 ![Dependabotアラート](/assets/images/help/security/advisory-database-dependabot-alerts.png)
+4. 必要に応じて、リストをフィルタするには、検索バーまたはドロップダウンメニューを使用します。 [Organization] ドロップダウンメニューを使用すると、オーナー（Organization またはユーザ）ごとに {% data variables.product.prodname_dependabot_alerts %} をフィルタできます。 ![アラートをフィルタするための検索バーとドロップダウンメニュー](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
+5. アドバイザリに関する詳細、そして脆弱性のあるリポジトリの修正方法に関するアドバイスについては、リポジトリ名をクリックしてください。
+
+{% endif %}
+
+## 参考リンク
+
+- MITREの[「脆弱性」の定義](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
index d0242bc452..85e085d51b 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
@@ -7,6 +7,8 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Security advisories
@@ -19,8 +21,9 @@ shortTitle: Advisory Databaseの編集
 
 ## {% data variables.product.prodname_advisory_database %}内のアドバイザリの編集について
 [github.com/advisories](https://github.com/advisories)にある{% data variables.product.prodname_advisory_database %}中のセキュリティアドバイザリは、グローバルなアドバイザリとみなされています。 {% data variables.product.prodname_advisory_database %}中のグローバルなセキュリティアドバイザリには、誰でも改善を提案できます。 追加で影響を受けるエコシステム、重要度、影響を受ける人の説明を含む、いかなる詳細も編集や追加ができます。 {% data variables.product.prodname_security %}のキュレーションチームは提案された改善をレビューし、受理されればそれらを{% data variables.product.prodname_advisory_database %}上に公開します。
+{% ifversion fpt or ghec %}
+リポジトリレベルのセキュリティアドバイザリを編集できるのは、リポジトリのオーナーと管理者のみです。 For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
 
-リポジトリレベルのセキュリティアドバイザリを編集できるのは、リポジトリのオーナーと管理者のみです。 詳しい情報については、「[リポジトリのセキュリティアドバイザリの編集](/code-security/security-advisories/editing-a-security-advisory)」を参照してください。
 ## GitHub Advisory Database中のアドバイザリの編集
 
 1. Https://github.com/advisories にアクセスします。
@@ -30,4 +33,15 @@ shortTitle: Advisory Databaseの編集
 5. アドバイザリの編集を終えたら、**Submit improvements（改善を提案）**をクリックしてください。
 6. 改善を提案したら、その変更を含むPull Requestが{% data variables.product.prodname_security %}キュレーションチームによって[github/advisory-database](https://github.com/github/advisory-database)内にレビューのために作成されます。 そのアドバイザリの発生元が{% data variables.product.prodname_dotcom %}リポジトリなら、オプションのコメントのためにオリジナルの公開者をタグ付けします。 あなたはこのPull Requestを見ることができ、このPull Requestが更新されるかクローズされると通知を受けます。
 
-[github/advisory-database](https://github.com/github/advisory-database)リポジトリ中のアドバイザリファイルに対して直接Pull Requestをオープンすることもできます。 詳しい情報については[コントリビューションのガイドライン](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md)を参照してください。 
+[github/advisory-database](https://github.com/github/advisory-database)リポジトリ中のアドバイザリファイルに対して直接Pull Requestをオープンすることもできます。 詳しい情報については[コントリビューションのガイドライン](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md)を参照してください。
+
+{% ifversion security-advisories-ghes-ghae %}
+## Editing advisories from {% data variables.product.product_location %}
+
+If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.product.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url.
+
+1. Navigate to `https://HOSTNAME/advisories`.
+2. コントリビュートしたいセキュリティアドバイザリを選択してください。
+3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on Github.com.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}. ![改善提案リンク](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png)
+4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above.
+{% endif %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
index f32ea8da46..dc4ff2dc9e 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
@@ -57,7 +57,7 @@ topics:
 
 ## 通信トークンの保護
 
-コードはしばしば、ネットワークを介して他のシステムと通信しなければならず、認証のためのシークレット（パスワードやAPIキーなど）を必要とします。 システムが実行されるためにはそれらのシークレットにアクセスできなければなりませんが、それらをソースコードには含めないのがベストプラクティスです。 これは特にパブリックリポジトリで重要ですが、多くの人々がアクセスするかもしれないプライベートリポジトリでも重要です。
+コードはしばしば、ネットワークを介して他のシステムと通信しなければならず、認証のためのシークレット（パスワードやAPIキーなど）を必要とします。 システムが実行されるためにはそれらのシークレットにアクセスできなければなりませんが、それらをソースコードには含めないのがベストプラクティスです。 これは特に、多くの人がアクセスするかもしれないリポジトリで重要で{% ifversion not ghae %}あり、パブリックリポジトリではきわめて重要で{% endif %}す。
 
 ### リポジトリのコミットされたシークレットの自動検出
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index ed9358a0c2..7d3517de96 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
@@ -70,7 +70,7 @@ The recommended formats explicitly define which versions are used for all direct
 | Package manager | Languages | Recommended formats | All supported formats |
 | --- | --- | --- | ---|
 {%- ifversion dependency-graph-rust-support %}
-| Cargo<sup>[*]</sup> | Rust | `Cargo.lock` | `Cargo.toml`, `Cargo.lock` | 
+| Cargo{% ifversion ghes = 3.6 or ghae-issue-7563 %}<sup>[*]</sup>{% endif %} | Rust | `Cargo.lock` | `Cargo.toml`, `Cargo.lock` | 
 {%- endif %}
 | Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |
 | NuGet | .NET languages (C#, F#, VB), C++  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
@@ -91,7 +91,7 @@ The recommended formats explicitly define which versions are used for all direct
 | RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
 | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
 
-{% ifversion dependency-graph-rust-support %}
+{% ifversion ghes = 3.6 or ghae-issue-7563 %}
 [*] For the initial release of Rust support, dependency graph does not have the metadata and mappings required to detect transitive dependencies. Dependency graph displays transitive dependencies, one level deep, when they are defined in a `Cargo.lock` file. {% data variables.product.prodname_dependabot_alerts %} and {% data variables.product.prodname_dependabot_security_updates %} are available for vulnerable dependencies defined in the `Cargo.lock` file.
 {% endif %}
 
diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md
index 4fa92e8d97..9a7ab09688 100644
--- a/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md
+++ b/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md
@@ -28,7 +28,7 @@ redirect_from:
 
 In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. この新しい codespace には、{% data variables.product.prodname_dotcom %} への最後のプッシュ時点までのすべての変更が含まれます。 For information on manually setting another region, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
 
-You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. 詳しい情報については「[開発コンテナの紹介](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)」を参照してください。
 
 ## オプション 2: リカバリを待つ
 
diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md
index 29dd25e8ae..d854370012 100644
--- a/translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md
+++ b/translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md
@@ -58,7 +58,7 @@ If you need to allow external access to services running on a codespace, you can
 
 If you need to connect to a service (such as a development web server) running within your codespace, you can configure port forwarding to make the service available on the internet.
 
-Organization owners can restrict the ability to make forward ports available publicly or within the organization. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
+Organizationのオーナーは、ポートのフォワードをパブリックに、あるいはOrganization内で利用できるようにする機能を制限できます。 For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
 
 **Privately forwarded ports**: Are accessible on the internet, but only the codespace creator can access them, after authenticating to {% data variables.product.product_name %}.
 
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md
index 9b94956da9..7446407522 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md
@@ -29,7 +29,7 @@ redirect_from:
 
 2. In the list of pull requests, click the pull request you'd like to open in {% data variables.product.prodname_codespaces %}.
 3. On the right-hand side of your screen, click **{% octicon "code" aria-label="The code icon" %} Code**.
-4. In the {% data variables.product.prodname_codespaces %} tab, click **Create codespace on BRANCH**. ![Option to open PR in a codespace](/assets/images/help/codespaces/open-with-codespaces-pr.png)
+4. In the {% data variables.product.prodname_codespaces %} tab, click **Create codespace on BRANCH**. ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/open-with-codespaces-pr.png)
 
 ## Reviewing a pull request in {% data variables.product.prodname_codespaces %}
 
@@ -41,4 +41,4 @@ For more information on reviewing a pull request, see "[Reviewing proposed chang
 
 Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review.
 
-  ![Option to open PR in a codespace](/assets/images/help/codespaces/incorporating-codespaces.png)
+  ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/incorporating-codespaces.png)
diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
index a565155d35..78c502e971 100644
--- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
+++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
@@ -2,8 +2,7 @@
 title: ディスカッションについて
 intro: 'ディスカッションでは、質問、質問への回答、情報の共有、発表、{% data variables.product.product_name %} 上のプロジェクトについて会話を実施したり参加したりすることができます。'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
@@ -22,7 +21,7 @@ You might use repository discussions to discuss topics that are specific to the
 
 Issue やプルリクエストをクローズするように、ディスカッションをクローズする必要はありません。
 
-If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who visits the repository can create and participate in discussions for the repository. If an organization owner enables {% data variables.product.prodname_discussions %} for an organization, anyone who can view the source repository can create an organization discussion.
+If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who has access to the repository can create and participate in discussions for the repository. If an organization owner enables {% data variables.product.prodname_discussions %} for an organization, anyone who can view the source repository can create an organization discussion.
 
 リポジトリ管理者とプロジェクトメンテナは、リポジトリ内のディスカッションとディスカッションカテゴリを管理し、ディスカッションを固定してディスカッションの可視性を高めることができます。 モデレータとコラボレータは、コメントを回答としてマークしたり、ディスカッションをロックしたり、Issue をディスカッションに変換したりすることができます。 Similarly, for organization discussions, the role of a user in the source repository determines how a user can interact with organization discussions. 詳しい情報については「[Organizationのリポジトリロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」を参照してください。
 
@@ -30,7 +29,7 @@ For more information about management of discussions, see "[Managing discussions
 
 ## About polls
 
-You can create polls in the polls category to gauge interest in new ideas and project direction. Anyone with read access to your repository can create polls, vote in polls, and view their results. Logged out users can view the results of polls in public repositories.
+You can create polls in the polls category to gauge interest in new ideas and project direction. Anyone with read access to your repository can create polls, vote in polls, and view their results.{% ifversion fpt or ghec %} Signed out users can view the results of polls in public repositories.{% endif %}
 
 Polls require a question and at least two options. You can add a maximum of eight options and the options can contain a maximum of 128 characters.
 
@@ -71,5 +70,5 @@ For more information, see "[Managing categories for discussions](/discussions/ma
 - 「[{% data variables.product.prodname_dotcom %} での書き方と書式設定について](/github/writing-on-github/about-writing-and-formatting-on-github)」
 - 「[ディスカッションを検索する](/search-github/searching-on-github/searching-discussions)」
 - 「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」
-- [コメントと会話の管理](/communities/moderating-comments-and-conversations)
-- 「[{% data variables.product.prodname_dotcom %} での安全性を維持する](/communities/maintaining-your-safety-on-github)」
+- "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)"{% ifversion fpt or ghec %}
+- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"{% endif %}
diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
index ce9ee36260..3003a7986a 100644
--- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
+++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
@@ -4,8 +4,7 @@ shortTitle: メンテナとコラボレーションする
 intro: 'ディスカッションでプロジェクトのメンテナと連絡を取り合うことにより、{% data variables.product.product_name %} でプロジェクトの目標、計画、健全性、およびコミュニティに貢献できます。'
 permissions: 'People with read access to a repository can start and participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can start and participate in discussions and polls in the organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
@@ -53,4 +52,6 @@ You can search for discussions and filter the list of discussions in a repositor
 ## 参考リンク
 
 - 「[{% data variables.product.prodname_dotcom %} での書き方と書式設定について](/github/writing-on-github/about-writing-and-formatting-on-github)」
+{%- ifversion fpt or ghec %}
 - 「[{% data variables.product.prodname_dotcom %} での安全性を維持する](/communities/maintaining-your-safety-on-github)」
+{%- endif %}
diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/index.md
index a486627af1..c2e15ed5cc 100644
--- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/index.md
+++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/index.md
@@ -3,8 +3,7 @@ title: ディスカッションを使用してコミュニティとコラボレ
 shortTitle: ディスカッションを使用してコラボレーションする
 intro: コミュニティメンバーや他のメンテナと集まってプロジェクトについてディスカッションしましょう。
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 children:
   - /about-discussions
   - /participating-in-a-discussion
diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index aafa78e79a..5630ff6f95 100644
--- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -3,8 +3,7 @@ title: ディスカッションに参加する
 intro: '{% data variables.product.product_name %} のプロジェクトのリポジトリ内のフォーラムで、コミュニティやメンテナと会話することができます。'
 permissions: 'People with read access to a repository can participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can participate in discussions and polls in that organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Participate in discussion
 ---
 
@@ -15,7 +14,7 @@ shortTitle: Participate in discussion
 
 In addition to starting or viewing discussions and polls, you can comment in response to the original comment from the author of the discussion. また、ディスカッション内で別のコミュニティメンバーが行った個々のコメントに返信してコメントスレッドを作成し、絵文字でコメントにリアクションすることもできます。
 
-{% data variables.product.product_name %} で、ユーザをブロックし、破壊的なコンテンツを報告して、安全で快適な環境を維持できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} での安全を維持する](/communities/maintaining-your-safety-on-github)」を参照してください。
+{% ifversion fpt or ghec %}You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)."{% endif %}
 
 ## 必要な環境
 
diff --git a/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md
index 37a870574f..6e0bc950d2 100644
--- a/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md
+++ b/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md
@@ -1,10 +1,9 @@
 ---
 title: GitHub におけるコミュニティの会話のベストプラクティス
 shortTitle: コミュニティの会話のベストプラクティス
-intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to an issue when you are ready to scope out the work.'
+intro: ディスカッションを使用してチームとブレインストーミングを行い、作業を確認する状況が整ったら、最終的に会話を Issue に移すことができます。
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
@@ -22,7 +21,7 @@ Issue のオープンおよびディスカッションの相互参照につい
 
 希望する会話のタイプに応じて、ディスカッション、Issue、プルリクエストを作成して参加できます。
 
-You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and develop a project's specific details before committing it to an issue, which can then be scoped. {% data variables.product.prodname_discussions %} is useful for teams if:
+You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and develop a project's specific details before committing it to an issue, which can then be scoped. {% data variables.product.prodname_discussions %} is useful for teams in a number of scenarios.
 - You are in the discovery phase of a project and are still learning which direction your team wants to go in
 - より広いコミュニティからプロジェクトについてのフィードバックを収集する必要がある場合
 - バグ修正、機能リクエスト、一般的な会話を別々に保持する必要がある場合
@@ -34,7 +33,7 @@ Issueは、バグレポートや計画された改善など、プロジェクト
 
 ## コントリビューションガイドラインに従う
 
-Before you open a discussion in an open source repository, check to see if the repository has contributing guidelines. CONTRIBUTING ファイルには、リポジトリメンテナがプロジェクトにアイデアを提供する方法に関する情報が含まれています。
+Before you open a discussion in a repository, check to see if the repository has contributing guidelines. CONTRIBUTING ファイルには、リポジトリメンテナがプロジェクトにアイデアを提供する方法に関する情報が含まれています。
 
 詳しい情報については、「[健全なコントリビューションを促すプロジェクトをセットアップする](/communities/setting-up-your-project-for-healthy-contributions)」を参照してください。
 
diff --git a/translations/ja-JP/content/discussions/guides/finding-your-discussions.md b/translations/ja-JP/content/discussions/guides/finding-your-discussions.md
index dd71f0eb48..59e9b65698 100644
--- a/translations/ja-JP/content/discussions/guides/finding-your-discussions.md
+++ b/translations/ja-JP/content/discussions/guides/finding-your-discussions.md
@@ -2,8 +2,7 @@
 title: Finding your discussions
 intro: You can easily access every discussion you've created or participated in.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Find discussions
 redirect_from:
   - /discussions/guides/finding-discussions-across-multiple-repositories
@@ -12,8 +11,7 @@ redirect_from:
 
 ## ディスカッションを検索する
 
-1. {% data variables.product.prodname_dotcom_the_website %}に移動します。
-1. {% data variables.product.prodname_dotcom_the_website %} の右上隅にあるプロフィール画像をクリックしてから、[**Your discussions**] をクリックします。 ![{% data variables.product.product_name %} のプロフィール画像のドロップダウンメニューにある [Your discussions]](/assets/images/help/discussions/your-discussions.png)
+1. {% data variables.product.product_location %} の右上隅にあるプロフィール画像をクリックしてから、[**Your discussions**] をクリックします。 ![{% data variables.product.product_name %} のプロフィール画像のドロップダウンメニューにある [Your discussions]](/assets/images/help/discussions/your-discussions.png)
 1. [**Created**] と [**Commented**] を切り替えて、作成または参加したディスカッションを表示します。
 
 ## 参考リンク
diff --git a/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
index 3b7b1d0d22..dbd4b46d2c 100644
--- a/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
+++ b/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
@@ -2,8 +2,7 @@
 title: 上位コントリビューターにより高い権限を付与する
 intro: リポジトリ管理者は、コミュニティメンバーをモデレータおよびメンテナに昇格させることができます。
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Grant higher permissions
 ---
 
@@ -16,11 +15,11 @@ shortTitle: Grant higher permissions
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
-1. Compare the list of contributors with their access permissions to the repository or, for organization discussions, to the source repository to see who qualifies to moderate the discussion.
+1. Compare the list of contributors with their access permissions to the repository or, for organization discussions, to the source repository to see who qualifies to moderate the discussion. ![Screenshot of most helpful contributors](/assets/images/help/discussions/most-helpful.png)
 
 ## Step 2: Review permission levels for {% data variables.product.prodname_discussions %}
 
-People with triage permissions for a repository can help moderate a repository's discussions by marking comments as answers, locking discussions that are not longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, people with triage permissions for the source repository for organization discussions can moderate the organization's discussions. 詳しい情報については、「[ ディスカッションをモデレートする](/discussions/managing-discussions-for-your-community/moderating-discussions)」を参照してください。
+People with triage permissions for a repository can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, people with triage permissions for the source repository for organization discussions can moderate the organization's discussions. 詳しい情報については、「[ ディスカッションをモデレートする](/discussions/managing-discussions-for-your-community/moderating-discussions)」を参照してください。
 
 リポジトリの権限レベルおよび {% data variables.product.prodname_discussions %} に関する詳しい情報については、「[Organization のリポジトリの権限レベル](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)」を参照してください。
 
diff --git a/translations/ja-JP/content/discussions/guides/index.md b/translations/ja-JP/content/discussions/guides/index.md
index bad942ecd6..90b71e25ff 100644
--- a/translations/ja-JP/content/discussions/guides/index.md
+++ b/translations/ja-JP/content/discussions/guides/index.md
@@ -3,8 +3,7 @@ title: ディスカッションガイド
 shortTitle: ガイド
 intro: コミュニティのディスカッションに参加したりモニタリングしたりするための最初のステップやベストプラクティスを学びましょう。
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 children:
   - /best-practices-for-community-conversations-on-github
   - /finding-your-discussions
diff --git a/translations/ja-JP/content/discussions/index.md b/translations/ja-JP/content/discussions/index.md
index a6945f78ce..c758d50bbc 100644
--- a/translations/ja-JP/content/discussions/index.md
+++ b/translations/ja-JP/content/discussions/index.md
@@ -1,7 +1,7 @@
 ---
 title: GitHub Discussions のドキュメント
 shortTitle: GitHub Discussions
-intro: '{% data variables.product.prodname_discussions %} は、オープンソースプロジェクトに関するコミュニティ向けの共同コミュニケーションフォーラムです。 コミュニティメンバーは、質問をしたり、質問に答えたり、最新情報を共有したり、自由形式の会話をしたり、コミュニティの動向に影響を与える決定をフォローしたりすることができます。'
+intro: '{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an{% ifversion fpt or ghec %} open source or{% endif %} internal project. コミュニティメンバーは、質問をしたり、質問に答えたり、最新情報を共有したり、自由形式の会話をしたり、コミュニティの動向に影響を与える決定をフォローしたりすることができます。'
 introLinks:
   quickstart: /discussions/quickstart
 featuredLinks:
@@ -27,8 +27,7 @@ examples_source: data/product-examples/discussions/community-examples.yml
 product_video: 'https://www.youtube-nocookie.com/embed/IpBw2SJkFyk'
 layout: product-landing
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 communityRedirect:
   name: Provide GitHub Feedback
   href: 'https://github.com/github/feedback/discussions/categories/discussions-feedback'
diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md
index bcf178bdca..79a8c1d66d 100644
--- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md
@@ -3,8 +3,7 @@ title: コミュニティのディスカッションを管理する
 shortTitle: ディスカッションを管理する
 intro: 'You can enable and configure {% data variables.product.prodname_discussions %} for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 children:
   - /managing-discussions
   - /managing-categories-for-discussions
diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
index 5c272e063b..1c9269cf27 100644
--- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
+++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
@@ -3,8 +3,7 @@ title: Managing categories for discussions
 intro: 'You can categorize discussions to organize conversations for your community members, and you can choose a format for each category.'
 permissions: Repository administrators and people with write or greater access to a repository can manage categories for discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage categories for discussions in the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Manage categories
 redirect_from:
   - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository
@@ -23,7 +22,7 @@ redirect_from:
 
 | カテゴリ            | 目的                                                                    | Format          |
 |:--------------- |:--------------------------------------------------------------------- |:--------------- |
-| 📣 Announcements | Updates and news from project maintainers                             | Announcement    |
+| 📣 Announcements | Updates and news from project maintainers                             | アナウンス           |
 | #️⃣ 全般          | プロジェクトに関連するすべての事柄                                                     | 自由回答形式のディスカッション |
 | 💡 Ideas         | プロジェクトを変更または改善するためのアイデア                                               | 自由回答形式のディスカッション |
 | 🗳 Polls         | Polls with multiple options for the community to vote for and discuss | Polls           |
@@ -43,7 +42,7 @@ redirect_from:
 
 カテゴリを編集して、カテゴリの絵文字、タイトル、説明、およびディスカッション形式を変更できます。
 
-1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to create a category.
+1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to edit a category.
 {% data reusables.discussions.discussions-tab %}
 1. リストのカテゴリの右側にある {% octicon "pencil" aria-label="The pencil icon" %} をクリックします ![リポジトリのカテゴリリストのカテゴリの右側にある [Edit] ボタン](/assets/images/help/discussions/click-edit-for-category.png)
 1. {% data reusables.discussions.edit-category-details %}
@@ -54,7 +53,7 @@ redirect_from:
 
 カテゴリを削除すると、{% data variables.product.product_name %} は、削除されたカテゴリのすべてのディスカッションを、選択した既存のカテゴリに移動します。
 
-1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to create a category.
+1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to delete a category.
 {% data reusables.discussions.discussions-tab %}
 1. リストのカテゴリの右側にある {% octicon "trash" aria-label="The trash icon" %} をクリックします ![リポジトリのカテゴリリストのカテゴリの右側にある [Trash] ボタン](/assets/images/help/discussions/click-delete-for-category.png)
 1. ドロップダウンメニューを使用して、削除するカテゴリのディスカッションの新しいカテゴリを選択します。 ![既存のカテゴリを削除するときに新しいカテゴリを選択するためのドロップダウンメニュー](/assets/images/help/discussions/choose-new-category.png)
diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md
index 05efb78422..5e7528c51f 100644
--- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md
+++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -3,8 +3,7 @@ title: ディスカッションを管理する
 intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
 permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: Manage discussions
 redirect_from:
   - /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
@@ -17,7 +16,7 @@ redirect_from:
 
 Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. 詳しい情報については、「[Organization 内のリポジトリのディスカッションの作成を管理する](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)」を参照してください。
 
-ディスカッションのメンテナとして、コミュニティリソースを作成して、プロジェクト全体の目標に沿ったディスカッションを促し、コラボレータのための親しみやすいオープンフォーラムを維持できます。 コラボレータが従う行動規範またはコントリビューションガイドラインを作成することは、協力的で生産的なフォーラムを促進するのに役立ちます。 コミュニティリソースの作成について詳しくは、「[プロジェクトに行動規範を追加する](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)」および 「[リポジトリコントリビューター向けのガイドラインを設定する](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)」を参照してください。
+ディスカッションのメンテナとして、コミュニティリソースを作成して、プロジェクト全体の目標に沿ったディスカッションを促し、コラボレータのための親しみやすいオープンフォーラムを維持できます。 Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and{% endif %} "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
 
 When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. 詳しい情報については、「[Issue を作成する](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)」を参照してください。
 
@@ -75,7 +74,7 @@ You can pin up to four important discussions above the list of discussions for t
 
 ## ディスカッションを移譲する
 
-ディスカッションを移譲するには、ディスカッションを移譲するリポジトリにディスカッションを作成する権限が必要です。 If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private repository to a public repository.
+ディスカッションを移譲するには、ディスカッションを移譲するリポジトリにディスカッションを作成する権限が必要です。 If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository.
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
index 7836edd013..85a48e2119 100644
--- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
+++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
@@ -1,16 +1,15 @@
 ---
 title: ディスカッションをモデレートする
-intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your community''s code of conduct.'
+intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.'
 permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
 ## ディスカッションのモデレートについて
 
-{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate a repository's discussions by marking comments as answers, locking discussions that are not longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, if you have triage permission for the source repository for organization discussions, you can moderate discussions for that organization.
+{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, if you have triage permission for the source repository for organization discussions, you can moderate discussions for that organization.
 
 ## コメントを回答としてマークする
 
diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
index fbb5d13ed5..0a465b1ced 100644
--- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
+++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
@@ -3,8 +3,7 @@ title: Viewing insights for your discussions
 intro: 'Discussions insights provide data about your discussions'' activity, views, and contributors.'
 permissions: Repository administrators and people with maintain access to a repository can view the insights dashboard for discussions in that repository. Repository administrators and people with maintain access to the source repository for organization discussions can view the insights dashboard for discussions in that organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Discussions
 shortTitle: View discussions insights
diff --git a/translations/ja-JP/content/discussions/quickstart.md b/translations/ja-JP/content/discussions/quickstart.md
index 33566f3d4a..c24ed0dcb2 100644
--- a/translations/ja-JP/content/discussions/quickstart.md
+++ b/translations/ja-JP/content/discussions/quickstart.md
@@ -3,21 +3,20 @@ title: GitHub Discussions のクイックスタート
 intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository or organization and start conversations with your community.'
 allowTitleToDifferFromFilename: true
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: クイックスタート
 ---
 
 
 ## はじめに
 
-{% data variables.product.prodname_discussions %} は、オープンソースプロジェクトに関するコミュニティ向けの共同コミュニケーションフォーラムです。 Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike {% data variables.product.prodname_github_issues %}. Discussions により、公開フォーラムで流動的でオープンな会話ができるようになります。
+{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source or internal project. Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike {% data variables.product.prodname_github_issues %}. Discussions により、公開フォーラムで流動的でオープンな会話ができるようになります。
 
 Discussions では、より協力的な会話ができるように、情報に接続して検索するためのより一元的なエリアを提供しています。
 
 ## リポジトリの {% data variables.product.prodname_discussions %} を有効化する
 
-Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public and private repositories.
+Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public{% ifversion ghes > 3.5 %}, internal{% endif %} and private repositories. The visibility of a discussion is inherited from the repository the discussion is created in.
 
 When you first enable {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post.
 
@@ -29,7 +28,7 @@ When you first enable {% data variables.product.prodname_discussions %}, you wil
 
 ## Enabling {% data variables.product.prodname_discussions %} on your organization
 
-Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.
+Organizationのオーナーは、自分のOrganizationで{% data variables.product.prodname_discussions %}を有効化できます。
 
 {% data reusables.discussions.about-organization-discussions %}
 
@@ -42,7 +41,7 @@ You can welcome your community and introduce a new way to communicate in a repos
 
 ## コントリビューター向けのコミュニティガイドラインを設定する
 
-For repository discussions, you can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. リポジトリの README を更新して、コラボレータが Issue やディスカッションをオープンするタイミングを伝えることもできます。 プロジェクトのガイドラインの提供方法の詳細については、「[プロジェクトに行動規範を追加する](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)」および 「[健全なコントリビューションのためのプロジェクトの設定](/communities/setting-up-your-project-for-healthy-contributions)」を参照してください。
+For repository discussions, you can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. リポジトリの README を更新して、コラボレータが Issue やディスカッションをオープンするタイミングを伝えることもできます。 For more information about providing guidelines for your project, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and{% endif %} "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
 
 For organization discussions, you share information about how to engage with your organization by creating an organization profile README. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."
 
@@ -62,7 +61,7 @@ Any authenticated user who can view a repository can create a poll. Similarly, s
 
 Repository owners and people with write access to the repository can create new categories to keep discussions organized. Similarly, since organization discussions are based on a source repository, repository owners and people with write access to the source repository can create new categories for organization discussions.
 
-参加しているコラボレータが新しいディスカッションを作成する場合、ディスカッションを最も関連性の高い既存のカテゴリにグループ化できます。 ディスカッションは、作成後に再分類することもできます。 For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+Collaborators participating in and creating new discussions can group discussions into the most relevant existing categories. ディスカッションは、作成後に再分類することもできます。 For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
 
 {% data reusables.discussions.you-can-label-discussions %}
 
diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md
index e741ab09ae..6fd7923662 100644
--- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md
+++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md
@@ -136,7 +136,7 @@ Notifications provide updates about the activity on {% data variables.product.pr
 ### 8. {% data variables.product.prodname_pages %} の活用
 You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages)」を参照してください。
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 ### 9. {% data variables.product.prodname_discussions %}を使用する
 You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. 詳しい情報については「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md
index 7f7636461a..e95b28ed6b 100644
--- a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md
+++ b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md
@@ -24,10 +24,9 @@ topics:
 
 {% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
-{% endif %}
-{% ifversion ghes or ghae %}
+{% else %}
 You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
 {% endif %}
 
@@ -100,7 +99,7 @@ The **Files changed** tab of the pull request shows the implemented fix.
 - The user creates a pull request with the fix.
 - A repository maintainer reviews the pull request, comments on it, and merges it.
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 ### Scenarios for {% data variables.product.prodname_discussions %}
 
 - I have a question that's not necessarily related to specific files in the repository.
@@ -147,8 +146,8 @@ For issues, for example, you can tag issues with labels for quicker searching an
 
 For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. 詳しい情報については[プルリクエストについて](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)を参照してください。
 
-{% ifversion fpt or ghec %}
-For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. 詳しい情報については「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。
+{% ifversion discussions %}
+For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt or ghec %} set up a code of conduct and{% endif %} pin discussions that contain important information for your community. 詳しい情報については「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。
 {% endif %}
 
 For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. 詳しい情報については[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)を参照してください。
diff --git a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
index 25ea9223f6..267a791258 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
@@ -47,7 +47,7 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
 | <kbd>G</kbd> <kbd>P</kbd> | [**Pull requests**] タブに移動します。 詳しい情報については、「[プルリクエストについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)」を参照してください。"{% ifversion fpt or ghes or ghec %}
 | <kbd>G</kbd> <kbd>A</kbd> | [**Actions**] タブに移動します。 詳しい情報については、「[アクションについて](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。{% endif %}
 | <kbd>G</kbd> <kbd>B</kbd> | [**Projects**] タブに移動します。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。                                                                                                                                       |
-| <kbd>G</kbd> <kbd>W</kbd> | [**Wiki**] タブに移動します。 For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %}
+| <kbd>G</kbd> <kbd>W</kbd> | [**Wiki**] タブに移動します。 For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion discussions %}
 | <kbd>G</kbd> <kbd>G</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
 
 ## ソースコード編集
diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
index 42bc9af90d..e536c4a135 100644
--- a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
+++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
@@ -69,7 +69,7 @@ Look! You can see my backticks.
 {% ifversion mermaid %}
 ## Creating diagrams
 
-You can also use code blocks to create diagrams in Markdown. GitHub supports Mermaid, geoJSON, topoJSON, and ASCII STL syntax. For more information, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)."
+You can also use code blocks to create diagrams in Markdown. GitHub supports Mermaid, GeoJSON, TopoJSON, and ASCII STL syntax. For more information, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)."
 
 {% endif %}
 ## 参考リンク
diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
index 58b21e3a35..edda6cad81 100644
--- a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
+++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
@@ -38,11 +38,11 @@ graph TD;
 
 {% endnote %}
 
-## Creating geoJSON and topoJSON maps
+## Creating GeoJSON and TopoJSON maps
 
-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. 詳しい情報については[コードブロックの作成とハイライト](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)を参照してください。
+You can use GeoJSON/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. 詳しい情報については[コードブロックの作成とハイライト](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)を参照してください。
 
-### Using geoJSON
+### Using GeoJSON
 
 For example, you can create a simple map:
 
@@ -77,9 +77,9 @@ For example, you can create a simple map:
 
 ![Rendered map](/assets/images/help/writing/fenced-geojson-rendered-map.png)
 
-### Using topoJSON
+### Using TopoJSON
 
-For example, you can create a simple topoJSON map:
+For example, you can create a simple TopoJSON map:
 
 <pre>
 ```topojson
diff --git a/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md
index e21bc40ca8..8ee52758f5 100644
--- a/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md
+++ b/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -2,8 +2,7 @@
 title: ディスカッションでのGraphQL APIの利用
 intro: '{% data variables.product.prodname_discussions %} GraphQL APIの使い方を学んでください。'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: ディスカッションでのGraphQLの利用
 ---
 
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 f557123324..b3cfff4f1d 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
@@ -48,7 +48,8 @@ Issueの最新のコメントの情報を得ておきたい場合には、Issue
 
 コメントに注意してもらうために、Issue内でリポジトリにアクセスできるコラボレータを@メンションできます。 同じリポジトリ内の関連するIssueをリンクするために、`#`につづいてIssueのタイトルの一部を続け、リンクしたいIssueをクリックできます。 責任を伝えるために、Issueを割り当てることができます。 同じコメントを頻繁に入力しているなら、返信テンプレートを利用できます。
 {% ifversion fpt or ghec %}詳しい情報については「[基本的な記述とフォーマットの構文](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)」及び「[他のGitHubユーザへのIssueやPull Requestの割り当て](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)」を参照してください。
-
+{% endif %}
+{% ifversion discussions %}
 ## Issueとディスカッションの比較
 
 会話の中には、{% data variables.product.prodname_discussions %}に適しているものもあります。 {% data reusables.discussions.you-can-use-discussions %} Issueあるいはディスカッションを使う場合のガイダンスについては「[GitHubでのコミュニケーション](/github/getting-started-with-github/quickstart/communicating-on-github)」を参照してください。
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index 3f53ee62f6..82eb0413cf 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -90,7 +90,7 @@ IssueもしくはPull Requestのコメントから、新しいIssueをオープ
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 
 ## ディスカッションからのIssueの作成
 
diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
index 0ec5668834..549f88e937 100644
--- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
+++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -1,6 +1,6 @@
 ---
 title: Organizationについて
-intro: 'Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once, with sophisticated security and administrative features.'
+intro: Organizationは、洗練されたセキュリティと管理機能を備えた、企業とオープンソースプロジェクトが多くのプロジェクトに渡って協力しあえる共有アカウントです。
 redirect_from:
   - /articles/about-organizations
   - /github/setting-up-and-managing-organizations-and-teams/about-organizations
@@ -18,20 +18,20 @@ topics:
 
 {% data reusables.organizations.about-organizations %} アカウントの種類に関する詳しい情報については「[{% data variables.product.prodname_dotcom %}アカウントの種類](/get-started/learning-about-github/types-of-github-accounts)」を参照してください。
 
-You can invite an unlimited number of people to join your organization, then give these organization members a variety of roles that grant different levels of access to the organization and its data. 詳しい情報については「[Organization内のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)」を参照してください。
+組織に参加してもらうよう、人数に制限無く招待をして、それらのOrganizationメンバーに、Organizationとそのデータに対して様々なレベルのアクセスを付与する様々なロールを与えることができます。 詳しい情報については「[Organization内のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)」を参照してください。
 
-In addition to managing access to the organization itself, you can separately manage access to your organization's repositories, project boards, and apps. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)", "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)", and "[Managing access to your organization's apps](/organizations/managing-access-to-your-organizations-apps)."
+Organizationそのものへのアクセスの管理に加え、別個にOrganizationのリポジトリ、プロジェクトボード、アプリケーションへのアクセスも管理できます。 詳しい情報については「[Organizationのリポジトリロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」、「[Organizationのプロジェクトボードの権限](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)」、「[Organizationのアプリケーションへのアクセス管理](/organizations/managing-access-to-your-organizations-apps)」を参照してください。
 
-To simplify access management and enhance collaboration, you can create nested teams that reflect your group's structure, with cascading access permissions and mentions. 詳細は「[Team について](/organizations/organizing-members-into-teams/about-teams)」を参照してください。
+アクセス管理をシンプルにし、コラボレーションを拡大するために、カスケードされた権限とメンションを持つ、グループの構造を反映した入れ子チームを作成できます。 詳細は「[Team について](/organizations/organizing-members-into-teams/about-teams)」を参照してください。
 
-You can configure the organization to meet the unique needs of your group by managing settings, such as restricting the types of repositories that members can create. For more information, see "[Managing organization settings](/organizations/managing-organization-settings)."
+メンバーが作成できるリポジトリの種類の制限などの設定を管理することによって、自分のグループ特有の要求を満たすようにOrganizationを設定できます。 詳しい情報については「[Organizationの設定の管理](/organizations/managing-organization-settings)」を参照してください。
 
-To harden your organization's security, you can enforce security requirements and review the organization's audit log. For more information, see "[Keeping your organization secure](/organizations/keeping-your-organization-secure)."
+Organizationのセキュリティを強化するために、セキュリティの要件を適用し、OrganizationのAudit logをレビューできます。 詳しい情報については「[Organizationをセキュアに保つ](/organizations/keeping-your-organization-secure)」を参照してください。
 
 {% data reusables.organizations.org-ownership-recommendation %}詳細は、「[Organization の所有権の継続性を管理する](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)」を参照してください。
 
 {% ifversion fpt or ghec %}
-## About feature availability
+## 利用できる機能について
 
 {% data reusables.organizations.organization-plans %}
 {% endif %}
@@ -44,7 +44,7 @@ Enterpriseアカウントは、オーナーが複数のOrganizationのポリシ
 {% ifversion ghec %}Enterpriseアカウントに属するOrganizationでは、支払いはEnterpriseアカウントのレベルで管理され、支払い設定はOrganizationレベルでは利用できません。{% endif %}EnterpriseオーナーはEnterpriseアカウント内のすべてのOrganizationに対するポリシーを設定するか、OrganizationのオーナーにOrganizationレベルでポリシーを設定できるよう許可することができます。 Organization のオーナーは、Enterprise アカウントのレベルで Organization に強制された設定を変更することはできません。 Organization のポリシーや設定について質問がある場合は Enterprise アカウントのオーナーに問い合わせてください。
 
 {% ifversion ghec %}
-{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
+{% data reusables.enterprise.create-an-enterprise-account %} 詳しい情報については「[Enterpriseアカウントの作成](/admin/overview/creating-an-enterprise-account)」を参照してください。
 
 {% data reusables.enterprise-accounts.invite-organization %}
 {% endif %}
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
index 4aa44e907a..219fb4280e 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -816,4 +816,6 @@ For more information, see "[Managing the publication of {% data variables.produc
 ## Further reading
 
 - "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %}
+{%- ifversion fpt or ghec %}
 - "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
+{%- endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
index 0d9d079b7d..ba946be185 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
@@ -140,7 +140,7 @@ Organizationレベルの設定の管理に加えて、Organizationのオーナ
 | [リポジトリのアーカイブ](/articles/about-archiving-repositories)                                                                                                                                                                                                                                                                                                                                                                            |       |        |       |          |                 **X** |{% ifversion fpt or ghec %}
 | スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照)                                                                                                                                                                                                                                                                                                                               |       |        |       |          |                         **X** 
 {% endif %}
-| JiraやZendeskなどの外部リソースに対する自動リンク参照の作成 (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。                                                                                                                                                                                                                                                                                               |       |        |       |          |                 **X** |{% ifversion fpt or ghec %}
+| JiraやZendeskなどの外部リソースに対する自動リンク参照の作成 (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。                                                                                                                                                                                                                                                                                               |       |        |       |          |                 **X** |{% ifversion discussions %}
 | リポジトリの [{% data variables.product.prodname_discussions %} の有効化](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)                                                                                                                                                                                                                                                                    |       |        |       |  **X**   |                                **X**                                |
 | {% data variables.product.prodname_discussions %} の[カテゴリの作成および編集](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)                                                                                                                                                                                                                                                                      |       |        |       |  **X**   |                                **X**                                |
 | [ディスカッションを別のカテゴリに移動する](/discussions/managing-discussions-for-your-community/managing-discussions)                                                                                                                                                                                                                                                                                                                                |       |        | **X** |  **X**   |                                **X**                                |
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
index 1f35a4a9fb..70895a13ef 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
@@ -3,8 +3,7 @@ title: OrganizationでのGitHub Discussionsの有効化もしくは無効化
 intro: 'Organization内の1つのリポジトリに限定されない会話をするための場所として、{% data variables.product.prodname_discussions %}をOrganizationで利用できます。'
 permissions: 'Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Organizations
 shortTitle: Organizationのディスカッション
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/index.md b/translations/ja-JP/content/organizations/managing-organization-settings/index.md
index 2f977fef8e..3981302429 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/index.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/index.md
@@ -27,6 +27,7 @@ children:
   - /allowing-people-to-delete-issues-in-your-organization
   - /enabling-or-disabling-github-discussions-for-an-organization
   - /managing-discussion-creation-for-repositories-in-your-organization
+  - /managing-the-commit-signoff-policy-for-your-organization
   - /setting-team-creation-permissions-in-your-organization
   - /managing-scheduled-reminders-for-your-organization
   - /managing-the-default-branch-name-for-repositories-in-your-organization
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index 5d7d1bcafb..dc3e754f07 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -5,8 +5,7 @@ redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization
 permissions: Organization owners can manage discussion creation for repositories owned by the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Organizations
   - Teams
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
new file mode 100644
index 0000000000..66928608d1
--- /dev/null
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
@@ -0,0 +1,25 @@
+---
+title: Managing the commit signoff policy for your organization
+intro: 'You can require users to automatically sign off all commits they make in {% data variables.product.product_name %}''s web interface to repositories owned by your organization.'
+versions:
+  feature: commit-signoffs
+permissions: Organization owners can require all commits to repositories owned by the organization be signed off by the commit author.
+topics:
+  - Organizations
+shortTitle: Manage the commit signoff policy
+---
+
+## About commit signoffs
+
+To affirm that a commit complies with the rules and licensing governing a repository, many organizations require developers to sign off on every commit. If your organization requires commit signoffs, you can make signing off a seamless part of the commit process by enabling compulsory commit signoffs for users committing through {% data variables.product.product_name %}'s web interface. After you enable compulsory commit signoffs for an organization, every commit made to repositories in that organization through {% data variables.product.product_name %}'s web interface will automatically be signed off on by the commit author.
+
+People with admin access to a repository can also enable compulsory commit signoffs at the repository level. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
+{% data reusables.repositories.commit-signoffs %}
+
+## Managing compulsory commit signoffs for your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.repository-defaults %}
+1. Select or deselect **Require contributors to sign off on web-based commits**. ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/organizations/require-signoffs.png)
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index 27fb80e687..64d36defce 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -22,6 +22,9 @@ Organization のオーナーは、Organization 内のメンバー名表示を管
 
 Organization の各メンバーは、自分のプロフィール名を設定で選択します。 詳細は「[プロフィールをパーソナライズする](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)」を参照してください。
 
+{% ifversion profile-name-enterprise-setting %}
+You may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)」を参照してください。{% endif %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
index c0947122b6..8e453b64f0 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -49,7 +49,7 @@ Organization内では、ロールをOrganization、Team、リポジトリのレ
 
 継承されたロールにまだ含まれていない場合にのみ、追加の権限を選択できます。 たとえば、継承されたロールがリポジトリへの**Write**アクセスを提供しているなら、"Close a pull request"権限は継承されたロールに既に含まれています。
 
-{% ifversion ghec %}
+{% ifversion discussions %}
 ### Discussions
 
 - **Create a discussion category（ディスカッションカテゴリの作成）**: 新しいディスカッションカテゴリを作成できる。 詳しい情報については「[新しいディスカッションカテゴリの作成](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)」を参照してください。
diff --git a/translations/ja-JP/content/packages/index.md b/translations/ja-JP/content/packages/index.md
index a03b3d8bbe..df29da2cf1 100644
--- a/translations/ja-JP/content/packages/index.md
+++ b/translations/ja-JP/content/packages/index.md
@@ -12,10 +12,11 @@ featuredLinks:
     - /packages/learn-github-packages/installing-a-package
   popular:
     - /packages/working-with-a-github-packages-registry/working-with-the-npm-registry
-    - '{% ifversion fpt or ghec or ghes > 3.4 %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}'
+    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
     - /packages/learn-github-packages
     - /packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry
   guideCards:
+    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
     - '{% ifversion fpt or ghec or ghes > 3.4 %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}'
     - /packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry
 changelog:
diff --git a/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
index 360f84b646..91da35239e 100644
--- a/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
+++ b/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -16,7 +16,7 @@ shortTitle: アクセスコントロールと可視性
 
 詳細な権限を持つパッケージは、個人ユーザもしくはOrganizationアカウントをスコープとします。 パッケージのアクセス制御と可視性は、パッケージに接続された（あるいはリンクされた）リポジトリは別個に変更できます。
 
-現在は、{% data variables.product.prodname_container_registry %}でのみ詳細な権限を使うことができます。 詳細な権限は、npmレジストリなど他のパッケージレジストリではサポートされていません。
+現在は、{% data variables.product.prodname_container_registry %}でのみ詳細な権限を使うことができます。 Granular permissions are not supported in our other package registries, such as the npm registry.{% ifversion docker-ghcr-enterprise-migration %} For more information about migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."{% endif %}
 
 リポジトリをスコープとするパッケージの権限や、PATに関するパッケージ関連のスコープ、Actionsのワークフローの権限の管理についての詳しい情報は、「[GitHub Packagesの権限について](/packages/learn-github-packages/about-permissions-for-github-packages)」を参照してください。
 
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
index eca15605e1..c8b05d49f1 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -1,6 +1,6 @@
 ---
 title: Dockeerレジストリからコンテナレジストリへの移行
-intro: '以前はDockerレジストリに保存されていたDockerイメージは、自動的に{% data variables.product.prodname_container_registry %}に移行されます。'
+intro: '{% ifversion docker-ghcr-enterprise-migration %}An enterprise owner can{% else %}{% data variables.product.company_short %} will{% endif %} migrate Docker images previously stored in the Docker registry on {% data variables.product.product_location %} to the {% data variables.product.prodname_container_registry %}.'
 product: '{% data reusables.gated-features.packages %}'
 redirect_from:
   - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
@@ -9,35 +9,61 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: コンテナレジストリへの移行
+  feature: docker-ghcr-enterprise-migration
+shortTitle: Migration to Container registry
+topics:
+  - Containers
+  - Docker
+  - Migration
 ---
 
-{% data variables.product.prodname_dotcom %}のDockerレジストリは、{% data variables.product.prodname_container_registry %}で置き換えられました。 DockerイメージをDockerレジストリに保存していたなら、それらは自動的に{% data variables.product.prodname_container_registry %}に移されます。 あなたは何もする必要がありません。 Dockerレジストリ(`docker.pkg.github.com`) に名前空間を使っていたスクリプトや{% data variables.product.prodname_actions %}のワークフローは、{% data variables.product.prodname_container_registry %}(`ghcr.io`)への移行後も動作し続けます。
+{% data reusables.package_registry.container-registry-ghes-beta %}
 
-移行は一度にではなく、徐々に行われます。 まだイメージが移動されていなければ、待ち続けてください。遠からずそれらは移行されます。
+## {% data variables.product.prodname_container_registry %} について
 
-## イメージが移行されたかはどうすれば分かりますか？
+{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
 
-Dockerイメージが{% data variables.product.prodname_container_registry %}に移行されると、そのパッケージの詳細ページに以下の変更が示されます。
+## About migration from the Docker registry
 
-* 以前はDockerロゴだったアイコンは{% data variables.product.prodname_container_registry %}ロゴになります。
-* 以前は`docker.pkg.github.com`だったプルURL内のドメインは、`ghcr.io`になります。
+{% data reusables.package_registry.container-registry-replaces-docker-registry %} If you've stored Docker images in the Docker registry, {% ifversion docker-ghcr-enterprise-migration %}an enterprise owner{% else %}{% data variables.product.company_short %}{% endif %} will gradually migrate the images to the {% data variables.product.prodname_container_registry %}. No action is required on your part.
 
-![{% data variables.product.prodname_container_registry %}詳細ページ](/assets/images/help/package-registry/container-registry-details-page.png)
+{% ifversion docker-ghcr-enterprise-migration %}
 
-## {% data variables.product.prodname_container_registry %}とDockerレジストリの主な違い
+{% note %}
 
-{% data variables.product.prodname_container_registry %}は、コンテナに固有の要求をサポートするために最適化されています。
+**Note**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
 
-{% data variables.product.prodname_container_registry %}を使うと、以下のことができます。
-- コンテナイメージをOrganizationや個人アカウント内に保存するか、リポジトリに接続する。
-- 権限をリポジトリから継承するか、リポジトリとは独立に詳細な権限を設定するかを選択する。
-- 匿名でパブリックなコンテナイメージにアクセスする。
+{% endnote %}
 
-### Dockerイメージの詳細に関するAPIクエリ
+{% endif %}
 
-移行後は、GraphQL APIを使って`PackageType` "DOCKER"のパッケージに対するクエリを実行することはできなくなります。 その代わりに、REST APIを使って`package_type` "container"のパッケージに対するクエリを実行できるようになります。 詳しい情報については、REST APIの記事「[パッケージ](/rest/reference/packages)」を参照してください。
+After a Docker image has been migrated to the {% data variables.product.prodname_container_registry %}, you'll see the following changes to the details for the package.
 
-## 支払い
+- The icon will be the {% data variables.product.prodname_container_registry %} logo instead of the Docker logo.
+- The domain in the pull URL will be {% data variables.product.prodname_container_registry_namespace %} instead of {% data variables.product.prodname_docker_registry_namespace %}.
 
-{% data variables.product.prodname_container_registry %}に対する支払に関する詳しい情報については「[{% data variables.product.prodname_registry %}の支払について](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)」を参照してください。
+{% ifversion fpt or ghec %}
+
+![Screenshot of a Docker image migrated to the {% data variables.product.prodname_container_registry %}](/assets/images/help/package-registry/container-registry-details-page.png)
+
+{% endif %}
+
+{% data reusables.package_registry.container-registry-migration-namespaces %}
+
+{% ifversion fpt or ghec %}
+
+After migration, you'll no longer be able to use the GraphQL API to query for packages with a `PackageType` of "DOCKER". Instead, you can use the REST API to query for packages with a `package_type` of "container". For more information, see "[Packages](/rest/reference/packages)" in the REST API documentation.
+
+## {% data variables.product.prodname_container_registry %}の支払いについて
+
+For more information about billing for the {% data variables.product.prodname_container_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+
+{% endif %}
+
+{% ifversion docker-ghcr-enterprise-migration %}
+
+## 参考リンク
+
+- "[Migrating your enterprise to the {% data variables.product.prodname_container_registry %} from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)"
+
+{% endif %}
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
index 72fcea30ab..02708a404d 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -18,19 +18,19 @@ versions:
   ghes: '>= 3.5'
 shortTitle: Container registry
 ---
-{% ifversion ghes > 3.4 %}
-{% note %}
 
-**Note**: {% data variables.product.prodname_container_registry %} is currently in beta for {% data variables.product.product_name %} and subject to change.
+{% data reusables.package_registry.container-registry-ghes-beta %}
 
-{% endnote %}
-{% endif %}
+## About the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-benefits %}
 
 {% ifversion ghes > 3.4 %}
-## Prerequisites
 
-To configure and use the {% data variables.product.prodname_container_registry %} on {% data variables.product.prodname_ghe_server %}, your site administrator must first enable {% data variables.product.prodname_registry %} **and** subdomain isolation. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" and "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)."
+To use the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, your site administrator must first configure {% data variables.product.prodname_registry %} for your instance **and** enable subdomain isolation. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" and "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)."
+
 {% endif %}
+
 ## About {% data variables.product.prodname_container_registry %} support
 
 The {% data variables.product.prodname_container_registry %} currently supports the following container image formats:
diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
index 83cca63e32..cd875e1de0 100644
--- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
+++ b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
@@ -18,6 +18,9 @@ versions:
 
 {% data reusables.commits.about-commits %}
 
+{% ifversion commit-signoffs %}
+If the repository you are committing to has compulsory commit signoffs enabled, and you are committing via the web interface, you will automatically sign off on the commit as part of the commit process. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)." {% endif %}
+
 共同作業しているコミットに共作者を追加できます。 詳しい情報については、「[複数の作者を持つコミットを作成する](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)」を参照してください。
 
 {% ifversion fpt or ghec %}
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
index 0b958cd325..09a01f0cad 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
@@ -1,11 +1,9 @@
 ---
 title: リポジトリの GitHub Discussions を有効化または無効化する
 intro: 'You can use {% data variables.product.prodname_discussions %} in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.'
-product: '{% data reusables.gated-features.discussions %}'
 permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_discussions %} for the repository.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Repositories
 redirect_from:
@@ -19,7 +17,7 @@ shortTitle: Discussions
 {% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %}
 1. Discussions を無効化するには、[Features] で [**Discussions**] の選択を解除します。
 
-You can also use organization discussions to facilitate conversations that span multiple repositories in your organization. For more information, see "[Enabling or disabling GitHub Discussions for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+You can also use organization discussions to facilitate conversations that span multiple repositories in your organization. 詳しい情報については「[OrganizationでのGitHub Discussionsの有効化もしくは無効化](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)」を参照してください。
 
 ## 参考リンク
 
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
index b22a9ce9ea..a85fb3b0fc 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
@@ -13,6 +13,7 @@ children:
   - /managing-teams-and-people-with-access-to-your-repository
   - /managing-the-forking-policy-for-your-repository
   - /managing-pull-request-reviews-in-your-repository
+  - /managing-the-commit-signoff-policy-for-your-repository
   - /managing-git-lfs-objects-in-archives-of-your-repository
   - /enabling-anonymous-git-read-access-for-a-repository
   - /about-email-notifications-for-pushes-to-your-repository
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
new file mode 100644
index 0000000000..0e76db15bc
--- /dev/null
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
@@ -0,0 +1,24 @@
+---
+title: Managing the commit signoff policy for your repository
+intro: 'You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}''s web interface.'
+versions:
+  feature: commit-signoffs
+permissions: Organization owners and repository administrators can require all commits to a repository to be signed off by the commit author.
+topics:
+  - Repositories
+shortTitle: Manage the commit signoff policy
+---
+
+## About commit signoffs
+
+Commit signoffs enable users to affirm that a commit complies with the rules and licensing governing a repository. You can enable compulsory commit signoffs on individual repositories for users committing through {% data variables.product.product_location %}'s web interface, making signing off on a commit a seemless part of the commit process. Once compulsory commit signoffs are enabled for a repository, every commit made to that repository through {% data variables.product.product_location %}'s web interface will automatically be signed off on by the commit author.
+
+Organization owners can also enable compulsory commit signoffs at the organization level. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)."
+
+{% data reusables.repositories.commit-signoffs %}
+
+## Enabling or disabling compulsory commit signoffs for your repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Select **Require contributors to sign off on web-based commits**. ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png)
diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index e18e4e9f73..709ad63c9b 100644
--- a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -63,7 +63,7 @@ You can create new releases with release notes, @mentions of contributors, and l
 ![Releases description](/assets/images/enterprise/3.5/releases/releases_description_auto.png){% endif %}
 1. オプションで、コンパイルされたプログラムなどのバイナリファイルをリリースに含めるには、ドラッグアンドドロップするかバイナリボックスで手動で選択します。 ![リリースに DMG ファイルを含める](/assets/images/help/releases/releases_adding_binary.gif)
 2. リリースが不安定であり、運用準備ができていないことをユーザに通知するには、[**This is a pre-release**] を選択します。 ![リリースをプレリリースとしてマークするチェックボックス](/assets/images/help/releases/prerelease_checkbox.png)
-{%- ifversion fpt or ghec %}
+{%- ifversion discussions %}
 1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![リリースディスカッションを作成するためのチェックボックスと、カテゴリを選択するドロップダウンメニュー](/assets/images/help/releases/create-release-discussion.png)
 {%- endif %}
 9. リリースを公開する準備ができている場合は、[**Publish release**] をクリックします。 リリースの作業を後でする場合は、[**Save draft**] をクリックします。 ![[Publish release] と [Save draft] ボタン](/assets/images/help/releases/release_buttons.png)
diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
index 61d4e1203f..6ec81c8e7f 100644
--- a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
+++ b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
@@ -233,9 +233,9 @@ HTML ドキュメントへのコミットのレンダリング済みビューは
 
 通常、埋め込み HTML を含むドキュメントへの変更のレンダリング済みビューでは、{% data variables.product.product_name %} のドキュメントのビューでサポートされている要素への変更を表示します。 埋め込み HTML を含むドキュメントへの変更のレビューは、完全を期して、常にレンダリング済みとソースの両方のビューで行う必要があります。
 
-## Mapping geoJSON files on {% data variables.product.prodname_dotcom %}
+## Mapping GeoJSON/TopoJSON files on {% data variables.product.prodname_dotcom %}
 
-{% data variables.product.product_name %} は、{% data variables.product.product_name %} リポジトリでの geoJSON および topoJSON マップ ファイルのレンダリングをサポートしています。 `.geojson` または `.topojson` 拡張子を使って、通常と同じようにファイルをコミットするだけです。 `.json` 拡張子の付いたファイルもサポートされますが、`type` が `FeatureCollection`、`GeometryCollection`、または `topology` に設定されている場合に限られます。 コミット後、GitHub.com で geoJSON ファイルのパスに移動してください。
+{% data variables.product.product_name %} supports rendering GeoJSON and TopoJSON map files within {% data variables.product.product_name %} repositories. `.geojson` または `.topojson` 拡張子を使って、通常と同じようにファイルをコミットするだけです。 `.json` 拡張子の付いたファイルもサポートされますが、`type` が `FeatureCollection`、`GeometryCollection`、または `topology` に設定されている場合に限られます。 Then, navigate to the path of the GeoJSON/TopoJSON file on GitHub.com.
 
 右側にある紙アイコンをクリックすると、そのファイル ドキュメントに加えられた変更も、コミットの一部として表示されます。
 
@@ -243,12 +243,12 @@ HTML ドキュメントへのコミットのレンダリング済みビューは
 
 ### Geometry types
 
-{% data variables.product.product_name %} のマップは [Leaflet.js](http://leafletjs.com) を使用し、[geoJSON の仕様](http://www.geojson.org/geojson-spec.html) (Point、LineString、Polygon、MultiPoint、MultiLineString、MultiPolygon、GeometryCollection) に概要が示されているジオメトリのタイプをすべてサポートしています。 TopoJSON ファイルは "Topology" タイプで、[topoJSON の仕様](https://github.com/mbostock/topojson/wiki/Specification)に従っている必要があります。
+{% data variables.product.product_name %} のマップは [Leaflet.js](http://leafletjs.com) を使用し、[geoJSON の仕様](http://www.geojson.org/geojson-spec.html) (Point、LineString、Polygon、MultiPoint、MultiLineString、MultiPolygon、GeometryCollection) に概要が示されているジオメトリのタイプをすべてサポートしています。 TopoJSON files should be type "Topology" and adhere to the [TopoJSON spec](https://github.com/mbostock/topojson/wiki/Specification).
 
 {% ifversion geoJSON-with-MapBox %}
 ### フィーチャーのスタイリング
 
-GeoJSON オブジェクトのプロパティで追加のメタデータを渡すと、特定の色を指定する、説明アイコンを追加するなど、フィーチャーの表示方法をカスタマイズすることができます。 オプションは次のとおりです:
+You can customize the way features are displayed, such as specifying a particular color or adding a descriptive icon, by passing additional metadata within the GeoJSON object's properties. オプションは次のとおりです:
 
 * `marker-size` - `small`、`medium`、または `large`
 * `marker-color` - 有効な RGB 16 進カラー
@@ -264,7 +264,7 @@ GeoJSON オブジェクトのプロパティで追加のメタデータを渡す
 
 ### マップを他の場所に埋め込む
 
-GeoJSON マップを {% data variables.product.product_name %} 以外の場所で使用するには、 次のテンプレートを修正し、JavaScript をサポートしている任意の HTML ページに貼り付けてください (例: [{% data variables.product.prodname_pages %}](http://pages.github.com))。
+Want to make your GeoJSON map available someplace other than {% data variables.product.product_name %}? Simply modify this template, and place it in any HTML page that supports JavaScript (e.g., [{% data variables.product.prodname_pages %}](http://pages.github.com)):
 
 ```html
 <script src="https://embed.github.com/view/geojson/<username>/<repo>/<ref>/<path_to_file>"></script>
@@ -287,7 +287,7 @@ GeoJSON マップを {% data variables.product.product_name %} 以外の場所
 {% ifversion mermaid %}
 ### Mapping in Markdown
 
-You can embed geoJSON and topoJSON directly in Markdown. For more information, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-geojson-and-topojson-maps)."
+You can embed GeoJSON and TopoJSON directly in Markdown. For more information, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-geojson-and-topojson-maps)."
 {% endif %}
 
 ### クラスタリング
@@ -300,7 +300,7 @@ You can embed geoJSON and topoJSON directly in Markdown. For more information, s
 
 ### トラブルシューティング
 
-geoJSON ファイルのレンダリングに問題がある場合は、[geoJSON 文法チェッカー](http://geojsonlint.com/)でそのファイルを実行し、有効な geoJSON ファイルであることを確認してください。 ポイントが、意図しない場所 (<em></em>海の中など) にある場合、そのデータには、現在サポートされていない投影法が使われている可能性があります。 現在、{% data variables.product.product_name %}でサポートされているのは `urn:ogc:def:crs:OGC:1.3:CRS84` 投影だけです。
+If you're having trouble rendering GeoJSON files, ensure you have a valid GeoJSON file by running it through a [GeoJSON linter](http://geojsonlint.com/). ポイントが、意図しない場所 (<em></em>海の中など) にある場合、そのデータには、現在サポートされていない投影法が使われている可能性があります。 現在、{% data variables.product.product_name %}でサポートされているのは `urn:ogc:def:crs:OGC:1.3:CRS84` 投影だけです。
 
 また、10 MB を超えるような大きな `.geojson` ファイルは、ブラウザではレンダリングできません。 その場合は通常、次のようなメッセージが表示されます:
 
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 5f05d74dbb..a0fd80932c 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
@@ -355,6 +355,7 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > x-ratelimit-limit: 60
 > x-ratelimit-remaining: 56
+> x-ratelimit-used: 4
 > x-ratelimit-reset: 1372700873
 ```
 
@@ -362,6 +363,7 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 | ----------------------- | ----------------------------------------------------------------------------- |
 | `x-ratelimit-limit`     | 1 時間あたりのリクエスト数の上限。                                                            |
 | `x-ratelimit-remaining` | 現在のレート制限ウィンドウに残っているリクエストの数。                                                   |
+| `x-ratelimit-used`      | 現在のレート制限ウィンドウ内で発行したリクエスト数。                                                    |
 | `x-ratelimit-reset`     | 現在のレート制限ウィンドウが [UTC エポック秒](http://en.wikipedia.org/wiki/Unix_time)でリセットされる時刻。 |
 
 時刻に別の形式を使用する必要がある場合は、最新のプログラミング言語で作業を完了できます。 たとえば、Web ブラウザでコンソールを開くと、リセット時刻を JavaScript の Date オブジェクトとして簡単に取得できます。
@@ -378,6 +380,7 @@ new Date(1372700873 * 1000)
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
 > x-ratelimit-limit: 60
 > x-ratelimit-remaining: 0
+> x-ratelimit-used: 60
 > x-ratelimit-reset: 1377013266
 
 > {
@@ -396,6 +399,7 @@ $ curl -u my_client_id:my_client_secret -I {% data variables.product.api_url_pre
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > x-ratelimit-limit: 5000
 > x-ratelimit-remaining: 4966
+> x-ratelimit-used: 34
 > x-ratelimit-reset: 1372700873
 ```
 
@@ -639,4 +643,3 @@ $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_ur
 [uri]: https://github.com/hannesg/uri_template
 
 [pagination-guide]: /guides/traversing-with-pagination
-
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md b/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md
index 1ea1c006ba..17f02430d0 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md
@@ -2,8 +2,7 @@
 title: ディスカッションを検索する
 intro: '{% data variables.product.product_name %} 上のディスカッションを検索し、検索修飾子を使用して検索結果を絞り込むことができます。'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - GitHub search
 redirect_from:
diff --git a/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md b/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md
index 7e32fc51c4..0beba8ec7a 100644
--- a/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md
@@ -17,6 +17,8 @@ redirect_from:
   - /github/working-with-github-support/github-enterprise-cloud-support
   - /articles/business-plan-support
   - /articles/github-business-cloud-support
+  - /admin/enterprise-support/about-support-for-advanced-security
+  - /enterprise-server/admin/enterprise-support/about-support-for-advanced-security
 topics:
   - Support
 ---
diff --git a/translations/ja-JP/data/features/GH-advisory-db-erlang-support.yml b/translations/ja-JP/data/features/GH-advisory-db-erlang-support.yml
new file mode 100644
index 0000000000..bfb6aa0a58
--- /dev/null
+++ b/translations/ja-JP/data/features/GH-advisory-db-erlang-support.yml
@@ -0,0 +1,7 @@
+#Reference: Issue #6207.
+#We have added support for Elixir advisories to the Advisory Database.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-6207'
diff --git a/translations/ja-JP/data/features/audit-log-streaming.yml b/translations/ja-JP/data/features/audit-log-streaming.yml
new file mode 100644
index 0000000000..1ff0517353
--- /dev/null
+++ b/translations/ja-JP/data/features/audit-log-streaming.yml
@@ -0,0 +1,5 @@
+#Reference: #7055
+#Documentation for audit log streaming
+versions:
+  ghec: '*'
+  ghes: '>= 3.6'
diff --git a/translations/ja-JP/data/features/commit-signoffs.yml b/translations/ja-JP/data/features/commit-signoffs.yml
new file mode 100644
index 0000000000..26fe611963
--- /dev/null
+++ b/translations/ja-JP/data/features/commit-signoffs.yml
@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6049'
diff --git a/translations/ja-JP/data/features/discussions.yml b/translations/ja-JP/data/features/discussions.yml
new file mode 100644
index 0000000000..66a3bb8592
--- /dev/null
+++ b/translations/ja-JP/data/features/discussions.yml
@@ -0,0 +1,4 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
diff --git a/translations/ja-JP/data/features/docker-ghcr-enterprise-migration.yml b/translations/ja-JP/data/features/docker-ghcr-enterprise-migration.yml
new file mode 100644
index 0000000000..48c1b97cc9
--- /dev/null
+++ b/translations/ja-JP/data/features/docker-ghcr-enterprise-migration.yml
@@ -0,0 +1,4 @@
+#Reference: #7360
+#Documentation for migration from Docker registry to Container registry for enterprise products
+versions:
+  ghes: '>= 3.6'
diff --git a/translations/ja-JP/data/features/ghas-enablement-webhook.yml b/translations/ja-JP/data/features/ghas-enablement-webhook.yml
index cbb4509714..83f8a995bc 100644
--- a/translations/ja-JP/data/features/ghas-enablement-webhook.yml
+++ b/translations/ja-JP/data/features/ghas-enablement-webhook.yml
@@ -2,5 +2,5 @@
 #docs-content 7314. GHAS enablement webhook
 versions:
   ghec: '*'
-  ghes: '>3.6'
+  ghes: '>= 3.6'
   ghae: 'issue-7314'
diff --git a/translations/ja-JP/data/features/motion-management.yml b/translations/ja-JP/data/features/motion-management.yml
new file mode 100644
index 0000000000..573307aac2
--- /dev/null
+++ b/translations/ja-JP/data/features/motion-management.yml
@@ -0,0 +1,7 @@
+#Issue 6523
+#Support for customizing the automatic playback of animated images in the web interface
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6523'
diff --git a/translations/ja-JP/data/features/pause-audit-log-stream.yml b/translations/ja-JP/data/features/pause-audit-log-stream.yml
new file mode 100644
index 0000000000..59bcda81d5
--- /dev/null
+++ b/translations/ja-JP/data/features/pause-audit-log-stream.yml
@@ -0,0 +1,4 @@
+#Reference #4640
+#Documentation for pausing an audit log stream
+versions:
+  ghec: '*'
diff --git a/translations/ja-JP/data/features/require-tls-for-smtp.yml b/translations/ja-JP/data/features/require-tls-for-smtp.yml
new file mode 100644
index 0000000000..dd1f0d2c78
--- /dev/null
+++ b/translations/ja-JP/data/features/require-tls-for-smtp.yml
@@ -0,0 +1,4 @@
+#Reference 7394
+#Documentation for the option to enforce TLS encryption for incoming SMTP connections
+versions:
+  ghes: '>=3.6'
diff --git a/translations/ja-JP/data/features/security-advisories-ghes-ghae.yml b/translations/ja-JP/data/features/security-advisories-ghes-ghae.yml
new file mode 100644
index 0000000000..c4d8f488a5
--- /dev/null
+++ b/translations/ja-JP/data/features/security-advisories-ghes-ghae.yml
@@ -0,0 +1,4 @@
+#Reference: Issue #6982 Community Contributions to Security Advisories - Enterprise 3.6
+versions:
+  ghes: '>=3.6'
+  ghae: 'issue-6982'
diff --git a/translations/ja-JP/data/glossaries/internal.yml b/translations/ja-JP/data/glossaries/internal.yml
index f3d1b6cc70..9ea579ed43 100644
--- a/translations/ja-JP/data/glossaries/internal.yml
+++ b/translations/ja-JP/data/glossaries/internal.yml
@@ -665,7 +665,7 @@
   description: >-
     パスワードの代わりに使用できます。トークンには、個人アクセストークン、OAuth トークン、API トークンがあります。
 - 
-  term: topoJSON
+  term: TopoJSON
   description: GeoJSON の機能拡張版。トポロジをエンコードします。
 - 
   term: TOTPアプリケーション
diff --git a/translations/ja-JP/data/graphql/ghes-3.6/graphql_previews.enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.6/graphql_previews.enterprise.yml
new file mode 100644
index 0000000000..a9f2bdc09d
--- /dev/null
+++ b/translations/ja-JP/data/graphql/ghes-3.6/graphql_previews.enterprise.yml
@@ -0,0 +1,123 @@
+- 
+  title: パッケージのバージョン削除へのアクセス
+  description: >-
+    このプレビューは、プライベートパッケージバージョンの削除を有効化する、DeletePackageVersionのミューテーションのサポートを追加します。
+  toggled_by: ':package-deletes-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.deletePackageVersion
+  owning_teams:
+    - '@github/pe-package-registry'
+- 
+  title: デプロイメント
+  description: >-
+    このプレビューは、デプロイメントのミューテーションと新しいデプロイメントの機能を追加します。
+  toggled_by: ':flash-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - DeploymentStatus.environment
+    - Mutation.createDeploymentStatus
+    - CreateDeploymentStatusInput
+    - CreateDeploymentStatusPayload
+    - Mutation.createDeployment
+    - CreateDeploymentInput
+    - CreateDeploymentPayload
+  owning_teams:
+    - '@github/c2c-actions-service'
+- 
+  title: >-
+    >- MergeInfoPreview - Pull Requestのマージ状態に関する詳細な情報。
+  description: >-
+    このプレビューは、プルリクエストのマージ状態に関する詳細な情報を提供するフィールドへのアクセスのサポートを追加します。
+  toggled_by: ':merge-info-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - PullRequest.canBeRebased
+    - PullRequest.mergeStateStatus
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: UpdateRefsPreview - 1回の操作で複数の参照を更新します。
+  description: このプレビューは、1回の操作による複数の参照の更新のサポートを追加します。
+  toggled_by: ':update-refs-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateRefs
+    - GitRefname
+    - RefUpdate
+    - UpdateRefsInput
+    - UpdateRefsPayload
+  owning_teams:
+    - '@github/reponauts'
+- 
+  title: プロジェクトイベントの詳細
+  description: >-
+    このプレビューは、プロジェクト関連のIssueイベントに対し、プロジェクト、プロジェクトカード、プロジェクト列の詳細を追加します。
+  toggled_by: ':starfox-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - AddedToProjectEvent.project
+    - AddedToProjectEvent.projectCard
+    - AddedToProjectEvent.projectColumnName
+    - ConvertedNoteToIssueEvent.project
+    - ConvertedNoteToIssueEvent.projectCard
+    - ConvertedNoteToIssueEvent.projectColumnName
+    - MovedColumnsInProjectEvent.project
+    - MovedColumnsInProjectEvent.projectCard
+    - MovedColumnsInProjectEvent.projectColumnName
+    - MovedColumnsInProjectEvent.previousProjectColumnName
+    - RemovedFromProjectEvent.project
+    - RemovedFromProjectEvent.projectColumnName
+  owning_teams:
+    - '@github/github-projects'
+- 
+  title: ラベルのプレビュー
+  description: >-
+    このプレビューは、ラベルの追加、更新、作成、削除のサポートを追加します。
+  toggled_by: ':bane-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createLabel
+    - CreateLabelPayload
+    - CreateLabelInput
+    - Mutation.deleteLabel
+    - DeleteLabelPayload
+    - DeleteLabelInput
+    - Mutation.updateLabel
+    - UpdateLabelPayload
+    - UpdateLabelInput
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: プロジェクトのインポート
+  description: このプレビューは、プロジェクトのインポートのサポートを追加します。
+  toggled_by: ':slothette-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.importProject
+  owning_teams:
+    - '@github/pe-issues-projects'
+- 
+  title: Teamレビューの割り当てプレビュー
+  description: >-
+    このプレビューは、Teamレビューの割り当て設定の更新サポートを追加します
+  toggled_by: ':stone-crop-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateTeamReviewAssignment
+    - UpdateTeamReviewAssignmentInput
+    - TeamReviewAssignmentAlgorithm
+    - Team.reviewRequestDelegationEnabled
+    - Team.reviewRequestDelegationAlgorithm
+    - Team.reviewRequestDelegationMemberCount
+    - Team.reviewRequestDelegationNotifyTeam
+  owning_teams:
+    - '@github/pe-pull-requests'
diff --git a/translations/ja-JP/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml
new file mode 100644
index 0000000000..5485c04839
--- /dev/null
+++ b/translations/ja-JP/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml
@@ -0,0 +1,86 @@
+---
+upcoming_changes:
+  - 
+    location: LegacyMigration.uploadUrlTemplate
+    description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。'
+    reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。'
+    date: '2019-04-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: tambling
+  - 
+    location: AssignedEvent.user
+    description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。'
+    reason: アサインされた人を、マネキンにできるようになりました。
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: tambling
+  - 
+    location: UnassignedEvent.user
+    description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。'
+    reason: アサインされた人を、マネキンにできるようになりました。
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: tambling
+  - 
+    location: Issue.timeline
+    description: '`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。'
+    reason: '`timeline`は削除されます。'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: mikesea
+  - 
+    location: PullRequest.timeline
+    description: '`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。'
+    reason: '`timeline`は削除されます。'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: mikesea
+  - 
+    location: MergeStateStatus.DRAFT
+    description: '`DRAFT`は削除されます。代わりにPullRequest.isDraftを使ってください。'
+    reason: DRAFTの状態はこのenumから削除されるので、代わりに`isDraft`を使わなければなりません。
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: nplasterer
+  - 
+    location: PackageType.DOCKER
+    description: '`DOCKER`は削除されます。'
+    reason: DOCKERは、Packages REST APIでのみ使われるように移行されるので、このenumから削除されます。
+    date: '2021-06-21'
+    criticality: 破壊的
+    owner: reybard
+  - 
+    location: ReactionGroup.users
+    description: '`users`は削除されます。代わりに`reactors`フィールドを使ってください。'
+    reason: リアクターは、マネキン、ボット、Organizationになることができます。
+    date: '2021-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: synthead
+  - 
+    location: Repository.defaultMergeQueue
+    description: '`defaultMergeQueue`は削除されます。代わりに`Repository.mergeQueue`を使用してください。'
+    reason: '`defaultMergeQueue`は削除されます。'
+    date: '2022-04-01'
+    criticality: 破壊的
+    owner: colinshum
+  - 
+    location: AddPullRequestToMergeQueueInput.branch
+    description: '`branch`は削除されます。'
+    reason: PRsはベースブランチのマージキューに追加されます。引数`branch`はno-opになりました。
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: jhunschejones
+  - 
+    location: Enterprise.userAccounts
+    description: '`userAccounts`は削除されます。代わりに`Enterprise.members`フィールドを使用してください。'
+    reason: '`Enterprise.userAccounts`フィールドは削除されています。'
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: jdennes
+  - 
+    location: RemovePullRequestFromMergeQueueInput.branch
+    description: '`branch`は削除されます。'
+    reason: PRはベースブランチのマージキューから削除され、引数`branch`はno-opになりました。
+    date: '2022-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: jhunschejones
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/16.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/16.yml
new file mode 100644
index 0000000000..fac1c2578d
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/16.yml
@@ -0,0 +1,17 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**中**: サーバーサイドリクエストフォージェリ（SSRF）が、任意のデータをMemcachedをインジェクションすることによってSubversion（SVN）ブリッジにリモートコードを実行させうる攻撃を防ぎます。"
+    - Grafanaをバージョン7.5.17にアップデートします。このバージョンは [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9)及び[CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g)を含む様々なセキュリティ脆弱性に対処しています。
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - 成果物のzipアーカイブ中のファイルが、unzipツールを使って展開されたときに000の権限を持つ問題を修正しました。GitHub.comでの動作と同じように、それらのファイルの権限には644が設定されるようになりました。
+    - collectdデーモンが過剰にメモリを消費することがありました。
+    - ローテーとされたログファイルのバックアップが蓄積され、過剰にストレージを消費することがありました。
+    - 新しい機能リリースへのアップグレードとそれに続く設定の実行後、Elasticsearchがインデックスの再構築の間に過剰な例外を記録することがありました。
+    - 保護されたブランチが1つ以上の承認レビューを要求する場合に、Pull Requestが必要な承認レビュー数よりも少ないレビュー数でマージできてしまうことがありました。
+    - LDAP認証を使用しているインスタンスで、sudoモードに対する認証プロンプトにおいてユーザ名とパスワードに対するテキストフィールドがどちらも見えている場合に、誤ってカーソルがデフォルトでパスワードフィールドに置かれてしまいました。
+  changes:
+    - '`ghe-set-password`コマンドラインユーティリティは、インスタンスがリカバリモードで起動されているときに自動的に必要なサービスを起動します。'
+    - バックグラウンドプロセスの`aqueduct`のメトリクスは、転送してManagement Consoleで表示するためにCollectdに収集されます。
+    - データベースの移行及び設定の実行ログ`/data/user/common/ghe-config.log`の場所は、進行中の移行の詳細を示すページに表示されるようになりました。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/11.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/11.yml
new file mode 100644
index 0000000000..0b34fa85fa
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/11.yml
@@ -0,0 +1,18 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**中**: サーバーサイドリクエストフォージェリ（SSRF）が、任意のデータをMemcachedをインジェクションすることによってSubversion（SVN）ブリッジにリモートコードを実行させうる攻撃を防ぎます。"
+    - "**中**: 攻撃者が、GitHub Enterprise ServerのWebインターフェース内のドロップダウンUI要素のクロスサイトスクリプティング（XSS）脆弱性を悪用することによってJavascriptのコードを実行することを防ぎます。"
+    - Grafanaをバージョン7.5.17にアップデートします。このバージョンは [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9)及び[CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g)を含む様々なセキュリティ脆弱性に対処しています。
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - 成果物のzipアーカイブ中のファイルが、unzipツールを使って展開されたときに000の権限を持つ問題を修正しました。GitHub.comでの動作と同じように、それらのファイルの権限には644が設定されるようになりました。
+    - collectdデーモンが過剰にメモリを消費することがありました。
+    - ローテーとされたログファイルのバックアップが蓄積され、過剰にストレージを消費することがありました。
+    - 新しい機能リリースへのアップグレードとそれに続く設定の実行後、Elasticsearchがインデックスの再構築の間に過剰な例外を記録することがありました。
+    - 保護されたブランチが1つ以上の承認レビューを要求する場合に、Pull Requestが必要な承認レビュー数よりも少ないレビュー数でマージできてしまうことがありました。
+    - LDAP認証を使用しているインスタンスで、sudoモードに対する認証プロンプトにおいてユーザ名とパスワードに対するテキストフィールドがどちらも見えている場合に、誤ってカーソルがデフォルトでパスワードフィールドに置かれてしまいました。
+  changes:
+    - '`ghe-set-password`コマンドラインユーティリティは、インスタンスがリカバリモードで起動されているときに自動的に必要なサービスを起動します。'
+    - バックグラウンドプロセスの`aqueduct`のメトリクスは、転送してManagement Consoleで表示するためにCollectdに収集されます。
+    - データベースの移行及び設定の実行ログ`/data/user/common/ghe-config.log`の場所は、進行中の移行の詳細を示すページに表示されるようになりました。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml
index 69416e0428..dece67887a 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml
@@ -28,7 +28,7 @@ sections:
     - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
     - |
       セルフホストランナーを--ephemeral`パラメータ付きで複数レベル（たとえばEnterpriseとOrganizationというように）に登録したあと、ランナーがアイドル状態で停止し、再登録が必要になることがあります。[更新: 2022年6月17日]
-    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
+    - '{% data variables.product.prodname_ghe_server %} 3.4にアップグレードしたあと、リリースがリポジトリから失われたように見えることがあります。これは、必要なElasticsearchのインデックスの移行が成功終了していない場合に起こります。'
   deprecations:
     - 
       heading: GitHub Enterprise Server 3.0の非推奨化
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml
index 3ea8c95caa..eec8741756 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml
@@ -37,4 +37,4 @@ sections:
     - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
     - |
       セルフホストランナーを--ephemeral`パラメータ付きで複数レベル（たとえばEnterpriseとOrganizationというように）に登録したあと、ランナーがアイドル状態で停止し、再登録が必要になることがあります。[更新: 2022年6月17日]
-    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4 releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
+    - '{% data variables.product.prodname_ghe_server %} 3.4にアップグレードしたあと、リリースがリポジトリから失われたように見えることがあります。これは、必要なElasticsearchのインデックスの移行が成功終了していない場合に起こります。'
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/5.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/5.yml
index f30e685273..a8ceb142f4 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/5.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/5.yml
@@ -32,4 +32,4 @@ sections:
       この問題を回避するためには、以下の2つの方法のいずれかを取ることができます。
       - `WantAssertionsEncrypted`属性なしのSAMLメタデータの静的なコピーをアップロードして、IdPを再設定する。
       - SAMLメタデータをコピーし、`WantAssertionsEncrypted`を削除し、それをWebサーバーでホストして、そのURLを指してIdPを再設定する。
-    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
+    - '{% data variables.product.prodname_ghe_server %} 3.4にアップグレードしたあと、リリースがリポジトリから失われたように見えることがあります。これは、必要なElasticsearchのインデックスの移行が成功終了していない場合に起こります。'
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/6.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/6.yml
new file mode 100644
index 0000000000..7f7a43d706
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/6.yml
@@ -0,0 +1,20 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**中**: サーバーサイドリクエストフォージェリ（SSRF）が、任意のデータをMemcachedをインジェクションすることによってSubversion（SVN）ブリッジにリモートコードを実行させうる攻撃を防ぎます。"
+    - "**中**: 攻撃者が、GitHub Enterprise ServerのWebインターフェース内のドロップダウンUI要素のクロスサイトスクリプティング（XSS）脆弱性を悪用することによってJavascriptのコードを実行することを防ぎます。"
+    - Grafanaをバージョン7.5.17にアップデートします。このバージョンは [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9)及び[CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g)を含む様々なセキュリティ脆弱性に対処しています。
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - collectdデーモンが過剰にメモリを消費することがありました。
+    - ローテーとされたログファイルのバックアップが蓄積され、過剰にストレージを消費することがありました。
+    - 新しい機能リリースへのアップグレードとそれに続く設定の実行後、Elasticsearchがインデックスの再構築の間に過剰な例外を記録することがありました。
+    - 保護されたブランチが1つ以上の承認レビューを要求する場合に、Pull Requestが必要な承認レビュー数よりも少ないレビュー数でマージできてしまうことがありました。
+    - LDAP認証を使用しているインスタンスで、sudoモードに対する認証プロンプトにおいてユーザ名とパスワードに対するテキストフィールドがどちらも見えている場合に、誤ってカーソルがデフォルトでパスワードフィールドに置かれてしまいました。
+    - スケジュールされたGitHub Actionsワークフローが無効化されることがありました。
+    - 'Billing APIの"[OrganizationのGitHub Advanced Securityのアクティブなコミッターの取得](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)"エンドポイントは、ページネーションに関する情報を提供するために`Link`ヘッダを返すようになりました。'
+    - 'Billing APIの"[OrganizationのGitHub Advanced Securityのアクティブなコミッターの取得](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)"エンドポイントは、正しいコミッターの総数を返すようになりました。'
+  changes:
+    - '`ghe-set-password`コマンドラインユーティリティは、インスタンスがリカバリモードで起動されているときに自動的に必要なサービスを起動します。'
+    - バックグラウンドプロセスの`aqueduct`のメトリクスは、転送してManagement Consoleで表示するためにCollectdに収集されます。
+    - データベースの移行及び設定の実行ログ`/data/user/common/ghe-config.log`の場所は、進行中の移行の詳細を示すページに表示されるようになりました。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/3.yml
new file mode 100644
index 0000000000..325d553e3c
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/3.yml
@@ -0,0 +1,22 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**中**: サーバーサイドリクエストフォージェリ（SSRF）が、任意のデータをMemcachedをインジェクションすることによってSubversion（SVN）ブリッジにリモートコードを実行させうる攻撃を防ぎます。"
+    - "**中**: 攻撃者が、GitHub Enterprise ServerのWebインターフェース内のドロップダウンUI要素のクロスサイトスクリプティング（XSS）脆弱性を悪用することによってJavascriptのコードを実行することを防ぎます。"
+    - Grafanaをバージョン7.5.17にアップデートします。このバージョンは [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9)及び[CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g)を含む様々なセキュリティ脆弱性に対処しています。
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - collectdデーモンが過剰にメモリを消費することがありました。
+    - ローテーとされたログファイルのバックアップが蓄積され、過剰にストレージを消費することがありました。
+    - 新しい機能リリースへのアップグレードとそれに続く設定の実行後、Elasticsearchがインデックスの再構築の間に過剰な例外を記録することがありました。
+    - 保護されたブランチが1つ以上の承認レビューを要求する場合に、Pull Requestが必要な承認レビュー数よりも少ないレビュー数でマージできてしまうことがありました。
+    - GitHub Enterprise Importerは、リポジトリ内のプロジェクトの設定を正しく移行しませんでした。
+    - LDAP認証を使用しているインスタンスで、sudoモードに対する認証プロンプトにおいてユーザ名とパスワードに対するテキストフィールドがどちらも見えている場合に、誤ってカーソルがデフォルトでパスワードフィールドに置かれてしまいました。
+    - サイトアドミンのダッシュボードに、休眠ユーザをリストするレポートをエクスポートするオプションが誤って含まれていました。
+    - 'Billing APIの"[OrganizationのGitHub Advanced Securityのアクティブなコミッターの取得](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)"エンドポイントは、ページネーションに関する情報を提供するために`Link`ヘッダを返すようになりました。'
+    - 'Billing APIの"[OrganizationのGitHub Advanced Securityのアクティブなコミッターの取得](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)"エンドポイントは、正しいコミッターの総数を返すようになりました。'
+    - Organizationの設定のサイドバーで、**Archive**ナビゲーションアイテムが子を含みませんでした。
+  changes:
+    - '`ghe-set-password`コマンドラインユーティリティは、インスタンスがリカバリモードで起動されているときに自動的に必要なサービスを起動します。'
+    - バックグラウンドプロセスの`aqueduct`のメトリクスは、転送してManagement Consoleで表示するためにCollectdに収集されます。
+    - データベースの移行及び設定の実行ログ`/data/user/common/ghe-config.log`の場所は、進行中の移行の詳細を示すページに表示されるようになりました。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml
new file mode 100644
index 0000000000..7beaf78a0f
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml
@@ -0,0 +1,216 @@
+date: '2022-07-26'
+release_candidate: true
+deprecated: false
+intro: |
+  {% note %}
+
+  **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend that you only run release candidates in a test environment.
+
+  {% endnote %}
+
+  For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+sections:
+  features:
+    - 
+      heading: Infrastructure
+      notes:
+        - |
+          Repository caching is generally available. Repository caching increases Git read performance for distributed developers, providing the data locality and convenience of geo-replication without impact on push workflows. With the general availability release, GitHub Enterprise Server caches both Git and Git LFS data. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+    - 
+      heading: Instance security
+      notes:
+        - |
+          GitHub has changed the supported algorithms and hash functions for all SSH connections to GitHub Enterprise Server, disabled the unencrypted and unauthenticated Git protocol, and optionally allowed the advertisement of an Ed25519 host key. For more information, see the [GitHub Blog](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server/) and the following articles.
+
+          - "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)"
+          - "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)"
+          - "[Configuring host keys for your instance](/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance)"
+        - |
+          You can require TLS encryption for incoming SMTP connections to your instance. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)."
+    - 
+      heading: 監査ログ
+      notes:
+        - |
+          You can stream audit log and Git events for your instance to Amazon S3, Azure Blob Storage, Azure Event Hubs, Google Cloud Storage, or Splunk. Audit log streaming is in public beta and subject to change. For more information, see "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
+    - 
+      heading: GitHub Connect
+      notes:
+        - |
+          Server Statistics is now generally available. Server Statistics collects aggregate usage data from your GitHub Enterprise Server instance, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from GitHub Enterprise Server. For more information, see "[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+    - 
+      heading: Administrator experience
+      notes:
+        - |
+          Enterprise owners can join organizations on the instance as a member or owner from the enterprise account's **Organizations** page. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."
+        - |
+          Enterprise owners can allow users to dismiss the configured global announcement banner. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
+    - 
+      heading: GitHub Advanced Security
+      notes:
+        - |
+          Users on an instance with a GitHub Advanced Security license can opt to receive a webhook event that triggers when an organization owner or repository administrator enables or disables a code security or analysis feature. For more information, see the following documentation.
+
+          - "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#security_and_analysis)" in the webhook documentation
+          - "[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)"
+          - "[Managing security and analysis features for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)"
+        - |
+          Users on an instance with a GitHub Advanced Security license can optionally add a comment when dismissing a code scanning alert in the web UI or via the REST API. Dismissal comments appear in the event timeline. Users can also add or retrieve a dismissal comment via the REST API. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests#dismissing-an-alert-on-your-pull-request)" and "[Code Scanning](/rest/code-scanning#update-a-code-scanning-alert)" in the REST API documentation.
+        - |
+          On instances with a GitHub Advanced Security license, secret scanning prevents the leak of secrets in the web editor. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-web-ui)."
+        - |
+          Enterprise owners and users on an instance with a GitHub Advanced Security license can view secret scanning alerts and bypasses of secret scanning's push protection in the enterprise and organization audit logs, and via the REST API. For more information, see the following documentation.
+
+          - "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)"
+          - "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#secret_scanning_push_protection-category-actions)"
+          - "[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#secret_scanning_push_protection-category-actions)"
+          - "[Secret Scanning](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)" in the REST API documentation
+        - |
+          Enterprise owners on an instance with a GitHub Advanced Security license can perform dry runs of custom secret scanning patterns for the enterprise, and all users can perform dry runs when editing a pattern. Dry runs allow you to understand a pattern's impact across the entire instance and hone the pattern before publication and generation of alerts. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+        - |
+          Users on an instance with a GitHub Advanced Security license can use `sort` and `direction` parameters in the REST API when retrieving secret scanning alerts, and sort based on the alert’s `created` or `updated` fields. The new parameters are available for the entire instance, or for individual organizations or repositories. For more information, see the following documentation.
+
+          - "[List secret scanning alerts for an enterprise](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)"
+          - "[List secret scanning alerts for an organization](/rest/secret-scanning#list-secret-scanning-alerts-for-an-organization)"
+          - "[List secret scanning alerts for a repository](/rest/secret-scanning#list-secret-scanning-alerts-for-a-repository)"
+          - "[Secret Scanning](/rest/secret-scanning)" in the REST API documentation
+        - |
+          The contents of the `github/codeql-go` repository have moved to the `github/codeql` repository, to live alongside similar libraries for all other programming languages supported by CodeQL. The open-source CodeQL queries, libraries, and extractor for analyzing codebases written in the Go programming language with GitHub's CodeQL code analysis tools can now be found in the new location. For more information, including guidance on migrating your existing workflows, see [github/codeql-go#741](https://github.com/github/codeql-go/issues/741).
+    - 
+      heading: Dependabot
+      notes:
+        - |
+          Enterprise owners on instances with a GitHub Advanced Security license can see an overview of Dependabot alerts for the entire instance, including a repository-centric view of application security risks, and an alert-centric view of all secret scanning and Dependabot alerts. The views are in beta and subject to change, and alert-centric views for code scanning are planned for a future release of GitHub Enterprise Server. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview#viewing-the-security-overview-for-an-enterprise)."
+        - |
+          Dependabot alerts show users if repository code calls vulnerable functions. Individual alerts display a "vulnerable call" label and code snippet, and users can filter search by `has:vulnerable-calls`. Vulnerable functions are curated during publication to the [GitHub Advisory Database](https://github.com/advisories). New incoming Python advisories will be supported, and GitHub is backfilling known vulnerable functions for historical Python advisories. After beta testing with Python, GitHub will add support for other ecosystems. For more information, see "[Viewing and updating Dependabot alerts](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)."
+        - |
+          Users can select multiple Dependabot alerts, then dismiss or reopen or dismiss the alerts. For example, from the **Closed alerts** tab, you can select multiple alerts that have been previously dismissed, and then reopen them all at once. For more information, see "[About Dependabot alerts](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."
+        - |
+          Dependabot updates `@types` dependencies alongside corresponding packages in TypeScript projects. Before this change, users would see separate pull requests for a package and the corresponding `@types` package. This feature is automatically enabled for repositories containing `@types` packages in the project's `devDependencies` within the _package.json_ file. You can disable this behavior by setting the [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore) field in your `dependabot.yml` file to `@types/*`. For more information, see "[About Dependabot version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)" and "[Configuration options for the _dependabot.yml_ file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file)."
+    - 
+      heading: コードセキュリティ
+      notes:
+        - |
+          GitHub Actions can enforce dependency reviews on users' pull requests by scanning for dependencies, and will warn users about associated security vulnerabilities. The `dependency-review-action` action is supported by a new API endpoint that diffs the dependencies between any two revisions. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)."
+        - |
+          The dependency graph detects _Cargo.toml_ and _Cargo.lock_ files for Rust. These files will be displayed in the **Dependency graph** section of the **Insights** tab. Users will receive Dependabot alerts and updates for vulnerabilities associated with their Rust dependencies. Package metadata, including mapping packages to repositories, will be added at a later date. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
+        - |
+          If GitHub Connect is enabled for your instance, users can contribute an improvement to a security advisory in the [GitHub Advisory Database](https://github.com/advisories). To contribute, click **Suggest improvements for this vulnerability** while viewing an advisory's details. For more information, see the following articles.
+
+          - "[Managing GitHub Connect](/admin/configuration/configuring-github-connect/managing-github-connect)"
+          - "[Browsing security vulnerabilities in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+          - "[About GitHub Security Advisories for repositories](/enterprise-cloud@latest/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)" in the GitHub Enterprise Cloud documentation
+          - "[Editing security advisories in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+    - 
+      heading: GitHub Actions
+      notes:
+        - |
+          Within a workflow that calls a reusable workflow, users can pass the secrets to the reusable workflow with `secrets: inherit`. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow)."
+        - |
+          When using GitHub Actions, to reduce the risk of merging a change that was not reviewed by another person into a protected branch, enterprise owners and repository administrators can prevent Actions from creating pull requests. Organization owners could previously enable this restriction. For more information, see the following articles.
+
+          - "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)"
+          - "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-creating-or-approving-pull-requests)"
+          - "[Managing GitHub 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)"
+        - |
+          Users can write a single workflow triggered by `workflow_dispatch` and `workflow_call`, and use the `inputs` context to access input values. Previously, `workflow_dispatch` inputs were in the event payload, which increased difficulty for workflow authors who wanted to write one workflow that was both reusable and manually triggered. For workflows triggered by `workflow_dispatch`, inputs are still available in the `github.event.inputs` context to maintain compatibility.  For more information, see "[Contexts](/actions/learn-github-actions/contexts#inputs-context)."
+        - |
+          To summarize the result of a job, users can generate Markdown and publish the contents as a job summary. For example, after running tests with GitHub Actions, a summary can provide an overview of passed, failed, or skipped tests, potentially reducing the need to review the full log output. For more information, see "[Workflow commands for GitHub Actions](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)."
+        - |
+          To more easily diagnose job execution failures during a workflow re-run, users can enable debug logging, which outputs information about a job's execution and environment. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)" and "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
+        - |
+          If you manage self-hosted runners for GitHub Actions, you can ensure a consistent state on the runner itself before and after a workflow run by defining scripts to execute. By using scripts, you no longer need to require that users manually incorporate these steps into workflows. Pre- and post-job scripts are in beta and subject to change. For more information, see "[Running scripts before or after a job](/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job)."
+    - 
+      heading: GitHub Packages
+      notes:
+        - |
+          Enterprise owners can migrate container images from the GitHub Docker registry to the GitHub Container registry. The Container registry provides the following benefits.
+
+          - Improves the sharing of containers within an organization
+          - Allows the application of granular access permissions
+          - Permits the anonymous sharing of public container images
+          - Implements OCI standards for hosting Docker images
+
+          The Container registry is in beta and subject to change. For more information, see "[Migrating your enterprise to the Container registry from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)."
+    - 
+      heading: Community experience
+      notes:
+        - |
+          GitHub Discussions is available for GitHub Enterprise Server. GitHub Discussions provides a central gathering space to ask questions, share ideas, and build connections. For more information, see "[GitHub Discussions](/discussions)."
+        - |
+          Enterprise owners can configure a policy to control whether people's usernames or full names are displayed within internal or public repositories. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-display-of-member-names-in-your-repositories)."
+    - 
+      heading: Organization
+      notes:
+        - |
+          Users can create member-only READMEs for an organization. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."
+        - |
+          Organization owners can pin a repository to an organization's profile directly from the repository via the new **Pin repository** dropdown. Pinned public repositories appear to all users of your instance, while public, private, and internal repositories are only visible to organization members.
+    - 
+      heading: リポジトリ
+      notes:
+        - |
+          While creating a fork, users can customize the fork's name. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
+        - |
+          Users can block creation of branches that match a configured name pattern with the **Restrict pushes that create matching branches** branch protection rule. For example, if a repository's default branch changes from `master` to `main`, a repository administrator can prevent any subsequent creation or push of the `master` branch. For more information, see
+          "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#restrict-who-can-push-to-matching-branches)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)."
+        - |
+          Users can create a branch directly from a repository's **Branches** page by clicking the **New branch**. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+        - |
+          Users can delete a branch that's associated with an open pull request. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+        - |
+          Repositories with multiple licenses display all of the licenses in the "About" sidebar on the {% octicon "code" aria-label="The code icon" %} **Code** tab. For more information, see "[Licensing a repository](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository)."
+        - When a user renames or moves a file to a new directory, if at least half of the file's contents are identical, the commit history indicates that the file was renamed, similar to `git log --follow`. For more information, see the [GitHub Blog](https://github.blog/changelog/2022-06-06-view-commit-history-across-file-renames-and-moves/).
+        - |
+          Users can require a successful deployment of a branch before anyone can merge the pull request associated with the branch. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-deployments-to-succeed-before-merging)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+        - |
+          Enterprise owners can prevent organization owners from inviting collaborators to repositories on the instance. For more information, see "[Enforcing a policy for inviting collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)."
+        - |
+          Users can grant exceptions to GitHub Apps for any branch protection rule that supports exceptions. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+    - 
+      heading: コミット
+      notes:
+        - |
+          For public GPG signing keys that are expired or revoked, GitHub Enterprise Server verifies Git commit signatures and show commits as verified if the user made the commit while the key was still valid. Users can also upload expired or revoked GPG keys. For more information, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
+        - |
+          To affirm that a commit complies with the rules and licensing governing a repository, organization owners and repository administrators can now require developers to sign off on commits made through the web interface. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)" and "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+    - 
+      heading: プルリクエスト
+      notes:
+        - |
+          Using the file tree located in the **Files changed** tab of a pull request, users can navigate modified files, understand the size and scope of changes, and focus reviews. The file tree appears if a pull request modifies at least two files, and the browser window is sufficiently wide. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" and "[Filtering files in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+        - |
+          Users can default to using pull requests titles as the commit message for all squash merges. For more information, see "[Configuring commit squashing for pull requests](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)."
+    - 
+      heading: リリース
+      notes:
+        - |
+          When viewing the details for a particular release, users can see the creation date for each release asset. For more information, see "[Viewing your repository's releases and tags](/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
+        - While creating a release with automatically generated release notes, users can see the tag identified as the previous release, then choose to select a different tag to specify as the previous release. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
+    - 
+      heading: Markdown
+      notes:
+        - |
+          Editing Markdown in the web interface has been improved.
+
+          - After a user selects text and pastes a URL, the selected text will become a Markdown link to the pasted URL.
+          - When a user pastes spreadsheet cells or HTML tables, the resulting text will render as a table.
+          - When a user copies text containing links, the pasted text will include the link as a Markdown link.
+
+          For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#links)."
+        - |
+          When editing a Markdown file in the web interface, clicking the **Preview** tab will automatically scroll to the place in the preview that you were editing. The scroll location is based on the position of your cursor before you clicked the **Preview** tab.
+  changes:
+    - Interactive elements in the web interface such as links and buttons show a visible outline when focused with a keyboard, to help users find the current position on a page. In addition, when focused, form fields have a higher contrast outline.
+    - If a user refreshes the page while creating a new issue or pull request, the assignees, reviewers, labels and projects will all be preserved.
+  known_issues:
+    - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。
+    - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
+    - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
+    - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
+    - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+    - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+    - In some cases, users cannot convert existing issues to discussions.
+    - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
diff --git a/translations/ja-JP/data/reusables/actions/supported-github-runners.md b/translations/ja-JP/data/reusables/actions/supported-github-runners.md
index fd3c94594d..68b601bbc8 100644
--- a/translations/ja-JP/data/reusables/actions/supported-github-runners.md
+++ b/translations/ja-JP/data/reusables/actions/supported-github-runners.md
@@ -84,7 +84,7 @@ macOS Catalina 10.15 <sup>[deprecated]</sup>
 <code>macos-10.15</code>
 </td>
 <td>
-Migrate to <code>macOS-11</code> or <code>macOS-12</code>. For more information, see <A href="https://github.blog/changelog/2022-07-20-github-actions-the-macos-10-15-actions-runner-image-is-being-deprecated-and-will-be-removed-by-8-30-22/">this GitHub blog post</A>.
+<code>macOS-11</code>もしくは<code>macOS-12</code>に移行してください。 詳しい情報については<A href="https://github.blog/changelog/2022-07-20-github-actions-the-macos-10-15-actions-runner-image-is-being-deprecated-and-will-be-removed-by-8-30-22/">GitHubブログのポスト</A>を参照してください。
 </td>
 </tr>
 </tbody>
diff --git a/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md b/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md
index 37446f2df5..acfc210be9 100644
--- a/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md
+++ b/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md
@@ -1,5 +1,5 @@
-{% note %}
+{% ifversion GH-advisory-db-supports-malware %}{% note %}
 
 **ノート:** マルウェアのアドバイザリは現在ベータであり、変更されることがあります。
 
-{% endnote %}
+{% endnote %}{% endif %}
diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md
index 4b3cdb42c8..48be014db5 100644
--- a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md
+++ b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md
@@ -5,7 +5,7 @@
 | `advisory_credit`   | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 {%- endif %}
 | `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts.
-{%- ifversion ghec %}
+{%- ifversion audit-log-streaming %}
 | `audit_log_streaming`  | Contains activities related to streaming audit logs for organizations in an enterprise account.
 {%- endif %}
 {%- ifversion fpt or ghec %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/alert-tracking-link.md b/translations/ja-JP/data/reusables/code-scanning/alert-tracking-link.md
index 25b7b94f3b..0400806e7e 100644
--- a/translations/ja-JP/data/reusables/code-scanning/alert-tracking-link.md
+++ b/translations/ja-JP/data/reusables/code-scanning/alert-tracking-link.md
@@ -1,2 +1,2 @@
 
-For more information about creating issues to track {% data variables.product.prodname_code_scanning %} alerts, see "[Tracking {% data variables.product.prodname_code_scanning %} alerts in issues using task lists](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)."
+{% data variables.product.prodname_code_scanning %}アラートを追跡するためのIssueの作成に関する詳しい情報については「[タスクリストを使用したIssue内の{% data variables.product.prodname_code_scanning %}アラートの追跡](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/code-scanning/beta-codeql-ml-queries.md b/translations/ja-JP/data/reusables/code-scanning/beta-codeql-ml-queries.md
index 57004ecc5c..00dc1d76b9 100644
--- a/translations/ja-JP/data/reusables/code-scanning/beta-codeql-ml-queries.md
+++ b/translations/ja-JP/data/reusables/code-scanning/beta-codeql-ml-queries.md
@@ -2,7 +2,7 @@
 
 {% note %}
 
-**Note:** Experimental alerts for {% data variables.product.prodname_code_scanning %} are created using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature is currently available as a beta release for JavaScript code and is subject to change.
+**ノート:**{% data variables.product.prodname_code_scanning %}の実験的アラートは、{% data variables.product.prodname_codeql %}アクションの実験的な技術を使って作成されます。 この機能は現在JavaScriptのコードに対してベータとして利用可能であり、変更されることがあります。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/data/reusables/code-scanning/beta-codeql-packs-cli.md b/translations/ja-JP/data/reusables/code-scanning/beta-codeql-packs-cli.md
index dff81e1499..d16f7fe5a5 100644
--- a/translations/ja-JP/data/reusables/code-scanning/beta-codeql-packs-cli.md
+++ b/translations/ja-JP/data/reusables/code-scanning/beta-codeql-packs-cli.md
@@ -2,7 +2,7 @@
 
 {% note %}
 
-**Note:** The {% data variables.product.prodname_codeql %} package management functionality, including {% data variables.product.prodname_codeql %} packs, is currently in beta and subject to change.
+**ノート:** {% data variables.product.prodname_codeql %}を含む{% data variables.product.prodname_codeql %}パッケージ管理の機能は、現在ベータであり、変更されることがあります。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/data/reusables/code-scanning/choose-alert-dismissal-reason.md b/translations/ja-JP/data/reusables/code-scanning/choose-alert-dismissal-reason.md
index 6ae84d6029..56af6cc51d 100644
--- a/translations/ja-JP/data/reusables/code-scanning/choose-alert-dismissal-reason.md
+++ b/translations/ja-JP/data/reusables/code-scanning/choose-alert-dismissal-reason.md
@@ -1,3 +1,3 @@
 クエリが将来の分析に含まれ続けるかに影響することがあるので、ドロップダウンメニューから適切な理由を選択することは重要です。
-{% ifversion comment-dismissed-code-scanning-alert %}Optionally, you can comment on a dismissal to record the context of an alert dismissal. The dismissal comment is added to the alert timeline and can be used as justification during auditing and reporting. You can retrieve or set a comment by using the code scanning REST API. The comment is contained in `dismissed_comment` for the `alerts/{alert_number}` endpoint. For more information, see "[Code Scanning](/rest/code-scanning#update-a-code-scanning-alert)."
+{% ifversion comment-dismissed-code-scanning-alert %}あるいは、アラートの却下に関するコンテキストを記録するために、却下の際にコメントすることができます。 却下のコメントはアラートのタイムラインに追加され、監査とレポートの際の正当性として利用できます。 コードスキャンニングのREST APIを使用して、コメントの取得や設定ができます。 コメントは、`alerts/{alert_number}`エンドポイントの`dismissed_comment`に含まれています。 詳しい情報については「[Code scanning](/rest/code-scanning#update-a-code-scanning-alert)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md b/translations/ja-JP/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md
index 33af00e09c..2bc7959ce5 100644
--- a/translations/ja-JP/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md
@@ -1 +1 @@
-{% data variables.product.prodname_codeql_cli %}をサードパーティのシステムに追加して、コードを分析するツールを呼び、SARIFの結果を{% data variables.product.product_name %}にアップロードしてください。 結果の{% data variables.product.prodname_code_scanning %}アラートは、{% data variables.product.product_name %}内で生成されたアラートとともに表示されます。 For more information, see "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
+{% data variables.product.prodname_codeql_cli %}をサードパーティのシステムに追加して、コードを分析するツールを呼び、SARIFの結果を{% data variables.product.product_name %}にアップロードしてください。 結果の{% data variables.product.prodname_code_scanning %}アラートは、{% data variables.product.product_name %}内で生成されたアラートとともに表示されます。 詳しい情報については「[CIシステムでのCodeQLコードスキャンニングについて](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md
index 5025b325d7..d2d013daa8 100644
--- a/translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md
@@ -9,9 +9,9 @@
 
 {% note %}
 
-**Note**: {% data variables.product.prodname_codeql %} analysis for Ruby is currently in beta. During the beta, analysis of Ruby will be less comprehensive than {% data variables.product.prodname_codeql %} analysis of other languages.
+**ノート**: Rubyの{% data variables.product.prodname_codeql %}分析は現在ベータです。 このベータの間、Rubyの分析は他の言語の{% data variables.product.prodname_codeql %}分析よりも包括的ではありません。
 
 {% endnote %}
 
-For more information, see the documentation on the {% data variables.product.prodname_codeql %} website: "[Supported languages and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/)."
+詳しい情報については{% data variables.product.prodname_codeql %} Webサイトのドキュメンテーション「[サポートされている言語とフレームワーク](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md
index 946b677788..fd7dd22c50 100644
--- a/translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md
@@ -1 +1 @@
-`cpp`, `csharp`, `go`, `java`, `javascript`,{% ifversion fpt or ghes > 3.3 or ghae-issue-5017 %} `python`, and `ruby`{% else %} and `python`{% endif %}
+`cpp`、`csharp`、`go`、`java`、`javascript`、{% ifversion fpt or ghes > 3.3 or ghae-issue-5017 %} `python`、`ruby`{% else %}、`python`{% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites-explanation.md b/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites-explanation.md
index 60edba44d6..e1e345fff2 100644
--- a/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites-explanation.md
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites-explanation.md
@@ -2,4 +2,4 @@
 
 {% data reusables.code-scanning.codeql-query-suites %}
 
-When you specify a query suite, the {% data variables.product.prodname_codeql %} analysis engine will run the default set of queries and any extra queries defined in the additional query suite. {% ifversion codeql-ml-queries %}The `security-extended` and `security-and-quality` query suites for JavaScript contain experimental queries. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% endif %}
+クエリスイートを指定した場合、{% data variables.product.prodname_codeql %}分析エンジンはクエリのデフォルトセットと、追加のクエリスイートで定義された追加のクエリを実行します。 {% ifversion codeql-ml-queries %}JavaScriptの`security-extended`及び`security-and-quality`は実験的なクエリを含みます。 詳しい情報については「[{% data variables.product.prodname_code_scanning %}アラートについて](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)」を参照してください。{% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/deprecation-codeql-runner.md b/translations/ja-JP/data/reusables/code-scanning/deprecation-codeql-runner.md
index 2ed52c32ff..84b1da296a 100644
--- a/translations/ja-JP/data/reusables/code-scanning/deprecation-codeql-runner.md
+++ b/translations/ja-JP/data/reusables/code-scanning/deprecation-codeql-runner.md
@@ -2,22 +2,22 @@
 
 {% ifversion fpt or ghec %}
 
-**Note:** The {% data variables.product.prodname_codeql_runner %} is deprecated. On {% data variables.product.product_name %}, the {% data variables.product.prodname_codeql_runner %} was supported until March 2022. You should upgrade to the latest version of [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases).
+**ノート:** {% data variables.product.prodname_codeql_runner %}は非推奨になりました。 {% data variables.product.product_name %}では、{% data variables.product.prodname_codeql_runner %}は2022年3月までサポートされていました。 最新バージョンの[{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases)にアップグレードしてください。
 
 {% elsif ghes > 3.3 %}
 
-**Note:** The {% data variables.product.prodname_codeql_runner %} has been deprecated and is not included in {% data variables.product.prodname_ghe_server %} 3.4. You should migrate to [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) version 2.7.6.
+**ノート:** {% data variables.product.prodname_codeql_runner %}は非推奨になっており、{% data variables.product.prodname_ghe_server %} 3.4には含まれていません。 [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) 2.7.6に移行してください。
 
 {% elsif ghes < 3.4 %}
 
-**Note:** The {% data variables.product.prodname_codeql_runner %} is being deprecated. On {% data variables.product.prodname_ghe_server %} 3.0 and greater, you can install [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) version 2.6.3 to replace {% data variables.product.prodname_codeql_runner %}.
+**ノート:** {% data variables.product.prodname_codeql_runner %}は非推奨になりました。 {% data variables.product.prodname_ghe_server %} 3.0移行では、[{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases)バージョン2.6.3をインストールして{% data variables.product.prodname_codeql_runner %}を置き換えることができます。
 
 {% elsif ghae %}
 
-**Note:** The {% data variables.product.prodname_codeql_runner %} has been deprecated. You should migrate to [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases).
+**ノート:** {% data variables.product.prodname_codeql_runner %}は非推奨になりました。 [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases)に移行してください。
 
 {% endif %}
 
-For more information, see [the CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). {% data variables.product.prodname_codeql_cli %}への移行に関する情報については「[CodeQLランナーからCodeQL CLIへの移行](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)」を参照してください。
+詳しい情報については[CodeQLランナーの非推奨化](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/)を参照してください。 {% data variables.product.prodname_codeql_cli %}への移行に関する情報については「[CodeQLランナーからCodeQL CLIへの移行](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)」を参照してください。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/enabling-options.md b/translations/ja-JP/data/reusables/code-scanning/enabling-options.md
index cddfdc8dc4..dec3cc7fa0 100644
--- a/translations/ja-JP/data/reusables/code-scanning/enabling-options.md
+++ b/translations/ja-JP/data/reusables/code-scanning/enabling-options.md
@@ -15,7 +15,7 @@
     </td>
     
     <td>
-      Using {% data variables.product.prodname_actions %} (see "<a href="/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Setting up {% data variables.product.prodname_code_scanning %} using actions</a>") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "<a href="/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system">About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system</a>").
+      {% data variables.product.prodname_actions %}の利用（「<a href="/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">アクションを使った{% data variables.product.prodname_code_scanning %}のセットアップ</a>」参照）もしくはサードパーティの継続的インテグレーション（CI）システムでの{% data variables.product.prodname_codeql %}分析の実行（「<a href="/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system">CIシステムでの{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}について</a>」参照）。
     </td>
   </tr>
   
@@ -25,7 +25,7 @@
     </td>
     
     <td>
-      Using {% data variables.product.prodname_actions %} (see "<a href="/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Setting up {% data variables.product.prodname_code_scanning %} using actions</a>") or generated externally and uploaded to {% data variables.product.product_name %} (see "<a href="/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github">Uploading a SARIF file to {% data variables.product.prodname_dotcom %}</a>").
+      {% data variables.product.prodname_actions %}の利用（「<a href="/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">アクションを使う{% data variables.product.prodname_code_scanning %}のセットアップ</a>」）あるいは外部で生成して{% data variables.product.product_name %}へアップロード（「<a href="/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github">{% data variables.product.prodname_dotcom %}へのSARIFファイルのアップロード</a>」）。
     </td>
   </tr>
 </table>
diff --git a/translations/ja-JP/data/reusables/code-scanning/false-positive-fix-codeql.md b/translations/ja-JP/data/reusables/code-scanning/false-positive-fix-codeql.md
index 73aa156fef..ea34cc759d 100644
--- a/translations/ja-JP/data/reusables/code-scanning/false-positive-fix-codeql.md
+++ b/translations/ja-JP/data/reusables/code-scanning/false-positive-fix-codeql.md
@@ -1 +1 @@
-If you dismiss a {% data variables.product.prodname_codeql %} alert as a false positive result, for example because the code uses a sanitization library that isn't supported, consider contributing to the {% data variables.product.prodname_codeql %} repository and improving the analysis. {% data variables.product.prodname_codeql %}に関する詳しい情報については「[{% data variables.product.prodname_codeql %}に貢献する](https://github.com/github/codeql/blob/main/CONTRIBUTING.md)」を参照してください。
+{% data variables.product.prodname_codeql %}のアラートを、たとえばコードがサポートされていないサニタイズのライブラリを使っているといった理由で偽陽性の結果として却下する場合、{% data variables.product.prodname_codeql %}リポジトリに貢献して分析を改善することを検討してください。 {% data variables.product.prodname_codeql %}に関する詳しい情報については「[{% data variables.product.prodname_codeql %}に貢献する](https://github.com/github/codeql/blob/main/CONTRIBUTING.md)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/code-scanning/filter-non-default-branches.md b/translations/ja-JP/data/reusables/code-scanning/filter-non-default-branches.md
index 6d8d85de0b..0abe36f5a2 100644
--- a/translations/ja-JP/data/reusables/code-scanning/filter-non-default-branches.md
+++ b/translations/ja-JP/data/reusables/code-scanning/filter-non-default-branches.md
@@ -1 +1 @@
-Please note that if you have filtered for alerts on a non-default branch, but the same alerts exist on the default branch, the alert page for any given alert will still only reflect the alert's status on the default branch, even if that status conflicts with the status on a non-default branch. For example, an alert that appears in the "Open" list in the summary of alerts for `branch-x` could show a status of "Fixed" on the alert page, if the alert is already fixed on the default branch. You can view the status of the alert for the branch you filtered on in the  **Affected branches** section on the right side of the alert page.
+デフォルトではないブランチ上のアラートをフィルタリングしたものの、同じアラートがデフォルトブランチにも存在している場合、どのアラートのアラートページも、デフォルトではないブランチ上のステータスとの差異があっても、デフォルトブランチ上のアラートのステータスだけが反映されることに注意してください。 たとえば、`branch-x`に対するアラートのサマリ中の"Open"リストに表示されるアラートは、そのアラートが既にデフォルトブランチで修復されているなら、そのアラートページでは"Fixed"というステータスで表示されます。 フィルタしたブランチに対するアラートのステータスは、アラートページの右側の**Affected branches（影響されたブランチ）**セクションで見ることができます。
diff --git a/translations/ja-JP/data/reusables/code-scanning/github-issues-integration.md b/translations/ja-JP/data/reusables/code-scanning/github-issues-integration.md
index 5cd2ea59ec..bb6c0b86f7 100644
--- a/translations/ja-JP/data/reusables/code-scanning/github-issues-integration.md
+++ b/translations/ja-JP/data/reusables/code-scanning/github-issues-integration.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_code_scanning_capc %} alerts integrate with task lists in {% data variables.product.prodname_github_issues %} to make it easy for you to prioritize and track alerts with all your development work. Issue に関する詳しい情報については「[Issue について](/issues/tracking-your-work-with-issues/about-issues)」を参照してください。
+{% data variables.product.prodname_code_scanning_capc %}アラートは、{% data variables.product.prodname_github_issues %}でタスクリストと統合されており、開発作業全体の中でアラートを優先順位付けして追跡しやすくします。 Issue に関する詳しい情報については「[Issue について](/issues/tracking-your-work-with-issues/about-issues)」を参照してください。
 
-To track a code scanning alert in an issue, add the URL for the alert as a task list item in the issue. For more information about task lists, see "[About tasks lists](/issues/tracking-your-work-with-issues/about-task-lists)."
+Issue内でCode scanningアラートを追跡するには、アラートのURLをタスクリストのアイテムとしてIssueに追加してください。 タスクリストに関する詳しい情報については「[タスクリストについて](/issues/tracking-your-work-with-issues/about-task-lists)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/code-scanning/licensing-note.md b/translations/ja-JP/data/reusables/code-scanning/licensing-note.md
index 71ac760b15..8a1df37865 100644
--- a/translations/ja-JP/data/reusables/code-scanning/licensing-note.md
+++ b/translations/ja-JP/data/reusables/code-scanning/licensing-note.md
@@ -1,8 +1,8 @@
 {% note %}
 
-**Note:** {% ifversion fpt %}
-The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories. The {% data variables.product.prodname_codeql_cli %} is also available in private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. 詳細については「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}の利用規約](https://securitylab.github.com/tools/codeql/license)」及び「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
-{%- elsif ghec %} The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. 詳細については「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}の利用規約](https://securitylab.github.com/tools/codeql/license)」及び「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
+**ノート:** {% ifversion fpt %}
+{% data variables.product.prodname_codeql_cli %}はパブリックリポジトリでは無料で使用できます。 {% data variables.product.prodname_codeql_cli %}は、{% data variables.product.prodname_ghe_cloud %}を使用し、{% data variables.product.prodname_GH_advanced_security %}のライセンスを持っているOrganizationが所有するプライベートリポジトリでも使用できます。 詳細については「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}の利用規約](https://securitylab.github.com/tools/codeql/license)」及び「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
+{%- elsif ghec %}{% data variables.product.prodname_codeql_cli %}は{% data variables.product.prodname_dotcom_the_website %}でメンテナンスされているパブリックリポジトリでは無料で使用でき、{% data variables.product.prodname_advanced_security %}ライセンスを持っているお客様が所有するプライベートリポジトリでも使用できます。 詳細については「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}の利用規約](https://securitylab.github.com/tools/codeql/license)」及び「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
 {%- elsif ghes or ghae %}{% data variables.product.prodname_codeql_cli %}は、{% data variables.product.prodname_advanced_security %}ライセンスを持つお客様にご利用いただけます。
 {% endif %}
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md b/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md
index 07f444ca8d..3f25bd67d1 100644
--- a/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md
+++ b/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md
@@ -1,20 +1,18 @@
-コードをスキャンするために{% data variables.product.prodname_codeql %}を使う場合、{% data variables.product.prodname_codeql %}分析エンジンはコードからデータベースを生成し、それに対してクエリを実行します。 {% data variables.product.prodname_codeql %}の分析はデフォルトのクエリセットを使いますが、デフォルトのクエリに加えてもっと多くのクエリを実行するよう指定することもできます。
+When you use {% data variables.product.prodname_codeql %} to scan code, the {% data variables.product.prodname_codeql %} analysis engine generates a database from the code and runs queries on it. {% data variables.product.prodname_codeql %} analysis uses a default set of queries, but you can specify more queries to run, in addition to the default queries.
 
 {% ifversion codeql-packs %}
-You can run extra queries if they are part of a
-{% data variables.product.prodname_codeql %} pack (beta) published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} or a {% data variables.product.prodname_ql %} pack stored in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
+You can run extra queries if they are part of a {% data variables.product.prodname_codeql %} pack (beta) published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} or a {% data variables.product.prodname_ql %} pack stored in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
 
 The options available to specify the additional queries you want to run are:
 
 - `packs` to install one or more {% data variables.product.prodname_codeql %} query packs (beta) and run the default query suite or queries for those packs.
-- `queries` to specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. クエリスイートの定義に関する詳しい情報については「[{% data variables.product.prodname_codeql %}クエリスイートの作成](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)」を参照してください。
+- `queries` to specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. For more information about query suite definitions, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)."
 
 You can use both `packs` and `queries` in the same workflow.
 {% else %}
-Any additional queries you want to run must belong to a
-{% data variables.product.prodname_ql %} pack in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
+Any additional queries you want to run must belong to a {% data variables.product.prodname_ql %} pack in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
 
-単一の _.ql_ ファイル、複数の _.ql_ ファイルを含むディレクトリ、_.qls_ クエリスイート定義ファイル、または任意の組み合わせを指定できます。 クエリスイートの定義に関する詳しい情報については「[{% data variables.product.prodname_codeql %}クエリスイートの作成](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)」を参照してください。
+You can specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. For more information about query suite definitions, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)."
 {% endif %}
 
 {% ifversion fpt or ghec %}We don't recommend referencing query suites directly from the `github/codeql` repository, for example, `github/codeql/cpp/ql/src@main`. Such queries would have to be recompiled, and may not be compatible with the version of {% data variables.product.prodname_codeql %} currently active on {% data variables.product.prodname_actions %}, which could lead to errors during analysis.{% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md
index a2888bdc46..7ddce88f51 100644
--- a/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md
+++ b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md
@@ -1,8 +1,8 @@
 {% note %}
 
 **ノート:**
-- SARIF upload supports a maximum of 5000 results per upload. この制限を超えた結果は無視されます。 ツールがあまりに多くの結果を生成する場合、最も重要なルールやクエリに対する結果に焦点を当てるよう、設定を更新すべきです。
+- SARIFアップロードは、アップロードごとに最大5000件の結果をサポートします。 この制限を超えた結果は無視されます。 ツールがあまりに多くの結果を生成する場合、最も重要なルールやクエリに対する結果に焦点を当てるよう、設定を更新すべきです。
 
- - For each upload, SARIF upload supports a maximum size of 10 MB for the `gzip`-compressed SARIF file. Any uploads over this limit will be rejected. If your SARIF file is too large because it contains too many results, you should update the configuration to focus on results for the most important rules or queries.
+ - アップロードごとに、SARIFアップロードは最大10MBの`gzip`圧縮されたSARIFファイルをサポートします。 この制限を超えるアップロードは拒否されます。 結果が多すぎてSARIFファイルが大きすぎる場合、設定ファイルを更新して最も重要なルールやクエリに結果を集中させるようにすべきです。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md b/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md
index 3701caf95d..ad3e50ede9 100644
--- a/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md
+++ b/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md
@@ -1 +1 @@
-アプリケーションのテストとデバッグのために、codespace中のポートをフォワードできます。 You can also manage the port protocol and share the port within your organization or publicly.
+アプリケーションのテストとデバッグのために、codespace中のポートをフォワードできます。 ポートプロトコルを管理し、Organization内で、もしくはパブリックにポートを共有することもできます。
diff --git a/translations/ja-JP/data/reusables/codespaces/availability.md b/translations/ja-JP/data/reusables/codespaces/availability.md
index df1d8f27be..6e70aae964 100644
--- a/translations/ja-JP/data/reusables/codespaces/availability.md
+++ b/translations/ja-JP/data/reusables/codespaces/availability.md
@@ -1 +1 @@
-Codespaces are available for repositories owned by organizations using {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %}.
+Codespacesは、{% data variables.product.prodname_team %}及び{% data variables.product.prodname_ghe_cloud %}を使用するOrganizationが所有するリポジトリで利用できます。
diff --git a/translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md b/translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md
index ab80f5c0e1..a8f0fc5047 100644
--- a/translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md
+++ b/translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md
@@ -1,7 +1,7 @@
-By default, a {% data variables.product.prodname_actions %} workflow is triggered every time you create or update a prebuild template, or push to a prebuild-enabled branch. As with other workflows, while prebuild workflows are running they will either consume some of the Actions minutes included with your account, if you have any, or they will incur charges for Actions minutes. For more information about pricing for Actions minutes, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+デフォルトでは、{% data variables.product.prodname_actions %}ワークフローは事前ビルドされたテンプレートを作成あるいは更新するたび、あるいは事前ビルドが有効化されたブランチにプッシュするたびにトリガーされます。 他のワークフローと同じように、事前ビルドされたワークフローはアカウントに含まれるActionsの分があればその一部を消費し、そうでない場合はActionsの分に対する課金を生じさせます。 Actionsの分の価格に関する詳しい情報については「[{% data variables.product.prodname_actions %}の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。
 
-Alongside {% data variables.product.prodname_actions %} minutes, you will also be billed for the storage of prebuild templates associated with each prebuild configuration for a given repository and region. Storage of prebuild templates is billed at the same rate as storage of codespaces. For more information, see "[Calculating storage usage](#calculating-storage-usage)."
+{% data variables.product.prodname_actions %}の分と合わせて、指定されたリポジトリとリージョンについて、それぞれの事前ビルドされた設定と関連づけられた事前ビルドテンプレートのストレージに対しても課金されます。 事前ビルドされたテンプレートのストレージは、Codespacesのストレージと同じレートで課金されます。 詳しい情報については「[ストレージの利用の計算](#calculating-storage-usage)」を参照してください。
 
-To reduce consumption of Actions minutes, you can set a prebuild template to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. You can also manage your storage usage by adjusting the number of template versions to be retained for your prebuild configurations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
+Actionsの分の消費を削減するために、開発コンテナ設定ファイルを変更したときにのみ、あるいはカスタムのスケジュールだけに従って事前ビルドされたテンプレートが更新されるように設定できます。 また、事前ビルドされた設定に対して保持されるテンプレートのバージョン数を調整することによって、ストレージの使用量を管理することもできます。 詳しい情報については「[事前ビルドの設定](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)」を参照してください。
 
-If you are an organization owner, you can track usage of prebuild workflows and storage by downloading a {% data variables.product.prodname_actions %} usage report for your organization. You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create Codespaces Prebuilds." 詳しい情報については「[{% data variables.product.prodname_actions %}の利用状況の表示](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)」を参照してください。
+Organizationのオーナーは、事前ビルドされたワークフローとストレージの使用状況を、Organizationの{% data variables.product.prodname_actions %}使用状況レポートをダウンロードして追跡できます。 事前ビルドに対するワークフローの実行は、CSVの出力を"Create Codespaces Prebuilds"というワークフローだけが含まれるようにフィルタリングすれば、特定できます。 詳しい情報については「[{% data variables.product.prodname_actions %}の利用状況の表示](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-api-beta-note.md b/translations/ja-JP/data/reusables/codespaces/codespaces-api-beta-note.md
index 3bd6971a87..4141967f7b 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-api-beta-note.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-api-beta-note.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note**: The {% data variables.product.prodname_codespaces %} API is currently in public beta and subject to change.
+**ノート**: {% data variables.product.prodname_codespaces %} APIは現在パブリックベータであり、変更されることがあります。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md b/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md
index 0be4a46707..6f7db70036 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md
@@ -1,9 +1,9 @@
-{% data variables.product.prodname_codespaces %} are billed in US dollars (USD) according to their compute and storage usage.
+{% data variables.product.prodname_codespaces %}は、コンピュートとストレージの使用量に応じて米ドル（USD）で課金されます。
 
-### Calculating compute usage
-Compute usage is defined as the total number of uptime minutes for which a {% data variables.product.prodname_github_codespaces %} instance is active. Compute usage is calculated by summing the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly.
+### コンピュートの使用量の計算
+コンピュートの使用量は、{% data variables.product.prodname_github_codespaces %}インスタンスがアクティブな稼働時間の分の合計として定義されます。 コンピュートの使用量は、すべてのCodespacesが使用した実際の分数を合計することによって計算されます。 それらの合計は、日次で支払いサービスに報告され、月次で課金されます。
 
-Uptime is controlled by stopping your codespace, which can be done manually or automatically after a developer specified period of inactivity. For more information, see "[Closing or stopping your codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)".
+稼働時間はcodespaceを停止することによって制御でき、この停止は手動で行うことも、あるいは開発者が非アクティブな期間を指定したあとで自動的に行うこともできます。 詳しい情報については「[codespaceのクローズもしくは停止](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)」を参照してください。
 
-### Calculating storage usage
-For {% data variables.product.prodname_github_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and are billed monthly. 月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。 
+### ストレージの使用量の計算
+{% data variables.product.prodname_github_codespaces %}の支払いにおいては、アカウントのすべてのCodespacesが使用するすべてのストレージが含まれます。 これには、Codespacesが使うあらゆるファイル、中でもクローンされたリポジトリ、設定ファイル、機能拡張などが含まれます。 それらの合計は、日次で支払いサービスに報告され、月次で課金されます。 月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。 
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-type-availability.md b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-type-availability.md
index 557b845f10..d167ae1bc4 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-type-availability.md
+++ b/translations/ja-JP/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. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+利用可能なマシンタイプの選択は、Organizationで設定されたポリシーによって、あるいはリポジトリのマシンタイプの最小仕様によって制限されていることがあります。 詳しい情報については「[マシンタイプへのアクセスの制限](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)」及び「[codespaceマシンの最小仕様の設定](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md
index 53aecddf17..608b5ef7c1 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md
@@ -1,3 +1,3 @@
-Typically, you can run your codespace on a choice of remote machine, from 2 cores to 32 cores. これらはそれぞれ、異なるレベルのリソースと支払い層を持っています。 For information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+通常、codespaceは2コアから32コアでリモートのマシンを選択して実行できます。 これらはそれぞれ、異なるレベルのリソースと支払い層を持っています。 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)」を参照してください。
 
-By default the machine type with the lowest valid resources is used when you create a codespace. 
+codespaceを作成したとき、デフォルトでは有効な最小リソースを持つマシンタイプが使われます。 
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md
index ccf956a015..79c395d216 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md
@@ -1,3 +1,3 @@
-1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policies**.
-1. On the "Codespace policies" page, click **Create Policy**.
-1. Enter a name for your new policy.
+1. サイドバーの"Code, planning, and automation（コード、計画、自動化）"のセクションで、**{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}**を選択し、続いて** Policies（ポリシー）**をクリックしてください。
+1. "Codespace policies（ Codespaceのポリシー）"ページで、**Create Policy（ポリシーの作成）**をクリックしてください。
+1. 新しいポリシーの名前を入力してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md b/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md
index 04e4a9bfda..e9c2d3a2a9 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md
@@ -1,11 +1,11 @@
-1. In the "Change policy target" area, click the dropdown button.
-1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
+1. "Change policy target（ポリシーターゲットの変更）"のエリアで、ドロップダウンボタンをクリックしてください。
+1. **All repositories（すべてのリポジトリ）**もしくは**Selected repositories（選択したリポジトリ）**を選択し、ポリシーを適用するリポジトリを決定してください。
 1. [**Selected repositories**] を選択した場合、以下の手順に従います。
    1. {% octicon "gear" aria-label="The settings icon" %} をクリックします。
 
-      ![Edit the settings for the policy](/assets/images/help/codespaces/policy-edit.png)
+      ![ポリシー設定の編集](/assets/images/help/codespaces/policy-edit.png)
 
-   2. Select the repositories you want this policy to apply to.
-   3. At the bottom of the repository list, click **Select repositories**.
+   2. ポリシーを適用したいリポジトリを選択してください。
+   3. リポジトリリストの下部で、**Select repositories（リポジトリの選択）**をクリックしてください。
 
-      ![Select repositories for this policy](/assets/images/help/codespaces/policy-select-repos.png)
+      ![このポリシーのリポジトリを選択](/assets/images/help/codespaces/policy-select-repos.png)
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md b/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md
index 61e7031435..8f72ade561 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md
@@ -1,9 +1,9 @@
 {% note %}
 
-**Note:** You must set a spending limit before you can use {% data variables.product.prodname_codespaces %}.
+**ノート:** {% data variables.product.prodname_codespaces %}を利用するには、利用上限を設定しなければなりません。
 
 {% endnote %}
 
-By default, your organization or enterprise will have a {% data variables.product.prodname_github_codespaces %} spending limit of $0, which prevents new codespaces from being created or existing codespaces from being opened. To allow your users to create codespaces in your organization, set the limit to a value higher than $0.
+デフォルトでは、OrganizationもしくはEnterpriseは$0の{% data variables.product.prodname_github_codespaces %}の利用上限を持っており、これは新しいcodespaceの作成や、既存のcodespaceのオープンを禁止します。 Organiationでユーザがcodespaceを作成できるようにするには、この上限を$0よりも大きな値に設定してください。
 
 {% data reusables.billing.overages-billed-monthly %}
diff --git a/translations/ja-JP/data/reusables/codespaces/command-palette-container.md b/translations/ja-JP/data/reusables/codespaces/command-palette-container.md
index 0a3b03efb3..efad9c25b4 100644
--- a/translations/ja-JP/data/reusables/codespaces/command-palette-container.md
+++ b/translations/ja-JP/data/reusables/codespaces/command-palette-container.md
@@ -1,3 +1,3 @@
-1. Access the {% data variables.product.prodname_vscode_command_palette %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)), then start typing "dev container". **Codespaces: Add Development Container Configuration Files...（Codespaces: 開発コンテナ設定ファイルを追加...）**を選択してください。
+1. {% data variables.product.prodname_vscode_command_palette %}にアクセスし(<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux))、 "dev container"と入力し始めてください。 **Codespaces: Add Development Container Configuration Files...（Codespaces: 開発コンテナ設定ファイルを追加...）**を選択してください。
 
-   !["Codespaces: Add Development Container Configuration Files..." in the {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+   ![{% data variables.product.prodname_vscode_command_palette %}での"Codespaces: Add Development Container Configuration Files..."](/assets/images/help/codespaces/add-prebuilt-container-command.png)
diff --git a/translations/ja-JP/data/reusables/codespaces/contact-support.md b/translations/ja-JP/data/reusables/codespaces/contact-support.md
index b3ea0615e1..ea14af60a8 100644
--- a/translations/ja-JP/data/reusables/codespaces/contact-support.md
+++ b/translations/ja-JP/data/reusables/codespaces/contact-support.md
@@ -1 +1 @@
-you may need to contact support. For more information, see "[Working with support](/codespaces/troubleshooting/working-with-support-for-codespaces)."
+サポートに連絡する必要があるかもしれません。 詳しい情報については「[サポートとの作業](/codespaces/troubleshooting/working-with-support-for-codespaces)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md
index c6b3a9fde2..6ad33181dd 100644
--- a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md
+++ b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md
@@ -1,17 +1,17 @@
-After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. 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).
+{% data variables.product.product_location %}上のアカウントを{% data variables.product.prodname_github_codespaces %}の機能拡張に接続すると、新しいcodespaceを作成できます。 {% data variables.product.prodname_github_codespaces %}の機能拡張に関する詳しい情報については[{% data variables.product.prodname_vs_marketplace_shortname %} Marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces)を参照してください。
 
 {% note %}
 
-**Note**: Currently, {% data variables.product.prodname_vscode_shortname %} doesn't allow you to choose a dev container configuration when you create a codespace. If you want to choose a specific dev container configuration, use the {% data variables.product.prodname_dotcom %} web interface to create your codespace. For more information, click the **Web browser** tab at the top of this page.
+**ノート**: 現在、{% data variables.product.prodname_vscode_shortname %}ではcodespaceの作成時に開発コンテナの設定を選択することはできません。 特定の開発コンテナの設定を選択したい場合、{% data variables.product.prodname_dotcom %} Webインターフェースを使ってcodespaceを作成してください。 詳しい情報については、このページの上部の**Web browser（Webブラウザ）**タブをクリックしてください。
 
 {% endnote %}
 
 {% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-2. Click the Add icon: {% octicon "plus" aria-label="The plus icon" %}.
+2. 追加アイコン {% octicon "plus" aria-label="The plus icon" %} をクリックしてください。
 
    ![{% data variables.product.prodname_codespaces %} の [Create New Codespace] オプション](/assets/images/help/codespaces/create-codespace-vscode.png)
 
-3. Type the name of the repository you want to develop in, then select it.
+3. 開発を行いたいリポジトリ名を入力し、選択してください。
 
    ![新しい {% data variables.product.prodname_codespaces %} を作成するためのリポジトリを検索する](/assets/images/help/codespaces/choose-repository-vscode.png)
 
@@ -19,7 +19,7 @@ After you connect your account on {% data variables.product.product_location %}
 
    ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/choose-branch-vscode.png)
 
-5. Click the machine type you want to use.
+5. 使用したいマシンタイプをクリックしてください。
 
    ![新しい {% data variables.product.prodname_codespaces %} のインスタンスタイプ](/assets/images/help/codespaces/choose-sku-vscode.png)
 
diff --git a/translations/ja-JP/data/reusables/codespaces/customize-vcpus-and-ram.md b/translations/ja-JP/data/reusables/codespaces/customize-vcpus-and-ram.md
index f215b74e73..add53f86da 100644
--- a/translations/ja-JP/data/reusables/codespaces/customize-vcpus-and-ram.md
+++ b/translations/ja-JP/data/reusables/codespaces/customize-vcpus-and-ram.md
@@ -1,5 +1,5 @@
 vCPU と RAM の量を調整したり、[ドットファイルを追加して環境をパーソナライズ](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)したり、インストールされているツールやスクリプトを変更したりして、codespace をカスタマイズできます。
 
-{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to configure the development container that you use when you work in a codespace. Each repository can contain one or more  `devcontainer.json` files, to give you exactly the development environment you need to work on your code in a codespace.
+{% data variables.product.prodname_codespaces %}は`devcontainer.json`というファイルを使って、codespaceで作業する際に使用する開発コンテナを設定します。 それぞれのリポジトリには1つ以上の`devcontainer.json`ファイルを含めて、codespaceでコードの作業をするのに必要なとおりの開発環境を提供できます。
 
-On launch, {% data variables.product.prodname_codespaces %} uses a `devcontainer.json` file, and any dependent files that make up the dev container configuration, to install tools and runtimes, and perform other setup tasks that the project requires. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+起動時に{% data variables.product.prodname_codespaces %}は`devcontainer.json`ファイルと開発コンテナの設定を構成する依存ファイルを使い、ツールやランタイムをンストールし、プロジェクトが必要とするその他のセットアップタスクを行います。 詳しい情報については「[開発コンテナの紹介](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/deleting-a-codespace-in-vscode.md b/translations/ja-JP/data/reusables/codespaces/deleting-a-codespace-in-vscode.md
index 11feb3a8f3..1119abf9e8 100644
--- a/translations/ja-JP/data/reusables/codespaces/deleting-a-codespace-in-vscode.md
+++ b/translations/ja-JP/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.
+codespaceで作業をしていないときは、{% data variables.product.prodname_vscode_shortname %}内からcodespaceを削除できます。
 
 {% 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. "GITHUB CODESPACES"の下で、削除したいcodespaceを右クリックしてください。
+1. **Delete Codespace（Codespaceを削除）**をクリックしてください。
 
    ![{% data variables.product.prodname_dotcom %} で Codespaces を削除する](/assets/images/help/codespaces/delete-codespace-vscode.png)
diff --git a/translations/ja-JP/data/reusables/codespaces/exporting-changes.md b/translations/ja-JP/data/reusables/codespaces/exporting-changes.md
index f2c0e5a6e3..ca43afc318 100644
--- a/translations/ja-JP/data/reusables/codespaces/exporting-changes.md
+++ b/translations/ja-JP/data/reusables/codespaces/exporting-changes.md
@@ -1 +1 @@
-If you hit a spending limit, you will no longer be able to create or resume your codespaces. You can still [export any work in progress changes to a new branch](/codespaces/troubleshooting/exporting-changes-to-a-branch). 
+利用上限に達すると、codespaceを作成したり再開したりすることはできなくなります。 ただし[進行中の変更を新しいブランチにエクスポート](/codespaces/troubleshooting/exporting-changes-to-a-branch)することはできます。 
diff --git a/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md b/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md
index d4e5abc125..d6e5aa5ebc 100644
--- a/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md
+++ b/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md
@@ -1 +1 @@
-To get started with {% data variables.product.prodname_codespaces %}, see "[Quickstart for {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/quickstart)." To learn more about how {% data variables.product.prodname_codespaces %} works, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)."
+{% data variables.product.prodname_codespaces %}を使い始めるには、「[{% data variables.product.prodname_github_codespaces %}のクイックスタート](/codespaces/getting-started/quickstart)」を参照してください。 {% data variables.product.prodname_codespaces %}がどのように動作するのか、詳しく学ぶには「[{% data variables.product.prodname_github_codespaces %}を深く掘り下げる](/codespaces/getting-started/deep-dive)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md b/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md
index 0980b3abc4..688c7f5842 100644
--- a/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md
+++ b/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md
@@ -1 +1 @@
-For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+`devcontainer.json`ファイルで可能な設定とプロパティについては、{% data variables.product.prodname_vscode_shortname %} ドキュメントの 「[devcontainer.json リファレンス](https://aka.ms/vscode-remote/devcontainer.json)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/port-visibility-settings.md b/translations/ja-JP/data/reusables/codespaces/port-visibility-settings.md
index 9879723104..9bb16553fd 100644
--- a/translations/ja-JP/data/reusables/codespaces/port-visibility-settings.md
+++ b/translations/ja-JP/data/reusables/codespaces/port-visibility-settings.md
@@ -1,5 +1,5 @@
-There are three visibility settings:
+可視性の設定は3つあります:
 
-* `private` - Visible only to you. This is the default setting when you forward a port.
-* `org` - Visible to members of the organization that owns the repository.
-* `public` - Visible to anyone who knows the URL and port number.
+* `private` - 自分にだけ見えます。 これはポートをフォワードする際のデフォルト設定です。
+* `org` - リポジトリを所有するOrganizationのメンバーに見えます。
+* `public` - URLとポート番号を知っている人なら誰にでも見えます。
diff --git a/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md b/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md
index 68d9b051fd..ef98855a91 100644
--- a/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md
+++ b/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md
@@ -1 +1 @@
-To speed up codespace creation, repository administrators can enable {% data variables.product.prodname_codespaces %} prebuilds for a repository. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."
+codespaceの作成を高速化するために、リポジトリの管理者はリポジトリで{% data variables.product.prodname_codespaces %}の事前ビルドを有効化できます。 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の事前ビルドについて](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md b/translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md
index c82899edb6..632cb4a61c 100644
--- a/translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md
+++ b/translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md
@@ -1 +1 @@
-Prebuilds are not available if you choose to use a `devcontainer.json` file from a `.devcontainer/SUBDIRECTORY` location when you create a codespace. For information about choosing a `devcontainer.json` file, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
+codespaceを作成する際に`.devcontainer/SUBDIRECTORY`という場所から`devcontainer.json`ファイルを使うよう選択した場合、事前ビルドは利用できません。 `devcontainer.json`ファイルを選択することに関する情報については「[codespaceの作成](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/rebuild-command.md b/translations/ja-JP/data/reusables/codespaces/rebuild-command.md
index ebdc1b5c0e..9e79fd326b 100644
--- a/translations/ja-JP/data/reusables/codespaces/rebuild-command.md
+++ b/translations/ja-JP/data/reusables/codespaces/rebuild-command.md
@@ -1,4 +1,4 @@
-1. Access the {% data variables.product.prodname_vscode_command_palette %} (<kbd>Shift</kbd> + <kbd>Command</kbd> + <kbd>P</kbd> / <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd>), then start typing "rebuild". **Codespaces: Rebuild Container（Codespaces: コンテナをリビルド）**を選択してください。
+1. {% data variables.product.prodname_vscode_command_palette %}にアクセスし(<kbd>Shift</kbd> + <kbd>Command</kbd> + <kbd>P</kbd> / <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd>)、"rebuild"と入力し始めてください。 **Codespaces: Rebuild Container（Codespaces: コンテナをリビルド）**を選択してください。
 
     ![コンテナリビルドの選択肢](/assets/images/help/codespaces/codespaces-rebuild.png)
     
diff --git a/translations/ja-JP/data/reusables/codespaces/recovery-mode.md b/translations/ja-JP/data/reusables/codespaces/recovery-mode.md
index bc0a55a9cc..07d3a26e26 100644
--- a/translations/ja-JP/data/reusables/codespaces/recovery-mode.md
+++ b/translations/ja-JP/data/reusables/codespaces/recovery-mode.md
@@ -1 +1 @@
-If changes to your dev container configuration cause a container error, your codespace will run in recovery mode, and you will see an error message.
+開発コンテナの設定の変更でコンテナエラーが生じた場合、codespaceはリカバリモードで動作し、エラーメッセージが表示されます。
diff --git a/translations/ja-JP/data/reusables/codespaces/restrict-port-visibility.md b/translations/ja-JP/data/reusables/codespaces/restrict-port-visibility.md
index ca60cbd5a4..1bbb289023 100644
--- a/translations/ja-JP/data/reusables/codespaces/restrict-port-visibility.md
+++ b/translations/ja-JP/data/reusables/codespaces/restrict-port-visibility.md
@@ -1 +1 @@
-Organization owners can restrict the ability to make forward ports available publicly or within the organization. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
+Organizationのオーナーは、ポートのフォワードをパブリックに、あるいはOrganization内で利用できるようにする機能を制限できます。 詳しい情報については「[フォワードされたポートの可視性の制限](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/review-pr.md b/translations/ja-JP/data/reusables/codespaces/review-pr.md
index cf263511e8..f7305af917 100644
--- a/translations/ja-JP/data/reusables/codespaces/review-pr.md
+++ b/translations/ja-JP/data/reusables/codespaces/review-pr.md
@@ -1,5 +1,5 @@
-1. Open the pull request in a codespace, as described in "[Opening a pull request](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)."
-2. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace. ![Option to open PR in a codespace](/assets/images/help/codespaces/github-pr-view.png)
-3. To review a specific file, click the **Open File** icon in the Side Bar. ![Option to open PR in a codespace](/assets/images/help/codespaces/changes-in-files.png)
-4. To add review comments, click the **+** icon next to the line number. Type your review comment and then click **Start Review**. ![Option to open PR in a codespace](/assets/images/help/codespaces/start-review.png)
-5. When you are finished adding review comments, from the Side Bar you can choose to either submit the comments, approve the changes, or request changes. ![Option to open PR in a codespace](/assets/images/help/codespaces/submit-review.png)
+1. 「[Pull Requestのオープン](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)」の説明に従って、codespaceでPull Requestをオープンしてください。
+2. アクティビティバーで、**GitHub Pull Request**ビューをクリックしてください。 このビューは、codespaceでPull Requestをオープンした場合にのみ表示されます。 ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/github-pr-view.png)
+3. 特定のファイルをレビューするには、サイドバーの**Open File（ファイルをオープン）**アイコンをクリックしてください。 ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/changes-in-files.png)
+4. レビューコメントを追加するには、行番号の隣の**+**をクリックしてください。 レビューコメントを入力し、**Start Review（レビューを開始）**をクリックしてください。 ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/start-review.png)
+5. レビューコメントの追加を完了したら、コメントをサブミットするか、変更を承認するか、変更をリクエストするかをサイドバーから選択できます。 ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/submit-review.png)
diff --git a/translations/ja-JP/data/reusables/codespaces/secret-precedence.md b/translations/ja-JP/data/reusables/codespaces/secret-precedence.md
index ff45e6dc04..23562721a3 100644
--- a/translations/ja-JP/data/reusables/codespaces/secret-precedence.md
+++ b/translations/ja-JP/data/reusables/codespaces/secret-precedence.md
@@ -1 +1 @@
-If a secret with the same name exists at multiple levels, the secret at the lowest level takes precedence. たとえば、Organization レベルのシークレット名がリポジトリレベルのシークレット名と同じ場合、リポジトリレベルのシークレット名が優先されます。
+複数のレベルで同じ名前のシークレットが存在する場合、最も低いレベルのシークレットが優先されます。 たとえば、Organization レベルのシークレット名がリポジトリレベルのシークレット名と同じ場合、リポジトリレベルのシークレット名が優先されます。
diff --git a/translations/ja-JP/data/reusables/codespaces/setup-custom-devcontainer.md b/translations/ja-JP/data/reusables/codespaces/setup-custom-devcontainer.md
index 5a973ebb51..6f32bfdd0d 100644
--- a/translations/ja-JP/data/reusables/codespaces/setup-custom-devcontainer.md
+++ b/translations/ja-JP/data/reusables/codespaces/setup-custom-devcontainer.md
@@ -1 +1 @@
-To set up your repository to use a custom dev container, you will need to create one or more `devcontainer.json` files. You can add these either from a template, in {% data variables.product.prodname_vscode %}, or you can write your own. For more information on dev container configurations, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+カスタムの開発コンテナを使うようにリポジトリをセットアップするには、1つ以上の`devcontainer.json`ファイルを作成しなければなりません。 これらは{% data variables.product.prodname_vscode %}内でテンプレートから追加することも、独自に書くこともできます。 開発コンテナの設定に関する詳しい情報については「[開発コンテナの紹介](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
index f93d8ed377..a9a658277a 100644
--- a/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
+++ b/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -1,3 +1,3 @@
-1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Your codespaces**.
+1. {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}の右上から、プロフィール写真をクリックし、続いて**Your codespaces（あなたのcodespaces）**をクリックしてください。
 
-  !['自分のcodespaces'メニューオプション](/assets/images/help/codespaces/your-codespaces-option.png)
+  !['あなたのcodespaces'メニューオプション](/assets/images/help/codespaces/your-codespaces-option.png)
diff --git a/translations/ja-JP/data/reusables/command-palette/beta-note.md b/translations/ja-JP/data/reusables/command-palette/beta-note.md
index a6681190ee..f27f91ba18 100644
--- a/translations/ja-JP/data/reusables/command-palette/beta-note.md
+++ b/translations/ja-JP/data/reusables/command-palette/beta-note.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** The {% data variables.product.prodname_command_palette %} is currently in public beta and is subject to change.
+**ノート:** {% data variables.product.prodname_command_palette %}は現在パブリックベータであり、変更されることがあります。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/command-palette/change-scope.md b/translations/ja-JP/data/reusables/command-palette/change-scope.md
index 4cf46c21a4..2823401a3b 100644
--- a/translations/ja-JP/data/reusables/command-palette/change-scope.md
+++ b/translations/ja-JP/data/reusables/command-palette/change-scope.md
@@ -1,5 +1,5 @@
-1. Optionally, narrow, expand, or completely change the scope for suggestions by editing the path in the command palette's text field.
+1. あるいは、コマンドパレットのテキストフィールド内のパスを編集することによって、候補のスコープを狭めたり、広げたり、完全に変更したりしてください。
 
-   - To narrow the scope within a user or organization account, highlight a repository then use <kbd>Tab</kbd> to add it to the scope.
-   - To expand the scope, highlight and remove an item in the scope using the <kbd>Backspace</kbd> or <kbd>delete</kbd> key.
-   - To clear the scope and text box, click **Clear** or use <kbd>Ctrl</kbd><kbd>Backspace</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Backspace</kbd> (Mac).
+   - スコープをユーザもしくはOragnizationアカウント内に狭めるには、リポジトリをハイライトしてから<kbd>Tab</kbd>を使ってそのリポジトリをスコープに追加してください。
+   - スコープを広げるには、スコープ内のアイテムをハイライトしてから<kbd>バックスペース</kbd>もしくは<kbd>削除</kbd>キーを使って削除してください。
+   - スコープとテキストボックスをクリアするには、**Clear（クリア）**をクリックするか、<kbd>Ctrl</kbd><kbd>Backspace</kbd> (Windows and Linux)もしくは<kbd>⌘</kbd><kbd>Backspace</kbd> (Mac)を使ってください。
diff --git a/translations/ja-JP/data/reusables/command-palette/open-palette.md b/translations/ja-JP/data/reusables/command-palette/open-palette.md
index 46636e2c25..3b189abfb4 100644
--- a/translations/ja-JP/data/reusables/command-palette/open-palette.md
+++ b/translations/ja-JP/data/reusables/command-palette/open-palette.md
@@ -1 +1 @@
-1. Use <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) or <kbd>Command</kbd>+<kbd>K</kbd> (Mac) to open the command palette with a scope determined by your current location in the UI. 
+1. <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)もしくは<kbd>Command</kbd>+<kbd>K</kbd> (Mac) を使い、UI中の現在の場所で決まるスコープでコマンドパレットをオープンしてください。 
diff --git a/translations/ja-JP/data/reusables/community/issue-forms-beta.md b/translations/ja-JP/data/reusables/community/issue-forms-beta.md
index 9c912118dd..36dea274ae 100644
--- a/translations/ja-JP/data/reusables/community/issue-forms-beta.md
+++ b/translations/ja-JP/data/reusables/community/issue-forms-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Issue forms are currently in beta for public repositories on {% data variables.product.prodname_dotcom_the_website %} only.
+**ノート:** Issue フォームは、現在ベータとして{% data variables.product.prodname_dotcom_the_website %} の公開リポジトリでのみ利用できます。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/copilot/accept-or-reject-suggestion.md b/translations/ja-JP/data/reusables/copilot/accept-or-reject-suggestion.md
index 56cc4ec30a..707e856d4d 100644
--- a/translations/ja-JP/data/reusables/copilot/accept-or-reject-suggestion.md
+++ b/translations/ja-JP/data/reusables/copilot/accept-or-reject-suggestion.md
@@ -1 +1 @@
-1. To accept a suggestion, press <kbd>Tab</kbd>. To reject all suggestions, press <kbd>Esc</kbd>.
+1. 提案を受け入れるには<kbd>タブ</kbd>を押してください。 すべての提案を拒否するには<kbd>Esc</kbd>を押してください。
diff --git a/translations/ja-JP/data/reusables/copilot/accept-suggestion-new-tab.md b/translations/ja-JP/data/reusables/copilot/accept-suggestion-new-tab.md
index 183cf25da8..332c0c13ae 100644
--- a/translations/ja-JP/data/reusables/copilot/accept-suggestion-new-tab.md
+++ b/translations/ja-JP/data/reusables/copilot/accept-suggestion-new-tab.md
@@ -1 +1 @@
-1. To accept a suggestion from the new tab, above the suggestion you want to accept, click **Accept solution**.
+1. 新しいタブからの提案を受け入れるには、受け入れたい提案の上の**Accept solution（ソリューションを受け入れる）**をクリックしてください。
diff --git a/translations/ja-JP/data/reusables/copilot/accept-suggestion-tab.md b/translations/ja-JP/data/reusables/copilot/accept-suggestion-tab.md
index 5bee724a53..a64b405d1d 100644
--- a/translations/ja-JP/data/reusables/copilot/accept-suggestion-tab.md
+++ b/translations/ja-JP/data/reusables/copilot/accept-suggestion-tab.md
@@ -1 +1 @@
-1. If {% data variables.product.prodname_copilot %} offers a suggestion you want to accept, press <kbd>Tab</kbd>.
+1. {% data variables.product.prodname_copilot %}が受け入れたい提案をしてきたら、<kbd>タブ</kbd>を押してください。
diff --git a/translations/ja-JP/data/reusables/copilot/accept-suggestion.md b/translations/ja-JP/data/reusables/copilot/accept-suggestion.md
index 4882c5d748..a972f3e690 100644
--- a/translations/ja-JP/data/reusables/copilot/accept-suggestion.md
+++ b/translations/ja-JP/data/reusables/copilot/accept-suggestion.md
@@ -1 +1 @@
-1. To accept the suggestion, press <kbd>Tab</kbd>.
+1. 提案を受け入れるには<kbd>タブ</kbd>を押してください。
diff --git a/translations/ja-JP/data/reusables/copilot/alternative-suggestions.md b/translations/ja-JP/data/reusables/copilot/alternative-suggestions.md
index a92c9879c7..ea13525d1d 100644
--- a/translations/ja-JP/data/reusables/copilot/alternative-suggestions.md
+++ b/translations/ja-JP/data/reusables/copilot/alternative-suggestions.md
@@ -1 +1 @@
-For any given input, {% data variables.product.prodname_copilot %} may offer multiple suggestions. You can select which suggestion to use, or reject all suggestions.
+任意の入力に対して{% data variables.product.prodname_copilot %}は複数の提案をすることがあります。 使用する提案を選択したり、すべての提案を拒否したりすることができます。
diff --git a/translations/ja-JP/data/reusables/copilot/close-suggestions-tab.md b/translations/ja-JP/data/reusables/copilot/close-suggestions-tab.md
index 22b4ce4d82..1827274313 100644
--- a/translations/ja-JP/data/reusables/copilot/close-suggestions-tab.md
+++ b/translations/ja-JP/data/reusables/copilot/close-suggestions-tab.md
@@ -1 +1 @@
-1. Alternatively, to reject all suggestions, close the suggestions tab.
+1. あるいは、すべての提案を拒否するには、提案のタブを閉じてください。
diff --git a/translations/ja-JP/data/reusables/copilot/copilot-prerequisites.md b/translations/ja-JP/data/reusables/copilot/copilot-prerequisites.md
index a3436c556e..bcec9ba4ed 100644
--- a/translations/ja-JP/data/reusables/copilot/copilot-prerequisites.md
+++ b/translations/ja-JP/data/reusables/copilot/copilot-prerequisites.md
@@ -1,2 +1,2 @@
-- {% data variables.product.prodname_copilot %} is free to use for verified students and open source maintainers.
-- If you are not a student or open source maintainer, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. You must provide billing information in order to start a free trial. 詳しい情報については、「[{% data variables.product.prodname_copilot %}の支払いについて](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)」を参照してください。
+- {% data variables.product.prodname_copilot %}は、検証済みの学生やオープンソースのメンテナなら無料で使用できます。
+- 学生やオープンソースのメンテナではない人は、1回60日のトライアルで{% data variables.product.prodname_copilot %}を無料で試すことができます。 無料のトライアルが終わったあと、継続して使うには有料プランが必要になります。 無料トライアルを始めるには、支払い情報を提供しなければなりません。 詳しい情報については、「[{% data variables.product.prodname_copilot %}の支払いについて](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/copilot/create-c-file.md b/translations/ja-JP/data/reusables/copilot/create-c-file.md
index 9a40edc6ce..724d84084c 100644
--- a/translations/ja-JP/data/reusables/copilot/create-c-file.md
+++ b/translations/ja-JP/data/reusables/copilot/create-c-file.md
@@ -1 +1 @@
-1. In {% data variables.product.prodname_vs %}, create a new C# (_*.cs_) file.
+1. {% data variables.product.prodname_vs %}で、新しいC#(_*.cs_) のファイルを作成してください。
diff --git a/translations/ja-JP/data/reusables/copilot/create-java-file.md b/translations/ja-JP/data/reusables/copilot/create-java-file.md
index d38696a1dd..b8a6abde9c 100644
--- a/translations/ja-JP/data/reusables/copilot/create-java-file.md
+++ b/translations/ja-JP/data/reusables/copilot/create-java-file.md
@@ -1 +1 @@
-1. In your JetBrains IDE, create a new Java (_*.java_) file.
+1. JetBrains IDEで、新しいJava (_*.java_) のファイルを作成してください。
diff --git a/translations/ja-JP/data/reusables/copilot/create-js-file.md b/translations/ja-JP/data/reusables/copilot/create-js-file.md
index 38946eaa58..530fb6757f 100644
--- a/translations/ja-JP/data/reusables/copilot/create-js-file.md
+++ b/translations/ja-JP/data/reusables/copilot/create-js-file.md
@@ -1 +1 @@
-1. In {% data variables.product.prodname_vscode %}, create a new JavaScript (_*.js_) file.
+1. {% data variables.product.prodname_vscode %}で、新しいJavaScript(_*.js_)のファイルを作成してください。
diff --git a/translations/ja-JP/data/reusables/copilot/dotcom-settings.md b/translations/ja-JP/data/reusables/copilot/dotcom-settings.md
index 80318ab8a0..49c4afdfd7 100644
--- a/translations/ja-JP/data/reusables/copilot/dotcom-settings.md
+++ b/translations/ja-JP/data/reusables/copilot/dotcom-settings.md
@@ -6,7 +6,8 @@ Once you have an active {% data variables.product.prodname_copilot %} trial or s
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.copilot-settings %}
-1. Under **Suggestions matching public code**, select the dropdown menu, then click **Allow** to allow suggestions matching public code, or **Block** to block suggestions matching public code. ![Screenshot of duplication detection option](/assets/images/help/copilot/duplication-detection.png)
+1. Under **Suggestions matching public code**, select the dropdown menu, then click **Allow** to allow suggestions matching public code, or **Block** to block suggestions matching public code.
+  ![Screenshot of duplication detection option](/assets/images/help/copilot/duplication-detection.png)
 {% data reusables.copilot.save-settings %}
 
 ### Enabling or disabling telemetry
@@ -15,5 +16,6 @@ You can configure how {% data variables.product.prodname_copilot %} uses your da
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.copilot-settings %}
-1. To allow or prevent {% data variables.product.prodname_dotcom %} using your telemetry data, select or deselect **Allow {% data variables.product.prodname_dotcom %} to use my code snippets for product improvements**. ![Screenshot of telemetry option](/assets/images/help/copilot/telemetry-option.png)
+1. To allow or prevent {% data variables.product.prodname_dotcom %} using your telemetry data, select or deselect **Allow {% data variables.product.prodname_dotcom %} to use my code snippets for product improvements**.
+  ![Screenshot of telemetry option](/assets/images/help/copilot/telemetry-option.png)
 {% data reusables.copilot.save-settings %}
diff --git a/translations/ja-JP/data/reusables/copilot/enabling-disabling-in-jetbrains.md b/translations/ja-JP/data/reusables/copilot/enabling-disabling-in-jetbrains.md
index 51edb37e07..a381d0e1a3 100644
--- a/translations/ja-JP/data/reusables/copilot/enabling-disabling-in-jetbrains.md
+++ b/translations/ja-JP/data/reusables/copilot/enabling-disabling-in-jetbrains.md
@@ -1,6 +1,6 @@
 ## {% data variables.product.prodname_copilot %} の有効化または無効化
 
-You can enable or disable {% data variables.product.prodname_copilot %} from within JetBrains. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of the JetBrains window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the icon is highlighted. When disabled, the icon is grayed out.
+{% data variables.product.prodname_copilot %}は、JetBrainsから有効化あるいは無効化できます。 JetBrainsウィンドウの下部のパネルの{% data variables.product.prodname_copilot %}ステータスアイコンは、{% data variables.product.prodname_copilot %}が有効化されているか、無効化されているかを示します。 有効化されている場合、このアイコンはハイライトされています。 無効化されている場合、このアイコンは灰色になります。
 
-1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the JetBrains window. ![Screenshot of status icon in JetBrains](/assets/images/help/copilot/status-icon-jetbrains.png)
-2. If you are disabling {% data variables.product.prodname_copilot %}, JetBrains will ask whether you want to disable the feature globally, or for the language of the file you are currently editing. To disable globally, click **Disable Completions**. Alternatively, click the button to disable completions for the language of the file you are currently editing. ![Screenshot of options to disable {% data variables.product.prodname_copilot %} globally or for the current language](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png)
+1. {% data variables.product.prodname_copilot %}を有効化あるいは無効化するには、JetBrainsウィンドウの下部のパネルでステータスアイコンをクリックしてください。 ![JetBrainsのステータスアイコンのスクリーンショット](/assets/images/help/copilot/status-icon-jetbrains.png)
+2. {% data variables.product.prodname_copilot %}を無効化しようとしている場合、JetBrainsはこの機能をグローバルに無効化したいのか、あるいは現在編集中の言語のファイルで無効化したいのかを尋ねてきます。 グローバルに無効化する場合は**Disable Completions（補完の無効化）**をクリックしてください。 あるいは、現在編集中のファイルの言語に対する補完の無効化のボタンをクリックしてください。 ![グローバルもしくは現在の言語に対する{% data variables.product.prodname_copilot %}の無効化のオプションのスクリーンショット](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png)
diff --git a/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-in-vsc.md b/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-in-vsc.md
index 2072011e5d..de3cc41cc8 100644
--- a/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-in-vsc.md
+++ b/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-in-vsc.md
@@ -1,9 +1,11 @@
-## {% data variables.product.prodname_copilot %} の有効化または無効化
+## Enabling or disabling {% data variables.product.prodname_copilot %}
 
 You can enable or disable {% data variables.product.prodname_copilot %} from within {% data variables.product.prodname_vscode %}. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of the {% data variables.product.prodname_vscode %} window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the background color of the icon will match the color of the status bar. When disabled, the background color of the icon will contrast with the color of the status bar.
 
-1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the {% data variables.product.prodname_vscode %} window. ![Screenshot of the status icon in {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/status-icon-visual-studio-code.png)
+1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the {% data variables.product.prodname_vscode %} window.
+   ![Screenshot of the status icon in {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/status-icon-visual-studio-code.png)
 2. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable suggestions globally, or for the language of the file you are currently editing.
 
    - To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Disable Globally**.
-   - To disable suggestions from {% data variables.product.prodname_copilot %} for the specified language, click **Disable for _LANGUAGE_**. ![Screenshot of option to disable {% data variables.product.prodname_copilot %} globally or for the current language](/assets/images/help/copilot/disable-copilot-global-or-langugage.png)
+   - To disable suggestions from {% data variables.product.prodname_copilot %} for the specified language, click **Disable for _LANGUAGE_**.
+   ![Screenshot of option to disable {% data variables.product.prodname_copilot %} globally or for the current language](/assets/images/help/copilot/disable-copilot-global-or-langugage.png)
diff --git a/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-vs.md b/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-vs.md
index 50b19449a3..934ca3c637 100644
--- a/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-vs.md
+++ b/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-vs.md
@@ -1,8 +1,9 @@
-## {% data variables.product.prodname_copilot %} の有効化または無効化
+## Enabling or disabling {% data variables.product.prodname_copilot %}
 
 The {% data variables.product.prodname_copilot %} status icon in the bottom panel of the {% data variables.product.prodname_vs %} window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the background color of the icon will match the color of the status bar. When disabled, it will have a diagonal line through it.
 
-1. To enable or disable {% data variables.product.prodname_copilot %}, click the {% data variables.product.prodname_copilot %} icon in the bottom panel of the {% data variables.product.prodname_vs %} window. ![Screenshot of editor margin in Visual Studio with the GitHub Copilot icon emphasized](/assets/images/help/copilot/editor-margin-visual-studio.png)
+1. To enable or disable {% data variables.product.prodname_copilot %}, click the {% data variables.product.prodname_copilot %} icon in the bottom panel of the {% data variables.product.prodname_vs %} window.
+  ![Screenshot of editor margin in Visual Studio with the GitHub Copilot icon emphasized](/assets/images/help/copilot/editor-margin-visual-studio.png)
 2. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable suggestions globally, or for the language of the file you are currently editing.
 
    - To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Enable Globally**.
diff --git a/translations/ja-JP/data/reusables/copilot/generating-suggestions-from-comments.md b/translations/ja-JP/data/reusables/copilot/generating-suggestions-from-comments.md
index ad62637674..0437723ca4 100644
--- a/translations/ja-JP/data/reusables/copilot/generating-suggestions-from-comments.md
+++ b/translations/ja-JP/data/reusables/copilot/generating-suggestions-from-comments.md
@@ -1 +1 @@
-You can describe something you want to do using natural language within a comment, and {% data variables.product.prodname_copilot %} will suggest the code to accomplish your goal.
+やりたいことは自然言語でコメント内に記述でき、{% data variables.product.prodname_copilot %}はその目的を達成するためのコードを提案します。
diff --git a/translations/ja-JP/data/reusables/copilot/install-copilot-in-neovim.md b/translations/ja-JP/data/reusables/copilot/install-copilot-in-neovim.md
index d2de9c1036..51937e45af 100644
--- a/translations/ja-JP/data/reusables/copilot/install-copilot-in-neovim.md
+++ b/translations/ja-JP/data/reusables/copilot/install-copilot-in-neovim.md
@@ -1,2 +1,2 @@
-1. To use {% data variables.product.prodname_copilot %} in Neovim, install the {% data variables.product.prodname_copilot %} plugin. You can either install the plugin from a plugin manager or directly.
-   - If you use a plugin manager like vim-plug or packer.nvim, use the plugin manager to install `github/copilot.vim`. For more information, see the documentation for the plugin manager. For example, you can see the documentation for [vim-plug](https://github.com/junegunn/vim-plug) or [packer.nvim](https://github.com/wbthomason/packer.nvim).
+1. {% data variables.product.prodname_copilot %}をNeovimで使うには、{% data variables.product.prodname_copilot %}プラグインをインストールしてください。 プラグインは、プラグインマネージャーから、もしくは直接にインストールできます。
+   - vim-plugあるいはpacker.nvimのようなプラグインマネージャーを使っているなら、そのプラグインマネージャーを使って`github/copilot.vim`をインストールしてください。 詳しい情報についてはプラグインマネージャーのドキュメンテーションを参照してください。 たとえば[vim-plug](https://github.com/junegunn/vim-plug)あるいは[packer.nvim](https://github.com/wbthomason/packer.nvim)のドキュメンテーションが参照できます。
diff --git a/translations/ja-JP/data/reusables/copilot/jetbrains-ides.md b/translations/ja-JP/data/reusables/copilot/jetbrains-ides.md
index 8beae81654..cc7011c2cb 100644
--- a/translations/ja-JP/data/reusables/copilot/jetbrains-ides.md
+++ b/translations/ja-JP/data/reusables/copilot/jetbrains-ides.md
@@ -1,4 +1,4 @@
-To use {% data variables.product.prodname_copilot %} in JetBrains, you must have a compatible JetBrains IDE installed. {% data variables.product.prodname_copilot %} is compatible with the following IDEs.
+{% data variables.product.prodname_copilot %}をJetBrainsで使うには、互換性のあるJetBrains IDEをインストールしていなければなりません。 {% data variables.product.prodname_copilot %}は以下のIDEと互換性があります。
 
 - IntelliJ IDEA (Ultimate, Community, Educational)
 - Android Studio
@@ -16,4 +16,4 @@ To use {% data variables.product.prodname_copilot %} in JetBrains, you must have
 - RubyMine
 - WebStorm
 
-For more information, see the [JetBrains IDEs](https://www.jetbrains.com/products/) tool finder.
+詳しい情報については[JetBrains IDEs](https://www.jetbrains.com/products/)ツールファインダーを参照してください。
diff --git a/translations/ja-JP/data/reusables/copilot/procedural-intro.md b/translations/ja-JP/data/reusables/copilot/procedural-intro.md
index 4c4cd6306d..5cb3b7e996 100644
--- a/translations/ja-JP/data/reusables/copilot/procedural-intro.md
+++ b/translations/ja-JP/data/reusables/copilot/procedural-intro.md
@@ -1 +1 @@
-{% data variables.product.prodname_copilot %} provides autocomplete-style suggestions from an AI pair programmer as you code. For more information, see "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)".
+{% data variables.product.prodname_copilot %}は、コーディング中にAIペアプログラマから自動補完スタイルの提案を提供します。 詳しい情報については「[{% data variables.product.prodname_copilot %}について](/copilot/overview-of-github-copilot/about-github-copilot)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/copilot/reject-suggestions-escape.md b/translations/ja-JP/data/reusables/copilot/reject-suggestions-escape.md
index 6d7bfe5886..4677df4289 100644
--- a/translations/ja-JP/data/reusables/copilot/reject-suggestions-escape.md
+++ b/translations/ja-JP/data/reusables/copilot/reject-suggestions-escape.md
@@ -1 +1 @@
-1. Alternatively, to reject all suggestions, press <kbd>Esc</kbd>.
+1. あるいは、すべての提案を拒否するには<kbd>Esc</kbd>を押してください。
diff --git a/translations/ja-JP/data/reusables/copilot/save-settings.md b/translations/ja-JP/data/reusables/copilot/save-settings.md
index 9bfed3a0d8..6adfe4cb16 100644
--- a/translations/ja-JP/data/reusables/copilot/save-settings.md
+++ b/translations/ja-JP/data/reusables/copilot/save-settings.md
@@ -1 +1 @@
-1. To confirm your new settings, click **Save**.
+1. 新しい設定を決定するには**Save（保存）**をクリックしてください。
diff --git a/translations/ja-JP/data/reusables/copilot/see-alternative-suggestions.md b/translations/ja-JP/data/reusables/copilot/see-alternative-suggestions.md
index 4e39f7b40b..efe53a231d 100644
--- a/translations/ja-JP/data/reusables/copilot/see-alternative-suggestions.md
+++ b/translations/ja-JP/data/reusables/copilot/see-alternative-suggestions.md
@@ -1 +1 @@
-1. Optionally, you can see alternative suggestions, if any are available.
+1. あるいは、代替提案が利用できる場合は、それらを見ることができます。
diff --git a/translations/ja-JP/data/reusables/copilot/signup-procedure.md b/translations/ja-JP/data/reusables/copilot/signup-procedure.md
index 139ac25221..7ecea862a5 100644
--- a/translations/ja-JP/data/reusables/copilot/signup-procedure.md
+++ b/translations/ja-JP/data/reusables/copilot/signup-procedure.md
@@ -1,17 +1,17 @@
 {% data variables.product.prodname_copilot %}を使い始めるには、無料の試用もしくはプランのセットアップが必要です。
 
 {% data reusables.user-settings.access_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-label="The copilot icon" %} GitHub Copilot**.
-1. On the {% data variables.product.prodname_copilot %} settings page, click **Enable {% data variables.product.prodname_copilot %}**.
+1. サイドバーの"Code, planning, and automation（コード、計画、自動化）"のセクションで、**{% octicon "copilot" aria-label="The copilot icon" %} GitHub Copilot**をクリックしてください。
+1. {% data variables.product.prodname_copilot %}の設定ページで**Enable {% data variables.product.prodname_copilot %}**をクリックしてください。
 
-   ![Screenshot of GitHub Copilot settings with Enable {% data variables.product.prodname_copilot %} button emphasized](/assets/images/help/copilot/copilot-settings-enable-button.png)
+   ![{% data variables.product.prodname_copilot %}の有効化ボタンが強調されたGitHub Copilotの設定のスクリーンショット](/assets/images/help/copilot/copilot-settings-enable-button.png)
 1. 支払いを月次でするか年次でするかを選択し、 **Continue to get access to Copilot（Copilotへのアクセスを継続）**をクリックしてください。
-   - If your personal account meets the criteria for a free {% data variables.product.prodname_copilot %} subscription instead of a trial, you will automatically be taken to step 6.
+   - 個人アカウントがトライアルの代わりに無料の{% data variables.product.prodname_copilot %}分の基準を満たしている場合、自動的にステップ6に進みます。
 
    ![Copilotへのアクセスを継続のボタンが強調された試用のセットアップのスクリーンショット](/assets/images/help/copilot/copilot-billing-cycle.png)
-1. Follow the steps to confirm your payment details, then click **Submit**.
+1. 手順にしたがって支払いの詳細を確認し、**Submit（サブミット）**をクリックしてください。
 1. 設定を選択し、**Save and get started（保存して使用を開始）**をクリックしてください。
 
-   ![Screenshot of GitHub Copilot settings with Save and get started button](/assets/images/help/copilot/copilot-signup-preferences.png)
+   ![保存と開始ボタンがあるGitHub Copilotの設定のスクリーンショット](/assets/images/help/copilot/copilot-signup-preferences.png)
 
-   You can change these preferences at a later time by returning to your {% data variables.product.prodname_copilot %} settings. For more information, see "[Configuring GitHub Copilot in Visual Studio Code](/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code#configuring-github-copilot-settings-on-githubcom)."
+   これらの設定は、{% data variables.product.prodname_copilot %}の設定に戻れば後ほど変更できます。 詳しい情報については「[Visual Studio CodeでのGitHub Copilotの設定](/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code#configuring-github-copilot-settings-on-githubcom)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/copilot/suggestions-new-tab.md b/translations/ja-JP/data/reusables/copilot/suggestions-new-tab.md
index 7f89c6b13f..4a4375ed2e 100644
--- a/translations/ja-JP/data/reusables/copilot/suggestions-new-tab.md
+++ b/translations/ja-JP/data/reusables/copilot/suggestions-new-tab.md
@@ -1 +1 @@
-You may not want any of the initial suggestions {% data variables.product.prodname_copilot %} offers. You can use a keyboard shortcut to prompt {% data variables.product.prodname_copilot %} to show you multiple suggestions in a new tab.
+{% data variables.product.prodname_copilot %}による最初の提案は受け入れられないかもしれません。 キーボードショートカットを使って、{% data variables.product.prodname_copilot %}に複数の提案を新しいタブに表示させるようにすることができます。
diff --git a/translations/ja-JP/data/reusables/copilot/supported-languages.md b/translations/ja-JP/data/reusables/copilot/supported-languages.md
index 3568cc314a..ed51adfa44 100644
--- a/translations/ja-JP/data/reusables/copilot/supported-languages.md
+++ b/translations/ja-JP/data/reusables/copilot/supported-languages.md
@@ -1 +1 @@
-{% data variables.product.prodname_copilot %} provides suggestions for numerous languages and a wide variety of frameworks, but works especially well for Python, JavaScript, TypeScript, Ruby, Go, C# and C++.
+{% data variables.product.prodname_copilot %}は多くの言語と幅広いフレームワークに対して提案を行いますが、特にPython、JavaScript、TypeScript、Ruby、Go、C#、C++でうまく機能します。
diff --git a/translations/ja-JP/data/reusables/copilot/type-function-header-c.md b/translations/ja-JP/data/reusables/copilot/type-function-header-c.md
index 5e8a63d0f4..be413b54a9 100644
--- a/translations/ja-JP/data/reusables/copilot/type-function-header-c.md
+++ b/translations/ja-JP/data/reusables/copilot/type-function-header-c.md
@@ -1,4 +1,4 @@
-1. In the C# file, type the following function header.
+1. C#のファイルで、以下の関数ヘッダを入力してください。
 
     ```csharp{:copy}
     function calculateDaysBetweenDates(begin, end) {
diff --git a/translations/ja-JP/data/reusables/copilot/windows-linux-next-suggestion.md b/translations/ja-JP/data/reusables/copilot/windows-linux-next-suggestion.md
index b4eb718d8f..48e4125fa2 100644
--- a/translations/ja-JP/data/reusables/copilot/windows-linux-next-suggestion.md
+++ b/translations/ja-JP/data/reusables/copilot/windows-linux-next-suggestion.md
@@ -1 +1 @@
-- On Windows or Linux, press <kbd>Alt</kbd>+<kbd>]</kbd> for the next suggestion, or <kbd>Alt</kbd>+<kbd>[</kbd> for the previous suggestion.
+- WindowsまたはLinuxでは、<kbd>Alt</kbd>+<kbd>]</kbd>を押せば次の提案に、<kbd>Alt</kbd>+<kbd>[</kbd>を押せば前の提案に移ります。
diff --git a/translations/ja-JP/data/reusables/dependabot/about-the-dependency-graph.md b/translations/ja-JP/data/reusables/dependabot/about-the-dependency-graph.md
index 2f18d3737b..571842fb79 100644
--- a/translations/ja-JP/data/reusables/dependabot/about-the-dependency-graph.md
+++ b/translations/ja-JP/data/reusables/dependabot/about-the-dependency-graph.md
@@ -1,4 +1,4 @@
-The dependency graph is a summary of the manifest and lock files stored in a repository{% ifversion dependency-submission-api %} and any dependencies that are submitted for the repository using the Dependency submission API (beta){% endif %}. それぞれのリポジトリにおいて、依存関係グラフは以下を表示します。{% ifversion fpt or ghec %}
+依存関係グラフは、リポジトリに保存されているマニフェスト及びロックファイル{% ifversion dependency-submission-api %}及びDependency submission API（ベータ）を使ってリポジトリにサブミットされた依存関係{% endif %}のまとめです。 それぞれのリポジトリにおいて、依存関係グラフは以下を表示します。{% ifversion fpt or ghec %}
 
 - リポジトリが依存している依存関係、エコシステム、パッケージ
 - リポジトリに依存する対象、リポジトリ、パッケージ{% else %}依存関係、すなわちリポジトリが依存するエコシステムとパッケージ。 {% data variables.product.product_name %}は、リポジトリに依存する対象、リポジトリ、パッケージに関する情報を計算しません。{% endif %}
diff --git a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md
index f50ef78f03..0e6b435b8f 100644
--- a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md
+++ b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md
@@ -2,7 +2,7 @@
 
 {% note %}
 
-**Note:** Dependabot security updates and version updates are currently available for {% data variables.product.prodname_ghe_cloud %} and in beta for {% data variables.product.prodname_ghe_server %} 3.3. Please [contact your account management team](https://enterprise.github.com/contact) for instructions on enabling Dependabot updates.
+**ノート:** Dependabotのセキュリティアップデート及びバージョンアップデートは、現在{% data variables.product.prodname_ghe_cloud %}で利用可能であり、{% data variables.product.prodname_ghe_server %} 3.3でベータです。 Dependabotアップデートの有効化の手順については[営業チームに連絡](https://enterprise.github.com/contact)してください。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md
index 948349fcb4..81c29fbb0c 100644
--- a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md
+++ b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md
@@ -2,9 +2,9 @@
 
 {% note %}
 {% ifversion ghes = 3.4 %}
-**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in public beta and subject to change.
+**ノート:** {% data variables.product.prodname_dependabot %}セキュリティ及びバージョンアップデートは現在パブリックベータであり、変更されることがあります。
 {% else %}
-**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in private beta and subject to change. Please [contact your account management team](https://enterprise.github.com/contact) for instructions on enabling Dependabot updates.
+**ノート:** {% data variables.product.prodname_dependabot %}セキュリティ及びバージョンアップデートは現在プライベートベータであり、変更されることがあります。 Dependabotアップデートの有効化の手順については[営業チームに連絡](https://enterprise.github.com/contact)してください。
 {% endif %}
 
 {% endnote %}
@@ -15,7 +15,7 @@
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in public beta and subject to change.
+**ノート:** {% data variables.product.prodname_dependabot %}セキュリティ及びバージョンアップデートは現在パブリックベータであり、変更されることがあります。
 
 {% endnote %}
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/dependabot/configuration-options.md b/translations/ja-JP/data/reusables/dependabot/configuration-options.md
index 9ab6ec3a2f..5753ce531d 100644
--- a/translations/ja-JP/data/reusables/dependabot/configuration-options.md
+++ b/translations/ja-JP/data/reusables/dependabot/configuration-options.md
@@ -1,25 +1,25 @@
-| オプション                                                                                                                                                                            |  必須   | Security Updates | Version Updates | 説明                                                                      |
-|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:----------------:|:---------------:|:----------------------------------------------------------------------- |
-| [`package-ecosystem`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem)                                  | **X** |                  |        X        | 使用するパッケージマネージャー                                                         |
-| [`directory`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#directory)                                                  | **X** |                  |        X        | パッケージマニフェストの場所                                                          |
-| [`schedule.interval`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleinterval)                                   | **X** |                  |        X        | 更新を確認する頻度                                                               |
-| [`allow`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#allow)                                                          |       |        X         |        X        | 許可する更新をカスタマイズする                                                         |
-| [`assignees`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#assignees)                                                  |       |        X         |        X        | プルリクエストのアサイン担当者                                                         |
-| [`commit-message`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#commit-message)                                        |       |        X         |        X        | コミットメッセージの設定                 |{% ifversion fpt or ghec or ghes > 3.4 %}
-| [`enable-beta-ecosystems`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#enable-beta-ecosystems)                        |       |                  |        X        | ベータレベルのサポートがあるエコシステムを有効にする 
+| オプション                                                                                                                                                                            |  必須   | セキュリティアップデート | バージョンアップデート | 説明                                                                      |
+|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------------:|:-----------:|:----------------------------------------------------------------------- |
+| [`package-ecosystem`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem)                                  | **X** |              |      X      | 使用するパッケージマネージャー                                                         |
+| [`directory`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#directory)                                                  | **X** |              |      X      | パッケージマニフェストの場所                                                          |
+| [`schedule.interval`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleinterval)                                   | **X** |              |      X      | 更新を確認する頻度                                                               |
+| [`allow`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#allow)                                                          |       |      X       |      X      | 許可する更新をカスタマイズする                                                         |
+| [`assignees`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#assignees)                                                  |       |      X       |      X      | プルリクエストのアサイン担当者                                                         |
+| [`commit-message`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#commit-message)                                        |       |      X       |      X      | コミットメッセージの設定                 |{% ifversion fpt or ghec or ghes > 3.4 %}
+| [`enable-beta-ecosystems`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#enable-beta-ecosystems)                        |       |              |      X      | ベータレベルのサポートがあるエコシステムを有効にする 
 {% endif %}
-| [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)                                                        |       |        X         |        X        | 特定の依存関係またはバージョンを無視する                                                    |
-| [`insecure-external-code-execution`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#insecure-external-code-execution)    |       |                  |        X        | マニフェストファイル内でコードの実行を許可または拒否する                                            |
-| [`labels`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#labels)                                                        |       |        X         |        X        | プルリクエストに設定するラベル                                                         |
-| [`マイルストーン`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#milestone)                                                    |       |        X         |        X        | プルリクエストに設定するマイルストーン                                                     |
-| [`open-pull-requests-limit`](#open-pull-requests-limit)                                                                                                                          |       |        X         |        X        | バージョン更新時のオープンなプルリクエスト数を制限する                                             |
-| [`pull-request-branch-name.separator`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#pull-request-branch-nameseparator) |       |        X         |        X        | プルリクエストブランチ名の区切り文字を変更する                                                 |
-| [`rebase-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#rebase-strategy)                                      |       |        X         |        X        | 自動リベースを無効にする                                                            |
-| [`registries`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#registries)                                                |       |                  |        X        | {% data variables.product.prodname_dependabot %} がアクセスできるプライベートリポジトリ    |
-| [`レビュー担当者`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#reviewers)                                                    |       |        X         |        X        | プルリクエストのレビュー担当者                                                         |
-| [`schedule.day`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleday)                                             |       |                  |        X        | 更新を確認する曜日                                                               |
-| [`schedule.time`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletime)                                           |       |                  |        X        | 更新を確認する時刻 (hh:mm)                                                       |
-| [`schedule.timezone`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletimezone)                                   |       |                  |        X        | 時刻のタイムゾーン（ゾーン識別子）                                                       |
-| [`target-branch`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#target-branch)                                          |       |                  |        X        | プルリクエストを作成するブランチ                                                        |
-| [`vendor`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#vendor)                                                        |       |                  |        X        | ベンダーまたはキャッシュされた依存関係を更新する                                                |
-| [`versioning-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#versioning-strategy)                              |       |        X         |        X        | マニフェストのバージョン要件の更新方法                                                     |
+| [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)                                                        |       |      X       |      X      | 特定の依存関係またはバージョンを無視する                                                    |
+| [`insecure-external-code-execution`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#insecure-external-code-execution)    |       |              |      X      | マニフェストファイル内でコードの実行を許可または拒否する                                            |
+| [`labels`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#labels)                                                        |       |      X       |      X      | プルリクエストに設定するラベル                                                         |
+| [`マイルストーン`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#milestone)                                                    |       |      X       |      X      | プルリクエストに設定するマイルストーン                                                     |
+| [`open-pull-requests-limit`](#open-pull-requests-limit)                                                                                                                          |       |      X       |      X      | バージョン更新時のオープンなプルリクエスト数を制限する                                             |
+| [`pull-request-branch-name.separator`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#pull-request-branch-nameseparator) |       |      X       |      X      | プルリクエストブランチ名の区切り文字を変更する                                                 |
+| [`rebase-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#rebase-strategy)                                      |       |      X       |      X      | 自動リベースを無効にする                                                            |
+| [`registries`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#registries)                                                |       |              |      X      | {% data variables.product.prodname_dependabot %} がアクセスできるプライベートリポジトリ    |
+| [`レビュー担当者`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#reviewers)                                                    |       |      X       |      X      | プルリクエストのレビュー担当者                                                         |
+| [`schedule.day`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleday)                                             |       |              |      X      | 更新を確認する曜日                                                               |
+| [`schedule.time`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletime)                                           |       |              |      X      | 更新を確認する時刻 (hh:mm)                                                       |
+| [`schedule.timezone`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletimezone)                                   |       |              |      X      | 時刻のタイムゾーン（ゾーン識別子）                                                       |
+| [`target-branch`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#target-branch)                                          |       |              |      X      | プルリクエストを作成するブランチ                                                        |
+| [`vendor`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#vendor)                                                        |       |              |      X      | ベンダーまたはキャッシュされた依存関係を更新する                                                |
+| [`versioning-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#versioning-strategy)                              |       |      X       |      X      | マニフェストのバージョン要件の更新方法                                                     |
diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md
index c2bfc45615..2c5c4d6883 100644
--- a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md
+++ b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md
@@ -1,7 +1,7 @@
 {% ifversion ghae %}
 {% note %}
 
-**Note:** {% data variables.product.prodname_dependabot_alerts %} is currently in beta and is subject to change.
+**ノート:** {% data variables.product.prodname_dependabot_alerts %}は現在ベータであり、変更されることがあります。
 
 {% endnote %}
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
index 367cbb25f8..6010e6221c 100644
--- a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
+++ b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
@@ -1,3 +1,3 @@
 {% ifversion ghes or ghae %}
-Enterprise owners can configure {% ifversion ghes %}the dependency graph and {% endif %}{% data variables.product.prodname_dependabot_alerts %} for an enterprise. 詳しい情報については{% ifversion ghes %}「[Enterpriseでの依存関係グラフの有効化](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)」及び{% endif %}「[Enterpriseでの{% data variables.product.prodname_dependabot %}の有効化](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)」を参照してください。
+Enterpriseのオーナーは、{% ifversion ghes %}依存関係グラフと{% endif %}{% data variables.product.prodname_dependabot_alerts %}をEnterpriseで設定できます。 詳しい情報については{% ifversion ghes %}「[Enterpriseでの依存関係グラフの有効化](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)」及び{% endif %}「[Enterpriseでの{% data variables.product.prodname_dependabot %}の有効化](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)」を参照してください。
 {% endif %} 
diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-scope.md b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-scope.md
index b7461e93c5..6716e3b0ad 100644
--- a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-scope.md
+++ b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-scope.md
@@ -1,13 +1,13 @@
-The table below summarizes whether dependency scope is supported for various ecosystems and manifests, that is, whether {% data variables.product.prodname_dependabot %} can identify if a dependency is used for development or production.
+以下の表は、依存関係のスコープが様々なエコシステム及びマニフェストでサポートされているか、すなわち{% data variables.product.prodname_dependabot %}が依存関係が開発もしくは実働で利用されているかを特定できるかをまとめたものです。
 
-| **言語**                  |   **エコシステム**   |          **Manifest file**           | **Dependency scope supported**                                                      |
+| **言語**                  |   **エコシステム**   |            **マニフェストファイル**            | **依存関係スコープがサポートされているか**                                                             |
 |:----------------------- |:--------------:|:------------------------------------:|:----------------------------------------------------------------------------------- |
-| Go                      |    Goモジュール     |                go.mod                | No, defaults to runtime                                                             |
-| Go                      |    Goモジュール     |                go.sum                | No, defaults to runtime                                                             |
-| Java                    |     Maven      |               pom.xml                | ✔ `test` maps to development, else scope defaults to runtime                        |
+| Go                      |    Goモジュール     |                go.mod                | いいえ。デフォルトはランタイム                                                                     |
+| Go                      |    Goモジュール     |                go.sum                | いいえ。デフォルトはランタイム                                                                     |
+| Java                    |     Maven      |               pom.xml                | ✔ `test`は開発にマップされ、そうでなければスコープはデフォルトでランタイム                                           |
 | JavaScript              |      npm       |             package.json             | ✔                                                                                   |
 | JavaScript              |      npm       |          package-lock.json           | ✔                                                                                   |
-| JavaScript              |    yarn v1     |              yarn.lock               | No, defaults to runtime                                                             |
+| JavaScript              |    yarn v1     |              yarn.lock               | いいえ。デフォルトはランタイム                                                                     |
 | PHP                     |    Composer    |            composer.json             | ✔                                                                                   |
 | PHP                     |    Composer    |            composer.lock             | ✔                                                                                   |
 | Python                  |     Poetry     |             poetry.lock              | ✔                                                                                   |
@@ -16,10 +16,10 @@ The table below summarizes whether dependency scope is supported for various eco
 | Python                  |      pip       |             pipfile.lock             | ✔                                                                                   |
 | Python                  |      pip       |               pipfile                | ✔                                                                                   |
 | Ruby                    |    RubyGems    |               Gemfile                | ✔                                                                                   |
-| Ruby                    |    RubyGems    |             Gemfile.lock             | No, defaults to runtime                                                             |
+| Ruby                    |    RubyGems    |             Gemfile.lock             | いいえ。デフォルトはランタイム                                                                     |
 | Rust                    |     Cargo      |              Cargo.toml              | ✔                                                                                   |
-| Rust                    |     Cargo      |              Cargo.lock              | No, defaults to runtime                                                             |
-| YAML                    | GitHub Actions |                  -                   | No, defaults to runtime                                                             |
-| .NET (C#, F#, VB, etc.) |     NuGet      | .csproj / .vbproj .vcxproj / .fsproj | No, defaults to runtime                                                             |
-| .NET                    |     NuGet      |           packages.config            | No, defaults to runtime                                                             |
+| Rust                    |     Cargo      |              Cargo.lock              | いいえ。デフォルトはランタイム                                                                     |
+| YAML                    | GitHub Actions |                  -                   | いいえ。デフォルトはランタイム                                                                     |
+| .NET (C#, F#, VB, etc.) |     NuGet      | .csproj / .vbproj .vcxproj / .fsproj | いいえ。デフォルトはランタイム                                                                     |
+| .NET                    |     NuGet      |           packages.config            | いいえ。デフォルトはランタイム                                                                     |
 | .NET                    |     NuGet      |               .nuspec                | ✔ When the tag != runtime                                                           |
diff --git a/translations/ja-JP/data/reusables/discussions/about-organization-discussions.md b/translations/ja-JP/data/reusables/discussions/about-organization-discussions.md
index c9964a9b33..08628cb121 100644
--- a/translations/ja-JP/data/reusables/discussions/about-organization-discussions.md
+++ b/translations/ja-JP/data/reusables/discussions/about-organization-discussions.md
@@ -1,5 +1,5 @@
 When you enable organization discussions, you will choose a repository in the organization to be the source repository for your organization discussions. You can use an existing repository or create a repository specifically to hold your organization discussions. Discussions will appear both on the discussions page for the organization and on the discussion page for the source repository.
 
-Permission to participate in or manage discussion in your organization is based on permission in the source repository. For example, a user needs write permission to the source repository in order to delete an organization discussion. This is identical to how a user needs write permission in a repository in order to delete a repository discussion.
+Permission to participate in or manage discussions in your organization is based on permission in the source repository. For example, a user needs write permission to the source repository in order to delete an organization discussion. This is identical to how a user needs write permission in a repository in order to delete a repository discussion.
 
 You can change the source repository at any time. If you change the source repository, discussions are not transferred to the new source repository.
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/packages-tab.md b/translations/ja-JP/data/reusables/enterprise-accounts/packages-tab.md
new file mode 100644
index 0000000000..e5656496c5
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/packages-tab.md
@@ -0,0 +1 @@
+1. 左のサイドバーで**Packages**をクリックしてください。
diff --git a/translations/ja-JP/data/reusables/enterprise/about-ssh-ports.md b/translations/ja-JP/data/reusables/enterprise/about-ssh-ports.md
new file mode 100644
index 0000000000..f7cba5e6b2
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise/about-ssh-ports.md
@@ -0,0 +1,5 @@
+Each {% data variables.product.product_name %} instance accepts SSH connections over two ports. Site administrators can access the administrative shell via SSH, then run command-line utilities, troubleshoot, and perform maintenance. Users can connect via SSH to access and write Git data in the instance's repositories. Users do not have shell access to your instance. 詳しい情報については、次の記事を参照してください。
+
+- "[Network ports](/admin/configuration/configuring-network-settings/network-ports)"
+- "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)"
+- 「[SSHについて](/authentication/connecting-to-github-with-ssh/about-ssh)」
diff --git a/translations/ja-JP/data/reusables/enterprise/apply-configuration.md b/translations/ja-JP/data/reusables/enterprise/apply-configuration.md
new file mode 100644
index 0000000000..b436efa0a1
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise/apply-configuration.md
@@ -0,0 +1,12 @@
+1. To apply the configuration, enter the following command.
+
+   {% note %}
+
+   **Note**: During a configuration run, services on {% data variables.product.product_location %} may restart, which can cause brief downtime for users.
+
+   {% endnote %}
+
+    ```shell
+    ghe-config-apply
+    ```
+1. 設定が完了するのを待ってください。
diff --git a/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md b/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md
index a6035dfd4f..33783192a4 100644
--- a/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md
+++ b/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md
@@ -1,5 +1,7 @@
+{% ifversion ghes < 3.6 %}
 {% note %}
 
 **Note:** Repository caching is currently in beta and subject to change.
 
 {% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md
index 1811645d3b..2878e9c49b 100644
--- a/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md
+++ b/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md
@@ -1,4 +1,5 @@
-1. {% data variables.product.product_location %}にSSHでアクセスしてください。 詳しい情報については「[管理シェル（SSH）にアクセスする](/admin/configuration/accessing-the-administrative-shell-ssh)」を参照してください。
-```shell
-$ ssh -p 122 admin@<em>HOSTNAME</em>
-```
+1. {% data variables.product.product_location %}にSSHでアクセスしてください。 If your instance comprises multiple nodes, for example if high availability or geo-replication are configured, SSH into the primary node. If you use a cluster, you can SSH into any node. For more information about SSH access, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+
+   ```shell
+   $ ssh -p 122 admin@<em>HOSTNAME</em>
+   ```
diff --git a/translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md b/translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
index e989e63cdf..a11b1fb4f4 100644
--- a/translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
+++ b/translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
@@ -1,5 +1,9 @@
 {% warning %}
 
-**ノート:** 匿名Gitアクセスを有効にする場合、この機能のすべてのアクセスと利用に責任を負うことになります。 {% data variables.product.company_short %}は、この機能のあらゆる意図しないアクセスや悪用に対して責任を負いません。 また、弊社から購入したユーザライセンス数の制限を含む{% data variables.product.company_short %}のライセンスに違反するためにこの機能を使うことはできません。
+**警告:**
+
+- The Git protocol is unauthenticated and unencrypted. An attacker could intercept repository data transferred over connections using this protocol.
+- If you enable anonymous Git read access, you're responsible for all access and use of the feature. {% data variables.product.company_short %} is not responsible for any unintended access, security risks, or misuse of the feature.
+- You may not use this feature to violate your license from {% data variables.product.company_short %}, including the limit on the number of user licenses for {% data variables.product.product_location %}.
 
 {% endwarning %}
diff --git a/translations/ja-JP/data/reusables/gated-features/copilot.md b/translations/ja-JP/data/reusables/gated-features/copilot.md
index 0a9cd66858..f3dcf72768 100644
--- a/translations/ja-JP/data/reusables/gated-features/copilot.md
+++ b/translations/ja-JP/data/reusables/gated-features/copilot.md
@@ -1 +1 @@
-{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_copilot %} is free to use for verified students and open source maintainers. If you are not a student or open source maintainer, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. 詳しい情報については、「[{% data variables.product.prodname_copilot %}の支払いについて](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)」を参照してください。
+{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_copilot %}は、検証済みの学生やオープンソースのメンテナなら無料で使用できます。 学生やオープンソースのメンテナではない人は、1回60日のトライアルで{% data variables.product.prodname_copilot %}を無料で試すことができます。 無料のトライアルが終わったあと、継続して使うには有料プランが必要になります。 詳しい情報については、「[{% data variables.product.prodname_copilot %}の支払いについて](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/gated-features/discussions.md b/translations/ja-JP/data/reusables/gated-features/discussions.md
deleted file mode 100644
index 65d9afd325..0000000000
--- a/translations/ja-JP/data/reusables/gated-features/discussions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_discussions %} is available for public and private repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %}
diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-benefits.md b/translations/ja-JP/data/reusables/package_registry/container-registry-benefits.md
new file mode 100644
index 0000000000..079a514846
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/container-registry-benefits.md
@@ -0,0 +1 @@
+The {% data variables.product.prodname_container_registry %} stores container images within your organization or personal account, and allows you to associate an image with a repository. You can choose whether to inherit permissions from a repository, or set granular permissions independently of a repository. You can also access public container images anonymously.
diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md b/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md
new file mode 100644
index 0000000000..5d685d5f4f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md
@@ -0,0 +1 @@
+{% data variables.product.product_name %} 3.6 supports migration for Docker images stored in organizations. A future release will support migration of user-owned images.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-migration-namespaces.md b/translations/ja-JP/data/reusables/package_registry/container-registry-migration-namespaces.md
new file mode 100644
index 0000000000..9d7d0dc5e0
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/container-registry-migration-namespaces.md
@@ -0,0 +1 @@
+Any scripts or {% data variables.product.prodname_actions %} workflows that use the namespace for the Docker registry, {% data variables.product.prodname_docker_registry_namespace %}, will continue to work after migration to the {% data variables.product.prodname_container_registry %} at {% data variables.product.prodname_container_registry_namespace %}.
diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-replaces-docker-registry.md b/translations/ja-JP/data/reusables/package_registry/container-registry-replaces-docker-registry.md
new file mode 100644
index 0000000000..5b6ed35c4f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/container-registry-replaces-docker-registry.md
@@ -0,0 +1 @@
+The {% data variables.product.prodname_container_registry %} replaces {% data variables.product.company_short %}'s Docker registry.
diff --git a/translations/ja-JP/data/reusables/package_registry/verify_repository_field.md b/translations/ja-JP/data/reusables/package_registry/verify_repository_field.md
index b276a52455..a698129aaa 100644
--- a/translations/ja-JP/data/reusables/package_registry/verify_repository_field.md
+++ b/translations/ja-JP/data/reusables/package_registry/verify_repository_field.md
@@ -1 +1 @@
-1. プロジェクトの*package.json*中の`repository`フィールドを検証してください。 `repository`フィールドは、{% data variables.product.prodname_dotcom %}リポジトリのURLと一致していなければなりません。 たとえば、あなたのリポジトリのURLが`github.com/my-org/test`なら、repositoryフィールドは`git://github.com/my-org/test.git`でなければなりません。
+1. プロジェクトの*package.json*中の`repository`フィールドを検証してください。 `repository`フィールドは、{% data variables.product.prodname_dotcom %}リポジトリのURLと一致していなければなりません。 For example, if your repository URL is `github.com/my-org/test` then the repository field should be `https://github.com/my-org/test.git`.
diff --git a/translations/ja-JP/data/reusables/repositories/commit-signoffs.md b/translations/ja-JP/data/reusables/repositories/commit-signoffs.md
new file mode 100644
index 0000000000..1de17f89af
--- /dev/null
+++ b/translations/ja-JP/data/reusables/repositories/commit-signoffs.md
@@ -0,0 +1,10 @@
+Compulsory commit signoffs only apply to commits made via the web interface. For commits made via the Git command line interface, the commit author must sign off on the commit using the `--signoff` option. For more information, see the [Git documentation](https://git-scm.com/docs/git-commit).
+
+
+You can determine whether a repository you are contributing to has compulsory commit signoffs enabled by checking the header of the commit form at the bottom of the file you are editing. After compulsory commit signoff has been enabled, the header will read "Sign off and commit changes."
+
+![Screenshot of commit commit form with compulsory signoff enabled](/assets/images/help/commits/commit-form-with-signoff-enabled.png)
+
+Before signing off on a commit, you should ensure that your commit is in compliance with the rules and licensing governing the repository you're committing to. The repository may use a sign off agreement, such as the Developer Certificate of Origin from the Linux Foundation. For more information, see the [Developer Certificate of Origin](https://developercertificate.org/).
+
+Signing off on a commit differs from signing a commit. For more information about signing a commit, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md
index 7a23691721..c2dc16ef62 100644
--- a/translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md
+++ b/translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -1,5 +1 @@
-{% ifversion fpt or ghec %}
-For more information, see "[Browsing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)."
-{% else %}
-For more information about advisory data, see "[Browsing security advisories in the {% data variables.product.prodname_advisory_database %}](/free-pro-team@latest/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the {% data variables.product.prodname_dotcom_the_website %} documentation.
-{% endif %}
+詳しい情報については、「[{% data variables.product.prodname_advisory_database %} のセキュリティアドバイザリを参照する](/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/server-statistics/release-phase.md b/translations/ja-JP/data/reusables/server-statistics/release-phase.md
deleted file mode 100644
index 17f100fd26..0000000000
--- a/translations/ja-JP/data/reusables/server-statistics/release-phase.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note:** {% data variables.product.prodname_server_statistics %} is in public beta and subject to change.
-
-{% endnote %}
diff --git a/translations/ja-JP/data/reusables/ssh/about-ssh.md b/translations/ja-JP/data/reusables/ssh/about-ssh.md
new file mode 100644
index 0000000000..b4c0c5361a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/ssh/about-ssh.md
@@ -0,0 +1 @@
+You can access and write data in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} using SSH (Secure Shell Protocol). When you connect via SSH, you authenticate using a private key file on your local machine.
diff --git a/translations/ja-JP/data/reusables/ssh/key-type-support.md b/translations/ja-JP/data/reusables/ssh/key-type-support.md
index f2a03a9ed5..85ace1b53c 100644
--- a/translations/ja-JP/data/reusables/ssh/key-type-support.md
+++ b/translations/ja-JP/data/reusables/ssh/key-type-support.md
@@ -8,4 +8,21 @@ As of that date, DSA keys (`ssh-dss`) are no longer supported. You cannot add ne
 RSA keys (`ssh-rsa`) with a `valid_after` before November 2, 2021 may continue to use any signature algorithm. RSA keys generated after that date must use a SHA-2 signature algorithm. Some older clients may need to be upgraded in order to use SHA-2 signatures.
 
 {% endnote %}
-{% endif %}
+
+{% elsif ghes = 3.6 or ghes = 3.7 or ghes = 3.8 %}
+
+{% note %}
+
+**Note**: By default with {% data variables.product.product_name %} 3.6 and later, as of the cutoff date of midnight UTC on August 1, 2022, SSH connections that satisfy **both** of the following conditions will fail.
+
+<br/>
+
+{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %}
+
+{% data variables.product.product_name %} 3.6 and later also does not support SSH connections that use DSA, HMAC-SHA-1, or CBC ciphers. RSA SSH keys uploaded before the cutoff date can continue to authenticate using the SHA-1 hash function as long as the key remains valid. For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
+
+Your site administrator can adjust the cutoff date for connections using RSA-SHA-1, and may block all connections using RSA-SHA-1. For more information, contact your site administrator or see "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md b/translations/ja-JP/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md
new file mode 100644
index 0000000000..d2c95da8a5
--- /dev/null
+++ b/translations/ja-JP/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md
@@ -0,0 +1,2 @@
+- The RSA key was added to a user account on {% data variables.product.product_location %} after the cutoff date of midnight UTC on August 1, 2022.
+- The SSH client signs the connection attempt with the SHA-1 hash function.
diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml
index 698b07d89a..84da4d68e8 100644
--- a/translations/ja-JP/data/ui.yml
+++ b/translations/ja-JP/data/ui.yml
@@ -179,7 +179,7 @@ product_landing:
   try_another: 他のフィルタを試すか、あなたのコードサンプルを追加してください。
   no_result: 申し訳ありませんが、指定されたフィルタにマッチするガイドはありません。
   learn: コードサンプルの追加方法を学ぶ
-  communities_using_discussions: ディスカッションを使用しているコミュニティ
+  communities_using_discussions: Communities on GitHub.com using discussions
   add_your_community: コミュニティを追加する
   sponsor_community: GitHub Sponsorsコミュニティ
   supported_releases: サポートされているリリース
diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml
index 4379a0d442..512d0a26c3 100644
--- a/translations/ja-JP/data/variables/product.yml
+++ b/translations/ja-JP/data/variables/product.yml
@@ -100,6 +100,8 @@ prodname_github_issues: 'GitHubのIssue'
 #GitHub Packages
 prodname_registry: 'GitHub Packages'
 prodname_container_registry: 'コンテナレジストリ'
+prodname_docker_registry_namespace: '{% ifversion fpt or ghec %}`docker.pkg.github.com`{% elsif ghes or ghae %}<code>docker.<em>HOSTNAME</em></code>{% endif %}'
+prodname_container_registry_namespace: '{% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes or ghae %}<code>containers.<em>HOSTNAME</em></code>{% endif %}'
 #GitHub Insights
 prodname_insights: 'GitHub Insights'
 #GitHub Sponsors
diff --git a/translations/ja-JP/data/variables/release_candidate.yml b/translations/ja-JP/data/variables/release_candidate.yml
index ec65ef6f94..d39e7c0f8d 100644
--- a/translations/ja-JP/data/variables/release_candidate.yml
+++ b/translations/ja-JP/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
 ---
-version: ''
+version: enterprise-server@3.6
diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv
index b77721c7ae..571b7f4b34 100644
--- a/translations/log/cn-resets.csv
+++ b/translations/log/cn-resets.csv
@@ -112,7 +112,6 @@ translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your
 translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,broken liquid tags
 translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md,broken liquid tags
 translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,broken liquid tags
-translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,broken liquid tags
 translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,broken liquid tags
 translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md,broken liquid tags
 translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,broken liquid tags
@@ -160,7 +159,6 @@ translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scannin
 translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
 translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
 translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,rendering error
-translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,broken liquid tags
 translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md,broken liquid tags
 translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,broken liquid tags
 translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md,broken liquid tags
@@ -269,7 +267,6 @@ translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.m
 translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,broken liquid tags
 translations/zh-CN/content/packages/quickstart.md,broken liquid tags
 translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,broken liquid tags
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,broken liquid tags
 translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,broken liquid tags
 translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,broken liquid tags
 translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,broken liquid tags
@@ -386,7 +383,7 @@ translations/zh-CN/data/reusables/enterprise_installation/hardware-consideration
 translations/zh-CN/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags
 translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,rendering error
 translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
-translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md,rendering error
+translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md,broken liquid tags
 translations/zh-CN/data/reusables/gated-features/packages.md,broken liquid tags
 translations/zh-CN/data/reusables/gated-features/secret-scanning-partner.md,broken liquid tags
 translations/zh-CN/data/reusables/gated-features/secret-scanning.md,broken liquid tags
@@ -415,7 +412,6 @@ translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,bro
 translations/zh-CN/data/reusables/scim/after-you-configure-saml.md,broken liquid tags
 translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
 translations/zh-CN/data/reusables/secret-scanning/partner-program-link.md,broken liquid tags
-translations/zh-CN/data/reusables/security-advisory/link-browsing-advisory-db.md,broken liquid tags
 translations/zh-CN/data/reusables/sponsors/feedback.md,broken liquid tags
 translations/zh-CN/data/reusables/support/enterprise-resolving-and-closing-tickets.md,broken liquid tags
 translations/zh-CN/data/reusables/support/free-and-paid-support.md,broken liquid tags
diff --git a/translations/log/es-resets.csv b/translations/log/es-resets.csv
index acc450c448..ef570bcea8 100644
--- a/translations/log/es-resets.csv
+++ b/translations/log/es-resets.csv
@@ -300,6 +300,7 @@ translations/es-ES/content/support/learning-about-github-support/about-github-pr
 translations/es-ES/content/support/learning-about-github-support/about-github-support.md,broken liquid tags
 translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml,broken liquid tags
 translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml,broken liquid tags
+translations/es-ES/data/release-notes/enterprise-server/3-6/0-rc1.yml,broken liquid tags
 translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml,broken liquid tags
 translations/es-ES/data/release-notes/github-ae/2022-05/2022-05-17.yml,broken liquid tags
 translations/es-ES/data/reusables/actions/contacting-support.md,broken liquid tags
diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv
index 38ba73cf86..7fe44f1a7a 100644
--- a/translations/log/ja-resets.csv
+++ b/translations/log/ja-resets.csv
@@ -111,7 +111,6 @@ translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scannin
 translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,broken liquid tags
 translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
 translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,broken liquid tags
-translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,broken liquid tags
 translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md,broken liquid tags
 translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,broken liquid tags
 translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md,broken liquid tags
@@ -281,10 +280,15 @@ translations/ja-JP/data/reusables/apps/user-to-server-rate-limits-ghec.md,broken
 translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md,broken liquid tags
 translations/ja-JP/data/reusables/billing/ghes-with-no-enterprise-account.md,broken liquid tags
 translations/ja-JP/data/reusables/classroom/classroom-codespaces-link.md,broken liquid tags
+translations/ja-JP/data/reusables/code-scanning/beta-alert-tracking-in-issues.md,broken liquid tags
 translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
 translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
+translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags
 translations/ja-JP/data/reusables/code-scanning/upload-sarif-ghas.md,broken liquid tags
 translations/ja-JP/data/reusables/community/report-content.md,broken liquid tags
+translations/ja-JP/data/reusables/copilot/dotcom-settings.md,broken liquid tags
+translations/ja-JP/data/reusables/copilot/enabling-or-disabling-in-vsc.md,broken liquid tags
+translations/ja-JP/data/reusables/copilot/enabling-or-disabling-vs.md,broken liquid tags
 translations/ja-JP/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md,broken liquid tags
 translations/ja-JP/data/reusables/dotcom_billing/downgrade-org-to-free.md,broken liquid tags
 translations/ja-JP/data/reusables/dotcom_billing/lfs-remove-data.md,broken liquid tags
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
index 4b35fff304..f7581cf998 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
@@ -1,7 +1,7 @@
 ---
 title: Gerenciando configurações de acessibilidade
-shortTitle: Manage accessibility settings
-intro: '{% data variables.product.product_name %}''s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs.'
+shortTitle: Gerenciar as configurações de acessibilidade
+intro: 'A interface de usuário de {% data variables.product.product_name %} pode se adaptar às suas necessidades de visão, audição, motoras, cognitivas ou de aprendizado.'
 versions:
   feature: keyboard-shortcut-accessibility-setting
 redirect_from:
@@ -12,39 +12,39 @@ miniTocMaxHeadingLevel: 3
 
 ## Sobre as configurações de acessibilidade
 
-To accommodate your vision, hearing, motor, cognitive, or learning needs, you can customize the user interface for {% data variables.product.product_location %}.
+Para acomodar as suas necessidades de visão, audição, motoras, cognitivas ou de aprendizado, você pode personalizar a interface de usuário para {% data variables.product.product_location %}.
 
 ## Gerenciando configurações de acessibilidade
 
-You can decide whether you want to use some or all keyboard shortcuts on {% ifversion fpt or ghec %}{% data variables.product.product_location %}{% elsif ghes or ghae %}the website for {% data variables.product.product_location %}{% endif %}, and you can control the display of animated images.
+Você pode decidir se deseja usar alguns ou todos os atalhos de teclado no {% ifversion fpt or ghec %}{% data variables.product.product_location %}{% elsif ghes or ghae %}site para {% data variables.product.product_location %}{% endif %}, e você pode controlar a exibição de imagens animadas.
 
-### Managing keyboard shortcuts
+### Gerenciando atalhos de teclado
 
-You can perform actions across the {% data variables.product.product_name %} website without using your mouse by using your keyboard instead. Keyboard shortcuts can be useful to save time for some people, but may interfere with accessibility if you don't intend to use the shortcuts.
+Você pode executar ações no site de {% data variables.product.product_name %} sem usar seu mouse e usando o teclado. Os atalhos do teclado podem ser úteis para economizar tempo para algumas pessoas, mas podem interferir com a acessibilidade se você não pretender usar os atalhos.
 
-By default, all keyboard shortcuts are enabled on {% data variables.product.product_name %}. Para obter mais informações, consulte "[Atalhos de teclado](/get-started/using-github/keyboard-shortcuts)".
+Por padrão, todos os atalhos de teclado estão habilitados em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Atalhos de teclado](/get-started/using-github/keyboard-shortcuts)".
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.accessibility_settings %}
-1. Under "Keyboard shortcuts", manage settings for your keyboard shortcuts.
+1. Em "atalhos de teclado", gerencie as configurações para seus atalhos de teclado.
 
-   - Optionally, to disable or enable shortcut keys that don't use modifiers keys like <kbd>Control</kbd> or <kbd>Command</kbd>, under "General", deselect **Character keys**. If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key.
+   - Opcionalmente, para desabilitar ou habilitar as teclas de atalho que não usam teclas de modificador como <kbd>Control</kbd> ou <kbd>Command</kbd>, em "General", desmarque **teclas de caracteres**. Se você desabilitar as teclas do caracteres, você ainda poderá acionar atalhos ao seu navegador da web, bem como habilitar os atalhos para {% data variables.product.product_name %} que usa uma tecla modificadora.
 {%- ifversion command-palette %}
-   - Optionally, to customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)."
+   - Opcionalmente, para personalizar os atalhos de teclado para acionar a paleta de comando, em "Paleta de comando", use os menus suspensos para escolher um atalho de teclado. Para obter mais informações, consulte "[Paleta de Comando de {% data variables.product.company_short %}](/get-started/using-github/github-command-palette)".
    {%- endif %}
 
 {% ifversion motion-management %}
 
-### Managing motion
+### Gerenciando o movimento
 
-You can control how {% data variables.product.product_name %} displays animated images.
+Você pode controlar como {% data variables.product.product_name %} exibe imagens animadas.
 
-By default, {% data variables.product.product_name %} syncs with your system-level preference for reduced motion. For more information, see the documentation or settings for your operating system.
+Por padrão, {% data variables.product.product_name %} sincroniza com sua preferência no nível de sistema para movimento reduzido. Para obter mais informações, consulte a documentação ou as configurações do seu sistema operacional.
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.accessibility_settings %}
-1. Under "Motion", manage settings for motion.
+1. Em "Movimento", gerencia configurações para movimento.
 
-   - Optionally, to control how {% data variables.product.product_name %} displays animaged images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**.
+   - Opcionalmente, para controlar como {% data variables.product.product_name %} exibe imagens animadas, em "Reproduzir imagens animadas automaticamente", selecione **sincronização com o sistema**, **habilitado**ou **desabilitado**.
 
 {% endif %}
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index 9de22e2c20..2d3fb87c3d 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -51,6 +51,8 @@ Você também pode adicionar este fluxo de trabalho manualmente, criando um novo
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Java CI
 
 on: [push]
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md
index 776d02c115..123f761f67 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md
@@ -380,6 +380,8 @@ Para este exemplo, você deverá criar dois [tokens da API do PyPI](https://pypi
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Upload Python Package
 
 on:
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
index 90de5cd924..456c9962fb 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
@@ -38,6 +38,8 @@ Para iniciar rapidamente, adicione o fluxo de trabalho inicial para o diretório
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Ruby
 
 on:
@@ -102,6 +104,8 @@ O fluxo de trabalho totalmente atualizado com uma estratégia de matriz pode par
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Ruby CI
 
 on:
@@ -206,6 +210,8 @@ O exemplo a seguir da matriz testa todas as versões estáveis e versões princi
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Matrix Testing
 
 on:
@@ -239,6 +245,8 @@ O exemplo a seguir instala `rubocop` e o utiliza para fazer lint de todos os arq
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Linting
 
 on: [push]
@@ -265,6 +273,8 @@ Você pode armazenar qualquer token de acesso ou credenciais necessárias para p
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Ruby Gem
 
 on:
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md
index 74478cc0ce..c4c292575f 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md
@@ -68,8 +68,12 @@ Os exemplos abaixo demonstram o uso da ação `fwal/setup-fast`.
 Você pode configurar seu trabalho para usar várias versões do Swift em uma matriz.
 
 ```yaml{:copy}
+
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+
 name: Swift
 
 on: [push]
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
index d8f103784a..9dc0859d15 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
@@ -92,6 +92,8 @@ Certifique-se de fornecer seus próprios valores para todas as variáveis na cha
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Deploy to Amazon ECS
 
 on:
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
index 55b012fd69..91379310ea 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
@@ -81,6 +81,8 @@ Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env`
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Build and deploy a container to an Azure Web App
 
 env:
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
index d4c63c611b..d019ed310f 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
@@ -67,6 +67,8 @@ Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env`
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Build and deploy JAR app to Azure Web App
 
 env:
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
index 9720214297..09b1f6a083 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
@@ -66,6 +66,8 @@ Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env`
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Build and deploy ASP.Net Core app to an Azure Web App
 
 env:
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
index ba6377d52f..6bb8213204 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
@@ -72,6 +72,8 @@ Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env`
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 on:
   push:
     branches:
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
index 53fd1f465c..86191208d2 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
@@ -66,6 +66,8 @@ Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env`
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Build and deploy PHP app to Azure Web App
 
 env:
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
index 427dbae90f..fa0c9c188f 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
@@ -69,6 +69,8 @@ Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env`
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Build and deploy Python app to Azure Web App
 
 env:
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
index 73698e3dfb..5d5b6df5dc 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
@@ -55,6 +55,8 @@ Este fluxo de trabalho usa o mecanismo de interpretação `helm` para a ação [
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Build and deploy to Azure Kubernetes Service
 
 env:
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
index 4af71c53b9..bf6ed6b7c8 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
@@ -54,6 +54,8 @@ Para obter mais informações sobre esses valores, consulte "[Criar configuraç
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Deploy web app to Azure Static Web Apps
 
 env:
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
index 3ab4cefb0e..b6a6f3f369 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
@@ -137,6 +137,8 @@ Na chave `env`, altere o valor de `GKE_CLUSTER` para o nome do seu cluster, `GKE
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Build and Deploy to GKE
 
 on:
diff --git a/translations/pt-BR/content/actions/learn-github-actions/contexts.md b/translations/pt-BR/content/actions/learn-github-actions/contexts.md
index 68cdb4b695..c13dd4f28d 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/contexts.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/contexts.md
@@ -172,25 +172,27 @@ O contexto `github` context contém informações sobre a execução do fluxo de
 {% data reusables.actions.github-context-warning %}
 {% data reusables.actions.context-injection-warning %}
 
-| Nome da propriedade        | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| -------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `github`                   | `objeto` | Contexto de nível mais alto disponível em qualquer trabalho ou etapa de um fluxo de trabalho. Este objeto contém todas as propriedades listadas abaixo.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| `github.action`            | `string` | O nome da ação atualmente em execução ou o [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid) de uma etapa. {% data variables.product.prodname_dotcom %} remove caracteres especiais e usa o nome `__run` quando a etapa atual executa um script sem um `id`. Se você usar a mesma ação mais de uma vez no mesmo trabalho, o nome incluirá um sufixo com o número da sequência com o sublinhado antes dele. Por exemplo, o primeiro script que você executar terá o nome `__run` e o segundo script será denominado `__run_2`. Da mesma forma, a segunda invocação de `actions/checkout` será `actionscheckout2`.                                                                              |
-| `github.action_path`       | `string` | O caminho onde uma ação está localizada. Esta propriedade só é compatível com ações compostas. Você pode usar este caminho para acessar arquivos localizados no mesmo repositório da ação.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| `github.action_ref`        | `string` | Para uma etapa executando uma ação, este é o ref da ação que está sendo executada. Por exemplo, `v2`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| `github.action_repository` | `string` | Para uma etpa que executa uma ação, este é o nome do proprietário e do repositório da ação. Por exemplo, `actions/checkout`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| `github.action_status`     | `string` | Para uma ação composta, o resultado atual da ação composta.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| `github.actor`             | `string` | O nome de usuário que iniciou a execução do fluxo de trabalho.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `github.api_url`           | `string` | A URL da API REST de {% data variables.product.prodname_dotcom %}.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| `github.base_ref`          | `string` | `base_ref` ou branch alvo da pull request em uma execução de fluxo de trabalho. Esta propriedade só está disponível quando o evento que aciona a execução de um fluxo de trabalho for `pull_request` ou `pull_request_target`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `github.env`               | `string` | Caminho no executor para o arquivo que define variáveis de ambiente dos comandos do fluxo de trabalho. Este arquivo é único para a etapa atual e é um arquivo diferente para cada etapa de um trabalho. Para obter mais informações, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#setting-an-environment-variable)".                                                                                                                                                                                                                                                                                                |
-| `github.event`             | `objeto` | Carga de evento de webhook completa. Você pode acessar as propriedades individuais do evento usando este contexto. Este objeto é idêntico à carga do webhook do evento que acionou a execução do fluxo de trabalho e é diferente para cada evento. Os webhooks para cada evento de {% data variables.product.prodname_actions %} que está vinculado em "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows/)". Por exemplo, para uma execução do fluxo de trabalho acionada por um evento [`push`](/actions/using-workflows/events-that-trigger-workflows#push), esse objeto contém o conteúdo da [carga do webhook de push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push). |
-| `github.event_name`        | `string` | Nome do evento que acionou a execução do fluxo de trabalho.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| `github.event_path`        | `string` | O caminho para o arquivo no executor que contém a carga completa do webhook do evento.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| `github.graphql_url`       | `string` | A URL da API do GraphQL de {% data variables.product.prodname_dotcom %}.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| `github.head_ref`          | `string` | `head_ref` ou branch de origem da pull request em uma execução de fluxo de trabalho. Esta propriedade só está disponível quando o evento que aciona a execução de um fluxo de trabalho for `pull_request` ou `pull_request_target`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| `github.job`               | `string` | O [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) do trabalho atual. <br /> Observação: Esta propriedade de contexto é definida pelo executor do Actions e só está disponível dentro da execução `etapas` de um trabalho. Caso contrário, o valor desta propriedade será `nulo`.                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| `github.ref`               | `string` | {% data reusables.actions.ref-description %}
+| Nome da propriedade                                                                                                                                                                                                                                                                                                                                                                                                                          | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `github`                                                                                                                                                                                                                                                                                                                                                                                                                                     | `objeto` | Contexto de nível mais alto disponível em qualquer trabalho ou etapa de um fluxo de trabalho. Este objeto contém todas as propriedades listadas abaixo.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `github.action`                                                                                                                                                                                                                                                                                                                                                                                                                              | `string` | O nome da ação atualmente em execução ou o [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid) de uma etapa. {% data variables.product.prodname_dotcom %} remove caracteres especiais e usa o nome `__run` quando a etapa atual executa um script sem um `id`. Se você usar a mesma ação mais de uma vez no mesmo trabalho, o nome incluirá um sufixo com o número da sequência com o sublinhado antes dele. Por exemplo, o primeiro script que você executar terá o nome `__run` e o segundo script será denominado `__run_2`. Da mesma forma, a segunda invocação de `actions/checkout` será `actionscheckout2`.                                                                              |
+| `github.action_path`                                                                                                                                                                                                                                                                                                                                                                                                                         | `string` | O caminho onde uma ação está localizada. Esta propriedade só é compatível com ações compostas. Você pode usar este caminho para acessar arquivos localizados no mesmo repositório da ação.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `github.action_ref`                                                                                                                                                                                                                                                                                                                                                                                                                          | `string` | Para uma etapa executando uma ação, este é o ref da ação que está sendo executada. Por exemplo, `v2`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `github.action_repository`                                                                                                                                                                                                                                                                                                                                                                                                                   | `string` | Para uma etpa que executa uma ação, este é o nome do proprietário e do repositório da ação. Por exemplo, `actions/checkout`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `github.action_status`                                                                                                                                                                                                                                                                                                                                                                                                                       | `string` | Para uma ação composta, o resultado atual da ação composta.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `github.actor`                                                                                                                                                                                                                                                                                                                                                                                                                               | `string` |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| {% ifversion actions-stable-actor-ids %}The username of the user that triggered the initial workflow run. If the workflow run is a re-run, this value may differ from `github.triggering_actor`. Any workflow re-runs will use the privileges of `github.actor`, even if the actor initiating the re-run (`github.triggering_actor`) has different privileges.{% else %}The username of the user that initiated the workflow run.{% endif %} |          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                              |          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `github.api_url`                                                                                                                                                                                                                                                                                                                                                                                                                             | `string` | A URL da API REST de {% data variables.product.prodname_dotcom %}.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `github.base_ref`                                                                                                                                                                                                                                                                                                                                                                                                                            | `string` | `base_ref` ou branch alvo da pull request em uma execução de fluxo de trabalho. Esta propriedade só está disponível quando o evento que aciona a execução de um fluxo de trabalho for `pull_request` ou `pull_request_target`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `github.env`                                                                                                                                                                                                                                                                                                                                                                                                                                 | `string` | Caminho no executor para o arquivo que define variáveis de ambiente dos comandos do fluxo de trabalho. Este arquivo é único para a etapa atual e é um arquivo diferente para cada etapa de um trabalho. Para obter mais informações, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#setting-an-environment-variable)".                                                                                                                                                                                                                                                                                                |
+| `github.event`                                                                                                                                                                                                                                                                                                                                                                                                                               | `objeto` | Carga de evento de webhook completa. Você pode acessar as propriedades individuais do evento usando este contexto. Este objeto é idêntico à carga do webhook do evento que acionou a execução do fluxo de trabalho e é diferente para cada evento. Os webhooks para cada evento de {% data variables.product.prodname_actions %} que está vinculado em "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows/)". Por exemplo, para uma execução do fluxo de trabalho acionada por um evento [`push`](/actions/using-workflows/events-that-trigger-workflows#push), esse objeto contém o conteúdo da [carga do webhook de push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push). |
+| `github.event_name`                                                                                                                                                                                                                                                                                                                                                                                                                          | `string` | Nome do evento que acionou a execução do fluxo de trabalho.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `github.event_path`                                                                                                                                                                                                                                                                                                                                                                                                                          | `string` | O caminho para o arquivo no executor que contém a carga completa do webhook do evento.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `github.graphql_url`                                                                                                                                                                                                                                                                                                                                                                                                                         | `string` | A URL da API do GraphQL de {% data variables.product.prodname_dotcom %}.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `github.head_ref`                                                                                                                                                                                                                                                                                                                                                                                                                            | `string` | `head_ref` ou branch de origem da pull request em uma execução de fluxo de trabalho. Esta propriedade só está disponível quando o evento que aciona a execução de um fluxo de trabalho for `pull_request` ou `pull_request_target`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `github.job`                                                                                                                                                                                                                                                                                                                                                                                                                                 | `string` | O [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) do trabalho atual. <br /> Observação: Esta propriedade de contexto é definida pelo executor do Actions e só está disponível dentro da execução `etapas` de um trabalho. Caso contrário, o valor desta propriedade será `nulo`.                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `github.ref`                                                                                                                                                                                                                                                                                                                                                                                                                                 | `string` | {% data reusables.actions.ref-description %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %}
 | `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} | | `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} | | `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %}
 {%- endif %}
@@ -198,7 +200,7 @@ O contexto `github` context contém informações sobre a execução do fluxo de
 {%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-4722 %}
 | `github.run_attempt` | `string` | Um número exclusivo para cada tentativa de execução de um fluxo de trabalho específico em um repositório. Este número começa em 1 para a primeira tentativa de execução do fluxo de trabalho e aumenta a cada nova execução. |
 {%- endif %}
-| `github.server_url` | `string` | A URL do servidor do GitHub. Por exemplo: `https://github.com`. | | `github.sha` | `string` | O SHA do commit que acionou a execução do fluxo de trabalho. | | `github.token` | `string` | Um token para efetuar a autenticação em nome do aplicativo instalado no seu repositório. Isso é funcionalmente equivalente ao segredo `GITHUB_TOKEN`. Para obter mais informações, consulte "[Autenticação automática de tokens](/actions/security-guides/automatic-token-authentication)".  <br /> Observação: Esta propriedade de contexto é definida pelo executor do Actions e só está disponível dentro da execução `etapas` de um trabalho. Caso contrário, o valor desta propriedade será `nulo`. | | `github.workflow` | `string` | O nome do fluxo de trabalho. Se o fluxo de trabalho não determina um `name` (nome), o valor desta propriedade é o caminho completo do arquivo do fluxo de trabalho no repositório. | | `github.workspace` | `string` | O diretório de trabalho padrão no executor para as etapas e a localidade padrão do seu repositório ao usar a ação [`checkout`](https://github.com/actions/checkout). |
+| `github.server_url` | `string` | A URL do servidor do GitHub. Por exemplo: `https://github.com`. | | `github.sha` | `string` | O SHA do commit que acionou a execução do fluxo de trabalho. | | `github.token` | `string` | Um token para efetuar a autenticação em nome do aplicativo instalado no seu repositório. Isso é funcionalmente equivalente ao segredo `GITHUB_TOKEN`. Para obter mais informações, consulte "[Autenticação automática de tokens](/actions/security-guides/automatic-token-authentication)".  <br /> Observação: Esta propriedade de contexto é definida pelo executor do Actions e só está disponível dentro da execução `etapas` de um trabalho. Caso contrário, o valor desta propriedade será `nulo`. |{% ifversion actions-stable-actor-ids %} | `github.triggering_actor` | `string` | The username of the user that initiated the workflow run. If the workflow run is a re-run, this value may differ from `github.actor`. Any workflow re-runs will use the privileges of `github.actor`, even if the actor initiating the re-run (`github.triggering_actor`) has different privileges. |{% endif %} | `github.workflow` | `string` | The name of the workflow. Se o fluxo de trabalho não determina um `name` (nome), o valor desta propriedade é o caminho completo do arquivo do fluxo de trabalho no repositório. | | `github.workspace` | `string` | O diretório de trabalho padrão no executor para as etapas e a localidade padrão do seu repositório ao usar a ação [`checkout`](https://github.com/actions/checkout). |
 
 ### Exemplo de conteúdo do contexto `github`
 
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
index 2aabe47545..dd6828a66b 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
@@ -32,6 +32,8 @@ No tutorial, primeiro você criará um arquivo de fluxo de trabalho que usa a a
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
 
+{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
+
     name: Label issues
     on:
       issues:
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
index 7b4fff24f7..5f45972a31 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
@@ -33,6 +33,8 @@ No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
 
+{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
+
     name: Add comment
     on:
       issues:
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
index 05b66eafea..9d1415e1ba 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
@@ -34,6 +34,8 @@ No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
 
+{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
+
     name: Move assigned card
     on:
       issues:
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index 3021a84ca4..e7dd35d0c4 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -30,10 +30,11 @@ No tutorial, primeiro você criará um arquivo de fluxo de trabalho que usa a a
 2. Escolha um projeto que pertence ao repositório. Este fluxo de trabalho não pode ser usado com projetos que pertencem a usuários ou organizações. Você pode usar um projeto existente ou criar um novo projeto. Para obter mais informações sobre como criar um projeto, consulte "[Criar um quadro de projeto](/github/managing-your-work-on-github/creating-a-project-board)".
 3. {% data reusables.actions.make-workflow-file %}
 4. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
-
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
 
+{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
+
     name: Remove labels
     on:
       project_card:
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
index 77b678ae91..f76d7e6a55 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
@@ -32,6 +32,8 @@ No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
 
+{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
+
     name: Weekly Team Sync
     on:
       schedule:
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
index 3e7a036ab0..d7e3beca2a 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -17,7 +17,7 @@ versions:
 
 ## Sobre a reexecução de fluxos de trabalho e trabalhos
 
-A reexecução de um fluxo de trabalho{% ifversion re-run-jobs %} ou trabalhos em um fluxo de trabalho{% endif %} usa o mesmo `GITHUB_SHA` (commit SHA) e `GITHUB_REF` (Git ref) do evento original que acionou a execução do fluxo de trabalho. Você pode re-executar um fluxo de trabalho{% ifversion re-run-jobs %} ou trabalhos em um fluxo de trabalho{% endif %} por até 30 dias após a execução inicial.{% ifversion re-run-jobs %} Você não pode re-executar trabalhos em um fluxo de trabalho uma vez que seus registros superaram seus limites de retenção. Para obter mais informações, consulte "[Limites de uso, cobrança e administração](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %}{% ifversion debug-reruns %} Quando você re-executar um fluxo de trabalho ou trabalhos em um fluxo de trabalho, você pode habilitar o registro de depuração para a re-execução. Isso permitirá o registro de diagnóstico do executor e o registro de depuração de etapas para a nova execução. Para obter mais informações sobre o registro de depuração, consulte "[Habilitando o registro de depuração](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)"{% endif %}
+A reexecução de um fluxo de trabalho{% ifversion re-run-jobs %} ou trabalhos em um fluxo de trabalho{% endif %} usa o mesmo `GITHUB_SHA` (commit SHA) e `GITHUB_REF` (Git ref) do evento original que acionou a execução do fluxo de trabalho. {% ifversion actions-stable-actor-ids %}The workflow will use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. {% endif %}You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. Para obter mais informações, consulte "[Limites de uso, cobrança e administração](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %}{% ifversion debug-reruns %} Quando você re-executar um fluxo de trabalho ou trabalhos em um fluxo de trabalho, você pode habilitar o registro de depuração para a re-execução. Isso permitirá o registro de diagnóstico do executor e o registro de depuração de etapas para a nova execução. Para obter mais informações sobre o registro de depuração, consulte "[Habilitando o registro de depuração](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)"{% endif %}
 
 ## Reexecutar todos os trabalhos em um fluxo de trabalho
 
diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
index a9a99d5a73..8a4a7edcfd 100644
--- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
@@ -410,6 +410,8 @@ fluxos de trabalho:
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Containers
 
 on: [push]
diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md b/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md
index 0f53c5bb72..55d4024269 100644
--- a/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md
+++ b/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md
@@ -71,6 +71,8 @@ As opções `build-push-action` necessárias para o Docker Hub são:
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Publish Docker image
 
 on:
@@ -144,9 +146,12 @@ As opções de `build-push-action` necessárias para {% data variables.product.p
 O fluxo de trabalho acima é acionado por um push para o branch da "versão". Ele verifica o repositório GitHub e usa `login-action` para fazer login no {% data variables.product.prodname_container_registry %}. Em seguida, extrai etiquetas e tags para a imagem do Docker. Finalmente, ele usa a ação `de build-push-action` para criar a imagem e publicá-la no {% data variables.product.prodname_container_registry %}.
 
 {% else %}
+
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Publish Docker image
 
 on:
@@ -196,6 +201,8 @@ O fluxo de trabalho a seguir usa os passos das seções anteriores ("[Publicar i
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Publish Docker image
 
 on:
diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index a6230b0338..59361d481c 100644
--- a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -77,8 +77,11 @@ publishing {
 Com essa configuração, é possível criar um fluxo de trabalho que publica seu pacote no Repositório Central do Maven ao executar o comando `publicação do gradle`. Na etapa de implementação, você deverá definir variáveis de ambiente para o nome de usuário e senha ou token usado para fazer a autenticação no repositório do Maven. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
 ```yaml{:copy}
+
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Publish package to the Maven Central Repository
 on:
   release:
@@ -146,8 +149,11 @@ publishing {
 Com esta configuração, você pode criar um fluxo de trabalho que publica seu pacote em {% data variables.product.prodname_registry %}, executando o comando `gradle publish`.
 
 ```yaml{:copy}
+
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Publish package to GitHub Packages
 on:
   release:
@@ -224,8 +230,11 @@ publishing {
 Com esta configuração, você pode criar um fluxo de trabalho que publica seu pacote no Repositório Central do Maven e em {% data variables.product.prodname_registry %}, executando o comando `publicação do gradle`.
 
 ```yaml{:copy}
+
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
   release:
diff --git a/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md
index e306ca5092..f873d74061 100644
--- a/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -447,7 +447,7 @@ on:
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Observação**: Este evento não ocorre para projetos (beta). Para obter mais informações, consulte "[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)".
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
 
 {% endnote %}
 {% endif %}
@@ -485,7 +485,7 @@ on:
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Observação**: Este evento não ocorre para projetos (beta). Para obter mais informações, consulte "[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)".
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
 
 {% endnote %}
 {% endif %}
@@ -523,7 +523,7 @@ on:
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Observação**: Este evento não ocorre para projetos (beta). Para obter mais informações, consulte "[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)".
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
 
 {% endnote %}
 {% endif %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
index 037459917e..5b756004d9 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
@@ -31,16 +31,12 @@ Os servidores de nomes que você especificar devem resolver o nome de host da {%
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 
-2. Para editar seus servidores de nomes, insira:
+2. To edit your nameservers, use the `ghe-setup-network` command in visual mode. Para obter mais informações, consulte "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-setup-network)".
 
   ```shell
-  sudo vim /etc/resolvconf/resolv.conf.d/head
+  ghe-setup-network -v
   ```
 
-{% data reusables.enterprise_installation.preventing-nameservers-change %}
-
-3. Adicione quaisquer entradas `nameserver` e salve o arquivo.
-4. Depois de verificar suas alterações, salve o arquivo.
 5. Para adicionar as suas novas entradas de nameserver para {% data variables.product.product_location %}, execute o seguinte:
 
   ```shell
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index 851bb76fa0..26ce053235 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -344,6 +344,18 @@ Com `ghe-set-password`, você pode definir uma nova senha para autenticação no
 ghe-set-password <new_password>
 ```
 
+### ghe-setup-network
+
+This utility allows you to configure the primary network interface.
+
+To enter visual mode, which will guide you through configuration of network settings:
+
+```shell
+$ ghe-setup-network -v
+```
+
+Para consultar opções adicionais, use o sinalizador -h.
+
 ### ghe-ssh-check-host-keys
 
 Este utilitário verifica as chaves do host SSH atuais para identificar chaves vazadas conhecidas.
@@ -655,7 +667,7 @@ ghe-repo <em>username</em>/<em>reponame</em>
 
 ### ghe-repo-gc
 
-Este utilitário reempacota manualmente uma rede de repositórios para otimizar o armazenamento do pacote. Se você tem um repositório muito grande, esse comando pode ajudar a reduzir o tamanho. O {% data variables.product.prodname_enterprise %} executa automaticamente este comando durante toda a sua interação com uma rede de repositórios.
+Este utilitário empacota manualmente uma rede de repositórios para otimizar o armazenamento do pacote. Se você tem um repositório muito grande, esse comando pode ajudar a reduzir o tamanho. O {% data variables.product.prodname_enterprise %} executa automaticamente este comando durante toda a sua interação com uma rede de repositórios.
 
 Você pode adicionar o argumento opcional `--prune` para remover objetos inacessíveis do Git que não são referenciados em um branch, tag ou qualquer outra referência. Fazer isso é útil principalmente para remover de imediato [informações confidenciais já eliminadas](/enterprise/user/articles/remove-sensitive-data/).
 
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
index 9313be72ec..3f65ba84aa 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -74,14 +74,14 @@ Os proprietários das empresas podem configurar e-mails para notificações.
 {% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
 
 {% ifversion require-tls-for-smtp %}
-## Enforcing TLS for SMTP connections
+## Aplicando TLS para conexões SMTP
 
-You can enforce TLS encryption for all incoming SMTP connections, which can help satisfy an ISO-27017 certification requirement.
+Você pode aplicar a criptografia TLS para todas as conexões SMTP recebidas, o que pode ajudar a satisfazer um requisito de certificação ISO-27017.
 
 {% data reusables.enterprise_site_admin_settings.email-settings %}
-1. Under "Authentication," select **Enforce TLS auth (recommended)**.
+1. Em "Autenticação", selecione **Aplicar TLS auth (recomendado)**.
 
-   ![Screenshot of the "Enforce TLS auth (recommended)" checkbox](/assets/images/enterprise/configuration/enforce-tls-for-smtp-checkbox.png)
+   ![Captura de tela da caixa de seleção "Forçar autenticação TLS (recomendado)"](/assets/images/enterprise/configuration/enforce-tls-for-smtp-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 {% endif %}
 
@@ -92,7 +92,7 @@ Se quiser permitir o recebimento de respostas para os e-mails de notificação,
 1. A porta 25 da instância deve estar acessível para o seu servidor SMTP.
 2. Crie um registro A que aponte para `reply.[hostname]`. Dependendo do provedor DNS e da configuração do host da instância, você poderá criar um único registro A que aponte para `*.[hostname]`.
 3. Crie um registro MX que aponte para `reply.[hostname]`, de forma que os e-mails desse domínio sejam roteados para a instância.
-4. Crie um registro MX que aponte `noreply.[hostname]` para `[hostname]`, de forma que as respostas ao endereço `cc` nos e-mails de notificação sejam roteadas para a instância. For more information, see {% ifversion ghes %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."
+4. Crie um registro MX que aponte `noreply.[hostname]` para `[hostname]`, de forma que as respostas ao endereço `cc` nos e-mails de notificação sejam roteadas para a instância. Para obter mais informações, consulte {% ifversion ghes %}"[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[Sobre notificações de e-mail](/github/receiving-notifications-about-activity-on-github/about-email-notifications)"{% endif %}."
 
 ## Resolver problemas na entrega de e-mails
 
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
index dd05637a5b..81a0713b4f 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring host keys for your instance
-shortTitle: Configure host keys
-intro: 'You can increase the security of {% data variables.product.product_location %} by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections.'
+title: Configurando chaves de host para sua instância
+shortTitle: Configurar chaves do host
+intro: 'Você pode aumentar a segurança de {% data variables.product.product_location %} configurando os algoritmos que sua instância usa para gerar e anunciar chaves de host para entrar em conexões SSH.'
 permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.'
 versions:
   ghes: '>= 3.6'
@@ -15,31 +15,31 @@ topics:
   - SSH
 ---
 
-## About host keys for your instance
+## Sobre as chaves de host para sua instância
 
-Servers that accept SSH connections advertise one or more cryptographic host keys to securely identify the server to SSH clients. To confirm the server's identity during the initialization of a connection, clients store and verify the host key. For more information, see [SSH Host Key - What, Why, How](https://ssh.com/academy/ssh/host-key) on the SSH Academy website.
+Os servidores que aceitam conexões SSH anunciam uma ou mais chaves criptográficas para identificar de forma segura o servidor com clientes SSH. Para confirmar a identidade do servidor durante a inicialização de uma conexão, os clientes armazenam e verificam a chave do host. Para obter mais informações, consulte [chave do host SSH - o quê, por quê e como](https://ssh.com/academy/ssh/host-key) no site da Academia de SSH.
 
 {% data reusables.enterprise.about-ssh-ports %}
 
-By default, {% data variables.product.product_location %} generates and advertises host keys with OpenSSH-style host key rotation. To increase the security of SSH in your environment, you can enable additional algorithms for the generation of host keys.
+Por padrão, {% data variables.product.product_location %} gera e anuncia as chaves do host com rotação de chave do estilo OpenSSH. Para aumentar a segurança de SSH no seu ambiente, você pode habilitar algoritmos adicionais para a geração de chaves de host.
 
 {% note %}
 
-**Note**: If you enable additional host key algorithms, clients that do not use OpenSSH for SSH connections may experience warnings during connection, or fail to connect entirely. Some SSH implementations can ignore unsupported algorithms and fall back to a different algorithm. If the client does not support fallback, the connection will fail. For example, the SSH library for Go does not support fallback to a different algorithm.
+**Observação**: Se você habilitar mais algoritmos de chave de host, os clientes que não usam OpenSSH para conexões SSH pododerão ver avisos durante a conexão ou nem sequer chegar a conctar-se completamente. Algumas implementações de SSH podem ignorar algoritmos não comapatíveis e voltar para um algoritmo diferente. Se o cliente não for compatível com o fallback, a conexão falhará. Por exemplo, a biblioteca SSH para o Go não é compatível com o fallback para um algoritmo diferente.
 
 {% endnote %}
 
-## Managing an Ed25519 host key
+## Gerenciando uma chave de host Ed25519
 
-To improve security for clients that connect to {% data variables.product.product_location %}, you can enable the generation and advertisement of an Ed25519 host key. Ed25519 is immune to some attacks that target older signature algorithms, without sacrificing speed. Older SSH clients may not support Ed25519. By default, {% data variables.product.product_name %} instances do not generate or advertise an Ed25519 host key. For more information, see [the Ed25519 website](https://ed25519.cr.yp.to).
+Para melhorar a segurança dos clientes que se conectam a {% data variables.product.product_location %}, você pode habilitar a geração e o anúncio de uma chave do host Ed25519. Ed25519 está imune a alguns ataques que visam algoritmos de assinatura mais antigos, sem sacrificar a velocidade. Os clientes SSH mais antigos não são compatíveis com Ed25519. Por padrão, as instâncias {% data variables.product.product_name %} não geram ou anunciam uma chave de host Ed25519. Para obter mais informações, consulte [o site Ed25519](https://ed25519.cr.yp.to).
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-1. To enable generation and advertisement of the Ed25519 host key, enter the following command.
+1. Para habilitar a geração e publicidade da chave de host Ed25519, digite o seguinte comando.
 
    ```shell
    ghe-config app.babeld.host-key-ed25519 true
    ```
-1. Optionally, enter the following command to disable generation and advertisement of the Ed25519 host key.
+1. Opcionalmente, digite o seguinte comando para desabilitar a geração e publicidade da chave do host Ed25519.
 
    ```shell
    ghe-config app.babeld.host-key-ed25519 false
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
index d520512631..2f147a4c15 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring SSH connections to your instance
-shortTitle: Configure SSH connections
-intro: 'You can increase the security of {% data variables.product.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.'
+title: Configurando conexões SSH para sua instância
+shortTitle: Configurar conexões SSH
+intro: 'Você pode aumentar a segurança de {% data variables.product.product_location %} configurando os algoritmos SSH que os clientes podem usar para estabelecer uma conexão.'
 permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.'
 versions:
   ghes: '>= 3.6'
@@ -15,37 +15,37 @@ topics:
   - SSH
 ---
 
-## About SSH connections to your instance
+## Sobre as conexões SSH para sua instância
 
 {% data reusables.enterprise.about-ssh-ports %}
 
-To accommodate the SSH clients in your environment, you can configure the types of connections that {% data variables.product.product_location %} will accept.
+Para acomodar os clientes SSH em seu ambiente, você pode configurar os tipos de conexões que {% data variables.product.product_location %} aceitará.
 
-## Configuring SSH connections with RSA keys
+## Configurando conexões SSH com chaves RSA
 
-When users perform Git operations on {% data variables.product.product_location %} via SSH over port 22, the client can authenticate with an RSA key. The client may sign the attempt using the SHA-1 hash function. In this context, the SHA-1 hash function is no longer secure. For more information, see [SHA-1](https://en.wikipedia.org/wiki/SHA-1) on Wikipedia.
+Quando os usuários executam operações do Git em {% data variables.product.product_location %} via SSH na porta 22, o cliente pode efetuar a autenticação com uma chave RSA. O cliente pode assinar a tentativa usando a função hash SHA-1. Neste contexto, a função hash SHA-1 não é mais segura. Para obter mais informações, consulte [SHA-1](https://en.wikipedia.org/wiki/SHA-1) na Wikipédia.
 
-By default{% ifversion ghes < 3.7 %} on {% data variables.product.product_name %} 3.6 and later{% endif %}, SSH connections that satisfy **both** of the following conditions will fail.
+Por padrão{% ifversion ghes < 3.7 %} nas versões {% data variables.product.product_name %} 3.6 e posteriores{% endif %}, as conexões SSH que satisfazem **ambas** das seguintes condições irão falhar.
 
 {% data reusables.ssh.rsa-sha-1-connection-failure-criteria %}
 
-You can adjust the cutoff date. If the user uploaded the RSA key before the cutoff date, the client can continue to connect successfuly using SHA-1 as long as the key remains valid. Alternatively, you can reject all SSH connections authenticated with an RSA key if the client signs the connection using the SHA-1 hash function.
+Você pode ajustar a data limite. Se o usuário enviou a chave RSA antes da data final o cliente pode continuar a se conectar com sucesso usando o SHA-1 enquanto a chave permanecer válida. Como alternativa, você pode rejeitar todas as conexões SSH autenticadas com uma chave RSA se o cliente assinar a conexão usando a função hash SHA-1.
 
-Regardless of the setting you choose for your instance, clients can continue to connect using any RSA key signed with a SHA-2 hash function.
+Independentemente da configuração que você escolher para sua instância, os clientes podem continuar a se conectar usando qualquer chave RSA assinada com uma função hash SHA-2.
 
-If you use an SSH certificate authority, connections will fail if the certificate's `valid_after` date is after the cutoff date. Para obter mais informações, consulte "[Sobre autoridades certificadas de SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)".
+Se você usar uma autoridade certificada de SSH, as conexões irão falhar se a data `valid_after` do certificado for posterior à data de corte. Para obter mais informações, consulte "[Sobre autoridades certificadas de SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)".
 
 Para obter mais informações, consulte [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server).
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-1. Audit your instance's logs for connections that use unsecure algorithms or hash functions using the `ghe-find-insecure-git-operations` utility. Para obter mais informações, consulte "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-find-insecure-git-operations)".
-1. To configure a cutoff date after which {% data variables.product.product_location %} will deny connections from clients that use an RSA key uploaded after the date if the connection is signed by the SHA-1 hash function, enter the following command. Replace _**RFC-3399-UTC-TIMESTAMP**_ with a valid RFC 3399 UTC timestamp. For example, the default value, August 1, 2022, would be represented as `2022-08-01T00:00:00Z`. For more information, see [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) on the IETF website.
+1. Audita os logs da sua instância para conexões que usam algoritmos inseguros ou funções hash usando o utilitário `ghe-find-insecure-git-operations`. Para obter mais informações, consulte "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-find-insecure-git-operations)".
+1. Para configurar uma data limite após a qual {% data variables.product.product_location %} negará as conexões dos clientes que usam uma chave RSA enviada após a data se a conexão for assinada pela função hash SHA-1, digite o comando a seguir. Substitua _**RFC-3399-UTC-TIMEAMP**_ por um horário RFC 3399 UTC válido. Por exemplo, o valor padrão, 1 de agosto de 2022, seria representado como `2022-08-01T00:00Z`. Para obter mais informações, consulte [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) no site IETF.
 
    <pre>
    $ ghe-config app.gitauth.rsa-sha1 <em>RFC-3339-UTC-TIMESTAMP</em>
    </pre>
 
-1. Alternatively, to completely disable SSH connections using RSA keys that are signed with the SHA-1 hash function, enter the following command.
+1. Como alternativa, para desabilitar completamente as conexões SSH usando chaves RSA que são assinadas com a função hash SHA-1, digite o seguinte comando.
 
    ```shell
    ghe-config app.gitauth.rsa-sha1 false
diff --git a/translations/pt-BR/content/admin/guides.md b/translations/pt-BR/content/admin/guides.md
index b4fe97e4c1..c3c79bcd76 100644
--- a/translations/pt-BR/content/admin/guides.md
+++ b/translations/pt-BR/content/admin/guides.md
@@ -119,6 +119,7 @@ includeGuides:
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise
   - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise
diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md
index eba9bf1154..e4752b57a1 100644
--- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md
+++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md
@@ -15,14 +15,14 @@ topics:
   - Authentication
   - Enterprise
   - Identity
-shortTitle: Fallback authentication
+shortTitle: Autenticação de fallback
 ---
 
 ## Sobre a autenticação integrada para usuários fora do seu provedor
 
 Por padrão, quando você habilitar a autenticação externa para {% data variables.product.product_name %}, a autenticação integrada está desabilitada para sua instância. Para obter mais informações, consulte "[Sobre a autenticação para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)".
 
-If you're unable to add specific accounts to your external authentication provider, such as accounts for contractors or machine users, you can configure fallback authentication. Fallback authentication allows built-in authentication for outside users and to access a fallback account if your authentication provider is unavailable.
+Se você não puder adicionar contas específicas ao seu provedor de autenticação externa, como contas para contratados ou usuários de máquina, você pode configurar a autenticação de fallback. A autenticação de fallback permite a autenticação integrada para usuários externos, bem como o acesso a uma conta de fallback se seu provedor de autenticação não estiver disponível.
 
 Se você configurar a autenticação integrada e uma pessoa autenticada com sucesso com o SAML ou CAS, a pessoa não terá mais a opção de realizar a autenticação com um nome de usuário e senha. Se o usuário se autenticar com êxito via LDAP, as credenciais não serão mais consideradas internas.
 
diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md
index e5f02bd7d1..4e818a1430 100644
--- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md
+++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md
@@ -40,4 +40,4 @@ Veja outras questões que você deve manter em mente:
 
 * **Autenticação de dois fatores:** {% data reusables.enterprise_user_management.external_auth_disables_2fa %}
 
-* **Fallback authentication for users with no account on your external authentication provider:** You can invite users to authenticate to {% data variables.product.product_location %} without adding them to your identity provider. Para obter mais informações, consulte "[Permitir a autenticação integrada para usuários de fora do seu provedor](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)".
+* **Autenticação de fallback para usuários sem conta no seu provedor de autenticação externo:** Você pode convidar usuários para efetuarem a autenticação em {% data variables.product.product_location %} sem adicioná-los ao seu provedor de identidade. Para obter mais informações, consulte "[Permitir a autenticação integrada para usuários de fora do seu provedor](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)".
diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
index 1c601bacb6..4fd91e8d94 100644
--- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
@@ -35,7 +35,8 @@ Além de visualizar seu registro de auditoria, você pode monitorar atividades n
 
 Como proprietário corporativo{% ifversion ghes %} ou administrador do site{% endif %}, você pode interagir com os dados do log de auditoria na sua empresa de várias maneiras:
 - Você pode visualizar o log de auditoria da sua empresa. Para obter mais informações, consulte[Acessando o log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)".
-- Você pode pesquisar eventos específicos no log de auditoria{% ifversion ghec %} e exportar dados de log de auditoria{% endif %}. Para obter mais informações, consulte "[Pesquisando o log de auditoria para a sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} e "[Exportando o log de auditoria para a sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}.
+- Você pode pesquisar eventos específicos no log de auditoria{% ifversion ghec %} e exportar dados de log de auditoria{% endif %}. For more information, see "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} and "[Exporting the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}.{% ifversion audit-data-retention-tab %}
+- You can configure settings, such as the retention period for audit log events{% ifversion enable-git-events %} and whether Git events are included{% endif %}. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise)."{% endif %}
 {%- ifversion enterprise-audit-log-ip-addresses %}
 - Você pode exibir o endereço IP associado a eventos no log de auditoria. Para obter mais informações, consulte[Exibindo endereços IP no log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise)".
 {%- endif %}
diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
index b856ac2e4a..2ec44890f3 100644
--- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
@@ -377,9 +377,15 @@ O escopo dos eventos que aparecem no log de auditoria da sua empresa depende se
 | `gist.destroy`           | Um gist foi excluído.                   |
 | `gist.visibility_change` | A visibilidade de um gist foi alterada. |
 
-{% ifversion ghec or ghes > 3.4 or ghae-issue-6724 %}
+{% ifversion git-events-audit-log %}
 ## ações da categoria `git`
 
+{% ifversion enable-git-events %}
+Before you'll see `git` category actions, you must enable Git events in the audit log. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise#managing-git-events-in-the-audit-log)."
+{% endif %}
+
+{% data reusables.audit_log.git-events-not-in-search-results %}
+
 | Ação        | Descrição                                                  |
 | ----------- | ---------------------------------------------------------- |
 | `git.clone` | Um repositório foi clonado.                                |
@@ -818,20 +824,20 @@ O escopo dos eventos que aparecem no log de auditoria da sua empresa depende se
 | `project.update_team_permission` | O nível de permissão de um quadro de projeto da equipe foi alterado ou quando uma equipe foi adicionada ou removida do quadro de um projeto. Para obter mais informações, consulte "[Gerenciando o acesso da equipe a um quadro de projeto da organização](/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board)".             |
 | `project.update_user_permission` | Um membro da organização ou colaborador externo foi adicionado ou removido de um quadro de projetos ou teve seu nível de permissão alterado. Para obter mais informações, consulte[Gerenciando o acesso de um indivíduo ao quadro de projeto da organização](/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board)." |
 
-{%- ifversion fpt or ghec %}
+{%- ifversion projects-v2 %}
 ## Ações da categoria `project_field`
 
-| Ação                   | Descrição                                                                                                                                                                                              |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `project_field.create` | Um campo foi criado em um quadro de projeto. Para obter mais informações, consulte "[" Criando um projeto (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)".   |
-| `project_field.delete` | Um campo foi excluído em um quadro de projeto. Para obter mais informações, consulte "[" Criando um projeto (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)". |
+| Ação                   | Descrição                                                                                                                                                                            |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `project_field.create` | Um campo foi criado em um quadro de projeto. For more information, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)."         |
+| `project_field.delete` | Um campo foi excluído em um quadro de projeto. For more information, see "[Deleting fields](/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields)." |
 
 ## Ações da categoria `project_view`
 
-| Ação                  | Descrição                                                                                                                                                                                                                                                  |
-| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `project_view.create` | Uma visualização foi criada em um quadro de projeto. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#creating-a-project-view)". |
-| `project_view.delete` | Uma visualização foi excluída em um quadro de projeto. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#deleting-a-saved-view)". |
+| Ação                  | Descrição                                                                                                                                                                                                    |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `project_view.create` | Uma visualização foi criada em um quadro de projeto. For more information, see "[Managing your views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)."   |
+| `project_view.delete` | Uma visualização foi excluída em um quadro de projeto. For more information, see "[Managing your views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)." |
 {%- endif %}
 
 ## ações da categoria `protected_branch`
@@ -900,7 +906,7 @@ O escopo dos eventos que aparecem no log de auditoria da sua empresa depende se
 
 | Ação                                                     | Descrição                                                                                                                                                                                                                                                         |
 | -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `repo.access`                                            | A visibilidade de um repositório alterado para privado{%- ifversion ghes %}, público,{% endif %} ou interno.                                                                                                                                                      |
+| `repo.access`                                            | The visibility of a repository changed to private{%- ifversion ghes %}, public,{% endif %} or internal.                                                                                                                                                           |
 | `repo.actions_enabled`                                   | {% data variables.product.prodname_actions %} foi habilitado para um repositório.                                                                                                                                                                                 |
 | `repo.add_member`                                        | Um colaborador foi adicionado ao repositório.                                                                                                                                                                                                                     |
 | `repo.add_topic`                                         | Um tópico foi adicionado a um repositório.                                                                                                                                                                                                                        |
@@ -912,14 +918,14 @@ O escopo dos eventos que aparecem no log de auditoria da sua empresa depende se
 | `repo.code_scanning_analysis_deleted`                    | Análise da digitalização de código para um repositório foi excluída. Para obter mais informações, consulte "[Excluir uma análise de digitalização de código de um repositório](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository)". |
 | `repo.change_merge_setting`                              | As opções de merge de pull request foram alteradas para um repositório.                                                                                                                                                                                           |
 | `repo.clear_actions_settings`                            | Um administrador de repositório limpou as configurações da política {% data variables.product.prodname_actions %} para um repositório.                                                                                                                            |
-| `repo.config`                                            | Um administrador de repositório bloqueou push forçado. Para obter mais informações, consulte [Bloquear pushes forçados em um repositório](/enterprise/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/).                                    |
+| `repo.config`                                            | Um administrador de repositório bloqueou push forçado. For more information, see [Blocking force pushes to a repository](/enterprise/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) to a repository.                                     |
 {%- ifversion fpt or ghec %}
 | `repo.config.disable_collaborators_only` | O limite de interação apenas para colaboradores foi deaabilitado. Para obter mais informações, consulte "[Restringir interações no seu repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)". | `repo.config.disable_contributors_only` | O limite de interação somente para colaboradores anteriores foi desabilitado em um repositório. Para obter mais informações, consulte "[Restringir interações no seu repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)". | `repo.config.disable_sockpuppet_disallowed` | O limite de interação somente para usuários existentes foi desabilitado em um repositório. Para obter mais informações, consulte "[Restringir interações no seu repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)". | `repo.config.enable_collaborators_only` | O limite de interação somente para colaboradores foi habilitado em um repositório. Os usuários que não são colaboradores ou integrantes da organização não puderam interagir com um repositório durante uma duração definida. Para obter mais informações, consulte "[Restringir interações no seu repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)". | `repo.config.enable_contributors_only` | O limite de interação somente para colaboradores anteriores foi habilitado em um repositório. Os usuários que não são colaboradores anteriores ou integrantes da organização não puderam interagir com um repositório durante uma duração definida. Para obter mais informações, consulte "[Restringir interações no seu repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)". | `repo.config.enable_sockpuppet_disallowed` | O limite de interação para usuários existentes foi habilitado em um repositório. Novos usuários não conseguem interagir com um repositório para uma duração definida. Os usuários existentes no repositório, colaboradores, colaboradores ou integrantes da organização podem interagir com um repositório. Para obter mais informações, consulte "[Restringir interações no seu repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)".
 {%- endif %}
 {%- ifversion ghes %}
-| `repo.config.disable_anonymous_git_access`| O acesso de leitura anônimo do Git foi desabilitado para um repositório. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)". | `repo.config.enable_anonymous_git_access` | O acesso de leitura anônimo do Git foi habilitado para um repositório. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)". | `repo.config.lock_anonymous_git_access` | A configuração do acesso de leitura anônimo do Git de um repositório foi bloqueada, o que impediu que os administradores do repositório alterassem (habilitassem ou desabilitassem) essa configuração. Para obter mais informações, consulte "[Impedir os usuários de alterarem o acesso de leitura anônimo do Git](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)". | `repo.config.unlock_anonymous_git_access` | A configuração de acesso de leitura anônima do Git de um repositório foi desbloqueada, o que permitiu que os administradores do repositório alterassem (habilitassem ou desabilitassem) essa configuração. Para obter mais informações, consulte "[Impedir os usuários de alterarem o acesso de leitura anônimo do Git](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)".
+| `repo.config.disable_anonymous_git_access`| O acesso de leitura anônimo do Git foi desabilitado para um repositório. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." | `repo.config.enable_anonymous_git_access` | O acesso de leitura anônimo do Git foi habilitado para um repositório. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." | `repo.config.lock_anonymous_git_access` | A configuração do acesso de leitura anônimo do Git de um repositório foi bloqueada, o que impediu que os administradores do repositório alterassem (habilitassem ou desabilitassem) essa configuração. For more information, see "[Preventing users from changing anonymous Git read access](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)." | `repo.config.unlock_anonymous_git_access` | A configuração de acesso de leitura anônima do Git de um repositório foi desbloqueada, o que permitiu que os administradores do repositório alterassem (habilitassem ou desabilitassem) essa configuração. For more information, see "[Preventing users from changing anonymous Git read access](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."
 {%- endif %}
-| `repo.create` | Um repositório foi criado. | `repo.create_actions_secret` | Um segredo de {% data variables.product.prodname_actions %} criado para um repositório. Para obter mais informações, consulte "[Criar segredos criptografados para um repositório](/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository)". | `repo.create_integration_secret` | Um segredo de integração de {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} ou {% data variables.product.prodname_codespaces %}{% endif %} foi criado para um repositório. | `repo.destroy` | Um repositório foi excluído.
+| `repo.create` | Um repositório foi criado. | `repo.create_actions_secret` | Um segredo de {% data variables.product.prodname_actions %} criado para um repositório. For more information, see "[Creating encrypted secrets for a repository](/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository)." | `repo.create_integration_secret` | Um segredo de integração de {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} ou {% data variables.product.prodname_codespaces %}{% endif %} foi criado para um repositório. | `repo.destroy` | Um repositório foi excluído.
 {%- ifversion ghes %}
 | `repo.disk_archive`  | Um repositório foi arquivado em um disco. Para obter mais informações, consulte "[Arquivando repositórios](/repositories/archiving-a-github-repository/archiving-repositories)".
 {%- endif %}
diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
new file mode 100644
index 0000000000..da681fec4c
--- /dev/null
+++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
@@ -0,0 +1,56 @@
+---
+title: Configuring the audit log for your enterprise
+intro: You can configure settings for your enterprise's audit log.
+shortTitle: Configure audit logs
+permissions: Enterprise owners can configure the audit log.
+versions:
+  feature: audit-data-retention-tab
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+---
+
+## About audit log configuration
+
+You can configure a retention period for audit log data and see index storage details.
+
+{% ifversion enable-git-events %}
+After you configure a retention period, you can enable or disable Git-related events from appearing in the audit log.
+{% endif %}
+
+## Configuring a retention period for audit log data
+
+You can configure a retention period for audit log data for {% data variables.product.product_location %}. Data that exceeds the period you configure will be permanently removed from disk.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.audit-log-tab %}
+{% data reusables.audit_log.audit-data-retention-tab %}
+1. Under "Configure audit log retention settings", select the dropdown menu and click a retention period.
+
+   ![Screenshot of the dropdown menu for audit log retention settings](/assets/images/help/enterprises/audit-log-retention-dropdown.png)
+1. Clique em **Salvar**.
+
+{% ifversion enable-git-events %}
+## Managing Git events in the audit log
+
+You can enable or disable Git-related events, such as `git.clone` and `git.push`, from appearing in your audit log. For a list of the Git events are are logged, 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)."
+
+If you do enable Git events, due to the large number of Git events that are logged, we recommend monitoring your instance's file storage and reviewing your related alert configurations. For more information, see "[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)."
+
+Before you can enable Git events in the audit log, you must configure a retention period for audit log data other than "infinite." For more information, see "[Configuring a retention period for audit log data](#configuring-a-retention-period-for-audit-log-data)."
+
+{% data reusables.audit_log.git-events-not-in-search-results %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.audit-log-tab %}
+{% data reusables.audit_log.audit-data-retention-tab %}
+1. Under "Git event opt-in", select or deselect **Enable git events in the audit-log**.
+
+   ![Screenshot of the checkbox to enable Git events in the audit log](/assets/images/help/enterprises/enable-git-events-checkbox.png)
+1. Clique em **Salvar**.
+
+{% endif %}
diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
index b07d5506e8..e31c510714 100644
--- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
+++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
@@ -11,6 +11,7 @@ topics:
 children:
   - /about-the-audit-log-for-your-enterprise
   - /accessing-the-audit-log-for-your-enterprise
+  - /configuring-the-audit-log-for-your-enterprise
   - /displaying-ip-addresses-in-the-audit-log-for-your-enterprise
   - /searching-the-audit-log-for-your-enterprise
   - /exporting-audit-log-activity-for-your-enterprise
diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
index bcb2f568c4..e97a793452 100644
--- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
@@ -29,9 +29,11 @@ Você pode pesquisar o log de auditoria da empresa diretamente a partir da inter
 
 Para obter mais informações sobre como visualizar o seu log de auditoria corporativa, consulte[Acessando o log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)".
 
+{% data reusables.audit_log.git-events-not-in-search-results %}
+
 Você também pode usar a API para recuperar os eventos de log de auditoria. Para obter mais informações, consulte[Usando a API do log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)".
 
-Observe que não é possível pesquisar as entradas usando texto. No entanto, é possível criar consultas de pesquisa usando diversos filtros. Muitos operadores usados ao consultar o log de auditoria, como `-`, `>`, ou `<`, correspondem ao mesmo formato de pesquisa no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
+You cannot search for entries using text. No entanto, é possível criar consultas de pesquisa usando diversos filtros. Muitos operadores usados ao consultar o log de auditoria, como `-`, `>`, ou `<`, correspondem ao mesmo formato de pesquisa no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
 
 {% note %}
 
diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
index aaa0a5de9a..ded3849c64 100644
--- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
@@ -20,7 +20,7 @@ permissions: Enterprise owners can configure audit log streaming.
 {% ifversion ghes %}
 {% note %}
 
-**Note:** Audit log streaming is currently in beta for {% data variables.product.product_name %} and is subject to change.
+**Observação:** A transmissão do log de auditoria está atualmente em beta para {% data variables.product.product_name %} e sujeito a alterações.
 
 {% endnote %}
 {% endif %}
@@ -32,11 +32,11 @@ Para ajudar a proteger sua propriedade intelectual e manter a conformidade da su
 
 Os benefícios do streaming de dados de auditoria incluem:
 
-* **Exploração de dados**. Você pode examinar eventos transmitidos usando sua ferramenta preferida para consultar grandes quantidades de dados. The stream contains both audit events and Git events across the entire enterprise account.{% ifversion pause-audit-log-stream %}
-* **Continuidade dos dados**. You can pause the stream for up to seven days without losing any audit data.{% endif %}
+* **Exploração de dados**. Você pode examinar eventos transmitidos usando sua ferramenta preferida para consultar grandes quantidades de dados. A transmissão contém eventos de auditoria e Git em toda a conta corporativa.{% ifversion pause-audit-log-stream %}
+* **Continuidade dos dados**. Você pode pausar a transmissão por até sete dias sem perder nenhum dado da auditoria.{% endif %}
 * **Retenção de dados**. Você pode manter seus registros de auditoria exportados e dados de eventos do Git se precisar.
 
-Enterprise owners can set up{% ifversion pause-audit-log-stream %}, pause,{% endif %} or delete a stream at any time. The stream exports the audit and Git events data for all of the organizations in your enterprise.
+Os proprietários das empresas podem configurar{% ifversion pause-audit-log-stream %}, pausar{% endif %} ou excluir uma transmissão a qualquer momento. A transmissão exporta os dados de eventos de auditoria e do Git para todas as organizações da sua empresa.
 
 ## Configurando a transmissão do log de auditoria
 
diff --git a/translations/pt-BR/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/translations/pt-BR/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
index e5596ea705..0613dfc2f1 100644
--- a/translations/pt-BR/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
+++ b/translations/pt-BR/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating your enterprise to the Container registry from the Docker registry
-intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.product.product_location %} to the {% data variables.product.prodname_container_registry %}.'
+title: Migrando sua empresa para o Registro do Container a partir do Registro Docker
+intro: 'Você pode migrar imagens do Docker previamente armazenadas no registro do Docker em {% data variables.product.product_location %} para o {% data variables.product.prodname_container_registry %}.'
 product: '{% data reusables.gated-features.packages %}'
 permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.'
 versions:
@@ -16,13 +16,13 @@ topics:
 
 ## Sobre o {% data variables.product.prodname_container_registry %}
 
-{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+{% data reusables.package_registry.container-registry-benefits %} Para obter mais informações, consulte "[Trabalhando com o {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)".
 
-For more information about configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+Para obter mais informações sobre a configuração de {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}, consulte "[Começando com {% data variables.product.prodname_registry %} para a sua empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)".
 
-## About migration from the Docker registry
+## Sobre a migração do registro do Docker
 
-{% data reusables.package_registry.container-registry-replaces-docker-registry %} If the Docker registry on {% data variables.product.product_location %} contains images, you must manually migrate the images to the {% data variables.product.prodname_container_registry %}.
+{% data reusables.package_registry.container-registry-replaces-docker-registry %} Se o Registro do Docker em {% data variables.product.product_location %} contiver imagens, você deverá migrar manualmente as imagens para o {% data variables.product.prodname_container_registry %}.
 
 {% ifversion ghes %}
 
@@ -34,24 +34,24 @@ For more information about configuring {% data variables.product.prodname_regist
 
 {% endif %}
 
-{% data reusables.package_registry.container-registry-migration-namespaces %} For more information about the impact of migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the  {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry#about-migration-from-the-docker-registry)."
+{% data reusables.package_registry.container-registry-migration-namespaces %} Para obter mais informações sobre o impacto da migração para o {% data variables.product.prodname_container_registry %}, consulte "[Migrando para o  {% data variables.product.prodname_container_registry %} a partir do registro do Docker](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry#about-migration-from-the-docker-registry)".
 
-## Migrating organizations to the {% data variables.product.prodname_container_registry %}
+## Fazendo a migração das organizações para o {% data variables.product.prodname_container_registry %}
 
-You can start a migration of all your organizations' Docker images to the {% data variables.product.prodname_container_registry %}. The duration of the migration operation depends on the total number of images to migrate, and the overall load on {% ifversion ghes %}your instance{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. After a successful migration, {% data variables.product.product_name %} will display a summary, and all future uploads of Docker images will use the {% data variables.product.prodname_container_registry %}.
+Você pode começar uma migração das imagens do Docker de todas as suas organizações para o {% data variables.product.prodname_container_registry %}. A duração da operação de migração depende do número total de imagens a serem transferidas, e a carga geral na {% ifversion ghes %}sua instância{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. Após uma migração bem-sucedida, {% data variables.product.product_name %} exibirá um resumo, e todos os próximos uploads das imagens do Docker usarão {% data variables.product.prodname_container_registry %}.
 
-If {% ifversion ghes %}a site administrator{% elsif ghae %}an enterprise owner{% endif %} has configured email notifications for {% data variables.product.product_location %}, you will receive an email after the migration is complete. Para obter mais informações, consulte "[Configurar e-mail para notificações](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications).
+Se {% ifversion ghes %}um administrador do site{% elsif ghae %}um proprietário de uma empresa{% endif %} tiver notificações de e-mail para {% data variables.product.product_location %}, você receberá um e-mail depois que a migração estiver concluída. Para obter mais informações, consulte "[Configurar e-mail para notificações](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications).
 
 {% note %}
 
 **{% ifversion ghes %}Observações{% elsif ghae %}Observação{% endif %}**:
 
 {%- ifversion ghes %}
-- During the migration, the CPU and memory usage for your instance will increase. To ensure the performance of the instance for your users, {% data variables.product.company_short %} recommends that you begin a migration during a period of reduced activity.
+- Durante a migração, o uso de CPU e memória para sua instância aumentará. Para garantir o desempenho da instância para seus usuários, {% data variables.product.company_short %} recomenda que você inicie a migração durante um período de atividade reduzida.
 {%- endif %}
-{% ifversion ghes %}- {% endif %}During the migration, do not modify settings for your enterprise{% ifversion ghes %} or run `ghe-config-apply` from an administrative SSH session{% endif %}. {% ifversion ghes %}These actions will trigger a configuration run, which can restart services and {% elsif ghae %}Modifying these settings {% endif %} may interrupt the migration.
+{% ifversion ghes %}- {% endif %}Durante a migração, não modifique as configurações da sua empresa{% ifversion ghes %} ou execute `ghe-config-apply` a partir de uma sessão SSH administrativa{% endif %}. {% ifversion ghes %}Estas ações acionarão uma configuração executada, que pode reiniciar serviços e a modificação {% elsif ghae %}destas configurações {% endif %} pode interromper a migração.
 {%- ifversion ghes %}
-- After the migration, storage pressure on your instance will increase due to the duplication of image files in the Docker registry and the {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.product_name %} will remove the duplicated files when all migrations are complete.
+- Após a migração, a pressão do armazenamento na sua instância aumentará devido à duplicação de arquivos de imagem no registro Docker e no {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.product_name %} will remove the duplicated files when all migrations are complete.
 
 For more information about monitoring the performance and storage of {% data variables.product.product_location %}, see "[Accessing the monitor dashboard](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)."
 {% endif %}
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 463e048ca2..418d7e9fb0 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -205,23 +205,23 @@ Por padrão, quando você impõe os limites de upload do repositório, as pessoa
 
 {% ifversion profile-name-enterprise-setting %}
 
-## Enforcing a policy for the display of member names in your repositories
+## Aplicando uma política para a exibição de nomes de integrantes nos repositórios
 
-Across all organizations owned by your enterprise, you can allow members to see a comment author's profile name, in addition to their username, in issues and pull requests for public and internal repositories.
+Em todas as organizações pertencentes à sua empresa, você pode permitir que os integrantes vejam o nome do autor de um comentário, além de seu nome de usuário, em problemas e pull requests para repositórios públicos e internos.
 
 ![Nome de perfil do autor do comentário exibido no comentário](/assets/images/help/issues/commenter-full-name.png)
 
 {% note %}
 
-**Note:** When this policy is enforced for all repositories in the enterprise, it overrides the organization setting for private repositories. For more information, see "[Managing the display of member names in your organization](/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization)".
+**Observação:** Quando esta política é aplicada em todos os repositórios da empresa, ela substitui a configuração da organização para repositórios privados. Para obter mais informações, consulte "[Gerenciar a exibição de nomes de integrantes na organização](/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization)".
 
 {% endnote %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Allow members to see the comment author's profile name in public and internal repositories", select the dropdown menu and click a policy. ![Screenshot of Options page with policy drop down emphasized](/assets/images/enterprise/site-admin-settings/comment-authors-profile-name-drop-down.png)
-5. Optionally, to enforce the display of profile names for all repositories in your enterprise, select **Enforce for all repositories on the instance**. ![Screenshot of "Enforce for all repositories" option emphasized](/assets/images/enterprise/site-admin-settings/enforce-for-all-repositories-option.png)
+4. Em "Permitir que os integrantes vejam o nome do perfil do autor do comentário em repositórios públicos e internos", selecione o menu suspenso e clique em uma política. ![Captura de tela da página de Opções com o menu suspenso da política destacado](/assets/images/enterprise/site-admin-settings/comment-authors-profile-name-drop-down.png)
+5. Opcionalmente, para aplicar a exibição de nomes de perfil para todos os repositórios da sua empresa, selecione **Aplicar para todos os repositórios na instância**. ![Captura de tela da opção "Aplicar para todos os repositórios" destacada](/assets/images/enterprise/site-admin-settings/enforce-for-all-repositories-option.png)
 
 {% endif %}
 
@@ -287,17 +287,17 @@ Você pode substituir as configurações padrão herdadas definindo as configura
 
 {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
 
-If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) for {% data variables.product.product_location %}, you can allow repository administrators to enable anonymous Git read access to public repositories.
+Se você tiver o [habilitado o modo privado](/enterprise/admin/configuration/enabling-private-mode) para {% data variables.product.product_location %}, você poderá permitir que os administradores do repositório habilitem o acesso de leitura anônimo do Git aos repositórios públicos.
 
 Habilitar o acesso de leitura anônimo do Git permite que os usuários ignorem a autenticação para ferramentas personalizadas na sua empresa. Quando você ou um administrador de repositório habilitar essa configuração de acesso em um repositório, as operações não autenticadas do Git (e qualquer pessoa com acesso de rede ao {% data variables.product.product_name %}) terão acesso de leitura sem autenticação ao repositório.
 
-Anonymous Git read access is disabled by default.{% ifversion ghes = 3.4 or ghes = 3.5 or ghes = 3.6 or ghes = 3.7 %} When you upgrade to {% data variables.product.product_name %} 3.6 or later, anonymous Git read access is automatically disabled at the application level, and `git://` connections on port 9418 will return the following error.
+O acesso de leitura anônimo do Git está desabilitado por padrão.{% ifversion ghes = 3.4 or ghes = 3.5 or ghes = 3.6 or ghes = 3.7 %} Ao atualizar para {% data variables.product.product_name %} 3.6 ou uma versão posterior, o acesso de leitura anônimo do Git é automaticamente desabilitado no nível do aplicativo, e `git://` as conexões na porta 9418 retornarão o seguinte erro.
 
 ```
-The unauthenticated git protocol on port 9418 is no longer supported.
+O protocolo não autenticado do git na porta 9418 não é mais compatível.
 ```
 
-If you wish to support the unathenticated Git protocol in your environment, you must manually re-enable the feature. {% data variables.product.company_short %} recommends using SSH instead of the Git protocol. Para obter mais informações, consulte [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server).
+Se você deseja fornecer compatibilidade para o protocolo não autenticado doGit no seu ambiente, você deverá reabilitar o recurso manualmente. {% data variables.product.company_short %} recomenda o uso de SSH em vez do protocolo do Git. Para obter mais informações, consulte [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server).
 
 {% endif %}
 
diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md
index c7febf14c4..8fd59f3ee4 100644
--- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md
+++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md
@@ -16,9 +16,9 @@ topics:
 
 ## Sobre o SSH
 
-{% data reusables.ssh.about-ssh %} For more information about SSH, see [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) on Wikipedia.
+{% data reusables.ssh.about-ssh %} Para obter mais informações sobre SSH, consulte [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) na Wikipédia.
 
-When you set up SSH, you will need to generate a new private SSH key and add it to the SSH agent. You must also add the public SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. Para mais informações consulte "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" e "[Adicionar uma nova chave SSH à sua conta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
+Ao configurar o SSH, você deverá gerar uma nova chave SSH privada e adicioná-la ao agente SSH. Você também deve adicionar a chave SSH pública à sua conta no {% data variables.product.product_name %} antes de usar a chave para efetuar a autenticação. Para mais informações consulte "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" e "[Adicionar uma nova chave SSH à sua conta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
 
 Você pode proteger ainda mais sua chave SSH usando uma chave de segurança de hardware, o que exige que a chave de segurança física do hardware seja conectada ao seu computador quando o par de chaves é usado para efetuar a autenticação com SSH. Você também pode proteger sua chave SSH, adicionando sua chave ao agente do ssh-agent e usando uma frase secreta. Para obter mais informações, consulte "[Trabalhar com frases secretas da chave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)".
 
diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
index a690fa2025..3dc3bf6f0a 100644
--- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
@@ -15,20 +15,20 @@ topics:
 shortTitle: Adicionar uma nova chave SSH
 ---
 
-## About addition of SSH keys to your account
+## Sobre a adição de chaves SSH à sua conta
 
-{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+{% data reusables.ssh.about-ssh %} Para obter mais informações, consulte "[Sobre SSH](/authentication/connecting-to-github-with-ssh/about-ssh)".
 
-After you generate an SSH key pair, you must add the public key to {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable SSH access for your account.
+Após gerar um par de chaves SSH, você deve adicionar a chave pública em {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} para habilitar o acesso SSH para a sua conta.
 
 ## Pré-requisitos
 
-Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, complete the following steps.
+Antes de adicionar uma nova chave SSH à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, siga os seguintes passos.
 
-1. Check for existing SSH keys. Para obter mais informações, consulte "[Verificar as chaves SSH existentes](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)".
-1. Generate a new SSH key and add it to your machine's SSH agent. Para obter mais informações, consulte "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)".
+1. Verifique se há chaves SSH existentes. Para obter mais informações, consulte "[Verificar as chaves SSH existentes](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)".
+1. Gere uma nova chave SSH e adicione-a ao agente SSH da sua máquina. Para obter mais informações, consulte "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)".
 
-## Adding a new SSH key to your account
+## Adicionando uma nova chave SSH à sua conta
 
 Depois de adicionar uma nova chave SSH à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, você poderá reconfigurar quaisquer repositórios locais para usar SSH. Para obter mais informações, consulte "[Alternar URLs remotos de HTTPS para SSH](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)".
 
diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
index da09885c8b..8cbebe9084 100644
--- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
+++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
@@ -15,15 +15,15 @@ topics:
 shortTitle: Verificar se há chave SSH existente
 ---
 
-## About SSH keys
+## Sobre as chaves SSH
 
-You can use SSH to perform Git operations in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. Para obter mais informações, consulte[Sobre SSH](/authentication/connecting-to-github-with-ssh/about-ssh)".
+Você pode usar SSH para executar operações do Git nos repositórios do {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. Para obter mais informações, consulte[Sobre SSH](/authentication/connecting-to-github-with-ssh/about-ssh)".
 
-If you have an existing SSH key, you can use the key to authenticate Git operations over SSH.
+Se você tiver uma chave SSH existente, você pode usar a chave para autenticar as operações do Git por SSH.
 
 ## Verificar se há chaves SSH
 
-Before you generate a new SSH key, you should check your local machine for existing keys.
+Antes de gerar uma nova chave SSH, você deve verificar a chave existente no seu computador.
 
 {% data reusables.ssh.key-type-support %}
 
diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index f00c66d3a7..32f2d732e8 100644
--- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -17,11 +17,11 @@ topics:
 shortTitle: Gerar nova chave SSH
 ---
 
-## About SSH key passphrases
+## Sobre as frases secretas da chave SSH
 
-{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+{% data reusables.ssh.about-ssh %} Para obter mais informações, consulte "[Sobre SSH](/authentication/connecting-to-github-with-ssh/about-ssh)".
 
-When you generate an SSH key, you can add a passphrase to further secure the key. Whenever you use the key, you must enter the passphrase. If your key has a passphrase and you don't want to enter the passphrase every time you use the key, you can add your key to the SSH agent. The SSH agent manages your SSH keys and remembers your passphrase.
+Ao gerar uma chave SSH, você pode adicionar uma senha para proteger ainda mais a chave. Sempre que você usar a chave, você deverá digitar a senha. Se a sua chave tiver uma senha e você não quiser inserir a senha toda vez que usar a tecla, você poderá adicionar sua chave ao agente SSH. O agente SSH gerencia suas chaves SSH e lembra sua frase secreta.
 
 Se você ainda não tem uma chave SSH, você deve gerar uma nova chave SSH para usar para a autenticação. Se você não tem certeza se já tem uma chave SSH, você pode verificar se há chaves existentes. Para obter mais informações, consulte "[Verificar as chaves SSH existentes](/github/authenticating-to-github/checking-for-existing-ssh-keys)".
 
@@ -29,7 +29,7 @@ Se você deseja usar uma chave de segurança de hardware para efetuar a autentic
 
 ## Gerar uma nova chave SSH
 
-You can generate a new SSH key on your local machine. After you generate the key, you can add the key to your account on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable authentication for Git operations over SSH.
+Você pode gerar uma nova chave SSH na sua máquina local. Após gerar a chave, você poderá adicionar a chave à sua conta em {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} para habilitar a autenticação para operações do Git por meio do SSH.
 
 {% data reusables.ssh.key-type-support %}
 
@@ -126,9 +126,9 @@ Antes de adicionar uma nova chave SSH ao agente para gerenciar suas chaves, voc
 
      **Notas:**
 
-     - If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
+     - Se você escolheu não adicionar uma senha à sua chave, você deve omitir a linha `UseKeychain`.
 
-     - If you see a `Bad configuration option: usekeychain` error, add an additional line to the configuration's' `Host *` section.
+     - Se você vir um erro `Bad configuration option: usekeychain`, adicione uma linha extra à seção `Host *` da configuração.
 
        ```
        Host *
diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
index 6f55a74da6..d811e6e294 100644
--- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
+++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
@@ -17,9 +17,9 @@ topics:
 shortTitle: Frases secretas da chave SSH
 ---
 
-## About passphrases for SSH keys
+## Sobre as frases secretas para chaves SSH
 
-With SSH keys, if someone gains access to your computer, the attacker can gain access to every system that uses that key. Para incluir uma camada extra de segurança, adicione uma frase secreta à sua chave SSH. To avoid entering the passphrase every time you connect, you can securely save your passphrase in the SSH agent.
+Com chaves SSH, se alguém obtiver acesso ao seu computador, o invasor poderá obter acesso a todos os sistemas que usam essa chave. Para incluir uma camada extra de segurança, adicione uma frase secreta à sua chave SSH. Para evitar inserir a senha toda vez que você se conectar, você pode salvar a sua frase secreta de forma segura no agente SSH.
 
 ## Adicionar ou alterar frase secreta
 
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
index a399486eb0..bd1c4ec88b 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
@@ -69,7 +69,7 @@ Quando quiser usar um {% data variables.product.prodname_oauth_app %} que se int
 | Dados pessoais do usuário | Os dados do usuário incluem informações encontradas no seu perfil de usuário, como nome, endereço de e-mail e localização.                                                                                                                                                                                                      |
 | Repositórios              | As informações de repositório incluem os nomes dos contribuidores, os branches que você criou e os arquivos reais dentro do repositório. Os apps podem solicitar acesso para repositórios públicos ou privados em um nível amplo de usuário.                                                                                    |
 | Exclusão de repositório   | Os apps podem solicitar a exclusão de repositórios que você administra, mas não terão acesso ao seu código. |{% ifversion projects-oauth-scope %}
-| Projetos                  | Acesso aos projetos de usuário e organização (beta). Os aplicativos podem solicitar acesso somente leitura/gravação ou leitura. 
+| Projetos                  | Access to user and organization {% data variables.projects.projects_v2 %}. Os aplicativos podem solicitar acesso somente leitura/gravação ou leitura. 
 {% endif %}
 
 ## Solicitar permissões atualizadas
diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
index d52c939df9..300d985ccf 100644
--- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
+++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
@@ -29,7 +29,7 @@ Os commits e tags têm o seguinte status de verificação, dependendo se você h
 
 {% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
 
-Signing commits differs from signing off on a commit. For more information about signing off on commits, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+A assinatura de commits difere encerrar a sessão em um commit. Para obter mais informações sobre a encerrar sessão nos commits, consulte "[Gerenciando a política de encerramento de sessão do commit do seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository). "
 
 ### Status padrão
 
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
index eab645d1f1..8a913afa6c 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
@@ -22,6 +22,9 @@ Os proprietários da organização e gerentes de faturamento podem ver o uso do
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.codespaces-minutes %}
 {% data reusables.dotcom_billing.actions-packages-report-download-org-account %}
+1. Filter the report to show only rows that mention "Codespaces" in the `Product` field.
+
+   ![A usage report filtered for Codespaces](/assets/images/help/codespaces/CSV-usage-report.png)
 
 {% ifversion ghec %}
 ## Visualizando o uso de {% data variables.product.prodname_codespaces %} para sua conta corporativa
diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
index 87225cd591..55b0c09643 100644
--- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
+++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
@@ -26,7 +26,7 @@ topics:
 
 ## Sobre o {% data variables.product.prodname_advisory_database %}
 
-The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
+O {% data variables.product.prodname_advisory_database %} contém uma lista de vulnerabilidades de segurança conhecidas {% ifversion GH-advisory-db-supports-malware %}e malware, {% endif %}agrupados em duas categorias: consultorias revisadas por {% data variables.product.company_short %} e consultorias não revisadas.
 
 {% data reusables.repositories.tracks-vulnerabilities %}
 
@@ -34,7 +34,7 @@ The {% data variables.product.prodname_advisory_database %} contains a list of k
 
 {% data reusables.advisory-database.beta-malware-advisories %}
 
-Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}.
+Cada cosultoria no {% data variables.product.prodname_advisory_database %} é para uma vulnerabilidade em projetos de código aberto{% ifversion GH-advisory-db-supports-malware %} ou para software de código aberto malicioso{% endif %}.
 
 {% data reusables.repositories.a-vulnerability-is %} De modo geral, as vulnerabilidades no código são introduzidas por acidente e corrigidas logo após serem descobertas. Você deve atualizar seu código para usar a versão fixa da dependência assim que estiver disponível.
 
@@ -46,7 +46,7 @@ Em contraste, o software malicioso, ou malware, é um código projetado intencio
 
 ### Consultorias revisadas por {% data variables.product.company_short %}
 
-{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. Analisamos cuidadosamente cada consultoria com relação à validade e nos asseguramos de que elas tenham uma descrição completa e contenham tanto o ecossistema como as informações sobre pacotes.
+As consultorias revisadas por {% data variables.product.company_short %} são vulnerabilidades de segurança{% ifversion GH-advisory-db-supports-malware %} ou malware{% endif %} que foram mapeados com pacotes em ecossistemas com os quais temos compatibilidade. Analisamos cuidadosamente cada consultoria com relação à validade e nos asseguramos de que elas tenham uma descrição completa e contenham tanto o ecossistema como as informações sobre pacotes.
 
 Geralmente, nós nomeamos nossos ecossistemas compatíveis após o registro do pacote associado à linguagem de programação de software. Nós revisamos as consultorias se eças não forem para uma vulnerabilidade em um pacote que vem de um registro compatível.
 
@@ -62,7 +62,7 @@ Geralmente, nós nomeamos nossos ecossistemas compatíveis após o registro do p
 
 Se você tem uma sugestão para um novo ecossistema com o qual devemos ter compatibilidade, abra um problema de [](https://github.com/github/advisory-database/issues) para discussão.
 
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)".
+Se você habilitar {% data variables.product.prodname_dependabot_alerts %} para seus repositórios, você será notificado automaticamente quando uma nova consultoria revisada por {% data variables.product.company_short %} relatar uma vulnerabilidade {% ifversion GH-advisory-db-supports-malware %}ou malware{% endif %} para um pacote de que você depende. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)".
 
 ### Consultorias não revisadas
 
@@ -72,7 +72,7 @@ As consultorias não revisadas são vulnerabilidades de segurança que publicamo
 
 ## Sobre informações em consultorias de segurança
 
-Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. Além disso, a consultoria da lista de Bancos de Vulnerabilidade Nacional contêm um link para o registro CVE, onde você pode ler mais detalhes sobre a vulnerabilidade, suas pontuações CVSS e seu nível de gravidade qualitativa. Para obter mais informações, consulte a "[Base de Dados de Vulnerabilidade Nacional](https://nvd.nist.gov/)" do Instituto Nacional de Padrões e Tecnologia.
+Cada consultoria de segurança contém informações sobre a vulnerabilidade{% ifversion GH-advisory-db-supports-malware %} ou malware,{% endif %} que podem incluir a descrição, gravidade, pacote afetado, ecossistema de pacotes, versões afetadas e versões alteradas, impacto e informações opcionais como referências, soluções alternativas e créditos. Além disso, a consultoria da lista de Bancos de Vulnerabilidade Nacional contêm um link para o registro CVE, onde você pode ler mais detalhes sobre a vulnerabilidade, suas pontuações CVSS e seu nível de gravidade qualitativa. Para obter mais informações, consulte a "[Base de Dados de Vulnerabilidade Nacional](https://nvd.nist.gov/)" do Instituto Nacional de Padrões e Tecnologia.
 
 O nível de gravidade é um dos quatro níveis possíveis definidos no [ Sistema de Pontuação de vulnerabilidade Comum (CVSS), Seção 5](https://www.first.org/cvss/specification-document)".
 - Baixo
@@ -93,12 +93,12 @@ O {% data variables.product.prodname_advisory_database %} usa os níveis de CVSS
    **Dica:** Você pode usar a barra lateral à esquerda para explorar as consultorias revisadas por {% data variables.product.company_short %} e as consultorias não revisadas separadamente.
 
    {% endtip %}
-3. Click an advisory to view details. Por padrão, você verá consultorias revisadas por {% data variables.product.company_short %} para vulnerabilidades de segurança. {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %}
+3. Clique em uma consultoria para ver os detalhes. Por padrão, você verá consultorias revisadas por {% data variables.product.company_short %} para vulnerabilidades de segurança. {% ifversion GH-advisory-db-supports-malware %}Para mostrar consultorias de malware, use `type:malware` na barra de pesquisa.{% endif %}
 
 
 {% note %}
 
-O banco de dados também pode ser acessado usando a API do GraphQL. {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
+O banco de dados também pode ser acessado usando a API do GraphQL. {% ifversion GH-advisory-db-supports-malware %}Por padrão, as consultas retornarão consultorias revisadas por {% data variables.product.company_short %} de vulnerabilidades de segurança, a menos que você especifique `type:malware`.{% endif %} Para obter mais informações, consulte o evento de webhook "[`security_advisory`](/webhooks/event-payloads/#security_advisory)".
 
 {% endnote %}
 
@@ -116,13 +116,13 @@ Você pode procurar no banco de dados e usar qualificadores para limitar sua bus
 | Qualifier       | Exemplo                                                                                                                                                                                       |
 | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `type:reviewed` | [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) mostrará as consultorias revisadas por {% data variables.product.company_short %} para vulerabilidades de segurança. |
-{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
-{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
-| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | | `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | | `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | | `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | | `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | | `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | | `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | | `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | | `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | | `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | | `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | | `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | | `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | | `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
+{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**tipo:malware**](https://github.com/advisories?query=type%3Amalware) mostrará as consultorias revisadas por {% data variables.product.company_short %} para malware. |
+{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) mostrará as consultorias não revisadas. |
+| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) mostrará a consultoria com o ID de {% data variables.product.prodname_advisory_database %}. | | `CVE-ID`|[**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) mostrará a consultoria com este ID de CVE. | | `ecosystem:ECOSYSTEM`|[**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) mostrará apenas as consultorias que afetam os pacotes NPM. | | `severity:LEVEL`|[**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) mostrará apenas as consultorias com um alto nível de gravidade. | | `affects:LIBRARY`|[**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) mostrará apenas as consultorias que afetam a biblioteca de lodash. | | `cwe:ID`|[**cwe:352**](https://github.com/advisories?query=cwe%3A352) mostrará apenas as consultorias com este número de CWE. | | `credit:USERNAME`|[**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) mostrará apenas as consultorias creditadas na conta de usuário "octocat". | | `sort:created-asc`|[**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) classificará os resultados, mostrando as consultorias mais antigas primeiro. | | `sort:created-desc`|[**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) classificará os resultados mostrando as consultorias mais novas primeiro. | | `sort:updated-asc`|[**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) classificará os resultados, mostrando os menos atualizados primeiro. | | `sort:updated-desc`|[**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) classificará os resultados, mostrando os mais atualizados primeiro. | | `is:withdrawn`|[**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) mostrará apenas as consultorias que foram retiradas. | | `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | | `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
 
 ## Visualizar seus repositórios vulneráveis
 
-For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. Para ver um repositório vulnerável, você deve ter acesso a {% data variables.product.prodname_dependabot_alerts %} para esse repositório. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)".
+Para qualquer consultoria revisada por {% data variables.product.company_short %} no {% data variables.product.prodname_advisory_database %}, você pode ver quais de seus repositórios são afetados por essa vulnerabilidade de segurança{% ifversion GH-advisory-db-supports-malware %} ou malware{% endif %}. Para ver um repositório vulnerável, você deve ter acesso a {% data variables.product.prodname_dependabot_alerts %} para esse repositório. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)".
 
 1. Navegue até https://github.com/advisories.
 2. Clique em uma consultoria.
@@ -131,30 +131,30 @@ For any {% data variables.product.company_short %}-reviewed advisory in the {% d
 5. Para mais detalhes sobre a vulnerabilidade e para aconselhamento sobre como corrigir o repositório vulnerável clique no nome do repositório.
 
 {% ifversion security-advisories-ghes-ghae %}
-## Accessing the local advisory database on {% data variables.product.product_location %}
+## Acessando o banco de dados local de consultoria em {% data variables.product.product_location %}
 
-If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.product.product_location %}, you can also browse reviewed advisories locally. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
+Se o administrador do site tiver habilitado {% data variables.product.prodname_github_connect %} para {% data variables.product.product_location %}, você também poderá procurar consultorias revisadas localmente. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
 
-You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories.
+Você pode usar o seu banco de dados local de consultoria para verificar se uma vulnerabilidade de segurança específica está incluída e, portanto, se você receberá alertas de dependências vulneráveis. Você também pode visualizar todos os repositórios vulneráveis.
 
-1. Navigate to `https://HOSTNAME/advisories`.
+1. Acesse `https://HOSTNAME/advisories`.
 2. Opcionalmente, para filtrar a lista, use qualquer um dos menus suspensos. ![Filtros do menu suspenso](/assets/images/help/security/advisory-database-dropdown-filters.png)
    {% note %}
 
-   **Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)".
+   **Observação:** Apenas consultorias revisadas serão listadas. As consultorias não revisadas podem ser visualizadas em {% data variables.product.prodname_advisory_database %} em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte[Acessando uma consultoria no banco de dados do GitHub](#accessing-an-advisory-in-the-github-advisory-database)".
 
    {% endnote %}
-3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %}
+3. Clique em uma consultoria para ver detalhes.{% ifversion GH-advisory-db-supports-malware %} Por padrão, você verá consultorias revisadas por {% data variables.product.company_short %} para vulnerabilidades de segurança. Para mostrar consultorias de malware, use `type:malware` na barra de pesquisa.{% endif %}
 
-You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.product.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)".
+Pode também sugerir melhorias para qualquer consultoria diretamente do banco de dados de consultoria local. Para obter mais informações, consulte "[Editando consultorias de {% data variables.product.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)".
 
-### Viewing vulnerable repositories for {% data variables.product.product_location %}
+### Visualizando repositórios vulneráveis para {% data variables.product.product_location %}
 
 {% data reusables.repositories.enable-security-alerts %}
 
-In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. Para ver um repositório vulnerável, você deve ter acesso a {% data variables.product.prodname_dependabot_alerts %} para esse repositório. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)".
+No banco de dados local da consultoria , você pode ver quais repositórios são afetados por cada vulnerabilidade de segurança{% ifversion GH-advisory-db-supports-malware %} ou malware{% endif %}. Para ver um repositório vulnerável, você deve ter acesso a {% data variables.product.prodname_dependabot_alerts %} para esse repositório. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)".
 
-1. Navigate to `https://HOSTNAME/advisories`.
+1. Acesse `https://HOSTNAME/advisories`.
 2. Clique em uma consultoria.
 3. Na parte superior da página da consultoria, clique em **Alertas do dependabot**. ![Alertas do Dependabot](/assets/images/help/security/advisory-database-dependabot-alerts.png)
 4. Opcionalmente, para filtrar a lista, use a barra de pesquisa ou os menus suspensos. O menu suspenso "Organização" permite filtrar {% data variables.product.prodname_dependabot_alerts %} por proprietário (organização ou usuário). ![Barra de pesquisa e menus suspensos para filtrar alertas](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
index 5f266d1dca..e57510ea76 100644
--- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
+++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
@@ -22,7 +22,7 @@ shortTitle: Editar banco de dados consultivo
 ## Sobre a edição de consultorias no {% data variables.product.prodname_advisory_database %}
 Consultorias de segurança em {% data variables.product.prodname_advisory_database %} em [github.com/advisories](https://github.com/advisories) são consideradas consultorias globais. Qualquer pessoa pode sugerir melhorias em qualquer consultoria de segurança global na {% data variables.product.prodname_advisory_database %}. Você pode editar ou adicionar qualquer detalhe, incluindo ecossistemas adicionalmente afetados, nível de gravidade ou descrição de quem é impactado. A equipe de curadoria da {% data variables.product.prodname_security %} irá revisar as melhorias apresentadas e publicá-las em {% data variables.product.prodname_advisory_database %}, se aceitas.
 {% ifversion fpt or ghec %}
-Somente proprietários e administradores de repositórios podem editar consultorias de segurança no nível do repositório. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
+Somente proprietários e administradores de repositórios podem editar consultorias de segurança no nível do repositório. Para obter mais informações, consulte"[Editando a consultoria de segurança de um repositório](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
 
 ## Editando consultorias no banco de dados consultivo do GitHub
 
@@ -36,12 +36,12 @@ Somente proprietários e administradores de repositórios podem editar consultor
 Você também pode abrir um pull request diretamente em um arquivo consultivo no repositório [github/advisory-database](https://github.com/github/advisory-database). Para obter mais informações, consulte as [diretrizes de contribuição](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md).
 
 {% ifversion security-advisories-ghes-ghae %}
-## Editing advisories from {% data variables.product.product_location %}
+## Editando consultorias de {% data variables.product.product_location %}
 
-If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.product.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url.
+Se você tiver {% data variables.product.prodname_github_connect %} habilitado para {% data variables.product.product_location %}, você poderá ver consultorias adicionando `/advisories` à URL da instância.
 
-1. Navigate to `https://HOSTNAME/advisories`.
+1. Acesse `https://HOSTNAME/advisories`.
 2. Selecione a consultoria de segurança com a qual você gostaria de contribuir.
-3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on Github.com.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}. ![Link para sugerir melhorias](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png)
-4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above.
+3. No lado direito da página, clique no link **Sugerir melhorias para esta vulnerabilidade no no Github.com**. Uma noba guia será aberta com a mesma consultoria de segurança em {% data variables.product.prodname_dotcom_the_website %}. ![Link para sugerir melhorias](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png)
+4. Edite a consultoria, seguindo os passos quatro a seis em "[Editando consultorias no banco de dados do GitHub](#editing-advisories-in-the-github-advisory-database)" acima.
 {% endif %}
diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
index 6038a6d436..6f4354c2b7 100644
--- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
+++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
@@ -43,6 +43,8 @@ Para fluxos de trabalho iniciados por {% data variables.product.prodname_dependa
 Para fluxos de trabalho iniciados por {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) que usam eventos de `pull_request_target`, se a referência da base do pull request foi criada por {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`), the `GITHUB_TOKEN` será somente leitura e os segredos não estarão disponíveis.
 {% endif %}
 
+{% ifversion actions-stable-actor-ids %}These restrictions apply even if the workflow is re-run by a different actor.{% endif %}
+
 Para obter mais informações, consulte ["Manter seus GitHub Actions e fluxos de trabalho seguro: Evitando solicitações de pwn"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
 
 {% ifversion fpt or ghec or ghes > 3.3 %}
@@ -224,8 +226,16 @@ jobs:
 
 ### Reexecutando manualmente um fluxo de trabalho
 
+{% ifversion actions-stable-actor-ids %}
+
+When you manually re-run a Dependabot workflow, it will run with the same privileges as before even if the user who initiated the rerun has different privileges. Para obter mais informações, consulte "[Executando novamente os fluxos de trabalho e trabalhos](/actions/managing-workflow-runs/re-running-workflows-and-jobs)".
+
+{% else %}
+
 Você também pode executar novamente um fluxo de trabalho pendente no Dependabot, e ele será executado com um token de leitura-gravação e acesso a segredos. Antes de executar manualmente um fluxo de trabalho com falha, você deve sempre verificar se a dependência está sendo atualizada para garantir que a mudança não introduza qualquer comportamento malicioso ou não intencional.
 
+{% endif %}
+
 ## Automações comuns de dependência
 
 Aqui estão vários cenários comuns que podem ser automatizados usando {% data variables.product.prodname_actions %}.
@@ -466,6 +476,7 @@ on: pull_request_target
 
 permissions:
   contents: write
+  pull-requests: write
 
 jobs:
   dependabot:
@@ -497,6 +508,7 @@ on: pull_request
 
 permissions:
   contents: write
+  pull-requests: write
 
 jobs:
   dependabot:
diff --git a/translations/pt-BR/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
index 3ee71a4693..b75e31852c 100644
--- a/translations/pt-BR/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
+++ b/translations/pt-BR/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
@@ -24,8 +24,16 @@ shortTitle: Proteção por push
 
 Até agora, {% data variables.product.prodname_secret_scanning_GHAS %} verifica segredos _após_ um push e alerta usuários de segredos expostos. {% data reusables.secret-scanning.push-protection-overview %}
 
+If a contributor bypasses a push protection block for a secret, {% data variables.product.prodname_dotcom %}:
+- generates an alert.
+- creates an alert in the "Security" tab of the repository.
+- adds the bypass event to the audit log.{% ifversion secret-scanning-push-protection-email %}
+- sends an email alert to organization owners, security managers, and repository administrators, with a link to the related secret and the reason why it was allowed.{% endif %}
+
 {% data variables.product.prodname_secret_scanning_caps %} como proteção por push atualmente verifica repositórios de segredos emitidos pelos seguintes prestadores de serviços.
 
+{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
+
 {% data reusables.secret-scanning.secret-list-private-push-protection %}
 
 ## Habilitando {% data variables.product.prodname_secret_scanning %} como uma proteção por push
@@ -78,6 +86,8 @@ Se você confirmar que um segredo é real e pretender corrigi-lo mais tarde, voc
 
 {% data reusables.secret-scanning.push-protection-allow-secrets-alerts %}
 
+{% data reusables.secret-scanning.push-protection-allow-email %}
+
 1. Acesse o URL retornado por {% data variables.product.prodname_dotcom %} quando seu push foi bloqueado. ![Captura de tela que mostra o formulário com opções para desbloquear o push de um segredo](/assets/images/help/repository/secret-scanning-unblock-form.png)
 {% data reusables.secret-scanning.push-protection-choose-allow-secret-options %}
 1. Clique **Me permite enviar por push este segredo**.
@@ -102,6 +112,8 @@ Se {% data variables.product.prodname_dotcom %} bloquear um segredo que você ac
 
 {% data reusables.secret-scanning.push-protection-allow-secrets-alerts %}
 
+{% data reusables.secret-scanning.push-protection-allow-email %}
+
 Se você confirmar que um segredo é real e pretender corrigi-lo mais tarde, você deverá procurar remediar o segredo o mais rápido possível.
 
 1. No banner que apareceu na parte suérior da página quando {% data variables.product.prodname_dotcom %} bloqueou o seu commit, clique em **Ignorar proteção**.
diff --git a/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md b/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md
index 53d905cd20..7cbccf7eaf 100644
--- a/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md
+++ b/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md
@@ -34,6 +34,8 @@ As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {
 
 O {% data variables.product.product_name %} atualmente verifica repositórios públicos para encontrar segredos emitidos pelos seguintes provedores de serviços. Para obter mais informações sobre {% data variables.product.prodname_secret_scanning_partner %}, consulte "[Sobre {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)."
 
+{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
+
 {% data reusables.secret-scanning.partner-secret-list-public-repo %}
 {% endif %}
 
@@ -42,6 +44,8 @@ O {% data variables.product.product_name %} atualmente verifica repositórios p
 
 Quando {% data variables.product.prodname_secret_scanning_GHAS %} está habilitado, {% data variables.product.prodname_dotcom %} digitalia os segredos emitidos pelos seguintes prestadores de serviços. {% ifversion ghec %}Para obter mais informações sobre {% data variables.product.prodname_secret_scanning_GHAS %}, consulte "[Sobre {% data variables.product.prodname_secret_scanning_GHAS %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)."{% endif %}
 
+{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
+
 Se você usar a API REST para a digitalização de segredo, você pode usar o tipo `tipo de segredo` para relatar segredos de emissores específicos. Para obter mais informações, consulte "[Verificação de segredo](/enterprise-cloud@latest/rest/secret-scanning)".
 
 {% ifversion ghes or ghae or ghec %}
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
index 8e086c32fd..d41feaaee7 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
@@ -52,6 +52,8 @@ O recurso de revisão de dependências é disponibilizado quando você habilitar
 
 A ação está disponível para todos os repositórios públicos {% ifversion fpt or ghec %}, bem como repositórios privados {% endif %}que habilitaram {% data variables.product.prodname_GH_advanced_security %}.
 
+{% data reusables.dependency-review.action-enterprise %}
+
 Você pode usar o {% data variables.product.prodname_dependency_review_action %} em seu repositório para impor revisões de dependência nos seus pull requests A ação verifica versões vulneráveis de dependências introduzidas por alterações na versão do pacote nos pull requests, e avisa você sobre as vulnerabilidades de segurança associadas. Isso permite uma melhor visibilidade do que está mudando em um pull request e ajuda a evitar que as vulnerabilidades sejam adicionadas ao seu repositório. Para obter mais informações, consulte [`dependency-review-action`](https://github.com/actions/dependency-review-action).
 
 ![Exemplo de ação de revisão de dependência](/assets/images/help/graphs/dependency-review-action.png)
@@ -61,7 +63,7 @@ Por padrão, a verificação {% data variables.product.prodname_dependency_revie
 A ação usa a API REST de Revisão de Dependência para obter o diff das alterações de dependência entre o commit base e o commit principal. Você pode usar a API de Revisão de Dependência para obter o diff de alterações de dependência, incluindo dados de vulnerabilidade, entre quaisquer dois commits em um repositório. Para obter mais informações, consulte "[Revisão de dependência](/rest/reference/dependency-graph#dependency-review)".
 
 {% ifversion dependency-review-action-configuration %}
-Você pode configurar a {% data variables.product.prodname_dependency_review_action %} para melhor atender às suas necessidades. Por exemplo, você pode especificar o nível de gravidade que fará a ação falhar ou definir uma lista de permissão ou proibição para que as licenças digitalizem. Para obter mais informações, consulte [Configurando revisão de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review#configuring-the-dependency-review-github-action)".
+Você pode configurar a {% data variables.product.prodname_dependency_review_action %} para melhor atender às suas necessidades. For example, you can specify the severity level that will make the action fail{% ifversion dependency-review-action-licenses %}, or set an allow or deny list for licenses to scan{% endif %}. Para obter mais informações, consulte [Configurando revisão de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review#configuring-the-dependency-review-github-action)".
 {% endif %}
 
 {% endif %}
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
index bb7658450a..0753459a60 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
@@ -56,17 +56,21 @@ A revisão de dependências está disponível quando o gráfico de dependências
 
 As seguintes opções de configuração estão disponíveis.
 
-| Opção              | Obrigatório | Uso                                                                                                                                                                                                                                                                              |
-| ------------------ | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `fail-on-severity` | Opcional    | Define o limite para o nível de gravidade (`baixo`, `moderado`, `alto`, `grave`).</br>A ação irpa falhar em qualquer pull request que introduzir vulnerabilidades do nível de gravidade especificado ou superior.                                                                |
-| `allow-licenses`   | Opcional    | Contém uma lista de licenças permitidas. Você pode encontrar os valores possíveis para este parâmetro na página de [Licenças](/rest/licenses) da documentação da API.</br>A ação falhará em pull requests que introduzem dependências com licenças que não correspondem à lista. |
-| `deny-licenses`    | Opcional    | Contém uma lista de licenças proibidas. Você pode encontrar os valores possíveis para este parâmetro na página de [Licenças](/rest/licenses) da documentação da API.</br>A ação falhará em pull requests que introduzem dependências com licenças que correspondam à lista.      |
+| Opção              | Obrigatório | Uso                                                                                                                                                                                                               |
+| ------------------ | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `fail-on-severity` | Opcional    | Define o limite para o nível de gravidade (`baixo`, `moderado`, `alto`, `grave`).</br>A ação irpa falhar em qualquer pull request que introduzir vulnerabilidades do nível de gravidade especificado ou superior. |
+{%- ifversion dependency-review-action-licenses %}
+| `allow-licenses` | Optional | Contains a list of allowed licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that do not match the list.|{% endif %}
+{%- ifversion dependency-review-action-licenses %}
+| `deny-licenses` | Optional | Contains a list of prohibited licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that match the list.|{% endif %}
 
+{% ifversion dependency-review-action-licenses %}
 {% tip %}
 
 Dica de **:** As opções `allow-licenses` e  `deny-licenses` são mutuamente exclusivas.
 
 {% endtip %}
+{% endif %}
 
 Este exemplo do arquivo de {% data variables.product.prodname_dependency_review_action %} ilustra como você pode usar essas opções de configuração.
 
@@ -88,6 +92,7 @@ jobs:
         with:
           # Possible values: "critical", "high", "moderate", "low" 
           fail-on-severity: critical
+{% ifversion dependency-review-action-licenses %}
           # You can only can only include one of these two options: `allow-licenses` and `deny-licences`
           # ([String]). Only allow these licenses (optional)
           # Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses 
@@ -96,6 +101,7 @@ jobs:
           # ([String]). Block the pull request on these licenses (optional)
           # Possible values: Any  `spdx_id` value(s) from https://docs.github.com/en/rest/licenses 
           # deny-licenses: LGPL-2.0, BSD-2-Clause
+{% endif %}
 ```
 
 Para obter mais detalhes sobre as opções de configuração, consulte [`dependency-review-action`](https://github.com/actions/dependency-review-action#readme).
diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md
index 94b4b667e7..7358df27eb 100644
--- a/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md
+++ b/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md
@@ -1,5 +1,5 @@
 ---
-title: Understanding billing for GitHub Codespaces
+title: Entender a cobrança para o GitHub Codespaces
 intro: 'Saiba como seu uso de {% data variables.product.prodname_github_codespaces %} é cobrado.'
 versions:
   fpt: '*'
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md
index a4a36981db..9e5baa3e37 100644
--- a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md
@@ -1,5 +1,5 @@
 ---
-title: Using GitHub Codespaces for pull requests
+title: Usando o GitHub Codespaces para pull requests
 shortTitle: Pull requests
 intro: 'Você pode usar {% data variables.product.prodname_github_codespaces %} no seu fluxo de trabalho de desenvolvimento para criar pull requests, revisar pull requests e resolver comentários de revisão.'
 product: '{% data reusables.gated-features.codespaces %}'
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md
index 1dfd457058..9e0c70e564 100644
--- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md
@@ -1,5 +1,5 @@
 ---
-title: Managing encrypted secrets for your repository and organization for GitHub Codespaces
+title: Gerenciar segredos criptografados para o seu repositório e organização para o GitHub Codespaces
 shortTitle: Segredos criptografados
 intro: 'Os segredos criptografados permitem que você armazene informações confidenciais na sua organização, repositório ou {% data variables.product.prodname_github_codespaces %}.'
 product: '{% data reusables.gated-features.codespaces %}'
diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
index 29a12bdbdd..b61b8c0783 100644
--- a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
+++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
@@ -75,6 +75,22 @@ Você pode atualizar o valor de um segredo existente, bem como alterar quais rep
 1. Em "Segredos dos codespaces", à direita do segredo que você deseja excluir, clique em **Excluir**. ![Botão "Excluir"](/assets/images/help/settings/codespaces-secret-delete-button.png)
 1. Leia o alerta e clique em **OK**. ![Confirmação para excluir um segredo](/assets/images/help/settings/codespaces-secret-delete-warning.png)
 
+## Usar segredos
+
+A secret is exported as an environment variable into the user's terminal session.
+
+  ![Displaying the value of an exported secret in the terminal](/assets/images/help/codespaces/exported-codespace-secret.png)
+
+You can use secrets in a codespace after the codespace is built and is running. For example, a secret can be used:
+
+* When launching an application from the integrated terminal or ssh session.
+* Within a dev container lifecycle script that is run after the codespace is running. For more information about dev container lifecycle scripts, see the documentation on containers.dev: [Specification](https://containers.dev/implementors/json_reference/#lifecycle-scripts).
+
+Codespace secrets cannot be used during:
+
+* Codespace build time (that is, within a Dockerfile or custom entry point).
+* Within a dev container feature. For more information, see the `features` attribute in the documentation on containers.dev: [Specification](https://containers.dev/implementors/json_reference/#general-properties).
+
 ## Leia mais
 
 - "[Gerenciando segredos criptografados para o seu repositório e organização para {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)"
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md
index 16372cc13a..3ad2a03f3b 100644
--- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -1,6 +1,6 @@
 ---
 title: 'Configurando seu repositório para {% data variables.product.prodname_github_codespaces %}'
-shortTitle: Setting up your repository
+shortTitle: Configurando seu repositório
 allowTitleToDifferFromFilename: true
 intro: 'Aprenda como dar os primeiros passos com {% data variables.product.prodname_github_codespaces %}, incluindo a configuração para linguagens específicas.'
 product: '{% data reusables.gated-features.codespaces %}'
diff --git a/translations/pt-BR/content/codespaces/troubleshooting/github-codespaces-logs.md b/translations/pt-BR/content/codespaces/troubleshooting/github-codespaces-logs.md
index 6cdaffd6ab..c3e4288382 100644
--- a/translations/pt-BR/content/codespaces/troubleshooting/github-codespaces-logs.md
+++ b/translations/pt-BR/content/codespaces/troubleshooting/github-codespaces-logs.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Codespaces logs
+title: Logs do GitHub Codespaces
 intro: 'Visão geral dos locais de registros usados por {% data variables.product.prodname_github_codespaces %}.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
diff --git a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
index 45078be127..e596d22d49 100644
--- a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
+++ b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
@@ -34,8 +34,8 @@ Quando você bloqueia um usuário:
 - Você é removido como colaborador em seus repositórios
 - O patrocínio dele para você é cancelado
 - Qualquer convite pendente de sucessor de uma conta ou de repositório para ou de um usuário bloqueado é cancelado
-- O usuário é removido como colaborador de todos os Quadros de Projeto & Projetos (beta) pertencentes a você
-- Você é removido como colaborador de todos os Quadros de Projeto & Projetos (beta) pertencentes ao usuário
+- The user is removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by you
+- You are removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by the user
 
 Depois que você bloqueou um usuário, ele não pode:
 - Enviar notificações a você, incluindo por [@menção](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) do seu nome de usuário
@@ -48,8 +48,8 @@ Depois que você bloqueou um usuário, ele não pode:
 - Faz referência cruzada de seus repositórios em comentários
 - Bifurque, inspecione, fixe ou favorite seus repositórios
 - Patrocinar você
-- Adicione você como colaborador nos seus Quadros de Projetos & Projetos (beta)
-- Faça as alterações nos seus Quadros de Projetos & Projetos (beta)
+- Add you as a collaborator on their projects and {% data variables.projects.projects_v1_boards %}
+- Make changes to your public projects and {% data variables.projects.projects_v1_boards %}
 
 Nos repositórios que você possui, os usuários bloqueados também não podem:
 - Criar problemas
diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
index 51a8cae861..e1d378c087 100644
--- a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
+++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
@@ -43,7 +43,7 @@ X-Accepted-OAuth-Scopes: user
 | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion not ghae %}
 | **`(sem escopo)`**       | Concede acesso somente leitura a informações públicas (incluindo informações do perfil do usuário, informações do repositório e gists){% endif %}{% ifversion ghes or ghae %}
 | **`site_admin`**         | Concede acesso de administrador aos pontos de extremidades da API de administração [{% data variables.product.prodname_ghe_server %}](/rest/reference/enterprise-admin).{% endif %}
-| **`repo`**               | Concede acesso total aos repositórios, incluindo repositórios privados. Isso inclui acesso de leitura/gravação ao código, status do commit, repositório e projetos da organização, convites, colaboradores, adição de associações de equipe, status de implantação e webhooks de repositórios para repositórios e organizações. Também concede capacidade para gerenciar projetos de usuário.                                                                                                                                                                                         |
+| **`repo`**               | Grants full access to public{% ifversion ghec or ghes or ghae %}, internal,{% endif %} and private repositories including read and write access to code, commit statuses, repository invitations, collaborators, deployment statuses, and repository webhooks. **Note**: In addition to repository related resources, the `repo` scope also grants access to manage organization-owned resources including projects, invitations, team memberships and webhooks. This scope also grants the ability to manage projects owned by users.                                                |
 | &emsp;`repo:status`      | Concede acesso de leitura/gravaçãopara fazer commit de status em {% ifversion fpt %}repositórios públicos, privados e internos{% elsif ghec or ghes %} privados e internos{% elsif ghae %}privados e internos{% endif %}. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso a status de compromisso de repositórios privados *sem* conceder acesso ao código.                                                                                                                                                                                            |
 | &emsp;`repo_deployment`  | Concede acesso aos [status da implementação](/rest/reference/repos#deployments) para {% ifversion not ghae %}público{% else %}interno{% endif %} e repositórios privados. Este escopo só é necessário para conceder a outros usuários ou serviços acesso aos status de implantação, *sem* conceder acesso ao código.{% ifversion not ghae %}
 | &emsp;`public_repo`      | Limita o acesso a repositórios públicos. Isso inclui acesso de leitura/gravação em código, status de commit, projetos de repositório, colaboradores e status de implantação de repositórios e organizações públicos. Também é necessário para repositórios públicos marcados como favoritos.{% endif %}
@@ -65,8 +65,8 @@ X-Accepted-OAuth-Scopes: user
 | &emsp;`read:user`        | Concede acesso para ler as informações do perfil de um usuário.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
 | &emsp;`usuário:email`    | Concede acesso de leitura aos endereços de e-mail de um usuário.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | &emsp;`user:follow`      | Concede acesso para seguir ou deixar de seguir outros usuários.{% ifversion projects-oauth-scope %}
-| **`project`**            | Concede acesso de leitura/gravação aos projetos de usuário e organização (beta).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| &emsp;`read:project`     | Concede acesso somente de leitura a usuários e projetos de organizações (beta).{% endif %}
+| **`project`**            | Grants read/write access to user and organization {% data variables.projects.projects_v2 %}.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| &emsp;`read:project`     | Grants read only access to user and organization {% data variables.projects.projects_v2 %}.{% endif %}
 | **`delete_repo`**        | Concede acesso para excluir repositórios administráveis.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
 | **`write:discussion`**   | Permite acesso de leitura e gravação para discussões da equipe.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
 | &emsp;`leia:discussion`  | Permite acesso de leitura para discussões em equipe.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
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 74045caad8..8f39d513fa 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
@@ -892,10 +892,10 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data
 - Webhooks da organização
 - {% data variables.product.prodname_github_apps %} com a permissão `repository_projects` ou `organization_projects`
 
-{% ifversion fpt or ghec %}
+{% ifversion projects-v2 %}
 {% note %}
 
-**Observação**: Este evento não ocorre para Projetos (beta).
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
 
 {% endnote %}
 {% endif %}
@@ -924,10 +924,10 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data
 - Webhooks da organização
 - {% data variables.product.prodname_github_apps %} com a permissão `repository_projects` ou `organization_projects`
 
-{% ifversion fpt or ghec %}
+{% ifversion projects-v2 %}
 {% note %}
 
-**Observação**: Este evento não ocorre para Projetos (beta).
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
 
 {% endnote %}
 {% endif %}
@@ -954,6 +954,14 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data
 - Webhooks da organização
 - {% data variables.product.prodname_github_apps %} com a permissão `repository_projects` ou `organization_projects`
 
+{% ifversion projects-v2 %}
+{% note %}
+
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
+
+{% endnote %}
+{% endif %}
+
 ### Objeto da carga do webhook
 
 {% data reusables.webhooks.project_column_properties %}
@@ -972,11 +980,11 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data
 
 {% note %}
 
-**Observação:** Os eventos de Webhook para Projetos (beta) estão atualmente no beta e sujeitos a alterações. Para compartilhar feedback sobre webhooks de projetos (beta) com {% data variables.product.product_name %}, veja os [Webhooks de projetos (beta) de feedback](https://github.com/github/feedback/discussions/17405).
+**Note:** Webhook events for {% data variables.projects.projects_v2 %} are currently in beta and subject to change. To share feedback about {% data variables.projects.projects_v2 %} webhooks with {% data variables.product.product_name %}, see the [Projects webhook feedback discussion](https://github.com/github/feedback/discussions/17405).
 
 {% endnote %}
 
-Atividade relacionada aos itens em um projeto (beta) {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte "[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects).
+Activity related to items in a {% data variables.projects.project_v2 %}. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte "[Sobre {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects).
 
 ### Disponibilidade
 
@@ -988,7 +996,7 @@ Atividade relacionada aos itens em um projeto (beta) {% data reusables.webhooks.
 | Tecla              | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                                                  |
 | ------------------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `Ação`             | `string` | A ação que foi executada no item do projeto. Pode ser: `archived`, `converted`, `created`, `edited`, `restored`, `deleted` ou `reordered`.                                                                                                                                                                                                                                                                 |
-| `projects_v2_item` | `objeto` | O item do projeto em si. Para encontrar mais informações sobre o item do projeto, você pode usar `node_id` (o ID do nó do item do projeto) e `project_node_id` (o ID do nó do projeto) para consultar informações na API do GraphQL. Para obter mais informações, consulte[Usando a API para gerenciar projetos (beta)](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)". |
+| `projects_v2_item` | `objeto` | O item do projeto em si. Para encontrar mais informações sobre o item do projeto, você pode usar `node_id` (o ID do nó do item do projeto) e `project_node_id` (o ID do nó do projeto) para consultar informações na API do GraphQL. For more information, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." |
 | `alterações`       | `objeto` | As alterações no item do projeto.                                                                                                                                                                                                                                                                                                                                                                          |
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
diff --git a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
index 3365a78f9f..71758d94c2 100644
--- a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
+++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
@@ -21,7 +21,7 @@ Você pode usar discussões no repositório para discutir tópicos específicos
 
 Você não precisa fechar uma discussão como você fecha um problema ou um pull request.
 
-If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who has access to the repository can create and participate in discussions for the repository. Se um proprietário da organização permitir que {% data variables.product.prodname_discussions %} para uma organização, qualquer pessoa que possa visualizar o repositório de origem pode criar uma discussão na organização.
+Se o administrador de um repositório ou mantenedor do projeto habilitar {% data variables.product.prodname_discussions %} para um repositório, qualquer pessoa que tiver acesso ao repositório poderá criar e participar de discussões do repositório. Se um proprietário da organização permitir que {% data variables.product.prodname_discussions %} para uma organização, qualquer pessoa que possa visualizar o repositório de origem pode criar uma discussão na organização.
 
 Os administradores de repositório e mantenedores de projetos podem gerenciar as discussões e categorias de discussão em um repositório e fixar discussões para aumentar a visibilidade da discussão. Os moderadores e colaboradores podem marcar comentários como respostas, travar discussões e converter problemas em discussões. Da mesma forma, para discussões na organização, a função de um usuário no repositório de origem determina como um usuário pode interagir com as discussões da organização. Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
@@ -29,7 +29,7 @@ Para obter mais informações sobre o gerenciamento das discussões, consulte "[
 
 ## Sobre as enquetes
 
-Você pode criar enquetes na categoria de enquetes para medir o interesse em novas idéias e na direção do projeto. Anyone with read access to your repository can create polls, vote in polls, and view their results.{% ifversion fpt or ghec %} Signed out users can view the results of polls in public repositories.{% endif %}
+Você pode criar enquetes na categoria de enquetes para medir o interesse em novas idéias e na direção do projeto. Qualquer pessoa com acesso de leitura ao seu repositório pode criar pesquisas, votar em enquetes e ver seus resultados.{% ifversion fpt or ghec %} Os usuários desconectados podem visualizar os resultados das enquetes em repositórios públicos.{% endif %}
 
 As enquetes exigem uma pergunta e pelo menos duas opções. Você pode adicionar um máximo de oito opções e as opções podem conter, no máximo, 128 caracteres.
 
@@ -70,5 +70,5 @@ Você pode compartilhar seus comentários sobre {% data variables.product.prodna
 - "[Sobre escrita e formatação em {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)"
 - "[Pesquisar discussões](/search-github/searching-on-github/searching-discussions)"
 - "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
-- "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)"{% ifversion fpt or ghec %}
-- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"{% endif %}
+- "[Moderando comentários e conversas](/communities/moderating-comments-and-conversations)"{% ifversion fpt or ghec %}
+- "[Mantendo sua segurança em {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"{% endif %}
diff --git a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index 9a8373ce9d..d6693692ef 100644
--- a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -14,7 +14,7 @@ shortTitle: Participar da discussão
 
 Além de iniciar ou visualizar discussões e enquetes, você pode fazer comentários em resposta ao comentário original do autor da discussão. Você também pode criar um tópico de comentário respondendo a um comentário individual feito por outro integrante da comunidade dentro da discussão e reagir aos comentários com emoji.
 
-{% ifversion fpt or ghec %}You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)."{% endif %}
+{% ifversion fpt or ghec %}Você pode bloquear os usuários e informar conteúdo disruptivo para manter um ambiente seguro e agradável para você mesmo em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Mantendo sua segurança em {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)."{% endif %}
 
 ## Pré-requisitos
 
diff --git a/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md
index c7f195f4d3..682e93c243 100644
--- a/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md
+++ b/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md
@@ -21,7 +21,7 @@ Para mais informações sobre como abrir um problema e fazer referências cruzad
 
 Você pode criar e participar de discussões, problemas e pull requests, dependendo do tipo de conversa que você gostaria de ter.
 
-Você pode usar {% data variables.product.prodname_discussions %} para discutir o panorama geral, levantamento de hipóteses e desenvolver detalhes específicos de um projeto antes de vinculá-lo a um problema, que poderá ter o escopo definido. {% data variables.product.prodname_discussions %} is useful for teams in a number of scenarios.
+Você pode usar {% data variables.product.prodname_discussions %} para discutir o panorama geral, levantamento de hipóteses e desenvolver detalhes específicos de um projeto antes de vinculá-lo a um problema, que poderá ter o escopo definido. {% data variables.product.prodname_discussions %} é útil para equipes em vários cenários.
 - Você está na fase de descoberta de um projeto e ainda está aprendendo qual direção a sua equipe quer acessar
 - Você deseja coletar comentários de uma comunidade mais ampla sobre um projeto
 - Você deseja manter correções de erros, solicitações de recursos e conversas gerais separadas
@@ -33,7 +33,7 @@ Os problemas são úteis para discutir detalhes específicos de um projeto, como
 
 ## Seguindo as diretrizes de contribuição
 
-Before you open a discussion in a repository, check to see if the repository has contributing guidelines. O arquivo CONTRIBUTING inclui informações sobre como o mantenedor do repositório gostaria que você contribuísse com ideias para o projeto.
+Antes de abrir uma discussão em um repositório, verifique se o repositório tem diretrizes de contribuição. O arquivo CONTRIBUTING inclui informações sobre como o mantenedor do repositório gostaria que você contribuísse com ideias para o projeto.
 
 Para obter mais informações, consulte "[Configurando seu projeto para Contribuições Úteis](/communities/setting-up-your-project-for-healthy-contributions)."
 
diff --git a/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
index 3e65a716a1..9f6a1b1801 100644
--- a/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
+++ b/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
@@ -15,11 +15,11 @@ Os contribuidores mais úteis dos últimos 30 dias são destacados no painel de
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
-1. Compare the list of contributors with their access permissions to the repository or, for organization discussions, to the source repository to see who qualifies to moderate the discussion. ![Screenshot of most helpful contributors](/assets/images/help/discussions/most-helpful.png)
+1. Comparar a lista de contribuidores com suas permissões de acesso ao repositório, ou para discussões na organização com o repositório de origem para ver quem se qualifica para moderar a discussão. ![Captura de tela dos colaboradores mais úteis](/assets/images/help/discussions/most-helpful.png)
 
 ## Etapa 2: Reveja os níveis de permissão para {% data variables.product.prodname_discussions %}
 
-People with triage permissions for a repository can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Da mesma forma, as pessoas com permissões de triagem para o repositório de origem para discussões da organização podem moderar as discussões da organização. Para obter mais informações, consulte "[Moderação de discussões](/discussions/managing-discussions-for-your-community/moderating-discussions)".
+Pessoas com permissões de triagem para um repositório podem ajudar a moderar as discussões de um repositório, marcando comentários como respostas, bloqueando discussões que já não são úteis ou prejudicam a comunidade e convertendo os problemas em discussões quando uma ideia ainda está nos primeiros estágios de desenvolvimento. Da mesma forma, as pessoas com permissões de triagem para o repositório de origem para discussões da organização podem moderar as discussões da organização. Para obter mais informações, consulte "[Moderação de discussões](/discussions/managing-discussions-for-your-community/moderating-discussions)".
 
 Para obter mais informações sobre os níveis de permissão do repositório e {% data variables.product.prodname_discussions %}, consulte "[Níveis de permissões do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)".
 
diff --git a/translations/pt-BR/content/discussions/index.md b/translations/pt-BR/content/discussions/index.md
index f394d207a6..443a9cc956 100644
--- a/translations/pt-BR/content/discussions/index.md
+++ b/translations/pt-BR/content/discussions/index.md
@@ -1,7 +1,7 @@
 ---
 title: Documentação de discussões do GitHub
 shortTitle: GitHub Discussions
-intro: '{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an{% ifversion fpt or ghec %} open source or{% endif %} internal project. Os integrantes da comunidade podem perguntar e responder a perguntas, compartilhar atualizações, ter conversas abertas e acompanhar decisões que afetam o modo de trabalho da comunidade.'
+intro: '{% data variables.product.prodname_discussions %} é um fórum de comunicação colaborativo para a comunidade sobre{% ifversion fpt or ghec %} código aberto ou{% endif %} projeto interno. Os integrantes da comunidade podem perguntar e responder a perguntas, compartilhar atualizações, ter conversas abertas e acompanhar decisões que afetam o modo de trabalho da comunidade.'
 introLinks:
   quickstart: /discussions/quickstart
 featuredLinks:
diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
index 4387563d58..b7855f5182 100644
--- a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
+++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
@@ -42,7 +42,7 @@ Cada categoria deve ter um nome e um pareamento de emojis únicos e pode ser aco
 
 Você pode editar uma categoria para alterar o emoji, título, descrição e formato da discussão.
 
-1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to edit a category.
+1. No {% data variables.product.product_location %}, acesse a página principal do repositório ou organização onde você deseja editar uma categoria.
 {% data reusables.discussions.discussions-tab %}
 1. À direita de uma categoria na lista, clique em {% octicon "pencil" aria-label="The pencil icon" %}. ![Botão de editar à direita da categoria na lista de categorias para um repositório](/assets/images/help/discussions/click-edit-for-category.png)
 1. {% data reusables.discussions.edit-category-details %}![Editar emoji, título, descrição e formato de discussão para uma categoria existente](/assets/images/help/discussions/edit-existing-category-details.png)
@@ -52,7 +52,7 @@ Você pode editar uma categoria para alterar o emoji, título, descrição e for
 
 Ao você excluir uma categoria, {% data variables.product.product_name %} moverá todas as discussões da categoria excluída para uma categoria existente que você escolher.
 
-1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to delete a category.
+1. Em {% data variables.product.product_location %}, acesse a página principal do repositório ou organização onde você deseja excluir uma categoria.
 {% data reusables.discussions.discussions-tab %}
 1. À direita de uma categoria na lista, clique em {% octicon "trash" aria-label="The trash icon" %}. ![Botão de lixeira à direita da categoria na lista de categorias para um repositório](/assets/images/help/discussions/click-delete-for-category.png)
 1. Use o menu suspenso e escolha uma nova categoria para qualquer discussão na categoria que você está excluindo. ![Menu suspenso para escolher nova categoria ao excluir uma categoria existente](/assets/images/help/discussions/choose-new-category.png)
diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions.md
index 6dce42c323..ce81019a8e 100644
--- a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions.md
+++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -16,7 +16,7 @@ redirect_from:
 
 Os proprietários da organização podem escolher as permissões necessárias para criar uma discussão para repositórios pertencentes à organização. Da mesma forma, para escolher as permissões necessárias para criar uma discussão na organização, os proprietários da organização podem alterar as permissões necessárias no repositório de origem. Para obter mais informações, consulte "[Gerenciar a criação de discussões para repositórios na sua organização](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)".
 
-Como mantenedor de discussões, você pode criar recursos da comunidade para incentivar discussões alinhadas com o objetivo geral do projeto e manter um fórum aberto amigável para os colaboradores. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and{% endif %} "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
+Como mantenedor de discussões, você pode criar recursos da comunidade para incentivar discussões alinhadas com o objetivo geral do projeto e manter um fórum aberto amigável para os colaboradores. Criar{% ifversion fpt or ghec %} um código de conduta ou{% endif %} diretrizes de contribuição para os colaboradores a seguir ajudarão a facilitar um fórum colaborativo e produtivo. Para obter mais informações sobre como criar recursos da comunidade, consulte{% ifversion fpt or ghec %} "[Adicionando um código de conduta ao seu projeto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project), e{% endif %} "[Definindo diretrizes para contribuidores do repositório](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)".
 
 Quando uma discussão fornece uma ideia ou um erro que está pronto para ser trabalhado, você pode criar um novo problema a partir de uma discussão. Para obter mais informações, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)".
 
@@ -74,7 +74,7 @@ Editar uma discussão fixada não irá alterar a categoria da discussão. Para o
 
 ## Transferir uma discussão
 
-Para transferir uma discussão, você precisa ter permissão de criar discussões no repositório, em que você deseja transferir a discussão. Se você deseja transferir uma discussão para uma organização, você deve ter permissão para criar discussões no repositório de origem para as discussões da organização. Você somente pode transferir discussões entre repositórios pertencentes à mesma conta de usuário ou organização. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository.
+Para transferir uma discussão, você precisa ter permissão de criar discussões no repositório, em que você deseja transferir a discussão. Se você deseja transferir uma discussão para uma organização, você deve ter permissão para criar discussões no repositório de origem para as discussões da organização. Você somente pode transferir discussões entre repositórios pertencentes à mesma conta de usuário ou organização. Você não pode transferir uma discussão de um repositório{% ifversion ghec or ghes %} privado ou interno{% endif %} para um repositório público.
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
index f3bab3a4f4..e75dadfbb9 100644
--- a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
+++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
@@ -1,6 +1,6 @@
 ---
 title: Moderar discussões
-intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.'
+intro: 'Você pode promover uma colaboração saudável marcando comentários como respostas, bloqueando ou desbloqueando discussões, convertendo problemas em discussões e editando ou excluindo comentários, discussões e categorias que não estão alinhadas com o código de conduta da sua comunidade{% ifversion fpt or ghec %}, organização{% elsif ghes > 3.5 %} as diretrizes de contribuição da organização{% endif %}.'
 permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
 versions:
   feature: discussions
@@ -9,7 +9,7 @@ versions:
 
 ## Sobre a moderação de discussões
 
-{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Da mesma forma, se você tem permissão de triagem para o repositório de origem para discussões na organização, é possível moderar as discussões dessa organização.
+{% data reusables.discussions.about-discussions %} Se você tiver permissões de triagem para um repositório, você poderá ajudar a moderar as discussões de um repositório marcando comentários como respostas, bloqueando discussões que não são mais úteis ou que prejudicam a comunidade e convertendo os problemas em discussões quando uma ideia ainda está nos primeiros estágios de desenvolvimento. Da mesma forma, se você tem permissão de triagem para o repositório de origem para discussões na organização, é possível moderar as discussões dessa organização.
 
 ## Marcar um comentário como uma resposta
 
diff --git a/translations/pt-BR/content/discussions/quickstart.md b/translations/pt-BR/content/discussions/quickstart.md
index 0eeee67e17..9b2b35bd51 100644
--- a/translations/pt-BR/content/discussions/quickstart.md
+++ b/translations/pt-BR/content/discussions/quickstart.md
@@ -10,13 +10,13 @@ shortTitle: QuickStart
 
 ## Introdução
 
-{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source or internal project. As discussões são para conversas que precisam ser transparentes e acessíveis, mas não precisam ser rastreadas em um quadro de projeto e não estão relacionadas ao código, diferente de {% data variables.product.prodname_github_issues %}. As discussões permitem uma conversa fluida e aberta em um fórum público.
+{% data variables.product.prodname_discussions %} é um fórum de comunicação colaborativo para a comunidade sobre código aberto ou projeto interno. As discussões são para conversas que precisam ser transparentes e acessíveis, mas não precisam ser rastreadas em um quadro de projeto e não estão relacionadas ao código, diferente de {% data variables.product.prodname_github_issues %}. As discussões permitem uma conversa fluida e aberta em um fórum público.
 
 As discussões dão um espaço para conversas mais colaborativas, conectando-se e dando uma área mais centralizada para se conectar e encontrar informações.
 
 ## Habilitar {% data variables.product.prodname_discussions %} no seu repositório
 
-Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public{% ifversion ghes > 3.5 %}, internal{% endif %} and private repositories. The visibility of a discussion is inherited from the repository the discussion is created in.
+Os proprietários de repositórios e pessoas com acesso de gravação podem habilitar {% data variables.product.prodname_discussions %} para uma comunidade em seus repositórios privados {% ifversion ghes > 3.5 %}, internos{% endif %} e privados. A visibilidade de uma discussão é herdada do repositório em que a discussão é criada.
 
 Ao habilitar {% data variables.product.prodname_discussions %} pela primeira vez, você será convidado a configurar um post de boas-vindas.
 
@@ -41,7 +41,7 @@ Você pode dar as boas-vindas à sua comunidade e apresentar uma nova forma de s
 
 ## Configurar diretrizes da comunidade para colaboradores
 
-Para discussões de repositório, você pode definir diretrizes de contribuição para incentivar os colaboradores a terem conversas significativas e úteis que sejam relevantes para o repositório. Você também pode atualizar o README do repositório para comunicar as expectativas quando os colaboradores devem abrir um problema ou discussão. For more information about providing guidelines for your project, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and{% endif %} "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+Para discussões de repositório, você pode definir diretrizes de contribuição para incentivar os colaboradores a terem conversas significativas e úteis que sejam relevantes para o repositório. Você também pode atualizar o README do repositório para comunicar as expectativas quando os colaboradores devem abrir um problema ou discussão. Para obter mais informações sobre como fornecer diretrizes para o seu projeto, consulte{% ifversion fpt or ghec %} "[Adicionando um código de conduta ao seu projeto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" e{% endif %} "[Configurando seu projeto para contribuições saudáveis](/communities/setting-up-your-project-for-healthy-contributions)".
 
 Para discussões na organização, você compartilha informações sobre como se envolver com a sua organização criando um perfil README da organização. Para obter mais informações, consulte "[Personalizar o perfil da sua organização](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)".
 
@@ -61,7 +61,7 @@ Qualquer usuário autenticado que possa visualizar um repositório pode criar um
 
 Os proprietários dos repositórios e pessoas com acesso de gravação ao repositório podem criar novas categorias para manter as discussões organizadas. Da mesma forma, uma vez que as discussões da organização são baseadas em um repositório de origem, os proprietários de repositórios e as pessoas com acesso de gravação ao repositório de origem podem criar novas categorias para discussões da organização.
 
-Collaborators participating in and creating new discussions can group discussions into the most relevant existing categories. As discussões também podem ser recategorizadas depois que forem criadas. Para obter mais informações, consulte "[Gerenciando categorias para discussões](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)".
+Os colaboradores que participam e criam novas discussões podem agrupar discussões nas categorias existentes mais relevantes. As discussões também podem ser recategorizadas depois que forem criadas. Para obter mais informações, consulte "[Gerenciando categorias para discussões](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)".
 
 {% data reusables.discussions.you-can-label-discussions %}
 
diff --git a/translations/pt-BR/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md b/translations/pt-BR/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
new file mode 100644
index 0000000000..d79f280639
--- /dev/null
+++ b/translations/pt-BR/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
@@ -0,0 +1,45 @@
+---
+title: Getting started with GitHub Community Exchange
+shortTitle: Começar
+intro: 'Learn how to access {% data variables.product.prodname_community_exchange %} and submit your repository.'
+versions:
+  fpt: '*'
+---
+
+## Introdução
+
+{% data reusables.education.about-github-community-exchange-intro %} {% data variables.product.prodname_community_exchange %} can help you make your first open source contribution or grow your own open source project.
+
+For more information about how {% data variables.product.prodname_community_exchange %} can help you as a student, see "[About {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)."
+
+## Accessing {% data variables.product.prodname_community_exchange %}
+
+{% data reusables.education.access-github-community-exchange %}
+
+## Finding interesting repositories
+
+You can browse repositories submitted to {% data variables.product.prodname_community_exchange %} from the gallery page.
+
+As you think about what open source repositories may be interesting, consider if you're wanting to learn or collaborate, or if there are particular topics or languages that could be a good starting point.
+
+When exploring repositories in the {% data variables.product.prodname_community_exchange %} gallery, you can filter available repositories by purpose, topics, or languages, and search for repositories by name and description. You can sort the list of repositories in the gallery by submission date, or by the number of stars, forks, or issues a repository has.
+
+![Screenshot of Community Exchange search box and dropdown filters](/assets/images/help/education/community-exchange-search-and-filter.png)
+
+## Starring repositories
+
+You can star repositories listed in the {% data variables.product.prodname_community_exchange %} gallery. Starring makes it easy to find a repository in the gallery again later. Marcar um repositório com estrelas também demonstra apreciação ao trabalho do mantenedor de repositório.
+
+Repository listings in the {% data variables.product.prodname_community_exchange %} gallery can be sorted on the number of stars a repository has.
+
+To star a repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to star, and click {% octicon "star" aria-label="The star icon" %} **Star** button found right by its name.
+
+## Reporting abuse
+
+The {% data variables.product.prodname_community_exchange %} community moderates repository submissions. You can report abusive repositories, spammy, or disruptive content at any time.
+
+To report an abusive repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to report, click the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down right by its name, then click {% octicon "report" aria-label="The report symbol" %} **Report abuse**.
+
+## Leia mais
+
+- "[Sobre {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)"
diff --git a/translations/pt-BR/content/education/contribute-with-github-community-exchange/index.md b/translations/pt-BR/content/education/contribute-with-github-community-exchange/index.md
new file mode 100644
index 0000000000..caf08352b6
--- /dev/null
+++ b/translations/pt-BR/content/education/contribute-with-github-community-exchange/index.md
@@ -0,0 +1,12 @@
+---
+title: Contribute with GitHub Community Exchange
+shortTitle: '{% data variables.product.prodname_community_exchange %}'
+intro: 'With {% data variables.product.prodname_community_exchange %}, you can use {% data variables.product.product_name %} to contribute to open source and build your portfolio.'
+versions:
+  fpt: '*'
+children:
+  - /getting-started-with-github-community-exchange
+  - /submitting-your-repository-to-github-community-exchange
+  - /managing-your-submissions-to-github-community-exchange
+---
+
diff --git a/translations/pt-BR/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md b/translations/pt-BR/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
new file mode 100644
index 0000000000..6c04729a1b
--- /dev/null
+++ b/translations/pt-BR/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
@@ -0,0 +1,24 @@
+---
+title: Managing your submissions to GitHub Community Exchange
+shortTitle: Manage your submissions
+intro: 'You can manage the purpose, topics, and offers assigned to each of your repositories in the {% data variables.product.prodname_community_exchange %} gallery, or delete your repository submissions.'
+versions:
+  fpt: '*'
+---
+
+## About your submissions
+
+During the {% data variables.product.prodname_community_exchange %} submission process, you will choose a purpose, topics, and offers for your repository. Once a repository has been submitted to {% data variables.product.prodname_community_exchange %}, it will be published with these details. For more information, see "[Submitting your repository to GitHub Community Exchange](/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange)."
+
+After you've submitted, you can still edit the topics and offers associated with your repository. You can also update the purpose of your repository by changing the corresponding topic(s). Para obter mais informações, consulte "[Classificar seu repositório com tópicos](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics)".
+
+The language associated with your repository is the primary language used and is automatically determined by {% data variables.product.prodname_dotcom %}. For more information, see "[About repository languages](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages)."
+
+The {% data variables.product.prodname_community_exchange %} community moderates all repository submissions.
+
+## Managing your submissions
+
+1. From your {% data variables.product.prodname_global_campus %} dashboard, navigate to the {% data variables.product.prodname_community_exchange %} home page.
+1. Above the list of repositories, click the **Submissions** tab. ![Screenshot of the Submissions tab](/assets/images/help/education/community-exchange-submissions-tab.png)
+1. Optionally, edit your submitted repository. To the right of the repository you want to edit, click {% octicon "pencil" aria-label="The edit icon" %} to go directly to your repository homepage. From there, you can update the purpose, topics, and offers assigned to your repository.
+1. Optionally, delete a submitted repository from the gallery. To the right of the repository submission you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
diff --git a/translations/pt-BR/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md b/translations/pt-BR/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
new file mode 100644
index 0000000000..aeca760eab
--- /dev/null
+++ b/translations/pt-BR/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
@@ -0,0 +1,48 @@
+---
+title: Submitting your repository to GitHub Community Exchange
+shortTitle: Submit your repository
+intro: 'You can submit your repository to {% data variables.product.prodname_community_exchange %} for others to view or contribute to.'
+versions:
+  fpt: '*'
+---
+
+## About repository submissions
+
+Only public repositories owned by personal accounts can be submitted to {% data variables.product.prodname_community_exchange %}.
+
+There are three types of repository submissions:
+
+- **Learn.** A repository to share step-by-step instructions to build a project.
+- **Collaborate.** A repository seeking collaborators to work on a project.
+- **Learn and Collaborate.** A repository which is a combination of `Learn` and `Collaborate`.
+
+Consider what the main purpose of your repository is when choosing the type of submission for your repository.
+
+To promote your project and make it more discoverable to other students, you should assign one or more topics and {% data variables.product.prodname_student_pack %} offers to your repository. Para obter mais informações, consulte "[Classificar seu repositório com tópicos](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics)".
+
+Once a repository has been submitted to {% data variables.product.prodname_community_exchange %}, it will be published immediately with the purpose, topics, and offers you've chosen. The {% data variables.product.prodname_community_exchange %} community moderates all repository submissions.
+
+### Submission requirements
+
+Your repository must meet a minimum set of requirements for a submission to be accepted. During the submission process, if the submission criteria hasn't been met for your selected repository, you will be notified of the missing items.
+
+For a submission with a purpose of `Learn`, your repository must have:
+- A description.
+- A LEARN.md file to provide step-by-step instructions, with text and/or media, on how you built your project. Ideally, your LEARN.md file will deconstruct your project into small components and provide thorough details of each step, so that other students can code their project by following your instructions.
+- A README.md file to provide a detailed description of your project.
+
+For a submission with a purpose of `Collaborate`, your repository must have:
+- A description.
+- A README.md file to provide a detailed description of your project.
+- One or more issues for collaborators to work on.
+
+A good repository submission for both `Learn` and `Collaborate` purposes, is a repository that follows community standards. For more information, see "[About community profiles for public repositories](/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories)."
+
+## Submitting your repository
+
+1. From your {% data variables.product.prodname_global_campus %} dashboard, navigate to the {% data variables.product.prodname_community_exchange %} home page.
+1. Above the list of repositories, to the right of the search and dropdown filters, click **Add repository**. ![Screenshot of the Add repository button](/assets/images/help/education/community-exchange-submission-add-repo.png)
+1. Use the **What is the purpose of your submission?** drop-down menu and select one or more entries matching your submission. ![Screenshot of the purpose dropdown for a repository submission](/assets/images/help/education/community-exchange-repo-submission-purpose.png)
+1. Use the **Which repository would you like to use?** drop-down menu and select the repository for your submission. If the submission criteria hasn't been met, you will be notified of the missing items. ![Screenshot of the repository dropdown for a repository submission](/assets/images/help/education/community-exchange-repo-submission-repo.png)
+1. Use the **Which offers did you use for your project?** drop-down menu and select one or more entries matching your submission. ![Screenshot of the offers dropdown for a repository submission](/assets/images/help/education/community-exchange-repo-submission-offers.png)
+1. Click **Submit the project**.
diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange.md
index 263f2ef304..b5c3de787d 100644
--- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange.md
+++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange.md
@@ -1,14 +1,14 @@
 ---
 title: Sobre o GitHub Community Exchange
-intro: 'Como estudante, aprenda as habilidades que você precisa para contribuir para projetos de código aberto e faça crescer o seu próprio portfólio, com {% data variables.product.prodname_community_exchange %}.'
+intro: 'Learn the skills you need to contribute to open source projects and grow your own portfolio, with {% data variables.product.prodname_community_exchange %}.'
 versions:
   fpt: '*'
-shortTitle: Intercâmbio da comunidade
+shortTitle: About Community Exchange
 ---
 
 ## Sobre {% data variables.product.prodname_community_exchange %}
 
-{% data variables.product.prodname_community_exchange %} é uma comunidade estudantil dentro do portal de {% data variables.product.prodname_global_campus %}. Como estudante, é um lugar onde você pode obter exposição para o seu projeto e descobrir outros repositórios estudantis que precisam de colaboradores e mantenedores.
+{% data reusables.education.about-github-community-exchange-intro %}
 
 ![Captura de tela da página de da Community Exchange](/assets/images/help/education/community-exchange-page.png)
 
@@ -21,10 +21,10 @@ Você pode ajudar seus pares a aprender habilidades de código aberto, tornar-se
 - Envie um repositório para ensinar novas habilidades
 - Gerencie seus envios de repositórios
 
-Para acessar {% data variables.product.prodname_community_exchange %}, acesse seu painel de {% data variables.product.prodname_global_campus %} em https://education.github.com.
+For more information, see "[Contribute with GitHub Community Exchange](/education/contribute-with-github-community-exchange)."
 
-Se você é um aluno ou integrante do corpo docente de uma instituição de ensino credenciada, você pode solicitar benefícios de {% data variables.product.prodname_education %}, o que inclui acesso a {% data variables.product.prodname_community_exchange %} dentro de {% data variables.product.prodname_global_campus %}.
+{% data reusables.education.access-github-community-exchange %}
 
-- Se você é um estudante e ainda não participou de {% data variables.product.prodname_education %} , inscreva-se usando o [formulário de inscrição do aluno](https://education.github.com/discount_requests/student_application). Para obter mais informações, consulte "[Sobre o GitHub Education para alunos](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students)."
+## Leia mais
 
-- Se você é um educador e ainda não se participou de {% data variables.product.prodname_education %}, inscreva-se usando o [formulário de candidatura do professor](https://education.github.com/discount_requests/teacher_application). Para obter mais informações, consulte "[Sobre o GitHub Education para educadores](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount)".
+- "[Começar com {% data variables.product.prodname_community_exchange %}](/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange)"
diff --git a/translations/pt-BR/content/education/guides.md b/translations/pt-BR/content/education/guides.md
index 7dc2f17543..4ffcf02237 100644
--- a/translations/pt-BR/content/education/guides.md
+++ b/translations/pt-BR/content/education/guides.md
@@ -46,3 +46,5 @@ Participe da comunidade, receba treinamento de {% data variables.product.company
 - [{% data variables.product.prodname_education_community %}]({% data variables.product.prodname_education_forum_link %})
 - [Sobre Especialistas de campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts)
 - [Sobre Consultores de campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors)
+- [Sobre {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)
+- [Contribute with GitHub Community Exchange](/education/contribute-with-github-community-exchange)
diff --git a/translations/pt-BR/content/education/index.md b/translations/pt-BR/content/education/index.md
index 36df92ea3a..e6055e6018 100644
--- a/translations/pt-BR/content/education/index.md
+++ b/translations/pt-BR/content/education/index.md
@@ -27,6 +27,7 @@ versions:
 children:
   - /quickstart
   - /explore-the-benefits-of-teaching-and-learning-with-github-education
+  - /contribute-with-github-community-exchange
   - /manage-coursework-with-github-classroom
   - /guides
 ---
diff --git a/translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md b/translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md
index f5e8b9f6a7..4a1c0cb099 100644
--- a/translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md
+++ b/translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md
@@ -26,7 +26,17 @@ Este tutorial usa [o projeto Spoon-Knife](https://github.com/octocat/Spoon-Knife
 
 1. Acecsse o projeto `Spoon-Knife` em https://github.com/octocat/Spoon-Knife.
 2. Clique em **Bifurcação**. ![Botão Fork (Bifurcação)](/assets/images/help/repository/fork_button.png)
-1. {% data variables.product.product_name %} irá direcionar você para sua cópia (sua bifurcação) do repositório Spoon-Knife.
+3. Select an owner for the forked repository. ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
+4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
+5. Optionally, add a description of your fork. ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
+6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied. ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png)
+7. Click **Create fork**. ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png)
+
+{% note %}
+
+**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. Para obter mais informações, consulte "[Criar e excluir branches em seu repositório](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)".
+
+{% endnote %}
 
 ## Clonando uma bifurcação
 
diff --git a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md
index c373d044a2..36bc8a80f2 100644
--- a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md
@@ -34,7 +34,7 @@ Por exemplo, você pode usar bifurcações para propor alterações relacionadas
 
 ### Use o projeto de outra pessoa como ponto de partida para sua própria ideia.
 
-O software de código aberto baseia-se na ideia de que ao compartilhar códigos, podemos criar softwares melhores e mais confiáveis. For more information, see the "[About the Open Source Initiative](https://opensource.org/about)" on the Open Source Initiative.
+O software de código aberto baseia-se na ideia de que ao compartilhar códigos, podemos criar softwares melhores e mais confiáveis. Para obter mais informações, consulte "[Sobre a Iniciativa Open Source](https://opensource.org/about)" em Iniciativa Open Source.
 
 Para obter mais informações sobre a aplicação dos princípios de código aberto ao trabalho de desenvolvimento da sua organização em {% data variables.product.product_location %}, consulte o white paper de {% data variables.product.prodname_dotcom %} "[Uma introdução ao innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
 
@@ -57,7 +57,17 @@ Se ainda não o fez, primeiro [configure o Git](/articles/set-up-git). Lembre-se
 Você pode bifurcar um projeto para propor alterações no repositório upstream ou original. Nesse caso, uma boa prática é sincronizar regularmente sua bifurcação com o repositório upstream. Para isso, é necessário usar Git na linha de comando. Você pode praticar configurando o repositório upstream com o mesmo repositório [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) que você acabou de bifurcar.
 
 1. Em {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, acesse o repositório [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife).
-2. No canto superior direito da página, clique em **Fork** (Bifurcação). ![Botão Fork (Bifurcação)](/assets/images/help/repository/fork_button.png)
+2. In the top-right corner of the page, click **Fork**. ![Botão Fork (Bifurcação)](/assets/images/help/repository/fork_button.png)
+3. Select an owner for the forked repository. ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
+4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
+5. Optionally, add a description of your fork. ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
+6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied. ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png)
+7. Click **Create fork**. ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png)
+
+
+{% note %}
+
+**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}
 
 {% endwebui %}
 
diff --git a/translations/pt-BR/content/get-started/using-github/github-command-palette.md b/translations/pt-BR/content/get-started/using-github/github-command-palette.md
index 316e333784..91a555f3c1 100644
--- a/translations/pt-BR/content/get-started/using-github/github-command-palette.md
+++ b/translations/pt-BR/content/get-started/using-github/github-command-palette.md
@@ -39,8 +39,8 @@ Ao abrir a paleta de comando, ela mostra sua localização no canto superior esq
 {% note %}
 
 **Notas:**
-- Se você estiver editando o texto do Markdown, abra a paleta de comandos com <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows e Linux) ou <kbd>Comando</kbd>+<kbd>Opção</kbd>+<kbd>K</kbd> (Mac).
-- Se você estiver trabalhando em um projeto (beta), uma paleta de comandos específica do projeto será exibida no lugar. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
+- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).{% ifversion projects-v2 %}
+- If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."{% endif %}
 
 {% endnote %}
 
@@ -151,7 +151,7 @@ Estes comandos estão disponíveis em todos os escopos.
 | `Importar repositório`                 | Criar um novo repositório importando um projeto de outro sistema de controle de versão. Para obter mais informações, consulte "[Importando um repositório com o Importador do GitHub](/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)". |
 | `Novo gist`                            | Abra um novo gist. Para obter mais informações, consulte[Criando um gist](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)."                                                                                                                                                   |
 | `Nova organização`                     | Criar uma nova organização Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)".                                                                                                        |
-| `Novo projeto`                         | Criar um novo quadro de projeto. Para obter mais informações, consulte "[Criar um quadro de projeto](/issues/trying-out-the-new-projects-experience/creating-a-project)".                                                                                                                                           |
+| `Novo projeto`                         | Criar um novo quadro de projeto. Para obter mais informações, consulte "[Criar um quadro de projeto](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)".                                                                                                                            |
 | `Novo repositório`                     | Criar um novo repositório a partir do zero. Para obter mais informações, consulte "[Criar um novo repositório](/repositories/creating-and-managing-repositories/creating-a-new-repository)."                                                                                                                        |
 | `Alterar tema para <theme name>` | Mude diretamente para um tema diferente para a interface do usuário. Para obter mais informações, consulte "[Gerenciando as suas configurações de tema](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)".             |
 
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 11d0ca9692..86efb21489 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
@@ -146,7 +146,34 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod
 | <kbd>Alt</kbd> e clique                              | Alterna entre opções de recolhimento e expansão de todos os comentários de revisão desatualizados em uma pull request ao manter pressionada a tecla <kbd>Alt</kbd> e clicar em **Mostrar desatualizados** ou **Ocultar desatualizados**.                                                                                                                       |
 | Clique, em seguida <kbd>Shift</kbd> e clique         | Comente em várias linhas de uma pull request clicando em um número de linha, mantendo pressionado <kbd>Shift</kbd>, depois clique em outro número de linha. Para obter mais informações, consulte "[Comentando em uma pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." |
 
-## Quadros de projeto
+{% ifversion projects-v2 %}
+
+## {% data variables.projects.projects_v2_caps %}
+
+### Navigating a project
+
+| Atalho                                                                          | Descrição                    |
+| ------------------------------------------------------------------------------- | ---------------------------- |
+| <kbd>⌘</kbd>+<kbd>f</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>f</kbd> (Windows/Linux) | Focus filter field           |
+| <kbd>←</kbd>                                                                    | Move cell focus to the left  |
+| <kbd>→</kbd>                                                                    | Move cell focus to the right |
+| <kbd>↑</kbd>                                                                    | Move cell focus up           |
+| <kbd>↓</kbd>                                                                    | Move cell focus down         |
+
+### Manipulating a project
+
+| Atalho                                                                                                              | Descrição                             |
+| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
+| <kbd>Enter</kbd>                                                                                                    | Toggle edit mode for the focused cell |
+| <kbd>Escape</kbd>                                                                                                   | Cancel editing for the focused cell   |
+| <kbd>⌘</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Windows/Linux) | Open row actions menu                 |
+| <kbd>Shift</kbd>+<kbd>Space</kbd>                                                                                   | Selecionar item                       |
+| <kbd>Space (Espaço)</kbd>                                                                                           | Open selected item                    |
+| <kbd>e</kbd>                                                                                                        | Archive selected items                |
+
+{% endif %}
+
+## {% data variables.product.prodname_projects_v1_caps %}
 
 ### Mover uma coluna
 
@@ -201,12 +228,12 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod
 
 ## Notificações
 
-| Atalho                        | Descrição            |
-| ----------------------------- | -------------------- |
-| <kbd>E</kbd>                  | Marcar como pronto   |
-| <kbd>Shift</kbd>+<kbd>U</kbd> | Marcar como não lido |
-| <kbd>Shift</kbd>+<kbd>I</kbd> | Marca como lido      |
-| <kbd>Shift</kbd>+<kbd>M</kbd> | Cancelar assinatura  |
+| Atalho                        | Descrição             |
+| ----------------------------- | --------------------- |
+| <kbd>E</kbd>                  | Marcar como concluído |
+| <kbd>Shift</kbd>+<kbd>U</kbd> | Marcar como não lido  |
+| <kbd>Shift</kbd>+<kbd>I</kbd> | Marcar como lido      |
+| <kbd>Shift</kbd>+<kbd>M</kbd> | Cancelar assinatura   |
 
 ## gráfico de rede
 
diff --git a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
index ceaf3207ab..aba167c056 100644
--- a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
+++ b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -16,11 +16,7 @@ topics:
   - Pull requests
 ---
 
-{% warning %}
-
-**Aviso:** Se você anexar um arquivo a um pedido ou comentário de problema, qualquer pessoa poderá ver a URL anônima sem autenticação, mesmo se o pull request estiver em um repositório privado{% ifversion ghes %}, ou se o modo privado estiver habilitado{% endif %}. Para manter arquivos de mídia confidenciais privados, forneça-os a partir de uma rede privada ou servidor que exige autenticação. {% ifversion fpt or ghec %}Para mais informações sobre URLs anônimas, consulte "[Sobre URLs anônimas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
-
-{% endwarning %}
+{% data reusables.repositories.anyone-can-view-anonymized-url %}
 
 Para anexar um arquivo a uma conversa sobre um problema ou pull request, arraste-o e solte-o dentro da caixa de comentários. Como alternativa, você pode clicar na barra na parte inferior da caixa de comentários para navegar, selecionar e adicionar um arquivo do seu computador.
 
diff --git a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
index 566796cbf2..480dbd7abc 100644
--- a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
+++ b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
@@ -45,6 +45,15 @@ Nas conversas do {% data variables.product.product_name %}, as referências a pr
 Se você fizer referência a um problema, pull request ou discussão em uma lista, a referência irá desenrolar-se para mostrar o título e o estado. Para obter mais informações sobre listas de tarefas, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)".
 {% endif %}
 
+## Etiquetas
+When referencing the URL of a label in Markdown, the label is automatically rendered. Only labels of the same repository are rendered, URLs pointing to a label from a different repository are rendered as any [URL](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#urls).
+
+The URL of a label can be found by navigating to the labels page and clicking on a label. For example, the URL of the label "enhancement" in our public [docs repository](https://github.com/github/docs/) is
+
+```md
+https://github.com/github/docs/labels/enhancement
+```
+
 ## SHAs de commit
 
 As referências em um hash SHA de commit são convertidas automaticamente em links curtos para o commit no {% data variables.product.product_name %}.
diff --git a/translations/pt-BR/content/issues/guides.md b/translations/pt-BR/content/issues/guides.md
index a7e2218ed6..d390dcf523 100644
--- a/translations/pt-BR/content/issues/guides.md
+++ b/translations/pt-BR/content/issues/guides.md
@@ -10,11 +10,11 @@ versions:
   ghae: '*'
   ghec: '*'
 includeGuides:
-  - /issues/trying-out-the-new-projects-experience/automating-projects
-  - /issues/trying-out-the-new-projects-experience/creating-a-project
-  - /issues/trying-out-the-new-projects-experience/customizing-your-project-views
-  - /issues/trying-out-the-new-projects-experience/quickstart
-  - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
+  - /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
+  - /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
+  - /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view
+  - /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
+  - /issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects
   - /issues/tracking-your-work-with-issues/quickstart
   - /issues/tracking-your-work-with-issues/creating-an-issue
   - /issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests
diff --git a/translations/pt-BR/content/issues/index.md b/translations/pt-BR/content/issues/index.md
index 799e4b7a59..5f044bd61b 100644
--- a/translations/pt-BR/content/issues/index.md
+++ b/translations/pt-BR/content/issues/index.md
@@ -8,18 +8,19 @@ introLinks:
 featuredLinks:
   guides:
     - /issues/tracking-your-work-with-issues/creating-issues/creating-an-issue
-    - /issues/trying-out-the-new-projects-experience/quickstart
-    - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects
+    - /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
+    - /issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects
     - /communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
     - /issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project
   guideCards:
-    - /issues/trying-out-the-new-projects-experience/automating-projects
+    - /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view
     - /issues/tracking-your-work-with-issues/creating-issues/linking-a-pull-request-to-an-issue
     - '{% ifversion ghes or ghae %}/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards{% endif %}'
-    - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
+    - /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
   popular:
     - /issues/tracking-your-work-with-issues/creating-issues/about-issues
-    - /issues/trying-out-the-new-projects-experience/about-projects
+    - /issues/planning-and-tracking-with-projects/learning-about-projects/about-projects
+    - /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
     - /issues/tracking-your-work-with-issues/creating-issues/about-task-lists
     - /communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates
     - /issues/using-labels-and-milestones-to-track-work/managing-labels
@@ -32,8 +33,8 @@ featuredLinks:
       href: 'https://www.youtube-nocookie.com/embed/HwpVvDURHKw'
     - title: Issue Forms for open source – Luke Hefson
       href: 'https://www.youtube-nocookie.com/embed/2Yh8ueUE0oY'
-  videosHeading: GitHub Universe 2021 videos
-product_video: 'https://www.youtube-nocookie.com/embed/uiaLWluYJsA'
+  videosHeading: Videos
+product_video: '{% ifversion projects-v2 %}https://www.youtube-nocookie.com/embed/yFQ-p6wMS_Y{% else %}https://www.youtube-nocookie.com/embed/uiaLWluYJsA{% endif %}'
 layout: product-landing
 beta_product: false
 versions:
@@ -43,7 +44,7 @@ versions:
   ghec: '*'
 children:
   - /tracking-your-work-with-issues
-  - /trying-out-the-new-projects-experience
+  - /planning-and-tracking-with-projects
   - /organizing-your-work-with-project-boards
   - /using-labels-and-milestones-to-track-work
   - /guides
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/index.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/index.md
index a6fef6b6e9..4deb19447a 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/index.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/index.md
@@ -1,12 +1,10 @@
 ---
-title: Organizando seu trabalho com quadros de projetos
-shortTitle: Quadros de projeto
-intro: 'Use os quadros de projetos para gerenciar seu trabalho em {% data variables.product.prodname_dotcom %}'
+title: 'Organizing your work with {% data variables.product.prodname_projects_v1 %}'
+shortTitle: '{% data variables.product.prodname_projects_v1_caps %}'
+intro: 'Use {% data variables.product.prodname_projects_v1 %} to manage your work on {% data variables.product.prodname_dotcom %}'
+allowTitleToDifferFromFilename: true
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Issues
   - Projects
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
index e73df1def0..3cee1e3b87 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
@@ -1,31 +1,29 @@
 ---
-title: Sobre a automação para quadros de projeto
-intro: Você pode configurar fluxos de trabalho automáticos para manter o status dos cartões do quadro de projeto em sincronia com os problemas e pull requests associados.
+title: 'About automation for {% data variables.product.prodname_projects_v1 %}'
+intro: 'You can configure automatic workflows to keep the status of {% data variables.projects.projects_v1_board %} cards in sync with the associated issues and pull requests.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/about-automation-for-project-boards
   - /articles/about-automation-for-project-boards
   - /github/managing-your-work-on-github/about-automation-for-project-boards
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
-shortTitle: Automação para quadros de projeto
+shortTitle: 'Automation for {% data variables.product.prodname_projects_v1 %}'
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
-{% data reusables.project-management.automate-project-board-permissions %}  Para obter mais informações, consulte "[Permissões do quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)."
+{% data reusables.project-management.automate-project-board-permissions %}  For more information, see "[{% data variables.product.prodname_projects_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
-Você pode automatizar ações com base nos eventos de disparo para colunas do quadro de projeto. Isso elimina algumas das tarefas manuais no gerenciamento de um quadro de projeto. Por exemplo, é possível configurar uma coluna "Tarefas pendentes", onde qualquer problema ou pull request que você adiciona a um quadro de projeto é automaticamente movido para a coluna configurada. Para obter mais informações, consulte "[Configurar a automação para quadros de projeto](/articles/configuring-automation-for-project-boards)."
+You can automate actions based on triggering events for {% data variables.projects.projects_v1_board %} columns. This eliminates some of the manual tasks in managing a {% data variables.projects.projects_v1_board %}. For example, you can configure a "To do" column, where any new issues or pull requests you add to a {% data variables.projects.projects_v1_board %} are automatically moved to the configured column. For more information, see "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)."
 
 {% data reusables.project-management.use-automated-template %}
 
 {% data reusables.project-management.copy-project-boards %}
 
-A automação do quadro de projeto também pode ajudar as equipes a desenvolver uma compreensão compartilhada da finalidade de um quadro de projeto e o processo de desenvolvimento da equipe criando um fluxo de trabalho padrão para determinadas ações.
+{% data variables.projects.projects_v1_board_caps %} automation can also help teams develop a shared understanding of a {% data variables.projects.projects_v1_board %}'s purpose and the team's development process by creating a standard workflow for certain actions.
 
 {% data reusables.project-management.resync-automation %}
 
@@ -39,10 +37,10 @@ A automação do quadro de projeto também pode ajudar as equipes a desenvolver
 
 ## Acompanhamento do andamento do projeto
 
-Você pode acompanhar o progresso no seu quadro de projeto. Cartões nas colunas "Pendente", "Em progresso" ou "Concluído" contam para o progresso geral do projeto. {% data reusables.project-management.project-progress-locations %}
+You can track the progress on your {% data variables.projects.projects_v1_board %}. Cartões nas colunas "Pendente", "Em progresso" ou "Concluído" contam para o progresso geral do projeto. {% data reusables.project-management.project-progress-locations %}
 
-Para obter mais informações, consulte "[Acompanhamento do progresso no quadro de projeto](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)".
+For more information, see "[Tracking progress on your {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)."
 
 ## Leia mais
-- "[Configurar a automação para quadros de projeto](/articles/configuring-automation-for-project-boards)"{% ifversion fpt or ghec %}
-- "[Copiar um quadro de projeto](/articles/copying-a-project-board)"{% endif %}
+- "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)"{% ifversion fpt or ghec %}
+- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %}
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
index 8fc7e162b4..cec96ec53c 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
@@ -1,55 +1,53 @@
 ---
-title: Sobre quadros de projeto
-intro: 'Os quadros de projeto no {% data variables.product.product_name %} ajudam você a organizar e priorizar seu trabalho. É possível criar quadros de projeto para trabalho de recurso específico, roteiros abrangentes ou, até mesmo, checklists de versão. Com os quadros de projeto, você tem a flexibilidade de criar fluxos de trabalho personalizados adequados às suas necessidades.'
+title: 'Sobre {% data variables.product.prodname_projects_v1 %}'
+intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/about-project-boards
   - /articles/about-projects
   - /articles/about-project-boards
   - /github/managing-your-work-on-github/about-project-boards
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
-Os quadros de projeto são compostos por problemas, pull requests e observações que são categorizados como cartões em colunas de sua escolha. É possível arrastar e soltar ou usar atalhos de teclado para reordenar cartões em uma coluna, mover cartões de coluna para coluna e alterar a ordem das colunas.
+{% data variables.projects.projects_v1_boards_caps %} are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. É possível arrastar e soltar ou usar atalhos de teclado para reordenar cartões em uma coluna, mover cartões de coluna para coluna e alterar a ordem das colunas.
 
-Os cartões do quadro de projeto contêm metadados relevantes para problemas e pull requests, como etiquetas, responsáveis, o status e quem os abriu. {% data reusables.project-management.edit-in-project %}
+{% data variables.projects.projects_v1_board_caps %} cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %}
 
-Você pode criar observações dentro de colunas para servirem de lembretes de tarefa, fazer referência a problemas e pull requests de qualquer repositório no {% data variables.product.product_location %} ou adicionar informações relacionadas ao quadro de projeto. É possível criar um cartão de referência para outro quadro de projeto adicionando um link a uma observação. Se a observação não for suficiente para suas necessidades, você poderá convertê-la em um problema. Para obter mais informações sobre como converter observações de quadro de projeto em problemas, consulte "[Adicionar observações a um quadro de projeto](/articles/adding-notes-to-a-project-board)".
+You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the {% data variables.projects.projects_v1_board %}. You can create a reference card for another {% data variables.projects.projects_v1_board %} by adding a link to a note. Se a observação não for suficiente para suas necessidades, você poderá convertê-la em um problema. For more information on converting notes to issues, see "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)."
 
 Tipos de quadros de projeto:
 
-- Os **quadros de projeto possuídos pelo usuário** podem conter problemas e pull requests de qualquer repositório pessoal.
-- Os **quadros de projeto de toda a organização** podem conter problemas e pull requests de qualquer repositório que pertença a uma organização.  {% data reusables.project-management.link-repos-to-project-board %} Para obter mais informações, consulte "[Vincular um repositório a um quadro de projeto](/articles/linking-a-repository-to-a-project-board)."
-- Os **quadros de projeto do repositório** abrangem problemas ou pull requests dentro de um único repositório. Eles também podem incluir observações que fazem referência a problemas e pull requests em outros repositórios.
+- **User-owned {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any personal repository.
+- **Organization-wide {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any repository that belongs to an organization.  {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)."
+- **Repository {% data variables.projects.projects_v1_board %}** are scoped to issues and pull requests within a single repository. Eles também podem incluir observações que fazem referência a problemas e pull requests em outros repositórios.
 
-## Criar e exibir quadros de projeto
+## Creating and viewing {% data variables.projects.projects_v1_boards %}
 
-Para criar um quadro de projeto para sua organização, você deve ser um integrante da organização. Os proprietários da organização e as pessoas com permissões de administrador de quadro de projeto podem personalizar o acesso ao quadro de projeto.
+To create a {% data variables.projects.projects_v1_board %} for your organization, you must be an organization member. Organization owners and people with {% data variables.projects.projects_v1_board %} admin permissions can customize access to the {% data variables.projects.projects_v1_board %}.
 
-Se um quadro de projeto possuído pela organização incluir problemas ou pull requests de um repositório que você não tem permissão para exibir, o cartão será removido.  Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)".
+If an organization-owned {% data variables.projects.projects_v1_board %} includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted.  For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
-A exibição da atividade mostra o histórico recente do quadro de projeto, como cartões que alguém criou ou moveu entre colunas. Para acessar a exibição da atividade, clique em **Menu** e role para baixo.
+The activity view shows the {% data variables.projects.projects_v1_board %}'s recent history, such as cards someone created or moved between columns. Para acessar a exibição da atividade, clique em **Menu** e role para baixo.
 
-Para encontrar cartões específicos em um quadro de projeto ou exibir um subconjunto dos cartões, você pode filtrar cartões do quadro de projeto. Para obter mais informações, consulte "[Filtrar cartões em um quadro de projeto](/articles/filtering-cards-on-a-project-board)".
+To find specific cards on a {% data variables.projects.projects_v1_board %} or view a subset of the cards, you can filter {% data variables.projects.projects_v1_board %} cards. For more information, see "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)."
 
-Para simplificar seu fluxo de trabalho a manter as tarefas concluídas fora do quadro de projeto, você pode arquivar cartões. Para obter mais informações, consulte "[Arquivar cartões em um quadro de projeto](/articles/archiving-cards-on-a-project-board)."
+To simplify your workflow and keep completed tasks off your {% data variables.projects.projects_v1_board %}, you can archive cards. For more information, see "[Archiving cards on a {% data variables.product.prodname_project_v1 %}](/articles/archiving-cards-on-a-project-board)."
 
-Se você concluiu todas as tarefas do quadro de projeto ou não precisar mais usar o quadro de projeto, é possível fechá-lo. Para obter mais informações, consulte "[Fechar um quadro de projeto](/articles/closing-a-project-board)".
+If you've completed all of your {% data variables.projects.projects_v1_board %} tasks or no longer need to use your {% data variables.projects.projects_v1_board %}, you can close the {% data variables.projects.projects_v1_board %}. For more information, see "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)."
 
-Também é possível [desabilitar quadros de projeto em um repositório](/articles/disabling-project-boards-in-a-repository) ou [desabilitar quadros de projeto em sua organização](/articles/disabling-project-boards-in-your-organization), se preferir rastrear o trabalho de maneira diferente.
+You can also [disable {% data variables.projects.projects_v1_boards %} in a repository](/articles/disabling-project-boards-in-a-repository) or [disable {% data variables.projects.projects_v1_boards %} in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way.
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## Modelos para quadros de projeto
+## Templates for {% data variables.projects.projects_v1_boards %}
 
-É possível usar modelos para configurar rapidamente um novo quadro de projeto. Quando você usar um modelo para criar um quadro de projeto, o novo quadro incluirá colunas, bem como cartões com dicas para usar quadros de projeto. Você também pode escolher um modelo com automação já configurada.
+You can use templates to quickly set up a new {% data variables.projects.projects_v1_board %}. When you use a template to create a {% data variables.projects.projects_v1_board %}, your new board will include columns as well as cards with tips for using {% data variables.product.prodname_projects_v1 %}. Você também pode escolher um modelo com automação já configurada.
 
 | Modelo                          | Descrição                                                                                                                                                                              |
 | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -58,17 +56,17 @@ Também é possível [desabilitar quadros de projeto em um repositório](/articl
 | Kanban automatizado com revisão | Cartões são movidos automaticamente entre as colunas To do (Pendentes), In progress (Em andamento) e Done (Concluídos), com gatilhos adicionais para status de revisão de pull request |
 | Triagem de erros                | Faça a triagem e priorize erros com as colunas To do (Pendentes), High priority (Prioridade alta), Low priority (Prioridade baixa) e Closed (Fechados)                                 |
 
-Para obter mais informações sobre automação para quadros de projeto, consulte "[Sobre automação para quadros de projeto](/articles/about-automation-for-project-boards)".
+For more information on automation for {% data variables.product.prodname_projects_v1 %}, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
 
-![Quadro de projeto com modelo de kanban básico](/assets/images/help/projects/project-board-basic-kanban-template.png)
+![{% data variables.product.prodname_project_v1 %} with basic kanban template](/assets/images/help/projects/project-board-basic-kanban-template.png)
 
 {% data reusables.project-management.copy-project-boards %}
 
 ## Leia mais
 
-- "[Criar um quadro de projeto](/articles/creating-a-project-board)"
-- "[Editar um quadro de projeto](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
-- "[Copiar um quadro de projeto](/articles/copying-a-project-board)"{% endif %}
-- "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)"
+- "[Criar um {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)"
+- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
+- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %}
+- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
 - "[Atalhos de teclado](/articles/keyboard-shortcuts/#project-boards)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
index 5c97da8836..446abe56cf 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
@@ -1,18 +1,16 @@
 ---
-title: Alterar a visibilidade dos quadros de projeto
-intro: 'Como proprietário ou administrador de um projeto da organização, você pode tornar um quadro de projeto {% ifversion ghae %}interno{% else %}público{% endif %} ou privado.'
+title: 'Changing {% data variables.product.prodname_project_v1 %} visibility'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can make a {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %} or private.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility
   - /articles/changing-project-board-visibility
   - /github/managing-your-work-on-github/changing-project-board-visibility
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
 shortTitle: Alterar visibilidade
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
@@ -21,7 +19,7 @@ shortTitle: Alterar visibilidade
 
 {% tip %}
 
-**Dica:** Ao tornar seu quadro de projeto {% ifversion ghae %}interno{% else %}público{% endif %}, os integrantes da organização recebem acesso de leitura por padrão. Você pode conceder a integrantes específicos da organização permissões de gravação ou de administrador dando às equipes acesso ao quadro de projeto em que eles estão ativos ou adicionando-os ao quadro de projeto como um colaborador. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)".
+**Tip:** When you make your {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving access to teams they're on or by adding them to the {% data variables.projects.projects_v1_board %} as a collaborator. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% endtip %}
 
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
index 3285486a76..a87be0f04a 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
@@ -1,34 +1,32 @@
 ---
-title: Fechar um quadro de projeto
-intro: 'Se você concluiu todas as tarefas em um quadro de projeto ou não precisa mais usar um quadro de projeto, é possível fechá-lo.'
+title: 'Closing a {% data variables.product.prodname_project_v1 %}'
+intro: 'If you''ve completed all the tasks in a {% data variables.projects.projects_v1_board %} or no longer need to use a {% data variables.projects.projects_v1_board %}, you can close the {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/closing-a-project-board
   - /articles/closing-a-project
   - /articles/closing-a-project-board
   - /github/managing-your-work-on-github/closing-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
-Quando você fecha um quadro de projeto, qualquer automação de fluxo de trabalho configurada é pausada por padrão.
+When you close a {% data variables.projects.projects_v1_board %}, any configured workflow automation will pause by default.
 
-Se você reabrir um quadro de projeto, existirá a opção de *sincronizar* a automação, o que atualiza a posição dos cartões no quadro de acordo com as configurações de automação definidas para o quadro. Para obter mais informações, consulte "[Reabrir um quadro de projeto fechado](/articles/reopening-a-closed-project-board)" ou "[Sobre automação para quadros de projeto](/articles/about-automation-for-project-boards)".
+If you reopen a {% data variables.projects.projects_v1_board %}, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board. For more information, see "[Reopening a closed {% data variables.product.prodname_project_v1 %}](/articles/reopening-a-closed-project-board)" or "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
 
-1. Acesse a lista de quadros de projetos no seu repositório ou organização ou pertencente à sua conta pessoal.
-2. Na lista de projetos, ao lado do quadro de projeto que deseja fechar, clique em {% octicon "chevron-down" aria-label="The chevron icon" %}. ![Ícone de divisa à direita do nome do quadro de projeto](/assets/images/help/projects/project-list-action-chevron.png)
+1. Navigate to the list of {% data variables.projects.projects_v1_boards %} in your repository or organization, or owned by your personal account.
+2. In the projects list, next to the {% data variables.projects.projects_v1_board %} you want to close, click {% octicon "chevron-down" aria-label="The chevron icon" %}. ![Ícone de divisa à direita do nome do quadro de projeto](/assets/images/help/projects/project-list-action-chevron.png)
 3. Clique em **Fechar**. ![Menu suspenso para fechar item no quadro de projeto](/assets/images/help/projects/close-project.png)
 
 ## Leia mais
 
-- "[Sobre quadros de projetos](/articles/about-project-boards)"
-- "[Excluir um quadro de projeto](/articles/deleting-a-project-board)"
-- "[Desabilitar quadros de projeto em um repositório](/articles/disabling-project-boards-in-a-repository)"
-- "[Desabilitar quadros de projeto na sua organização](/articles/disabling-project-boards-in-your-organization)"
-- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)"
+- "[Sobre o {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Deleting a {% data variables.product.prodname_project_v1 %}](/articles/deleting-a-project-board)"
+- "[Disabling {% data variables.product.prodname_projects_v1 %} in a repository](/articles/disabling-project-boards-in-a-repository)"
+- "[Disabling {% data variables.product.prodname_projects_v1 %} in your organization](/articles/disabling-project-boards-in-your-organization)"
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
index 6d78fa34db..f6e94c9c54 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
@@ -1,15 +1,12 @@
 ---
-title: Configurar a automação para quadros de projeto
-intro: Você pode configurar fluxos de trabalho automáticos para mover problemas e pull requests para uma coluna de quadro de projeto quando ocorre um determinado evento.
+title: 'Configuring automation for {% data variables.product.prodname_projects_v1 %}'
+intro: 'You can set up automatic workflows to move issues and pull requests to a {% data variables.projects.projects_v1_board %} column when a specified event occurs.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/configuring-automation-for-project-boards
   - /articles/configuring-automation-for-project-boards
   - /github/managing-your-work-on-github/configuring-automation-for-project-boards
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
   - Projects
@@ -17,11 +14,12 @@ topics:
   - Project management
 shortTitle: Configurar automação
 type: how_to
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
-{% data reusables.project-management.automate-project-board-permissions %} Para obter mais informações, consulte "[Sobre a automação para quadros de projeto](/articles/about-automation-for-project-boards)".
+{% data reusables.project-management.automate-project-board-permissions %} For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
 
 {% data reusables.project-management.use-automated-template %}
 
@@ -33,7 +31,7 @@ type: how_to
 
 {% endtip %}
 
-1. Navegue até o quadro de projeto que deseja automatizar.
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to automate.
 2. Na coluna que deseja automatizar, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Ícone Edit (Editar)](/assets/images/help/projects/edit-column-button.png)
 3. Clique em **Manage automation** (Gerenciar automação). ![Botão Manage automation (Gerenciar automação)](/assets/images/help/projects/manage-automation-button.png)
 4. Usando o menu suspenso Preset (Predefinida), selecione uma automação predefinida. ![Selecionar automação predefinida no menu](/assets/images/help/projects/select-automation.png)
@@ -41,4 +39,4 @@ type: how_to
 6. Clique em **Update automation** (Atualizar automação).
 
 ## Leia mais
-- "[Sobre a automação para quadros de projeto](/articles/about-automation-for-project-boards)"
+- "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
index cd5301cbbc..65ea8cf049 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Copiar um quadro de projeto
-intro: Você pode copiar um quadro de projeto para criar rapidamente um projeto. A cópia frequentemente usada ou altamente personalizada dos quadros de projeto ajuda a padronizar seu fluxo de trabalho.
+title: 'Copying a {% data variables.product.prodname_project_v1 %}'
+intro: 'You can copy a {% data variables.projects.projects_v1_board %} to quickly create a new project. Copying frequently used or highly customized {% data variables.projects.projects_v1_boards %} helps standardize your workflow.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/copying-a-project-board
   - /articles/copying-a-project-board
@@ -10,23 +10,24 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
-Copiar um quadro de projeto permite reutilizar o título, a descrição e a configuração de automação desse quadro. É possível copiar quadros de projeto para eliminar o processo manual de criar outros quadros para fluxos de trabalho semelhantes.
+Copying a {% data variables.projects.projects_v1_board %} allows you to reuse a {% data variables.projects.projects_v1_board %}'s title, description, and automation configuration. You can copy {% data variables.projects.projects_v1_boards %} to eliminate the manual process of creating new {% data variables.projects.projects_v1_boards %} for similar workflows.
 
-É preciso ter acesso de leitura a um quadro de projeto para copiá-lo em um repositório ou uma organização onde você tenha acesso de gravação.
+You must have read access to a {% data variables.projects.projects_v1_board %} to copy it to a repository or organization where you have write access.
 
-Quando você copia um quadro de projeto em uma organização, a visibilidade do quadro é padronizada para privada, com uma opção para alterar essa visibilidade. Para obter mais informações, consulte "[Alterar visibilidade do quadro de projeto](/articles/changing-project-board-visibility/)".
+When you copy a {% data variables.projects.projects_v1_board %} to an organization, the {% data variables.projects.projects_v1_board %}'s visibility will default to private, with an option to change the visibility. For more information, see "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility/)."
 
-A automação de um quadro de projeto também é habilitada por padrão. Para obter mais informações, consulte "[Sobre a automação para quadros de projeto](/articles/about-automation-for-project-boards/)".
+A {% data variables.projects.projects_v1_board %}'s automation is also enabled by default. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards/)."
 
-1. Navegue até o quadro de projeto que deseja copiar.
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to copy.
 {% data reusables.project-management.click-menu %}
 3. Clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, em **Copy** (Copiar). ![Opção de cópia no menu suspenso da barra lateral do quadro de projeto](/assets/images/help/projects/project-board-copy-setting.png)
 4. Em "Owner" (Proprietário), use o menu suspenso e clique no repositório ou na organização em que deseja copiar o quadro de projeto. ![Selecionar proprietário do quadro de projeto copiado no menu suspenso](/assets/images/help/projects/copied-project-board-owner.png)
-5. Se preferir, em "Project board name" (Nome do quadro de projeto), digite o nome do quadro de projeto copiado. ![Campo para digitar um nome para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-name.png)
+5. Optionally, under "Project board name", type the name of the copied {% data variables.projects.projects_v1_board %}. ![Campo para digitar um nome para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-name.png)
 6. Se desejar, em "Description" (Descrição), digite uma descrição do quadro de projeto copiado que outras pessoas verão. ![Campo para digitar uma descrição para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-description.png)
 7. Se desejar, em "Automation settings" (Configurações de automação), selecione se deseja copiar os fluxos de trabalho automáticos configurados. Essa opção é habilitada por padrão. Para obter mais informações, consulte "[Sobre a automação para quadros de projeto](/articles/about-automation-for-project-boards/)". ![Configurações de seleção de automação para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-automation-settings.png)
 {% data reusables.project-management.choose-visibility %}
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
index 4e5d01c314..85025552b0 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
@@ -1,22 +1,20 @@
 ---
-title: Criar um quadro de projeto
-intro: 'Os quadros de projeto podem ser usados para criar fluxos de trabalho personalizados adequados às suas necessidades, como rastreamento e priorização de trabalho de recursos específicos, roteiros abrangentes ou, até mesmo, checklists de versão.'
+title: 'Criar {% data variables.product.prodname_project_v1 %}'
+intro: '{% data variables.projects.projects_v1_boards_caps %} can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board
   - /articles/creating-a-project
   - /articles/creating-a-project-board
   - /github/managing-your-work-on-github/creating-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
   - Issues
   - Projects
   - Project management
 type: how_to
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
@@ -25,20 +23,21 @@ type: how_to
 
 {% data reusables.project-management.copy-project-boards %}
 
-{% data reusables.project-management.link-repos-to-project-board %} Para obter mais informações, consulte "[Vincular um repositório a um quadro de projeto](/articles/linking-a-repository-to-a-project-board)."
+{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %} ](/articles/linking-a-repository-to-a-project-board)."
 
-Após a criação do quadro de projeto, você poderá adicionar a ele problemas, pull requests e observações. Para obter mais informações, consulte "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)" e "[Adicionar observações a um quadro de projeto](/articles/adding-notes-to-a-project-board)".
+Once you've created your {% data variables.projects.projects_v1_board %}, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)."
 
-Também é possível configurar automações de fluxo de trabalho para manter seu quadro de projeto em sincronia com o status de problemas e pull requests. Para obter mais informações, consulte "[Sobre a automação para quadros de projeto](/articles/about-automation-for-project-boards)".
+You can also configure workflow automations to keep your {% data variables.projects.projects_v1_board %} in sync with the status of issues and pull requests. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## Criar um quadro de projeto de propriedade do usuário
+## Creating a user-owned {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
 {% data reusables.profile.access_profile %}
-2. No topa da página do seu perfil, na navegação principal, clique em {% octicon "project" aria-label="The project board icon" %} **Projects** (Projetos). ![Aba Project (Projeto)](/assets/images/help/projects/user-projects-tab.png)
+2. No topa da página do seu perfil, na navegação principal, clique em {% octicon "project" aria-label="The project board icon" %} **Projects** (Projetos). ![Project tab](/assets/images/help/projects/user-projects-tab.png){% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
@@ -54,13 +53,14 @@ Também é possível configurar automações de fluxo de trabalho para manter se
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Criar um quadro de projeto em toda a organização
+## Creating an organization-wide {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
@@ -76,12 +76,13 @@ Também é possível configurar automações de fluxo de trabalho para manter se
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Criar um quadro de projeto de repositório
+## Creating a repository {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Abaixo do nome do repositório, clique em {% octicon "project" aria-label="The project board icon" %} **Projects** (Projetos). ![Aba Project (Projeto)](/assets/images/help/projects/repo-tabs-projects.png)
+2. Abaixo do nome do repositório, clique em {% octicon "project" aria-label="The project board icon" %} **Projects** (Projetos). ![Project tab](/assets/images/help/projects/repo-tabs-projects.png){% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
index 1a7379a123..89b5873bca 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
@@ -1,29 +1,27 @@
 ---
-title: Excluir um quadro de projeto
-intro: Você pode excluir um quadro de projeto existente se já não precisa mais ter acesso ao conteúdo dele.
+title: 'Deleting a {% data variables.product.prodname_project_v1 %}'
+intro: 'You can delete an existing {% data variables.projects.projects_v1_board %} if you no longer need access to its contents.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board
   - /articles/deleting-a-project
   - /articles/deleting-a-project-board
   - /github/managing-your-work-on-github/deleting-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Dica**: para manter o acesso a um quadro de projeto concluído ou desnecessário sem perder o acesso ao conteúdo dele, [feche o quadro de projeto](/articles/closing-a-project-board) em vez de excluí-lo.
+**Tip**: If you'd like to retain access to a completed or unneeded {% data variables.projects.projects_v1_board %} without losing access to its contents, you can [close the {% data variables.projects.projects_v1_board %}](/articles/closing-a-project-board) instead of deleting it.
 
 {% endtip %}
 
-1. Navegue até o quadro de projeto que deseja excluir.
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to delete.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.click-edit-sidebar-menu-project-board %}
 4. Clique em **Delete project** (Excluir projeto). ![Botão Delete project (Excluir projeto)](/assets/images/help/projects/delete-project-button.png)
@@ -31,6 +29,6 @@ topics:
 
 ## Leia mais
 
-- "[Fechar um quadro de projeto](/articles/closing-a-project-board)"
-- "[Desabilitar quadros de projeto em um repositório](/articles/disabling-project-boards-in-a-repository)"
-- "[Desabilitar quadros de projeto na sua organização](/articles/disabling-project-boards-in-your-organization)"
+- "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)"
+- "[Disabling {% data variables.product.prodname_project_v1_caps %} in a repository](/articles/disabling-project-boards-in-a-repository)"
+- "[Disabling {% data variables.product.prodname_project_v1_caps %} in your organization](/articles/disabling-project-boards-in-your-organization)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
index 7d1a4bdc53..21f8f8a3cf 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Editar um quadro de projeto
-intro: Você pode editar o título e a descrição de um quadro de projeto existente.
+title: 'Editing a {% data variables.product.prodname_project_v1 %}'
+intro: 'You can edit the title and description of an existing {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/editing-a-project-board
   - /articles/editing-a-project
@@ -8,29 +8,27 @@ redirect_from:
   - /articles/editing-a-project-board
   - /github/managing-your-work-on-github/editing-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Dica:** para ver detalhes sobre como adicionar, remover ou editar colunas no quadro de projeto, consulte "[Criar um quadro de projeto](/articles/creating-a-project-board)".
+**Tip:** For details on adding, removing, or editing columns in your {% data variables.projects.projects_v1_board %}, see "[Creating a {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)."
 
 {% endtip %}
 
-1. Navegue até o quadro de projeto que deseja editar.
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to edit.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.click-edit-sidebar-menu-project-board %}
-4. Modifique o nome e a descrição do quadro de projeto conforme necessário e clique em **Save project** (Salvar projeto). ![Campos com o nome e a descrição do quadro de projeto e o botão Save project (Salvar projeto)](/assets/images/help/projects/edit-project-board-save-button.png)
+4. Modify the {% data variables.projects.projects_v1_board %} name and description as needed, then click **Save project**. ![Campos com o nome e a descrição do quadro de projeto e o botão Save project (Salvar projeto)](/assets/images/help/projects/edit-project-board-save-button.png)
 
 ## Leia mais
 
-- "[Sobre quadros de projetos](/articles/about-project-boards)"
-- "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Excluir um quadro de projeto](/articles/deleting-a-project-board)"
+- "[Sobre o {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[Deleting a {% data variables.product.prodname_project_v1 %}](/articles/deleting-a-project-board)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
index 803c154622..4eb7b48810 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
@@ -1,12 +1,9 @@
 ---
-title: Gerenciar quadros de projeto
-shortTitle: Gerenciar quadros de projeto
-intro: Aprenda como criar e gerenciar quadros de projetos
+title: 'Gerenciar {% data variables.product.prodname_projects_v1 %}'
+shortTitle: 'Gerenciar {% data variables.product.prodname_projects_v1 %}'
+intro: 'Learn how to create and manage {% data variables.projects.projects_v1_boards %}'
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Issues
   - Projects
@@ -24,6 +21,7 @@ children:
   - /deleting-a-project-board
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
index 929174ffd7..ca1ebfd904 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
@@ -1,27 +1,25 @@
 ---
-title: Vincular um repositório a um quadro de projeto
-intro: É possível vincular um repositório ao quadro de projeto da organização ou conta pessoal.
+title: 'Linking a repository to a {% data variables.product.prodname_project_v1 %}'
+intro: 'You can link a repository to your organization''s or personal account''s {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/linking-a-repository-to-a-project-board
   - /articles/linking-a-repository-to-a-project-board
   - /github/managing-your-work-on-github/linking-a-repository-to-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
 shortTitle: Vincular repositório ao quadro
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
-Qualquer pessoa com permissões de gravação em um quadro de projeto pode vincular repositórios pertencentes a essa organização ou conta pessoal ao quadro de projeto. Para obter mais informações, consulte "[Permissões de quadro de projeto da organização](/articles/project-board-permissions-for-an-organization/)" ou "[Níveis de permissão para quadros de projetos de propriedade de usuários](/articles/permission-levels-for-user-owned-project-boards/)".
+Anyone with write permissions to a {% data variables.projects.projects_v1_board %} can link repositories owned by that organization or personal account to the {% data variables.projects.projects_v1_board %}. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization/)" or "[Permission levels for user-owned {% data variables.product.prodname_projects_v1 %}](/articles/permission-levels-for-user-owned-project-boards/)."
 
-{% data reusables.project-management.link-repos-to-project-board %} Você pode adicionar problemas e pull requests de quaisquer repositórios desvinculados digitando a URL do problema ou pull request em um cartão. Para obter mais informações, consulte "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)".
+{% data reusables.project-management.link-repos-to-project-board %} Você pode adicionar problemas e pull requests de quaisquer repositórios desvinculados digitando a URL do problema ou pull request em um cartão. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)."
 
-1. Navegue até o quadro de projeto onde você quer vincular um repositório.
+1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to link a repository.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
 4. Na barra lateral esquerda, clique em **Linked repositories** (Repositórios vinculados). ![Menu de opção Linked repositories (Repositórios vinculados) na barra lateral esquerda](/assets/images/help/projects/project-board-linked-repositories-setting.png)
@@ -31,10 +29,10 @@ Qualquer pessoa com permissões de gravação em um quadro de projeto pode vincu
 
 {% note %}
 
-**Observação:** Para vincular um repositório à sua organização ou quadro de projeto de propriedade de usuário, o repositório precisa ter problemas habilitados. Ou seja, o repositório tem uma aba "Problemas" (os problemas nos repositórios bifurcados são desabilitados por padrão).  Para obter informações sobre como habilitar ou desabilitar problemas para um repositório, consulte "[Desabilitar problemas para um repositório](/github/managing-your-work-on-github/disabling-issues). "
+**Note:** In order to link a repository to your organization or user owned {% data variables.projects.projects_v1_board %} the repository needs to have issues enabled. Ou seja, o repositório tem uma aba "Problemas" (os problemas nos repositórios bifurcados são desabilitados por padrão).  Para obter informações sobre como habilitar ou desabilitar problemas para um repositório, consulte "[Desabilitar problemas para um repositório](/github/managing-your-work-on-github/disabling-issues). "
 
 {% endnote %}
 
 ## Leia mais
 
-- "[Sobre quadros de projetos](/articles/about-project-boards)"
+- "[Sobre o {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
index cdcb2eea95..1cd4e2979a 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
@@ -1,32 +1,30 @@
 ---
-title: Reabrir um quadro de projeto fechado
-intro: Você pode reabrir um painel de projeto fechado e reiniciar qualquer automação de fluxo de trabalho que tenha sido configurada para o quadro de projetos.
+title: 'Reopening a closed {% data variables.product.prodname_project_v1 %}'
+intro: 'You can reopen a closed {% data variables.projects.projects_v1_board %} and restart any workflow automation that was configured for the {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board
   - /articles/reopening-a-closed-project-board
   - /github/managing-your-work-on-github/reopening-a-closed-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
-shortTitle: Reabrir quadro de projeto
+shortTitle: 'Reopen {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
-Quando você fecha um quadro de projeto, todas as automações de fluxo de trabalho configuradas para o quadro de projeto são pausadas por padrão. Para obter mais informações, consulte "[Fechar um quadro de projeto](/articles/closing-a-project-board)".
+When you close a {% data variables.projects.projects_v1_board %}, any workflow automation that was configured for the {% data variables.projects.projects_v1_board %} will pause by default. For more information, see "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)."
 
-Quando você reabre um quadro de projeto, tem a opção de *sincronizar* a automação, o que atualiza a posição dos cartões no quadro de acordo com as configurações de automação definidas para o quadro.
+When you reopen a {% data variables.projects.projects_v1_board %}, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board.
 
-1. Navegue até o quadro de projeto que deseja reabrir.
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to reopen.
 {% data reusables.project-management.click-menu %}
-3. Escolha se deseja sincronizar a automação do quadro de projeto ao reabri-lo.
-    - Para reabrir o quadro de projeto e sincronizar a automação, clique em **Reopen and sync project** (Reabrir e sincronizar projeto). ![Selecione o botão "Reopen and resync project" (Reabrir e sincronizar projeto)](/assets/images/help/projects/reopen-and-sync-project.png)
-    - Para reabrir o quadro de projeto sem sincronizar a automação, use o menu suspenso reopen (reabrir) e clique em **Reopen only** (Somente reabrir). Em seguida, clique em **Reopen only** (Somente reabrir). ![Menu suspenso de reabertura de quadro de projeto fechado](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png)
+3. Choose whether to sync automation for your {% data variables.projects.projects_v1_board %} or reopen your {% data variables.projects.projects_v1_board %} without syncing.
+    - To reopen your {% data variables.projects.projects_v1_board %} and sync automation, click **Reopen and sync project**. ![Selecione o botão "Reopen and resync project" (Reabrir e sincronizar projeto)](/assets/images/help/projects/reopen-and-sync-project.png)
+    - To reopen your {% data variables.projects.projects_v1_board %} without syncing automation, using the reopen drop-down menu, click **Reopen only**. Em seguida, clique em **Reopen only** (Somente reabrir). ![Menu suspenso de reabertura de quadro de projeto fechado](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png)
 
 ## Leia mais
 
-- "[Configurar a automação para quadros de projeto](/articles/configuring-automation-for-project-boards)"
+- "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
index c06ab49427..3ad663c727 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
@@ -1,27 +1,25 @@
 ---
-title: Adicionar problemas e pull requests a um quadro de projeto
-intro: Você pode adicionar problemas e pull requests a um quadro de projeto na forma de cartões e fazer a triagem deles em colunas.
+title: 'Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}'
+intro: 'You can add issues and pull requests to a {% data variables.projects.projects_v1_board %} in the form of cards and triage them into columns.'
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board
   - /articles/adding-issues-and-pull-requests-to-a-project
   - /articles/adding-issues-and-pull-requests-to-a-project-board
   - /github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
-shortTitle: Adicionar issues & PRs ao quadro
+shortTitle: 'Add issues & PRs to {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
-Você pode adicionar cartões de problema ou pull request ao seu quadro de projeto ao:
+You can add issue or pull request cards to your {% data variables.projects.projects_v1_board %} by:
 - Arrastar os cartões da seção **Triage** (Triagem) na barra lateral.
 - Digitar a URL do problema ou da pull request em um cartão.
-- Pesquisar problemas ou pull requests na barra lateral de pesquisa do quadro de projeto.
+- Searching for issues or pull requests in the {% data variables.projects.projects_v1_board %} search sidebar.
 
 É possível colocar 2.500 cartões, no máximo, em cada coluna do projeto. Se uma coluna atingir o número máximo de cartões, nenhum cartão poderá ser movido para essa coluna.
 
@@ -29,28 +27,28 @@ Você pode adicionar cartões de problema ou pull request ao seu quadro de proje
 
 {% note %}
 
-**Observação:** também é possível adicionar observações ao seu quadro de projeto para que sirvam de lembretes de tarefas, referências a problemas e pull requests de qualquer repositório no {% data variables.product.product_name %} ou para adicionar informações relacionadas ao seu quadro de projeto. Para obter mais informações, consulte "[Adicionar observações a um quadro de projeto](/articles/adding-notes-to-a-project-board)".
+**Note:** You can also add notes to your project board to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your {% data variables.projects.projects_v1_board %}. Para obter mais informações, consulte "[Adicionar observações a um quadro de projeto](/articles/adding-notes-to-a-project-board)".
 
 {% endnote %}
 
 {% data reusables.project-management.edit-in-project %}
 
-{% data reusables.project-management.link-repos-to-project-board %} Quando você pesquisa problemas ou pull requests para adicionar ao quadro de projeto, a pesquisa automaticamente é colocada no escopo de seus repositórios vinculados. É possível remover esses qualificadores para pesquisar em todos os repositórios da organização. Para obter mais informações, consulte "[Vincular um repositório a um quadro de projeto](/articles/linking-a-repository-to-a-project-board)".
+{% data reusables.project-management.link-repos-to-project-board %} When you search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %}, the search automatically scopes to your linked repositories. É possível remover esses qualificadores para pesquisar em todos os repositórios da organização. Para obter mais informações, consulte "[Vincular um repositório a um quadro de projeto](/articles/linking-a-repository-to-a-project-board)".
 
-## Adicionar problemas e pull requests a um quadro de projeto
+## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %}
 
-1. Navegue até o quadro de projeto onde deseja adicionar problemas e pull requests.
-2. No quadro de projeto, clique em {% octicon "plus" aria-label="The plus icon" %} **Add cards** (Adicionar cartões). ![Botão Add cards (Adicionar cartões)](/assets/images/help/projects/add-cards-button.png)
-3. Pesquise problemas e pull requests para adicionar ao quadro de projeto usando qualificadores de pesquisa. Para obter mais informações sobre qualificadores de pesquisa que você pode usar, consulte [Pesquisar problemas](/articles/searching-issues)". ![Pesquisar problemas e pull requests](/assets/images/help/issues/issues_search_bar.png)
+1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add issues and pull requests.
+2. In your {% data variables.projects.projects_v1_board %}, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**. ![Botão Add cards (Adicionar cartões)](/assets/images/help/projects/add-cards-button.png)
+3. Search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %} using search qualifiers. Para obter mais informações sobre qualificadores de pesquisa que você pode usar, consulte [Pesquisar problemas](/articles/searching-issues)". ![Pesquisar problemas e pull requests](/assets/images/help/issues/issues_search_bar.png)
 
   {% tip %}
 
   **Dicas:**
     - Também é possível adicionar um problema ou uma pull request digitando a URL em um cartão.
-    - Se estiver trabalhando em um recurso específico, você poderá aplicar uma etiqueta a cada pull request ou problema relacionado a esse recurso e, assim, adicionar facilmente cartões ao quadro de projeto pesquisando o nome da etiqueta. Para obter mais informações, consulte "[Aplicar etiquetas a problemas e pull requests](/articles/applying-labels-to-issues-and-pull-requests)".
+    - If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your {% data variables.projects.projects_v1_board %} by searching for the label name. Para obter mais informações, consulte "[Aplicar etiquetas a problemas e pull requests](/articles/applying-labels-to-issues-and-pull-requests)".
 
   {% endtip %}
-4. Na lista filtrada de problemas e pull requests, arraste o cartão que deseja adicionar ao quadro de projeto e solte-o na coluna correta. Como alternativa, você pode mover cartões usando os atalhos de teclado. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+4. From the filtered list of issues and pull requests, drag the card you'd like to add to your {% data variables.projects.projects_v1_board %} and drop it in the correct column. Como alternativa, você pode mover cartões usando os atalhos de teclado. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
 
     {% tip %}
 
@@ -58,16 +56,16 @@ Você pode adicionar cartões de problema ou pull request ao seu quadro de proje
 
     {% endtip %}
 
-## Adicionar problemas e pull request a um quadro de projeto da barra lateral
+## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %} from the sidebar
 
 1. No lado direito de um problema ou uma pull request, clique em **Projects (Projetos) {% octicon "gear" aria-label="The Gear icon" %}**. ![Botão Project board (Quadro de projeto) na barra lateral](/assets/images/help/projects/sidebar-project.png)
-2. Clique na aba **Recent** (Recente), **Repository** (Repositório), **User** (Usuário) ou **Organization** (Organização) do quadro de projeto ao qual deseja adicionar. ![Guias Recent (Recente), Repository (Repositório) e Organization (Organização)](/assets/images/help/projects/sidebar-project-tabs.png)
+2. Click the **Recent**, **Repository**,**User**, or **Organization** tab for the {% data variables.projects.projects_v1_board %} you would like to add to. ![Guias Recent (Recente), Repository (Repositório) e Organization (Organização)](/assets/images/help/projects/sidebar-project-tabs.png)
 3. Digite o nome do projeto no campo **Filter projects** (Filtrar projetos). ![Caixa de pesquisa Project board (Quadro de projeto)](/assets/images/help/projects/sidebar-search-project.png)
-4. Selecione um ou mais quadros de projeto ao qual você deseja adicionar o problema ou pull request. ![Quadro de projeto selecionado](/assets/images/help/projects/sidebar-select-project.png)
-5. Clique em {% octicon "triangle-down" aria-label="The down triangle icon" %} e depois na coluna onde você quer seu problema ou pull request. O cartão irá para a parte inferior da coluna do quadro de projeto que você selecionou. ![Menu Move card to column (Mover cartão para coluna)](/assets/images/help/projects/sidebar-select-project-board-column-menu.png)
+4. Select one or more {% data variables.projects.projects_v1_boards %} where you want to add the issue or pull request. ![Quadro de projeto selecionado](/assets/images/help/projects/sidebar-select-project.png)
+5. Clique em {% octicon "triangle-down" aria-label="The down triangle icon" %} e depois na coluna onde você quer seu problema ou pull request. The card will move to the bottom of the {% data variables.projects.projects_v1_board %} column you select. ![Menu Move card to column (Mover cartão para coluna)](/assets/images/help/projects/sidebar-select-project-board-column-menu.png)
 
 ## Leia mais
 
-- "[Sobre quadros de projetos](/articles/about-project-boards)"
-- "[Editar um quadro de projeto](/articles/editing-a-project-board)"
-- "[Filtrar cartões em um quadro de projeto](/articles/filtering-cards-on-a-project-board)"
+- "[Sobre o {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"
+- "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
index bd62e3ce37..3d312dbd2d 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
@@ -1,19 +1,17 @@
 ---
-title: Adicionar observações a um quadro de projeto
-intro: Você pode adicionar observações a um quadro de projeto para que sirvam como lembretes de tarefas ou para adicionar informações relacionadas ao quadro de projeto.
+title: 'Adding notes to a {% data variables.product.prodname_project_v1 %}'
+intro: 'You can add notes to a {% data variables.projects.projects_v1_board %} to serve as task reminders or to add information related to the {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board
   - /articles/adding-notes-to-a-project
   - /articles/adding-notes-to-a-project-board
   - /github/managing-your-work-on-github/adding-notes-to-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
-shortTitle: Adicionar notas ao quadro
+shortTitle: 'Add notes to {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
@@ -23,17 +21,17 @@ shortTitle: Adicionar notas ao quadro
 **Dicas:**
 - É possível formatar a observação usando a sintaxe markdown. Por exemplo, você pode usar títulos, links, listas de tarefas ou emojis. Para obter mais informações, consulte "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax)".
 - Você pode arrastar e soltar ou usar atalhos de teclado para reordenar observações e movê-las entre colunas. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
-- Seu quadro de projeto deve ter pelo menos uma coluna para que seja possível adicionar observações. Para obter mais informações, consulte "[Criar um quadro de projeto](/articles/creating-a-project-board)".
+- Your {% data variables.projects.projects_v1_board %} must have at least one column before you can add notes. Para obter mais informações, consulte "[Criar um quadro de projeto](/articles/creating-a-project-board)".
 
 {% endtip %}
 
-Ao adicionar a uma observação uma URL para um problema, uma pull request ou outro quadro de projeto, você vê uma visualização em um cartão de resumo abaixo do seu texto.
+When you add a URL for an issue, pull request, or another {% data variables.projects.projects_v1_board %} to a note, you'll see a preview in a summary card below your text.
 
 ![Cartões de quadro de projeto mostrando a visualização de um problema e outro quadro de projeto](/assets/images/help/projects/note-with-summary-card.png)
 
-## Adicionar observações a um quadro de projeto
+## Adding notes to a {% data variables.projects.projects_v1_board %}
 
-1. Navegue até o quadro de projeto onde deseja adicionar observações.
+1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add notes.
 2. Na coluna que deseja adicionar uma observação, clique em {% octicon "plus" aria-label="The plus icon" %}. ![Ícone de mais no header da coluna](/assets/images/help/projects/add-note-button.png)
 3. Digite sua observação e clique em **Add** (Adicionar). ![Campo para digitar uma observação e botão Add card (Adicionar cartão)](/assets/images/help/projects/create-and-add-note-button.png)
 
@@ -51,17 +49,17 @@ Quando você converte uma observação em um problema, o problema é criado auto
 
 {% tip %}
 
-**Dica:** é possível adicionar conteúdo no texto da observação para fazer @menção a alguém, vinculá-la a outro problema ou pull request e adicionar emoji. Esses recursos markdown em estilo {% data variables.product.prodname_dotcom %} não são aceitos em observações do quadro de projeto, mas depois que a observação for convertida em um problema, ela será exibida corretamente. Para obter mais informações sobre o uso desses recursos, consulte "[Sobre escrita e formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)".
+**Dica:** é possível adicionar conteúdo no texto da observação para fazer @menção a alguém, vinculá-la a outro problema ou pull request e adicionar emoji. These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within {% data variables.projects.projects_v1_board %} notes, but once your note is converted to an issue, they'll appear correctly. Para obter mais informações sobre o uso desses recursos, consulte "[Sobre escrita e formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)".
 
 {% endtip %}
 
 1. Navegue para a observação que deseja converter em um problema.
 {% data reusables.project-management.project-note-more-options %}
 3. Clique em **Convert to issue** (Converter em problema). ![Botão Convert to issue (Converter em problema)](/assets/images/help/projects/convert-to-issue.png)
-4. Se o cartão estiver em um quadro de projeto em toda a organização, no menu suspenso, escolha o repositório ao qual deseja adicionar o problema. ![Menu suspenso listando repositórios onde é possível criar o problema](/assets/images/help/projects/convert-note-choose-repository.png)
+4. If the card is on an organization-wide {% data variables.projects.projects_v1_board %}, in the drop-down menu, choose the repository you want to add the issue to. ![Menu suspenso listando repositórios onde é possível criar o problema](/assets/images/help/projects/convert-note-choose-repository.png)
 5. Se desejar, edite o título do problema previamente preenchido e digite um texto para o problema. ![Campos para título e texto do problema](/assets/images/help/projects/convert-note-issue-title-body.png)
 6. Clique em **Convert to issue** (Converter em problema).
-7. A observação é convertida automaticamente em um problema. No quadro de projeto, o novo cartão de problema estará no mesmo local que a observação anterior.
+7. A observação é convertida automaticamente em um problema. In the {% data variables.projects.projects_v1_board %}, the new issue card will be in the same location as the previous note.
 
 ## Editar e remover uma observação
 
@@ -72,7 +70,7 @@ Quando você converte uma observação em um problema, o problema é criado auto
 
 ## Leia mais
 
-- "[Sobre quadros de projetos](/articles/about-project-boards)"
-- "[Criar um quadro de projeto](/articles/creating-a-project-board)"
-- "[Editar um quadro de projeto](/articles/editing-a-project-board)"
-- "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[Sobre o {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Criar um {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)"
+- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"
+- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
index 702986793e..860879dd30 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
@@ -1,31 +1,29 @@
 ---
-title: Arquivar cartões em um quadro de projeto
-intro: Você pode arquivar cartões de quadro de projeto para limpar seu fluxo de trabalho sem perder o contexto histórico de um projeto.
+title: 'Archiving cards on a {% data variables.product.prodname_project_v1 %}'
+intro: 'You can archive {% data variables.projects.projects_v1_board %} cards to declutter your workflow without losing the historical context of a project.'
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/archiving-cards-on-a-project-board
   - /articles/archiving-cards-on-a-project-board
   - /github/managing-your-work-on-github/archiving-cards-on-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
-shortTitle: Arquivar cartões no quadro
+shortTitle: 'Archive cards on {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
-A automação no quadro de projeto não se aplica a cartões do quadro de projeto arquivados. Por exemplo, se você fechar um problema no arquivamento de um quadro de projeto, o cartão arquivado não será movido automaticamente para a coluna "Done" (Concluído). Quando você restaura um cartão do arquivamento do quadro de projeto, o cartão retorna à coluna em que foi arquivada.
+Automation in your {% data variables.projects.projects_v1_board %} does not apply to archived {% data variables.projects.projects_v1_board %} cards. For example, if you close an issue in a {% data variables.projects.projects_v1_board %}'s archive, the archived card does not automatically move to the "Done" column. When you restore a card from the {% data variables.projects.projects_v1_board %} archive, the card will return to the column where it was archived.
 
-## Arquivar cartões em um quadro de projeto
+## Archiving cards on a {% data variables.projects.projects_v1_board %}
 
-1. Em um quadro de projeto, encontre o cartão que você deseja arquivar e clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Lista de opções para edição de um cartão do quadro de projeto](/assets/images/help/projects/select-archiving-options-project-board-card.png)
+1. In a {% data variables.projects.projects_v1_board %}, find the card you want to archive, then click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Lista de opções para edição de um cartão do quadro de projeto](/assets/images/help/projects/select-archiving-options-project-board-card.png)
 2. Clique em **Arquivar**. ![Opção de seleção de arquivamento no menu](/assets/images/help/projects/archive-project-board-card.png)
 
-## Restaurar cartões em um quadro de projeto usando a barra lateral
+## Restoring cards on a {% data variables.projects.projects_v1_board %} from the sidebar
 
 {% data reusables.project-management.click-menu %}
 2. Clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **View archive** (Exibir arquivamento). ![Opção de seleção de exibição de arquivamento no menu](/assets/images/help/projects/select-view-archive-option-project-board-card.png)
-3. Acima do cartão do quadro de projeto que deseja desarquivar, clique em **Restore** (Restaurar). ![Seleção da restauração do cartão do quadro de projeto](/assets/images/help/projects/restore-card.png)
+3. Above the {% data variables.projects.projects_v1_board %} card you want to unarchive, click **Restore**. ![Seleção da restauração do cartão do quadro de projeto](/assets/images/help/projects/restore-card.png)
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
index 0467f0d8ae..820a4f0846 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
@@ -1,25 +1,23 @@
 ---
-title: Filtrar cartões em um quadro de projeto
-intro: É possível filtrar um cartão em um quadro de projetos para pesquisar cartões específicos ou visualizar uma subcategoria de cartões.
+title: 'Filtering cards on a {% data variables.product.prodname_project_v1 %}'
+intro: 'You can filter the cards on a {% data variables.projects.projects_v1_board %} to search for specific cards or view a subset of the cards.'
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/filtering-cards-on-a-project-board
   - /articles/filtering-cards-on-a-project-board
   - /github/managing-your-work-on-github/filtering-cards-on-a-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
-shortTitle: Filtrar cartões no quadro
+shortTitle: 'Filter cards on {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
-Em um cartão, você pode clicar em qualquer responsável, marco ou etiqueta para filtrar o quadro de projeto por esse qualificador. Para limpar a pesquisa, você pode clicar no mesmo responsável, marco ou etiqueta novamente.
+On a card, you can click any assignee, milestone, or label to filter the {% data variables.projects.projects_v1_board %} by that qualifier. Para limpar a pesquisa, você pode clicar no mesmo responsável, marco ou etiqueta novamente.
 
-Também é possível usar a barra de pesquisa "Filter cards" (Fitrar cartões) que está na parte superior de cada quadro de projetos para pesquisar por cartões. Você pode filtrar cartões usando os seguintes qualificadores de pesquisa em qualquer combinação ou simplesmente digitando algum texto que você gostaria de pesquisar.
+You can also use the "Filter cards" search bar at the top of each {% data variables.projects.projects_v1_board %} to search for cards. Você pode filtrar cartões usando os seguintes qualificadores de pesquisa em qualquer combinação ou simplesmente digitando algum texto que você gostaria de pesquisar.
 
 - Filtrar cartões por autor com `author:USERNAME`
 - Filtrar cartões por responsável com `assignee:USERNAME` ou `no:assignee`
@@ -31,9 +29,9 @@ Também é possível usar a barra de pesquisa "Filter cards" (Fitrar cartões) q
 - Filtrar cartões por tipo com `type:issue`, `type:pr` ou `type:note`
 - Filtrar cartões por estado e tipo com `is:open`, `is:closed` ou `is:merged`; e `is:issue`, `is:pr` ou `is:note`
 - Filtrar cartões por problemas vinculados a um pull request por uma referência de fechamento usando `linked:pr`
-- Filtrar cartões por repositório em um quadro de projetos de toda a organização com `repo:ORGANIZATION/REPOSITORY`
+- Filter cards by repository in an organization-wide {% data variables.projects.projects_v1_board %} using `repo:ORGANIZATION/REPOSITORY`
 
-1. Navegue até o quadro de projetos que contém os cartões que você deseja filtrar.
+1. Navigate to the {% data variables.projects.projects_v1_board %} that contains the cards you want to filter.
 2. Acima da coluna cartão de projeto, clique na barra de pesquisa "Filter cards" (Filtrar cartões) e digite uma consulta para filtrar os cartões. ![Barra de pesquisa Filter card (Filtrar cartões)](/assets/images/help/projects/filter-card-search-bar.png)
 
 {% tip %}
@@ -44,6 +42,6 @@ Também é possível usar a barra de pesquisa "Filter cards" (Fitrar cartões) q
 
 ## Leia mais
 
-- "[Sobre quadros de projetos](/articles/about-project-boards)"
-- "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Adicionar observações em um quadro de projeto](/articles/adding-notes-to-a-project-board)"
+- "[Sobre o {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
index ab2c0e67e3..1ce3c25b30 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
@@ -1,12 +1,9 @@
 ---
-title: Acompanhar o andamento do quadro de projeto
-shortTitle: Monitorando projetos
-intro: Aprenda a monitorar o seu trabalho em quadros de projetos
+title: 'Tracking progress on your {% data variables.product.prodname_projects_v1 %}'
+shortTitle: 'Tracking {% data variables.product.prodname_projects_v1 %}'
+intro: 'Learn how to track your work on {% data variables.projects.projects_v1_board %}'
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Issues
   - Projects
@@ -18,6 +15,7 @@ children:
   - /archiving-cards-on-a-project-board
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
index e4c2db2eef..65720d30d9 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
@@ -1,25 +1,23 @@
 ---
-title: Acompanhar o andamento do quadro de projeto
-intro: Você pode ver o progresso geral do seu projeto na barra de progresso.
+title: 'Tracking progress on your {% data variables.product.prodname_project_v1 %}'
+intro: 'You can see the overall progress of your {% data variables.projects.projects_v1_board %} in a progress bar.'
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/tracking-progress-on-your-project-board
   - /articles/tracking-progress-on-your-project-board
   - /github/managing-your-work-on-github/tracking-progress-on-your-project-board
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
+  feature: projects-v1
 topics:
   - Pull requests
-shortTitle: Acompanhar o progresso no quadro
+shortTitle: 'Track progress on {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
 ---
 
 {% data reusables.projects.project_boards_old %}
 
 {% data reusables.project-management.project-progress-locations %}
 
-1. Acesse o quadro de projeto onde você deseja habilitar ou desabilitar o acompanhamento do progresso do projeto.
+1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to enable or disable project progress tracking.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.click-edit-sidebar-menu-project-board %}
 4. Selecione ou desmarque **Acompanhar o progresso do projeto**.
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/automating-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
similarity index 93%
rename from translations/pt-BR/content/issues/trying-out-the-new-projects-experience/automating-projects.md
rename to translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
index 977a41e10b..13c2ad11b0 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/automating-projects.md
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
@@ -1,33 +1,18 @@
 ---
-title: Automatizando projetos (beta)
-intro: 'Você pode usar fluxos de trabalho integrados ou a API e {% data variables.product.prodname_actions %} para gerenciar seus projetos.'
-allowTitleToDifferFromFilename: true
+title: 'Automating {% data variables.product.prodname_projects_v2 %} using Actions'
+shortTitle: Automating with Actions
+intro: 'You can use {% data variables.product.prodname_actions %} to automate your projects.'
 miniTocMaxHeadingLevel: 3
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/automating-projects
 type: tutorial
 topics:
   - Projects
-  - Workflows
-  - Project management
+allowTitleToDifferFromFilename: true
 ---
 
-{% data reusables.projects.projects-beta %}
-
-{% data reusables.projects.graphql-deprecation %}
-
-## Introdução
-
-Você pode adicionar a automação para ajudar a gerenciar seu projeto. Os projetos (beta) incluem fluxos de trabalho internos que você pode configurar por meio da interface do usuário. Além disso, você pode escrever fluxos de trabalho personalizados com a API do GraphQL e {% data variables.product.prodname_actions %}.
-
-## Fluxos de trabalho integrados
-
-{% data reusables.projects.about-workflows %}
-
-Você pode habilitar ou desabilitar os fluxos de trabalho internos para o seu projeto.
-
-{% data reusables.projects.enable-basic-workflow %}
 
 ## Fluxos de trabalho {% data variables.product.prodname_actions %}
 
@@ -39,11 +24,13 @@ Um projeto pode incluir vários repositórios, mas um fluxo de trabalho é espec
 
 Este artigo pressupõe que você tem um entendimento básico de {% data variables.product.prodname_actions %}. Para obter mais informações sobre {% data variables.product.prodname_actions %}, consulte "[{% data variables.product.prodname_actions %}](/actions).
 
-Para obter mais informações sobre outras alterações que você pode fazer no seu projeto por meio da API, consulte "[Usando a API para gerenciar projetos](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)".
+Para obter mais informações sobre outras alterações que você pode fazer no seu projeto por meio da API, consulte "[Usando a API para gerenciar projetos](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)".
+
+You may also want to use the **actions/add-to-project** workflow, which is maintained by {% data variables.product.company_short %} and will add the current issue or pull request to the project specified. For more information, see the [actions/add-to-project](https://github.com/actions/add-to-project) repository and README.
 
 {% note %}
 
-**Observação:** `GITHUB_TOKEN` tem o escopo para o nível de repositório e não pode acessar projetos (beta). Para acessar projetos (beta) você pode criar um {% data variables.product.prodname_github_app %} (recomendado para projetos organizacionais) ou um token de acesso pessoal (recomendado para projetos de usuários). Exemplos de fluxo de trabalho para ambas as abordagens são mostrados abaixo.
+**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access {% data variables.projects.projects_v2 %}. To access {% data variables.projects.projects_v2 %} you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a personal access token (recommended for user projects). Exemplos de fluxo de trabalho para ambas as abordagens são mostrados abaixo.
 
 {% endnote %}
 
@@ -66,6 +53,8 @@ Para obter mais informações sobre outras alterações que você pode fazer no
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Add PR to project
 on:
   pull_request:
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
new file mode 100644
index 0000000000..aa4bd02928
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
@@ -0,0 +1,16 @@
+---
+title: 'Automating your {% data variables.projects.project_v2 %}'
+shortTitle: 'Automating {% data variables.projects.projects_v2 %}'
+intro: 'Learn how to use the built-in workflows, {% data variables.product.prodname_actions %}, and the API to automate your projects.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /using-the-built-in-automations
+  - /using-the-api-to-manage-projects
+  - /automating-projects-using-actions
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
similarity index 94%
rename from translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
rename to translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
index e15fa8fe85..c1b555c1eb 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
@@ -1,22 +1,22 @@
 ---
-title: Usando a API para gerenciar projetos (beta)
-intro: Você pode usar a API do GraphQL para encontrar informações sobre projetos e atualizar projetos.
-versions:
-  fpt: '*'
-  ghec: '*'
+title: 'Using the API to manage {% data variables.product.prodname_projects_v2 %}'
+shortTitle: Automating with the API
+intro: You can use the GraphQL API to automate your projects.
 miniTocMaxHeadingLevel: 3
-allowTitleToDifferFromFilename: true
-type: how_to
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
+type: tutorial
 topics:
   - Projects
+allowTitleToDifferFromFilename: true
 ---
 
+Este artigo demonstra como usar a API do GraphQL para gerenciar um projeto. For more information about how to use the API in a {% data variables.product.prodname_actions %} workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)." Para uma lista completa dos tipos de dados disponíveis, consulte "[Referência](/graphql/reference)".
+
 {% data reusables.projects.graphql-deprecation %}
 
-Este artigo demonstra como usar a API do GraphQL para gerenciar um projeto. Para obter mais informações sobre como utilizar a API em um fluxo de trabalho {% data variables.product.prodname_actions %}, consulte "[Automatizando projetos (beta)](/issues/trying-out-the-new-projects-experience/automating-projects)". Para uma lista completa dos tipos de dados disponíveis, consulte "[Referência](/graphql/reference)".
-
-{% data reusables.projects.projects-beta %}
-
 ## Autenticação
 
 {% curl %}
@@ -714,3 +714,7 @@ gh api graphql -f query='
   }'
 ```
 {% endcli %}
+
+## Using webhooks
+
+You can use webhooks to subscribe to events taking place in your project. For example, when an item is edited, {% data variables.product.product_name %} can send a HTTP POST payload to the webhook's configured URL which can trigger automation on your server. For more information about webhooks, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)." To learn more about the `projects_v2_item` webhook event, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#projects_v2_item)."
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
new file mode 100644
index 0000000000..acd5e6979b
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
@@ -0,0 +1,23 @@
+---
+title: Using the built-in automations
+shortTitle: Using built-in automations
+intro: You can use built-in workflows to automate your projects.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+---
+
+{% note %}
+
+**Note:** Built-in workflows are available as part of a limited beta.
+
+{% endnote %}
+
+{% data reusables.projects.about-workflows %}
+
+Você pode habilitar ou desabilitar os fluxos de trabalho internos para o seu projeto.
+
+{% data reusables.projects.enable-basic-workflow %}
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
new file mode 100644
index 0000000000..835ab48e2b
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
@@ -0,0 +1,39 @@
+---
+title: 'Criar {% data variables.projects.project_v2 %}'
+intro: Learn how to create an organization or user project.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/creating-a-project
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+{% data variables.product.prodname_projects_v2 %} are an adaptable collection of items that stay up-to-date with {% data variables.product.company_short %} data. Your projects can track issues, pull requests, and ideas that you note down. Você pode adicionar campos personalizados e criar visualizações para fins específicos.
+
+## Criando um projeto
+
+### Criando um projeto de organização
+
+Organization projects can track issues and pull requests from the organization's repositories.
+
+{% data reusables.projects.create-project %}
+
+### Criando um projeto de usuário
+
+User projects can track issues and pull requests from the repositories owned by your personal account.
+
+{% data reusables.projects.create-user-project %}
+
+## Atualizando a descrição e o README do seu projeto
+
+{% data reusables.projects.project-description %}
+
+## Leia mais
+
+- "[Adding your project to a repository](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository)"
+- "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)"
+- "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)"
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/creating-projects/index.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
new file mode 100644
index 0000000000..34c2bf24af
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
@@ -0,0 +1,15 @@
+---
+title: 'Creating {% data variables.projects.projects_v2 %}'
+shortTitle: 'Creating {% data variables.projects.projects_v2 %}'
+intro: 'Learn about creating projects and migrating your {% data variables.projects.projects_v1_boards %}.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /creating-a-project
+  - /migrating-from-projects-classic
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/migrating-your-project.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
similarity index 70%
rename from translations/pt-BR/content/issues/trying-out-the-new-projects-experience/migrating-your-project.md
rename to translations/pt-BR/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
index 4164b9eeb5..3b67fade27 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/migrating-your-project.md
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
@@ -1,23 +1,24 @@
 ---
-title: Migrando seu projeto para Projetos (beta)
-intro: Você pode migrar seus projetos da experiência de projetos antigos para Projetos (beta).
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
+title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
+intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
+miniTocMaxHeadingLevel: 3
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/migrating-your-project
+type: tutorial
 topics:
   - Projects
-  - Organizations
+allowTitleToDifferFromFilename: true
 ---
 
+
 {% note %}
 
 **Notas:**
 
-- Projetos (beta) está atualmente na versão beta pública e sujeitos a alterações.
 - Se o projeto que você está migrando contiver mais de 1200 itens, os problemas abertos serão priorizados seguidos por pull requests abertos e, por último, observações. O espaço restante será usado para problemas fechados, pull requests mesclados e pull requests fechados. Os tens que não podem ser transferidos devido a esse limite serão transferidos para o arquivo. Se o limite de arquivamento de 10.000 itens for atingido, não será realizada a migração dos itens adicionais.
-- Os cartões das observações são convertidos em problemas de rascunho e os conteúdos são salvos no texto do problema do rascunho. Se parecer que a informação está faltando, torne visível qualquer campo oculto. Para obter mais informações, consulte "[Mostrando e ocultando campos](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#showing-and-hiding-fields)."
+- Os cartões das observações são convertidos em problemas de rascunho e os conteúdos são salvos no texto do problema do rascunho. Se parecer que a informação está faltando, torne visível qualquer campo oculto. Para obter mais informações, consulte "[Mostrando e ocultando campos](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
 - Não será realizada a migração da automação.
 - Não será realizada a migração da triagem, arquivos e atividades.
 - Após a migração, o novo projeto migrado e o projeto antigo não serão mantidos em sincronia.
@@ -26,7 +27,7 @@ topics:
 
 ## Sobre a migração do projeto
 
-Você pode migrar seus quadros de projeto para a experiência de todos os novos projetos (beta) e experimentar tabelas, várias visualizações, novas opções de automação e tipos de campo poderosos. Para obter mais informações, consulte "[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)".
+You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
 
 ## Migrando um quadro de projetos de organização
 
@@ -49,7 +50,7 @@ Você pode migrar seus quadros de projeto para a experiência de todos os novos
 
 {% note %}
 
-**Observação:** Projetos (beta) não é compatível com projetos do nível do repositório. Quando você migrar um quadro de projeto repositório, ele será transferido para a organização ou conta pessoal à qual pertence o projeto do repositório, e o projeto transferido será fixado no repositório original.
+**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. Quando você migrar um quadro de projeto repositório, ele será transferido para a organização ou conta pessoal à qual pertence o projeto do repositório, e o projeto transferido será fixado no repositório original.
 
 {% endnote %}
 
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
new file mode 100644
index 0000000000..4b8c36ea71
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
@@ -0,0 +1,98 @@
+---
+title: Customizing a view
+intro: 'Display the information you need by changing the layout, grouping, sorting in your project.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/customizing-your-project-views
+type: tutorial
+topics:
+  - Projects
+---
+
+
+## Alterando o layout do projeto
+
+Você pode visualizar o seu projeto como uma tabela ou como um quadro.
+
+{% data reusables.projects.open-view-menu %}
+1. Under "Layout", click either **Table** or **Board**. ![Screenshot showing layout option](/assets/images/help/projects-v2/table-or-board.png)
+
+
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Switch layout."
+
+## Exibindo e ocultando campos
+
+Você pode mostrar ou ocultar um campo específico.
+
+{% data reusables.projects.open-view-menu %}
+1. Under "Configuration", click {% octicon "note" aria-label="the note icon" %} and the list of currently shown fields. ![Screenshot showing show and hide fields menu option](/assets/images/help/projects-v2/show-hide-fields-menu-item.png)
+1. Select or deselect the fields you want to show or hide. ![Screenshot showing show and hide fields menu](/assets/images/help/projects-v2/show-hide-fields.png)
+
+You can also hide individual fields in table view.
+
+1. Next to the field you want to hide, click {% octicon "kebab-horizontal" aria-label="the kebab icon" %}. ![Screenshot showing field menu icon](/assets/images/help/projects-v2/modify-field-menu.png)
+1. Click {% octicon "eye-closed" aria-label="the eye closed icon" %} **Hide field**. ![Screenshot showing hide field menu option](/assets/images/help/projects-v2/hide-field-via-menu.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "show", "hide", or the name of the field.
+
+## Reordenando campos
+
+In table layout, you can change the order of fields.
+
+1. Click the field header. ![Screenshot showing the field header](/assets/images/help/projects-v2/select-field-header.png)
+2. While continuing to click, drag the field to the required location.
+
+## Reordenando linhas
+
+No layout da tabela, você pode alterar a ordem das linhas.
+
+1. Click the number at the start of the row. ![Screenshot showing the row number](/assets/images/help/projects-v2/select-row-number.png)
+2. While continuing to click, drag the row to the required location.
+
+## Ordenação por valores do campo
+
+No layout de tabela, você pode classificar itens por um valor de campo.
+
+{% note %}
+
+**Observação:** Quando uma tabela é ordenada, você não pode reordenar manualmente as linhas.
+
+{% endnote %}
+
+{% data reusables.projects.open-view-menu %}
+1. Click **Sort**. ![Screenshot showing the sort menu item](/assets/images/help/projects-v2/sort-menu-item.png)
+1. Click the field you want to sort by. ![Screenshot showing the sort menu](/assets/images/help/projects-v2/sort-menu.png)
+2. Optionally, to change the direction of the sort, click {% octicon "sort-desc" aria-label="the sort icon" %}. ![Screenshot showing sort order option](/assets/images/help/projects-v2/sort-order.png)
+3. Optionally, to remove a sort, click {% octicon "x" aria-label="the x icon" %} **No sorting** at the bottom of the list. ![Screenshot showing "no sorting"](/assets/images/help/projects-v2/no-sorting.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Sort by."
+
+## Agrupamento por valores de campo no layout de tabela
+
+No layout da tabela, você pode agrupar os itens por um valor de campo personalizado. Quando os itens são agrupados, se você arrastar um item para um novo grupo, será aplicado o valor desse grupo. Por exemplo, se você agrupar por "Status" e, em seguida, arrastar um item com um status de `Em andamento` para o grupo `Concluído` o status do item mudará para `Concluído`. Da mesma forma, ao adicionar um novo item a um grupo, o novo item será preenchido com o valor do grupo.
+
+{% note %}
+
+**Note:** You cannot group by title, labels, reviewers, or linked pull requests.
+
+{% endnote %}
+
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**. ![Screenshot showing the group menu item](/assets/images/help/projects-v2/group-menu-item.png)
+1. Click the field you want to group by. ![Screenshot showing the group menu](/assets/images/help/projects-v2/group-menu.png)
+2. Optionally, to disable grouping, click {% octicon "x" aria-label="the x icon" %} **No grouping** at the bottom of the list. ![Screenshot showing "no grouping"](/assets/images/help/projects-v2/no-grouping.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Group by."
+
+## Definir o campo da coluna no layout do quadro
+
+No layout do painel, você escolhe qualquer campo de seleção ou iteração para as suas colunas. Se você arrastar um item para uma nova coluna, o valor dessa coluna será aplicado ao item arrastado. Por exemplo, se você usar o campo "Status" para as colunas do seu quadro e, em seguida, arrastar um item com o status de `Em andamento` para a coluna `Concluído`, o status do item mudará para `Concluído`.
+
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "columns" aria-label="the columns icon" %} **Column field**. ![Screenshot showing the column field item](/assets/images/help/projects-v2/column-field-menu-item.png)
+1. Click the field you want to use. ![Screenshot showing the column field menu](/assets/images/help/projects-v2/column-field-menu.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Column field by."
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
new file mode 100644
index 0000000000..e70fdb4859
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
@@ -0,0 +1,31 @@
+---
+title: 'Filtering {% data variables.projects.projects_v2 %}'
+intro: Use filters to choose which items appear in your project's views.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/filtering-projects
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+Você pode personalizar as visualizações usando filtros para os metadados do item, como os responsáveis e as etiquetas aplicadas aos problemas e pelos campos no seu projeto. Você pode combinar filtros e salvá-los como visualizações. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)".
+
+Para filtrar um projeto, clique em {% octicon "filter" aria-label="The Filter icon" %} e comece a digitar os campos e valores que você gostaria de filtrar. À medida que você digita, serão exibidos os possíveis valores. You can also open the project command palette, by pressing {% data variables.projects.command-palette-shortcut %}, and type "Filter by" to choose from the available filters.
+
+Using multiple filters will act as a logical AND filter. For example, `label:bug status:"In progress"` will return items with the `bug` label with the "In progress" status. {% data variables.product.prodname_projects_v2 %} does not currently support logical OR filters across multiple fields.
+
+The same filters are available for charts you create using insights for {% data variables.product.prodname_projects_v2 %}, allowing you to filter the data used to create your charts. Para obter mais informações, consulte "[Usando insights com projetos](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects)".
+
+## Filtrando itens
+
+Clique em {% octicon "filter" aria-label="the filter icon" %} na parte superior da tabela para mostrar a barra "Filtrar por palavra-chave ou por campo". Comece a digitar o nome do campo e o valor que você deseja filtrar. À medida que você digita, serão exibidos os possíveis valores.
+
+{% data reusables.projects.projects-filters %}
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Filter by."
+
+No layout da tabela, você pode clicar nos dados de item para filtrar para itens com esse valor. Por exemplo, clique em um responsável para mostrar apenas itens para ele. Para remover o filtro, clique nos dados do item novamente.
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
new file mode 100644
index 0000000000..4f812bee04
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
@@ -0,0 +1,16 @@
+---
+title: 'Customizing views in your {% data variables.projects.project_v2 %}'
+shortTitle: Customizing views
+intro: 'You can create multiple views to look at your project from different angles, deciding which items to show and how to present them.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /customizing-a-view
+  - /filtering-projects
+  - /managing-your-views
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
new file mode 100644
index 0000000000..eee7e8fd48
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
@@ -0,0 +1,70 @@
+---
+title: Managing your views
+intro: 'Learn how to create, save, and manage your project views.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+---
+
+
+## Criando uma visualização do projeto
+
+As visualizações do projeto permitem que você visualize rapidamente os aspectos específicos do seu projeto. Cada visualização é exibida em uma guia separada no seu projeto.
+
+Por exemplo, você pode ter:
+- Uma visualização que mostra todos os itens ainda não iniciados (filtro de "Status").
+- Uma exibição que mostra a carga de trabalho para cada equipe (agrupar por um campo personalizado de "Equipe").
+- Uma visualização que mostra itens com a data mais antiga de envio (classificar por um campo de data).
+
+Para adicionar uma nova visualização:
+
+{% data reusables.projects.new-view %}
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "New view."
+
+A nova visualização é salva automaticamente.
+
+## Duplicating a view
+
+You can duplicate an existing view and use it as a base to make further changes.
+
+1. Switch to the view you want to duplicate.
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "versions" aria-label="the versions icon" %} **Duplicate view**. ![Screenshot showing the duplicate menu item](/assets/images/help/projects-v2/duplicate-view.png)
+
+## Salvando alterações em uma visualização
+
+Ao fazer alterações a uma visualização como, por exemplo, ordenação, reordenação, filtragem ou agrupamento de dados em uma visualização, será exibido um ponto ao lado do nome da visualização para indicar que existem alterações não salvas.
+
+![Indicador de alterações não salvas](/assets/images/help/projects/unsaved-changes.png)
+
+Se você não desejar salvar as alterações, você poderá ignorar este indicador. Ninguém mais verá as suas alterações.
+
+{% data reusables.projects.save-view %}
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Save view."
+
+## Reordenando as visualizações salvas
+
+Para alterar a ordem das abas que contêm as exibições salvas, clique e arraste uma aba para um novo local. A nova ordem da aba é salva automaticamente.
+
+## Renomeando uma visualização salva
+
+You can rename your saved views. A alteração de nome será salva automaticamente.
+
+1. Switch to the view you want to rename.
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "pencil" aria-label="the pencil icon" %} **Rename view**. ![Screenshot showing the rename menu item](/assets/images/help/projects-v2/rename-view.png)
+1. Type the new name for your view.
+1. To save your changes, press <kbd>Return</kbd>.
+
+## Excluindo uma visualização salva
+
+1. Switch to the view you want to delete.
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "trash" aria-label="the trasj icon" %} **Delete view**. ![Screenshot showing the rename delete item](/assets/images/help/projects-v2/delete-view.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Delete view."
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/index.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/index.md
new file mode 100644
index 0000000000..0c575a334f
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/index.md
@@ -0,0 +1,21 @@
+---
+title: 'Planning and tracking with {% data variables.product.prodname_projects_v2 %}'
+shortTitle: '{% data variables.product.prodname_projects_v2 %}'
+intro: 'Build adaptable projects to track your work on {% data variables.product.company_short %}.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /learning-about-projects
+  - /creating-projects
+  - /managing-items-in-your-project
+  - /understanding-field-types
+  - /customizing-views-in-your-project
+  - /automating-your-project
+  - /viewing-insights-from-your-project
+  - /managing-your-project
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
new file mode 100644
index 0000000000..a6217cb300
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
@@ -0,0 +1,49 @@
+---
+title: 'Sobre {% data variables.product.prodname_projects_v2 %}'
+intro: '{% data variables.product.prodname_projects_v2 %} is an adaptable, flexible tool for planning and tracking work on {% data variables.product.company_short %}.'
+allowTitleToDifferFromFilename: true
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/about-projects
+type: overview
+topics:
+  - Projects
+---
+
+## Sobre {% data variables.product.prodname_projects_v2 %}
+
+A project is an adaptable spreadsheet that integrates with your issues and pull requests on {% data variables.product.company_short %} to help you plan and track your work effectively. You can create and customize multiple views by filtering, sorting, grouping your issues and pull requests, adding custom fields to track metadata specific to your team, and visualize work with configurable charts. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes.
+
+### Mantendo-se atualizado
+
+Your projects are built from the issues and pull requests you add, creating direct references between your project and your work. Information is synced automatically to your project as you make changes, updating your views and charts. This integration works both ways, so that when you change information about a pull request or issue in your project, the pull request or issue reflects that information. For example, change an assignee in your project and that change is shown in your issue. You can take this integration even further, group your project by assignee, and make changes to issue assignment by dragging issues into the different groups.
+
+### Adicionando metadados às suas tarefas
+
+You can use custom fields to add metadata to your tasks and build a richer view of item attributes. You’re not limited to the built-in metadata (assignee, milestone, labels, etc.) that currently exists for issues and pull requests. For example, you can add the following metadata as custom fields:
+
+- A date field to track target ship dates.
+- A number field to track the complexity of a task.
+- A single select field to track whether a task is Low, Medium, or High priority.
+- A text field to add a quick note.
+- An iteration field to plan work week-by-week, including support for breaks.
+
+### Visualizando seu projeto de diferentes perspectivas
+
+Quickly answer your most pressing questions by tailoring your project view to give you the information you need. You can save these views, allowing you to quickly return to them as needed and make them available to your team. Views not only let you scope down the items listed but also offer two different layout options.
+
+Você pode ver seu projeto como um layout de tabela de alta densidade:
+
+![Tabela de projeto](/assets/images/help/issues/projects_table.png)
+
+Ou como um quadro:
+
+![Quadro de projeto](/assets/images/help/issues/projects_board.png)
+
+Para ajudar você a concentrar-se em aspectos específicos do seu projeto, você pode agrupar, ordenar ou filtrar itens:
+
+![Visualização do projeto](/assets/images/help/issues/project_view.png)
+
+For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
similarity index 64%
rename from translations/pt-BR/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
rename to translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
index c57f9a9744..8ad25b526c 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
@@ -1,11 +1,12 @@
 ---
-title: Práticas recomendadas para gerenciar projetos (beta)
-intro: 'Aprenda dicas para gerenciar seus projetos em {% data variables.product.company_short %}.'
+title: 'Práticas recomendadas para {% data variables.product.prodname_projects_v2 %}'
+intro: Learn tips for managing your projects.
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects
 type: overview
 topics:
   - Projects
@@ -13,9 +14,7 @@ topics:
   - Project management
 ---
 
-{% data reusables.projects.projects-beta %}
-
-Você pode usar os projetos para gerenciar seu trabalho em {% data variables.product.company_short %}, onde os seus problemas e pull requests são gerados. Leia sobre as dicas para gerenciar seus projetos de forma eficiente e eficaz. Para obter mais informações sobre projetos, consulte "[Sobre projetos](/issues/trying-out-the-new-projects-experience/about-projects)".
+You can use {% data variables.product.prodname_projects_v2 %} to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. Leia sobre as dicas para gerenciar seus projetos de forma eficiente e eficaz. Para obter mais informações sobre {% data variables.product.prodname_projects_v2 %}, consulte "[Sobre {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
 
 ## Dividir problemas grandes em problemas menores
 
@@ -39,7 +38,7 @@ Por exemplo:
 
 Os READMEs de projeto são compatíveis com Markdown, o que permite que você utilize imagens e formatação avançada, como links, listas e cabeçalhos.
 
-Para obter mais informações, consulte "[Criando um projeto (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#updating-your-project-description-and-readme)".
+Para obter mais informações, consulte "[Criando um {% data variables.projects.project_v2 %}](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)."
 
 ## Usar visualizações
 
@@ -51,32 +50,32 @@ Por exemplo:
 - Agrupar por um campo personalizado de prioridade para monitorar o volume de itens de alta prioridade
 - Ordenar por um campo de data personalizado para exibir os itens com a data de envio mais recente
 
-Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
+For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."
 
 ## Tenha uma única fonte de verdade
 
 Para evitar que as informações não fiquem sincronizadas, mantenha uma única fonte de verdade. Por exemplo, monitore uma data de envio em um único local, em vez de se espalhar por vários campos. Posteriormente, se a data de envio for alterada, você deverá apenas atualizar a data em um só lugar.
 
-Os projetos de {% data variables.product.company_short %} ficam automaticamente atualizados com os dados de {% data variables.product.company_short %}, como os responsáveis, marcos e etiquetas. Quando um desses campos é alterado em um problema ou pull request, a alteração é refletida automaticamente no seu projeto.
+{% data variables.product.prodname_projects_v2 %} automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. Quando um desses campos é alterado em um problema ou pull request, a alteração é refletida automaticamente no seu projeto.
 
 ## Usar automação
 
 Você pode automatizar as tarefas para gastar menos tempo com trabalho e mais tempo no próprio projeto. Quanto menos você precisar se lembrar de fazer manualmente, mais provável será que o seu projeto fique atualizado.
 
-Os projetos (beta) oferecem fluxos de trabalho integrados. Por exemplo, quando um problema é fechado, você pode definir automaticamente o status como "Concluído".
+{% data variables.product.prodname_projects_v2 %} offers built-in workflows. Por exemplo, quando um problema é fechado, você pode definir automaticamente o status como "Concluído".
 
 Além disso, {% data variables.product.prodname_actions %} e a API do GraphQL permitem que você automatize as tarefas de gerenciamento de projetos rotineiros. Por exemplo, para manter o controle de pull requests que estão aguardando revisão, você pode criar um fluxo de trabalho que adiciona um pull request a um projeto e define o status para "precisa de revisão"; este processo pode ser acionado automaticamente quando um pull request é marcado como "pronto para revisão."
 
-- Para obter um exemplo de fluxo de trabalho, consulte "[Automatizando projetos](/issues/trying-out-the-new-projects-experience/automating-projects)".
-- Para obter mais informações sobre a API, consulte "[Usando a API para gerenciar projetos](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)".
+- For an example workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)."
+- For more information about the API, see "[Using the API to manage {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)."
 - Para obter mais informações sobre {% data variables.product.prodname_actions %}, consulte ["{% data variables.product.prodname_actions %}](/actions)".
 
 ## Usar diferentes tipos de campos
 
 Aproveite os vários tipos de campo para atender às suas necessidades.
 
-Use um campo de iteração para agendar o trabalho ou criar uma linha do tempo. Você pode agrupar por iteração para ver se os itens estão equilibrados entre iterações, ou você pode filtrar para focar em uma única iteração. Os campos de iteração também permitem ver o trabalho que você realizou em iterações anteriores, o que pode ajudar no planejamento de velocidade e refletir sobre as realizações da sua equipe. Os campos de iteração também são compatíveis com pausas para mostrar quando você e sua equipe estão tirando tempo de suas iterações. Para obter mais informações, consulte "[Gerenciando iterações nos projetos](/issues/trying-out-the-new-projects-experience/managing-iterations). "
+Use um campo de iteração para agendar o trabalho ou criar uma linha do tempo. Você pode agrupar por iteração para ver se os itens estão equilibrados entre iterações, ou você pode filtrar para focar em uma única iteração. Os campos de iteração também permitem ver o trabalho que você realizou em iterações anteriores, o que pode ajudar no planejamento de velocidade e refletir sobre as realizações da sua equipe. Os campos de iteração também são compatíveis com pausas para mostrar quando você e sua equipe estão tirando tempo de suas iterações. For more information, see "[About iteration fields](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)."
 
 Use um único campo de seleção para rastrear informações sobre uma tarefa com base em uma lista de valores predefinidos. Por exemplo, monitore a prioridade ou a fase do projeto. Como os valores são selecionados a partir de uma lista predefinida, você pode facilmente agrupar ou filtrar focar em itens com um valor específico.
 
-Para obter mais informações sobre os diferentes tipos de campos, consulte "[Criando um projeto (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-custom-fields)".
+For more information about the different field types, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)."
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
new file mode 100644
index 0000000000..aed5d5a211
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
@@ -0,0 +1,15 @@
+---
+title: 'Learning about {% data variables.product.prodname_projects_v2 %}'
+intro: 'Learn about {% data variables.product.prodname_projects_v2 %} and how to make the very best of this powerful tool.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /about-projects
+  - /quickstart-for-projects
+  - /best-practices-for-projects
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
new file mode 100644
index 0000000000..392cead7b8
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
@@ -0,0 +1,151 @@
+---
+title: 'Quickstart for {% data variables.product.prodname_projects_v2 %}'
+intro: 'Experience the speed, flexibility, and customization of {% data variables.product.prodname_projects_v2 %} by creating a project in this interactive guide.'
+allowTitleToDifferFromFilename: true
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/quickstart
+type: quick_start
+topics:
+  - Projects
+---
+
+## Introdução
+
+This guide demonstrates how to use {% data variables.product.prodname_projects_v2 %} to plan and track work. Neste guia, você irá criar um novo projeto e adicionar um campo personalizado para acompanhar as prioridades das suas tarefas. Você também aprenderá como criar visualizações salvas que ajudem a comunicar as prioridades e o progresso com seus colaboradores.
+
+## Pré-requisitos
+
+Você pode criar um projeto de organização ou um projeto de usuário. Para criar um projeto de organização, você precisa de uma organização de {% data variables.product.prodname_dotcom %}. Para obter mais informações sobre a criação de uma organização, consulte "[Criar uma nova organização a partir do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)".
+
+Neste guia, você adicionará problemas existentes de repositórios pertencentes à sua organização (para projetos de organização) ou por você (para projetos de usuário) ao seu novo projeto. Para obter mais informações sobre a criação de problemas, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-an-issue)".
+
+## Criando um projeto
+
+Primeiro, crie um projeto de organização ou um projeto de usuário.
+
+### Criando um projeto de organização
+
+{% data reusables.projects.create-project %}
+
+### Criando um projeto de usuário
+
+{% data reusables.projects.create-user-project %}
+
+## Configurando a descrição e o README do seu projeto
+
+{% data reusables.projects.project-description %}
+
+## Adicionando problemas ao seu projeto
+
+Em seguida, adicione alguns problemas ao seu projeto.
+
+{% data reusables.projects.add-item-via-paste %}
+
+Repita os passos acima algumas vezes para adicionar vários problemas ao seu projeto.
+
+For more information and other ways to add issues to your project, or about other items you can add to your project, see "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)."
+
+## Adicionando rascunhos de problemas ao seu projeto
+
+Em seguida, adicione um rascunho ao seu projeto.
+
+{% data reusables.projects.add-draft-issue %}
+
+## Adding an iteration field
+
+Next, create an iteration field so you can plan and track your work over repeating blocks of time. Iterations can be configured to suit how you and your team works, with customizable lengths and the ability to insert breaks.
+
+{% data reusables.projects.new-field %}
+1. Select **Iteration** ![Screenshot showing the iteration option](/assets/images/help/projects-v2/new-field-iteration.png)
+3. Para mudar a duração de cada iteração, digite um novo número, em seguida, selecione o menu suspenso e clique em **dias** ou **semanas**. ![Screenshot showing the iteration duration](/assets/images/help/projects-v2/iteration-field-duration.png)
+4. Clique em **Salvar**. ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save-and-create.png)
+
+## Criando um campo para monitorar a prioridade
+
+Now, create a custom field named `Priority` and containing the values: `High`, `Medium`, or `Low`.
+
+{% data reusables.projects.new-field %}
+1. Select **Single select** ![Screenshot showing the single select option](/assets/images/help/projects-v2/new-field-single-select.png)
+1. Below "Options", type the first option, "High". ![Screenshot showing the single select option](/assets/images/help/projects-v2/priority-example.png)
+1. To add additional fields, for "Medium" and "Low", click **Add option**.
+1. Clique em **Salvar**. ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png)
+
+Especifique uma prioridade para todos os problemas no seu projeto.
+
+![Prioridades de exemplo](/assets/images/help/projects/priority_example.png)
+
+## Agrupar problemas por prioridade
+
+Em seguida, agrupe todos os itens do seu projeto por prioridade para facilitar o foco nos itens de alta prioridade.
+
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**. ![Screenshot showing the group menu item](/assets/images/help/projects-v2/group-menu-item.png)
+1. Click **Priority**. ![Screenshot showing the group menu](/assets/images/help/projects-v2/group-menu.png)
+
+Agora, transfira os problemas entre grupos para mudar a sua prioridade.
+
+1. Escolha um problema.
+2. Arraste e solte o problema em um grupo de prioridade diferente. Ao fazer isso, a prioridade do problema passará a ser a prioridade do seu novo grupo.
+
+![Transferir problemas entre grupos](/assets/images/help/projects/move_between_group.gif)
+
+## Salvando a visualização da prioridade
+
+Quando você agrupou os seus problemas por prioridade na etapa anterior, seu projeto exibiu um indicador para mostrar que a visualização foi modificada. Salve essas alterações para que os seus colaboradores vejam as tarefas agrupadas por prioridade.
+
+{% data reusables.projects.save-view %}
+
+Você pode compartilhar a URL com seu time para manter todos alinhados com as prioridades do projeto.
+
+Quando a visualização é salva, qualquer pessoa que abrir o projeto verá a visualização salva. Aqui, você agrupou por prioridade, mas você também pode adicionar outros modificadores como ordenação, filtro ou layout. Em seguida, você criará uma nova exibição com o layout modificado.
+
+## Adicionando um layout de quadro
+
+Para ver o progresso dos problemas do seu projeto, você pode alternar para o layout do quadro.
+
+O layout do quadro é baseado no campo de status. Portanto, especifique um status para cada problema no seu projeto.
+
+![Status do exemplo](/assets/images/help/projects/status_example.png)
+
+Em seguida, crie uma nova visualização.
+
+{% data reusables.projects.new-view %}
+
+Em seguida, mude para o layout do quadro.
+
+{% data reusables.projects.open-view-menu %}
+1. Under "Layout", click **Board**. ![Screenshot showing layout option](/assets/images/help/projects-v2/table-or-board.png)
+
+![Prioridades de exemplo](/assets/images/help/projects/example_board.png)
+
+Quando você alterou o layout, o projeto exibiu um indicador para mostrar que a visualização foi modificada. Salve esta visualização para que você e seus colaboradores possam acessá-la facilmente no futuro.
+
+{% data reusables.projects.save-view %}
+
+Para indicar o propósito da visão, dê um nome descritivo.
+
+{% data reusables.projects.open-view-menu %}
+1. Click {% octicon "pencil" aria-label="the pencil icon" %} **Rename view**. ![Screenshot showing the rename menu item](/assets/images/help/projects-v2/rename-view.png)
+1. Type the new name for your view.
+1. To save changes, press <kbd>Return</kbd>.
+
+![Prioridades de exemplo](/assets/images/help/projects/project-view-switch.gif)
+
+## Configure a automação integrada
+
+Por fim, adicione um fluxo de trabalho construído para definir o status como **Todo** quando um item for adicionado ao seu projeto.
+
+1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png)
+1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. ![Screenshot showing the 'Workflows' menu item](/assets/images/help/projects-v2/workflows-menu-item.png)
+1. Em **Fluxos de trabalho padrão**, clique em **Item adicionado ao projeto**. ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png)
+1. Ao lado de **Quando**, certifique-se de que `problemas` e `pull requests` estejam selecionados. ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png)
+1. Ao lado de **Definir**, selecione **Status:Todo**. ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png)
+1. Clique na opção **Desabilitada** para habilitar o fluxo de trabalho. ![Screenshot showing the "enable" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png)
+
+## Leia mais
+
+- "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)"
+- "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)"
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
new file mode 100644
index 0000000000..950c694b86
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
@@ -0,0 +1,75 @@
+---
+title: 'Adding items to your {% data variables.projects.project_v2 %}'
+shortTitle: Adding items
+intro: 'Learn how to add pull requests, issues, and draft issues to your projects individually or in bulk.'
+miniTocMaxHeadingLevel: 4
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+Seu projeto pode acompanhar os rascunhos de problemas, problemas e pull requests.
+
+{% note %}
+
+**Note:** A project can contain a maximum of 1,200 items and 10,000 archived items.
+
+{% endnote %}
+
+### Adding issues and pull requests to a project
+
+#### Pasting the URL of an issue or pull request
+
+{% data reusables.projects.add-item-via-paste %}
+
+#### Pesquisando um problema ou pull request
+
+{% data reusables.projects.add-item-bottom-row %}
+2. Digite <kbd>#</kbd>.
+3. Selecione o repositório onde está localizado o pull request ou problema. Você pode digitar parte do nome do repositório para restringir suas opções. ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-repo.png)
+4. Selecione o problema ou pull request. Você pode digitar parte do título para restringir suas opções. ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-issue.png)
+
+#### Bulk adding issues and pull requests
+
+1. In the bottom row of the project, click {% octicon "plus" aria-label="plus icon" %}. ![Screenshot showing + button at the bottom of the project](/assets/images/help/projects-v2/omnibar-add.png)
+1. Click **Add item from repository**. ![Screenshot showing "add item from repository" menu item](/assets/images/help/projects-v2/add-bulk-menu-item.png)
+{% data reusables.projects.bulk-add %}
+
+#### Adicionando vários problemas ou pull requests de um repositório
+
+1. No {% data variables.product.product_location %}, acesse o repositório que contém os problemas ou pull requests que você deseja adicionar ao projeto.
+{% data reusables.repositories.sidebar-issue-pr %}
+1. À esquerda de cada título do problema, selecione os problemas que você deseja adicionar ao seu projeto. ![Captura de tela que mostra caixa de seleção para selecionar problema ou pull request](/assets/images/help/issues/select-issue-checkbox.png)
+1. Opcionalmente, para selecionar cada problema ou pull request na página, na parte superior da lista de problemas ou pull requests, selecione tudo. ![Captura de tela que mostra caixa de seleção para selecionar todos na tela](/assets/images/help/issues/select-all-checkbox.png)
+1. Above the list of issues or pull requests, click **Projects**. ![Screenshot showing projects option](/assets/images/help/projects-v2/issue-index-project-menu.png)
+1. Clique nos projetos aos quais você deseja adicionar os problemas selecionados ou pull requests. ![Captura de tela que mostra caixa de seleção para selecionar todos na tela](/assets/images/help/projects-v2/issue-index-select-project.png)
+
+#### Atribuindo um projeto de dentro de um problema ou pull request
+
+1. Acesse o problema ou pull request que você deseja adicionar a um projeto.
+2. Na barra lateral, clique em **Projetos**. ![Screenshot showing "Projects" in the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-projects.png)
+3. Select the project that you want to add the issue or pull request to. ![Screenshot showing selecting a project from the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-select-project.png)
+4. Optionally, populate the custom fields. ![Barra lateral do projeto](/assets/images/help/projects-v2/issue-edit-project-sidebar.png)
+
+#### Using the command palette to add an issue or pull request
+
+1. {% data reusables.projects.open-command-palette %}
+1. Start typing "Add items" and press <kbd>Return</kbd>.
+{% data reusables.projects.bulk-add %}
+
+### Criando problemas de rascunho
+
+Os rascunhos são úteis para capturar ideias rapidamente. Unlike issues and pull requests that are referenced from your repositories, draft issues exist only in your project.
+
+{% data reusables.projects.add-draft-issue %}
+
+Os problemas do rascunho podem ter um título, texto, responsável e quaisquer campos personalizados do seu projeto. Para preencher o repositório, etiquetas ou marcos para o rascunho de um problema, você deverá primeiro converter o rascunho do problema em um problema. Para obter mais informações, consulte "[Convertendo rascunhos de problema em problemas](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues). "
+
+{% note %}
+
+**Observação**: Os usuários não receberão notificações quando forem atribuídos ou mencionados em um rascunho de problema, a menos que o rascunho do probelam seja convertido em um problema.
+
+{% endnote %}
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
new file mode 100644
index 0000000000..637ad1222d
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
@@ -0,0 +1,39 @@
+---
+title: 'Archiving items from your {% data variables.projects.project_v2 %}'
+shortTitle: Archiving items
+intro: 'You can archive items, keeping them available to restore, or permanently delete them.'
+miniTocMaxHeadingLevel: 2
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+## Archiving items
+
+Você pode arquivar um item para manter o contexto sobre o item no projeto, mas removê-lo das visualizações do projeto.
+
+{% data reusables.projects.select-an-item %}
+{% data reusables.projects.open-item-menu %}
+1. Clique em **Arquivar**. ![Screenshot showing archive option](/assets/images/help/projects-v2/archive-menu-item.png)
+1. When prompted, confirm your choice by clicking **Archive**. ![Screenshot showing archive prompt](/assets/images/help/projects-v2/archive-item-prompt.png)
+
+## Restaurando itens arquivados
+
+1. Navigate to your project.
+1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png)
+1. In the menu, click {% octicon "archive" aria-label="The archive icon" %} **Archived items**. ![Screenshot showing the 'Archived items' menu item](/assets/images/help/projects-v2/archived-items-menu-item.png)
+1. Opcionalmente, para filtrar os itens arquivados exibidos, digite seu filtro na caixa de texto acima da lista de itens. For more information about the available filters, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)." ![Captura de tela que mostra o campo para filtrar itens arquivados](/assets/images/help/issues/filter-archived-items.png)
+1. To the left of each item title, select the items you would like to restore. ![Captura de tela que mostra as caixas de seleção próximas aos itens arquivados](/assets/images/help/issues/select-archived-item.png)
+1. Para restaurar os itens selecionados, acima da lista de itens, clique em **Restaurar**. ![Captura de tela que mostra o botão "Restaurar"](/assets/images/help/issues/restore-archived-item-button.png)
+
+## Deleting items
+
+Você pode excluir um item para removê-lo do projeto completamente.
+
+{% data reusables.projects.select-an-item %}
+{% data reusables.projects.open-item-menu %}
+1. Click **Delete from project**. ![Screenshot showing delete option](/assets/images/help/projects-v2/delete-menu-item.png)
+1. When prompted, confirm your choice by clicking **Delete**. ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png)
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
new file mode 100644
index 0000000000..1772baf6f7
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
@@ -0,0 +1,27 @@
+---
+title: Convertendo rascunhos de problemas em problemas
+shortTitle: Converting draft issues
+intro: Learn how to convert draft issues into issues.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+---
+
+## Converting draft issues in table layout
+
+1. Click the {% octicon "triangle-down" aria-label="the item menu" %} on the draft issue that you want to convert. ![Screenshot showing item menu button](/assets/images/help/projects-v2/item-context-menu-button-table.png)
+2. Selecione **Converter para problema**. ![Screenshot showing "Convert to issue" option](/assets/images/help/projects-v2/item-convert-to-issue.png)
+3. Select the repository that you want to add the issue to. ![Screenshot showing repository selection](/assets/images/help/projects-v2/convert-to-issue-select-repo.png)
+
+## Converting draft issues in board layout
+
+1. Click the {% octicon "kebab-horizontal" aria-label="the item menu" %} on the draft issue that you want to convert. ![Screenshot showing item menu button](/assets/images/help/projects-v2/item-context-menu-button-board.png)
+2. Selecione **Converter para problema**. ![Screenshot showing "Convert to issue" option](/assets/images/help/projects-v2/item-convert-to-issue.png)
+3. Select the repository that you want to add the issue to. ![Screenshot showing repository selection](/assets/images/help/projects-v2/convert-to-issue-select-repo.png)
+
+## Leia mais
+
+- "[Creating draft issues](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project#creating-draft-issues)"
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
new file mode 100644
index 0000000000..0d43deeba0
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
@@ -0,0 +1,16 @@
+---
+title: 'Managing items in your {% data variables.projects.project_v2 %}'
+shortTitle: 'Managing items in your {% data variables.projects.project_v2 %}'
+intro: 'Learn how to add and manage issues, pull requests, and draft issues.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /adding-items-to-your-project
+  - /converting-draft-issues-to-issues
+  - /archiving-items-from-your-project
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
new file mode 100644
index 0000000000..6cac0f2e88
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
@@ -0,0 +1,22 @@
+---
+title: 'Adding your {% data variables.projects.project_v2 %} to a repository'
+shortTitle: 'Adding a {% data variables.projects.project_v2 %} to a repo'
+intro: 'You can add your {% data variables.projects.project_v2 %} to a repository to make it accessible from that repository.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+Você pode listar projetos relevantes em um repositório. Você só pode listar projetos que pertencem ao mesmo usuário ou organização proprietária do repositório.
+
+Para que os participantes do repositório vejam um projeto listado em um repositório, eles deverão ter visibilidade sobre o projeto. For more information, see "[Managing visibility of your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)" and "[Managing access to your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)."
+
+1. No {% data variables.product.prodname_dotcom %}, navegue até a página principal do seu repositório.
+1. Clique em {% octicon "table" aria-label="the project icon" %} **Projetos**. ![Screenshot showing projects tab in a repository](/assets/images/help/projects-v2/repo-tab.png)
+1. Clique **Adicionar projeto**. ![Screenshot showing "Add project" button](/assets/images/help/projects-v2/add-to-repo-button.png)
+1. In the search bar that appears, search for projects that are owned by the same user or organization that owns the repository. ![Screenshot showing searching for a project](/assets/images/help/projects-v2/add-to-repo-search.png)
+1. Click on a project to list it in your repository. ![Screenshot showing "Add project" button](/assets/images/help/projects-v2/add-to-repo.png)
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
similarity index 77%
rename from translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-projects.md
rename to translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
index 947527864a..e77d325294 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-projects.md
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
@@ -1,16 +1,19 @@
 ---
-title: Gerenciando projetos (beta)
-intro: Você pode fechar e reabrir projetos ou pode excluir projetos permanentemente.
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
+title: 'Closing and deleting your {% data variables.projects.projects_v2 %}'
+shortTitle: 'Closing and deleting {% data variables.projects.projects_v2 %}'
+intro: 'Learn about closing, re-opening, and permanently deleting a {% data variables.projects.project_v2 %}.'
+miniTocMaxHeadingLevel: 3
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-projects
+type: tutorial
 topics:
   - Projects
-  - Organizations
+allowTitleToDifferFromFilename: true
 ---
 
+
 ## Excluindo um projeto
 
 Você pode excluir um projeto para removê-lo permanentemente.
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
new file mode 100644
index 0000000000..ad6852040f
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
@@ -0,0 +1,16 @@
+---
+title: 'Managing your {% data variables.projects.project_v2 %}'
+intro: Learn how to manage your projects and control visibility and access.
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /managing-visibility-of-your-projects
+  - /managing-access-to-your-projects
+  - /closing-and-deleting-your-projects
+  - /adding-your-project-to-a-repository
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
similarity index 61%
rename from translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
rename to translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
index 7207800978..13f7fe36ae 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
@@ -1,17 +1,18 @@
 ---
-title: Gerenciando acesso a projetos (beta)
-intro: 'Você pode controlar quem pode visualizar, editar ou gerenciar seus projetos.'
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
+title: 'Managing access to your {% data variables.projects.projects_v2 %}'
+shortTitle: 'Managing {% data variables.projects.project_v2 %} access'
+intro: 'Learn how to manage team and individual access to your {% data variables.projects.project_v2 %}.'
+miniTocMaxHeadingLevel: 3
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-access-to-projects
+type: tutorial
 topics:
   - Projects
-  - Organizations
+allowTitleToDifferFromFilename: true
 ---
 
-{% data reusables.projects.projects-beta %}
 
 ## Sobre o acesso ao projeto
 
@@ -28,8 +29,8 @@ Administradores do projeto também podem controlar a visibilidade do seu projeto
 A função base padrão é `gravar`, o que significa que todos na organização podem ver e editar o seu projeto. Para alterar o acesso ao projeto para todos da organização, você pode alterar a função-base. As alterações na função-base afetam apenas os integrantes da organização que não são proprietários da organização e a quem não é concedido acesso individual.
 
 {% data reusables.projects.project-settings %}
-1. Clique em **Gerenciar acesso**.
-2. Em **Função-base**, selecione a função-padrão.
+1. Clique em **Gerenciar acesso**. ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png)
+2. Em **Função-base**, selecione a função-padrão. ![Screenshot showing the base role menu](/assets/images/help/projects-v2/base-role.png)
    - **Sem acesso**: Somente os proprietários e usuários da organização com acesso individual pode ver o projeto. Os proprietários da organização também são administradores do projeto.
    - **Leitura**: Todos na organização podem ver o projeto. Os proprietários da organização também são administradores do projeto.
    - **Gravação**: Todos os integrantes da organização podem ver e editar o projeto. Os proprietários da organização também são administradores do projeto.
@@ -42,23 +43,24 @@ Também é possível adicionar equipes, colaboradores externos e integrantes da
 Você pode apenas convidar um usuário individual para colaborar no projeto a nível da organização se ele já for integrante da organização ou colaborador externo em pelo menos um repositório na organização.
 
 {% data reusables.projects.project-settings %}
-1. Clique em **Gerenciar acesso**.
-2. Em **Convidar colaboradores**, pesquisa a equipe ou usuário individual que você deseja convidar.
-3. Selecione a função para o colaborador.
+1. Clique em **Gerenciar acesso**. ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png)
+2. Em **Convidar colaboradores**, pesquisa a equipe ou usuário individual que você deseja convidar. ![Screenshot showing searching for a collaborator](/assets/images/help/projects-v2/access-search.png)
+3. Select the role for the collaborator. ![Screenshot showing selecting a role](/assets/images/help/projects-v2/access-role.png)
    - **Leitura**: A equipe ou indivíduo pode visualizar o projeto.
    - **Gravação**: A equipe ou indivíduo pode visualizar e editar o projeto.
    - **Administrador**: A equipe ou indivíduo pode visualizar, editar e adicionar novos colaboradores ao projeto.
-4. Clique em **Convidar**.
+4. Clique em **Convidar**. ![Screenshot showing the invite button](/assets/images/help/projects-v2/access-invite.png)
 
 ### Gerenciando o acesso de um colaborador existente no seu projeto
 
 {% data reusables.projects.project-settings %}
-1. Clique em **Gerenciar acesso**.
+1. Clique em **Gerenciar acesso**. ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png)
 1. Em **Gerenciar acesso**, encontre o(s) colaborador(es) cujas permissões você deseja modificar.
 
-   Você pode usar o menu suspenso **Tipo** e **Função** para filtrar a lista de acesso.
+   Você pode usar o menu suspenso **Tipo** e **Função** para filtrar a lista de acesso. ![Screenshot showing a collaborator](/assets/images/help/projects-v2/access-find-member.png)
 
-1. Editar a função para o(s) colaborador(es) ou clique em {% octicon "trash" aria-label="the trash icon" %} para remover o colaborador.
+1. Edit the role for the collaborator(s). ![Screenshot showing changing a collaborator's role](/assets/images/help/projects-v2/access-change-role.png)
+1. Optionally, click **Remove** to remove the collaborator(s). ![Screenshot showing removing a collaborator](/assets/images/help/projects-v2/access-remove-member.png)
 
 ## Gerenciando acesso para projetos no nível do usuário
 
@@ -71,20 +73,21 @@ Isto afeta apenas os colaboradores do projeto, não os repositórios do projeto.
 {% endnote %}
 
 {% data reusables.projects.project-settings %}
-1. Clique em **Gerenciar acesso**.
-2. Em **Convidar colaboradores**, pesquise o usuário que você deseja convidar.
-3. Selecione a função para o colaborador.
+1. Clique em **Gerenciar acesso**. ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png)
+2. Em **Convidar colaboradores**, pesquise o usuário que você deseja convidar. ![Screenshot showing searching for a collaborator](/assets/images/help/projects-v2/access-search.png)
+3. Select the role for the collaborator. ![Screenshot showing selecting a role](/assets/images/help/projects-v2/access-role.png)
    - **Leitura**: O indivíduo pode visualizar o projeto.
    - **Gravação**: O indivíduo pode visualizar e editar o projeto.
    - **Administrador**: O indivíduo pode visualizar, editar e adicionar novos colaboradores ao projeto.
-4. Clique em **Convidar**.
+4. Clique em **Convidar**. ![Screenshot showing the invite button](/assets/images/help/projects-v2/access-invite.png)
 
 ### Gerenciando o acesso de um colaborador existente no seu projeto
 
 {% data reusables.projects.project-settings %}
-1. Clique em **Gerenciar acesso**.
+1. Clique em **Gerenciar acesso**. ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png)
 1. Em **Gerenciar acesso**, encontre o(s) colaborador(es) cujas permissões você deseja modificar.
 
-   Você pode usar o menu suspenso **Função** para filtrar a lista de acesso.
+   Você pode usar o menu suspenso **Tipo** e **Função** para filtrar a lista de acesso. ![Screenshot showing a collaborator](/assets/images/help/projects-v2/access-find-member.png)
 
-1. Editar a função para o(s) colaborador(es) ou clique em {% octicon "trash" aria-label="the trash icon" %} para remover o colaborador.
+1. Edit the role for the collaborator(s). ![Screenshot showing changing a collaborator's role](/assets/images/help/projects-v2/access-change-role.png)
+1. Optionally, click **Remove** to remove the collaborator(s). ![Screenshot showing removing a collaborator](/assets/images/help/projects-v2/access-remove-member.png)
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
new file mode 100644
index 0000000000..d2f3338166
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
@@ -0,0 +1,40 @@
+---
+title: 'Managing visibility of your {% data variables.projects.projects_v2 %}'
+shortTitle: 'Managing {% data variables.projects.project_v2 %} visibility'
+intro: 'Learn about setting your {% data variables.projects.project_v2 %} to private or public visibility.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+permissions: Organization owners can manage the visibility of project boards in their organization. Organization owners can also allow collaborators with admin permissions to manage project visibility. Visibility of user projects can be managed by the owner of the project and collaborators with admin permissions.
+---
+
+## Sobre a visibilidade do projeto
+
+Projects can be public or private. Para projetos públicos, todos na Internet podem ver o projeto. Para projetos privados, apenas usuários concedidos pelo menos acessos de leitura podem ver o projeto.
+
+Apenas a visibilidade do projeto é afetada. Para ver um item no projeto, alguém deve ter as permissões necessárias para o repositório ao qual o item pertence. Se o seu projeto incluir itens de um repositório privado, pessoas que não forem colaboradores no repositório não poderão visualizar os itens desse repositório.
+
+![Projeto com item oculto](/assets/images/help/projects/hidden-items.png)
+
+Project admins and organization owners can control project visibility. Organization owners can restrict the ability to change project visibility to just organization owners.
+
+In public and private projects, insights are only visible to users with write permissions for the project.
+
+Em projetos privados, os avatares de usuários que estão fazendo atualizações para o projeto são exibidos na interface de usuário do projeto.
+
+Os administradores do projeto também podem gerenciar o acesso de gravação e administração ao seu projeto e controlar o acesso de leitura para usuários individuais. For more information, see "[Managing access to your projects](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)."
+
+## Alterando a visibilidade do projeto
+
+{% data reusables.projects.project-settings %}
+1. Next to **Visibility** in the "Danger zone", select **Private** or **Public**. ![Screenshot showing the visibility controls](/assets/images/help/projects-v2/visibility.png)
+
+## Leia mais
+
+- [Allowing project visibility changes in your organization](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md
new file mode 100644
index 0000000000..4fa58e845e
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md
@@ -0,0 +1,21 @@
+---
+title: About date fields
+shortTitle: About date fields
+intro: You can create custom date fields that can be set by typing a date or using a calendar.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+---
+
+You can filter for date values using the `YYYY-MM-DD` format, for example: `date:2022-07-01`. You can also use operators, such as `>`, `>=`, `<`, `<=`, and `..`. For example, `date:>2022-07-01` and `date:2022-07-01..2022-07-31`. You can also provide `@today` to represent the current day in your filter. Para obter mais informações, consulte "[Filtrando projetos](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)".
+
+## Adding a date field
+
+{% data reusables.projects.new-field %}
+1. Select **Date** ![Screenshot showing the date option](/assets/images/help/projects-v2/new-field-date.png)
+1. Clique em **Salvar**. ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md
new file mode 100644
index 0000000000..804f3c40c8
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md
@@ -0,0 +1,60 @@
+---
+title: About iteration fields
+shortTitle: About iteration fields
+intro: Você pode criar iterações para planejar os itens de trabalho e grupos futuros.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-iterations
+type: tutorial
+topics:
+  - Projects
+---
+
+Você pode criar um campo de iteração para associar itens com blocos de tempo repetidos específicos. As iterações podem ser definidas para qualquer período de tempo, podem incluir intervalos e podem ser editadas individualmente para modificar o nome e o intervalo de datas. Com os projetos, você pode agrupar por iteração para visualizar o equilíbrio do trabalho futuro, usar filtros para focar em uma única iteração, bem como ordenar por iteração.
+
+You can filter for iterations by specifying the iteration name or `@current` for the current iteration, `@previous` for the previous iteration, or `@next` for the next iteration. You can also use operators such as `>`, `>=`, `<`, `<=`, and `..`.  For example, `iteration:>"Iteration 4"` and `iteration:<@current`. Para obter mais informações, consulte "[Filtrando projetos](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)".
+
+Ao criar um campo de iteração, três iterações serão criadas automaticamente.  Você pode adicionar iterações adicionais e fazer outras alterações na página de configurações do seu projeto.
+
+![Captura de tela que mostra as configurações para um campo de iteração](/assets/images/help/issues/iterations-example.png)
+
+## Adding an iteration field
+
+{% data reusables.projects.new-field %}
+1. Select **Iteration** ![Screenshot showing the iteration option](/assets/images/help/projects-v2/new-field-iteration.png)
+2. Optionally, if you don't want the iteration to start today, select the calendar dropdown next to "Starts on" and choose a new start date. ![Screenshot showing the iteration start date](/assets/images/help/projects-v2/iteration-field-starts.png)
+3. Para mudar a duração de cada iteração, digite um novo número, em seguida, selecione o menu suspenso e clique em **dias** ou **semanas**. ![Screenshot showing the iteration duration](/assets/images/help/projects-v2/iteration-field-duration.png)
+4. Clique em **Salvar**. ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save-and-create.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
+
+## Adicionando novas iterações
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the iteration field you want to adjust. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png)
+1. Para adicionar uma nova iteração da mesma duração, clique em **Adicionar iteração**. ![Screenshot the "add iteration" button](/assets/images/help/projects-v2/add-iteration.png)
+1. Optionally, to customize the duration of the new iteration and when it will start, click {% octicon "triangle-down" aria-label="The triangle icon" %} **More options**, select a starting date and duration, and click **Add**. ![Screenshot the add iteration options form](/assets/images/help/projects-v2/add-iteration-options.png)
+1. Clique em **Save changes** (Salvar alterações). ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png)
+
+## Editando uma iteração
+
+Você pode editar as iterações nas configurações do seu projeto. Você também pode acessar as configurações para um campo de iteração clicando em {% octicon "triangle-down" aria-label="The triangle icon" %} no cabeçalho da tabela para o campo e clicando em **Editar valores**.
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the iteration field you want to adjust. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png)
+1. To change the name of an iteration, click on the name and start typing. ![Screenshot an title field to rename an iteration](/assets/images/help/projects-v2/iteration-rename.png)
+1. Para alterar a data ou a duração de uma iteração, clique na data para abrir o calendário. Clique no dia de início, depois clique no dia de fim e depois clique em **Aplicar**. ![Screenshot showing iteration dates](/assets/images/help/projects-v2/iteration-date.png)
+1. Optionally, to delete an iteration, click {% octicon "trash" aria-label="The trash icon" %}. ![Screenshot the delete button](/assets/images/help/projects-v2/iteration-delete.png)
+2. Clique em **Save changes** (Salvar alterações). ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png)
+
+## Inserindo uma pausa
+
+Você pode inserir pausas em suas iterações para se comunicar quando você está tirando o tempo do trabalho agendado. O padrão da duração de uma nova pausa é o comprimento da iteração criada mais recentemente.
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the iteration field you want to adjust. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png)
+2. Na linha de divisão acima de uma iteração e à direita, clique em **Inserir pausa**. ![Captura de tela que mostra a localização do botão "Inserir pausa"](/assets/images/help/issues/iteration-insert-break.png)
+3. Opcionalmente, para alterar a duração da pausa, clique na data para abrir o calendário. Clique no dia de início, depois clique no dia de fim e depois clique em **Aplicar**.
+4. Clique em **Save changes** (Salvar alterações). ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png)
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md
new file mode 100644
index 0000000000..27fef4bf52
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md
@@ -0,0 +1,33 @@
+---
+title: About single select fields
+shortTitle: About single select fields
+intro: You can create single select fields with defined options that can be selected from a dropdown menu.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+---
+
+You can filter by your single select fields by specifying the option, for example: `fieldname:option`. You can filter for multiple values by providing a comma-separated list of options, for example: `fieldname:option,option`. Para obter mais informações, consulte "[Filtrando projetos](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)".
+
+Single select fields can contain up to 50 options.
+
+## Adding a single select field
+
+{% data reusables.projects.new-field %}
+1. Select **Single select** ![Screenshot showing the single select option](/assets/images/help/projects-v2/new-field-single-select.png)
+1. Below "Options", type the first option. ![Screenshot showing the single select option](/assets/images/help/projects-v2/single-select-create-with-options.png)
+   - To add additional options, click **Add option**.
+1. Clique em **Salvar**. ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
+
+## Editing a single select field
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the single select field you want to adjust. ![Screenshot showing an single select field](/assets/images/help/projects-v2/select-single-select.png)
+1. Edit existing options or click **Add option**. ![Screenshot showing single select options](/assets/images/help/projects-v2/single-select-edit-options.png)
+1. Optionally, to delete an option, click {% octicon "x" aria-label="The x icon" %}. ![Screenshot showing delete button](/assets/images/help/projects-v2/single-select-delete.png)
+1. Click **Save options**. ![Screenshot showing save button](/assets/images/help/projects-v2/save-options.png)
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md
new file mode 100644
index 0000000000..9c2f8f75ba
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md
@@ -0,0 +1,33 @@
+---
+title: About text and number fields
+shortTitle: About text and number fields
+intro: You can add custom text and number fields to your project.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+---
+
+You can use text fields to include notes or any other freeform text in your project.
+
+Text fields can be used in filters, for example: `field:"exact text"`. Text fields and item titles will also be used if you filter for text without specifying a field.
+
+Number fields can also be used in filters. You can use `>`, `>=`, `<`, `<=`, and `..` range queries to filter by a number field. For example: `field:5..15` or `field:>=20`. Para obter mais informações, consulte "[Filtrando projetos](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)".
+
+## Adding a text field
+
+{% data reusables.projects.new-field %}
+1. Select **Text** ![Screenshot showing the text option](/assets/images/help/projects-v2/new-field-text.png)
+1. Clique em **Salvar**. ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
+
+## Adding a number field
+
+{% data reusables.projects.new-field %}
+1. Select **Number** ![Screenshot showing the number option](/assets/images/help/projects-v2/new-field-number.png)
+1. Clique em **Salvar**. ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md
new file mode 100644
index 0000000000..94b0ea1cec
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md
@@ -0,0 +1,15 @@
+---
+title: Deleting fields
+intro: 'Learn how to delete a field from your {% data variables.projects.project_v2 %}.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+---
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the field you want to delete. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-single-select.png)
+1. Next to the field's name, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing field name](/assets/images/help/projects-v2/field-options.png)
+1. Click **Delete field**. ![Screenshot showing field name](/assets/images/help/projects-v2/delete-field.png)
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md
new file mode 100644
index 0000000000..09b569a5d0
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md
@@ -0,0 +1,19 @@
+---
+title: Understanding field types
+shortTitle: Understanding field types
+intro: 'Learn about the different custom field types, how to add custom fields to your project, and how to manage custom fields.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /about-text-and-number-fields
+  - /about-date-fields
+  - /about-single-select-fields
+  - /about-iteration-fields
+  - /renaming-fields
+  - /deleting-fields
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md
new file mode 100644
index 0000000000..0455d3640d
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md
@@ -0,0 +1,15 @@
+---
+title: Renaming fields
+intro: 'Learn about renaming existing fields in your {% data variables.projects.project_v2 %}.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+---
+
+{% data reusables.projects.project-settings %}
+1. Click the name of the field you want to rename. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-single-select.png)
+1. Under "Field name", type the new name for the field. ![Screenshot showing field name](/assets/images/help/projects-v2/field-rename.png)
+1. To save changes, press <kbd>Return</kbd>.
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
new file mode 100644
index 0000000000..f80a529e2a
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
@@ -0,0 +1,51 @@
+---
+title: 'About insights for {% data variables.product.prodname_projects_v2 %}'
+intro: Você pode visualizar e personalizar gráficos construídos a partir dos dados do seu projeto.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/using-insights-with-projects
+type: tutorial
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+---
+
+{% ifversion fpt %}
+
+{% note %}
+
+**Note:** Historical charts are currently available as a feature preview for organizations using {% data variables.product.prodname_team %} and are generally available for organizations using {% data variables.product.prodname_ghe_cloud %}.
+
+{% endnote %}
+
+{% endif %}
+
+ You can use insights for {% data variables.product.prodname_projects_v2 %} to view, create, and customize charts that use the items added to your project as their source data. Você pode aplicar filtros ao gráfico padrão e também criar seus próprios gráficos. When you create a chart, you set the filters, chart type, the information displayed, and the chart is available to anyone that can view the project. You can generate two types of chart: current charts and historical charts.
+
+ ### About current charts
+
+You can create current charts to visualize your project items. For example, you can create charts to show how many items are assigned to each individual, or how many issues are assigned to each upcoming iteration.
+
+You can also use filters to manipulate the data used to build your chart. For example, you can create a chart showing how much upcoming work you have, but limit those results to particular labels or assignees. Para obter mais informações, consulte "[Filtrando projetos](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)".
+
+ ![Captura de tela que mostra um gráfico de colunas empilhadas com tipos de itens para cada iteração](/assets/images/help/issues/column-chart-example.png)
+
+For more information, see "[Creating charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)."
+
+ ### About historical charts
+
+ Historical charts are time-based charts that allow you to view your project's trends and progress. You can view the number of items, grouped by status and other fields, over time.
+
+ O gráfico padrão "Burn up" mostra o status do item ao longo do tempo, permitindo que você visualize o progresso e os padrões de ponto ao longo do tempo.
+
+![Captura de tela que mostra um exemplo do gráfico padrão de burn up para a iteração atual](/assets/images/help/issues/burnup-example.png)
+
+ To create a historical chart, set your chart's X-axis to "Time." For more information, see "[Creating charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)" and "[Configuring charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts)."
+
+## Leia mais
+
+- "[Sobre o {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)"
+- "[Disabling insights for {% data variables.product.prodname_projects_v2 %} in your organization](/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization)"
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
new file mode 100644
index 0000000000..584620aaf1
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
@@ -0,0 +1,30 @@
+---
+title: Configuring charts
+intro: Learn how to configure your charts and filter data from your project.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+---
+
+{% ifversion fpt %}
+
+{% note %}
+
+**Note:** Historical charts are currently available as a feature preview.
+
+{% endnote %}
+
+{% endif %}
+
+{% data reusables.projects.access-insights %}
+1. In the menu on the left, click on the chart you would like to configure. ![Screenshot showing selecting a custom chart](/assets/images/help/projects-v2/insights-select-a-chart.png)
+1. No lado direito da página, clique em **Configurar**. Será aberto um painel à direita. ![Screenshot showing the configure button](/assets/images/help/projects-v2/insights-configure.png)
+1. Para alterar o tipo de gráfico, selecione a lista suspensa do **Layout** e clique no tipo de gráfico que você deseja usar. ![Screenshot showing selecting a chart layout](/assets/images/help/projects-v2/insights-layout.png)
+1. Para alterar o campo usado no eixo X do gráfico, selecione o menu suspenso **Eixo X** e clique no campo que você deseja usar. ![Screenshot showing selecting what to display on the x axis](/assets/images/help/projects-v2/insights-x-axis.png)
+1. Opcionalmente, para agrupar os itens no seu eixo X por outro campo, selecione **Agrupar por** e clique no campo que você deseja usar ou clique em "Nenhum" para desabilitar o agrupamento. ![Screenshot showing selecting a grouping method](/assets/images/help/projects-v2/insights-group.png)
+1. Opcionalmente, se o seu projeto contiver campos numéricos e você quiser que o eixo Y exiba a soma, média, mínimo ou máximo de um desses campos numéricos, selecione **eixo Y** e clique em uma opção. Em seguida, selecione o menu suspenso que aparece abaixo e clique no campo número que você deseja usar. ![Screenshot showing selecting what to display on the y axis](/assets/images/help/projects-v2/insights-y-axis.png)
+1. Para salvar seu gráfico, clique em **Salvar alterações**. ![Screenshot showing the save button](/assets/images/help/projects-v2/insights-save.png)
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
new file mode 100644
index 0000000000..00b3d81b8f
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
@@ -0,0 +1,17 @@
+---
+title: Creating charts
+intro: Learn how to create new charts to save your configurations.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+---
+
+{% data reusables.projects.access-insights %}
+3. No menu à esquerda, clique em **Novo gráfico**. ![Screenshot showing the new chart button](/assets/images/help/projects-v2/insights-new-chart.png)
+4. Opcionalmente, para alterar o nome do novo gráfico, clique em {% octicon "triangle-down" aria-label="The triangle icon" %}, digite um novo nome e pressione <kbd>Retornar</kbd>. ![Screenshot showing how to rename a chart](/assets/images/help/projects-v2/insights-rename.png)
+5. Acima do gráfico, digite os filtros para alterar os dados utilizados para a construção do gráfico. Para obter mais informações, consulte "[Filtrando projetos](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)".
+6. À direita da caixa de texto do filtro, clique em **Salvar alterações**. ![Screenshot showing save button](/assets/images/help/projects-v2/insights-save-filter.png)
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md
new file mode 100644
index 0000000000..84047d3771
--- /dev/null
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md
@@ -0,0 +1,17 @@
+---
+title: 'Viewing insights from your {% data variables.projects.project_v2 %}'
+shortTitle: Viewing insights
+intro: ...
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+children:
+  - /about-insights-for-projects
+  - /creating-charts
+  - /configuring-charts
+allowTitleToDifferFromFilename: true
+---
+
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md
index fdfca1edb0..9446f7eaac 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -32,7 +32,7 @@ Os problemas podem ser criados de várias maneiras. Portanto, você pode escolhe
 
 Você pode organizar e priorizar problemas com projetos. {% ifversion fpt or ghec %}Para monitorar problemas como parte de um problema maior, você pode usar as listas de tarefas.{% endif %} Para categorizar problemas relacionados, você pode usar etiquetas e marcos.
 
-Para obter mais informações sobre os projetos, consulte {% ifversion fpt or ghec %}"[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)e {% endif %}"[Organizar seu trabalho com quadros de projeto](/issues/organizing-your-work-with-project-boards)". {% ifversion fpt or ghec %}Para obter mais informações sobre listas de tarefas, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)". {% endif %}Para obter mais informações sobre etiquetas e marcos, consulte "[Usando etiquetas e marcos para rastrear o trabalho](/issues/using-labels-and-milestones-to-track-work)".
+For more information about projects, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." {% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} {% ifversion fpt or ghec %}For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %}Para obter mais informações sobre etiquetas e marcos, consulte "[Usando etiquetas e marcos para rastrear o trabalho](/issues/using-labels-and-milestones-to-track-work)".
 
 ## Mantenha-se atualizado
 
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
index 84a700c17c..248853e53d 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
@@ -90,24 +90,32 @@ Depois de criar uma etiqueta em um repositório, é possível aplicá-lo em qual
 Abaixo está um exemplo de uma etiqueta `front-end` que criamos e adicionamos ao problema.
 
 ![Adicionando uma etiqueta a um exemplo do problema](/assets/images/help/issues/quickstart-add-label-to-issue.png)
+
 ## Adicionando problemas a um quadro de projeto
-{% ifversion fpt or ghec %}Você pode usar projetos em {% data variables.product.prodname_dotcom %}, atualmente em beta público limitado, para planejar e acompanhar o trabalho da sua equipe. Um projeto é uma planilha personalizável integradas aos seus problemas e pull requests em {% data variables.product.prodname_dotcom %}, mantendo-se atualizada automaticamente com as informações em {% data variables.product.prodname_dotcom %}. Você pode personalizar o layout filtrando, organizando e agrupando seus problemas e PRs. Para começar com projetos, consulte "[Inicialização rápida para projetos (beta)](/issues/trying-out-the-new-projects-experience/quickstart). ".
-### Exemplo de projeto (beta)
+
+{% ifversion projects-v2 %}
+
+You can use {% data variables.projects.projects_v2 %} on {% data variables.product.prodname_dotcom %} to plan and track the work for your team. Um projeto é uma planilha personalizável integradas aos seus problemas e pull requests em {% data variables.product.prodname_dotcom %}, mantendo-se atualizada automaticamente com as informações em {% data variables.product.prodname_dotcom %}. Você pode personalizar o layout filtrando, organizando e agrupando seus problemas e PRs. To get started with projects, see "[Quickstart for projects](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects)."
+### Project example
 Aqui está o layout da tabela de um projeto de exemplo, preenchido com os problemas do projeto Octocat que criamos.
 
-![Exemplo do layout da tabela de projetos (beta)](/assets/images/help/issues/quickstart-projects-table-view.png)
+![Projects table layout example](/assets/images/help/issues/quickstart-projects-table-view.png)
 
 Podemos também visualizar o mesmo projeto como um quadro.
 
-![Exemplo do quadro do layout de projetos (beta)](/assets/images/help/issues/quickstart-projects-board-view.png)
+![Projects board layout example](/assets/images/help/issues/quickstart-projects-board-view.png)
 
 {% endif %}
+{% ifversion projects-v1 %}
 
-Você também pode {% ifversion fpt or ghec %} usar os quadros de projeto existentes{% else %} usar{% endif %} no {% data variables.product.prodname_dotcom %} para planejar e acompanhar o trabalho da sua equipe. Os quadros de projeto são compostos por problemas, pull requests e observações que são categorizados como cartões em colunas de sua escolha. Você pode criar quadros de projetos para trabalho de funcionalidades, itinerários de alto nível ou até mesmo aprovar checklists. Para obter mais informações, consulte "[Sobre quadros de projeto](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)".
+You can {% ifversion projects-v2 %} also use the existing{% else %} use{% endif %} {% data variables.product.prodname_projects_v1 %} on {% data variables.product.prodname_dotcom %} to plan and track your or your team's work. Os quadros de projeto são compostos por problemas, pull requests e observações que são categorizados como cartões em colunas de sua escolha. Você pode criar quadros de projetos para trabalho de funcionalidades, itinerários de alto nível ou até mesmo aprovar checklists. Para obter mais informações, consulte "[Sobre quadros de projeto](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)".
 ### Exemplo de quadro de projeto
 Abaixo, está um painel de projeto para o nosso exemplo de projeto Octocat com o problema que criamos, e os problemas menores nos quais separamos, foram adicionados.
 
 ![Exemplo de quadro de projeto](/assets/images/help/issues/quickstart-project-board.png)
+
+{% endif %}
+
 ## Próximas etapas
 
 Agora você aprendeu sobre as ferramentas que {% data variables.product.prodname_dotcom %} oferece para planejamento e acompanhamento do seu trabalho e deu o seu primeiro passo para definir a sua equipe multifuncional ou repositório de projetos! Aqui estão alguns recursos úteis para personalizar ainda mais seu repositório e organizar seu trabalho.
@@ -117,6 +125,6 @@ Agora você aprendeu sobre as ferramentas que {% data variables.product.prodname
 - "[Sobre problemas e modelos de pull request](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)para aprender mais sobre modelos de problemas
 - "[Gerenciando etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)" para aprender a criar, editar e excluir etiquetas
 - "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)" para aprender mais sobre listas de tarefas
-{% ifversion fpt or ghec %} - "[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" para aprender mais sobre a experiência dos novos projetos, atualmente em beta público limitado
-- "[Personalizando as visualizações do seu projeto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)" para aprender como personalizar visualizações para projetos, atualmente em beta público limitado{% endif %}
-- "[Sobre os quadros de projetos](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" para aprender como gerenciar os quadros de projetos
+{% ifversion projects-v2 %} - "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" for learning more about projects
+- "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)" for learning how to customize views for projects{% endif %}
+{% ifversion projects-v1 %}- "[About {% data variables.product.prodname_projects_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" for learning how to manage project boards{% endif %}
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/quickstart.md
index 35077005ed..1c0b81e2ac 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/quickstart.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/quickstart.md
@@ -71,7 +71,7 @@ Para comunicar-se responsabilidade, você pode atribuir o problema a um integran
 
 ## Adicionando a problema a um projeto
 
-Você pode adicionar um problema a um projeto existente. {% ifversion fpt or ghec %}Se você usar projetos (beta), você também poderá preencher os metadados do projeto. {% endif %} Para mais informações sobre projetos, consulte {% ifversion fpt or ghec %}"[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)e {% endif %}"[Organizar o seu trabalho com quadros de projeto](/issues/organizing-your-work-with-project-boards)".
+You can add the issue to an existing project{% ifversion projects-v2 %} and populate metadata for the project. {% endif %} For more information about projects, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."{% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %}
 
 ![problema com projetos](/assets/images/help/issues/issue-project.png)
 
@@ -97,5 +97,5 @@ Você pode usar problemas para uma grande variedade de finalidades. Por exemplo:
 Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_github_issues %}:
 
 - Para saber mais sobre problemas, consulte "[Sobre problemas](/issues/tracking-your-work-with-issues/about-issues)".
-- Para saber mais sobre como os projetos podem ajudar você no planejamento e acompanhamento, consulte {% ifversion fpt or ghec %}"[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)ou {% endif %}"[Organizar seu trabalho com quadros de projeto](/issues/organizing-your-work-with-project-boards)".
+- To learn more about how projects can help you with planning and tracking, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."{% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %}
 - Para aprender mais sobre o uso dos modelos de problemas{% ifversion fpt or ghec %} e formulários de problemas{% endif %} para incentivar os contribuidores a fornecer informações específicas, consulte "[Usar modelos para incentivar problemas úteis e pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)".
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/about-projects.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/about-projects.md
deleted file mode 100644
index d27ff65385..0000000000
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/about-projects.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Sobre projetos (beta)
-intro: 'Os projetos são uma ferramenta personalizável e flexível para planejamento e acompanhamento de trabalhos em {% data variables.product.company_short %}.'
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-type: overview
-topics:
-  - Projects
----
-
-{% data reusables.projects.projects-beta %}
-
-## Sobre projetos
-
-Um projeto é uma planilha personalizável que se integra aos seus problemas e pull requests em {% data variables.product.company_short %}. Você pode personalizar o layout filtrando, organizando e agrupando seus problemas e PRs. Você também pode adicionar campos personalizados para rastrear metadados. Os projetos são flexíveis para que sua equipe possa trabalhar da maneira que for melhor para eles.
-
-### Mantendo-se atualizado
-
-O seu projeto permanece automaticamente atualizado com as informações em {% data variables.product.company_short %}. Quando um pull request ou um problema é alterado, o seu projeto reflete essa alteração. Esta integração também funciona nos dois sentidos, para que, quando você altera as informações sobre um problema ou pull request do seu projeto, o problema ou o pull request irá refletir essa informação.
-
-### Adicionando metadados às suas tarefas
-
-Você pode usar campos personalizados para adicionar metadados às suas tarefas. Por exemplo, você pode monitorar os seguintes metadados:
-
-- um campo de data para acompanhar as datas de envio
-- um campo numérico para monitorar a complexidade de uma tarefa
-- um único campo de seleção para rastrear se uma tarefa tem prioridade baixa, média ou alta
-- um campo de texto para adicionar uma observação rápida
-- um campo de iteração para planejar o trabalho semanalmente, incluindo suporte para pausas
-
-### Visualizando seu projeto de diferentes perspectivas
-
-Você pode ver seu projeto como um layout de tabela de alta densidade:
-
-![Tabela de projeto](/assets/images/help/issues/projects_table.png)
-
-Ou como um quadro:
-
-![Quadro de projeto](/assets/images/help/issues/projects_board.png)
-
-Para ajudar você a concentrar-se em aspectos específicos do seu projeto, você pode agrupar, ordenar ou filtrar itens:
-
-![Visualização do projeto](/assets/images/help/issues/project_view.png)
-
-Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
-
-### Trabalhando com a paleta de comandos do projeto
-
-Você pode usar a paleta de comandos do projeto para alterar rapidamente as visualizações ou adicionar campos. A paleta de comandos guia você para que você não precise memorizar atalhos de teclado personalizados. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
-
-### Automatizando tarefas de gerenciamento de projetos
-
-Os projetos (beta) oferecem fluxos de trabalho integrados. Por exemplo, quando um problema é fechado, você pode definir automaticamente o status como "Concluído". Você também pode usar a API do GraphQL e {% data variables.product.prodname_actions %} para automatizar tarefas cotidianas de gerenciamento de projeto. Para obter mais informações, consulte "[Automatizando projetos](/issues/trying-out-the-new-projects-experience/automating-projects)" e "[Usando a API para gerenciar os projetos](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)".
-
-## Comparação de projetos (beta) com os projetos que não são beta
-
-Projetos (beta) é uma nova versão personalizável dos projetos. Para obter mais informações sobre a versão que não é beta dos projetos, consulte "[Organizar seu trabalho com quadros de projeto](/issues/organizing-your-work-with-project-boards)".
-
-## Compartilhando feedback
-
-Você pode compartilhar seu feedback sobre projetos (beta) com {% data variables.product.company_short %}. Para juntar-se à conversa, consulte [a discussão de feedbacks](https://github.com/github/feedback/discussions/categories/issues-feedback).
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
deleted file mode 100644
index 955bcd53d7..0000000000
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
+++ /dev/null
@@ -1,198 +0,0 @@
----
-title: Criando um projeto (beta)
-intro: 'Aprenda a criar um projeto, preencher e adicionar campos personalizados.'
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-type: tutorial
-topics:
-  - Projects
----
-
-Os projetos são uma coleção personalizável de itens que se mantêm atualizados com os dados do {% data variables.product.company_short %}. Seus projetos podem rastrear problemas, pull requests, e ideias que você anotar. Você pode adicionar campos personalizados e criar visualizações para fins específicos.
-
-{% data reusables.projects.projects-beta %}
-
-## Criando um projeto
-
-### Criando um projeto de organização
-
-{% data reusables.projects.create-project %}
-
-### Criando um projeto de usuário
-
-{% data reusables.projects.create-user-project %}
-
-## Atualizando a descrição e o README do seu projeto
-
-{% data reusables.projects.project-description %}
-
-## Adicionando itens ao seu projeto
-
-Seu projeto pode acompanhar os rascunhos de problemas, problemas e pull requests.
-
-### Criando problemas de rascunho
-
-Os rascunhos são úteis para capturar ideias rapidamente.
-
-1. Coloque seu cursor na linha inferior do projeto, ao lado do {% octicon "plus" aria-label="plus icon" %}.
-1. Digite sua ideia e, em seguida, pressione **Enter**.
-1. Para adicionar texto, clique no título do problema do rascunho. Na caixa de entrada do markdown que será exibida, digite o texto para o texto do problema do rascunho e clique em **Salvar**.
-
-Os problemas do rascunho podem ter um título, texto, responsável e quaisquer campos personalizados do seu projeto. Para preencher o repositório, etiquetas ou marcos para o rascunho de um problema, você deverá primeiro converter o rascunho do problema em um problema. Para obter mais informações, consulte "[Convertendo rascunhos de problema em problemas](#converting-draft-issues-to-issues). "
-
-{% note %}
-
-**Observação**: Os usuários não receberão notificações quando forem atribuídos ou mencionados em um rascunho de problema, a menos que o rascunho do probelam seja convertido em um problema.
-
-{% endnote %}
-
-### Problemas e pull requests
-
-#### Cole a URL de um problema ou pull request
-
-1. Coloque seu cursor na linha inferior do projeto, ao lado do {% octicon "plus" aria-label="plus icon" %}.
-1. Cole a URL do problema ou pull request.
-
-#### Pesquisando um problema ou pull request
-
-1. Coloque seu cursor na linha inferior do projeto, ao lado do {% octicon "plus" aria-label="plus icon" %}.
-2. Digite <kbd>#</kbd>.
-3. Selecione o repositório onde está localizado o pull request ou problema. Você pode digitar parte do nome do repositório para restringir suas opções.
-4. Selecione o problema ou pull request. Você pode digitar parte do título para restringir suas opções.
-
-#### Adicionando vários problemas ou pull requests de um repositório
-
-1. No {% data variables.product.product_location %}, acesse o repositório que contém os problemas ou pull requests que você deseja adicionar ao projeto.
-{% data reusables.repositories.sidebar-issue-pr %}
-1. À esquerda de cada título do problema, selecione os problemas que você deseja adicionar ao seu projeto. ![Captura de tela que mostra caixa de seleção para selecionar problema ou pull request](/assets/images/help/issues/select-issue-checkbox.png)
-1. Opcionalmente, para selecionar cada problema ou pull request na página, na parte superior da lista de problemas ou pull requests, selecione tudo. ![Captura de tela que mostra caixa de seleção para selecionar todos na tela](/assets/images/help/issues/select-all-checkbox.png)
-1. Acima da lista de problemas ou pull requests, clique em **Projetos (beta)**. ![Captura de tela que mostra caixa de seleção para selecionar todos na tela](/assets/images/help/issues/projects-beta-assign-button.png)
-1. Clique nos projetos aos quais você deseja adicionar os problemas selecionados ou pull requests. ![Captura de tela que mostra caixa de seleção para selecionar todos na tela](/assets/images/help/issues/projects-beta-assign-dropdown.png)
-
-#### Atribuindo um projeto de dentro de um problema ou pull request
-
-1. Acesse o problema ou pull request que você deseja adicionar a um projeto.
-2. Na barra lateral, clique em **Projetos**.
-3. Selecione o projeto ao qual você deseja adicionar o problema ou pull request.
-4. Opcionalmente, preencha os campos personalizados.
-
-   ![Barra lateral do projeto](/assets/images/help/issues/project_side_bar.png)
-
-## Convertendo rascunhos de problemas em problemas
-
-No layout de tabela:
-
-1. Clique em {% octicon "triangle-down" aria-label="the item menu" %} no rascunho do problema que você deseja converter.
-2. Selecione **Converter para problema**.
-3. Selecione o repositório ao qual você deseja adicionar o problema.
-4. Como alternativa, edite os campos `etiquetas`, `marco` ou `repository` do rascunho do problema que você deseja converter.
-
-Layout do quadro:
-
-1. Clique em {% octicon "kebab-horizontal" aria-label="the item menu" %} no rascunho do problema que você deseja converter.
-2. Selecione **Converter para problema**.
-3. Selecione o repositório ao qual você deseja adicionar o problema.
-
-## Removendo itens do seu projeto
-
-Você pode arquivar um item para manter o contexto sobre o item no projeto, mas removê-lo das visualizações do projeto. Você pode excluir um item para removê-lo do projeto completamente.
-
-1. Selecione o(s) item(ns) para arquivar ou excluir. Para selecionar múltiplos itens, siga um dos passos a seguir:
-     - <kbd>Command</kbd>+Click (Mac) ou <kbd>Ctrl</kbd>+Click (Windows/Linux) em cada item.
-     - Selecione um item e, em seguida, <kbd>Shift</kbd>+<kbd>↑</kbd> ou <kbd>Shift</kbd>+<kbd>↓</kbd>para selecionar itens adicionais acima ou abaixo do item selecionado inicialmente.
-     - Selecione um item e, em seguida, <kbd>Shift</kbd>+ clique em outro item para selecionar todos os itens entre dois itens.
-     - Insira <kbd>Command</kbd>+<kbd>A</kbd> (Mac) ou <kbd>Ctrl</kbd>+<kbd>A</kbd> (Windows/Linux) para selecionar todos os itens em uma coluna em um layout de tabuleiro ou em um layout de tabela.
-2. Para arquivar todos os itens selecionados, digite <kbd>E</kbd>. Para excluir todos os itens selecionados, digite <kbd>Del</kbd>. Como alternativa, selecione o {% octicon "triangle-down" aria-label="the item menu" %} (no layout de tabela) ou o {% octicon "kebab-horizontal" aria-label="the item menu" %} (no layout do quadro) e, em seguida, selecione a ação desejada.
-
-Você pode restaurar itens arquivados, mas não itens excluídos. Para obter mais informações, consulte [Restaurando itens arquivados](#restoring-archived-items).
-
-## Restaurando itens arquivados
-
-1. Navigate to your project.
-1. No canto superior direito, clique em {% octicon "kebab-horizontal" aria-label="the kebab icon" %}.
-1. No menu, clique em **Itens arquivados**.
-1. Opcionalmente, para filtrar os itens arquivados exibidos, digite seu filtro na caixa de texto acima da lista de itens. Para obter mais informações sobre os filtros disponíveis, consulte "[Filtrando projetos (beta)](/issues/trying-out-the-new-projects-experience/filtering-projects)".
-
-   ![Captura de tela que mostra o campo para filtrar itens arquivados](/assets/images/help/issues/filter-archived-items.png)
-
-1. À esquerda de cada item de título, selecione os itens que deseja restaurar.
-
-   ![Captura de tela que mostra as caixas de seleção próximas aos itens arquivados](/assets/images/help/issues/select-archived-item.png)
-
-1. Para restaurar os itens selecionados, acima da lista de itens, clique em **Restaurar**.
-
-   ![Captura de tela que mostra o botão "Restaurar"](/assets/images/help/issues/restore-archived-item-button.png)
-
-## Adicionando campos
-
-Como os valores do campo mudam, eles são sincronizados automaticamente para que o seu projeto e os itens que ele rastreia fiquem atualizados.
-
-### Mostrando campos existentes
-
-O seu projeto rastreia informações atualizadas sobre problemas e pull requests, incluindo todas as alterações no título, responsáveis, etiquetas, marcos, repositórios, revisores e pull requests vinculados. Quando seu projeto é inicializado, são exibidos "título" e "responsáveis". Os outros campos permanecem ocultos. Você pode alterar a visibilidade desses campos no seu projeto.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar "mostrar".
-3. Selecione o comando desejado (por exemplo: "Mostrar: Repositório").
-
-Como alternativa, você pode fazer isso na interface do usuário:
-
-1. Clique em {% octicon "plus" aria-label="the plus icon" %} no cabeçalho mais à direita. Será exibido um menu suspenso com os campos do projeto. ![Exibir ou ocultar campos](/assets/images/help/issues/projects_fields_menu.png)
-2. Selecione o(s) campo(s) que você deseja exibir ou ocultar. Um {% octicon "check" aria-label="check icon" %} indica quais campos serão exibidos.
-
-### Adicionando campos personalizados
-
-Você pode adicionar campos personalizados ao seu projeto. Campos personalizados serão exibidos na barra lateral de problemas e pull requests no projeto.
-
-Os campos personalizados podem ser texto, número, data, seleção única ou iteração:
-
-- Texto: O valor pode ser qualquer texto.
-- Número: O valor deve ser um número.
-- Data: O valor deve ser uma data.
-- Seleção única: O valor deve ser selecionado a partir de um conjunto de valores especificados.
-- Iteração: O valor deve ser selecionado a partir de um conjunto de intervalos de datas (iterações). As iterações anteriores são automaticamente marcadas como "concluídas", e a iteração que cobre o intervalo de datas atual é marcada como "atual". Para obter mais informações, consulte "[Gerenciando iterações nos projetos](/issues/trying-out-the-new-projects-experience/managing-iterations). "
-
-1. {% data reusables.projects.open-command-palette %} Comece a digitar qualquer parte de "Criar novo campo". Quando "Criar novo campo" for exibido na paleta de comandos, selecione-o.
-2. Como alternativa, clique em {% octicon "plus" aria-label="the plus icon" %} no cabeçalho do campo mais à direita. Será exibido um menu suspenso com os campos do projeto. Clique em **Novo campo**.
-3. Uma janela pop-up irá aparecer para inserir informações sobre o novo campo. ![Novo campo](/assets/images/help/issues/projects_new_field.png)
-4. Na caixa de texto, digite um nome para o novo campo.
-5. Selecione o menu suspenso e clique no tipo desejado.
-6. Se você especificou **Seleção única** como o tipo, insira as opções.
-7. Se você especificou **Iteração** como o tipo, digite a data de início da primeira iteração e a duração da iteração. Três iterações são criadas automaticamente, e você pode adicionar iterações adicionais na página de configurações do projeto.
-
-Você também pode editar seus campos personalizados.
-
-{% data reusables.projects.project-settings %}
-1. Em **Campos**, selecione o campo que deseja editar.
-1. Para campos de seleção única, você pode adicionar, excluir ou reordenar as opções.
-1. Para campos de iteração, você pode adicionar ou excluir as iterações, alterar nomes da iteração e alterar a data e a duração de início da iteração.
-
-   Para obter mais informações sobre como modificar campos de iteração, consulte "[Gerenciando iterações nos projetos](/issues/trying-out-the-new-projects-experience/managing-iterations).
-
-## Personalizando as suas visualizações
-
-Você pode ver seu projeto como uma tabela ou quadro, agrupar itens por campo, filtrar itens e muito mais. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
-
-## Configurando a automação integrada
-
-{% data reusables.projects.about-workflows %}
-
-Você pode habilitar ou desabilitar os fluxos de trabalho internos para o seu projeto.
-
-{% data reusables.projects.enable-basic-workflow %}
-
-## Adicionando seu projeto a um repositório
-
-Você pode listar projetos relevantes em um repositório. Você só pode listar projetos que pertencem ao mesmo usuário ou organização proprietária do repositório.
-
-Para que os participantes do repositório vejam um projeto listado em um repositório, eles deverão ter visibilidade sobre o projeto. Para obter mais informações, consulte "[Gerenciando a visibilidade dos seus projetos (beta)](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)" e "[Gerenciando o acesso a projetos (beta)](/issues/trying-out-the-new-projects-experience/managing-access-to-projects)".
-
-1. No {% data variables.product.prodname_dotcom %}, navegue até a página principal do seu repositório.
-1. Clique em {% octicon "table" aria-label="the project icon" %} **Projetos**.
-1. Clique em **Projetos (Beta)** na barra lateral.
-1. Clique **Adicionar projeto**.
-1. Na barra de pesquisa que aparece, pesquise por projetos pertentencentes ao mesmo usuário ou organização proprietária do repositório.
-1. Clique em um projeto para listá-lo no seu repositório.
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
deleted file mode 100644
index 7ad0629f9a..0000000000
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
+++ /dev/null
@@ -1,204 +0,0 @@
----
-title: Personalizando as visualizações do seu projeto (beta)
-intro: 'Exibe as informações de que você precisa alterando o layout, agrupamento, ordenação e filtros no seu projeto.'
-allowTitleToDifferFromFilename: true
-versions:
-  fpt: '*'
-  ghec: '*'
-type: reference
-topics:
-  - Projects
----
-
-{% data reusables.projects.projects-beta %}
-
-## Paleta de comandos do projeto
-
-Use a paleta de comandos do projeto para alterar rapidamente as configurações e executar comandos no seu projeto.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar qualquer parte de um comando ou navegue pela janela da paleta de comandos para encontrar um comando. Veja as próximas seções para mais exemplos de comandos.
-
-## Alterando o layout do projeto
-
-Você pode visualizar o seu projeto como uma tabela ou como um quadro.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar "Alternar layout".
-3. Escolha o comando necessário. Por exemplo, **Switch layout: Table**.
-
-Como alternativa, clique em {% octicon "triangle-down" aria-label="the drop-down icon" %} ao lado de um nome de exibição e clique em **Tabela** ou **Quadro**.
-
-## Exibindo e ocultando campos
-
-Você pode mostrar ou ocultar um campo específico.
-
-### Mostrando e ocultando campos no layout da tabela
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar a ação que deseja realizar ("mostrar" ou "ocultar") ou o nome do campo.
-3. Escolha o comando necessário. Por exemplo, **Exibir: Marco**.
-
-Como alternativa, clique em {% octicon "plus" aria-label="the plus icon" %} à direita da tabela. No menu suspenso que aparece, indique quais campos mostrar ou ocultar. Um {% octicon "check" aria-label="check icon" %} indica quais campos serão exibidos.
-
-Como alternativa, clique em {% octicon "triangle-down" aria-label="the drop-down icon" %} ao lado do nome do campo e clique em **Ocultar o campo**.
-
-### Mostrando e ocultando campos no layout do quadro
-
-1. Clique em {% octicon "triangle-down" aria-label="the drop-down icon" %} ao lado do nome da exibição.
-2. Em**Configuração**, clique em {% octicon "list-unordered" aria-label="the unordered list icon" %}.
-3. No menu exibido, selecione os campos para adicioná-los e desmarque os campos para removê-los do modo de exibição.
-
-## Reordenando campos
-
-Você pode alterar a ordem dos campos.
-
-1. Clique no cabeçalho do campo.
-2. Ao clicar, arraste o campo para a localização necessária.
-
-## Reordenando linhas
-
-No layout da tabela, você pode alterar a ordem das linhas.
-
-1. Clique no número no início da linha.
-2. Ao clicar, arraste a linha para a localização necessária.
-
-## Ordenação por valores do campo
-
-No layout de tabela, você pode classificar itens por um valor de campo.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar "Ordenar por" ou o nome do campo que deseja ordenar.
-3. Escolha o comando necessário. Por exemplo, **Sort by: Assignees, asc**.
-
-Alternativamente, clique em {% octicon "triangle-down" aria-label="the drop-down icon" %} ao lado do campo que você deseja ordenar e clique em **Ordenação ascendente** ou **Ordenação decrescente**.
-
-{% note %}
-
-**Observação:** Quando uma tabela é ordenada, você não pode reordenar manualmente as linhas.
-
-{% endnote %}
-
-Siga passos semelhantes para remover uma ordenação.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar "Remover ordenação".
-3. Selecione **Remover ordenação por**.
-
-Como alternativa, clique em {% octicon "triangle-down" aria-label="the drop-down icon" %} ao lado do nome de exibição e clique no item de menu que indica a classificação atual.
-
-## Agrupamento por valores de campo no layout de tabela
-
-No layout da tabela, você pode agrupar os itens por um valor de campo personalizado. Quando os itens são agrupados, se você arrastar um item para um novo grupo, será aplicado o valor desse grupo. Por exemplo, se você agrupar por "Status" e, em seguida, arrastar um item com um status de `Em andamento` para o grupo `Concluído` o status do item mudará para `Concluído`. Da mesma forma, ao adicionar um novo item a um grupo, o novo item será preenchido com o valor do grupo.
-
-{% note %}
-
-**Observação:** Atualmente, você não pode agrupar por títulos, etiquetas, revisores ou pull requests.
-
-{% endnote %}
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar "Agrupar por" ou o nome do campo que você deseja agrupar.
-3. Escolha o comando necessário. Por exemplo, **Agrupar por: Status**.
-
-Como alternativa, clique em {% octicon "triangle-down" aria-label="the drop-down icon" %} ao lado do nome do campo que você deseja agrupar e clique em **Agrupar por valores**.
-
-Siga as etapas semelhantes para remover um agrupamento.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar "Remover agrupamento".
-3. Selecione **Remover agrupar por**.
-
-Como alternativa, clique em {% octicon "triangle-down" aria-label="the drop-down icon" %} ao lado do nome de exibição e clique no item de menu que indica a agrupamento atual.
-
-## Definir o campo da coluna no layout do quadro
-
-No layout do painel, você escolhe qualquer campo de seleção ou iteração para as suas colunas. Se você arrastar um item para uma nova coluna, o valor dessa coluna será aplicado ao item arrastado. Por exemplo, se você usar o campo "Status" para as colunas do seu quadro e, em seguida, arrastar um item com o status de `Em andamento` para a coluna `Concluído`, o status do item mudará para `Concluído`.
-
-1. {% data reusables.projects.open-command-palette %}
-1. Comece digitando "Campo Coluna por" ou o nome do campo que você deseja usar para suas colunas.
-1. Escolha o comando necessário. Por exemplo, **Column field by: Status**.
-
-Como alternativa, clique em {% octicon "triangle-down" aria-label="the drop-down icon" %} ao lado da exibição do quadro que você deseja modificar e clique no **campo coluna** {% octicon "columns" aria-label="the column icon" %}. Em seguida, selecione o campo que você deseja usar para as colunas do quadro.
-
-## Filtrando itens
-
-Clique em {% octicon "filter" aria-label="the filter icon" %} na parte superior da tabela para mostrar a barra "Filtrar por palavra-chave ou por campo". Comece a digitar o nome do campo e o valor que você deseja filtrar. À medida que você digita, serão exibidos os possíveis valores.
-
-{% data reusables.projects.projects-filters %}
-
-Como alternativa, use a paleta de comando.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar "Filtrar por" ou o nome do campo que você deseja filtrar.
-3. Escolha o comando necessário. Por exemplo, **Filtro por Status**.
-4. Digite o valor para o qual você deseja filtrar. Por exemplo: "Em andamento". Você também pode filtrar pela a ausência de valores específicos (por exemplo, escolha "Excluir status" e escolha um status) ou a ausência de todos os valores (por exemplo, "Sem status").
-
-No layout da tabela, você pode clicar nos dados de item para filtrar para itens com esse valor. Por exemplo, clique em um responsável para mostrar apenas itens para ele. Para remover o filtro, clique nos dados do item novamente.
-
-Para obter mais informações, consulte "[Filtrando projetos](/issues/trying-out-the-new-projects-experience/filtering-projects)".
-
-## Criando uma visualização do projeto
-
-As visualizações do projeto permitem que você visualize rapidamente os aspectos específicos do seu projeto. Cada visualização é exibida em uma guia separada no seu projeto.
-
-Por exemplo, você pode ter:
-- Uma visualização que mostra todos os itens ainda não iniciados (filtro de "Status").
-- Uma exibição que mostra a carga de trabalho para cada equipe (agrupar por um campo personalizado de "Equipe").
-- Uma visualização que mostra itens com a data mais antiga de envio (classificar por um campo de data).
-
-Para adicionar uma nova visualização:
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar "Nova visualização" (para criar uma nova visualização) ou "Duplicar visualização" (para duplicar a visualização atual).
-3. Escolha o comando necessário.
-
-Como alternativa, clique em {% octicon "plus" aria-label="the plus icon" %} **Nova Visualização** ao lado da visualização mais à direita.
-
-Como alternativa, clique em {% octicon "triangle-down" aria-label="the drop-down icon" %} ao lado de um nome de exibição e clique em **Duplicar visualização**.
-
-A nova visualização é salva automaticamente.
-
-## Salvando alterações em uma visualização
-
-Ao fazer alterações a uma visualização como, por exemplo, ordenação, reordenação, filtragem ou agrupamento de dados em uma visualização, será exibido um ponto ao lado do nome da visualização para indicar que existem alterações não salvas.
-
-![Indicador de alterações não salvas](/assets/images/help/projects/unsaved-changes.png)
-
-Se você não desejar salvar as alterações, você poderá ignorar este indicador. Ninguém mais verá as suas alterações.
-
-Para salvar a configuração atual da exibição para todos os integrantes do projeto:
-1. {% data reusables.projects.open-command-palette %}
-1. Comece a digitar "Salvar visualização" ou "Salvar alterações na nova visualização".
-1. Escolha o comando necessário.
-
-Como alternativa, clique em {% octicon "triangle-down" aria-label="the drop-down icon" %} ao lado de um nome de exibição e clique em **Salvar visualização** ou **Salvar alterações para a próxima visualização**.
-
-## Reordenando as visualizações salvas
-
-Para alterar a ordem das abas que contêm as exibições salvas, clique e arraste uma aba para um novo local.
-
-A nova ordem da aba é salva automaticamente.
-
-## Renomeando uma visualização salva
-
-Para renomear uma visualização:
-1. Clique duas vezes no nome na aba do projeto.
-1. Altere o nome.
-1. Pressione Enter ou clique fora da aba.
-
-A alteração de nome será salva automaticamente.
-
-## Excluindo uma visualização salva
-
-Para excluir uma visualização:
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar "Excluir visualização".
-3. Escolha o comando necessário.
-
-Como alternativa, clique em {% octicon "triangle-down" aria-label="the drop-down icon" %} ao lado de um nome de exibição e clique em **Excluir visualização**.
-
-## Leia mais
-
-- "[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)"
-- "[Criando um projeto (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)"
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/filtering-projects.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/filtering-projects.md
deleted file mode 100644
index 4ee30b4ef7..0000000000
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/filtering-projects.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Filtrando projetos (beta)
-intro: Você pode filtrar seus projetos para focar em informações específicas.
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Projects
-  - Organizations
----
-
-{% data reusables.projects.projects-beta %}
-
-## Sobre a filtragem de projetos
-
-Você pode personalizar as visualizações usando filtros para os metadados do item, como os responsáveis e as etiquetas aplicadas aos problemas e pelos campos no seu projeto. Você pode combinar filtros e salvá-los como visualizações. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
-
-Para filtrar um projeto, clique em {% octicon "filter" aria-label="The Filter icon" %} e comece a digitar os campos e valores que você gostaria de filtrar. À medida que você digita, serão exibidos os possíveis valores. Você também pode abrir a paleta de comandos e digitar "Filtrar por" para escolher um dos filtros disponíveis.
-
-Os mesmos filtros estão disponíveis para indights, permitindo que você filtre os dados usados para criar seus gráficos. Para obter mais informações, consulte "[Usando insights com projetos](/issues/trying-out-the-new-projects-experience/using-insights-with-projects)".
-
-## Sintaxe para filtrar projetos
-
-{% data reusables.projects.projects-filters %}
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/index.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/index.md
deleted file mode 100644
index de6f50d670..0000000000
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Experimentando a experiência dos novos projetos
-shortTitle: Projetos (beta)
-intro: 'Crie projetos personalizados para acompanhar seu trabalho em {% data variables.product.company_short %}.'
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Issues
-  - Projects
-children:
-  - /about-projects
-  - /quickstart
-  - /creating-a-project
-  - /migrating-your-project
-  - /managing-iterations
-  - /customizing-your-project-views
-  - /filtering-projects
-  - /using-the-api-to-manage-projects
-  - /automating-projects
-  - /managing-projects
-  - /managing-the-visibility-of-your-projects
-  - /managing-access-to-projects
-  - /using-insights-with-projects
-  - /best-practices-for-managing-projects
----
-
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-iterations.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-iterations.md
deleted file mode 100644
index 1a6f7c474f..0000000000
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-iterations.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Gerenciando iterações em projetos (beta)
-intro: Você pode criar iterações para planejar os itens de trabalho e grupos futuros.
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Projects
-  - Organizations
----
-
-{% data reusables.projects.projects-beta %}
-
-## Sobre iterações
-
-Você pode criar um campo de iteração para associar itens com blocos de tempo repetidos específicos. As iterações podem ser definidas para qualquer período de tempo, podem incluir intervalos e podem ser editadas individualmente para modificar o nome e o intervalo de datas. Com os projetos, você pode agrupar por iteração para visualizar o equilíbrio do trabalho futuro, usar filtros para focar em uma única iteração, bem como ordenar por iteração.
-
-Ao criar um campo de iteração, três iterações serão criadas automaticamente.  Você pode adicionar iterações adicionais e fazer outras alterações na página de configurações do seu projeto.
-
-![Captura de tela que mostra as configurações para um campo de iteração](/assets/images/help/issues/iterations-example.png)
-
-## Criando um campo de iteração
-
-Você pode criar um campo de iteração usando a paleta de comandos ou a interface do projeto.
-
-1. {% data reusables.projects.open-command-palette %} Comece a digitar qualquer parte de "Criar novo campo". Quando "Criar novo campo" for exibido na paleta de comandos, selecione-o.
-
-   Como alternativa, clique em {% octicon "plus" aria-label="the plus icon" %} no cabeçalho do campo mais à direita. Será exibido um menu suspenso com os campos do projeto. Clique em **Novo campo**.
-1. Na caixa de texto, digite um nome para o novo campo de iteração.
-1. Selecione o menu suspenso abaixo e clique em **Iteração**.
-1. Opcionalmente, se quiser mudar a data de início a partir do dia atual, selecione o calendário suspenso ao lado de "Começa em" e clique em uma nova data de início.
-2. Para mudar a duração de cada iteração, digite um novo número, em seguida, selecione o menu suspenso e clique em **dias** ou **semanas**.
-3. Clique em **Salvar & Criar**.
-
-## Adicionando novas iterações
-
-{% data reusables.projects.project-settings %}
-1. Clique no nome do campo de iteração que você deseja ajustar.
-1. Para adicionar uma nova iteração da mesma duração, clique em **Adicionar iteração**.
-1. Opcionalmente, para personalizar a duração da nova iteração e quando ela vai começar, clique em {% octicon "triangle-down" aria-label="The triangle icon" %} ao lado de "Adicionar iteração", selecione uma data e duração iniciais, e clique em **Adicionar**.
-1. Clique em **Save changes** (Salvar alterações).
-
-## Editando uma iteração
-
-Você pode editar as iterações nas configurações do seu projeto. Você também pode acessar as configurações para um campo de iteração clicando em {% octicon "triangle-down" aria-label="The triangle icon" %} no cabeçalho da tabela para o campo e clicando em **Editar valores**.
-
-{% data reusables.projects.project-settings %}
-1. Clique no nome do campo de iteração que você deseja ajustar.
-1. Para alterar o nome de uma iteração, clique no nome e comece a digitar.
-1. Para alterar a data ou a duração de uma iteração, clique na data para abrir o calendário. Clique no dia de início, depois clique no dia de fim e depois clique em **Aplicar**.
-1. Opcionalmente, para excluir uma iteração, clique em {% octicon "trash" aria-label="The trash icon" %}.
-1. Clique em **Save changes** (Salvar alterações).
-
-## Inserindo uma pausa
-
-Você pode inserir pausas em suas iterações para se comunicar quando você está tirando o tempo do trabalho agendado. O padrão da duração de uma nova pausa é o comprimento da iteração criada mais recentemente.
-
-{% data reusables.projects.project-settings %}
-1. Clique no nome do campo de iteração que você deseja ajustar.
-2. Na linha de divisão acima de uma iteração e à direita, clique em **Inserir pausa**. ![Captura de tela que mostra a localização do botão "Inserir pausa"](/assets/images/help/issues/iteration-insert-break.png)
-3. Opcionalmente, para alterar a duração da pausa, clique na data para abrir o calendário. Clique no dia de início, depois clique no dia de fim e depois clique em **Aplicar**.
-4. Clique em **Save changes** (Salvar alterações).
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md
deleted file mode 100644
index 0b0faa794b..0000000000
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Gerenciando a visibilidade dos seus projetos (beta)
-intro: Você pode controlar quem pode ver seus projetos.
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Projects
-  - Organizations
----
-
-{% data reusables.projects.projects-beta %}
-
-## Sobre a visibilidade do projeto
-
-Os projetos (beta) podem ser públicos ou privados. Para projetos públicos, todos na Internet podem ver o projeto. Para projetos privados, apenas usuários concedidos pelo menos acessos de leitura podem ver o projeto.
-
-Apenas a visibilidade do projeto é afetada. Para ver um item no projeto, alguém deve ter as permissões necessárias para o repositório ao qual o item pertence. Se o seu projeto incluir itens de um repositório privado, pessoas que não forem colaboradores no repositório não poderão visualizar os itens desse repositório.
-
-![Projeto com item oculto](/assets/images/help/projects/hidden-items.png)
-
-Somente os administradores do projeto podem controlar a visibilidade do projeto.
-
-Em projetos privados, os avatares de usuários que estão fazendo atualizações para o projeto são exibidos na interface de usuário do projeto.
-
-Os administradores do projeto também podem gerenciar o acesso de gravação e administração ao seu projeto e controlar o acesso de leitura para usuários individuais. Para obter mais informações, consulte "[Gerenciando o acesso aos projetos](/issues/trying-out-the-new-projects-experience/managing-access-to-projects)".
-
-## Alterando a visibilidade do projeto
-
-{% data reusables.projects.project-settings %}
-1. Em **Visibilidade**, selecione **Privado** ou **Público**.
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md
deleted file mode 100644
index 0c599b3b5e..0000000000
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md
+++ /dev/null
@@ -1,164 +0,0 @@
----
-title: Início rápido para projetos (beta)
-intro: 'Experimente a velocidade, flexibilidade e personalização de projetos (beta) criando um projeto neste guia interativo.'
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-type: quick_start
-topics:
-  - Projects
----
-
-{% data reusables.projects.projects-beta %}
-
-## Introdução
-
-Este guia demonstra como usar projetos (beta) para planejar e acompanhar o trabalho. Neste guia, você irá criar um novo projeto e adicionar um campo personalizado para acompanhar as prioridades das suas tarefas. Você também aprenderá como criar visualizações salvas que ajudem a comunicar as prioridades e o progresso com seus colaboradores.
-
-## Pré-requisitos
-
-Você pode criar um projeto de organização ou um projeto de usuário. Para criar um projeto de organização, você precisa de uma organização de {% data variables.product.prodname_dotcom %}. Para obter mais informações sobre a criação de uma organização, consulte "[Criar uma nova organização a partir do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)".
-
-Neste guia, você adicionará problemas existentes de repositórios pertencentes à sua organização (para projetos de organização) ou por você (para projetos de usuário) ao seu novo projeto. Para obter mais informações sobre a criação de problemas, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-an-issue)".
-
-## Criando um projeto
-
-Primeiro, crie um projeto de organização ou um projeto de usuário.
-
-### Criando um projeto de organização
-
-{% data reusables.projects.create-project %}
-
-### Criando um projeto de usuário
-
-{% data reusables.projects.create-user-project %}
-
-## Configurando a descrição e o README do seu projeto
-
-{% data reusables.projects.project-description %}
-
-## Adicionando problemas ao seu projeto
-
-Em seguida, adicione alguns problemas ao seu projeto.
-
-Quando seu novo projeto for iniciado, ele irá solicitar que você adicione itens ao seu projeto. Se você perder esta visualização ou desejar adicionar mais problemas posteriormente, coloque seu cursor na linha inferior do projeto, ao lado de {% octicon "plus" aria-label="plus icon" %}.
-
-1. Digite `#`.
-2. Selecione o repositório onde o problema está localizado. Para restringir as opções, você pode começar a digitar parte do nome do repositório.
-3. Selecione o seu problema. Para restringir as opções, você pode começar a digitar uma parte do título do problema.
-
-Repita os passos acima algumas vezes para adicionar vários problemas ao seu projeto.
-
-Para obter mais informações sobre outras formas de adicionar problemas ao seu projeto, ou sobre outros itens que você pode adicionar ao seu projeto, consulte "[Criando um projeto](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-items-to-your-project)."
-
-## Adicionando rascunhos de problemas ao seu projeto
-
-Em seguida, adicione um rascunho ao seu projeto.
-
-1. Coloque seu cursor na linha inferior do projeto, ao lado do {% octicon "plus" aria-label="plus icon" %}.
-1. Digite sua ideia e, em seguida, pressione **Enter**.
-1. Clique no título do rascunho do problema. Na caixa de entrada do markdown que será exibida, insira mais informações sobre a sua ideia e, em seguida, clique em **Salvar**.
-
-## Criando um campo para monitorar a prioridade
-
-Agora, crie um campo personalizado denominado `Prioridade` para conter os valores: `Alto`, `Médio` ou `Baixo`.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar qualquer parte de "Criar novo campo".
-3. Selecione **Criar novo campo**.
-4. Na janela de pop-up resultante, digite `Prioridade` na caixa de texto.
-5. Na lista de seleção, selecione **Seleção única**.
-6. Adicionar opções para `Alto`, `Médio` e `Baixo`. Você também pode incluir emojis nas suas opções. ![Novo exemplo de campo de seleção única](/assets/images/help/projects/new-single-select-field.png)
-7. Clique em **Salvar**.
-
-Especifique uma prioridade para todos os problemas no seu projeto.
-
-![Prioridades de exemplo](/assets/images/help/projects/priority_example.png)
-
-## Agrupar problemas por prioridade
-
-Em seguida, agrupe todos os itens do seu projeto por prioridade para facilitar o foco nos itens de alta prioridade.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar qualquer parte de "Agrupar por".
-3. Selecione **Agrupar por: Prioridade**.
-
-Agora, transfira os problemas entre grupos para mudar a sua prioridade.
-
-1. Escolha um problema.
-2. Arraste e solte o problema em um grupo de prioridade diferente. Ao fazer isso, a prioridade do problema passará a ser a prioridade do seu novo grupo.
-
-![Transferir problemas entre grupos](/assets/images/help/projects/move_between_group.gif)
-
-## Salvando a visualização da prioridade
-
-Quando você agrupou os seus problemas por prioridade na etapa anterior, seu projeto exibiu um indicador para mostrar que a visualização foi modificada. Salve essas alterações para que os seus colaboradores vejam as tarefas agrupadas por prioridade.
-
-1. Selecione o menu suspenso ao lado do nome da visualização.
-2. Clique em **Save changes** (Salvar alterações).
-
-Para indicar o propósito da visão, dê um nome descritivo.
-
-1. Coloque o cursor no nome atual da visualização, **Visualização 1**.
-2. Substitua o texto existente pelo novo nome, `Prioridades`.
-
-Você pode compartilhar a URL com seu time para manter todos alinhados com as prioridades do projeto.
-
-Quando a visualização é salva, qualquer pessoa que abrir o projeto verá a visualização salva. Aqui, você agrupou por prioridade, mas você também pode adicionar outros modificadores como ordenação, filtro ou layout. Em seguida, você criará uma nova exibição com o layout modificado.
-
-## Adicionando um layout de quadro
-
-Para ver o progresso dos problemas do seu projeto, você pode alternar para o layout do quadro.
-
-O layout do quadro é baseado no campo de status. Portanto, especifique um status para cada problema no seu projeto.
-
-![Status do exemplo](/assets/images/help/projects/status_example.png)
-
-Em seguida, crie uma nova visualização.
-
-1. Clique em {% octicon "plus" aria-label="the plus icon" %} **Nova Visualização** ao lado da visualização mais à direita.
-
-Em seguida, mude para o layout do quadro.
-
-1. {% data reusables.projects.open-command-palette %}
-2. Comece a digitar qualquer parte de "Layout Switch: Board".
-3. Selecione **Mudar layout: Board**. ![Prioridades de exemplo](/assets/images/help/projects/example_board.png)
-
-Quando você alterou o layout, o projeto exibiu um indicador para mostrar que a visualização foi modificada. Salve esta visualização para que você e seus colaboradores possam acessá-la facilmente no futuro.
-
-1. Selecione o menu suspenso ao lado do nome da visualização.
-2. Clique em **Save changes** (Salvar alterações).
-
-Para indicar o propósito da visão, dê um nome descritivo.
-
-1. Coloque o cursor no nome atual da visualização, **Visualização2**.
-2. Substitua o texto existente pelo novo nome, `Progresso`.
-
-![Prioridades de exemplo](/assets/images/help/projects/project-view-switch.gif)
-
-## Configure a automação integrada
-
-Por fim, adicione um fluxo de trabalho construído para definir o status como **Todo** quando um item for adicionado ao seu projeto.
-
-1. No seu projeto, clique em {% octicon "workflow" aria-label="the workflow icon" %}.
-2. Em **Fluxos de trabalho padrão**, clique em **Item adicionado ao projeto**.
-3. Ao lado de **Quando**, certifique-se de que `problemas` e `pull requests` estejam selecionados.
-4. Ao lado de **Definir**, selecione **Status:Todo**.
-5. Clique na opção **Desabilitada** para habilitar o fluxo de trabalho.
-
-## Próximas etapas
-
-Você pode usar projetos para uma ampla gama de finalidades. Por exemplo:
-
-- Acompanhar o trabalho para uma versão
-- Plan a sprint
-- Priorizar um backlog
-
-Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_github_issues %}:
-
-- Para fornecer feedback sobre os projetos (beta) experiência, acesse o [Repositório de comentários GitHub](https://github.com/github/feedback/discussions/categories/issues-feedback).
-- Para saber mais sobre como os projetos podem ajudar você com o planejamento e monitoramento, consulte "[Sobre projetos](/issues/trying-out-the-new-projects-experience/about-projects)".
-- Para saber mais sobre os campos e itens que você pode adicionar ao seu projeto, consulte "[Criar um projeto](/issues/trying-out-the-new-projects-experience/creating-a-project)".
-- Para aprender mais sobre maneiras de exibir as informações que você precisa, consulte "[Personalizar visualizações de projeto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md
deleted file mode 100644
index 9aed9e8e25..0000000000
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Usando insights com projetos (beta)
-intro: Você pode visualizar e personalizar gráficos construídos a partir dos dados do seu projeto.
-allowTitleToDifferFromFilename: true
-miniTocMaxHeadingLevel: 2
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Projects
-  - Organizations
----
-
-{% data reusables.projects.insights-alpha %}
-
-## Sobre insights
-
-Você pode usar os insights para visualizar e personalizar gráficos que usam os itens adicionados ao seu projeto como seus dados de origem. O gráfico padrão "Burn up" mostra o status do item ao longo do tempo, permitindo que você visualize o progresso e os padrões de ponto ao longo do tempo.
-
-![Captura de tela que mostra um exemplo do gráfico padrão de burn up para a iteração atual](/assets/images/help/issues/burnup-example.png)
-
-Você pode aplicar filtros ao gráfico padrão e também criar seus próprios gráficos. Ao criar um gráfico, você define os filtros, o tipo de gráfico e as informações exibidas, e o gráfico está disponível para qualquer pessoa que possa visualizar o projeto.
-
-![Captura de tela que mostra um gráfico de colunas empilhadas com tipos de itens para cada iteração](/assets/images/help/issues/column-chart-example.png)
-
-## Criando um gráfico
-
-{% data reusables.projects.access-insights %}
-3. No menu à esquerda, clique em **Novo gráfico**.
-4. Opcionalmente, para alterar o nome do novo gráfico, clique em {% octicon "triangle-down" aria-label="The triangle icon" %}, digite um novo nome e pressione <kbd>Retornar</kbd>.
-5. Acima do gráfico, digite os filtros para alterar os dados utilizados para a construção do gráfico. Para obter mais informações, consulte "[Filtrando projetos](/issues/trying-out-the-new-projects-experience/filtering-projects)".
-6. À direita da caixa de texto do filtro, clique em **Salvar alterações**.
-
-## Configurando um gráfico
-
-{% data reusables.projects.access-insights %}
-1. No menu à esquerda, clique no gráfico que deseja configurar.
-1. No lado direito da página, clique em **Configurar**. Será aberto um painel à direita.
-1. Para alterar o tipo de gráfico, selecione a lista suspensa do **Layout** e clique no tipo de gráfico que você deseja usar.
-1. Para alterar o campo usado no eixo X do gráfico, selecione o menu suspenso **Eixo X** e clique no campo que você deseja usar.
-1. Opcionalmente, para agrupar os itens no seu eixo X por outro campo, selecione **Agrupar por** e clique no campo que você deseja usar ou clique em "Nenhum" para desabilitar o agrupamento.
-1. Opcionalmente, se o seu projeto contiver campos numéricos e você quiser que o eixo Y exiba a soma, média, mínimo ou máximo de um desses campos numéricos, selecione **eixo Y** e clique em uma opção. Em seguida, selecione o menu suspenso que aparece abaixo e clique no campo número que você deseja usar.
-1. Para salvar seu gráfico, clique em **Salvar alterações**.
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
index 219fb4280e..d5cee8b617 100644
--- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -52,6 +52,7 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes or ghec %}
 | [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. | {% endif %}
 | [`hook`](#hook-category-actions) | Contains all activities related to webhooks.
+| [`integration_installation`](#integration_installation-category-actions)  | Contains activities related to integrations installed in an account. |
 | [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |{% ifversion ghec or ghae %}
 | [`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 %}
@@ -361,6 +362,21 @@ An overview of some of the most common actions that are recorded as events in th
 | `destroy` | Triggered when an existing hook was removed from a repository.
 | `events_changed` | Triggered when the events on a hook have been altered.
 
+### `integration_installation` category actions
+
+| Action | Description
+|--------|-------------
+| `contact_email_changed` | A contact email for an integration was changed.
+| `create` | An integration was installed.
+| `destroy` | An integration was uninstalled.
+| `repositories_added` | Repositories were added to an integration.
+| `repositories_removed` | Repositories were removed from an integration.
+{%- ifversion fpt or ghec %}
+| `suspend` | An integration was suspended.
+| `unsuspend` | An integration was unsuspended.
+{%- endif %}
+| `version_updated` | Permissions for an integration were updated.
+
 ### `integration_installation_request` category actions
 
 | Action | Description
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
index 7681d42c0a..9fe03c8946 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Adicionar um colaborador externo a um quadro de projeto em sua organização
-intro: 'Como um proprietário da organização ou administrador do quadro de projeto, você pode adicionar um colaborador externo e personalizar as permissões dele em um quadro de projeto.'
+title: 'Adding an outside collaborator to a {% data variables.product.prodname_project_v1 %} in your organization'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can add an outside collaborator and customize their permissions to a {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization
@@ -13,13 +13,17 @@ topics:
   - Organizations
   - Teams
 shortTitle: Adicionar um colaborador
+allowTitleToDifferFromFilename: true
 ---
 
-Um colaborador externo é uma pessoa que não é explicitamente um integrante da sua organização, mas tem permissões para um quadro de projeto em sua organização.
+{% data reusables.projects.project_boards_old %}
+
+An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a {% data variables.projects.projects_v1_board %} in your organization.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/index.md
index e5ad2f83cc..151b332f3b 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/index.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/index.md
@@ -1,6 +1,6 @@
 ---
-title: Gerenciar acessos aos quadros de projetos da organização
-intro: 'Como proprietário da organização ou administrador de quadro de projeto, você pode conceder a integrantes, equipes e colaboradores externos níveis diferentes de acesso a quadros de projetos de propriedade da organização.'
+title: 'Managing access to your organization’s {% data variables.product.prodname_projects_v1 %}'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give organization members, teams, and outside collaborators different levels of access to {% data variables.projects.projects_v1_boards %} owned by your organization.'
 redirect_from:
   - /articles/managing-access-to-your-organization-s-project-boards
   - /articles/managing-access-to-your-organizations-project-boards
@@ -20,6 +20,7 @@ children:
   - /managing-an-individuals-access-to-an-organization-project-board
   - /adding-an-outside-collaborator-to-a-project-board-in-your-organization
   - /removing-an-outside-collaborator-from-an-organization-project-board
-shortTitle: Gerenciar acesso ao quadro de projeto
+shortTitle: 'Manage {% data variables.product.prodname_project_v1 %} access'
+allowTitleToDifferFromFilename: true
 ---
 
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
index 63554d9316..790c3e29db 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
@@ -1,6 +1,6 @@
 ---
-title: Gerenciar acesso de integrantes da organização a um quadro de projeto
-intro: 'Como proprietário da organização ou administrador de quadro de projeto, você pode configurar um nível de permissão padrão para todos os integrantes da organização.'
+title: 'Managing access to a {% data variables.product.prodname_project_v1 %} for organization members'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can set a default permission level for a {% data variables.projects.projects_v1_board %} for all organization members.'
 redirect_from:
   - /articles/managing-access-to-a-project-board-for-organization-members
   - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members
@@ -13,21 +13,25 @@ topics:
   - Organizations
   - Teams
 shortTitle: Gerenciar acesso para os integrantes
+allowTitleToDifferFromFilename: true
 ---
 
-Por padrão, os integrantes de uma organização têm acesso de gravação nos quadros de projetos da organização, exceto se os proprietários da organização ou os administradores de quadro de projeto configurarem permissões diferentes para quadros de projetos específicos.
+{% data reusables.projects.project_boards_old %}
+
+By default, organization members have write access to their organization's {% data variables.projects.projects_v1_boards %} unless organization owners or {% data variables.projects.projects_v1_board %} admins set different permissions for specific {% data variables.projects.projects_v1_boards %}.
 
 ## Configurar um nível referencial de permissão para todos os integrantes da organização
 
 {% tip %}
 
-**Dica:** você pode dar a um integrante da organização as permissões mais altas em um um quadro de projeto. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)".
+**Tip:** You can give an organization member higher permissions to {% data variables.projects.projects_v1_board %}. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)".
 
 {% endtip %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
@@ -36,6 +40,6 @@ Por padrão, os integrantes de uma organização têm acesso de gravação nos q
 
 ## Leia mais
 
-- "[Gerenciar o acesso de um indivíduo a um quadro de projeto da organização](/articles/managing-an-individual-s-access-to-an-organization-project-board)"
-- "[Gerenciar o acesso da equipe a um quadro de projeto da organização](/articles/managing-team-access-to-an-organization-project-board)"
-- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)"
+- "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)"
+- "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)"
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
index f574771e00..17db62b3aa 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Gerenciar o acesso de um indivíduo a um quadro de projeto da organização
-intro: 'Como proprietário da organização ou administrador de quadro de projeto, você pode gerenciar o acesso de um integrante individual a um quadro de projeto pertencente à sua organização.'
+title: 'Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can manage an individual member''s access to a {% data variables.projects.projects_v1_board %} owned by your organization.'
 redirect_from:
   - /articles/managing-an-individual-s-access-to-an-organization-project-board
   - /articles/managing-an-individuals-access-to-an-organization-project-board
@@ -14,19 +14,23 @@ topics:
   - Organizations
   - Teams
 shortTitle: Gerenciar acesso individual
+allowTitleToDifferFromFilename: true
 ---
 
+{% data reusables.projects.project_boards_old %}
+
 {% note %}
 
-**Observação:** {% data reusables.project-management.cascading-permissions %} para obter mais informações, consulte "[Permissões do quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)".
+**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% endnote %}
 
-## Conceder a um integrante da organização acesso a um quadro de projeto
+## Giving an organization member access to a {% data variables.projects.projects_v1_board %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
@@ -35,24 +39,26 @@ shortTitle: Gerenciar acesso individual
 {% data reusables.project-management.add-collaborator %}
 {% data reusables.project-management.collaborator-permissions %}
 
-## Alterar o acesso de um integrante da organização a um quadro de projeto
+## Changing an organization member's access to a {% data variables.projects.projects_v1_board %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
 {% data reusables.project-management.collaborator-option %}
 {% data reusables.project-management.collaborator-permissions %}
 
-## Remover o acesso de um integrante da organização a um quadro de projeto
+## Removing an organization member's access to a {% data variables.projects.projects_v1_board %}
 
-Quando você remove um colaborador de um quadro de projeto, a pessoa ainda pode ter acesso ao quadro com base nas permisões que tem para outras funções. Para remover completamente o acesso ao quadro de projeto, você deve remover o acesso à cada função que a pessoa tem. Por exemplo, uma pessoa pode ter acesso ao quadro de projeto como integrante de uma organização ou equipe. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)".
+When you remove a collaborator from a {% data variables.projects.projects_v1_board %}, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a {% data variables.projects.projects_v1_board %}, you must remove access for each role the person has. For instance, a person may have access to the {% data variables.projects.projects_v1_board %} as an organization member or team member. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
@@ -61,4 +67,4 @@ Quando você remove um colaborador de um quadro de projeto, a pessoa ainda pode
 
 ## Leia mais
 
-- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)"
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index bd8eecf223..194e2aec07 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Gerenciar o acesso da equipe em um quadro de projeto da organização
-intro: 'Como proprietário da organização ou administrador de quadro de projeto, você pode conceder o acesso da equipe a um quadro de projeto pertencente à sua organização.'
+title: 'Managing team access to an organization {% data variables.product.prodname_project_v1 %}'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.'
 redirect_from:
   - /articles/managing-team-access-to-an-organization-project-board
   - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board
@@ -13,29 +13,33 @@ topics:
   - Organizations
   - Teams
 shortTitle: Gerenciar acesso de equipe
+allowTitleToDifferFromFilename: true
 ---
 
+{% data reusables.projects.project_boards_old %}
+
 {% warning %}
 
 **Avisos:**
-- Você pode alterar os níveis de permissões de uma equipe se a equipe tiver acesso direto a um quadro de projeto. Se o acesso da equipe ao quadro de projeto é herança de uma equipe principal, você deve alterar o acesso da equipe principal ao quadro de projeto.
-- Se você adicionar ou remover acesso de uma equipe principal ao quadro de projeto, cada uma das equipes secundárias da equipe principal também receberá ou perderá o acesso ao quadro de projeto. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)".
+- You can change a team's permission level if the team has direct access to a {% data variables.projects.projects_v1_board %}. If the team's access to the {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %}.
+- If you add or remove {% data variables.projects.projects_v1_board %} access for a parent team, each of that parent's child teams will also receive or lose access to the {% data variables.projects.projects_v1_board %}. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)".
 
 {% endwarning %}
 
-## Conceder a uma equipe acesso a um quadro de projeto
+## Giving a team access to a {% data variables.projects.projects_v1_board %}
 
-Você pode dar a uma equipe inteira o mesmo nível de permissão em um quadro de projeto.
+You can give an entire team the same permission level to a {% data variables.projects.projects_v1_board %}.
 
 {% note %}
 
-**Observação:** {% data reusables.project-management.cascading-permissions %} por exemplo, se um proprietário da organização deu a uma equipe permissões de leitura em um quadro de projeto e um administrador de quadro de projeto concede permissões de administrador a um integrante da equipe como um colaborador individual, essa pessoa teria permissões de administrador no quadro de projeto. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)".
+**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a {% data variables.projects.projects_v1_board %}, and a {% data variables.projects.projects_v1_board %} admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the {% data variables.projects.projects_v1_board %}. For more information see, "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% endnote %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
@@ -43,12 +47,12 @@ Você pode dar a uma equipe inteira o mesmo nível de permissão em um quadro de
 9. Para adicionar uma equipe, clique em **Add a team: Select team** (Adicionar uma equipe: Selecionar equipe). Depois, escolha uma equipe no menu suspenso ou pesquise a equipe que você deseja adicionar. ![Menu suspenso Add a team (Adicionar uma equipe) com lista de equipes na organização](/assets/images/help/projects/add-a-team.png)
 10. Ao lado do nome da equipe, use o menu suspenso para selecionar o nível de permissão desejado: **Read** (Leitura), **Write** (Gravação) ou **Admin** (Administrador). ![Menu suspenso Team permissions (Permissões de equipe) com opções read, write e admin (leitura, gravação e administrador)](/assets/images/help/projects/org-project-team-choose-permissions.png)
 
-## Configurar o acesso de uma equipe a um quadro de projeto
+## Configuring a team's access to a {% data variables.projects.projects_v1_board %}
 
-Se o acesso de uma equipe a um quadro de projeto for herdado de uma equipe principal, você deverá alterar o acesso da equipe principal ao quadro de projeto para atualizar o acesso das equipes secundárias.
+If a team's access to a {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %} to update access to the child teams.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.specific_team %}
 4. Acima das conversas da equipe, clique em {% octicon "project" aria-label="The Projects icon" %} **Projects** (Projetos). ![Aba repositórios da equipe](/assets/images/help/organizations/team-project-board-button.png)
-5. Para alterar os níveis de permissão, à direita do quadro de projetos que deseja atualizar, use o menu suspenso. Para remover um quadro de projeto, clique em **{% octicon "trash" aria-label="The trash icon" %}**. ![Botão Trash (Lixeira) Remove a project board from your team (Remover um quadro de projeto de sua equipe)](/assets/images/help/organizations/trash-button.png)
+5. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the drop-down. To remove a {% data variables.projects.projects_v1_board %}, click **{% octicon "trash" aria-label="The trash icon" %}**. ![Botão Trash (Lixeira) Remove a project board from your team (Remover um quadro de projeto de sua equipe)](/assets/images/help/organizations/trash-button.png)
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md
index f87e6273b5..3c035c136b 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Permissões do quadro de projeto da organização
-intro: 'Proprietários da organização e pessoas com permissões de administradores de quadro de projeto podem personalizar quem tem permissões de leitura, gravação e de administrador nos quadros de projeto da organização.'
+title: '{% data variables.product.prodname_project_v1_caps %} permissions for an organization'
+intro: 'Organization owners and people with {% data variables.projects.projects_v1_board %} admin permissions can customize who has read, write, and admin permissions to your organization’s {% data variables.projects.projects_v1_boards %}.'
 redirect_from:
   - /articles/project-board-permissions-for-an-organization
   - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization
@@ -12,35 +12,38 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Permissões do quadro de projeto
+shortTitle: 'Permissões do {% data variables.product.prodname_project_v1_caps %}'
+allowTitleToDifferFromFilename: true
 ---
 
+{% data reusables.projects.project_boards_old %}
+
 ## Visão geral das permissões
 
-Existem três níveis de permissões em um quadro de projeto para pessoas e equipes:
+There are three levels of permissions to a {% data variables.projects.projects_v1_board %} for people and teams:
 
 {% data reusables.project-management.project-board-permissions %}
 
-Os proprietários da organização e pessoas com permissões de administrador podem conceder acesso a alguém a um quadro de projeto da organização individualmente, como colaborador externo ou integrante da organização, ou ainda, por meio da associação dele a uma equipe ou organização. Um colaborador externo é uma pessoa que não é integrante da organização mas recebeu permissões para colaborar na organização.
+Organization owners and people with admin permissions can give a person access to an organization {% data variables.projects.projects_v1_board %} individually, as an outside collaborator or organization member, or through their membership in a team or organization. Um colaborador externo é uma pessoa que não é integrante da organização mas recebeu permissões para colaborar na organização.
 
-Proprietários da organização e pessoas com permissões de administrador em um quadro de projeto também podem:
+Organization owners and people with admin permissions to a {% data variables.projects.projects_v1_board %} can also:
 - Definir permissões de quadro de projeto padrão para todos os integrantes da organização.
-- Gerenciar o acesso de integrantes, equipes e colaboradores externos da organização ao quadro de projeto. Para obter mais informações, consulte "[Gerenciar o acesso da equipe a um quadro de projeto da organização](/articles/managing-team-access-to-an-organization-project-board)", "[Gerenciar o acesso de um indivíduo a um quadro de projeto da organização](/articles/managing-an-individual-s-access-to-an-organization-project-board)" ou "[Gerenciar o acesso de integrantes da organização a um quadro de projeto](/articles/managing-access-to-a-project-board-for-organization-members)".
-- Gerenciar a visibilidade do quadro de projeto. Para obter mais informações, consulte "[Gerenciar o acesso de integrantes da organização a um quadro de projeto](/articles/managing-access-to-a-project-board-for-organization-members)".
+- Gerenciar o acesso de integrantes, equipes e colaboradores externos da organização ao quadro de projeto. For more information, see "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)", "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)", or "[Managing access to a {% data variables.product.prodname_project_v1 %} for organization members](/articles/managing-access-to-a-project-board-for-organization-members)."
+- Gerenciar a visibilidade do quadro de projeto. For more information, see "[Managing access to a {% data variables.product.prodname_project_v1 %} for organization members](/articles/managing-access-to-a-project-board-for-organization-members)."
 
-## Permissões de acesso em cascata para quadros de projeto
+## Cascading permissions for {% data variables.projects.projects_v1_boards %}
 
 {% data reusables.project-management.cascading-permissions %}
 
-Por exemplo, se um proprietário da organização concedeu a todos os integrantes de uma equipe permissões de leitura em um quadro de projeto e um administrador de quadro de projeto concede permissões de gravação a um integrante da equipe naquele quadro de projeto como um colaborador individual, essa pessoa teria permissões de gravação no quadro de projeto.
+For example, if an organization owner has given all organization members read permissions to a {% data variables.projects.projects_v1_board %}, and a {% data variables.projects.projects_v1_board %} admin gives an organization member write permissions to that board as an individual collaborator, that person would have write permissions to the {% data variables.projects.projects_v1_board %}.
 
-## Visibilidade do quadro de projeto
+## {% data variables.projects.projects_v1_board_caps %} visibility
 
-{% data reusables.project-management.project-board-visibility %} Você pode alterar a visibilidade do quadro de projeto de privado para {% ifversion ghae %}interno{% else %}public{% endif %} e novamente para privado. Para obter mais informações, consulte "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)".
+{% data reusables.project-management.project-board-visibility %} You can change the {% data variables.projects.projects_v1_board %}'s visibility from private to {% ifversion ghae %}internal{% else %}public{% endif %} and back again. For more information, see "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility)."
 
 ## Leia mais
 
-- "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)"
-- "[Gerenciar o acesso de um indivíduo a um quadro de projeto da organização](/articles/managing-an-individual-s-access-to-an-organization-project-board)"
-- "[Gerenciar o acesso da equipe a um quadro de projeto da organização](/articles/managing-team-access-to-an-organization-project-board)"
-- "[Gerenciar o acesso de integrantes da organização a um quadro de projeto](/articles/managing-access-to-a-project-board-for-organization-members)"
+- "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility)"
+- "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)"
+- "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)"
+- "[Managing access to a {% data variables.product.prodname_project_v1 %} for organization members](/articles/managing-access-to-a-project-board-for-organization-members)"
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
index 57117660d8..0da2326542 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Remover um colaborador externo do quadro de projeto da organização
-intro: 'Como proprietário da organização ou administrador do quadro de projeto, você pode remover o acesso de um colaborador externo ao quadro de projeto.'
+title: 'Removing an outside collaborator from an organization {% data variables.product.prodname_project_v1 %}'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can remove an outside collaborator''s access to a {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /articles/removing-an-outside-collaborator-from-an-organization-project-board
   - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board
@@ -13,11 +13,15 @@ topics:
   - Organizations
   - Teams
 shortTitle: Remover colaborador externo
+allowTitleToDifferFromFilename: true
 ---
 
+{% data reusables.projects.project_boards_old %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
 {% data reusables.project-management.select-project %}
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
new file mode 100644
index 0000000000..c8ec1bce93
--- /dev/null
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
@@ -0,0 +1,26 @@
+---
+title: Allowing project visibility changes in your organization
+intro: Organization owners can allow members with admin permissions to adjust the visibility of projects in their organization.
+versions:
+  feature: projects-v2
+topics:
+  - Organizations
+  - Projects
+shortTitle: Project visibility permissions
+allowTitleToDifferFromFilename: true
+permissions: Organization owners can allow project visibility changes for an organization.
+---
+
+You can restrict who has the ability to change the visibility of projects in your organization, such as restricting members from changing a project from private to public.
+
+You can limit the ability to change project visibility to just organization owners, or you can allow anyone with admin permissions on a project to change the visibility.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
+1. To allow members to adjust project visibility, select **Allow members to change project visibilities for this organization**. ![Screenshot showing checkbox to set visibility changes](/assets/images/help/projects-v2/visibility-change-checkbox.png)
+1. Clique em **Salvar**.
+
+## Leia mais
+
+- "[Managing visibility of your projects](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)"
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
new file mode 100644
index 0000000000..390e19fc27
--- /dev/null
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
@@ -0,0 +1,25 @@
+---
+title: 'Disabling insights for {% data variables.projects.projects_v2 %} in your organization'
+intro: 'Organization owners can turn off insights for {% data variables.product.prodname_projects_v2 %} in their organization.'
+versions:
+  feature: projects-v2
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+shortTitle: 'Disable {% data variables.product.prodname_projects_v2 %} insights'
+allowTitleToDifferFromFilename: true
+---
+
+After you disable insights for projects in your organization, it won't be possible to access insights for any projects owned by the organization.
+
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the sidebar, click **{% octicon "sliders" aria-label="The sliders icon" %} Features**. ![Screenshot showing features menu item](/assets/images/help/projects-v2/features-org-menu.png)
+1. Under "Insights", deselect **Enable Insights for the organization**. ![Screenshot showing Enable Insights for the organization checkbox](/assets/images/help/projects-v2/disable-insights-checkbox.png)
+1. Clique em **Salvar**. ![Screenshot showing save button](/assets/images/help/projects-v2/disable-insights-save.png)
+
+## Leia mais
+
+- "[Sobre o {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)"
+- "[About insights for {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects)"
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
index 50994230dc..0daad087c7 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Desabilitar quadros de projeto na sua organização
-intro: Os proprietários da organização podem desativar quadros de projeto em toda a organização e quadros de projeto de repositório em uma organização.
+title: 'Disabling {% ifversion projects-v2 %}projects{% else %}project boards{% endif %} in your organization'
+intro: 'Organization owners can turn off {% ifversion projects-v2 %}organization-wide {% data variables.projects.projects_v2 %}, organization-wide {% data variables.projects.projects_v1_boards %}, and repository-level {% data variables.projects.projects_v1_boards %}{% else %}organization-wide project boards and repository project boards{% endif %} in an organization.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-your-organization
   - /articles/disabling-project-boards-in-your-organization
@@ -12,13 +12,15 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Desabilitar quadro de projetos
+shortTitle: Disable projects
+allowTitleToDifferFromFilename: true
 ---
 
-Após a desabilitação dos quadros de projeto em toda a organização, não é mais possível criar quadros de projeto no nível da organização nem acessar os quadros de projeto no nível de organização já existentes pelas URLs anteriores. Os quadros de projeto em repositórios não são afetados.
+Após a desabilitação dos quadros de projeto em toda a organização, não é mais possível criar quadros de projeto no nível da organização nem acessar os quadros de projeto no nível de organização já existentes pelas URLs anteriores. Os quadros de projeto em repositórios não são afetados. {% ifversion projects-v2 %}These settings apply to {% data variables.projects.projects_v2 %} and {% data variables.projects.projects_v1_boards %}.{% endif %}
 
 Após a desabilitação dos quadros de projeto de repositório em uma organização, não é mais possível criar quadros de projeto em repositórios da organização nem acessar os quadros de projeto já existentes em repositórios da organização pelas URLs anteriores. Os quadros de projeto no nível da organização não são afetados.
 
+
 Quando você desabilita quadros de projeto, deixa de ver informações relacionadas a eles em linhas do tempo ou [logs de auditoria](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization).
 
 
@@ -36,7 +38,8 @@ Quando você desabilita quadros de projeto, deixa de ver informações relaciona
 
 ## Leia mais
 
-- "[Sobre quadros de projetos](/articles/about-project-boards)"
-- "[Fechar um quadro de projeto](/articles/closing-a-project-board)"
-- "[Excluir um quadro de projeto](/articles/deleting-a-project-board)"
-- "[Desabilitar quadros de projeto em um repositório](/articles/disabling-project-boards-in-a-repository)"
+{% ifversion projects-v2 %}- "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)"{% endif %}
+- "[Sobre o {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Closing a {% data variables.projects.projects_v1_board %}](/articles/closing-a-project-board)"
+- "[Deleting a {% data variables.projects.projects_v1_board %}](/articles/deleting-a-project-board)"
+- "[Disabling {% data variables.projects.projects_v1_boards %} in a repository](/articles/disabling-project-boards-in-a-repository)"
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/index.md b/translations/pt-BR/content/organizations/managing-organization-settings/index.md
index 37700c74f3..d4abee0941 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/index.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/index.md
@@ -41,6 +41,8 @@ children:
   - /integrating-jira-with-your-organization-project-board
   - /upgrading-to-the-corporate-terms-of-service
   - /disabling-project-boards-in-your-organization
+  - /disabling-insights-for-projects-in-your-organization
+  - /allowing-project-visibility-changes-in-your-organization
 shortTitle: Gerenciar as configurações da organização
 ---
 
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
index 66928608d1..c06c37a2a8 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
@@ -1,5 +1,5 @@
 ---
-title: Managing the commit signoff policy for your organization
+title: Gerenciando a política de aprovação do commit para sua organização
 intro: 'You can require users to automatically sign off all commits they make in {% data variables.product.product_name %}''s web interface to repositories owned by your organization.'
 versions:
   feature: commit-signoffs
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index 084952cd74..006254d49c 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -23,7 +23,7 @@ Proprietários de organização podem gerenciar a exibição do nome de integran
 Cada integrante da organização escolhe o próprio nome de perfil nas configurações. Para obter mais informações, consulte "[Personalizar seu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)".
 
 {% ifversion profile-name-enterprise-setting %}
-You may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)".{% endif %}
+Você pode não conseguir definir esta configuração para a organização se um proprietário de empresa definiu uma política ao nível da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)".{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
diff --git a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
index f15394eb8c..f5ee768345 100644
--- a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
+++ b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
@@ -89,11 +89,14 @@ Crie um novo arquivo de fluxo de trabalho no repositório (como `.github/workflo
 {% data reusables.package_registry.publish-docker-image %}
 
 {% else %}
-```yaml{:copy}
-name: Create and publish a Docker image
 
+```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Create and publish a Docker image
+
 on:
   push:
     branches: ['release']
diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
index 6bfbba53e4..44177e2e46 100644
--- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -10,7 +10,7 @@ versions:
   fpt: '*'
   ghec: '*'
   feature: docker-ghcr-enterprise-migration
-shortTitle: Migration to Container registry
+shortTitle: Migração para o registro do contêiner
 topics:
   - Containers
   - Docker
@@ -21,9 +21,9 @@ topics:
 
 ## Sobre o {% data variables.product.prodname_container_registry %}
 
-{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+{% data reusables.package_registry.container-registry-benefits %} Para obter mais informações, consulte "[Trabalhando com o {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)".
 
-## About migration from the Docker registry
+## Sobre a migração do registro do Docker
 
 {% data reusables.package_registry.container-registry-replaces-docker-registry %} If you've stored Docker images in the Docker registry, {% ifversion docker-ghcr-enterprise-migration %}an enterprise owner{% else %}{% data variables.product.company_short %}{% endif %} will gradually migrate the images to the {% data variables.product.prodname_container_registry %}. No action is required on your part.
 
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
index faa5cd9249..a333f2fae9 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Desabilitar quadros de projeto em um repositório
-intro: Os administradores de repositório podem desativar quadros de projeto de um repositório se você ou sua equipe gerenciam o trabalho de forma diferente.
+title: 'Disabling {% data variables.projects.projects_v1_boards %} in a repository'
+intro: 'Repository administrators can turn off {% data variables.projects.projects_v1_boards %} for a repository if you or your team manages work differently.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-a-repository
   - /articles/disabling-project-boards-in-a-repository
@@ -13,13 +13,14 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Desabilitar quadro de projetos
+shortTitle: 'Disable {% data variables.projects.projects_v1_boards %}'
+allowTitleToDifferFromFilename: true
 ---
 
-Quando você desabilita quadros de projeto, deixa de ver informações relacionadas a eles em linhas do tempo ou [logs de auditoria](/articles/reviewing-your-security-log/).
+When you disable {% data variables.projects.projects_v1_boards %}, you will no longer see {% data variables.projects.projects_v1_board %} information in timelines or [audit logs](/articles/reviewing-your-security-log/).
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 3. Em "Features" (Recursos), desmarque a caixa de seleção **Projects** (Projetos). ![Caixa de seleção Remove Projects (Remover projetos)](/assets/images/help/projects/disable-projects-checkbox.png)
 
-Após a desabilitação dos quadros de projeto, não é mais possível acessar os quadros de projeto já existentes pelas URLs anteriores. {% data reusables.organizations.disable_project_board_results %}
+After {% data variables.projects.projects_v1_boards %} are disabled, existing {% data variables.projects.projects_v1_boards %} are inaccessible at their previous URLs. {% data reusables.organizations.disable_project_board_results %}
diff --git a/translations/pt-BR/content/rest/overview/endpoints-available-for-github-apps.md b/translations/pt-BR/content/rest/overview/endpoints-available-for-github-apps.md
index 23eb370fec..cb7a80b390 100644
--- a/translations/pt-BR/content/rest/overview/endpoints-available-for-github-apps.md
+++ b/translations/pt-BR/content/rest/overview/endpoints-available-for-github-apps.md
@@ -15,4 +15,4 @@ topics:
 shortTitle: Pontos de extremidade habilitados pelo aplicativo GitHub
 ---
 
-**O conteúdo desta página é processado como um componente da página do NextJS.**
+<!-- The content of this page is rendered as a NextJS page component. -->
diff --git a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md
index c25ab49304..c67392bf5e 100644
--- a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md
@@ -304,6 +304,18 @@ Os valores de `rel` possíveis são:
 | `first`   | A relação de link para a primeira página de resultados.          |
 | `prev`    | A relação de link para a página de resultados anterior imediata. |
 
+## Tempo esgotado
+
+If {% data variables.product.prodname_dotcom %} takes more than 10 seconds to process an API request, {% data variables.product.prodname_dotcom %} will terminate the request and you will receive a timeout response like this:
+
+```json
+{
+    "message": "Server Error"
+}
+```
+
+{% data variables.product.product_name %} reserves the right to change the timeout window to protect the speed and reliability of the API.
+
 ## Limite de taxa
 
 Os diferentes tipos de solicitações de API para {% data variables.product.product_location %} estão sujeitos a diferentes limites de taxa.
diff --git a/translations/pt-BR/content/rest/projects/cards.md b/translations/pt-BR/content/rest/projects/cards.md
index d63a5f04a9..893d6413c5 100644
--- a/translations/pt-BR/content/rest/projects/cards.md
+++ b/translations/pt-BR/content/rest/projects/cards.md
@@ -1,8 +1,8 @@
 ---
-title: Cartões de quadro de projeto
+title: '{% data variables.product.prodname_project_v1_caps %} cards'
 shortTitle: Cartões
 allowTitleToDifferFromFilename: true
-intro: A API de cartões de quadro projeto permite que você crie e gerencie cartões em um quadro de projeto.
+intro: 'The {% data variables.product.prodname_project_v1 %} cards API lets you create and manage cards on a {% data variables.projects.projects_v1_board %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/rest/projects/collaborators.md b/translations/pt-BR/content/rest/projects/collaborators.md
index 94cfab763a..1f9ddf287a 100644
--- a/translations/pt-BR/content/rest/projects/collaborators.md
+++ b/translations/pt-BR/content/rest/projects/collaborators.md
@@ -1,8 +1,8 @@
 ---
-title: Colaboradores do quadro de projeto
+title: '{% data variables.product.prodname_project_v1_caps %} collaborators'
 shortTitle: Colaboradores
 allowTitleToDifferFromFilename: true
-intro: A API de colaboradores do quadro de projeto permite que você gerencie colaboradores em um quadro de projetos.
+intro: 'The {% data variables.product.prodname_project_v1 %} collaborators API lets you manage collaborators on a {% data variables.projects.projects_v1_board %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/rest/projects/columns.md b/translations/pt-BR/content/rest/projects/columns.md
index c27c911d0f..fabf2f3daf 100644
--- a/translations/pt-BR/content/rest/projects/columns.md
+++ b/translations/pt-BR/content/rest/projects/columns.md
@@ -1,8 +1,8 @@
 ---
-title: Colunas do quadro de projeto
+title: '{% data variables.product.prodname_project_v1_caps %} columns'
 shortTitle: Colunas
 allowTitleToDifferFromFilename: true
-intro: A API de colunas do quadro de projetos permite que você crie e gerencie colunas em um quadro de projeto.
+intro: 'The {% data variables.product.prodname_project_v1 %} columns API lets you create and manage columns on a {% data variables.projects.projects_v1_board %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/rest/projects/index.md b/translations/pt-BR/content/rest/projects/index.md
index b4d2534eea..7064fbb384 100644
--- a/translations/pt-BR/content/rest/projects/index.md
+++ b/translations/pt-BR/content/rest/projects/index.md
@@ -1,6 +1,6 @@
 ---
-title: Projetos
-intro: 'A API dos Projetos permite que você crie, liste, atualize, exclua e personalize projetos em um repositório.'
+title: '{% data variables.product.prodname_projects_v1_caps %}'
+intro: 'The {% data variables.product.prodname_projects_v1 %} API lets you create, list, update, delete and customize {% data variables.projects.projects_v1_boards %}.'
 redirect_from:
   - /v3/projects
   - /rest/reference/projects
@@ -12,6 +12,7 @@ versions:
 topics:
   - API
 miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
 children:
   - /projects
   - /cards
diff --git a/translations/pt-BR/content/rest/projects/projects.md b/translations/pt-BR/content/rest/projects/projects.md
index 535ddf0f2b..64cddc91ad 100644
--- a/translations/pt-BR/content/rest/projects/projects.md
+++ b/translations/pt-BR/content/rest/projects/projects.md
@@ -1,8 +1,8 @@
 ---
-title: Quadros de projeto
+title: '{% data variables.product.prodname_projects_v1_caps %}'
 shortTitle: Quadros
 allowTitleToDifferFromFilename: true
-intro: A API de quadros de projetos permite criar e gerenciar projetos em um repositório.
+intro: 'The {% data variables.product.prodname_projects_v1 %} API lets you create and manage {% data variables.projects.projects_v1_boards %} in a repository.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/search-github/searching-on-github/finding-files-on-github.md b/translations/pt-BR/content/search-github/searching-on-github/finding-files-on-github.md
index a38ae575b0..db96c2f487 100644
--- a/translations/pt-BR/content/search-github/searching-on-github/finding-files-on-github.md
+++ b/translations/pt-BR/content/search-github/searching-on-github/finding-files-on-github.md
@@ -18,16 +18,50 @@ topics:
 
 **Dicas:**
 
-- Os resultados do localizador de arquivos excluem alguns diretórios, como `build`, `log`, `tmp` e `vendor`. Para pesquisar arquivos dentro desses diretórios, use o código qualificador da pesquisa [`filename` (nome do arquivo)](/search-github/searching-on-github/searching-code#search-by-filename).
+- By default, file finder results exclude some directories like `build`, `log`, `tmp`, and `vendor`. To search for files in these directories, use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename).{% ifversion file-finder-exclusion-controls %} Alternatively, you can customize which directories are excluded by default [using a `.gitattributes` file](#customizing-excluded-files).{% endif %}
 - É possível também abrir o file finder (localizador de arquivos) digitando `t` no teclado. Para obter mais informações, consulte "[Atalhos de teclado](/articles/keyboard-shortcuts)".
 
 {% endtip %}
 
+## Using the file finder
+
 {% data reusables.repositories.navigate-to-repo %}
 2. Acima da lista de arquivos, clique em **Ir para o arquivo**. ![Botão Find file (Localizar arquivo)](/assets/images/help/search/find-file-button.png)
 3. No campo de pesquisa, digite o nome do arquivo que está procurando. ![Campo de pesquisa Find file (Localizar arquivo)](/assets/images/help/search/find-file-search-field.png)
 4. Na lista de resultados, clique no arquivo que você queria encontrar.
 
+{% ifversion file-finder-exclusion-controls %}
+
+## Customizing excluded files
+
+By default, file finder results do not include files in the following directories if they exist at your repository root:
+
+ - `.git`
+ - `.hg`
+ - `.sass-cache`
+ - `.svn`
+ - `build`
+ - `dot_git`
+ - `log`
+ - `tmp`
+ - `vendor`
+
+You can override these default exclusions using a `.gitattributes` file.
+
+To do this, create or update a file called `.gitattributes` in your repository root, setting the [`linguist-generated`](https://github.com/github/linguist/blob/master/docs/overrides.md) attribute to `false` for each directory that should be included in file finder results.
+
+For example, the following `.gitattributes` file would cause files in the `build/` directory to be available to the file finder:
+
+```
+build/** linguist-generated=false
+```
+
+Note that this override requires the use of the recursive glob pattern (`**`). For more information, see "[pattern format](https://git-scm.com/docs/gitignore#_pattern_format)" in the Git documentation. More complex overrides of subdirectories within excluded-by-default directories are not supported.
+
+{% endif %}
+
 ## Leia mais
 
-- "[Sobre a pesquisa no GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)"
+- "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)"{% ifversion file-finder-exclusion-controls %}
+- "[Customizing how changed files appear on GitHub](/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github)"
+- [`.gitattributes`](https://git-scm.com/docs/gitattributes) in the Git documentation{% endif %}
diff --git a/translations/pt-BR/data/features/actions-stable-actor-ids.yml b/translations/pt-BR/data/features/actions-stable-actor-ids.yml
new file mode 100644
index 0000000000..bbf260ceac
--- /dev/null
+++ b/translations/pt-BR/data/features/actions-stable-actor-ids.yml
@@ -0,0 +1,7 @@
+#Issue 7387
+#Differentiating triggering actor from executing actor
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7387'
diff --git a/translations/pt-BR/data/features/audit-data-retention-tab.yml b/translations/pt-BR/data/features/audit-data-retention-tab.yml
new file mode 100644
index 0000000000..c1c6be7943
--- /dev/null
+++ b/translations/pt-BR/data/features/audit-data-retention-tab.yml
@@ -0,0 +1,5 @@
+#Reference #5104
+#Documentation for the "Audit data retention" tab in the enterprise audit log
+versions:
+  ghes: '>=3.4'
+  ghae: 'issue-5104'
diff --git a/translations/pt-BR/data/features/dependency-review-action-licenses.yml b/translations/pt-BR/data/features/dependency-review-action-licenses.yml
new file mode 100644
index 0000000000..58c8a0c630
--- /dev/null
+++ b/translations/pt-BR/data/features/dependency-review-action-licenses.yml
@@ -0,0 +1,4 @@
+#Reference: Issue #7486 Configuring the dependency review action - [Public Beta] for GHES
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/pt-BR/data/features/enable-git-events.yml b/translations/pt-BR/data/features/enable-git-events.yml
new file mode 100644
index 0000000000..76a3230d97
--- /dev/null
+++ b/translations/pt-BR/data/features/enable-git-events.yml
@@ -0,0 +1,5 @@
+#Reference: #7283
+#Documentation for enabling Git events in the audit log
+versions:
+  ghes: '>=3.5'
+  ghae: 'issue-7283'
diff --git a/translations/pt-BR/data/features/file-finder-exclusion-controls.yml b/translations/pt-BR/data/features/file-finder-exclusion-controls.yml
new file mode 100644
index 0000000000..a61b769e48
--- /dev/null
+++ b/translations/pt-BR/data/features/file-finder-exclusion-controls.yml
@@ -0,0 +1,6 @@
+#Reference: Issue #7579 - Improved file finder exclusion controls
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7579'
diff --git a/translations/pt-BR/data/features/git-events-audit-log.yml b/translations/pt-BR/data/features/git-events-audit-log.yml
new file mode 100644
index 0000000000..5d56317040
--- /dev/null
+++ b/translations/pt-BR/data/features/git-events-audit-log.yml
@@ -0,0 +1,6 @@
+#Reference: #6724
+#Documentation for Git events in the audit log
+versions:
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6724'
diff --git a/translations/pt-BR/data/features/projects-v1.yml b/translations/pt-BR/data/features/projects-v1.yml
new file mode 100644
index 0000000000..0587e91d72
--- /dev/null
+++ b/translations/pt-BR/data/features/projects-v1.yml
@@ -0,0 +1,8 @@
+#Issue 6980
+#Projects (classic)
+#n.b. /managing-project-boards/copying-a-project-board.md retains ghec/fpt versioning.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
diff --git a/translations/pt-BR/data/features/projects-v2.yml b/translations/pt-BR/data/features/projects-v2.yml
new file mode 100644
index 0000000000..2c50587de8
--- /dev/null
+++ b/translations/pt-BR/data/features/projects-v2.yml
@@ -0,0 +1,6 @@
+#Issue 6980
+#ProjectV2 GA
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-6980'
diff --git a/translations/pt-BR/data/features/secret-scanning-push-protection-email.yml b/translations/pt-BR/data/features/secret-scanning-push-protection-email.yml
new file mode 100644
index 0000000000..4a3eb211b9
--- /dev/null
+++ b/translations/pt-BR/data/features/secret-scanning-push-protection-email.yml
@@ -0,0 +1,6 @@
+#Reference: #7511.
+#When developers bypass a block by push protection for a detected secret, administrators will receive an email notification of that bypass.
+versions:
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7511'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml
index cef99fc654..213cadcabf 100644
--- a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml
@@ -245,13 +245,13 @@ sections:
       heading: Eventos do Git no log de auditoria da empresa
       notes:
         - |
-          Os seguintes eventos relacionados ao Gits agora podem aparecer no log de auditorias corporativas. Se você habilitar o recurso e definir um período de retenção de log de auditoria, os novos eventos estarão disponíveis para pesquisa por meio da interface do usuário e API, ou exportação via JSON ou CSV.
+          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.
 
           - `git.clone`
           - `git.fetch`
-          - `git. ush`
+          - `git.push`
 
-          Devido ao grande número de eventos do Git registrados, recomendamos que você monitore o armazenamento de arquivos da sua instância e revise as configurações de alerta relacionadas. Para obter mais informações, consulte "[Eventos do log de auditoria para a sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)" e "[Monitorando o armazenamento](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)."
+          Due 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 "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise#managing-git-events-in-the-audit-log)."
     - 
       heading: Melhorias nos CODEOWNERS
       notes:
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0.yml
index 4937a0ad05..5f9d8dbd2e 100644
--- a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0.yml
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0.yml
@@ -237,13 +237,13 @@ sections:
       heading: Eventos do Git no log de auditoria da empresa
       notes:
         - |
-          Os seguintes eventos relacionados ao Gits agora podem aparecer no log de auditorias corporativas. Se você habilitar o recurso e definir um período de retenção de log de auditoria, os novos eventos estarão disponíveis para pesquisa por meio da interface do usuário e API, ou exportação via JSON ou CSV.
+          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.
 
           - `git.clone`
           - `git.fetch`
-          - `git. ush`
+          - `git.push`
 
-          Devido ao grande número de eventos do Git registrados, recomendamos que você monitore o armazenamento de arquivos da sua instância e revise as configurações de alerta relacionadas. Para obter mais informações, consulte "[Eventos do log de auditoria para a sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)" e "[Monitorando o armazenamento](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)."
+          Due 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 "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise#managing-git-events-in-the-audit-log)."
     - 
       heading: Melhorias nos CODEOWNERS
       notes:
diff --git a/translations/pt-BR/data/reusables/actions/actions-use-sha-pinning-comment.md b/translations/pt-BR/data/reusables/actions/actions-use-sha-pinning-comment.md
new file mode 100644
index 0000000000..b3a3c95421
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/actions-use-sha-pinning-comment.md
@@ -0,0 +1,3 @@
+# GitHub recommends pinning actions to a commit SHA.
+# To get a newer version, you will need to update the SHA.
+# You can also reference a tag or branch, but the action may change without warning.
diff --git a/translations/pt-BR/data/reusables/audit_log/audit-data-retention-tab.md b/translations/pt-BR/data/reusables/audit_log/audit-data-retention-tab.md
new file mode 100644
index 0000000000..2f1850c4ef
--- /dev/null
+++ b/translations/pt-BR/data/reusables/audit_log/audit-data-retention-tab.md
@@ -0,0 +1,3 @@
+1. Under "Audit log", click **Audit Data Retention**.
+
+   ![Screenshot of the "Audit Data Retention" tab](/assets/images/help/enterprises/audit-data-retention-tab.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md b/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md
index 4c95242501..f07adb812e 100644
--- a/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md
+++ b/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md
@@ -50,7 +50,7 @@
 {%- ifversion ghae %}
 | `external_group` | Contains activities related to Okta groups. | `external_identity` | Contains activities related to a user in an Okta group.
 {%- endif %}
-| `gist` | Contains activities related to Gists. | `git` | Contains activities related to Git events. | `hook` | Contains activities related to webhooks. | `integration` | Contains activities related to integrations in an account. | `integration_installation` | Contains activities related to integrations installed in an account. | `integration_installation_request`  | Contains activities related to organization member requests for owners to approve integrations for use in the organization.
+| `gist` | Contains activities related to Gists. | `hook` | Contains activities related to webhooks. | `integration` | Contains activities related to integrations in an account. | `integration_installation` | Contains activities related to integrations installed in an account. | `integration_installation_request`  | Contains activities related to organization member requests for owners to approve integrations for use in the organization.
 {%- ifversion ghec or ghae %}
 | `ip_allow_list`   | Contains activities related to enabling or disabling the IP allow list for an organization. | `ip_allow_list_entry`   | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.
 {%- endif %}
diff --git a/translations/pt-BR/data/reusables/audit_log/git-events-not-in-search-results.md b/translations/pt-BR/data/reusables/audit_log/git-events-not-in-search-results.md
new file mode 100644
index 0000000000..7f54d1e816
--- /dev/null
+++ b/translations/pt-BR/data/reusables/audit_log/git-events-not-in-search-results.md
@@ -0,0 +1,7 @@
+{% ifversion git-events-audit-log %}
+{% note %}
+
+**Note:** Git events are not included in search results.
+
+{% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/audit_log/retention-periods.md b/translations/pt-BR/data/reusables/audit_log/retention-periods.md
index dbed08d376..5d47a7424c 100644
--- a/translations/pt-BR/data/reusables/audit_log/retention-periods.md
+++ b/translations/pt-BR/data/reusables/audit_log/retention-periods.md
@@ -1,3 +1,3 @@
-The audit log lists events triggered by activities that affect your enterprise{% ifversion not ghec %}. Audit logs for {% data variables.product.product_name %} are retained indefinitely.{% else %} within the current month and up to the previous six months. The audit log retains Git events for seven days.{% endif %}
+The audit log lists events triggered by activities that affect your enterprise{% ifversion not ghec %}. Audit logs for {% data variables.product.product_name %} are retained indefinitely{% ifversion audit-data-retention-tab %}, unless an enterprise owner configured a different retention period. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise)."{% else %}.{% endif %}{% else %} within the current month and up to the previous six months. The audit log retains Git events for seven days.{% endif %}
 
 {% data reusables.audit_log.only-three-months-displayed %}
diff --git a/translations/pt-BR/data/reusables/copilot/dotcom-settings.md b/translations/pt-BR/data/reusables/copilot/dotcom-settings.md
index 80318ab8a0..6e28a2b52c 100644
--- a/translations/pt-BR/data/reusables/copilot/dotcom-settings.md
+++ b/translations/pt-BR/data/reusables/copilot/dotcom-settings.md
@@ -2,18 +2,24 @@
 
 Once you have an active {% data variables.product.prodname_copilot %} trial or subscription, you can adjust {% data variables.product.prodname_copilot %} settings for your personal account on {% data variables.product.prodname_dotcom %} in the [{% data variables.product.prodname_copilot %} settings](https://github.com/settings/copilot). The settings apply anywhere that you use {% data variables.product.prodname_copilot %}. You can configure the suggestions that {% data variables.product.prodname_copilot %} offers and how {% data variables.product.company_short %} uses your telemetry data.
 
-### Enabling or disabling duplication detection
+## Enabling or disabling duplication detection
+
+{% data variables.product.prodname_copilot %} includes a filter which detects code suggestions matching public code on {% data variables.product.prodname_dotcom %}. You can choose to enable or disable the filter. When the filter is enabled, {% data variables.product.prodname_copilot %} checks code suggestions with their surrounding code of about 150 characters against public code on {% data variables.product.prodname_dotcom %}. If there is a match or near match, the suggestion will not be shown to you.
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.copilot-settings %}
 1. Under **Suggestions matching public code**, select the dropdown menu, then click **Allow** to allow suggestions matching public code, or **Block** to block suggestions matching public code. ![Screenshot of duplication detection option](/assets/images/help/copilot/duplication-detection.png)
 {% data reusables.copilot.save-settings %}
 
-### Enabling or disabling telemetry
+## Enabling or disabling telemetry
 
-You can configure how {% data variables.product.prodname_copilot %} uses your data. For more information about data that {% data variables.product.prodname_copilot %} may collect depending on your telemetry settings, see "[{% data variables.product.company_short %} Terms for Additional Products and Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)."
+You can choose whether your code snippets are collected and retained by GitHub and further processed and shared with Microsoft and OpenAI by adjusting your user settings. For more information about data that {% data variables.product.prodname_copilot %} may collect depending on your telemetry settings, see "[{% data variables.product.company_short %} Terms for Additional Products and Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)" and the [{% data variables.product.prodname_copilot %} privacy FAQ](https://github.com/features/copilot/#faq-privacy).
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.copilot-settings %}
 1. To allow or prevent {% data variables.product.prodname_dotcom %} using your telemetry data, select or deselect **Allow {% data variables.product.prodname_dotcom %} to use my code snippets for product improvements**. ![Screenshot of telemetry option](/assets/images/help/copilot/telemetry-option.png)
 {% data reusables.copilot.save-settings %}
+
+## Leia mais
+
+- [{% data variables.product.prodname_copilot %} FAQ](https://github.com/features/copilot/#faq)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/dependency-review/action-enterprise.md b/translations/pt-BR/data/reusables/dependency-review/action-enterprise.md
new file mode 100644
index 0000000000..93908578c8
--- /dev/null
+++ b/translations/pt-BR/data/reusables/dependency-review/action-enterprise.md
@@ -0,0 +1,3 @@
+{% ifversion ghes or ghae %}
+Enterprise owners and people with admin access to a repository can add the {% data variables.product.prodname_dependency_review_action %} to their enterprise and repository, respectively.
+{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/education/about-github-community-exchange-intro.md b/translations/pt-BR/data/reusables/education/about-github-community-exchange-intro.md
new file mode 100644
index 0000000000..9491a48f6c
--- /dev/null
+++ b/translations/pt-BR/data/reusables/education/about-github-community-exchange-intro.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_community_exchange %} é uma comunidade estudantil dentro do portal de {% data variables.product.prodname_global_campus %}. Como estudante, é um lugar onde você pode obter exposição para o seu projeto e descobrir outros repositórios estudantis que precisam de colaboradores e mantenedores.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/education/about-github-education-link.md b/translations/pt-BR/data/reusables/education/about-github-education-link.md
index d1993bcbde..33ac496a6a 100644
--- a/translations/pt-BR/data/reusables/education/about-github-education-link.md
+++ b/translations/pt-BR/data/reusables/education/about-github-education-link.md
@@ -1,3 +1,3 @@
-As a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_global_campus %}. {% data variables.product.prodname_global_campus %} is a portal that allows the GitHub Education Community to access their education benefits—all in one place! The {% data variables.product.prodname_global_campus %} portal includes access to {% data variables.product.prodname_education_community_with_url %}, industry tools used by professional developers, events, [Campus TV](https://www.twitch.tv/githubeducation) content, {% data variables.product.prodname_classroom_with_url %}, and other exclusive features to help students and teachers shape the next generation of software development.
+As a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_global_campus %}. {% data variables.product.prodname_global_campus %} is a portal that allows the GitHub Education Community to access their education benefits—all in one place! The {% data variables.product.prodname_global_campus %} portal includes access to {% data variables.product.prodname_education_community_with_url %}, industry tools used by professional developers, events, [Campus TV](https://www.twitch.tv/githubeducation) content, {% data variables.product.prodname_classroom_with_url %}, {% data variables.product.prodname_community_exchange %}, and other exclusive features to help students and teachers shape the next generation of software development.
 
 Antes de solicitar um desconto individual, verifique se sua comunidade de estudos já não é nossa parceira como uma escola {% data variables.product.prodname_campus_program %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)."
diff --git a/translations/pt-BR/data/reusables/education/access-github-community-exchange.md b/translations/pt-BR/data/reusables/education/access-github-community-exchange.md
new file mode 100644
index 0000000000..50130426fb
--- /dev/null
+++ b/translations/pt-BR/data/reusables/education/access-github-community-exchange.md
@@ -0,0 +1,7 @@
+Para acessar {% data variables.product.prodname_community_exchange %}, acesse seu painel de {% data variables.product.prodname_global_campus %} em https://education.github.com.
+
+Se você é um aluno ou integrante do corpo docente de uma instituição de ensino credenciada, você pode solicitar benefícios de {% data variables.product.prodname_education %}, o que inclui acesso a {% data variables.product.prodname_community_exchange %} dentro de {% data variables.product.prodname_global_campus %}.
+
+- Se você é um estudante e ainda não participou de {% data variables.product.prodname_education %} , inscreva-se usando o [formulário de inscrição do aluno](https://education.github.com/discount_requests/student_application). Para obter mais informações, consulte "[Sobre o GitHub Education para alunos](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students)."
+
+- Se você é um educador e ainda não se participou de {% data variables.product.prodname_education %}, inscreva-se usando o [formulário de candidatura do professor](https://education.github.com/discount_requests/teacher_application). Para obter mais informações, consulte "[Sobre o GitHub Education para educadores](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount)".
diff --git a/translations/pt-BR/data/reusables/gated-features/code-scanning.md b/translations/pt-BR/data/reusables/gated-features/code-scanning.md
index 47b9cefc47..247c6f564a 100644
--- a/translations/pt-BR/data/reusables/gated-features/code-scanning.md
+++ b/translations/pt-BR/data/reusables/gated-features/code-scanning.md
@@ -1,7 +1,13 @@
-{% ifversion fpt %} {% data variables.product.prodname_code_scanning_capc %} is available for all public repositories. {% data variables.product.prodname_code_scanning_capc %} is also available in private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}.
-{%- elsif ghec %} {% data variables.product.prodname_code_scanning_capc %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
-{%- elsif ghes %}{% data variables.product.prodname_code_scanning_capc %} está disponível para repositórios de organizações onde {% data variables.product.prodname_GH_advanced_security %} está habilitado.
+{%- ifversion fpt %}
+{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_code_scanning_capc %} is also available for private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghec %}
+{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. To use {% data variables.product.prodname_code_scanning %} in a private repository owned by an organization, you must have a license for {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghes %}
+{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories in {% data variables.product.product_name %}. This feature requires a license for {% data variables.product.prodname_GH_advanced_security %}.
+
 {%- elsif ghae %}
-{% data variables.product.prodname_code_scanning_capc %} está disponível como parte de {% data variables.product.prodname_GH_advanced_security %}, que é grátis durante a versão beta.
-{%- else %}
-{% data variables.product.prodname_code_scanning_capc %} está disponível se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
+{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories in {% data variables.product.product_name %}. This is a {% data variables.product.prodname_GH_advanced_security %} feature (free during the beta release).
+
+{%- endif %} For more information, see "[GitHub's products](/articles/githubs-products)."
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/gated-features/copilot.md b/translations/pt-BR/data/reusables/gated-features/copilot.md
index 9665d4356e..8f74fd9827 100644
--- a/translations/pt-BR/data/reusables/gated-features/copilot.md
+++ b/translations/pt-BR/data/reusables/gated-features/copilot.md
@@ -1 +1 @@
-{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_copilot %} is free to use for verified students and open source maintainers. If you are not a student or open source maintainer, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)".
+{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_copilot %} is free to use for verified students and maintainers of popular open source projects. If you are not a student or maintainer of a popular open source project, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)".
diff --git a/translations/pt-BR/data/reusables/gated-features/historical-insights-for-projects.md b/translations/pt-BR/data/reusables/gated-features/historical-insights-for-projects.md
new file mode 100644
index 0000000000..07502e255f
--- /dev/null
+++ b/translations/pt-BR/data/reusables/gated-features/historical-insights-for-projects.md
@@ -0,0 +1 @@
+Historical charts are available with {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} for organizations. You can save unlimited charts in private projects with {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} for organizations and {% data variables.product.prodname_pro %} for users. Users and organizations using a public project can also save unlimited charts. Users and organizations using {% data variables.product.prodname_free_team %} or a legacy plan can save two charts in private projects.  {% data reusables.gated-features.more-info %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/package_registry/publish-docker-image.md b/translations/pt-BR/data/reusables/package_registry/publish-docker-image.md
index be03c6a689..a0a12f644b 100644
--- a/translations/pt-BR/data/reusables/package_registry/publish-docker-image.md
+++ b/translations/pt-BR/data/reusables/package_registry/publish-docker-image.md
@@ -1,6 +1,8 @@
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
 name: Create and publish a Docker image
 
 on:
diff --git a/translations/pt-BR/data/reusables/project-management/automate-project-board-permissions.md b/translations/pt-BR/data/reusables/project-management/automate-project-board-permissions.md
index a6b556b4a1..b6de4865ba 100644
--- a/translations/pt-BR/data/reusables/project-management/automate-project-board-permissions.md
+++ b/translations/pt-BR/data/reusables/project-management/automate-project-board-permissions.md
@@ -1 +1 @@
-Para configurar fluxos de trabalho automáticos para um quadro de projetos de repositório, você deve ter acesso de gravação ao repositório. Os proprietários e integrantes da organização podem configurar fluxos de trabalho automáticos em um quadro de projetos para toda a organização.
+To set up automatic workflows for a repository {% data variables.projects.projects_v1_board %}, you must have write access to the repository. Organization owners and members can configure automatic workflows on an organization-wide {% data variables.projects.projects_v1_board %}.
diff --git a/translations/pt-BR/data/reusables/project-management/cascading-permissions.md b/translations/pt-BR/data/reusables/project-management/cascading-permissions.md
index da9799be55..d45274e43c 100644
--- a/translations/pt-BR/data/reusables/project-management/cascading-permissions.md
+++ b/translations/pt-BR/data/reusables/project-management/cascading-permissions.md
@@ -1 +1 @@
-Se uma pessoa tiver várias vias de acesso a um quadro de projeto da organização (individualmente, por uma equipe ou como integrante de uma organização), o nível de permissão mais alto do quadro de projeto substituirá os níveis mais baixos de permissão.
+If a person has multiple avenues of access to an organization {% data variables.projects.projects_v1_board %} (individually, through a team, or as an organization member), the highest {% data variables.projects.projects_v1_board %} permission level overrides lower permission levels.
diff --git a/translations/pt-BR/data/reusables/project-management/click-menu.md b/translations/pt-BR/data/reusables/project-management/click-menu.md
index 3390ad498e..e95bfdceb8 100644
--- a/translations/pt-BR/data/reusables/project-management/click-menu.md
+++ b/translations/pt-BR/data/reusables/project-management/click-menu.md
@@ -1 +1 @@
-1. No lado superior direito do quadro de projeto, clique em {% octicon "three-bars" aria-label="The three-bars octicon" %} **Menu**.
+1. On the top-right side of the {% data variables.projects.projects_v1_board %}, click {% octicon "three-bars" aria-label="The three-bars octicon" %} **Menu**.
diff --git a/translations/pt-BR/data/reusables/project-management/copy-project-boards.md b/translations/pt-BR/data/reusables/project-management/copy-project-boards.md
index 33fb50e653..95620daeee 100644
--- a/translations/pt-BR/data/reusables/project-management/copy-project-boards.md
+++ b/translations/pt-BR/data/reusables/project-management/copy-project-boards.md
@@ -1,3 +1,4 @@
 {% ifversion fpt or ghec %}
-Você também pode copiar um quadro de projeto para reutilizar suas personalizações para projetos similares. Para obter mais informações, consulte "[Copiar um quadro de projeto](/articles/copying-a-project-board)".
+You can also copy a
+{% data variables.projects.projects_v1_board %} to reuse its customizations for similar projects. For more information, see "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)."
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/project-management/edit-in-project.md b/translations/pt-BR/data/reusables/project-management/edit-in-project.md
index 7212016551..112ef81842 100644
--- a/translations/pt-BR/data/reusables/project-management/edit-in-project.md
+++ b/translations/pt-BR/data/reusables/project-management/edit-in-project.md
@@ -1 +1 @@
-É possível visualizar e fazer pequenas edições em problemas e solicitações pull em seu quadro de projeto clicando no título do problema ou da solicitação pull.
+You can view and make lightweight edits to issues and pull requests within your {% data variables.projects.projects_v1_board %} by clicking on the issue or pull request's title.
diff --git a/translations/pt-BR/data/reusables/project-management/link-repos-to-project-board.md b/translations/pt-BR/data/reusables/project-management/link-repos-to-project-board.md
index d638004aa4..6bce91fd71 100644
--- a/translations/pt-BR/data/reusables/project-management/link-repos-to-project-board.md
+++ b/translations/pt-BR/data/reusables/project-management/link-repos-to-project-board.md
@@ -1 +1 @@
-Você pode vincular até vinte e cinco repositórios à sua organização ou ao quadro de projetos pertencente ao usuário. Vincular repositórios facilita a adição de problemas e pull requests desses repositórios ao seu quadro de projeto usando **{% octicon "plus" aria-label="The Plus icon" %} Cartões de adição de ** ou na barra lateral de problemas ou pull requests.
+You can link up to twenty-five repositories to your organization or user-owned {% data variables.projects.projects_v1_board %}. Linking repositories makes it easier to add issues and pull requests from those repositories to your {% data variables.projects.projects_v1_board %} using **{% octicon "plus" aria-label="The Plus icon" %} Add cards** or from the issue or pull requests sidebar.
diff --git a/translations/pt-BR/data/reusables/project-management/project-board-permissions.md b/translations/pt-BR/data/reusables/project-management/project-board-permissions.md
index e1713ff880..cbb4e53a66 100644
--- a/translations/pt-BR/data/reusables/project-management/project-board-permissions.md
+++ b/translations/pt-BR/data/reusables/project-management/project-board-permissions.md
@@ -1,3 +1,3 @@
-- **Leitura**, que dá permissão para pessoas visualizarem um quadro de projeto.
-- **Gravação**, que dá permissão às pessoas para visualizar um quadro de projeto, vincular repositórios a um quadro de projeto e interagir com um quadro de projeto. Para obter mais informações, consulte "[Vincular um repositório a um quadro de projeto](/articles/linking-a-repository-to-a-project-board)".
-- **Administrador**, que dá permissão às pessoas para visualizar um quadro de projeto, interagir com um quadro de projeto, gerenciar as configurações do quadro de projeto e gerenciar o acesso de outras pessoas ao quadro de projetos.
+- **Read**, which gives people permission to view a {% data variables.projects.projects_v1_board %}.
+- **Write**, which gives people permission to view a {% data variables.projects.projects_v1_board %}, link repositories to a {% data variables.projects.projects_v1_board %}, and interact with a {% data variables.projects.projects_v1_board %}. For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)."
+- **Admin**, which gives people permission to view a {% data variables.projects.projects_v1_board %}, interact with a {% data variables.projects.projects_v1_board %}, manage {% data variables.projects.projects_v1_board %} settings, and manage other people's access to the {% data variables.projects.projects_v1_board %}.
diff --git a/translations/pt-BR/data/reusables/project-management/project-board-visibility.md b/translations/pt-BR/data/reusables/project-management/project-board-visibility.md
index 7fb24ae2e5..5021c82faf 100644
--- a/translations/pt-BR/data/reusables/project-management/project-board-visibility.md
+++ b/translations/pt-BR/data/reusables/project-management/project-board-visibility.md
@@ -1 +1 @@
-By default, user-owned and organization-wide project boards are private and only visible to people with read, write, or admin permissions to the project board. {% ifversion ghae %}An internal{% else %}A public{% endif %} project board is visible to {% ifversion ghae %}anyone with access to your enterprise on {% data variables.product.prodname_ghe_managed %}{% elsif ghes %}anyone with access to your {% data variables.product.prodname_ghe_server %} instance{% else %}anyone with the project board's URL{% endif %}. Repository-level project boards share the visibility of their repository. That is, a private repository will have a private board, and this visibility cannot be changed.
+By default, user-owned and organization-wide {% data variables.projects.projects_v1_boards %} are private and only visible to people with read, write, or admin permissions to the {% data variables.projects.projects_v1_board %}. {% ifversion ghae %}An internal{% else %}A public{% endif %} {% data variables.projects.projects_v1_board %} is visible to {% ifversion ghae %}any with access to your enterprise{% else %}anyone{% endif %} with the {% data variables.projects.projects_v1_board %}'s URL. Repository-level {% data variables.projects.projects_v1_boards %} share the visibility of their repository. That is, a private repository will have a private project, and this visibility cannot be changed.
diff --git a/translations/pt-BR/data/reusables/project-management/project-progress-locations.md b/translations/pt-BR/data/reusables/project-management/project-progress-locations.md
index cc120596cd..1df5983464 100644
--- a/translations/pt-BR/data/reusables/project-management/project-progress-locations.md
+++ b/translations/pt-BR/data/reusables/project-management/project-progress-locations.md
@@ -1 +1 @@
-Se o rastreamento de progresso estiver habilitado, uma barra de progresso aparecerá acima do quadro de projetos, na página de listagem do projeto, na barra lateral de questões e em referências ao projeto em outros quadros de projetos.
+If progress tracking is enabled, a progress bar appears above the {% data variables.projects.projects_v1_board %}, on the project listing page, in the issue sidebar, and in references to the project on other {% data variables.projects.projects_v1_boards %}.
diff --git a/translations/pt-BR/data/reusables/project-management/resync-automation.md b/translations/pt-BR/data/reusables/project-management/resync-automation.md
index 449801bdaa..25880d2441 100644
--- a/translations/pt-BR/data/reusables/project-management/resync-automation.md
+++ b/translations/pt-BR/data/reusables/project-management/resync-automation.md
@@ -1 +1 @@
-Ao fechar um quadro de projetos, qualquer automação de fluxo de trabalho configurada no quadro do projeto será pausada. Se você reabrir um quadro de projeto, existirá a opção de sincronizar a automação, o que atualiza a posição dos cartões no quadro de acordo com as configurações de automação definidas para o quadro. Para obter mais informações, consulte "[Reabrir um quadro de projeto fechado](/articles/reopening-a-closed-project-board)" ou "[Fechar um quadro de projeto](/articles/closing-a-project-board)".
+When you close a {% data variables.projects.projects_v1_board %}, any workflow automation configured for the {% data variables.projects.projects_v1_board %} will pause. If you reopen a {% data variables.projects.projects_v1_board %}, you have the option to sync automation, which updates the position of the cards on the board according to the automation settings configured for the project. For more information, see "[Reopening a closed {% data variables.product.prodname_project_v1 %}](/articles/reopening-a-closed-project-board)" or "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)."
diff --git a/translations/pt-BR/data/reusables/project-management/select-project.md b/translations/pt-BR/data/reusables/project-management/select-project.md
index bbfe91a830..b7e837db6a 100644
--- a/translations/pt-BR/data/reusables/project-management/select-project.md
+++ b/translations/pt-BR/data/reusables/project-management/select-project.md
@@ -1 +1 @@
-1. Na lista de projetos, clique no nome do quadro de projeto. ![Selecione o projeto](/assets/images/help/projects/select-project.png)
+1. In the projects list, click the name of the {% data variables.projects.projects_v1_board %}. ![Selecione o projeto](/assets/images/help/projects/select-project.png)
diff --git a/translations/pt-BR/data/reusables/project-management/use-automated-template.md b/translations/pt-BR/data/reusables/project-management/use-automated-template.md
index 43b88d1aa0..49e6e9ca08 100644
--- a/translations/pt-BR/data/reusables/project-management/use-automated-template.md
+++ b/translations/pt-BR/data/reusables/project-management/use-automated-template.md
@@ -1 +1 @@
-Você pode usar um modelo de quadro de projeto para criar um quadro de projeto com automação já configurada. Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards#templates-for-project-boards)".
+You can use a {% data variables.projects.projects_v1_board %} template to create a {% data variables.projects.projects_v1_board %} with automation already configured. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards#templates-for-project-boards)".
diff --git a/translations/pt-BR/data/reusables/projects/about-workflows.md b/translations/pt-BR/data/reusables/projects/about-workflows.md
index 5c78c53bc5..d2472004a5 100644
--- a/translations/pt-BR/data/reusables/projects/about-workflows.md
+++ b/translations/pt-BR/data/reusables/projects/about-workflows.md
@@ -1,3 +1,3 @@
-Projects (beta) includes built-in workflows that you can use to update the **Status** of items based on certain events. For example, you can automatically set the status to **Todo** when an item is added to your project or set the status to **Done** when an issue is closed.
+{% data variables.product.prodname_projects_v2 %} includes built-in workflows that you can use to update the **Status** of items based on certain events. For example, you can automatically set the status to **Todo** when an item is added to your project or set the status to **Done** when an issue is closed.
 
 When your project initializes, two workflows are enabled by default: When issues or pull requests in your project are closed, their status is set to **Done**, and when pull requests in your project are merged, their status is set to **Done**.
diff --git a/translations/pt-BR/data/reusables/projects/access-insights.md b/translations/pt-BR/data/reusables/projects/access-insights.md
index baa180aa23..39a1d5d62c 100644
--- a/translations/pt-BR/data/reusables/projects/access-insights.md
+++ b/translations/pt-BR/data/reusables/projects/access-insights.md
@@ -1,8 +1,2 @@
 1. Navigate to your project.
-2. In the top-right, to access insights, click {% octicon "graph" aria-label="the graph icon" %}.
-
-    {% note %}
-
-   **Note:** This feature is currently in a private preview and only available for some organizations. If the {% octicon "graph" aria-label="the graph icon" %} icon is not displayed in your project, insights is not yet enabled for your organization.
-
-   {% endnote %} 
+2. In the top-right, to access insights, click {% octicon "graph" aria-label="the graph icon" %}. ![Screenshot showing the insights icon](/assets/images/help/projects-v2/insights-button.png)
diff --git a/translations/pt-BR/data/reusables/projects/add-draft-issue.md b/translations/pt-BR/data/reusables/projects/add-draft-issue.md
new file mode 100644
index 0000000000..696a0e3615
--- /dev/null
+++ b/translations/pt-BR/data/reusables/projects/add-draft-issue.md
@@ -0,0 +1,3 @@
+{% data reusables.projects.add-item-bottom-row %}
+1. Digite sua ideia e, em seguida, pressione **Enter**. ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-draft-issue.png)
+1. Para adicionar texto, clique no título do problema do rascunho. Na caixa de entrada do markdown que será exibida, digite o texto para o texto do problema do rascunho e clique em **Salvar**.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/projects/add-item-bottom-row.md b/translations/pt-BR/data/reusables/projects/add-item-bottom-row.md
new file mode 100644
index 0000000000..055f3f35c0
--- /dev/null
+++ b/translations/pt-BR/data/reusables/projects/add-item-bottom-row.md
@@ -0,0 +1 @@
+1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}. ![Screenshot showing the bottom row to add an item](/assets/images/help/projects-v2/add-item.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/projects/add-item-via-paste.md b/translations/pt-BR/data/reusables/projects/add-item-via-paste.md
new file mode 100644
index 0000000000..f0ad9645a0
--- /dev/null
+++ b/translations/pt-BR/data/reusables/projects/add-item-via-paste.md
@@ -0,0 +1,3 @@
+{% data reusables.projects.add-item-bottom-row %}
+1. Paste the URL of the issue or pull request. ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/paste-url-to-add.png)
+3. To add the issue or pull request, press <kbd>Return</kbd>.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/projects/bulk-add.md b/translations/pt-BR/data/reusables/projects/bulk-add.md
new file mode 100644
index 0000000000..b4134a373f
--- /dev/null
+++ b/translations/pt-BR/data/reusables/projects/bulk-add.md
@@ -0,0 +1,3 @@
+1. Optionally, to change the repository, click the dropdown and select a repository. You can also search for specific issues and pull requests. ![Screenshot showing repository dropdown](/assets/images/help/projects-v2/add-bulk-select-repo.png)
+1. Select the issues and pull requests you want to add. ![Screenshot showing selecting issues and pull requests to add](/assets/images/help/projects-v2/add-bulk-select-issues.png)
+1. Click **Add selected items**. ![Screenshot showing "add selected items" button](/assets/images/help/projects-v2/add-bulk-save.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/projects/create-project.md b/translations/pt-BR/data/reusables/projects/create-project.md
index fb5a590584..a50d69bd52 100644
--- a/translations/pt-BR/data/reusables/projects/create-project.md
+++ b/translations/pt-BR/data/reusables/projects/create-project.md
@@ -1,8 +1,7 @@
-1. Em {% data variables.product.prodname_dotcom %}, acesse a página principal da sua organização.
-1. Clique em {% octicon "table" aria-label="The project icon" %} **Projetos**.
-1. Selecione o menu suspenso **Novo projeto** e clique em **Novo projeto (Beta)**.
-
-   ![Novo projeto](/assets/images/help/issues/new_project_beta.png)
-1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**.
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+1. No nome da sua organização, clique em {% octicon "table" aria-label="The project icon" %} **Projects** (Projetos). ![Screenshot showing the 'Projects' tab](/assets/images/help/projects-v2/tab-projects.png)
+1. Click **New project**. ![Screenshot showing New project button](/assets/images/help/projects-v2/new-project-button.png)
+1. When prompted to select a template, click a template or, to start with an empty project, click **Table** or **Board**. Then, click **Create**.
 
    ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png)
diff --git a/translations/pt-BR/data/reusables/projects/create-user-project.md b/translations/pt-BR/data/reusables/projects/create-user-project.md
index 36e57c46c9..9f2a95f851 100644
--- a/translations/pt-BR/data/reusables/projects/create-user-project.md
+++ b/translations/pt-BR/data/reusables/projects/create-user-project.md
@@ -1,7 +1,6 @@
-1. On any {% data variables.product.product_name %} page, click on your avatar, then select **Your projects**.
-1. Selecione o menu suspenso **Novo projeto** e clique em **Novo projeto (Beta)**.
-
-   ![Novo projeto](/assets/images/help/issues/new_project_beta.png)
-1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**.
+{% data reusables.profile.access_profile %}
+1. On your profile, click {% octicon "table" aria-label="The project icon" %} **Projects**. ![Screenshot showing the 'Projects' tab](/assets/images/help/projects-v2/tab-projects.png)
+1. Click **New project**. ![Novo projeto](/assets/images/help/projects-v2/new-project-button.png)
+1. When prompted to select a template, click a template or, to start with an empty project, click **Table** or **Board**. Then, click **Create**.
 
    ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png)
diff --git a/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md b/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md
index 92bb137381..109e25e0bb 100644
--- a/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md
+++ b/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md
@@ -1,7 +1,7 @@
 1. Navigate to your project.
-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. Under **Default workflows**, click on the workflow that you want to edit.
-1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on.
-1. Next to **Set**, choose the value that you want to set the status to.
-1. If the workflow is disabled, click the toggle next to **Disabled** to enable the workflow.
+1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png)
+1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. ![Screenshot showing the 'Workflows' menu item](/assets/images/help/projects-v2/workflows-menu-item.png)
+1. Under **Default workflows**, click on the workflow that you want to edit. ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png)
+1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on. ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png)
+1. Next to **Set**, choose the value that you want to set the status to. ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png)
+1. If the workflow is disabled, click the toggle next to **Disabled** to enable the workflow. ![Screenshot showing the "enable" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png)
diff --git a/translations/pt-BR/data/reusables/projects/migrate-project-steps.md b/translations/pt-BR/data/reusables/projects/migrate-project-steps.md
index 576572edb9..c6cc379d89 100644
--- a/translations/pt-BR/data/reusables/projects/migrate-project-steps.md
+++ b/translations/pt-BR/data/reusables/projects/migrate-project-steps.md
@@ -1,4 +1,4 @@
 1. Next to the project you want to migrate, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
-1. In the menu, click **Migrate to beta**. ![Screenshot showing migrate to beta option](/assets/images/help/issues/migrate-to-beta.png)
-1. In the the popup, select what you want to happen to the project after it is migrated. We recommend selecting "Close the old project" so it's clear which project is in use. ![Screenshot showing migrate to beta option](/assets/images/help/issues/migrate-option.png)
-1. In the bottom right of the popup, click **Start migration**. ![Screenshot showing migrate to beta option](/assets/images/help/issues/migrate-start.png)
+1. In the menu, click **Migrate**. ![Screenshot showing migrate option](/assets/images/help/issues/migrate-menu-item.png)
+1. In the the popup, select what you want to happen to the project after it is migrated. We recommend selecting "Close the old project" so it's clear which project is in use. ![Screenshot showing migrate modal](/assets/images/help/issues/migrate-option.png)
+1. In the bottom right of the popup, click **Start migration**. ![Screenshot showing start migration button](/assets/images/help/issues/migrate-start.png)
diff --git a/translations/pt-BR/data/reusables/projects/new-field.md b/translations/pt-BR/data/reusables/projects/new-field.md
new file mode 100644
index 0000000000..05ac80c961
--- /dev/null
+++ b/translations/pt-BR/data/reusables/projects/new-field.md
@@ -0,0 +1,3 @@
+1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}. ![Screenshot showing new field button](/assets/images/help/projects-v2/new-field-button.png)
+1. Clique em **Novo campo**. ![Screenshot showing new field menu item](/assets/images/help/projects-v2/new-field-menu-item.png)
+1. Type the name of your new field. ![Screenshot showing the field name](/assets/images/help/projects-v2/new-field-name.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/projects/new-view.md b/translations/pt-BR/data/reusables/projects/new-view.md
new file mode 100644
index 0000000000..6befea1d5f
--- /dev/null
+++ b/translations/pt-BR/data/reusables/projects/new-view.md
@@ -0,0 +1 @@
+1. To the right of your existing views, click **New view** ![Screenshot showing the column field menu](/assets/images/help/projects-v2/new-view.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/projects/open-item-menu.md b/translations/pt-BR/data/reusables/projects/open-item-menu.md
new file mode 100644
index 0000000000..5c9c7fc258
--- /dev/null
+++ b/translations/pt-BR/data/reusables/projects/open-item-menu.md
@@ -0,0 +1 @@
+1.  Select the {% octicon "triangle-down" aria-label="the item menu" %} (in table layout) or the {% octicon "kebab-horizontal" aria-label="the item menu" %} (in board layout).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/projects/open-view-menu.md b/translations/pt-BR/data/reusables/projects/open-view-menu.md
new file mode 100644
index 0000000000..e1012c7cb8
--- /dev/null
+++ b/translations/pt-BR/data/reusables/projects/open-view-menu.md
@@ -0,0 +1 @@
+1. Click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the name of the currently open view. ![Screenshot showing the view menu icon](/assets/images/help/projects-v2/view-menu-icon.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/projects/project-description.md b/translations/pt-BR/data/reusables/projects/project-description.md
index 5601910a7a..1e2c7fa118 100644
--- a/translations/pt-BR/data/reusables/projects/project-description.md
+++ b/translations/pt-BR/data/reusables/projects/project-description.md
@@ -1,10 +1,10 @@
 You can set your project's description and README to share the purpose of your project, provide instructions on how to use the project, and include any relevant links.
 
 {% data reusables.projects.project-settings %}
-1. To add a short description to your project, under "Add a description", type your description in the text box  and click **Save**.
+1. To add a short description to your project, under "Add a description", type your description in the text box  and click **Save**. ![Screenshot showing the 'Add my description' settings](/assets/images/help/projects-v2/edit-description.png)
 1. To update your project's README, under "README", type your content in the text box.
    - You can format your README using Markdown. Para obter mais informações, consulte "[Sintaxe básica de gravação e formatação](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)".
-   - To toggle between the text box and a preview of your changes, click {% octicon "eye" aria-label="The preview icon" %} or {% octicon "pencil" aria-label="The edit icon" %}.
-1. To save changes to your README, click **Save**.
+   - To toggle between the text box and a preview of your changes, click {% octicon "eye" aria-label="The preview icon" %} or {% octicon "pencil" aria-label="The edit icon" %}. ![Screenshot showing editing a project's README](/assets/images/help/projects-v2/edit-readme.png)
+1. To save changes to your README, click **Save**. ![Screenshot showing the 'Save' button for a project's README](/assets/images/help/projects-v2/save-readme-button.png)
 
 You can view and make quick changes to your project description and README by navigating to your project and clicking {% octicon "sidebar-expand" aria-label="The sidebar icon" %} in the top right.
diff --git a/translations/pt-BR/data/reusables/projects/project-settings.md b/translations/pt-BR/data/reusables/projects/project-settings.md
index 4c244857b3..1d847581a2 100644
--- a/translations/pt-BR/data/reusables/projects/project-settings.md
+++ b/translations/pt-BR/data/reusables/projects/project-settings.md
@@ -1,3 +1,3 @@
 1. Navigate to your project.
-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. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png)
+2. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings. ![Screenshot showing the 'Settings' menu item](/assets/images/help/projects-v2/settings-menu-item.png)
diff --git a/translations/pt-BR/data/reusables/projects/project_boards_old.md b/translations/pt-BR/data/reusables/projects/project_boards_old.md
index 119b93f436..d99fdaa756 100644
--- a/translations/pt-BR/data/reusables/projects/project_boards_old.md
+++ b/translations/pt-BR/data/reusables/projects/project_boards_old.md
@@ -3,9 +3,8 @@
 {% note %}
 
 **Notas:**
-
-* Projects (beta), the all-new projects experience, is now available. For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" and "[Migrating your project to Projects (beta)](/issues/trying-out-the-new-projects-experience/migrating-your-project)."
-* You can only create a new classic project board for an organization, user, or repository that already has at least one classic project board. If you're unable to create a classic project board, create a beta project board instead.
+* {% data variables.product.prodname_projects_v2 %}, the all-new projects experience, is now available. For more information about {% data variables.product.prodname_projects_v2 %}, see "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" and for information about migrating your {% data variables.projects.projects_v1_board %}, see "[Migrating from {% data variables.product.prodname_projects_v1_caps %}](/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic)."
+* You can only create a new classic project board for an organization, user, or repository that already has at least one classic project board. If you're unable to create a classic project board, create a project board instead.
 
 {% endnote %}
 
diff --git a/translations/pt-BR/data/reusables/projects/projects-api.md b/translations/pt-BR/data/reusables/projects/projects-api.md
index f011c82cee..2ca2517143 100644
--- a/translations/pt-BR/data/reusables/projects/projects-api.md
+++ b/translations/pt-BR/data/reusables/projects/projects-api.md
@@ -3,8 +3,8 @@
 
 **Notas:**
 
-* This API only applies to project boards. Projects (beta) can be managed with the GraphQL API. Para obter mais informações, consulte[Usando a API para gerenciar projetos (beta)](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)".
-* You can only create a new classic project board for an organization, user, or repository that already has at least one classic project board.
+* This API only applies to {% data variables.product.prodname_projects_v1 %}. {% data variables.product.prodname_projects_v2 %} can be managed with the GraphQL API. For more information, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)."
+* You can only create a new {% data variables.projects.projects_v1_board %} for an organization, user, or repository that already has at least one {% data variables.projects.projects_v1_board %}.
 
 {% endnote %}
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/projects/reopen-a-project.md b/translations/pt-BR/data/reusables/projects/reopen-a-project.md
index 2b16604667..05b2906fff 100644
--- a/translations/pt-BR/data/reusables/projects/reopen-a-project.md
+++ b/translations/pt-BR/data/reusables/projects/reopen-a-project.md
@@ -1,6 +1,6 @@
 1. Click the **Projects** tab. ![Captura de tela que mostra o botão de fechar projeto](/assets/images/help/issues/projects-profile-tab.png)
 1. To show closed projects, click **Closed**. ![Captura de tela que mostra o botão de fechar projeto](/assets/images/help/issues/closed-projects-tab.png)
 1. Click the project you want to reopen.
-1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
-1. In the menu, to access the project settings, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
+1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png)
+1. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings. ![Screenshot showing the 'Settings' menu item](/assets/images/help/projects-v2/settings-menu-item.png)
 1. At the bottom of the page, click **Re-open project**. ![Screenshot showing project re-open button](/assets/images/help/issues/reopen-project-button.png)
diff --git a/translations/pt-BR/data/reusables/projects/save-view.md b/translations/pt-BR/data/reusables/projects/save-view.md
new file mode 100644
index 0000000000..c5113751f4
--- /dev/null
+++ b/translations/pt-BR/data/reusables/projects/save-view.md
@@ -0,0 +1,2 @@
+{% data reusables.projects.open-view-menu %}
+1. Clique em **Save changes** (Salvar alterações). ![Screenshot showing the save menu item](/assets/images/help/projects-v2/save-view.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/projects/select-an-item.md b/translations/pt-BR/data/reusables/projects/select-an-item.md
new file mode 100644
index 0000000000..88159cd0ec
--- /dev/null
+++ b/translations/pt-BR/data/reusables/projects/select-an-item.md
@@ -0,0 +1,5 @@
+1. Select the item. Para selecionar múltiplos itens, siga um dos passos a seguir:
+     - Hold <kbd>Command</kbd> (Mac) or <kbd>Ctrl</kbd> (Windows/Linux) and click each item.
+     - Select an item then press <kbd>Shift</kbd>+<kbd>↑</kbd> or <kbd>Shift</kbd>+<kbd>↓</kbd> to select additional items above or below the selected item.
+     - Select an item then press <kbd>Shift</kbd> and click another item to select all items between the two items.
+     - With a row or item already selected, press <kbd>Command</kbd>+<kbd>A</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>A</kbd> (Windows/Linux) to select all items in a column in a board layout or all items in a table layout.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/repositories/anyone-can-view-anonymized-url.md b/translations/pt-BR/data/reusables/repositories/anyone-can-view-anonymized-url.md
new file mode 100644
index 0000000000..f5222c9d24
--- /dev/null
+++ b/translations/pt-BR/data/reusables/repositories/anyone-can-view-anonymized-url.md
@@ -0,0 +1,5 @@
+{% warning %}
+
+**Warning:** If you attach a file to a pull request, issue comment, or ticket in the {% data variables.contact.support_portal %}, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. Para manter arquivos de mídia confidenciais privados, forneça-os a partir de uma rede privada ou servidor que exige autenticação. {% ifversion fpt or ghec %}Para mais informações sobre URLs anônimas, consulte "[Sobre URLs anônimas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
+
+{% endwarning %}
diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index de00cdd432..be2e0f50df 100644
--- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -1,20 +1,15 @@
-| Provider      | Segredo compatível                            | Secret type                         |
-| ------------- | --------------------------------------------- | ----------------------------------- |
-| Adafruit IO   | Chave de IO de Adafruit                       | adafruit_io_key                   |
-| Adobe         | Adobe Device Token                            | adobe_device_token                |
-| Adobe         | Adobe Service Token                           | adobe_service_token               |
-| Adobe         | Adobe Short-Lived Access Token                | adobe_short_lived_access_token  |
-| Adobe         | Adobe JSON Web Token                          | adobe_jwt                           |
-| Alibaba Cloud | ID da chave de acesso da nuvem do Alibaba     | alibaba_cloud_access_key_id     |
-| Alibaba Cloud | Segredo da chave de acesso à nuvem do Alibaba | alibaba_cloud_access_key_secret |
+| Provider      | Segredo compatível                                               | Secret type                                                              |
+| ------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------ |
+| Adafruit IO   | Chave de IO de Adafruit                                          | adafruit_io_key                                                        |
+| Adobe         | Adobe Device Token                                               | adobe_device_token                                                     |
+| Adobe         | Adobe Service Token                                              | adobe_service_token                                                    |
+| Adobe         | Adobe Short-Lived Access Token                                   | adobe_short_lived_access_token                                       |
+| Adobe         | Adobe JSON Web Token                                             | adobe_jwt                                                                |
+| Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_id </br>alibaba_cloud_access_key_secret |
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
-Amazon | Amazon OAuth Client ID | amazon_oauth_client_id{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
-Amazon | Amazon OAuth Client Secret | amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key
+Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id </br>amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id </br>aws_secret_access_key
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} Asana | Asana Personal Access Token | asana_personal_access_token Atlassian | Atlassian API Token | atlassian_api_token Atlassian | Atlassian JSON Web Token | atlassian_jwt Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token
+Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token </br>aws_temporary_access_key_id </br>aws_secret_access_key{% endif %} Asana | Asana Personal Access Token | asana_personal_access_token Atlassian | Atlassian API Token | atlassian_api_token Atlassian | Atlassian JSON Web Token | atlassian_jwt Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
 Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
@@ -32,19 +27,15 @@ FullStory | FullStory API Key | fullstory_api_key{% endif %} GitHub | GitHub Per
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
 GitLab | GitLab Access Token | gitlab_access_token{% endif %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} Google | Google API Key | google_api_key Google | Google Cloud Private Key ID | google_cloud_private_key_id
+Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} Google | Google API Key | google_api_key Google | Google Cloud Private Key ID |
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %}
+Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %}
+Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
 Google | Google OAuth Access Token | google_oauth_access_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
-Google | Google OAuth Client ID | google_oauth_client_id{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
-Google | Google OAuth Client Secret | google_oauth_client_secret{% endif %}
+Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id </br>google_oauth_client_secret{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
 Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %} Grafana | Grafana API Key | grafana_api_key HashiCorp | Terraform Cloud / Enterprise API Token | terraform_api_token HashiCorp | HashiCorp Vault Batch Token | hashicorp_vault_batch_token HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token Hubspot | Hubspot API Key | hubspot_api_key Intercom | Intercom Access Token | intercom_access_token Ionic | Ionic Personal Access Token | ionic_personal_access_token Ionic | Ionic Refresh Token | ionic_refresh_token
 {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
@@ -80,9 +71,7 @@ PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Plivo | Plivo Auth ID | plivo_auth_id{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Plivo | Plivo Auth Token | plivo_auth_token{% endif %} Postman | Postman API Key | postman_api_key Proctorio | Proctorio Consumer Key | proctorio_consumer_key Proctorio | Proctorio Linkage Key | proctorio_linkage_key Proctorio | Proctorio Registration Key | proctorio_registration_key Proctorio | Proctorio Secret Key | proctorio_secret_key Pulumi | Pulumi Access Token | pulumi_access_token PyPI | PyPI API Token | pypi_api_token
+Plivo | Plivo Auth ID with Plivo Auth Token | plivo_auth_id </br>plivo_auth_token{% endif %} Postman | Postman API Key | postman_api_key Proctorio | Proctorio Consumer Key | proctorio_consumer_key Proctorio | Proctorio Linkage Key | proctorio_linkage_key Proctorio | Proctorio Registration Key | proctorio_registration_key Proctorio | Proctorio Secret Key | proctorio_secret_key Pulumi | Pulumi Access Token | pulumi_access_token PyPI | PyPI API Token | pypi_api_token
 {%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %}
 redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %} RubyGems | RubyGems API Key | rubygems_api_key Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token
 {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
diff --git a/translations/pt-BR/data/reusables/secret-scanning/push-protection-allow-email.md b/translations/pt-BR/data/reusables/secret-scanning/push-protection-allow-email.md
new file mode 100644
index 0000000000..7ec78f5cbc
--- /dev/null
+++ b/translations/pt-BR/data/reusables/secret-scanning/push-protection-allow-email.md
@@ -0,0 +1,3 @@
+{% ifversion secret-scanning-push-protection-email %}
+When a contributor bypasses a push protection block for a secret, {% data variables.product.prodname_dotcom %} also sends an email alert to the organization owners, security managers, and repository administrators who have opted in for email notifications.
+{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md
index a7b25f216f..027348a57e 100644
--- a/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md
+++ b/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md
@@ -1,48 +1,44 @@
-| Provider                  | Segredo compatível                                 | Secret type                                              |
-| ------------------------- | -------------------------------------------------- | -------------------------------------------------------- |
-| Adafruit IO               | Chave de IO de Adafruit                            | adafruit_io_key                                        |
-| Alibaba Cloud             | ID da chave de acesso da nuvem do Alibaba          | alibaba_cloud_access_key_id                          |
-| Alibaba Cloud             | Segredo da chave de acesso à nuvem do Alibaba      | alibaba_cloud_access_key_secret                      |
-| Amazon                    | Amazon OAuth Client ID                             | amazon_oauth_client_id                                 |
-| Amazon                    | Amazon OAuth Client Secret                         | amazon_oauth_client_secret                             |
-| Amazon Web Services (AWS) | ID da Chave de Acesso do AWS da Amazon             | aws_access_key_id                                      |
-| Amazon Web Services (AWS) | Chave de acesso secreta do AWS da Amazon           | aws_secret_access_key                                  |
-| Amazon Web Services (AWS) | Amazon AWS Session Token                           | aws_session_token                                      |
-| Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID                 | aws_temporary_access_key_id                          |
-| Asana                     | Asana Personal Access Token                        | asana_personal_access_token                            |
-| Atlassian                 | Bitbucket Server Personal Access Token             | bitbucket_server_personal_access_token               |
-| Azure                     | Azure Active Directory Application Secret          | azure_active_directory_application_secret            |
-| Azure                     | Azure Cache for Redis Access Key                   | azure_cache_for_redis_access_key                     |
-| Azure                     | Token de acesso pessoal do Azure DevOps            | azure_devops_personal_access_token                   |
-| Checkout.com              | Checkout.com Production Secret Key                 | checkout_production_secret_key                         |
-| Clojars                   | Token de implantação de Clojars                    | clojars_deploy_token                                   |
-| Databricks                | Token de acesso de Databricks                      | databricks_access_token                                |
-| DigitalOcean              | DigitalOcean Personal Access Token                 | digitalocean_personal_access_token                     |
-| DigitalOcean              | DigitalOcean OAuth Token                           | digitalocean_oauth_token                               |
-| DigitalOcean              | DigitalOcean Refresh Token                         | digitalocean_refresh_token                             |
-| DigitalOcean              | DigitalOcean System Token                          | digitalocean_system_token                              |
-| Discord                   | Token de Bot de Discord                            | discord_bot_token                                      |
-| Doppler                   | Token pessoal de Doppler                           | doppler_personal_token                                 |
-| Doppler                   | Token de serviço de Doppler                        | doppler_service_token                                  |
-| Doppler                   | Token de CLI de Doppler                            | doppler_cli_token                                      |
-| Doppler                   | Token de SCIM de Doppler                           | doppler_scim_token                                     |
-| Doppler                   | Doppler Audit Token                                | doppler_audit_token                                    |
-| Dropbox                   | Token de acesso à vida curta do Dropbox            | dropbox_short_lived_access_token                     |
-| Duffel                    | Duffel Live Access Token                           | duffel_live_access_token                               |
-| EasyPost                  | EasyPost Production API Key                        | easypost_production_api_key                            |
-| Flutterwave               | Flutterwave Live API Secret Key                    | flutterwave_live_api_secret_key                      |
-| Fullstory                 | FullStory API Key                                  | fullstory_api_key                                      |
-| GitHub                    | Token de acesso pessoal do GitHub                  | github_personal_access_token                           |
-| GitHub                    | GitHub OAuth Access Token                          | github_oauth_access_token                              |
-| GitHub                    | GitHub Refresh Token                               | github_refresh_token                                   |
-| GitHub                    | Token de acesso à instalação do aplicativo GitHub  | github_app_installation_access_token                 |
-| GitHub                    | Chave privada de SSH do GitHub                     | github_ssh_private_key                                 |
-| Google                    | Google Cloud Storage Access Key Secret             | google_cloud_storage_access_key_secret               |
-| Google                    | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id |
-| Google                    | Google Cloud Storage User Access Key ID            | google_cloud_storage_user_access_key_id            |
-| Grafana                   | Grafana API Key                                    | grafana_api_key                                        |
-| Hubspot                   | Chave da API de Hubspot                            | hubspot_api_key                                        |
-| Intercom                  | Intercom Access Token                              | intercom_access_token                                  |
+| Provider                  | Segredo compatível                                                                                | Secret type                                                                                              |
+| ------------------------- | ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
+| Adafruit IO               | Chave de IO de Adafruit                                                                           | adafruit_io_key                                                                                        |
+| Alibaba Cloud             | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret                                  | alibaba_cloud_access_key_id </br>alibaba_cloud_access_key_secret                                 |
+| Amazon                    | Amazon OAuth Client ID with Amazon OAuth Client Secret                                            | amazon_oauth_client_id </br>amazon_oauth_client_secret                                               |
+| Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key                                        | aws_access_key_id </br>aws_secret_access_key                                                         |
+| Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token </br>aws_temporary_access_key_id </br>aws_secret_access_key                    |
+| Asana                     | Asana Personal Access Token                                                                       | asana_personal_access_token                                                                            |
+| Atlassian                 | Bitbucket Server Personal Access Token                                                            | bitbucket_server_personal_access_token                                                               |
+| Azure                     | Azure Active Directory Application Secret                                                         | azure_active_directory_application_secret                                                            |
+| Azure                     | Azure Cache for Redis Access Key                                                                  | azure_cache_for_redis_access_key                                                                     |
+| Azure                     | Token de acesso pessoal do Azure DevOps                                                           | azure_devops_personal_access_token                                                                   |
+| Checkout.com              | Checkout.com Production Secret Key                                                                | checkout_production_secret_key                                                                         |
+| Clojars                   | Token de implantação de Clojars                                                                   | clojars_deploy_token                                                                                   |
+| Databricks                | Token de acesso de Databricks                                                                     | databricks_access_token                                                                                |
+| DigitalOcean              | DigitalOcean Personal Access Token                                                                | digitalocean_personal_access_token                                                                     |
+| DigitalOcean              | DigitalOcean OAuth Token                                                                          | digitalocean_oauth_token                                                                               |
+| DigitalOcean              | DigitalOcean Refresh Token                                                                        | digitalocean_refresh_token                                                                             |
+| DigitalOcean              | DigitalOcean System Token                                                                         | digitalocean_system_token                                                                              |
+| Discord                   | Token de Bot de Discord                                                                           | discord_bot_token                                                                                      |
+| Doppler                   | Token pessoal de Doppler                                                                          | doppler_personal_token                                                                                 |
+| Doppler                   | Token de serviço de Doppler                                                                       | doppler_service_token                                                                                  |
+| Doppler                   | Token de CLI de Doppler                                                                           | doppler_cli_token                                                                                      |
+| Doppler                   | Token de SCIM de Doppler                                                                          | doppler_scim_token                                                                                     |
+| Doppler                   | Doppler Audit Token                                                                               | doppler_audit_token                                                                                    |
+| Dropbox                   | Token de acesso à vida curta do Dropbox                                                           | dropbox_short_lived_access_token                                                                     |
+| Duffel                    | Duffel Live Access Token                                                                          | duffel_live_access_token                                                                               |
+| EasyPost                  | EasyPost Production API Key                                                                       | easypost_production_api_key                                                                            |
+| Flutterwave               | Flutterwave Live API Secret Key                                                                   | flutterwave_live_api_secret_key                                                                      |
+| Fullstory                 | FullStory API Key                                                                                 | fullstory_api_key                                                                                      |
+| GitHub                    | Token de acesso pessoal do GitHub                                                                 | github_personal_access_token                                                                           |
+| GitHub                    | GitHub OAuth Access Token                                                                         | github_oauth_access_token                                                                              |
+| GitHub                    | GitHub Refresh Token                                                                              | github_refresh_token                                                                                   |
+| GitHub                    | Token de acesso à instalação do aplicativo GitHub                                                 | github_app_installation_access_token                                                                 |
+| GitHub                    | Chave privada de SSH do GitHub                                                                    | github_ssh_private_key                                                                                 |
+| Google                    | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret    | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret |
+| Google                    | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret               | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret            |
+| Google                    | Google OAuth Client ID with Google OAuth Client Secret                                            | google_oauth_client_id </br>google_oauth_client_secret                                               |
+| Grafana                   | Grafana API Key                                                                                   | grafana_api_key                                                                                        |
+| Hubspot                   | Chave da API de Hubspot                                                                           | hubspot_api_key                                                                                        |
+| Intercom                  | Intercom Access Token                                                                             | intercom_access_token                                                                                  |
 {%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
 JFrog | JFrog Platform Access Token | jfrog_platform_access_token JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} Ionic | Ionic Personal Access Token | ionic_personal_access_token Ionic | Ionic Refresh Token | ionic_refresh_token Linear | Linear API Key | linear_api_key Linear | Linear OAuth Access Token | linear_oauth_access_token Midtrans | Midtrans Production Server Key | midtrans_production_server_key New Relic | New Relic Personal API Key | new_relic_personal_api_key New Relic | New Relic REST API Key | new_relic_rest_api_key New Relic | New Relic Insights Query Key | new_relic_insights_query_key npm | npm Access Token | npm_access_token NuGet | NuGet API Key | nuget_api_key Onfido | Onfido Live API Token | onfido_live_api_token OpenAI | OpenAI API Key | openai_api_key PlanetScale | PlanetScale Database Password | planetscale_database_password PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token PlanetScale | PlanetScale Service Token | planetscale_service_token Postman | Postman API Key | postman_api_key Proctorio | Proctorio Secret Key | proctorio_secret_key
 {%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %}
diff --git a/translations/pt-BR/data/reusables/secret-scanning/secret-scanning-pattern-pair-matches.md b/translations/pt-BR/data/reusables/secret-scanning/secret-scanning-pattern-pair-matches.md
new file mode 100644
index 0000000000..d664036275
--- /dev/null
+++ b/translations/pt-BR/data/reusables/secret-scanning/secret-scanning-pattern-pair-matches.md
@@ -0,0 +1 @@
+If access to a resource requires paired credentials, then secret scanning will create an alert only when both parts of the pair are detected in the same file. This ensures that the most critical leaks are not hidden behind information about partial leaks.
diff --git a/translations/pt-BR/data/reusables/support/submit-a-ticket.md b/translations/pt-BR/data/reusables/support/submit-a-ticket.md
index db429d5739..d78755fc6f 100644
--- a/translations/pt-BR/data/reusables/support/submit-a-ticket.md
+++ b/translations/pt-BR/data/reusables/support/submit-a-ticket.md
@@ -27,6 +27,8 @@
     - Etapas para reproduzir o problema
     - Quaisquer circunstâncias especiais relacionadas à descoberta do problema (como a primeira ocorrência ou ocorrência após um evento específico, frequência de ocorrência, impacto comercial do problema e urgência sugerida)
     - Redação exata das mensagens de erro
+{% indented_data_reference reusables.repositories.anyone-can-view-anonymized-url spaces=3 %}
+
 {%- ifversion ghes %}
 1. Optionally, attach diagnostics files and other files by dragging and dropping, uploading, or pasting from the clipboard.
 {%- endif %}
diff --git a/translations/pt-BR/data/reusables/webhooks/project_card_short_desc.md b/translations/pt-BR/data/reusables/webhooks/project_card_short_desc.md
index c8caa75605..7adf6d2394 100644
--- a/translations/pt-BR/data/reusables/webhooks/project_card_short_desc.md
+++ b/translations/pt-BR/data/reusables/webhooks/project_card_short_desc.md
@@ -1 +1 @@
-Atividade relacionada aos cartões do projeto. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos [cartões de projeto](/rest/reference/projects#cards)".
+Activity related to cards in a {% data variables.projects.projects_v1_board %}. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST dos [cartões de projeto](/rest/reference/projects#cards)".
diff --git a/translations/pt-BR/data/reusables/webhooks/project_column_short_desc.md b/translations/pt-BR/data/reusables/webhooks/project_column_short_desc.md
index 7c78f8425c..6a67705361 100644
--- a/translations/pt-BR/data/reusables/webhooks/project_column_short_desc.md
+++ b/translations/pt-BR/data/reusables/webhooks/project_column_short_desc.md
@@ -1 +1 @@
-Atividade relacionada a colunas em um quadro de projeto. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST das "[colunas do projeto](/rest/reference/projects#columns)".
+Activity related to columns in a {% data variables.projects.projects_v1_board %}. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a API REST das "[colunas do projeto](/rest/reference/projects#columns)".
diff --git a/translations/pt-BR/data/reusables/webhooks/project_short_desc.md b/translations/pt-BR/data/reusables/webhooks/project_short_desc.md
index 9aee5961b6..0f9aade5d3 100644
--- a/translations/pt-BR/data/reusables/webhooks/project_short_desc.md
+++ b/translations/pt-BR/data/reusables/webhooks/project_short_desc.md
@@ -1 +1 @@
-Atividade relacionada aos quadros de projeto. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte A API REST dos "[projetos](/rest/reference/projects)".
+Atividade relacionada a {% data variables.projects.projects_v1_boards %}. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte A API REST dos "[projetos](/rest/reference/projects)".
diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml
index 07dddcec87..c6e18c5e91 100644
--- a/translations/pt-BR/data/variables/product.yml
+++ b/translations/pt-BR/data/variables/product.yml
@@ -67,6 +67,16 @@ prodname_codeql_cli: 'CodeQL CLI'
 #Update this whenever a new enterprise version of CodeQL is being prepared.
 codeql_cli_ghes_recommended_version: >-
   {% ifversion ghes < 3.3 %}2.6.3{% elsif ghes < 3.5 %}2.7.6{% elsif ghes = 3.5 %}2.8.5{% elsif ghes = 3.6 %}2.9.4{% elsif ghae-issue-7470 %}2.8.5{% elsif ghae %}2.7.6{% endif %}
+#Projects v2
+prodname_projects_v2: 'Projetos'
+prodname_projects_v1: >-
+  {% ifversion ghes or ghae %}project boards{% else %}projects (classic){% endif %}
+prodname_projects_v1_caps: >-
+  {% ifversion ghes or ghae %}Project boards{% else %}Projects (classic){% endif %}
+prodname_project_v1: >-
+  {% ifversion ghes or ghae %}project board{% else %}project (classic){% endif %}
+prodname_project_v1_caps: >-
+  {% ifversion ghes or ghae %}Project board{% else %}Project (classic){% endif %}
 #Apps, GitHub Marketplace, and integrations
 prodname_marketplace: 'GitHub Marketplace'
 prodname_github_app: 'aplicativo GitHub'
@@ -150,7 +160,7 @@ prodname_code_scanning_capc: 'Varredura de código'
 prodname_codeql_runner: 'Executor do CodeQL'
 prodname_advisory_database: 'Banco de Dados Consultivo GitHub'
 prodname_codeql_workflow: 'Fluxo de trabalho de análise do CodeQL'
-prodname_dependency_review_action: 'Dependency Review GitHub Action'
+prodname_dependency_review_action: 'dependency review action'
 #Visual Studio
 prodname_vs: 'Visual Studio'
 prodname_vscode_shortname: 'VS Code'
diff --git a/translations/pt-BR/data/variables/projects.yml b/translations/pt-BR/data/variables/projects.yml
new file mode 100644
index 0000000000..8de5dcae0e
--- /dev/null
+++ b/translations/pt-BR/data/variables/projects.yml
@@ -0,0 +1,13 @@
+projects_v2: 'projetos'
+projects_v2_caps: 'Projetos'
+project_v2: 'project'
+project_v2_caps: 'Projeto'
+projects_v1_board: >-
+  {% ifversion ghes or ghae %}project board{% else %}classic project{% endif %}
+projects_v1_board_caps: >-
+  {% ifversion ghes or ghae %}Project board{% else %}Classic project{% endif %}
+projects_v1_boards: >-
+  {% ifversion ghes or ghae %}project boards{% else %}classic projects{% endif %}
+projects_v1_boards_caps: >-
+  {% ifversion ghes or ghae %}Project boards{% else %}Classic projects{% endif %}
+command-palette-shortcut: '<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)'
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
index 0296abe293..88f73f221d 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
@@ -1,21 +1,50 @@
 ---
 title: 管理辅助功能设置
-intro: '您可以在 {% data variables.product.prodname_dotcom %} 上的辅助功能设置中禁用字符键快捷方式。'
+shortTitle: Manage accessibility settings
+intro: '{% data variables.product.product_name %}''s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs.'
 versions:
   feature: keyboard-shortcut-accessibility-setting
 redirect_from:
   - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings
+type: how_to
+miniTocMaxHeadingLevel: 3
 ---
 
 ## 关于辅助功能设置
 
-{% data variables.product.product_name %} 包括各种键盘快捷键，便于您在整个站点中执行操作，而无需使用鼠标进行导航。 虽然快捷方式有助于节省时间，但它们有时会使 {% data variables.product.prodname_dotcom %} 更难使用且更难以访问。
+To accommodate your vision, hearing, motor, cognitive, or learning needs, you can customize the user interface for {% data variables.product.product_location %}.
 
-默认情况下，所有键盘快捷键都在 {% data variables.product.product_name %} 上启用，但您可以选择在辅助功能设置中禁用字符键快捷键。 此设置不影响 Web 浏览器提供的键盘快捷键，或者使用修饰键（如 <kbd>Control</kbd> 或 <kbd>Command</kbd>）的 {% data variables.product.prodname_dotcom %} 快捷键。
+## 管理辅助功能设置
 
-## 管理字符键快捷方式
+You can decide whether you want to use some or all keyboard shortcuts on {% ifversion fpt or ghec %}{% data variables.product.product_location %}{% elsif ghes or ghae %}the website for {% data variables.product.product_location %}{% endif %}, and you can control the display of animated images.
+
+### Managing keyboard shortcuts
+
+You can perform actions across the {% data variables.product.product_name %} website without using your mouse by using your keyboard instead. Keyboard shortcuts can be useful to save time for some people, but may interfere with accessibility if you don't intend to use the shortcuts.
+
+By default, all keyboard shortcuts are enabled on {% data variables.product.product_name %}. 更多信息请参阅“[键盘快捷键](/get-started/using-github/keyboard-shortcuts)”。
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.accessibility_settings %}
-1. 选中或取消选中 **Enable character key shortcuts（启用字符键快捷键）**复选框。 ![“启用字符键快捷方式”复选框的屏幕截图](/assets/images/help/settings/disable-character-key-shortcuts.png)
-2. 单击 **Save（保存）**。
+1. Under "Keyboard shortcuts", manage settings for your keyboard shortcuts.
+
+   - Optionally, to disable or enable shortcut keys that don't use modifiers keys like <kbd>Control</kbd> or <kbd>Command</kbd>, under "General", deselect **Character keys**. If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key.
+{%- ifversion command-palette %}
+   - Optionally, to customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)."
+   {%- endif %}
+
+{% ifversion motion-management %}
+
+### Managing motion
+
+You can control how {% data variables.product.product_name %} displays animated images.
+
+By default, {% data variables.product.product_name %} syncs with your system-level preference for reduced motion. For more information, see the documentation or settings for your operating system.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.accessibility_settings %}
+1. Under "Motion", manage settings for motion.
+
+   - Optionally, to control how {% data variables.product.product_name %} displays animaged images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**.
+
+{% endif %}
diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 68189622fe..ece89beed5 100644
--- a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -87,12 +87,12 @@ jobs:
 ## 支持的运行器和硬件资源
 
 Windows 和 Linux 虚拟机的硬件规格：
-- 2 核 CPU
+- 2 核 CPU (x86_64)
 - 7 GB RAM
 - 14 GB SSD 空间
 
 MacOS 虚拟机的硬件规格：
-- 3 核 CPU
+- 3 核 CPU (x86_64)
 - 14 GB RAM
 - 14 GB SSD 空间
 
diff --git a/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md
index 4433eeb1bf..a4831c701e 100644
--- a/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -185,7 +185,7 @@ on:
   deployment_status
 ```
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 ### `讨论`
 
 | Web 挂钩事件有效负载                                                                             | 活动类型                                                                                                                                                                                                                                                                                                    | `GITHUB_SHA` | `GITHUB_REF` |
diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
index f55661600d..391a8d0442 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
@@ -10,8 +10,6 @@ topics:
 shortTitle: Server Statistics
 ---
 
-{% data reusables.server-statistics.release-phase %}
-
 ## About {% data variables.product.prodname_server_statistics %}
 
 {% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.product.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. 
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index a5122d52e4..71543e2a68 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -737,6 +737,20 @@ This utility rewrites the imported repository. This gives you a chance to rename
 git-import-rewrite
 ```
 
+{% ifversion ghes > 3.3 %}
+
+## Security
+
+### ghe-find-insecure-git-operations
+
+This utility searches your instance's logs and identifies Git operations over SSH that use insecure algorithms or hash functions, including DSA, RSA-SHA-1, HMAC-SHA-1, and CBC ciphers. You can use the output to support each client's transition to a more secure SSH connection. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server){% ifversion ghes < 3.6 %}.{% elsif ghes > 3.5 %} and "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."{% endif %}
+
+```shell
+ghe-find-insecure-git-operations
+```
+
+{% endif %}
+
 ## Support
 
 ### ghe-diagnostics
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
index f0d176e832..12ea175610 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -73,6 +73,18 @@ shortTitle: 配置电子邮件通知
 5. 当测试电子邮件成功后，在页面的底部单击 **Save settings**。 ![Save settings 按钮](/assets/images/enterprise/management-console/save-settings.png)
 {% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
 
+{% ifversion require-tls-for-smtp %}
+## Enforcing TLS for SMTP connections
+
+You can enforce TLS encryption for all incoming SMTP connections, which can help satisfy an ISO-27017 certification requirement.
+
+{% data reusables.enterprise_site_admin_settings.email-settings %}
+1. Under "Authentication," select **Enforce TLS auth (recommended)**.
+
+   ![Screenshot of the "Enforce TLS auth (recommended)" checkbox](/assets/images/enterprise/configuration/enforce-tls-for-smtp-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+{% endif %}
+
 ## 配置 DNS 和防火墙设置以允许传入的电子邮件
 
 如果您希望允许通知的电子邮件回复，则必须配置 DNS 设置。
@@ -80,7 +92,7 @@ shortTitle: 配置电子邮件通知
 1. 确保您的 SMTP 服务器可以访问实例上的端口 25。
 2. 创建一个指向 `reply.[hostname]` 的 A 记录。 根据您的 DNS 提供商和实例主机配置，您可以创建一个指向 `*.[hostname]` 的 A 记录。
 3. 创建一个指向 `reply.[hostname]` 的 MX 记录，以便发送到该域的电子邮件可以路由到实例。
-4. 创建一个将 `noreply.[hostname]` 指向 `[hostname]` 的 MX 记录，以便对通知电子邮件中 `cc` 地址的回复可以路由到实例。 更多信息请参阅{% ifversion ghes %}"[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}“[关于电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}。”
+4. 创建一个将 `noreply.[hostname]` 指向 `[hostname]` 的 MX 记录，以便对通知电子邮件中 `cc` 地址的回复可以路由到实例。 For more information, see {% ifversion ghes %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."
 
 ## 排查电子邮件递送问题
 
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
new file mode 100644
index 0000000000..dd05637a5b
--- /dev/null
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
@@ -0,0 +1,47 @@
+---
+title: Configuring host keys for your instance
+shortTitle: Configure host keys
+intro: 'You can increase the security of {% data variables.product.product_location %} by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections.'
+permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.'
+versions:
+  ghes: '>= 3.6'
+type: how_to
+topics:
+  - Authentication
+  - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
+  - SSH
+---
+
+## About host keys for your instance
+
+Servers that accept SSH connections advertise one or more cryptographic host keys to securely identify the server to SSH clients. To confirm the server's identity during the initialization of a connection, clients store and verify the host key. For more information, see [SSH Host Key - What, Why, How](https://ssh.com/academy/ssh/host-key) on the SSH Academy website.
+
+{% data reusables.enterprise.about-ssh-ports %}
+
+By default, {% data variables.product.product_location %} generates and advertises host keys with OpenSSH-style host key rotation. To increase the security of SSH in your environment, you can enable additional algorithms for the generation of host keys.
+
+{% note %}
+
+**Note**: If you enable additional host key algorithms, clients that do not use OpenSSH for SSH connections may experience warnings during connection, or fail to connect entirely. Some SSH implementations can ignore unsupported algorithms and fall back to a different algorithm. If the client does not support fallback, the connection will fail. For example, the SSH library for Go does not support fallback to a different algorithm.
+
+{% endnote %}
+
+## Managing an Ed25519 host key
+
+To improve security for clients that connect to {% data variables.product.product_location %}, you can enable the generation and advertisement of an Ed25519 host key. Ed25519 is immune to some attacks that target older signature algorithms, without sacrificing speed. Older SSH clients may not support Ed25519. By default, {% data variables.product.product_name %} instances do not generate or advertise an Ed25519 host key. For more information, see [the Ed25519 website](https://ed25519.cr.yp.to).
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+1. To enable generation and advertisement of the Ed25519 host key, enter the following command.
+
+   ```shell
+   ghe-config app.babeld.host-key-ed25519 true
+   ```
+1. Optionally, enter the following command to disable generation and advertisement of the Ed25519 host key.
+
+   ```shell
+   ghe-config app.babeld.host-key-ed25519 false
+   ```
+{% data reusables.enterprise.apply-configuration %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
new file mode 100644
index 0000000000..3e3a1646e2
--- /dev/null
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
@@ -0,0 +1,53 @@
+---
+title: Configuring SSH connections to your instance
+shortTitle: Configure SSH connections
+intro: 'You can increase the security of {% data variables.product.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.'
+permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.'
+versions:
+  ghes: '>= 3.6'
+type: how_to
+topics:
+  - Authentication
+  - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
+  - SSH
+---
+
+## About SSH connections to your instance
+
+{% data reusables.enterprise.about-ssh-ports %}
+
+To accommodate the SSH clients in your environment, you can configure the types of connections that {% data variables.product.product_location %} will accept.
+
+## Configuring SSH connections with RSA keys
+
+When users perform Git operations on {% data variables.product.product_location %} via SSH over port 22, the client can authenticate with an RSA key. The client may sign the attempt using the SHA-1 hash function. In this context, the SHA-1 hash function is no longer secure. For more information, see [SHA-1](https://en.wikipedia.org/wiki/SHA-1) on Wikipedia.
+
+By default{% ifversion ghes < 3.7 %} on {% data variables.product.product_name %} 3.6 and later{% endif %}, SSH connections that satisfy **both** of the following conditions will fail.
+
+{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %}
+
+You can adjust the cutoff date. If the user uploaded the RSA key before the cutoff date, the client can continue to connect successfuly using SHA-1 as long as the key remains valid. Alternatively, you can reject all SSH connections authenticated with an RSA key if the client signs the connection using the SHA-1 hash function.
+
+Regardless of the setting you choose for your instance, clients can continue to connect using any RSA key signed with a SHA-2 hash function.
+
+If you use an SSH certificate authority, connections will fail if the certificate's `valid_after` date is after the cutoff date. 更多信息请参阅“[关于 SSH 认证机构](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)”。
+
+更多信息请参阅 [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server)。
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+1. Audit your instance's logs for connections that use unsecure algorithms or hash functions using the `ghe-find-insecure-git-operations` utility. 更多信息请参阅“[命令行实用程序](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-find-insecure-git-operations)”。
+1. To configure a cutoff date after which {% data variables.product.product_location %} will deny connections from clients that use an RSA key uploaded after the date if the connection is signed by the SHA-1 hash function, enter the following command. Replace _**RFC-3399-UTC-TIMESTAMP**_ with a valid RFC 3399 UTC timestamp. For example, the default value, August 1, 2022, would be represented as `2022-08-01T00:00:00Z`. For more information, see [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) on the IETF website.
+
+   <pre>
+   $ ghe-config app.gitauth.rsa-sha1 <em>RFC-3339-UTC-TIMESTAMP</em>
+   </pre>
+
+1. Alternatively, to completely disable SSH connections using RSA keys that are signed with the SHA-1 hash function, enter the following command.
+
+   ```shell
+   ghe-config app.gitauth.rsa-sha1 false
+   ```
+{% data reusables.enterprise.apply-configuration %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md
index 66d239caa5..fcf18608fb 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md
@@ -25,6 +25,7 @@ children:
   - /site-admin-dashboard
   - /enabling-private-mode
   - /managing-github-mobile-for-your-enterprise
+  - /configuring-ssh-connections-to-your-instance
   - /configuring-email-for-notifications
   - /verifying-or-approving-a-domain-for-your-enterprise
   - /configuring-rate-limits
@@ -34,6 +35,7 @@ children:
   - /command-line-utilities
   - /restricting-network-traffic-to-your-enterprise
   - /configuring-github-pages-for-your-enterprise
+  - /configuring-host-keys-for-your-instance
   - /configuring-the-referrer-policy-for-your-enterprise
   - /configuring-custom-footers
   - /configuring-web-commit-signing
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md
index 89dfe3b5c4..2d2281b5d3 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md
@@ -8,6 +8,7 @@ topics:
   - Enterprise
 redirect_from:
   - /admin/configuration/initializing-github-ae
+  - /enterprise-server@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae
 ---
 
 ## 关于初始化
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 074854e861..7c41481d8e 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -40,7 +40,7 @@ Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions
 Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see "[Using OpenID Connect with reusable workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)."
 {% endif %}
 
-You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)" and "[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)."{% else %}"[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."{% endif %}
+You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining this information longer than audit log data is retained, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)" and "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."{% else %}{% ifversion audit-log-streaming %}"[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)" and {% endif %}"[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."{% endif %}
 
 ![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
 
diff --git a/translations/zh-CN/content/admin/guides.md b/translations/zh-CN/content/admin/guides.md
index 199a0a6ff3..9eb712d745 100644
--- a/translations/zh-CN/content/admin/guides.md
+++ b/translations/zh-CN/content/admin/guides.md
@@ -52,6 +52,8 @@ includeGuides:
   - /admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise
   - /admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise
   - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud
+  - /admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance
+  - /admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance
   - /admin/configuration/enabling-and-scheduling-maintenance-mode
   - /admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise
   - /admin/configuration/enabling-private-mode
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
index 6b377792e4..69e9be94c0 100644
--- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
@@ -10,8 +10,6 @@ topics:
   - Enterprise
 ---
 
-{% data reusables.server-statistics.release-phase %}
-
 ## About the benefits of {% data variables.product.prodname_server_statistics %}
 
 {% data variables.product.prodname_server_statistics %} 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 %}.
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
index ca54ccc98e..ed7ee7003b 100644
--- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
@@ -8,8 +8,6 @@ redirect_from:
   - /early-access/github/analyze-how-your-team-works-with-server-statistics/exploring-server-statistics
 ---
 
-{% 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 %}. 
 
 Before you can download this data, you must enable {% data variables.product.prodname_server_statistics %}. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." 
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
index da30cecc04..ed0a3b2dd9 100644
--- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
@@ -8,8 +8,6 @@ redirect_from:
   - /early-access/github/analyze-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api
 ---
 
-{% data reusables.server-statistics.release-phase %}
-
 You can request up to 365 days of metrics in a single {% data variables.product.prodname_server_statistics %} REST API request. 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 %}. For a list of the metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)."
 
 Before you can use the {% data variables.product.prodname_server_statistics %} REST API, you must enable {% data variables.product.prodname_server_statistics %}. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." 
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
index a211ee696f..fa3437612f 100644
--- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
@@ -39,9 +39,10 @@ topics:
 {%- ifversion enterprise-audit-log-ip-addresses %}
 - 您可以在审核日志中显示与事件关联的 IP 地址。 更多信息请参阅“[在企业的审核日志中显示 IP 地址](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise)”。
 {%- endif %}
-{%- ifversion ghec %}
+{%- ifversion audit-log-streaming %}
 - 您可以将审核和 Git 事件数据从 {% data variables.product.prodname_dotcom %} 流式传输到外部数据管理系统。 更多信息请参阅“[流式传输企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)”。
-{%- else %}
+{%- endif %}
+{%- ifversion ghes %}
 - 您可以将审核和系统日志从企业转发到第三方托管的监控系统。 更多信息请参阅“[日志转发](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)。”
 {%- endif %}
 {%- ifversion ghec or ghes > 3.2 or ghae-issue-6648 %}
@@ -50,13 +51,6 @@ topics:
 
 有关企业审核日志中可能显示的审核日志操作的完整列表，请参阅“[企业的审核日志操作](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)”。
 
-{% ifversion ghec %}
-## Git 事件
-
-记录 Git 事件数据，如克隆、提取和推送。 更多信息请参阅“[流式传输企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)”。
-
-{% endif %}
-
 ## 延伸阅读
 - “[查看组织的审核日志](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)”
 {%- ifversion ghes %}
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
index d6f421fce9..53f6ef7258 100644
--- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
@@ -59,7 +59,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe
 |--------|-------------
 | `artifact.destroy`    | A workflow run artifact was manually deleted.
 
-{%- ifversion ghec %}
+{%- ifversion audit-log-streaming %}
 ## `audit_log_streaming` category actions
 
 | Action | Description
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
index 398dd5658b..2d681eb2d1 100644
--- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
@@ -3,7 +3,7 @@ title: 流式传输企业的审核日志
 intro: '您可以将审核和 Git 事件数据从 {% data variables.product.prodname_dotcom %} 流式传输到外部数据管理系统。'
 miniTocMaxHeadingLevel: 3
 versions:
-  ghec: '*'
+  feature: audit-log-streaming
 type: tutorial
 topics:
   - Auditing
@@ -17,6 +17,14 @@ redirect_from:
 permissions: Enterprise owners can configure audit log streaming.
 ---
 
+{% ifversion ghes %}
+{% note %}
+
+**Note:** Audit log streaming is currently in beta for {% data variables.product.product_name %} and is subject to change.
+
+{% endnote %}
+{% endif %}
+
 ## 关于审核日志流
 
 为了帮助保护您的知识产权并保持组织的合规性，您可以使用流式处理来保留审核日志数据的副本并监控：
@@ -24,11 +32,11 @@ permissions: Enterprise owners can configure audit log streaming.
 
 流式传输审计数据的好处包括：
 
-* **数据探索**。 您可以使用首选工具检查流事件，以查询大量数据。 流包含整个企业帐户中的审核事件和 Git 事件。
-* **数据连续性**。 您可以暂停流长达七天，而不会丢失任何审核数据。
+* **数据探索**。 您可以使用首选工具检查流事件，以查询大量数据。 The stream contains both audit events and Git events across the entire enterprise account.{% ifversion pause-audit-log-stream %}
+* **数据连续性**。 You can pause the stream for up to seven days without losing any audit data.{% endif %}
 * **数据保留**。 您可以根据需要保留导出的审核日志和 Git 事件数据。
 
-企业所有者可以随时设置、暂停或删除流。 流导出企业中所有组织的审核数据。
+Enterprise owners can set up{% ifversion pause-audit-log-stream %}, pause,{% endif %} or delete a stream at any time. The stream exports the audit and Git events data for all of the organizations in your enterprise.
 
 ## 设置审核日志流
 
@@ -272,6 +280,7 @@ Then, set up streaming with access keys until the vulnerability is resolved. For
 1. 单击 **Check endpoint（检查端点）**以验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Splunk 端点。 ![检查端点](/assets/images/help/enterprises/audit-stream-check-splunk.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
+{% ifversion pause-audit-log-stream %}
 ## 暂停审核日志流
 
 暂停流允许您对接收应用程序执行维护，而不会丢失审核数据。 审核日志在 {% data variables.product.product_location %} 上最多存储七天，然后在取消暂停流时导出。
@@ -284,6 +293,7 @@ Then, set up streaming with access keys until the vulnerability is resolved. For
 1. 将显示一条确认消息。 单击 **Pause stream（暂停流）**以确认。
 
 当应用程序准备好再次接收审核日志时，单击 **Resume stream（恢复流）**以重新启动流式处理审核日志。
+{% endif %}
 
 ## 删除审核日志流
 
diff --git a/translations/zh-CN/content/admin/packages/index.md b/translations/zh-CN/content/admin/packages/index.md
index 201a52784f..7b6f147bd0 100644
--- a/translations/zh-CN/content/admin/packages/index.md
+++ b/translations/zh-CN/content/admin/packages/index.md
@@ -14,6 +14,7 @@ children:
   - /enabling-github-packages-with-minio
   - /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
   - /configuring-package-ecosystem-support-for-your-enterprise
+  - /migrating-your-enterprise-to-the-container-registry-from-the-docker-registry
 shortTitle: 管理 GitHub Packages
 ---
 
diff --git a/translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..d131148de8
--- /dev/null
+++ b/translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,85 @@
+---
+title: Migrating your enterprise to the Container registry from the Docker registry
+intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.product.product_location %} to the {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.'
+versions:
+  feature: docker-ghcr-enterprise-migration
+shortTitle: 迁移到容器注册表
+topics:
+  - Containers
+  - Docker
+  - Migration
+---
+
+{% data reusables.package_registry.container-registry-ghes-beta %}
+
+## 关于 {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+
+For more information about configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+
+## About migration from the Docker registry
+
+{% data reusables.package_registry.container-registry-replaces-docker-registry %} If the Docker registry on {% data variables.product.product_location %} contains images, you must manually migrate the images to the {% data variables.product.prodname_container_registry %}.
+
+{% ifversion ghes %}
+
+{% note %}
+
+**注**：{% data reusables.package_registry.container-registry-ghes-migration-availability %}
+
+{% endnote %}
+
+{% endif %}
+
+{% data reusables.package_registry.container-registry-migration-namespaces %} For more information about the impact of migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the  {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry#about-migration-from-the-docker-registry)."
+
+## Migrating organizations to the {% data variables.product.prodname_container_registry %}
+
+You can start a migration of all your organizations' Docker images to the {% data variables.product.prodname_container_registry %}. The duration of the migration operation depends on the total number of images to migrate, and the overall load on {% ifversion ghes %}your instance{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. After a successful migration, {% data variables.product.product_name %} will display a summary, and all future uploads of Docker images will use the {% data variables.product.prodname_container_registry %}.
+
+If {% ifversion ghes %}a site administrator{% elsif ghae %}an enterprise owner{% endif %} has configured email notifications for {% data variables.product.product_location %}, you will receive an email after the migration is complete. 更多信息请参阅“[配置电子邮件通知](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)”。
+
+{% note %}
+
+**{% ifversion ghes %}注释{% elsif ghae %}注释{% endif %}**：
+
+{%- ifversion ghes %}
+- During the migration, the CPU and memory usage for your instance will increase. To ensure the performance of the instance for your users, {% data variables.product.company_short %} recommends that you begin a migration during a period of reduced activity.
+{%- endif %}
+{% ifversion ghes %}- {% endif %}During the migration, do not modify settings for your enterprise{% ifversion ghes %} or run `ghe-config-apply` from an administrative SSH session{% endif %}. {% ifversion ghes %}These actions will trigger a configuration run, which can restart services and {% elsif ghae %}Modifying these settings {% endif %} may interrupt the migration.
+{%- ifversion ghes %}
+- After the migration, storage pressure on your instance will increase due to the duplication of image files in the Docker registry and the {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.product_name %} will remove the duplicated files when all migrations are complete.
+
+For more information about monitoring the performance and storage of {% data variables.product.product_location %}, see "[Accessing the monitor dashboard](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)."
+{% endif %}
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+1. 在左边栏中，单击 **Packages（包）**。
+1. To the right of the number of packages to migrate, click **Start migration**. During the migration, {% data variables.product.product_name %} will display progress on this page.
+
+After the migration completes, the page will display the results. If a migration fails, the page will show the organizations that own the package that caused the failure.
+
+## Re-running a failed organization migration
+
+Prior to migration, if a user has created a package in the {% data variables.product.prodname_container_registry %} that has an identical name to an existing package in the Docker registry, the migration will fail.
+
+1. Delete the affected container in the {% data variables.product.prodname_container_registry %}. 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package#deleting-a-version-of-an-organization-scoped-package-on-github)”。
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.packages-tab %}
+1. To the right of the number of packages to migrate, click **Re-run migration**. During the migration, {% data variables.product.product_name %} will display progress on this page.
+1. If the migration fails again, start from step 1 and re-run the migration.
+
+{% ifversion ghes %}
+
+## Monitoring traffic to the registries
+
+You can use visualize traffic to the Docker registry and {% data variables.product.prodname_container_registry %} from {% data variables.product.product_location %}'s monitor dashboard. The "GitHub Container Package Registry" graph can help you confirm that you've successfully migrated all images to the {% data variables.product.prodname_container_registry %}. In the graph, "v1" represents traffic to the Docker registry, and "v2" represents traffic to the {% data variables.product.prodname_container_registry %}. 更多信息请参阅“[访问监控仪表板](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)”。
+
+{% endif %}
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index 44b70d814f..c33e89c990 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -13,6 +13,7 @@ redirect_from:
   - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise
   - /github/setting-up-and-managing-your-enterprise-account/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account
 versions:
   ghec: '*'
   ghes: '*'
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 6984a18e13..5e2042294f 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -203,6 +203,28 @@ shortTitle: 仓库管理策略
 4. 在“Repository upload limit”下，使用下拉菜单，然后单击最大对象大小。 ![包含最大对象大小选项的下拉菜单](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
 5. （可选）要对企业中的所有仓库实施最大上传限制，请选择 **Enforce on all repositories（对所有仓库强制执行）** ![对所有仓库选项强制执行最大对象限制](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
 
+{% ifversion profile-name-enterprise-setting %}
+
+## Enforcing a policy for the display of member names in your repositories
+
+Across all organizations owned by your enterprise, you can allow members to see a comment author's profile name, in addition to their username, in issues and pull requests for public and internal repositories.
+
+![评论中显示的评论者个人资料名称](/assets/images/help/issues/commenter-full-name.png)
+
+{% note %}
+
+**Note:** When this policy is enforced for all repositories in the enterprise, it overrides the organization setting for private repositories. For more information, see "[Managing the display of member names in your organization](/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization)".
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.options-tab %}
+4. Under "Allow members to see the comment author's profile name in public and internal repositories", select the dropdown menu and click a policy. ![Screenshot of Options page with policy drop down emphasized](/assets/images/enterprise/site-admin-settings/comment-authors-profile-name-drop-down.png)
+5. Optionally, to enforce the display of profile names for all repositories in your enterprise, select **Enforce for all repositories on the instance**. ![Screenshot of "Enforce for all repositories" option emphasized](/assets/images/enterprise/site-admin-settings/enforce-for-all-repositories-option.png)
+
+{% endif %}
+
 ## 为仓库之间的拉取请求配置合并冲突编辑器
 
 要求用户在其计算机上本地解决合并冲突可以避免用户因疏忽而从分叉写入到上游仓库。
@@ -265,10 +287,22 @@ shortTitle: 仓库管理策略
 
 {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
 
-{% ifversion ghes %}如果您已经在企业上[启用私密模式](/enterprise/admin/configuration/enabling-private-mode)，{% else %}您{% endif %}可以允许仓库管理员启用对公共仓库的匿名 Git 读取访问。
+If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) for {% data variables.product.product_location %}, you can allow repository administrators to enable anonymous Git read access to public repositories.
 
 启用匿名 Git 读取允许用户在企业上为自定义工具绕过身份验证。 当您或仓库管理员为仓库启用此权限设置时，未经过身份验证的 Git 操作（和具有 {% data variables.product.product_name %} 的网络访问权限的任何人）将获得仓库的读取权限（无需身份验证）。
 
+Anonymous Git read access is disabled by default.{% ifversion ghes = 3.4 or ghes = 3.5 or ghes = 3.6 or ghes = 3.7 %} When you upgrade to {% data variables.product.product_name %} 3.6 or later, anonymous Git read access is automatically disabled at the application level, and `git://` connections on port 9418 will return the following error.
+
+```
+The unauthenticated git protocol on port 9418 is no longer supported.
+```
+
+If you wish to support the unathenticated Git protocol in your environment, you must manually re-enable the feature. {% data variables.product.company_short %} recommends using SSH instead of the Git protocol. 更多信息请参阅 [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server)。
+
+{% endif %}
+
+
+
 如有必要，您可以通过锁定仓库的访问设置，阻止仓库管理员更改企业上仓库的匿名 Git 访问设置。 在您锁定仓库的 Git 读取权限设置后，只有站点管理员可以更改设置。
 
 {% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
diff --git a/translations/zh-CN/content/admin/policies/index.md b/translations/zh-CN/content/admin/policies/index.md
index 274dc3a48f..b7f4d96022 100644
--- a/translations/zh-CN/content/admin/policies/index.md
+++ b/translations/zh-CN/content/admin/policies/index.md
@@ -4,7 +4,6 @@ intro: '您可以在 {% data variables.product.product_name %} 中设置策略
 redirect_from:
   - /enterprise/admin/developer-workflow
   - /enterprise/admin/policies
-  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account
 versions:
   ghec: '*'
   ghes: '*'
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index f230fdbd9a..49888cbf20 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -9,6 +9,9 @@ redirect_from:
   - /github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account
   - /admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account
 intro: '组织适合在您的公司内创建不同的用户组，例如部门或参与相似项目的组。 属于组织的{% ifversion ghae %}内部{% else %}公共和内部{% endif %}仓库可供企业中其他组织中的成员访问，而私有仓库只能供被授予访问权限的组织成员访问。'
 versions:
   ghec: '*'
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
index 2be428403f..b9e4605730 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -25,6 +25,10 @@ You can see all current enterprise members and enterprise administrators{% ifver
 
 You can view all the current enterprise owners{% ifversion ghec %} and billing managers{% endif %} for your enterprise.{% ifversion enterprise-membership-view-improvements %} You can see useful information about each administrator{% ifversion ghec %} and filter the list by role{% endif %}.{% endif %} You can find a specific person by searching for their username or display name.
 
+{% ifversion ghes > 3.5 %}
+Enterprise owners whose accounts are suspended are included in the list of enterprise administrators, and are identified as suspended. You should consider demoting any suspended owners you see. For more information, see "[Promoting or demoting a site administrator](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator#demoting-a-site-administrator-from-the-enterprise-settings)."
+{% endif %}
+
 {% ifversion not ghae %}
 You can also remove an administrator. For more information. see "[Inviting people to manage your enterprise](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise#removing-an-enterprise-administrator-from-your-enterprise-account)."
 {% endif %}
diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md
index b0183c9f18..6a231f83f3 100644
--- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md
+++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md
@@ -13,7 +13,12 @@ versions:
 topics:
   - SSH
 ---
-When you set up SSH, you will need to generate a new SSH key and add it to the ssh-agent. You must add the SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+
+## About SSH
+
+{% data reusables.ssh.about-ssh %} For more information about SSH, see [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) on Wikipedia.
+
+When you set up SSH, you will need to generate a new private SSH key and add it to the SSH agent. You must also add the public SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
 
diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
index 6dbcd7c5cb..24570e7b3b 100644
--- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
@@ -15,9 +15,20 @@ topics:
 shortTitle: 添加新的 SSH 密钥
 ---
 
-在将新的 SSH 密钥添加到 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户之前，您应该具有：
-* [检查现有 SSH 密钥](/articles/checking-for-existing-ssh-keys)
-* [生成新 SSH 密钥并添加到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)
+## About addition of SSH keys to your account
+
+{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+
+After you generate an SSH key pair, you must add the public key to {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable SSH access for your account.
+
+## 基本要求
+
+Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, complete the following steps.
+
+1. Check for existing SSH keys. 更多信息请参阅“[检查现有 SSH 密钥](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)”。
+1. Generate a new SSH key and add it to your machine's SSH agent. 更多信息请参阅“[生成新的 SSH 密钥并添加到 ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。
+
+## Adding a new SSH key to your account
 
 在向您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户添加新 SSH 密钥后，您可以重新配置任何本地存储库以使用 SSH。 更多信息请参阅“[将远程 URL 从 HTTPS 转换为 SSH](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)”。
 
diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
index edd4ada50f..4550c3e576 100644
--- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
+++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
@@ -15,6 +15,16 @@ topics:
 shortTitle: Check for existing SSH key
 ---
 
+## About SSH keys
+
+You can use SSH to perform Git operations in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+
+If you have an existing SSH key, you can use the key to authenticate Git operations over SSH.
+
+## Checking for existing SSH keys
+
+Before you generate a new SSH key, you should check your local machine for existing keys.
+
 {% data reusables.ssh.key-type-support %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index 7e1a11e52b..9ba27ef225 100644
--- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -1,6 +1,6 @@
 ---
-title: Generating a new SSH key and adding it to the ssh-agent
-intro: 'After you''ve checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent.'
+title: 生成新 SSH 密钥并添加到 ssh-agent
+intro: 检查现有 SSH 密钥后，您可以生成新 SSH 密钥以用于身份验证，然后将其添加到 ssh-agent。
 redirect_from:
   - /articles/adding-a-new-ssh-key-to-the-ssh-agent
   - /articles/generating-a-new-ssh-key
@@ -14,147 +14,143 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: Generate new SSH key
+shortTitle: 生成新 SSH 密钥
 ---
-## About SSH key generation
 
-If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)."
+## About SSH key passphrases
 
-If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2).
+{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
 
-If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.
+When you generate an SSH key, you can add a passphrase to further secure the key. Whenever you use the key, you must enter the passphrase. If your key has a passphrase and you don't want to enter the passphrase every time you use the key, you can add your key to the SSH agent. The SSH agent manages your SSH keys and remembers your passphrase.
 
-## Generating a new SSH key
+如果您还没有 SSH 密钥，则必须生成新 SSH 密钥用于身份验证。 如果不确定是否已经拥有 SSH 密钥，您可以检查现有密钥。 更多信息请参阅“[检查现有 SSH 密钥](/github/authenticating-to-github/checking-for-existing-ssh-keys)”。
+
+如果要使用硬件安全密钥向 {% data variables.product.product_name %} 验证，则必须为硬件安全密钥生成新的 SSH 密钥。 使用密钥对进行身份验证时，您必须将硬件安全密钥连接到计算机。 更多信息请参阅 [OpenSSH 8.2 发行说明](https://www.openssh.com/txt/release-8.2)。
+
+## 生成新 SSH 密钥
+
+You can generate a new SSH key on your local machine. After you generate the key, you can add the key to your account on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable authentication for Git operations over SSH.
+
+{% data reusables.ssh.key-type-support %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Paste the text below, substituting in your {% data variables.product.product_name %} email address.
-    {% ifversion ghae %}
+2. 粘贴下面的文本（替换为您的 {% data variables.product.product_name %} 电子邮件地址）。
+   {%- ifversion ghae %}
     <!-- GitHub AE is FIPS 140-2 compliant. FIPS does not yet permit keys that use the ed25519 algorithm. -->
-  ```shell
-  $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>" 
-  ```
-    {% else %}
-  ```shell
-  $ ssh-keygen -t ed25519 -C "<em>your_email@example.com</em>"
-  ```
-  {% note %}
+   ```shell
+   $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>" 
+   ```
+   {%- else %}
+   ```shell
+   $ ssh-keygen -t ed25519 -C "<em>your_email@example.com</em>"
+   ```
+   {% note %}
 
-  **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use:
-  ```shell
-   $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
-  ```
+   **注：**如果您使用的是不支持 Ed25519 算法的旧系统，请使用以下命令：
+   ```shell
+    $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
+   ```
 
-  {% endnote %}
-  {% endif %}
+   {% endnote %}
+   {%- endif %}
 
-  This creates a new SSH key, using the provided email as a label.
-  ```shell
-  > Generating public/private <em>algorithm</em> key pair.
-  ```
-3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.
+   这将以提供的电子邮件地址为标签创建新 SSH 密钥。
+   ```shell
+   > Generating public/private <em>algorithm</em> key pair.
+   ```
+3. 提示您“Enter a file in which to save the key（输入要保存密钥的文件）”时，按 Enter 键。 这将接受默认文件位置。
 
-  {% mac %}
+   {% mac %}
 
-  ```shell
-  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_<em>algorithm</em>): <em>[Press enter]</em>
-  ```
+   ```shell
+   > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_<em>algorithm</em>): <em>[Press enter]</em>
+   ```
 
-  {% endmac %}
+   {% endmac %}
 
-  {% windows %}
+   {% windows %}
 
-  ```shell
-  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_<em>algorithm</em>):<em>[Press enter]</em>
-  ```
+   ```shell
+   > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_<em>algorithm</em>):<em>[Press enter]</em>
+   ```
 
-  {% endwindows %}
+   {% endwindows %}
 
-  {% linux %}
+   {% linux %}
 
-  ```shell
-  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/<em>algorithm</em>): <em>[Press enter]</em>
-  ```
+   ```shell
+   > Enter a file in which to save the key (/home/<em>you</em>/.ssh/<em>algorithm</em>): <em>[Press enter]</em>
+   ```
 
-  {% endlinux %}
+   {% endlinux %}
 
-4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
-  ```shell
-  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
-  > Enter same passphrase again: <em>[Type passphrase again]</em>
-  ```
+4. 在提示时输入安全密码。 更多信息请参阅“[使用 SSH 密钥密码](/articles/working-with-ssh-key-passphrases)”。
+   ```shell
+   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+   > Enter same passphrase again: <em>[Type passphrase again]</em>
+   ```
 
-## Adding your SSH key to the ssh-agent
+## 将 SSH 密钥添加到 ssh-agent
 
-Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. <span class="platform-mac">When adding your SSH key to the agent, use the default macOS `ssh-add` command, and not an application installed by [macports](https://www.macports.org/), [homebrew](http://brew.sh/), or some other external source.</span>
+在向 ssh 代理添加新的 SSH 密钥以管理您的密钥之前，您应该检查现有 SSH 密钥并生成新的 SSH 密钥。 <span class="platform-mac">将 SSH 密钥添加到该代理时，应使用默认的 macOS `ssh-add` 命令，而不是使用通过 [macports](https://www.macports.org/), [homebrew](http://brew.sh/) 或某些其他外部来源安装的应用程序。</span>
 
 {% mac %}
 
 {% data reusables.command_line.start_ssh_agent %}
 
-2. If you're using macOS Sierra 10.12.2 or later, you will need to modify your `~/.ssh/config` file to automatically load keys into the ssh-agent and store passphrases in your keychain.
+2. 如果您使用的是 macOS Sierra 10.12.2 或更高版本，则需要修改 `~/.ssh/config` 文件以自动将密钥加载到 ssh-agent 中并在密钥链中存储密码。
 
-    * First, check to see if your `~/.ssh/config` file exists in the default location.
+   * 首先，检查您的 `~/.ssh/config` 文件是否在默认位置。
 
-      ```shell
-      $ open ~/.ssh/config
-      > The file /Users/<em>you</em>/.ssh/config does not exist.
-      ```
+     ```shell
+     $ open ~/.ssh/config
+     > The file /Users/<em>you</em>/.ssh/config does not exist.
+     ```
 
-    * If the file doesn't exist, create the file.
+   * 如果文件不存在，请创建该文件。
 
-      ```shell
-      $ touch ~/.ssh/config
-      ```
+     ```shell
+     $ touch ~/.ssh/config
+     ```
 
-    * Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup. 
+   * 打开您的 `~/.ssh/config` 文件，然后修改文件以包含以下行。 如果您的 SSH 密钥文件与示例代码具有不同的名称或路径，请修改文件名或路径以匹配您当前的设置。
 
-      ```
-      Host *
-        AddKeysToAgent yes
-        UseKeychain yes
-        IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}
-      ```
+     ```
+     Host *
+       AddKeysToAgent yes
+       UseKeychain yes
+       IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}
+     ```
 
      {% note %}
 
-     **Note:** If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
-  
+     **注意：**
+
+     - If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
+
+     - If you see a `Bad configuration option: usekeychain` error, add an additional line to the configuration's' `Host *` section.
+
+       ```
+       Host *
+         IgnoreUnknown UseKeychain
+       ```
      {% endnote %}
-     
-      {% mac %}
-      {% note %}
 
-      **Note:** If you see an error like this
-
-      ```
-      /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain
-      ```
-
-      add an additional config line to your `Host *` section:
-
-      ```
-      Host *
-        IgnoreUnknown UseKeychain
-      ```
-
-      {% endnote %}
-      {% endmac %}
-  
-3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
+3. 将 SSH 私钥添加到 ssh-agent 并将密码存储在密钥链中。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
-  ```
-  {% note %}
+   ```
+   {% note %}
 
-  **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `-K` option. 
+   **注：**`-K` 选项位于 Apple 的 `ssh-add` 标准版本中，当您将 SSH 密钥添加到 ssh-agent 时，它会将密码存储在您的密钥链中。 如果选择不向密钥添加密码，请运行命令，而不使用 `-K` 选项。
 
-  If you don't have Apple's standard version installed, you may receive an error. For more information on resolving this error, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)."
-  
-  In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively. 
+   如果您没有安装 Apple 的标准版本，可能会收到错误消息。 有关解决此错误的详细信息，请参阅“[错误：ssh-add：非法选项 -- K](/articles/error-ssh-add-illegal-option-k)”。
 
-  {% endnote %}
+   在 MacOS Monterey (12.0) 中， `-K` 和 `-A` 标志已弃用，分别由 `--apple-use-keychain` 和 `--apple-load-keychain` 标志所取代。
 
-4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+   {% endnote %}
+
+4. 将 SSH 密钥添加到 {% data variables.product.product_name %} 上的帐户。 更多信息请参阅“[将新的 SSH 密钥添加到 {% data variables.product.prodname_dotcom %} 帐户](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)”。
 
 {% endmac %}
 
@@ -162,17 +158,17 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 {% data reusables.desktop.windows_git_bash %}
 
-1. Ensure the ssh-agent is running. You can use the "Auto-launching the ssh-agent" instructions in "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)", or start it manually:
-  ```shell
-  # start the ssh-agent in the background
-  $ eval "$(ssh-agent -s)"
-  > Agent pid 59566
-  ```
+1. 确保 ssh-agent 正在运行。 您可以根据“[使用 SSH 密钥密码](/articles/working-with-ssh-key-passphrases)”中的“自动启动 ssh-agent”说明，或者手动启动它：
+   ```shell
+   # start the ssh-agent in the background
+   $ eval "$(ssh-agent -s)"
+   > Agent pid 59566
+   ```
 
-2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
+2. 将 SSH 私钥添加到 ssh-agent。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+3. 将 SSH 密钥添加到 {% data variables.product.product_name %} 上的帐户。 更多信息请参阅“[将新的 SSH 密钥添加到 {% data variables.product.prodname_dotcom %} 帐户](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)”。
 
 {% endwindows %}
 
@@ -180,73 +176,64 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 {% data reusables.command_line.start_ssh_agent %}
 
-2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
+2. 将 SSH 私钥添加到 ssh-agent。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+3. 将 SSH 密钥添加到 {% data variables.product.product_name %} 上的帐户。 更多信息请参阅“[将新的 SSH 密钥添加到 {% data variables.product.prodname_dotcom %} 帐户](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)”。
 
 {% endlinux %}
 
-## Generating a new SSH key for a hardware security key
+## 为硬件安全密钥生成新的 SSH 密钥
 
-If you are using macOS or Linux, you may need to update your SSH client or install a new SSH client prior to generating a new SSH key. For more information, see "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)."
+如果您使用 macOS 或 Linux， 在生成新的 SSH 密钥之前，您可能需要更新 SSH 客户端或安装新的 SSH 客户端。 更多信息请参阅“[错误：未知密钥类型](/github/authenticating-to-github/error-unknown-key-type)”。
 
-1. Insert your hardware security key into your computer.
+1. 将硬件安全密钥插入计算机。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
-  ```shell
-  $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
-  ```
-  
-  {% ifversion not ghae %}
-  {% note %}
+3. 粘贴下面的文本，将电子邮件地址替换为您的 {% data variables.product.product_name %} 帐户的电子邮件地址。
+   ```shell
+   $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
+   ```
 
-  **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
-  ```shell
-   $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
-  ```
+   {%- ifversion not ghae %}
+   {% note %}
 
-  {% endnote %}
-  {% endif %}
-4. When you are prompted, touch the button on your hardware security key.
-5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
+   **注：**如果命令失败，并且您收到错误 `invalid format` 或 `feature not supported`，则表明您可能在使用不支持 Ed25519 算法的硬件安全密钥。 请输入以下命令。
+   ```shell
+    $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
+   ```
 
-  {% mac %}
+   {% endnote %}
+   {%- endif %}
+4. 出现提示时，请触摸硬件安全密钥上的按钮。
+5. 当提示您“Enter a file in which to save the key（输入要保存密钥的文件）”时，按 Enter 接受默认文件位置。
 
-  ```shell
-  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
-  ```
+   {% mac %}
 
-  {% endmac %}
+   ```shell
+   > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
+   ```
 
-  {% windows %}
+   {% endmac %}
 
-  ```shell
-  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):<em>[Press enter]</em>
-  ```
+   {% windows %}
 
-  {% endwindows %}
+   ```shell
+   > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):<em>[Press enter]</em>
+   ```
 
-  {% linux %}
+   {% endwindows %}
 
-  ```shell
-  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
-  ```
+   {% linux %}
 
-  {% endlinux %}
+   ```shell
+   > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
+   ```
 
-6. When you are prompted to type a passphrase, press **Enter**.
-  ```shell
-  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
-  > Enter same passphrase again: <em>[Type passphrase again]</em>
-  ```
-7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+   {% endlinux %}
 
-
-## Further reading
-
-- "[About SSH](/articles/about-ssh)"
-- "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)"
-{%- ifversion fpt or ghec %}
-- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
-{%- endif %}
+6. 当提示您输入密码时，按 **Enter**。
+   ```shell
+   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+   > Enter same passphrase again: <em>[Type passphrase again]</em>
+   ```
+7. 将 SSH 密钥添加到 {% data variables.product.prodname_dotcom %} 上的帐户。 更多信息请参阅“[将新的 SSH 密钥添加到 {% data variables.product.prodname_dotcom %} 帐户](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)”。
diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
index 633c82e4a2..625afebe3d 100644
--- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
+++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
@@ -17,7 +17,9 @@ topics:
 shortTitle: SSH 密钥密码
 ---
 
-使用 SSH 密钥时，如果有人获得您计算机的访问权限，他们也可以使用该密钥访问每个系统。 要添加额外的安全层，可以向 SSH 密钥添加密码。 您可以使用 `ssh-agent` 安全地保存密码，从而不必重新输入。
+## About passphrases for SSH keys
+
+With SSH keys, if someone gains access to your computer, the attacker can gain access to every system that uses that key. 要添加额外的安全层，可以向 SSH 密钥添加密码。 To avoid entering the passphrase every time you connect, you can securely save your passphrase in the SSH agent.
 
 ## 添加或更改密码
 
@@ -103,7 +105,3 @@ unset env
 否则，您可在将密钥添加到 ssh-agent 时在密钥链中存储密码。 更多信息请参阅“[添加 SSH 密钥到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)”。
 
 {% endmac %}
-
-## 延伸阅读
-
-- "[关于 SSH](/articles/about-ssh)"
diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
index 6f05b9af2a..adb05a61f9 100644
--- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
+++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
@@ -28,6 +28,8 @@ Commits and tags have the following verification statuses, depending on whether
 
 {% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
 
+Signing commits differs from signing off on a commit. For more information about signing off on commits, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
 ### Default statuses
 
 | Status         | Description |
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
index a8a23d4df4..a1131a1dfd 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
@@ -1,7 +1,7 @@
 ---
-title: Browsing security advisories in the GitHub Advisory Database
-intro: 'You can browse the {% data variables.product.prodname_advisory_database %} to find advisories for security risks in open source projects that are hosted on {% data variables.product.company_short %}.'
-shortTitle: Browse Advisory Database
+title: 浏览 GitHub Advisory 数据库中的安全通告
+intro: '您可以浏览 {% data variables.product.prodname_advisory_database %} ，查找有关托管在 {% data variables.product.company_short %} 上的开源项目中的安全风险的公告。'
+shortTitle: 浏览公告数据库
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
@@ -11,6 +11,8 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Security advisories
@@ -19,126 +21,147 @@ topics:
   - Vulnerabilities
   - CVEs
 ---
+
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
 
-## About the {% data variables.product.prodname_advisory_database %}
+## 关于 {% data variables.product.prodname_advisory_database %}
 
-The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities and malware, grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
+The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
 
 {% data reusables.repositories.tracks-vulnerabilities %}
 
-## About types of security advisories
+## 关于安全公告的类型
 
 {% data reusables.advisory-database.beta-malware-advisories %}
 
-Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects or for malicious open source software. 
+Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}.
 
-{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
+{% data reusables.repositories.a-vulnerability-is %} 代码中的漏洞通常是偶然引入的，在发现后不久就被修复。 您应该在依赖项的固定版本可用时立即更新代码以使用该版本。
 
-In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
+{% ifversion GH-advisory-db-supports-malware %}
 
-### {% data variables.product.company_short %}-reviewed advisories
+相反，恶意软件或恶意软件是故意设计用于执行不需要或有害功能的代码。 恶意软件可能以硬件、软件、机密数据或使用恶意软件的任何应用程序的用户为目标。 您需要从项目中删除恶意软件，并找到依赖项的替代，更安全的替代品。
 
-{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities or malware that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
+{% endif %}
 
-Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
+### {% data variables.product.company_short %} 审核的公告
 
-- Composer (registry: https://packagist.org/)
-- Erlang (registry: https://hex.pm/)
-- Go (registry: https://pkg.go.dev/)
-- Maven (registry: https://repo1.maven.org/maven2/org/)
-- npm (registry: https://www.npmjs.com/)
-- NuGet (registry: https://www.nuget.org/)
-- pip (registry: https://pypi.org/)
-- RubyGems (registry: https://rubygems.org/)
-- Rust (registry: https://crates.io/)
+{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. 我们会仔细审查每个公告的有效性，确保它们具有完整的描述，并包含生态系统和软件包信息。
 
-If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
+通常，我们以软件编程语言的关联包注册表命名支持的生态系统。 如果公告针对来自受支持注册表的程序包中的漏洞，我们会对其进行审查。
 
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability or malware for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
+- Erlang (registry: https://hex.pm/){% endif %}
+- Go（注册表：https://pkg.go.dev/）
+- Maven（注册表：https://repo1.maven.org/maven2/org）
+- npm（注册表：https://www.npmjs.com/）
+- NuGet（注册表：https://www.nuget.org/）
+- pip（注册表：https://pypi.org/）
+- RubyGems（注册表：https://rubygems.org/）
+- Rust（注册表：https://crates.io/）
 
-### Unreviewed advisories
+如果您对我们应该支持的新生态系统有任何建议，请打开[议题](https://github.com/github/advisory-database/issues)进行讨论。
 
-Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
+If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %} 警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。
 
-{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
+### 未审核的公告
 
-## About information in security advisories
+未审核的公告是我们直接从国家漏洞数据库源自动发布到 {% data variables.product.prodname_advisory_database %} 的安全漏洞。
 
-Each security advisory contains information about the vulnerability or malware, which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
+{% data variables.product.prodname_dependabot %} 不会为未审核的公告创建 {% data variables.product.prodname_dependabot_alerts %}，因为不会检查此类公告的有效性或完成情况。
 
-The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
-- Low
-- Medium/Moderate
-- High
-- Critical
+## 关于安全公告中的信息
 
-The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
+Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. 此外，国家漏洞数据库列表中的公告包含 CVE 记录链接，通过链接可以查看漏洞、其 CVSS 得分及其质化严重等级的更多详细信息。 更多信息请参阅国家标准和技术研究所 (National Institute of Standards and Technology) 的“[国家漏洞数据库](https://nvd.nist.gov/)”。
+
+我们在[常见漏洞评分系统 (CVSS) 第 5 节](https://www.first.org/cvss/specification-document)中定义了以下四种可能的严重性等级。
+- 低
+- 中
+- 高
+- 关键
+
+{% data variables.product.prodname_advisory_database %} 使用上述 CVSS 级别。 如果 {% data variables.product.company_short %} 获取 CVE，{% data variables.product.prodname_advisory_database %} 将使用 CVSS 版本 3.1。 如果 CVE 是导入的，则 {% data variables.product.prodname_advisory_database %} 支持 CVSS 版本 3.0 和 3.1。
 
 {% data reusables.repositories.github-security-lab %}
 
-## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
+## 访问 {% data variables.product.prodname_advisory_database %} 中的通告
 
-1. Navigate to https://github.com/advisories.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
+1. 导航到 https://github.com/advisories。
+2. （可选）要过滤列表，请使用任意下拉菜单。 ![下拉过滤器](/assets/images/help/security/advisory-database-dropdown-filters.png)
    {% tip %}
 
-   **Tip:** You can use the sidebar on the left to explore  {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
+   **提示：**您可以使用左侧的边栏分别浏览  {% data variables.product.company_short %} 已审核和未审核的公告。
 
    {% endtip %}
-3. Click on any advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.
+3. Click an advisory to view details. 默认情况下，您将看到 {% data variables.product.company_short %} 已审核的安全漏洞公告。 {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %}
 
 
 {% note %}
 
-The database is also accessible using the GraphQL API. By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`. For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
+也可以使用 GraphQL API 访问数据库。 {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
 
 {% endnote %}
 
-## Editing an advisory in the {% data variables.product.prodname_advisory_database %}
-You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)."
+## 在 {% data variables.product.prodname_advisory_database %} 中编辑公告
+您可以对 {% data variables.product.prodname_advisory_database %} 中的任何公告提出改进建议。 更多信息请参阅“[编辑 {% data variables.product.prodname_advisory_database %} 中的安全通告](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)”。
 
-## Searching the {% data variables.product.prodname_advisory_database %}
+## 搜索 {% data variables.product.prodname_advisory_database %}
 
-You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
+您可以搜索数据库，并使用限定符缩小搜索范围。 例如，您可以搜索在特定日期、特定生态系统或特定库中创建的通告。
 
 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example |
-| ------------- | ------------- |
-| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. |
-| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
-| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
-| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
-| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
-| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
-| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
-| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
-| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
-| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
-| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
-| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
-| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
-| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
-| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
-| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
-| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
+| 限定符             | 示例                                                                                                                                  |
+| --------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `type:reviewed` | [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) 将显示 {% data variables.product.company_short %} 已审核的安全漏洞公告。 |
+{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
+{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
+| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | | `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | | `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | | `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | | `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | | `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | | `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | | `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | | `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | | `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | | `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | | `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | | `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | | `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
 
-## Viewing your vulnerable repositories
+## 查看有漏洞的仓库
 
-For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability or malware. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
+For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. 要查看有漏洞的仓库，您必须有权访问该仓库的 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %} 警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)”。
 
-1. Navigate to https://github.com/advisories.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
+1. 导航到 https://github.com/advisories。
+2. 单击通告。
+3. 在通告页面的顶部，单击 **Dependabot alerts（Dependabot 警报）**。 ![Dependabot 警报](/assets/images/help/security/advisory-database-dependabot-alerts.png)
+4. （可选）要过滤列表，请使用搜索栏或下拉菜单。 “Organization（组织）”下拉菜单用于按所有者（组织或用户）过滤 {% data variables.product.prodname_dependabot_alerts %}。 ![用于过滤警报的搜索栏和下拉菜单](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
+5. 有关公告的更多详细信息，以及有关如何修复有漏洞的仓库的建议，请单击仓库名称。
 
-## Further reading
+{% ifversion security-advisories-ghes-ghae %}
+## Accessing the local advisory database on {% data variables.product.product_location %}
 
-- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
+If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.product.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
+
+You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories.
+
+1. Navigate to `https://HOSTNAME/advisories`.
+2. （可选）要过滤列表，请使用任意下拉菜单。 ![下拉过滤器](/assets/images/help/security/advisory-database-dropdown-filters.png)
+   {% note %}
+
+   **Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)".
+
+   {% endnote %}
+3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %}
+
+You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.product.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)".
+
+### Viewing vulnerable repositories for {% data variables.product.product_location %}
+
+{% data reusables.repositories.enable-security-alerts %}
+
+In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. 要查看有漏洞的仓库，您必须有权访问该仓库的 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %} 警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)”。
+
+1. Navigate to `https://HOSTNAME/advisories`.
+2. 单击通告。
+3. 在通告页面的顶部，单击 **Dependabot alerts（Dependabot 警报）**。 ![Dependabot 警报](/assets/images/help/security/advisory-database-dependabot-alerts.png)
+4. （可选）要过滤列表，请使用搜索栏或下拉菜单。 “Organization（组织）”下拉菜单用于按所有者（组织或用户）过滤 {% data variables.product.prodname_dependabot_alerts %}。 ![用于过滤警报的搜索栏和下拉菜单](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
+5. 有关公告的更多详细信息，以及有关如何修复有漏洞的仓库的建议，请单击仓库名称。
+
+{% endif %}
+
+## 延伸阅读
+
+- MITRE 的[“漏洞”定义](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
index cc5dd10e43..7fac857da6 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
@@ -7,6 +7,8 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Security advisories
@@ -19,8 +21,9 @@ shortTitle: 编辑公告数据库
 
 ## 关于在 {% data variables.product.prodname_advisory_database %} 中编辑公告
 [github.com/advisories](https://github.com/advisories) {% data variables.product.prodname_advisory_database %} 中的安全公告被视为全局公告。 任何人都可以在 {% data variables.product.prodname_advisory_database %} 中对任何全局安全公告提出改进建议。 您可以编辑或添加任何详细信息，包括其他受影响的生态系统、严重性级别或受影响者的描述。 {% data variables.product.prodname_security %} 管理团队将审查提交的改进，并在接受时将其发布到 {% data variables.product.prodname_advisory_database %} 上。
+{% ifversion fpt or ghec %}
+只有存储库所有者和管理员才能编辑存储库级别的安全公告。 For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
 
-只有存储库所有者和管理员才能编辑存储库级别的安全公告。 更多信息请参阅“[编辑存储库安全通告](/code-security/security-advisories/editing-a-security-advisory)”。
 ## 在 GitHub Advisory 数据库中编辑通告
 
 1. 导航到 https://github.com/advisories。
@@ -30,4 +33,15 @@ shortTitle: 编辑公告数据库
 5. 完成对公告的编辑后，单击 **Submit improvements（提交改进）**。
 6. 提交改进后，将创建一个包含您的更改的拉取请求，以供 {% data variables.product.prodname_security %} 策展团队在 [github/advisory-database](https://github.com/github/advisory-database) 中进行审核。 如果公告源自 {% data variables.product.prodname_dotcom %} 存储库，我们还将标记原始发布者以提供可选评论。 您可以查看拉取请求，并在其更新或关闭时收到通知。
 
-您还可以直接在 [github/advisory-database](https://github.com/github/advisory-database) 存储库中的公告文件上打开拉取请求。 更多信息请参阅[参与指南](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md)。 
+您还可以直接在 [github/advisory-database](https://github.com/github/advisory-database) 存储库中的公告文件上打开拉取请求。 更多信息请参阅[参与指南](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md)。
+
+{% ifversion security-advisories-ghes-ghae %}
+## Editing advisories from {% data variables.product.product_location %}
+
+If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.product.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url.
+
+1. Navigate to `https://HOSTNAME/advisories`.
+2. 选择您要参与的安全公告。
+3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on Github.com.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}. ![建议改进链接](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png)
+4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above.
+{% endif %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
index d0775db71c..156c69f77b 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
@@ -57,7 +57,7 @@ topics:
 
 ## 保护您的通信令牌
 
-代码通常需要通过网络与其他系统通信，并且需要机密（如密码或 API 密钥）进行身份验证。 系统需要访问这些机密才能运行，但最佳做法是不将它们包含在源代码中。 这对于公共存储库尤其重要，但对于许多人可能有权访问的私有存储库也尤其重要。
+代码通常需要通过网络与其他系统通信，并且需要机密（如密码或 API 密钥）进行身份验证。 系统需要访问这些机密才能运行，但最佳做法是不将它们包含在源代码中。 This is especially important for repositories to which many people might have access{% ifversion not ghae %} and critical for public repositories{% endif %}.
 
 ### 自动检测提交到存储库的机密
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index ed9358a0c2..7d3517de96 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -70,7 +70,7 @@ The recommended formats explicitly define which versions are used for all direct
 | Package manager | Languages | Recommended formats | All supported formats |
 | --- | --- | --- | ---|
 {%- ifversion dependency-graph-rust-support %}
-| Cargo<sup>[*]</sup> | Rust | `Cargo.lock` | `Cargo.toml`, `Cargo.lock` | 
+| Cargo{% ifversion ghes = 3.6 or ghae-issue-7563 %}<sup>[*]</sup>{% endif %} | Rust | `Cargo.lock` | `Cargo.toml`, `Cargo.lock` | 
 {%- endif %}
 | Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |
 | NuGet | .NET languages (C#, F#, VB), C++  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
@@ -91,7 +91,7 @@ The recommended formats explicitly define which versions are used for all direct
 | RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
 | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
 
-{% ifversion dependency-graph-rust-support %}
+{% ifversion ghes = 3.6 or ghae-issue-7563 %}
 [*] For the initial release of Rust support, dependency graph does not have the metadata and mappings required to detect transitive dependencies. Dependency graph displays transitive dependencies, one level deep, when they are defined in a `Cargo.lock` file. {% data variables.product.prodname_dependabot_alerts %} and {% data variables.product.prodname_dependabot_security_updates %} are available for vulnerable dependencies defined in the `Cargo.lock` file.
 {% endif %}
 
diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
index 848ae45182..b3333c47c3 100644
--- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
+++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
@@ -2,8 +2,7 @@
 title: About discussions
 intro: 'Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
@@ -22,7 +21,7 @@ You might use repository discussions to discuss topics that are specific to the
 
 You don't need to close a discussion like you close an issue or a pull request.
 
-If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who visits the repository can create and participate in discussions for the repository. If an organization owner enables {% data variables.product.prodname_discussions %} for an organization, anyone who can view the source repository can create an organization discussion.
+If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who has access to the repository can create and participate in discussions for the repository. If an organization owner enables {% data variables.product.prodname_discussions %} for an organization, anyone who can view the source repository can create an organization discussion.
 
 Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. Similarly, for organization discussions, the role of a user in the source repository determines how a user can interact with organization discussions. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
@@ -30,7 +29,7 @@ For more information about management of discussions, see "[Managing discussions
 
 ## About polls
 
-You can create polls in the polls category to gauge interest in new ideas and project direction. Anyone with read access to your repository can create polls, vote in polls, and view their results. Logged out users can view the results of polls in public repositories.
+You can create polls in the polls category to gauge interest in new ideas and project direction. Anyone with read access to your repository can create polls, vote in polls, and view their results.{% ifversion fpt or ghec %} Signed out users can view the results of polls in public repositories.{% endif %}
 
 Polls require a question and at least two options. You can add a maximum of eight options and the options can contain a maximum of 128 characters. 
 
@@ -71,5 +70,5 @@ You can share your feedback about {% data variables.product.prodname_discussions
 - "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)"
 - "[Searching discussions](/search-github/searching-on-github/searching-discussions)"
 - "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
-- "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)"
-- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"
+- "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)"{% ifversion fpt or ghec %}
+- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"{% endif %}
diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
index 53c2d80265..10715ddd4d 100644
--- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
+++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
@@ -4,8 +4,7 @@ shortTitle: 与维护者协作
 intro: '您可以通过在讨论中与项目的维护者沟通，为 {% data variables.product.product_name %} 项目的目标、计划、运行状况和社区做出贡献。'
 permissions: 'People with read access to a repository can start and participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can start and participate in discussions and polls in the organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
@@ -53,4 +52,6 @@ versions:
 ## 延伸阅读
 
 - “[关于 {% data variables.product.prodname_dotcom %} 上的书写和格式化](/github/writing-on-github/about-writing-and-formatting-on-github)”
+{%- ifversion fpt or ghec %}
 - “[在 {% data variables.product.prodname_dotcom %} 上维护您的安全](/communities/maintaining-your-safety-on-github)”
+{%- endif %}
diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/index.md
index d73db82785..f708000f5c 100644
--- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/index.md
+++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/index.md
@@ -3,8 +3,7 @@ title: 使用讨论与社区协作
 shortTitle: 使用讨论进行协作
 intro: 与社区成员和其他维护者一起收集和讨论您的项目。
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 children:
   - /about-discussions
   - /participating-in-a-discussion
diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index 379ce8a90a..1b5385ee2e 100644
--- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -3,8 +3,7 @@ title: 参与讨论
 intro: '您可以在仓库的论坛中与社区和维护者交流 {% data variables.product.product_name %} 上的项目。'
 permissions: 'People with read access to a repository can participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can participate in discussions and polls in that organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: 参与讨论
 ---
 
@@ -15,7 +14,7 @@ shortTitle: 参与讨论
 
 除了开始或查看讨论和投票之外，您还可以根据讨论作者的原始评论发表评论。 您还可以通过回复其他社区成员在讨论中进行的个人评论，以及使用表情符号对评论做出反应来创建评论线程。
 
-您可以阻止用户并报告破坏性内容，以便自己在 {% data variables.product.product_name %} 上保持一个安全愉快的环境。 更多信息请参阅“[保持您在 {% data variables.product.prodname_dotcom %} 上的安全](/communities/maintaining-your-safety-on-github)”。
+{% ifversion fpt or ghec %}You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)."{% endif %}
 
 ## 基本要求
 
diff --git a/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md
index d7c5ff434d..8d6f2f4b78 100644
--- a/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md
+++ b/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md
@@ -3,8 +3,7 @@ title: GitHub 上社区对话的最佳实践
 shortTitle: 社区对话的最佳实践
 intro: 您可以使用讨论与团队进行头脑风暴，并在准备好确定工作范围时最终将对话移动到议题中。
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
@@ -22,7 +21,7 @@ versions:
 
 您可以创建和参与讨论、议题及拉取请求，具体取决于您希望进行的对话类型。
 
-您可以使用 {% data variables.product.prodname_discussions %} 讨论大局想法、集思广益，并在将项目提交到议题之前，先找出项目的具体细节，然后可以确定议题的范围。 {% data variables.product.prodname_discussions %} 在以下情况下对团队有用：
+您可以使用 {% data variables.product.prodname_discussions %} 讨论大局想法、集思广益，并在将项目提交到议题之前，先找出项目的具体细节，然后可以确定议题的范围。 {% data variables.product.prodname_discussions %} is useful for teams in a number of scenarios.
 - 您处于项目的发现阶段，仍在了解您的团队希望由哪个主管领导
 - 您希望从更广泛的社区收集有关项目的反馈
 - 您希望将漏洞修复、功能请求和常规对话分开
@@ -34,7 +33,7 @@ versions:
 
 ## 遵守参与指南
 
-在开源存储库中打开讨论之前，请检查该存储库是否有参与指南。 CONTRIBUTING 文件包含仓库维护员希望您如何向项目贡献想法的信息。
+Before you open a discussion in a repository, check to see if the repository has contributing guidelines. CONTRIBUTING 文件包含仓库维护员希望您如何向项目贡献想法的信息。
 
 更多信息请参阅“[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
 
diff --git a/translations/zh-CN/content/discussions/guides/finding-your-discussions.md b/translations/zh-CN/content/discussions/guides/finding-your-discussions.md
index 7f5c96ba01..4c956960d5 100644
--- a/translations/zh-CN/content/discussions/guides/finding-your-discussions.md
+++ b/translations/zh-CN/content/discussions/guides/finding-your-discussions.md
@@ -2,8 +2,7 @@
 title: 查找讨论
 intro: 您可以轻松访问您创建或参与的每个讨论。
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: 查找讨论
 redirect_from:
   - /discussions/guides/finding-discussions-across-multiple-repositories
@@ -12,8 +11,7 @@ redirect_from:
 
 ## 查找讨论
 
-1. 导航至 {% data variables.product.prodname_dotcom_the_website %}。
-1. 在 {% data variables.product.prodname_dotcom_the_website %} 的右上角，单击您的个人资料照片，然后单击 **Your discussions（您的讨论）**。 ![{% data variables.product.product_name %} 上个人资料照片下拉菜单中的"您的讨论"](/assets/images/help/discussions/your-discussions.png)
+1. 在 {% data variables.product.product_location %} 的右上角，单击您的个人资料照片，然后单击 **Your discussions（您的讨论）**。 ![{% data variables.product.product_name %} 上个人资料照片下拉菜单中的"您的讨论"](/assets/images/help/discussions/your-discussions.png)
 1. 在 **Created（已创建）**与 **Commented（已评论）**之间切换，以查看您创建或参与的讨论。
 
 ## 延伸阅读
diff --git a/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
index e494a37138..9ac08ef0ef 100644
--- a/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
+++ b/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
@@ -2,8 +2,7 @@
 title: 向顶级贡献者授予更高的权限
 intro: 仓库管理员可以将任何社区成员提升到主持人和维护员。
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: 授予更高权限
 ---
 
@@ -16,11 +15,11 @@ shortTitle: 授予更高权限
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
-1. 将贡献者列表与其对存储库的访问权限进行比较，或者，对于组织讨论，比较源存储库，以查看谁有资格主持讨论。
+1. Compare the list of contributors with their access permissions to the repository or, for organization discussions, to the source repository to see who qualifies to moderate the discussion. ![Screenshot of most helpful contributors](/assets/images/help/discussions/most-helpful.png)
 
 ## 第 2 步：审查 {% data variables.product.prodname_discussions %} 的权限级别
 
-对仓库具有分类权限的人可以通过将评论标记为答案、锁定不再有用或对社区造成损害的讨论，以及在想法仍处于开发的早期阶段时将问题转换为讨论，从而帮助主持仓库的讨论。 同样，对组织讨论的源存储库具有分类权限的人员可以主持组织的讨论。 更多信息请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)”。
+People with triage permissions for a repository can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. 同样，对组织讨论的源存储库具有分类权限的人员可以主持组织的讨论。 更多信息请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)”。
 
 有关仓库权限级别和 {% data variables.product.prodname_discussions %} 的更多信息，请参阅“[组织的仓库权限级别](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)”。
 
diff --git a/translations/zh-CN/content/discussions/guides/index.md b/translations/zh-CN/content/discussions/guides/index.md
index 46eabf532e..cda195f322 100644
--- a/translations/zh-CN/content/discussions/guides/index.md
+++ b/translations/zh-CN/content/discussions/guides/index.md
@@ -3,8 +3,7 @@ title: 讨论指南
 shortTitle: 指南
 intro: 了解开始或学习参与或监控社区讨论的最佳做法的途径。
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 children:
   - /best-practices-for-community-conversations-on-github
   - /finding-your-discussions
diff --git a/translations/zh-CN/content/discussions/index.md b/translations/zh-CN/content/discussions/index.md
index cfb7e452af..0c313a5f24 100644
--- a/translations/zh-CN/content/discussions/index.md
+++ b/translations/zh-CN/content/discussions/index.md
@@ -1,7 +1,7 @@
 ---
 title: GitHub Discussions 文档
 shortTitle: GitHub Discussions
-intro: '{% data variables.product.prodname_discussions %} 是一个围绕开源项目为社区提供协作沟通的论坛。 社区成员可以提出和回答问题，分享更新，进行开放式对话，并关注影响社区工作方式的决策。'
+intro: '{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an{% ifversion fpt or ghec %} open source or{% endif %} internal project. 社区成员可以提出和回答问题，分享更新，进行开放式对话，并关注影响社区工作方式的决策。'
 introLinks:
   quickstart: /discussions/quickstart
 featuredLinks:
@@ -27,8 +27,7 @@ examples_source: data/product-examples/discussions/community-examples.yml
 product_video: 'https://www.youtube-nocookie.com/embed/IpBw2SJkFyk'
 layout: product-landing
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 communityRedirect:
   name: Provide GitHub Feedback
   href: 'https://github.com/github/feedback/discussions/categories/discussions-feedback'
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
index a6c5cde2d9..f719d50bf2 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
@@ -3,8 +3,7 @@ title: 管理社区的讨论
 shortTitle: 管理讨论
 intro: '您可以为仓库启用和配置 {% data variables.product.prodname_discussions %}，还可以使用 {% data variables.product.product_name %} 上的工具主持社区成员之间的对话。'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 children:
   - /managing-discussions
   - /managing-categories-for-discussions
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
index 1f5c5821bc..31fe5ab1d5 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
@@ -3,8 +3,7 @@ title: 管理讨论的类别
 intro: 您可以对讨论进行分类以组织社区成员的对话，并且可以为每个类别选择格式。
 permissions: Repository administrators and people with write or greater access to a repository can manage categories for discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage categories for discussions in the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: 管理类别
 redirect_from:
   - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository
@@ -43,7 +42,7 @@ redirect_from:
 
 您可以编辑类别以更改类别的表情符号、标题、说明和讨论格式。
 
-1. 在 {% data variables.product.product_location %} 上，导航到要在其中创建类别的存储库或组织的主页。
+1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to edit a category.
 {% data reusables.discussions.discussions-tab %}
 1. 在列表中类别右侧，单击 {% octicon "pencil" aria-label="The pencil icon" %}。 ![仓库类别列表中类别右侧的编辑按钮](/assets/images/help/discussions/click-edit-for-category.png)
 1. {% data reusables.discussions.edit-category-details %}
@@ -54,7 +53,7 @@ redirect_from:
 
 删除类别时，{% data variables.product.product_name %} 会将已删除类别中的所有讨论移到您选择的现有类别。
 
-1. 在 {% data variables.product.product_location %} 上，导航到要在其中创建类别的存储库或组织的主页。
+1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to delete a category.
 {% data reusables.discussions.discussions-tab %}
 1. 在列表中类别右侧，单击 {% octicon "trash" aria-label="The trash icon" %}。 ![仓库类别列表中类别右侧的垃圾桶按钮](/assets/images/help/discussions/click-delete-for-category.png)
 1. 使用下拉菜单，为要删除的类别中的任何讨论选择新类别。 ![删除现有类别时用于选择新类别的下拉菜单](/assets/images/help/discussions/choose-new-category.png)
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md
index bf7774f176..67be05421e 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -3,8 +3,7 @@ title: 管理讨论
 intro: 您可以对讨论进行分类、聚焦、转让或删除。
 permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: 管理讨论
 redirect_from:
   - /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
@@ -17,7 +16,7 @@ redirect_from:
 
 组织所有者可以选择为组织拥有的仓库创建讨论所需的权限。 同样，要选择创建组织讨论所需的权限，组织所有者可以更改源存储库中所需的权限。 更多信息请参阅“[管理组织中仓库的讨论创建](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)”。
 
-作为讨论维护者，您可以创建社区资源，以鼓励与总体项目目标一致的讨论，并为协作者维护一个友好、开放的论坛。 为协作者制定行为守则或参与指南将有助于促进协作和富有成效的论坛。 有关创建社区资源的更多信息，请参阅“[为项目中添加行为准则](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)”和“[设置仓库参与者指南](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)”。
+作为讨论维护者，您可以创建社区资源，以鼓励与总体项目目标一致的讨论，并为协作者维护一个友好、开放的论坛。 Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and{% endif %} "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
 
 当讨论产生可以解决的想法或漏洞时，您可以从讨论创建新议题。 更多信息请参阅“[创建议题](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)”。
 
@@ -75,7 +74,7 @@ redirect_from:
 
 ## 转让讨论
 
-要转让讨论，您必须具有在要转让讨论的仓库中创建讨论的权限。 如果要将讨论转移到组织，您必须有权限在源存储库中为组织的讨论创建讨论。 您只能在同一用户或组织帐户拥有的仓库之间转让讨论。 您无法将私有仓库的讨论转让给公共仓库。
+要转让讨论，您必须具有在要转让讨论的仓库中创建讨论的权限。 如果要将讨论转移到组织，您必须有权限在源存储库中为组织的讨论创建讨论。 您只能在同一用户或组织帐户拥有的仓库之间转让讨论。 You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository.
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
index da81e55a6d..4ff78371c6 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
@@ -1,16 +1,15 @@
 ---
 title: 主持讨论
-intro: 您可以通过将评论标记为答案、锁定或解锁讨论、将议题转换为讨论，以及编辑或删除评论、讨论和不符合社区行为准则的类别，以促进健康的协作。
+intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.'
 permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 ---
 
 
 ## 关于主持讨论
 
-{% data reusables.discussions.about-discussions %}如果您对仓库具有分类权限，便可通过将评论标记为答案、锁定不再有用或对社区造成损害的讨论，以及在想法仍处于开发的早期阶段时将问题转换为讨论，从而帮助主持仓库的讨论。 同样，如果您具有组织讨论的源存储库的分类权限，则可以主持该组织的讨论。
+{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. 同样，如果您具有组织讨论的源存储库的分类权限，则可以主持该组织的讨论。
 
 ## 将评论标记为答案
 
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
index c912567e70..ce72866422 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
@@ -3,8 +3,7 @@ title: 查看讨论的见解
 intro: 讨论见解提供有关讨论的活动、视图和参与者的数据。
 permissions: Repository administrators and people with maintain access to a repository can view the insights dashboard for discussions in that repository. Repository administrators and people with maintain access to the source repository for organization discussions can view the insights dashboard for discussions in that organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Discussions
 shortTitle: 查看讨论见解
diff --git a/translations/zh-CN/content/discussions/quickstart.md b/translations/zh-CN/content/discussions/quickstart.md
index ad3e93a5aa..a1f75f9158 100644
--- a/translations/zh-CN/content/discussions/quickstart.md
+++ b/translations/zh-CN/content/discussions/quickstart.md
@@ -3,21 +3,20 @@ title: GitHub Discussions 快速入门
 intro: '在现有仓库或组织上启用 {% data variables.product.prodname_discussions %} ，并发起与社区的对话。'
 allowTitleToDifferFromFilename: true
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: 快速入门
 ---
 
 
 ## 简介
 
-{% data variables.product.prodname_discussions %} 是一个围绕开源项目为社区提供协作沟通的论坛。 不像 {% data variables.product.prodname_github_issues %}，讨论用于需要透明和可访问的对话，但不需要在项目板上进行跟踪，并且与代码无关。 讨论使公共论坛中能够进行流畅、公开的对话。
+{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source or internal project. 不像 {% data variables.product.prodname_github_issues %}，讨论用于需要透明和可访问的对话，但不需要在项目板上进行跟踪，并且与代码无关。 讨论使公共论坛中能够进行流畅、公开的对话。
 
 通过连接和提供更集中的区域来连接和查找信息，讨论为更多协作对话提供了空间。
 
 ## 在仓库中启用 {% data variables.product.prodname_discussions %}
 
-仓库所有者和具有写入访问权限的人可在其公共和私有仓库中为社区启用 {% data variables.product.prodname_discussions %}。
+Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public{% ifversion ghes > 3.5 %}, internal{% endif %} and private repositories. The visibility of a discussion is inherited from the repository the discussion is created in.
 
 当您首次启用 {% data variables.product.prodname_discussions %} 时，将邀请您配置欢迎帖子。
 
@@ -42,7 +41,7 @@ shortTitle: 快速入门
 
 ## 为贡献者设置社区指南
 
-对于仓库讨论，您可以设置参与指南，以鼓励协作者进行与仓库相关的有意义、有用的对话。 您还可以更新仓库的 README，以传达协作者何时应打开问题或讨论的期望。 有关为项目提供指南的更多信息，请参阅“[为项目添加行为准则](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)”和“[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
+对于仓库讨论，您可以设置参与指南，以鼓励协作者进行与仓库相关的有意义、有用的对话。 您还可以更新仓库的 README，以传达协作者何时应打开问题或讨论的期望。 For more information about providing guidelines for your project, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and{% endif %} "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
 
 对于组织讨论，您可以通过创建组织配置文件 README 来共享有关如何与组织互动的信息。 更多信息请参阅“[自定义组织的配置文件](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)”。
 
@@ -62,7 +61,7 @@ shortTitle: 快速入门
 
 仓库所有者和对仓库具有写入权限的人可以创建新类别来保持讨论井然有序。 同样，由于组织讨论基于源存储库，因此存储库所有者和对源存储库具有写入访问权限的人员可以为组织讨论创建新类别。
 
-参与和创建新讨论的协作者可以将讨论分组到最相关的现有类别。 讨论也可以在创建后重新分类。 更多信息请参阅“[管理讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)”。
+Collaborators participating in and creating new discussions can group discussions into the most relevant existing categories. 讨论也可以在创建后重新分类。 更多信息请参阅“[管理讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)”。
 
 {% data reusables.discussions.you-can-label-discussions %}
 
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md
index 82e83fdb37..c0693210f6 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md
@@ -136,7 +136,7 @@ Notifications provide updates about the activity on {% data variables.product.pr
 ### 8. Working with {% data variables.product.prodname_pages %}
 You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 ### 9. Using {% data variables.product.prodname_discussions %}
 You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
 {% endif %}
diff --git a/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md b/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md
index a4328502c5..73ae95ff70 100644
--- a/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md
+++ b/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md
@@ -23,10 +23,9 @@ topics:
 
 {% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
-{% endif %}
-{% ifversion ghes or ghae %}
+{% else %}
 You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
 {% endif %}
 
@@ -99,7 +98,7 @@ The **Files changed** tab of the pull request shows the implemented fix.
 - The user creates a pull request with the fix.
 - A repository maintainer reviews the pull request, comments on it, and merges it.
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 ### Scenarios for {% data variables.product.prodname_discussions %}
 
 - I have a question that's not necessarily related to specific files in the repository.
@@ -146,8 +145,8 @@ For issues, for example, you can tag issues with labels for quicker searching an
 
 For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)."
 
-{% ifversion fpt or ghec %}
-For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+{% ifversion discussions %}
+For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt or ghec %} set up a code of conduct and{% endif %} pin discussions that contain important information for your community. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
 {% endif %}
 
 For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
diff --git a/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md b/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
index 22cf70e9d6..42d6c629f6 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
@@ -47,7 +47,7 @@ versions:
 | <kbd>G</kbd> <kbd>P</kbd> | 转到 **Pull requests（拉取请求）**选项卡。 更多信息请参阅“[关于拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)”。{% ifversion fpt or ghes or ghec %}
 | <kbd>G</kbd> <kbd>A</kbd> | 转到 **Actions（操作）**选项卡。 更多信息请参阅“[关于 Actions](/actions/getting-started-with-github-actions/about-github-actions)”。{% endif %}
 | <kbd>G</kbd> <kbd>B</kbd> | 转到 **Projects（项目）**选项卡。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。                                                                                                                                   |
-| <kbd>G</kbd> <kbd>W</kbd> | 转到 **Wiki** 选项卡。 更多信息请参阅“[关于 wiki](/communities/documenting-your-project-with-wikis/about-wikis)”。{% ifversion fpt or ghec %}
+| <kbd>G</kbd> <kbd>W</kbd> | 转到 **Wiki** 选项卡。 更多信息请参阅“[关于 wiki](/communities/documenting-your-project-with-wikis/about-wikis)”。{% ifversion discussions %}
 | <kbd>G</kbd> <kbd>G</kbd> | 转到 **Discussions（讨论）**选项卡。 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。{% endif %}
 
 ## 源代码编辑
diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
index 3668cf5dd6..fc1bc87fe4 100644
--- a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
+++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
@@ -70,7 +70,7 @@ Look! You can see my backticks.
 {% ifversion mermaid %}
 ## 创建图表
 
-您还可以使用代码块在 Markdown 中创建关系图。 GitHub 支持 Mermaid、geoJSON、topoJSON 和 ASCII STL 语法。 更多信息请参阅“[创建示意图](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)”。
+您还可以使用代码块在 Markdown 中创建关系图。 GitHub 支持 Mermaid、GeoJSON、TopoJSON 和 ASCII STL 语法。 更多信息请参阅“[创建示意图](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)”。
 
 {% endif %}
 ## 延伸阅读
diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
index daae4ab297..416dbd96f2 100644
--- a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
+++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
@@ -38,11 +38,11 @@ graph TD;
 
 {% endnote %}
 
-## 创建 geoJSON 和 topoJSON 地图
+## 创建 GeoJSON 和 TopoJSON 地图
 
-您可以使用 geo/topoJSON 语法来创建交互式地图。 要创建地图，请在具有 `geojson` 或 `topojson` 语法标识符的受防护代码块中添加 geoJSON 或 topoJSON。 更多信息请参阅“[创建和突出显示代码块](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)”。
+You can use GeoJSON/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. 更多信息请参阅“[创建和突出显示代码块](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)”。
 
-### 使用 geoJSON
+### Using GeoJSON
 
 例如，您可以创建一个简单的地图：
 
@@ -77,9 +77,9 @@ graph TD;
 
 ![渲染的地图](/assets/images/help/writing/fenced-geojson-rendered-map.png)
 
-### 使用 topoJSON
+### Using TopoJSON
 
-例如，您可以创建一个简单的 topoJSON 地图：
+For example, you can create a simple TopoJSON map:
 
 <pre>
 ```topojson
diff --git a/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md
index 49823fa9ed..0412ac7357 100644
--- a/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md
+++ b/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -2,8 +2,7 @@
 title: 使用 GraphQL API for Discussions
 intro: '了解如何使用 {% data variables.product.prodname_discussions %} GraphQL API。'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: 使用 GraphQL 进行讨论
 ---
 
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md
index 7b9a23e3fd..68e43804df 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -48,7 +48,8 @@ topics:
 
 您可以在议题中@提及能访问您的仓库的协作者，以提请他们注意评论。 要将相关议题链接到同一仓库，您可以键入 `#`，后接议题标题的一部分，然后点击要链接的议题。 为了沟通责任，您可以分配议题。 如果您发现自己经常输入相同的评论，可以使用已保存的回复。
 {% ifversion fpt or ghec %} 更多信息请参阅“[基本编写和格式语法](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)”和“[将议题和拉取请求分配到其他 GitHub 用户](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)”。
-
+{% endif %}
+{% ifversion discussions %}
 ## 比较议题和讨论
 
 有些对话更适合 {% data variables.product.prodname_discussions %}。 {% data reusables.discussions.you-can-use-discussions %} 有关何时使用议题或讨论的指导，请参阅“[在 GitHub 上沟通](/github/getting-started-with-github/quickstart/communicating-on-github)”。
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index 8187cb26de..5715c8f116 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -90,7 +90,7 @@ gh issue create --title "My new issue" --body "Here are more details." --assigne
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 
 ## 从讨论创建议题
 
diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
index 1307b3d3ee..1bde7a7e92 100644
--- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
+++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -1,6 +1,6 @@
 ---
 title: 关于组织
-intro: 'Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once, with sophisticated security and administrative features.'
+intro: 组织是共享帐户，企业和开源项目可以同时跨多个项目进行协作，具有复杂的安全性和管理功能。
 redirect_from:
   - /articles/about-organizations
   - /github/setting-up-and-managing-organizations-and-teams/about-organizations
@@ -18,20 +18,20 @@ topics:
 
 {% data reusables.organizations.about-organizations %} 有关帐户类型的详细信息，请参阅“[{% data variables.product.prodname_dotcom %} 帐户的类型](/get-started/learning-about-github/types-of-github-accounts)”。
 
-You can invite an unlimited number of people to join your organization, then give these organization members a variety of roles that grant different levels of access to the organization and its data. 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。
+您可以邀请不限数量的人员加入您的组织，然后为这些组织成员提供各种角色，以授予对组织及其数据的不同级别的访问权限。 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。
 
-In addition to managing access to the organization itself, you can separately manage access to your organization's repositories, project boards, and apps. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)", "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)", and "[Managing access to your organization's apps](/organizations/managing-access-to-your-organizations-apps)."
+除了管理对组织本身的访问外，您还可以单独管理对组织存储库、项目板和应用程序的访问。 更多信息请参阅“[组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”、“[组织的项目板权限](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)”和“[管理对组织应用程序的访问](/organizations/managing-access-to-your-organizations-apps)”。
 
-To simplify access management and enhance collaboration, you can create nested teams that reflect your group's structure, with cascading access permissions and mentions. 更多信息请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。
+为了简化访问管理并增强协作，您可以创建反映组结构的嵌套团队，并具有级联访问权限和提及。 更多信息请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。
 
-You can configure the organization to meet the unique needs of your group by managing settings, such as restricting the types of repositories that members can create. For more information, see "[Managing organization settings](/organizations/managing-organization-settings)."
+您可以通过管理设置（例如限制成员可以创建的存储库类型）来配置组织以满足组的独特需求。 更多信息请参阅“[管理组织设置](/organizations/managing-organization-settings)”。
 
-To harden your organization's security, you can enforce security requirements and review the organization's audit log. 更多信息请参阅“[保护组织安全](/organizations/keeping-your-organization-secure)”。
+为加强组织的安全性，可以强制实施安全要求并查看组织的审核日志。 更多信息请参阅“[保护组织安全](/organizations/keeping-your-organization-secure)”。
 
 {% data reusables.organizations.org-ownership-recommendation %} 更多信息请参阅“[管理组织的所有权连续性](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)”。
 
 {% ifversion fpt or ghec %}
-## About feature availability
+## 关于功能可用性
 
 {% data reusables.organizations.organization-plans %}
 {% endif %}
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
index 4aa44e907a..219fb4280e 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -816,4 +816,6 @@ For more information, see "[Managing the publication of {% data variables.produc
 ## Further reading
 
 - "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %}
+{%- ifversion fpt or ghec %}
 - "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
+{%- endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
index 553ca3278c..4b67ae1211 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
@@ -140,7 +140,7 @@ shortTitle: 存储库角色
 | [存档仓库](/articles/about-archiving-repositories)                                                                                                                                                                                                                                                                                                                                                                         |       |       |       |       |                 **X** |{% ifversion fpt or ghec %}
 | 显示赞助按钮（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）。                                                                                                                                                                                                                                                                                                                                   |       |       |       |       |                         **X** 
 {% endif %}
-| 创建到外部资源的自动链接引用，如 Jira 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”）                                                                                                                                                                                                                                                                                                 |       |       |       |       |                 **X** |{% ifversion fpt or ghec %}
+| 创建到外部资源的自动链接引用，如 Jira 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”）                                                                                                                                                                                                                                                                                                 |       |       |       |       |                 **X** |{% ifversion discussions %}
 | 在仓库中[启用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)                                                                                                                                                                                                                                                               |       |       |       | **X** |                                **X**                                |
 | 为 {% data variables.product.prodname_discussions %} [创建和编辑类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)                                                                                                                                                                                                                                                                |       |       |       | **X** |                                **X**                                |
 | [将讨论移动到其他类别](/discussions/managing-discussions-for-your-community/managing-discussions)                                                                                                                                                                                                                                                                                                                                |       |       | **X** | **X** |                                **X**                                |
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
index ccfe89d1b1..a9eba76639 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
@@ -3,8 +3,7 @@ title: 为组织启用或禁用 GitHub 讨论
 intro: '您可以使用组织中的 {% data variables.product.prodname_discussions %} 作为组织进行对话的位置，这些对话不特定于组织中的单个存储库。'
 permissions: 'Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Organizations
 shortTitle: 组织讨论
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/index.md b/translations/zh-CN/content/organizations/managing-organization-settings/index.md
index e0000d7a2f..59d6301bff 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/index.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/index.md
@@ -27,6 +27,7 @@ children:
   - /allowing-people-to-delete-issues-in-your-organization
   - /enabling-or-disabling-github-discussions-for-an-organization
   - /managing-discussion-creation-for-repositories-in-your-organization
+  - /managing-the-commit-signoff-policy-for-your-organization
   - /setting-team-creation-permissions-in-your-organization
   - /managing-scheduled-reminders-for-your-organization
   - /managing-the-default-branch-name-for-repositories-in-your-organization
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index 643025c828..f18cfd68c3 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -5,8 +5,7 @@ redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization
 permissions: Organization owners can manage discussion creation for repositories owned by the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Organizations
   - Teams
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
new file mode 100644
index 0000000000..66928608d1
--- /dev/null
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
@@ -0,0 +1,25 @@
+---
+title: Managing the commit signoff policy for your organization
+intro: 'You can require users to automatically sign off all commits they make in {% data variables.product.product_name %}''s web interface to repositories owned by your organization.'
+versions:
+  feature: commit-signoffs
+permissions: Organization owners can require all commits to repositories owned by the organization be signed off by the commit author.
+topics:
+  - Organizations
+shortTitle: Manage the commit signoff policy
+---
+
+## About commit signoffs
+
+To affirm that a commit complies with the rules and licensing governing a repository, many organizations require developers to sign off on every commit. If your organization requires commit signoffs, you can make signing off a seamless part of the commit process by enabling compulsory commit signoffs for users committing through {% data variables.product.product_name %}'s web interface. After you enable compulsory commit signoffs for an organization, every commit made to repositories in that organization through {% data variables.product.product_name %}'s web interface will automatically be signed off on by the commit author.
+
+People with admin access to a repository can also enable compulsory commit signoffs at the repository level. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
+{% data reusables.repositories.commit-signoffs %}
+
+## Managing compulsory commit signoffs for your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.repository-defaults %}
+1. Select or deselect **Require contributors to sign off on web-based commits**. ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/organizations/require-signoffs.png)
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index a1c5aabea3..debe8758bb 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -22,6 +22,9 @@ shortTitle: 管理成员名称的显示
 
 每个组织成员在自己的设置中选择自己的个人资料名称。 更多信息请参阅“[个性化您的个人资料](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)”。
 
+{% ifversion profile-name-enterprise-setting %}
+You may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)”。{% endif %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
index 19c556c236..c5da05e4d3 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -49,7 +49,7 @@ redirect_from:
 
 仅当继承的角色中尚未包含其他权限时，才能选择该权限。 例如，如果继承的角色提供对存储库**写入**访问权限，则“关闭拉取请求”权限将已包含在继承的角色中。
 
-{% ifversion ghec %}
+{% ifversion discussions %}
 ### Discussions
 
 - **创建讨论类别**：能够创建新的讨论类别。 更多信息请参阅“[创建新类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)”。
diff --git a/translations/zh-CN/content/packages/index.md b/translations/zh-CN/content/packages/index.md
index 6ebdcb6fc2..4773b4809f 100644
--- a/translations/zh-CN/content/packages/index.md
+++ b/translations/zh-CN/content/packages/index.md
@@ -12,10 +12,11 @@ featuredLinks:
     - /packages/learn-github-packages/installing-a-package
   popular:
     - /packages/working-with-a-github-packages-registry/working-with-the-npm-registry
-    - '{% ifversion fpt or ghec or ghes > 3.4 %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}'
+    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
     - /packages/learn-github-packages
     - /packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry
   guideCards:
+    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
     - '{% ifversion fpt or ghec or ghes > 3.4 %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}'
     - /packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry
 changelog:
diff --git a/translations/zh-CN/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/zh-CN/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
index 426cebe418..b545f54286 100644
--- a/translations/zh-CN/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
+++ b/translations/zh-CN/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -16,7 +16,7 @@ shortTitle: 访问控制和可见性
 
 具有精细权限的包仅限于个人用户或组织帐户。 您可以从与包相连（或链接）的仓库分别更改包的访问控制和可见性。
 
-目前，您只能对 {% data variables.product.prodname_container_registry %} 使用粒度权限。 粒度权限不支持我们的其他软件包注册表，如 npm 注册表。
+目前，您只能对 {% data variables.product.prodname_container_registry %} 使用粒度权限。 Granular permissions are not supported in our other package registries, such as the npm registry.{% ifversion docker-ghcr-enterprise-migration %} For more information about migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."{% endif %}
 
 有关仓库作用域的包、与包相关的 PAT 作用域或管理操作工作流程的权限的更多信息，请参阅“[关于 GitHub Packages 的权限](/packages/learn-github-packages/about-permissions-for-github-packages)”。
 
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
index a310417b14..140ed74059 100644
--- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -1,6 +1,6 @@
 ---
 title: 从 Docker 注册表迁移到容器注册表
-intro: '先前存储在 Docker 注册表中的 Docker 映像将自动迁移到 {% data variables.product.prodname_container_registry %}。'
+intro: '{% ifversion docker-ghcr-enterprise-migration %}An enterprise owner can{% else %}{% data variables.product.company_short %} will{% endif %} migrate Docker images previously stored in the Docker registry on {% data variables.product.product_location %} to the {% data variables.product.prodname_container_registry %}.'
 product: '{% data reusables.gated-features.packages %}'
 redirect_from:
   - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
@@ -9,35 +9,61 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: 迁移到容器注册表
+  feature: docker-ghcr-enterprise-migration
+shortTitle: Migration to Container registry
+topics:
+  - Containers
+  - Docker
+  - Migration
 ---
 
-{% data variables.product.prodname_dotcom %} 的 Docker 注册表已被 {% data variables.product.prodname_container_registry %} 取代。 如果您已将 Docker 映像存储在 Docker 注册表中，它们将自动移动到 {% data variables.product.prodname_container_registry %}。 您不需要任何操作。 使用 Docker 注册表 (`docker.pkg.github.com`) 名称空间的任何脚本或 {% data variables.product.prodname_actions %} 工作流程在迁移到 {% data variables.product.prodname_container_registry %} (`ghcr.io`)后将继续运行。
+{% data reusables.package_registry.container-registry-ghes-beta %}
 
-迁移逐步进行，而不是一次性完成。 如果您的映像尚未移动，请抓紧，我们很快就会收到它们。
+## 关于 {% data variables.product.prodname_container_registry %}
 
-## 如何判断您的映像是否已迁移？
+{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
 
-在 Docker 映像迁移到 {% data variables.product.prodname_container_registry %} 后，您将在包的详细信息页面上看到以下更改：
+## About migration from the Docker registry
 
-* 图标现在是 {% data variables.product.prodname_container_registry %} 徽标，之前是 Docker 徽标。
-* 拉取 URL 中的域名现在是 `ghcr.io`，以前是 `docker.pkg.github.com`。
+{% data reusables.package_registry.container-registry-replaces-docker-registry %} If you've stored Docker images in the Docker registry, {% ifversion docker-ghcr-enterprise-migration %}an enterprise owner{% else %}{% data variables.product.company_short %}{% endif %} will gradually migrate the images to the {% data variables.product.prodname_container_registry %}. No action is required on your part.
 
-![{% data variables.product.prodname_container_registry %} 详细信息页面](/assets/images/help/package-registry/container-registry-details-page.png)
+{% ifversion docker-ghcr-enterprise-migration %}
 
-## {% data variables.product.prodname_container_registry %} 与 Docker 注册表之间的主要差异
+{% note %}
 
-{% data variables.product.prodname_container_registry %} 进行了优化，以支持容器的一些独特需求。
+**Note**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
 
-通过 {% data variables.product.prodname_container_registry %}，您可以：
-- 将容器映像存储在组织和个人帐户中，或连接到仓库。
-- 选择是从仓库继承权限，还是独立于仓库设置粒度权限。
-- 匿名访问公共容器映像。
+{% endnote %}
 
-### Docker 映像详细信息的 API 查询
+{% endif %}
 
-迁移后，您将无法再使用 GraphQL API 来查询`包类型` "DOCKER"。 相反，您可以使用 REST API 来查询有 `package_type` "container" 的软件包。 更多信息请参阅 REST API 文章“[包](/rest/reference/packages)”。
+After a Docker image has been migrated to the {% data variables.product.prodname_container_registry %}, you'll see the following changes to the details for the package.
 
-## 计费
+- The icon will be the {% data variables.product.prodname_container_registry %} logo instead of the Docker logo.
+- The domain in the pull URL will be {% data variables.product.prodname_container_registry_namespace %} instead of {% data variables.product.prodname_docker_registry_namespace %}.
 
-有关 {% data variables.product.prodname_container_registry %} 计费的更多信息，请参阅“[关于 {% data variables.product.prodname_registry %} 的计费](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)”。
+{% ifversion fpt or ghec %}
+
+![Screenshot of a Docker image migrated to the {% data variables.product.prodname_container_registry %}](/assets/images/help/package-registry/container-registry-details-page.png)
+
+{% endif %}
+
+{% data reusables.package_registry.container-registry-migration-namespaces %}
+
+{% ifversion fpt or ghec %}
+
+After migration, you'll no longer be able to use the GraphQL API to query for packages with a `PackageType` of "DOCKER". Instead, you can use the REST API to query for packages with a `package_type` of "container". For more information, see "[Packages](/rest/reference/packages)" in the REST API documentation.
+
+## 关于 {% data variables.product.prodname_container_registry %} 的计费
+
+For more information about billing for the {% data variables.product.prodname_container_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+
+{% endif %}
+
+{% ifversion docker-ghcr-enterprise-migration %}
+
+## 延伸阅读
+
+- "[Migrating your enterprise to the {% data variables.product.prodname_container_registry %} from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)"
+
+{% endif %}
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
index 72fcea30ab..4a2181ae91 100644
--- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -1,6 +1,6 @@
 ---
-title: Working with the Container registry
-intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://{% data reusables.package_registry.container-registry-hostname %}`.'
+title: 使用容器注册表
+intro: '您可以在 {% data variables.product.prodname_container_registry %} 中存储和管理 Docker 和 OCI 映像，该管理器使用包命名空间 `https://{% data reusables.package_registry.container-registry-hostname %}`。'
 product: '{% data reusables.gated-features.packages %}'
 redirect_from:
   - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images
@@ -18,79 +18,79 @@ versions:
   ghes: '>= 3.5'
 shortTitle: Container registry
 ---
-{% ifversion ghes > 3.4 %}
-{% note %}
 
-**Note**: {% data variables.product.prodname_container_registry %} is currently in beta for {% data variables.product.product_name %} and subject to change.
+{% data reusables.package_registry.container-registry-ghes-beta %}
 
-{% endnote %}
-{% endif %}
+## 关于 {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-benefits %}
 
 {% ifversion ghes > 3.4 %}
-## Prerequisites
 
-To configure and use the {% data variables.product.prodname_container_registry %} on {% data variables.product.prodname_ghe_server %}, your site administrator must first enable {% data variables.product.prodname_registry %} **and** subdomain isolation. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" and "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)."
+To use the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, your site administrator must first configure {% data variables.product.prodname_registry %} for your instance **and** enable subdomain isolation. 更多信息请参阅“[企业的 GitHub Packages 使用入门](/admin/packages/getting-started-with-github-packages-for-your-enterprise)”和“[启用子域隔离](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)”。
+
 {% endif %}
-## About {% data variables.product.prodname_container_registry %} support
 
-The {% data variables.product.prodname_container_registry %} currently supports the following container image formats:
+## 关于 {% data variables.product.prodname_container_registry %} 支持
 
-* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
-* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec)
+{% data variables.product.prodname_container_registry %} 目前支持以下容器映像格式：
 
-When installing or publishing a Docker image, the {% data variables.product.prodname_container_registry %} supports foreign layers, such as Windows images.
+* [Docker 映像清单 V2，架构 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
+* [Open Container Initiative (OCI) 规格](https://github.com/opencontainers/image-spec)
 
-## Authenticating to the {% data variables.product.prodname_container_registry %}
+在安装或发布 Docker 映像时，{% data variables.product.prodname_container_registry %} 支持外部层，如 Windows 映像。
+
+## 向 {% data variables.product.prodname_container_registry %} 验证
 
 {% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
 
-{% ifversion ghes %}Ensure that you replace `HOSTNAME` with {% data variables.product.product_location_enterprise %} hostname or IP address in the examples below.{% endif %}
+{% ifversion ghes %}请确保将下面示例中的 `HOSTNAME` 替换为 {% data variables.product.product_location_enterprise %} 主机名或 IP 地址。{% endif %}
 
 {% data reusables.package_registry.authenticate-to-container-registry-steps %}
 
-## Pushing container images
+## 推送容器映像
 
-This example pushes the latest version of `IMAGE_NAME`.
+此示例推送最新版本的 `IMAGE_NAME`。
   ```shell
   $ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
   ```
 
-This example pushes the `2.5` version of the image.
+此示例推送 `2.5` 版的映像。
   ```shell
   $ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:2.5
   ```
 
-When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+首次发布包时，默认可见性是私有的。 要更改可见性或设置访问权限，请参阅“[配置包的访问控制和可见性](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)”。
 
-## Pulling container images
+## 拉取容器映像
 
-### Pull by digest
+### 通过摘要拉取
 
-To ensure you're always using the same image, you can specify the exact container image version you want to pull by the `digest` SHA value.
+为了确保始终使用相同的映像，您可以通过 `digest` SHA 值指定要拉取的准确容器映像版本。
 
-1. To find the digest SHA value, use `docker inspect` or `docker pull` and copy the SHA value after `Digest:`
+1. 要查找摘要 SHA 值，请使用 `docker inspect` 或 `docker pull`，并复制 `Digest:` 后的 SHA 值
   ```shell
   $ docker inspect {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME
   ```
-2. Remove image locally as needed.
+2. 按需要在本地删除映像。
   ```shell
   $ docker rmi  {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
   ```
 
-3. Pull the container image with `@YOUR_SHA_VALUE` after the image name.
+3. 拉取图像名称后有 `@YOUR_SHA_VALUE` 的容器映像。
   ```shell
   $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs
   ```
 
-### Pull by name
+### 按名称拉取
 
   ```shell
   $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME
   ```
 
-### Pull by name and version
+### 按名称和版本拉取
 
-Docker CLI example showing an image pulled by its name and the `1.14.1` version tag:
+显示按名称和 `1.14.1` 版本标记拉取映像的 Docker CLI 示例：
   ```shell
   $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:1.14.1
   > 5e35bd43cf78: Pull complete
@@ -102,7 +102,7 @@ Docker CLI example showing an image pulled by its name and the `1.14.1` version
   > {% data reusables.package_registry.container-registry-hostname %}/orgname/image-name/release:1.14.1
   ```
 
-### Pull by name and latest version
+### 按名称和最新版本拉取
 
   ```shell
   $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
@@ -112,16 +112,16 @@ Docker CLI example showing an image pulled by its name and the `1.14.1` version
   > {% data reusables.package_registry.container-registry-hostname %}/user/image-name:latest
   ```
 
-## Building container images
+## 构建容器映像
 
-This example builds the `hello_docker` image:
+此示例构建 `hello_docker` 映像：
   ```shell
   $ docker build -t hello_docker .
   ```
 
-## Tagging container images
+## 标记容器映像
 
-1. Find the ID for the Docker image you want to tag.
+1. 找到要标记的 Docker 映像的 ID。
   ```shell
   $ docker images
   > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
@@ -130,7 +130,7 @@ This example builds the `hello_docker` image:
   > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
   ```
 
-2. Tag your Docker image using the image ID and your desired image name and hosting destination.
+2. 使用映像 ID 以及所需的映像名称和托管目标标记 Docker 映像。
   ```shell
   $ docker tag 38f737a91f39 {% data reusables.package_registry.container-registry-hostname %}/OWNER/NEW_IMAGE_NAME:latest
   ```
diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
index 456dc8fca5..68de21f2b5 100644
--- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
+++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
@@ -18,6 +18,9 @@ versions:
 
 {% data reusables.commits.about-commits %}
 
+{% ifversion commit-signoffs %}
+If the repository you are committing to has compulsory commit signoffs enabled, and you are committing via the web interface, you will automatically sign off on the commit as part of the commit process. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)." {% endif %}
+
 您可以对协作处理的任何提交添加合作作者。 更多信息请参阅“[创建有多个作者的提交](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)”。
 
 {% ifversion fpt or ghec %}
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
index dbff10252b..7e3531df4b 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
@@ -1,11 +1,9 @@
 ---
 title: 启用或禁用仓库的 GitHub 讨论
 intro: '您可以将存储库中的 {% data variables.product.prodname_discussions %} 用作社区进行对话、提出问题和发布答案的位置，而无需界定议题的范围。'
-product: '{% data reusables.gated-features.discussions %}'
 permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_discussions %} for the repository.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Repositories
 redirect_from:
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
index c7255ae41f..717327c53c 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
@@ -13,6 +13,7 @@ children:
   - /managing-teams-and-people-with-access-to-your-repository
   - /managing-the-forking-policy-for-your-repository
   - /managing-pull-request-reviews-in-your-repository
+  - /managing-the-commit-signoff-policy-for-your-repository
   - /managing-git-lfs-objects-in-archives-of-your-repository
   - /enabling-anonymous-git-read-access-for-a-repository
   - /about-email-notifications-for-pushes-to-your-repository
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
new file mode 100644
index 0000000000..0e76db15bc
--- /dev/null
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
@@ -0,0 +1,24 @@
+---
+title: Managing the commit signoff policy for your repository
+intro: 'You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}''s web interface.'
+versions:
+  feature: commit-signoffs
+permissions: Organization owners and repository administrators can require all commits to a repository to be signed off by the commit author.
+topics:
+  - Repositories
+shortTitle: Manage the commit signoff policy
+---
+
+## About commit signoffs
+
+Commit signoffs enable users to affirm that a commit complies with the rules and licensing governing a repository. You can enable compulsory commit signoffs on individual repositories for users committing through {% data variables.product.product_location %}'s web interface, making signing off on a commit a seemless part of the commit process. Once compulsory commit signoffs are enabled for a repository, every commit made to that repository through {% data variables.product.product_location %}'s web interface will automatically be signed off on by the commit author.
+
+Organization owners can also enable compulsory commit signoffs at the organization level. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)."
+
+{% data reusables.repositories.commit-signoffs %}
+
+## Enabling or disabling compulsory commit signoffs for your repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Select **Require contributors to sign off on web-based commits**. ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png)
diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index 17ae92c3cc..f1c5f07f02 100644
--- a/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -63,7 +63,7 @@ shortTitle: 管理版本
 ![Releases description](/assets/images/enterprise/3.5/releases/releases_description_auto.png){% endif %}
 1. （可选）要在发行版中包含二进制文件（例如已编译的程序），请在二进制文件框中拖放或手动选择文件。 ![通过发行版提供 DMG](/assets/images/help/releases/releases_adding_binary.gif)
 2. 要通知用户发行版本尚不可用于生产，可能不稳定，请选择 **This is a pre-release（这是预发布）**。 ![将版本标记为预发行版的复选框](/assets/images/help/releases/prerelease_checkbox.png)
-{%- ifversion fpt or ghec %}
+{%- ifversion discussions %}
 1. （可选）如果在存储库中启用了 {% data variables.product.prodname_discussions %}，选择 **Create a discussion for this release（为此版本创建讨论）**，然后选择 **Category（类别）**下拉菜单，然后点击类别进行版本讨论。 ![用于创建发行版讨论和下拉菜单以选择类别的复选框](/assets/images/help/releases/create-release-discussion.png)
 {%- endif %}
 9. 如果您准备推广您的发行版，请单击 **Publish release（发布版本）**。 要在以后处理该发行版，请单击 **Save draft（保存草稿）**。 ![发布版本和草拟发行版按钮](/assets/images/help/releases/release_buttons.png)
diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md
index 110c95186b..b008de22dc 100644
--- a/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md
+++ b/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md
@@ -233,9 +233,9 @@ GitHub 支持呈现 PDF 文档。
 
 一般来说，包含嵌入式 HTML 的文档更改的呈现视图将显示对 {% data variables.product.product_name %} 文档视图中支持元素的更改。 必须始终在呈现视图和源视图中检查对包含嵌入式 HTML 的文档的更改以确保完整性。
 
-## 映射 {% data variables.product.prodname_dotcom %} 上的 geoJSON 文件
+## 映射 {% data variables.product.prodname_dotcom %} 上的 GeoJSON/TopoJSON 文件
 
-{% data variables.product.product_name %} 支持在 {% data variables.product.product_name %} 仓库中渲染 geoJSON 和 topoJSON 地图文件。 只需像平常一样提交扩展名为 `.geojson` 或 `.topojson` 的文件。 也支持扩展名为 `.json` 的文件，但仅当 `type` 设置为 `FeatureCollection`、`GeometryCollection` 或 `topology` 时才支持。 然后导航到 GitHub.com 上 geoJSON 文件的路径。
+{% data variables.product.product_name %} 支持在 {% data variables.product.product_name %} 仓库中渲染 GeoJSON 和 TopoJSON 地图文件。 只需像平常一样提交扩展名为 `.geojson` 或 `.topojson` 的文件。 也支持扩展名为 `.json` 的文件，但仅当 `type` 设置为 `FeatureCollection`、`GeometryCollection` 或 `topology` 时才支持。 然后导航到 GitHub.com 上 GeoJSON/TopoJSON 文件的路径。
 
 单击右侧的纸张图标时，您还会看到在提交时对该文件的更改。
 
@@ -243,12 +243,12 @@ GitHub 支持呈现 PDF 文档。
 
 ### 几何类型
 
-{% data variables.product.product_name %} 上的地图使用 [Leaflet.js](http://leafletjs.com)，并且支持 [geoJSON 规格](http://www.geojson.org/geojson-spec.html)中列出的所有几何类型（Point、LineString、Polygon、MultiPoint、MultiLineString、MultiPolygon 和 GeometryCollection）。 TopoJSON 文件类型应为 "Topology"（拓扑），并且遵守 [topoJSON 规格](https://github.com/mbostock/topojson/wiki/Specification)。
+{% data variables.product.product_name %} 上的地图使用 [Leaflet.js](http://leafletjs.com)，并且支持 [geoJSON 规格](http://www.geojson.org/geojson-spec.html)中列出的所有几何类型（Point、LineString、Polygon、MultiPoint、MultiLineString、MultiPolygon 和 GeometryCollection）。 TopoJSON 文件类型应为 "Topology"（拓扑），并且遵守 [TopoJSON 规格](https://github.com/mbostock/topojson/wiki/Specification)。
 
 {% ifversion geoJSON-with-MapBox %}
 ### 样式功能
 
-您可以传递 geoJSON 对象属性中的其他元数据，自定义功能显示的方式，例如指定特定的颜色或添加描述性图标。 选项包括：
+您可以传递 GeoJSON 对象属性中的其他元数据，自定义功能显示的方式，例如指定特定的颜色或添加描述性图标。 选项包括：
 
 * `marker-size` - `small`、`medium` 或 `large`
 * `marker-color` - 有效的 RGB 十六进制颜色
@@ -264,7 +264,7 @@ GitHub 支持呈现 PDF 文档。
 
 ### 在其他位置嵌入您的地图
 
-想让您的 geoJSON 地图用在 {% data variables.product.product_name %} 以外的地方？ 只需修改此模板，并将其放在任何支持 javascript 的 HTML 页面上（如 [{% data variables.product.prodname_pages %}](http://pages.github.com)）：
+想让您的 geoJSON 地图用在 {% data variables.product.product_name %} 以外的地方？ 只需修改此模板，并将其放在任何支持 JavaScript 的 HTML 页面上（如 [{% data variables.product.prodname_pages %}](http://pages.github.com)）：
 
 ```html
 <script src="https://embed.github.com/view/geojson/<username>/<repo>/<ref>/<path_to_file>"></script>
@@ -287,7 +287,7 @@ GitHub 支持呈现 PDF 文档。
 {% ifversion mermaid %}
 ### 在 Markdown 嵌入地图
 
-您可以直接在 Markdown 中嵌入 geoJSON 和 topoJSON。 更多信息请参阅“[创建示意图](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-geojson-and-topojson-maps)”。
+您可以直接在 Markdown 中嵌入 GeoJSON 和 TopoJSON。 更多信息请参阅“[创建示意图](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-geojson-and-topojson-maps)”。
 {% endif %}
 
 ### 集群
@@ -300,7 +300,7 @@ GitHub 支持呈现 PDF 文档。
 
 ### 疑难解答
 
-如果在渲染 geoJSON 文件时遇到问题，请通过 [geoJSON 语法检查](http://geojsonlint.com/)运行 geoJSON 文件，确认该文件有效。 如果您的地点没有出现在预期的位置（<em>例如</em>在海洋中间），可能是数据在规划中，目前不受支持。 目前，{% data variables.product.product_name %} 只支持 `urn:ogc:def:crs:OGC:1.3:CRS84` 规划。
+如果在渲染 GeoJSON 文件时遇到问题，请通过 [GeoJSON 语法检查](http://geojsonlint.com/)运行 GeoJSON 文件，确认该文件有效。 如果您的地点没有出现在预期的位置（<em>例如</em>在海洋中间），可能是数据在规划中，目前不受支持。 目前，{% data variables.product.product_name %} 只支持 `urn:ogc:def:crs:OGC:1.3:CRS84` 规划。
 
 此外，如果您的 `.geojson` 文件特别大（超过 10 MB），则无法在浏览器中渲染。 在这种情况下，您一般会看到一条类似以下的消息：
 
diff --git a/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md b/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md
index 2475f9038f..d1065ef852 100644
--- a/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md
@@ -400,6 +400,7 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > x-ratelimit-limit: 60
 > x-ratelimit-remaining: 56
+> x-ratelimit-used: 4
 > x-ratelimit-reset: 1372700873
 ```
 
@@ -407,6 +408,7 @@ Header Name | Description
 -----------|-----------|
 `x-ratelimit-limit` | The maximum number of requests you're permitted to make per hour.
 `x-ratelimit-remaining` | The number of requests remaining in the current rate limit window.
+`x-ratelimit-used` | The number of requests you've made in the current rate limit window.
 `x-ratelimit-reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time).
 
 If you need the time in a different format, any modern programming language can get the job done. For example, if you open up the console on your web browser, you can easily get the reset time as a JavaScript Date object.
@@ -423,6 +425,7 @@ If you exceed the rate limit, an error response returns:
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
 > x-ratelimit-limit: 60
 > x-ratelimit-remaining: 0
+> x-ratelimit-used: 60
 > x-ratelimit-reset: 1377013266
 
 > {
@@ -441,6 +444,7 @@ $ curl -u my_client_id:my_client_secret -I {% data variables.product.api_url_pre
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > x-ratelimit-limit: 5000
 > x-ratelimit-remaining: 4966
+> x-ratelimit-used: 34
 > x-ratelimit-reset: 1372700873
 ```
 
@@ -699,4 +703,3 @@ If no `Time-Zone` header is specified and you make an authenticated call to the
 If the steps above don't result in any information, we use UTC as the timezone to create the git commit.
 
 [pagination-guide]: /guides/traversing-with-pagination
-
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md b/translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md
index 4bef4d52be..4fb7ff1a81 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md
@@ -2,8 +2,7 @@
 title: 搜索讨论
 intro: '您可以在 {% data variables.product.product_name %} 上搜索讨论，并使用搜索限定符缩小结果范围。'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - GitHub search
 redirect_from:
diff --git a/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md b/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md
index 7e32fc51c4..0beba8ec7a 100644
--- a/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md
@@ -17,6 +17,8 @@ redirect_from:
   - /github/working-with-github-support/github-enterprise-cloud-support
   - /articles/business-plan-support
   - /articles/github-business-cloud-support
+  - /admin/enterprise-support/about-support-for-advanced-security
+  - /enterprise-server/admin/enterprise-support/about-support-for-advanced-security
 topics:
   - Support
 ---
diff --git a/translations/zh-CN/data/features/GH-advisory-db-erlang-support.yml b/translations/zh-CN/data/features/GH-advisory-db-erlang-support.yml
new file mode 100644
index 0000000000..bfb6aa0a58
--- /dev/null
+++ b/translations/zh-CN/data/features/GH-advisory-db-erlang-support.yml
@@ -0,0 +1,7 @@
+#Reference: Issue #6207.
+#We have added support for Elixir advisories to the Advisory Database.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-6207'
diff --git a/translations/zh-CN/data/features/audit-log-streaming.yml b/translations/zh-CN/data/features/audit-log-streaming.yml
new file mode 100644
index 0000000000..1ff0517353
--- /dev/null
+++ b/translations/zh-CN/data/features/audit-log-streaming.yml
@@ -0,0 +1,5 @@
+#Reference: #7055
+#Documentation for audit log streaming
+versions:
+  ghec: '*'
+  ghes: '>= 3.6'
diff --git a/translations/zh-CN/data/features/commit-signoffs.yml b/translations/zh-CN/data/features/commit-signoffs.yml
new file mode 100644
index 0000000000..26fe611963
--- /dev/null
+++ b/translations/zh-CN/data/features/commit-signoffs.yml
@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6049'
diff --git a/translations/zh-CN/data/features/discussions.yml b/translations/zh-CN/data/features/discussions.yml
new file mode 100644
index 0000000000..66a3bb8592
--- /dev/null
+++ b/translations/zh-CN/data/features/discussions.yml
@@ -0,0 +1,4 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
diff --git a/translations/zh-CN/data/features/docker-ghcr-enterprise-migration.yml b/translations/zh-CN/data/features/docker-ghcr-enterprise-migration.yml
new file mode 100644
index 0000000000..48c1b97cc9
--- /dev/null
+++ b/translations/zh-CN/data/features/docker-ghcr-enterprise-migration.yml
@@ -0,0 +1,4 @@
+#Reference: #7360
+#Documentation for migration from Docker registry to Container registry for enterprise products
+versions:
+  ghes: '>= 3.6'
diff --git a/translations/zh-CN/data/features/ghas-enablement-webhook.yml b/translations/zh-CN/data/features/ghas-enablement-webhook.yml
index cbb4509714..83f8a995bc 100644
--- a/translations/zh-CN/data/features/ghas-enablement-webhook.yml
+++ b/translations/zh-CN/data/features/ghas-enablement-webhook.yml
@@ -2,5 +2,5 @@
 #docs-content 7314. GHAS enablement webhook
 versions:
   ghec: '*'
-  ghes: '>3.6'
+  ghes: '>= 3.6'
   ghae: 'issue-7314'
diff --git a/translations/zh-CN/data/features/motion-management.yml b/translations/zh-CN/data/features/motion-management.yml
new file mode 100644
index 0000000000..573307aac2
--- /dev/null
+++ b/translations/zh-CN/data/features/motion-management.yml
@@ -0,0 +1,7 @@
+#Issue 6523
+#Support for customizing the automatic playback of animated images in the web interface
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6523'
diff --git a/translations/zh-CN/data/features/pause-audit-log-stream.yml b/translations/zh-CN/data/features/pause-audit-log-stream.yml
new file mode 100644
index 0000000000..59bcda81d5
--- /dev/null
+++ b/translations/zh-CN/data/features/pause-audit-log-stream.yml
@@ -0,0 +1,4 @@
+#Reference #4640
+#Documentation for pausing an audit log stream
+versions:
+  ghec: '*'
diff --git a/translations/zh-CN/data/features/require-tls-for-smtp.yml b/translations/zh-CN/data/features/require-tls-for-smtp.yml
new file mode 100644
index 0000000000..dd1f0d2c78
--- /dev/null
+++ b/translations/zh-CN/data/features/require-tls-for-smtp.yml
@@ -0,0 +1,4 @@
+#Reference 7394
+#Documentation for the option to enforce TLS encryption for incoming SMTP connections
+versions:
+  ghes: '>=3.6'
diff --git a/translations/zh-CN/data/features/security-advisories-ghes-ghae.yml b/translations/zh-CN/data/features/security-advisories-ghes-ghae.yml
new file mode 100644
index 0000000000..c4d8f488a5
--- /dev/null
+++ b/translations/zh-CN/data/features/security-advisories-ghes-ghae.yml
@@ -0,0 +1,4 @@
+#Reference: Issue #6982 Community Contributions to Security Advisories - Enterprise 3.6
+versions:
+  ghes: '>=3.6'
+  ghae: 'issue-6982'
diff --git a/translations/zh-CN/data/glossaries/internal.yml b/translations/zh-CN/data/glossaries/internal.yml
index 5e5e22ab40..36a0103e1d 100644
--- a/translations/zh-CN/data/glossaries/internal.yml
+++ b/translations/zh-CN/data/glossaries/internal.yml
@@ -221,7 +221,7 @@
   term: GET
   description: REST API 中的一种方法。
 - 
-  term: geoJSON
+  term: GeoJSON
   description: 用于编码各种地理数据结构的格式。
 - 
   term: GitHub Marketplace 开发者协议
@@ -665,7 +665,7 @@
   description: >-
     可用来代替密码。令牌可以是个人访问令牌、OAuth 令牌或 API 令牌。
 - 
-  term: topoJSON
+  term: TopoJSON
   description: 用于编码拓扑的 GeoJSON 扩展。
 - 
   term: TOTP 应用程序
diff --git a/translations/zh-CN/data/graphql/ghes-3.6/graphql_previews.enterprise.yml b/translations/zh-CN/data/graphql/ghes-3.6/graphql_previews.enterprise.yml
new file mode 100644
index 0000000000..222bca8087
--- /dev/null
+++ b/translations/zh-CN/data/graphql/ghes-3.6/graphql_previews.enterprise.yml
@@ -0,0 +1,123 @@
+- 
+  title: 使用包版本删除
+  description: >-
+    此预览支持允许删除私有包版本 DeletePackageVersion 突变。
+  toggled_by: ':package-deletes-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.deletePackageVersion
+  owning_teams:
+    - '@github/pe-package-registry'
+- 
+  title: 部署
+  description: >-
+    此预览支持部署突变和新部署功能。
+  toggled_by: ':flash-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - DeploymentStatus.environment
+    - Mutation.createDeploymentStatus
+    - CreateDeploymentStatusInput
+    - CreateDeploymentStatusPayload
+    - Mutation.createDeployment
+    - CreateDeploymentInput
+    - CreateDeploymentPayload
+  owning_teams:
+    - '@github/c2c-actions-service'
+- 
+  title: >-
+    >- MergeInfoPreview - 有关拉取请求合并状态的更多详细信息。
+  description: >-
+    此预览支持访问提供有关拉取请求合并状态的更多详细信息的字段。
+  toggled_by: ':merge-info-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - PullRequest.canBeRebased
+    - PullRequest.mergeStateStatus
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: UpdateRefsPreview - 在单个操作中更新多个 ref。
+  description: 此预览支持在单个操作中更新多个 ref。
+  toggled_by: ':update-refs-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateRefs
+    - GitRefname
+    - RefUpdate
+    - UpdateRefsInput
+    - UpdateRefsPayload
+  owning_teams:
+    - '@github/reponauts'
+- 
+  title: 项目事件详细信息
+  description: >-
+    此预览将项目、项目卡和项目列详细信息添加到与项目相关的议题事件。
+  toggled_by: ':starfox-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - AddedToProjectEvent.project
+    - AddedToProjectEvent.projectCard
+    - AddedToProjectEvent.projectColumnName
+    - ConvertedNoteToIssueEvent.project
+    - ConvertedNoteToIssueEvent.projectCard
+    - ConvertedNoteToIssueEvent.projectColumnName
+    - MovedColumnsInProjectEvent.project
+    - MovedColumnsInProjectEvent.projectCard
+    - MovedColumnsInProjectEvent.projectColumnName
+    - MovedColumnsInProjectEvent.previousProjectColumnName
+    - RemovedFromProjectEvent.project
+    - RemovedFromProjectEvent.projectColumnName
+  owning_teams:
+    - '@github/github-projects'
+- 
+  title: 标签预览
+  description: >-
+    此预览支持添加、更新、创建和删除标签。
+  toggled_by: ':bane-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createLabel
+    - CreateLabelPayload
+    - CreateLabelInput
+    - Mutation.deleteLabel
+    - DeleteLabelPayload
+    - DeleteLabelInput
+    - Mutation.updateLabel
+    - UpdateLabelPayload
+    - UpdateLabelInput
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: 导入项目
+  description: 此预览增加了对导入项目的支持。
+  toggled_by: ':slothette-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.importProject
+  owning_teams:
+    - '@github/pe-issues-projects'
+- 
+  title: 团队审查任务预览
+  description: >-
+    此预览支持更新团队审查任务的设置。
+  toggled_by: ':stone-crop-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateTeamReviewAssignment
+    - UpdateTeamReviewAssignmentInput
+    - TeamReviewAssignmentAlgorithm
+    - Team.reviewRequestDelegationEnabled
+    - Team.reviewRequestDelegationAlgorithm
+    - Team.reviewRequestDelegationMemberCount
+    - Team.reviewRequestDelegationNotifyTeam
+  owning_teams:
+    - '@github/pe-pull-requests'
diff --git a/translations/zh-CN/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml b/translations/zh-CN/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml
new file mode 100644
index 0000000000..6a780f3a4d
--- /dev/null
+++ b/translations/zh-CN/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml
@@ -0,0 +1,86 @@
+---
+upcoming_changes:
+  - 
+    location: LegacyMigration.uploadUrlTemplate
+    description: '`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。'
+    reason: '`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。'
+    date: '2019-04-01T00:00:00+00:00'
+    criticality: 重大
+    owner: tambling
+  - 
+    location: AssignedEvent.user
+    description: '`user` 将被删除。使用 `assignee` 字段代替。'
+    reason: 受理人现在可以作为人体模型。
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 重大
+    owner: tambling
+  - 
+    location: UnassignedEvent.user
+    description: '`user` 将被删除。使用 `assignee` 字段代替。'
+    reason: 受理人现在可以作为人体模型。
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 重大
+    owner: tambling
+  - 
+    location: Issue.timeline
+    description: '`timeline` 将被删除。使用 Issue.timelineItems 代替。'
+    reason: '`timeline` 将被删除'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 重大
+    owner: mikesea
+  - 
+    location: PullRequest.timeline
+    description: '`timeline` 将被删除。使用 PullRequest.timelineItems 代替。'
+    reason: '`timeline` 将被删除'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 重大
+    owner: mikesea
+  - 
+    location: MergeStateStatus.DRAFT
+    description: '`DRAFT` 将被删除。改为使用 PullRequest.isDraft。'
+    reason: DRAFT 状态将从这个枚举中删除，应改用 `isDraft`
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: 重大
+    owner: nplasterer
+  - 
+    location: PackageType.DOCKER
+    description: '`DOCKER` 将被删除。'
+    reason: DOCKER 将从这个枚举中移除，因为这种类型将被迁移到仅供软件包 REST API 使用。
+    date: '2021-06-21'
+    criticality: 重大
+    owner: reybard
+  - 
+    location: ReactionGroup.users
+    description: '`user` 将被删除。使用 `reactors` 字段代替。'
+    reason: 反应者现在可以是人体模特、自动程序和组织。
+    date: '2021-10-01T00:00:00+00:00'
+    criticality: 重大
+    owner: synthead
+  - 
+    location: Repository.defaultMergeQueue
+    description: '“defaultMergeQueue” 将被删除。请改用 “Repository.mergeQueue”。'
+    reason: '`defaultMergeQueue` 将被删除。'
+    date: '2022-04-01'
+    criticality: 重大
+    owner: colinshum
+  - 
+    location: AddPullRequestToMergeQueueInput.branch
+    description: '`branch` 将被删除。'
+    reason: PR 被添加到基本分支的合并队列中，`branch` 参数现在是 no-op
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: 重大
+    owner: jhunschejones
+  - 
+    location: Enterprise.userAccounts
+    description: '`userAccounts` 将被删除。使用 `Enterprise.members` 字段代替。'
+    reason: '`Enterprise.userAccounts` 字段被删除。'
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: 重大
+    owner: jdennes
+  - 
+    location: RemovePullRequestFromMergeQueueInput.branch
+    description: '`branch` 将被删除。'
+    reason: PRs are removed from the merge queue for the base branch, the `branch` argument is now a no-op
+    date: '2022-10-01T00:00:00+00:00'
+    criticality: 重大
+    owner: jhunschejones
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/16.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/16.yml
new file mode 100644
index 0000000000..344cc4382e
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/16.yml
@@ -0,0 +1,17 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**MEDIUM**: Prevents an attack where a server-side request forgery (SSRF) could potentially force the Subversion (SVN) bridge to execute remote code by injecting arbitrary data into Memcached."
+    - Updates Grafana to version 7.5.16, which addresses various security vulnerabilities including [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9) and [CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g).
+    - 包已更新到最新的安全版本。
+  bugs:
+    - Fixed an issue where the files inside the artifact zip archives had permissions of 000 when unpacked using an unzip tool. Now the files will have the permissions set to 644, the same way as it works in GitHub.com.
+    - In some cases, the collectd daemon could consume excess memory.
+    - In some cases, backups of rotated log files could accumulate and consume excess storage.
+    - After an upgrade to a new feature release and subsequent configuration run, Elasticsearch could log excessive exceptions while rebuilding indices.
+    - In some cases where a protected branch required more than one approving review, a pull request could be merged with fewer than the required number of approving reviews.
+    - On instances using LDAP authentication, the authentication prompt for sudo mode incorrectly placed the cursor within the password field by default when text fields for both a username and password were visible.
+  changes:
+    - The `ghe-set-password` command-line utility starts required services automatically when the instance is booted in recovery mode.
+    - Metrics for `aqueduct` background processes are gathered for Collectd forwarding and display in the Management Console.
+    - The location of the database migration and configuration run log, `/data/user/common/ghe-config.log`, is now displayed on the page that details a migration in progress.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/11.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/11.yml
new file mode 100644
index 0000000000..8aa91f04f0
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/11.yml
@@ -0,0 +1,18 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**MEDIUM**: Prevents an attack where a server-side request forgery (SSRF) could potentially force the Subversion (SVN) bridge to execute remote code by injecting arbitrary data into Memcached."
+    - "**MEDIUM**: Prevents an attacker from executing Javascript code by exploiting a cross-site scripting (XSS) vulnerability in dropdown UI elements within the GitHub Enterprise Server web interface."
+    - Updates Grafana to version 7.5.16, which addresses various security vulnerabilities including [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9) and [CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g).
+    - 包已更新到最新的安全版本。
+  bugs:
+    - Fixed an issue where the files inside the artifact zip archives had permissions of 000 when unpacked using an unzip tool. Now the files will have the permissions set to 644, the same way as it works in GitHub.com.
+    - In some cases, the collectd daemon could consume excess memory.
+    - In some cases, backups of rotated log files could accumulate and consume excess storage.
+    - After an upgrade to a new feature release and subsequent configuration run, Elasticsearch could log excessive exceptions while rebuilding indices.
+    - In some cases where a protected branch required more than one approving review, a pull request could be merged with fewer than the required number of approving reviews.
+    - On instances using LDAP authentication, the authentication prompt for sudo mode incorrectly placed the cursor within the password field by default when text fields for both a username and password were visible.
+  changes:
+    - The `ghe-set-password` command-line utility starts required services automatically when the instance is booted in recovery mode.
+    - Metrics for `aqueduct` background processes are gathered for Collectd forwarding and display in the Management Console.
+    - The location of the database migration and configuration run log, `/data/user/common/ghe-config.log`, is now displayed on the page that details a migration in progress.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/6.yml
new file mode 100644
index 0000000000..3e1f403ffd
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/6.yml
@@ -0,0 +1,20 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**MEDIUM**: Prevents an attack where a server-side request forgery (SSRF) could potentially force the Subversion (SVN) bridge to execute remote code by injecting arbitrary data into Memcached."
+    - "**MEDIUM**: Prevents an attacker from executing Javascript code by exploiting a cross-site scripting (XSS) vulnerability in dropdown UI elements within the GitHub Enterprise Server web interface."
+    - Updates Grafana to version 7.5.16, which addresses various security vulnerabilities including [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9) and [CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g).
+    - 包已更新到最新的安全版本。
+  bugs:
+    - In some cases, the collectd daemon could consume excess memory.
+    - In some cases, backups of rotated log files could accumulate and consume excess storage.
+    - After an upgrade to a new feature release and subsequent configuration run, Elasticsearch could log excessive exceptions while rebuilding indices.
+    - In some cases where a protected branch required more than one approving review, a pull request could be merged with fewer than the required number of approving reviews.
+    - On instances using LDAP authentication, the authentication prompt for sudo mode incorrectly placed the cursor within the password field by default when text fields for both a username and password were visible.
+    - In some cases, scheduled GitHub Actions workflows could become disabled.
+    - 'The Billing API''s "[Get GitHub Advanced Security active committers for an organization](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)" endpoint now returns `Link` headers to provide information about pagination.'
+    - 'The Billing API''s "[Get GitHub Advanced Security active committers for an organization](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)" endpoint now returns the correct number of total committers.'
+  changes:
+    - The `ghe-set-password` command-line utility starts required services automatically when the instance is booted in recovery mode.
+    - Metrics for `aqueduct` background processes are gathered for Collectd forwarding and display in the Management Console.
+    - The location of the database migration and configuration run log, `/data/user/common/ghe-config.log`, is now displayed on the page that details a migration in progress.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-5/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-5/3.yml
new file mode 100644
index 0000000000..983a608af5
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-5/3.yml
@@ -0,0 +1,22 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**MEDIUM**: Prevents an attack where a server-side request forgery (SSRF) could potentially force the Subversion (SVN) bridge to execute remote code by injecting arbitrary data into Memcached."
+    - "**MEDIUM**: Prevents an attacker from executing Javascript code by exploiting a cross-site scripting (XSS) vulnerability in dropdown UI elements within the GitHub Enterprise Server web interface."
+    - Updates Grafana to version 7.5.16, which addresses various security vulnerabilities including [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9) and [CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g).
+    - 包已更新到最新的安全版本。
+  bugs:
+    - In some cases, the collectd daemon could consume excess memory.
+    - In some cases, backups of rotated log files could accumulate and consume excess storage.
+    - After an upgrade to a new feature release and subsequent configuration run, Elasticsearch could log excessive exceptions while rebuilding indices.
+    - In some cases where a protected branch required more than one approving review, a pull request could be merged with fewer than the required number of approving reviews.
+    - The GitHub Enterprise Importer did not correctly migrate settings for projects within repositories.
+    - On instances using LDAP authentication, the authentication prompt for sudo mode incorrectly placed the cursor within the password field by default when text fields for both a username and password were visible.
+    - The site admin dashboard erroneously included an option to export a report listing dormant users.
+    - 'The Billing API''s "[Get GitHub Advanced Security active committers for an organization](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)" endpoint now returns `Link` headers to provide information about pagination.'
+    - 'The Billing API''s "[Get GitHub Advanced Security active committers for an organization](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)" endpoint now returns the correct number of total committers.'
+    - In the sidebar for an organization's settings, the **Archive** navigation item contained no children.
+  changes:
+    - The `ghe-set-password` command-line utility starts required services automatically when the instance is booted in recovery mode.
+    - Metrics for `aqueduct` background processes are gathered for Collectd forwarding and display in the Management Console.
+    - The location of the database migration and configuration run log, `/data/user/common/ghe-config.log`, is now displayed on the page that details a migration in progress.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml
new file mode 100644
index 0000000000..b8dc55835f
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml
@@ -0,0 +1,216 @@
+date: '2022-07-26'
+release_candidate: true
+deprecated: false
+intro: |
+  {% note %}
+
+  **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend that you only run release candidates in a test environment.
+
+  {% endnote %}
+
+  For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+sections:
+  features:
+    - 
+      heading: 基础架构
+      notes:
+        - |
+          Repository caching is generally available. Repository caching increases Git read performance for distributed developers, providing the data locality and convenience of geo-replication without impact on push workflows. With the general availability release, GitHub Enterprise Server caches both Git and Git LFS data. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+    - 
+      heading: Instance security
+      notes:
+        - |
+          GitHub has changed the supported algorithms and hash functions for all SSH connections to GitHub Enterprise Server, disabled the unencrypted and unauthenticated Git protocol, and optionally allowed the advertisement of an Ed25519 host key. For more information, see the [GitHub Blog](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server/) and the following articles.
+
+          - "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)"
+          - "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)"
+          - "[Configuring host keys for your instance](/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance)"
+        - |
+          You can require TLS encryption for incoming SMTP connections to your instance. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)."
+    - 
+      heading: 审核日志
+      notes:
+        - |
+          You can stream audit log and Git events for your instance to Amazon S3, Azure Blob Storage, Azure Event Hubs, Google Cloud Storage, or Splunk. Audit log streaming is in public beta and subject to change. For more information, see "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
+    - 
+      heading: GitHub Connect
+      notes:
+        - |
+          Server Statistics is now generally available. Server Statistics collects aggregate usage data from your GitHub Enterprise Server instance, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from GitHub Enterprise Server. For more information, see "[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+    - 
+      heading: Administrator experience
+      notes:
+        - |
+          Enterprise owners can join organizations on the instance as a member or owner from the enterprise account's **Organizations** page. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."
+        - |
+          Enterprise owners can allow users to dismiss the configured global announcement banner. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
+    - 
+      heading: GitHub Advanced Security
+      notes:
+        - |
+          Users on an instance with a GitHub Advanced Security license can opt to receive a webhook event that triggers when an organization owner or repository administrator enables or disables a code security or analysis feature. For more information, see the following documentation.
+
+          - "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#security_and_analysis)" in the webhook documentation
+          - "[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)"
+          - "[Managing security and analysis features for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)"
+        - |
+          Users on an instance with a GitHub Advanced Security license can optionally add a comment when dismissing a code scanning alert in the web UI or via the REST API. Dismissal comments appear in the event timeline. Users can also add or retrieve a dismissal comment via the REST API. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests#dismissing-an-alert-on-your-pull-request)" and "[Code Scanning](/rest/code-scanning#update-a-code-scanning-alert)" in the REST API documentation.
+        - |
+          On instances with a GitHub Advanced Security license, secret scanning prevents the leak of secrets in the web editor. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-web-ui)."
+        - |
+          Enterprise owners and users on an instance with a GitHub Advanced Security license can view secret scanning alerts and bypasses of secret scanning's push protection in the enterprise and organization audit logs, and via the REST API. For more information, see the following documentation.
+
+          - "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)"
+          - "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#secret_scanning_push_protection-category-actions)"
+          - "[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#secret_scanning_push_protection-category-actions)"
+          - "[Secret Scanning](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)" in the REST API documentation
+        - |
+          Enterprise owners on an instance with a GitHub Advanced Security license can perform dry runs of custom secret scanning patterns for the enterprise, and all users can perform dry runs when editing a pattern. Dry runs allow you to understand a pattern's impact across the entire instance and hone the pattern before publication and generation of alerts. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+        - |
+          Users on an instance with a GitHub Advanced Security license can use `sort` and `direction` parameters in the REST API when retrieving secret scanning alerts, and sort based on the alert’s `created` or `updated` fields. The new parameters are available for the entire instance, or for individual organizations or repositories. For more information, see the following documentation.
+
+          - "[List secret scanning alerts for an enterprise](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)"
+          - "[List secret scanning alerts for an organization](/rest/secret-scanning#list-secret-scanning-alerts-for-an-organization)"
+          - "[List secret scanning alerts for a repository](/rest/secret-scanning#list-secret-scanning-alerts-for-a-repository)"
+          - "[Secret Scanning](/rest/secret-scanning)" in the REST API documentation
+        - |
+          The contents of the `github/codeql-go` repository have moved to the `github/codeql` repository, to live alongside similar libraries for all other programming languages supported by CodeQL. The open-source CodeQL queries, libraries, and extractor for analyzing codebases written in the Go programming language with GitHub's CodeQL code analysis tools can now be found in the new location. For more information, including guidance on migrating your existing workflows, see [github/codeql-go#741](https://github.com/github/codeql-go/issues/741).
+    - 
+      heading: Dependabot
+      notes:
+        - |
+          Enterprise owners on instances with a GitHub Advanced Security license can see an overview of Dependabot alerts for the entire instance, including a repository-centric view of application security risks, and an alert-centric view of all secret scanning and Dependabot alerts. The views are in beta and subject to change, and alert-centric views for code scanning are planned for a future release of GitHub Enterprise Server. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview#viewing-the-security-overview-for-an-enterprise)."
+        - |
+          Dependabot alerts show users if repository code calls vulnerable functions. Individual alerts display a "vulnerable call" label and code snippet, and users can filter search by `has:vulnerable-calls`. Vulnerable functions are curated during publication to the [GitHub Advisory Database](https://github.com/advisories). New incoming Python advisories will be supported, and GitHub is backfilling known vulnerable functions for historical Python advisories. After beta testing with Python, GitHub will add support for other ecosystems. For more information, see "[Viewing and updating Dependabot alerts](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)."
+        - |
+          Users can select multiple Dependabot alerts, then dismiss or reopen or dismiss the alerts. For example, from the **Closed alerts** tab, you can select multiple alerts that have been previously dismissed, and then reopen them all at once. For more information, see "[About Dependabot alerts](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."
+        - |
+          Dependabot updates `@types` dependencies alongside corresponding packages in TypeScript projects. Before this change, users would see separate pull requests for a package and the corresponding `@types` package. This feature is automatically enabled for repositories containing `@types` packages in the project's `devDependencies` within the _package.json_ file. You can disable this behavior by setting the [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore) field in your `dependabot.yml` file to `@types/*`. For more information, see "[About Dependabot version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)" and "[Configuration options for the _dependabot.yml_ file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file)."
+    - 
+      heading: 代码安全
+      notes:
+        - |
+          GitHub Actions can enforce dependency reviews on users' pull requests by scanning for dependencies, and will warn users about associated security vulnerabilities. The `dependency-review-action` action is supported by a new API endpoint that diffs the dependencies between any two revisions. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)."
+        - |
+          The dependency graph detects _Cargo.toml_ and _Cargo.lock_ files for Rust. These files will be displayed in the **Dependency graph** section of the **Insights** tab. Users will receive Dependabot alerts and updates for vulnerabilities associated with their Rust dependencies. Package metadata, including mapping packages to repositories, will be added at a later date. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
+        - |
+          If GitHub Connect is enabled for your instance, users can contribute an improvement to a security advisory in the [GitHub Advisory Database](https://github.com/advisories). To contribute, click **Suggest improvements for this vulnerability** while viewing an advisory's details. For more information, see the following articles.
+
+          - "[Managing GitHub Connect](/admin/configuration/configuring-github-connect/managing-github-connect)"
+          - "[Browsing security vulnerabilities in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+          - "[About GitHub Security Advisories for repositories](/enterprise-cloud@latest/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)" in the GitHub Enterprise Cloud documentation
+          - "[Editing security advisories in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+    - 
+      heading: GitHub Actions
+      notes:
+        - |
+          Within a workflow that calls a reusable workflow, users can pass the secrets to the reusable workflow with `secrets: inherit`. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow)."
+        - |
+          When using GitHub Actions, to reduce the risk of merging a change that was not reviewed by another person into a protected branch, enterprise owners and repository administrators can prevent Actions from creating pull requests. Organization owners could previously enable this restriction. For more information, see the following articles.
+
+          - "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)"
+          - "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-creating-or-approving-pull-requests)"
+          - "[Managing GitHub 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)"
+        - |
+          Users can write a single workflow triggered by `workflow_dispatch` and `workflow_call`, and use the `inputs` context to access input values. Previously, `workflow_dispatch` inputs were in the event payload, which increased difficulty for workflow authors who wanted to write one workflow that was both reusable and manually triggered. For workflows triggered by `workflow_dispatch`, inputs are still available in the `github.event.inputs` context to maintain compatibility.  For more information, see "[Contexts](/actions/learn-github-actions/contexts#inputs-context)."
+        - |
+          To summarize the result of a job, users can generate Markdown and publish the contents as a job summary. For example, after running tests with GitHub Actions, a summary can provide an overview of passed, failed, or skipped tests, potentially reducing the need to review the full log output. For more information, see "[Workflow commands for GitHub Actions](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)."
+        - |
+          To more easily diagnose job execution failures during a workflow re-run, users can enable debug logging, which outputs information about a job's execution and environment. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)" and "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
+        - |
+          If you manage self-hosted runners for GitHub Actions, you can ensure a consistent state on the runner itself before and after a workflow run by defining scripts to execute. By using scripts, you no longer need to require that users manually incorporate these steps into workflows. Pre- and post-job scripts are in beta and subject to change. For more information, see "[Running scripts before or after a job](/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job)."
+    - 
+      heading: GitHub Packages
+      notes:
+        - |
+          Enterprise owners can migrate container images from the GitHub Docker registry to the GitHub Container registry. The Container registry provides the following benefits.
+
+          - Improves the sharing of containers within an organization
+          - Allows the application of granular access permissions
+          - Permits the anonymous sharing of public container images
+          - Implements OCI standards for hosting Docker images
+
+          The Container registry is in beta and subject to change. For more information, see "[Migrating your enterprise to the Container registry from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)."
+    - 
+      heading: Community experience
+      notes:
+        - |
+          GitHub Discussions is available for GitHub Enterprise Server. GitHub Discussions provides a central gathering space to ask questions, share ideas, and build connections. For more information, see "[GitHub Discussions](/discussions)."
+        - |
+          Enterprise owners can configure a policy to control whether people's usernames or full names are displayed within internal or public repositories. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-display-of-member-names-in-your-repositories)."
+    - 
+      heading: 组织
+      notes:
+        - |
+          Users can create member-only READMEs for an organization. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."
+        - |
+          Organization owners can pin a repository to an organization's profile directly from the repository via the new **Pin repository** dropdown. Pinned public repositories appear to all users of your instance, while public, private, and internal repositories are only visible to organization members.
+    - 
+      heading: 仓库
+      notes:
+        - |
+          While creating a fork, users can customize the fork's name. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
+        - |
+          Users can block creation of branches that match a configured name pattern with the **Restrict pushes that create matching branches** branch protection rule. For example, if a repository's default branch changes from `master` to `main`, a repository administrator can prevent any subsequent creation or push of the `master` branch. For more information, see
+          "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#restrict-who-can-push-to-matching-branches)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)."
+        - |
+          Users can create a branch directly from a repository's **Branches** page by clicking the **New branch**. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+        - |
+          Users can delete a branch that's associated with an open pull request. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+        - |
+          Repositories with multiple licenses display all of the licenses in the "About" sidebar on the {% octicon "code" aria-label="The code icon" %} **Code** tab. For more information, see "[Licensing a repository](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository)."
+        - When a user renames or moves a file to a new directory, if at least half of the file's contents are identical, the commit history indicates that the file was renamed, similar to `git log --follow`. For more information, see the [GitHub Blog](https://github.blog/changelog/2022-06-06-view-commit-history-across-file-renames-and-moves/).
+        - |
+          Users can require a successful deployment of a branch before anyone can merge the pull request associated with the branch. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-deployments-to-succeed-before-merging)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+        - |
+          Enterprise owners can prevent organization owners from inviting collaborators to repositories on the instance. For more information, see "[Enforcing a policy for inviting collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)."
+        - |
+          Users can grant exceptions to GitHub Apps for any branch protection rule that supports exceptions. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+    - 
+      heading: 提交
+      notes:
+        - |
+          For public GPG signing keys that are expired or revoked, GitHub Enterprise Server verifies Git commit signatures and show commits as verified if the user made the commit while the key was still valid. Users can also upload expired or revoked GPG keys. For more information, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
+        - |
+          To affirm that a commit complies with the rules and licensing governing a repository, organization owners and repository administrators can now require developers to sign off on commits made through the web interface. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)" and "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+    - 
+      heading: 拉取请求
+      notes:
+        - |
+          Using the file tree located in the **Files changed** tab of a pull request, users can navigate modified files, understand the size and scope of changes, and focus reviews. The file tree appears if a pull request modifies at least two files, and the browser window is sufficiently wide. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" and "[Filtering files in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+        - |
+          Users can default to using pull requests titles as the commit message for all squash merges. For more information, see "[Configuring commit squashing for pull requests](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)."
+    - 
+      heading: 版本发布
+      notes:
+        - |
+          When viewing the details for a particular release, users can see the creation date for each release asset. For more information, see "[Viewing your repository's releases and tags](/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
+        - While creating a release with automatically generated release notes, users can see the tag identified as the previous release, then choose to select a different tag to specify as the previous release. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
+    - 
+      heading: Markdown
+      notes:
+        - |
+          Editing Markdown in the web interface has been improved.
+
+          - After a user selects text and pastes a URL, the selected text will become a Markdown link to the pasted URL.
+          - When a user pastes spreadsheet cells or HTML tables, the resulting text will render as a table.
+          - When a user copies text containing links, the pasted text will include the link as a Markdown link.
+
+          For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#links)."
+        - |
+          When editing a Markdown file in the web interface, clicking the **Preview** tab will automatically scroll to the place in the preview that you were editing. The scroll location is based on the position of your cursor before you clicked the **Preview** tab.
+  changes:
+    - Interactive elements in the web interface such as links and buttons show a visible outline when focused with a keyboard, to help users find the current position on a page. In addition, when focused, form fields have a higher contrast outline.
+    - If a user refreshes the page while creating a new issue or pull request, the assignees, reviewers, labels and projects will all be preserved.
+  known_issues:
+    - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级过程中被删除。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
+    - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
+    - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。
+    - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+    - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+    - In some cases, users cannot convert existing issues to discussions.
+    - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
diff --git a/translations/zh-CN/data/reusables/advisory-database/beta-malware-advisories.md b/translations/zh-CN/data/reusables/advisory-database/beta-malware-advisories.md
index 94fc49a4c6..3c274857bb 100644
--- a/translations/zh-CN/data/reusables/advisory-database/beta-malware-advisories.md
+++ b/translations/zh-CN/data/reusables/advisory-database/beta-malware-advisories.md
@@ -1,5 +1,5 @@
-{% note %}
+{% ifversion GH-advisory-db-supports-malware %}{% note %}
 
 **Note:** Advisories for malware are currently in beta and subject to change.
 
-{% endnote %}
+{% endnote %}{% endif %}
diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md b/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md
index 4b3cdb42c8..48be014db5 100644
--- a/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md
+++ b/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md
@@ -5,7 +5,7 @@
 | `advisory_credit`   | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 {%- endif %}
 | `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts.
-{%- ifversion ghec %}
+{%- ifversion audit-log-streaming %}
 | `audit_log_streaming`  | Contains activities related to streaming audit logs for organizations in an enterprise account.
 {%- endif %}
 {%- ifversion fpt or ghec %}
diff --git a/translations/zh-CN/data/reusables/discussions/about-organization-discussions.md b/translations/zh-CN/data/reusables/discussions/about-organization-discussions.md
index 5ff3559602..b56cf1d414 100644
--- a/translations/zh-CN/data/reusables/discussions/about-organization-discussions.md
+++ b/translations/zh-CN/data/reusables/discussions/about-organization-discussions.md
@@ -1,5 +1,5 @@
 启用组织讨论时，您将选择组织中的存储库作为组织讨论的源存储库。 您可以使用现有存储库，也可以专门创建存储库来保存组织讨论。 讨论将显示在组织的讨论页面上和源存储库的讨论页面上。
 
-参与或管理组织中讨论的权限基于源存储库中的权限。 例如，用户需要对源存储库的写入权限才能删除组织讨论。 这与用户在存储库中需要写入权限才能删除存储库讨论的方式相同。
+Permission to participate in or manage discussions in your organization is based on permission in the source repository. 例如，用户需要对源存储库的写入权限才能删除组织讨论。 这与用户在存储库中需要写入权限才能删除存储库讨论的方式相同。
 
 您可以随时更改源存储库。 如果更改源存储库，讨论不会传输到新的源存储库。
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/packages-tab.md b/translations/zh-CN/data/reusables/enterprise-accounts/packages-tab.md
new file mode 100644
index 0000000000..1d5447a633
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/packages-tab.md
@@ -0,0 +1 @@
+1. 在左边栏中，单击 **Packages（包）**。
diff --git a/translations/zh-CN/data/reusables/enterprise/about-ssh-ports.md b/translations/zh-CN/data/reusables/enterprise/about-ssh-ports.md
new file mode 100644
index 0000000000..5fbb320011
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise/about-ssh-ports.md
@@ -0,0 +1,5 @@
+Each {% data variables.product.product_name %} instance accepts SSH connections over two ports. Site administrators can access the administrative shell via SSH, then run command-line utilities, troubleshoot, and perform maintenance. Users can connect via SSH to access and write Git data in the instance's repositories. Users do not have shell access to your instance. 更多信息请参阅以下文章。
+
+- "[网络端口](/admin/configuration/configuring-network-settings/network-ports)"
+- "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)"
+- "[关于 SSH](/authentication/connecting-to-github-with-ssh/about-ssh)"
diff --git a/translations/zh-CN/data/reusables/enterprise/apply-configuration.md b/translations/zh-CN/data/reusables/enterprise/apply-configuration.md
new file mode 100644
index 0000000000..a9614acda7
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise/apply-configuration.md
@@ -0,0 +1,12 @@
+1. To apply the configuration, enter the following command.
+
+   {% note %}
+
+   **Note**: During a configuration run, services on {% data variables.product.product_location %} may restart, which can cause brief downtime for users.
+
+   {% endnote %}
+
+    ```shell
+    ghe-config-apply
+    ```
+1. 等待配置运行完毕。
diff --git a/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md b/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md
index 7287ae406d..dd853b88fe 100644
--- a/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md
+++ b/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md
@@ -1,5 +1,7 @@
+{% ifversion ghes < 3.6 %}
 {% note %}
 
 **注意：** 存储库缓存目前处于测试阶段，可能会发生更改。
 
 {% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md
index 123e6c1792..5036fd6f9e 100644
--- a/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md
+++ b/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md
@@ -1,4 +1,5 @@
-1. SSH 连接到 {% data variables.product.product_location %}。 更多信息请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)。”
-```shell
-$ ssh -p 122 admin@<em>HOSTNAME</em>
-```
+1. SSH 连接到 {% data variables.product.product_location %}。 If your instance comprises multiple nodes, for example if high availability or geo-replication are configured, SSH into the primary node. If you use a cluster, you can SSH into any node. For more information about SSH access, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+
+   ```shell
+   $ ssh -p 122 admin@<em>HOSTNAME</em>
+   ```
diff --git a/translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md b/translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
index 6b7357edd6..befff885a2 100644
--- a/translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
+++ b/translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
@@ -1,5 +1,9 @@
 {% warning %}
 
-**注：**如果启用匿名 Git 读取访问，您将对此功能的所有访问和使用负责。 {% data variables.product.company_short %} 对功能的任何非预期访问或误用概不负责。 此外，使用此功能不得违反 {% data variables.product.company_short %} 的许可，包括您向我们订购的用户许可数的限制。
+**警告：**
+
+- The Git protocol is unauthenticated and unencrypted. An attacker could intercept repository data transferred over connections using this protocol.
+- If you enable anonymous Git read access, you're responsible for all access and use of the feature. {% data variables.product.company_short %} is not responsible for any unintended access, security risks, or misuse of the feature.
+- You may not use this feature to violate your license from {% data variables.product.company_short %}, including the limit on the number of user licenses for {% data variables.product.product_location %}.
 
 {% endwarning %}
diff --git a/translations/zh-CN/data/reusables/gated-features/discussions.md b/translations/zh-CN/data/reusables/gated-features/discussions.md
deleted file mode 100644
index 9a299d6435..0000000000
--- a/translations/zh-CN/data/reusables/gated-features/discussions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_discussions %} 可用于 {% data variables.product.prodname_dotcom_the_website %} 上的公共和私有仓库。 {% data reusables.gated-features.more-info-org-products %}
diff --git a/translations/zh-CN/data/reusables/package_registry/container-registry-benefits.md b/translations/zh-CN/data/reusables/package_registry/container-registry-benefits.md
new file mode 100644
index 0000000000..079a514846
--- /dev/null
+++ b/translations/zh-CN/data/reusables/package_registry/container-registry-benefits.md
@@ -0,0 +1 @@
+The {% data variables.product.prodname_container_registry %} stores container images within your organization or personal account, and allows you to associate an image with a repository. You can choose whether to inherit permissions from a repository, or set granular permissions independently of a repository. You can also access public container images anonymously.
diff --git a/translations/zh-CN/data/reusables/package_registry/container-registry-ghes-migration-availability.md b/translations/zh-CN/data/reusables/package_registry/container-registry-ghes-migration-availability.md
new file mode 100644
index 0000000000..5d685d5f4f
--- /dev/null
+++ b/translations/zh-CN/data/reusables/package_registry/container-registry-ghes-migration-availability.md
@@ -0,0 +1 @@
+{% data variables.product.product_name %} 3.6 supports migration for Docker images stored in organizations. A future release will support migration of user-owned images.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/package_registry/container-registry-migration-namespaces.md b/translations/zh-CN/data/reusables/package_registry/container-registry-migration-namespaces.md
new file mode 100644
index 0000000000..9d7d0dc5e0
--- /dev/null
+++ b/translations/zh-CN/data/reusables/package_registry/container-registry-migration-namespaces.md
@@ -0,0 +1 @@
+Any scripts or {% data variables.product.prodname_actions %} workflows that use the namespace for the Docker registry, {% data variables.product.prodname_docker_registry_namespace %}, will continue to work after migration to the {% data variables.product.prodname_container_registry %} at {% data variables.product.prodname_container_registry_namespace %}.
diff --git a/translations/zh-CN/data/reusables/package_registry/container-registry-replaces-docker-registry.md b/translations/zh-CN/data/reusables/package_registry/container-registry-replaces-docker-registry.md
new file mode 100644
index 0000000000..5b6ed35c4f
--- /dev/null
+++ b/translations/zh-CN/data/reusables/package_registry/container-registry-replaces-docker-registry.md
@@ -0,0 +1 @@
+The {% data variables.product.prodname_container_registry %} replaces {% data variables.product.company_short %}'s Docker registry.
diff --git a/translations/zh-CN/data/reusables/package_registry/verify_repository_field.md b/translations/zh-CN/data/reusables/package_registry/verify_repository_field.md
index fe2da77477..31c82fc871 100644
--- a/translations/zh-CN/data/reusables/package_registry/verify_repository_field.md
+++ b/translations/zh-CN/data/reusables/package_registry/verify_repository_field.md
@@ -1 +1 @@
-1. 在项目的 *package.json* 中验证 `repository（仓库）`字段。 `repository（仓库）`字段必须匹配 {% data variables.product.prodname_dotcom %} 仓库的 URL。 例如，如果您的仓库 URL 是 `github.com/my-org/test`，则仓库字段应为 `git://github.com/my-org/test.git`。
+1. 在项目的 *package.json* 中验证 `repository（仓库）`字段。 `repository（仓库）`字段必须匹配 {% data variables.product.prodname_dotcom %} 仓库的 URL。 For example, if your repository URL is `github.com/my-org/test` then the repository field should be `https://github.com/my-org/test.git`.
diff --git a/translations/zh-CN/data/reusables/repositories/commit-signoffs.md b/translations/zh-CN/data/reusables/repositories/commit-signoffs.md
new file mode 100644
index 0000000000..1de17f89af
--- /dev/null
+++ b/translations/zh-CN/data/reusables/repositories/commit-signoffs.md
@@ -0,0 +1,10 @@
+Compulsory commit signoffs only apply to commits made via the web interface. For commits made via the Git command line interface, the commit author must sign off on the commit using the `--signoff` option. For more information, see the [Git documentation](https://git-scm.com/docs/git-commit).
+
+
+You can determine whether a repository you are contributing to has compulsory commit signoffs enabled by checking the header of the commit form at the bottom of the file you are editing. After compulsory commit signoff has been enabled, the header will read "Sign off and commit changes."
+
+![Screenshot of commit commit form with compulsory signoff enabled](/assets/images/help/commits/commit-form-with-signoff-enabled.png)
+
+Before signing off on a commit, you should ensure that your commit is in compliance with the rules and licensing governing the repository you're committing to. The repository may use a sign off agreement, such as the Developer Certificate of Origin from the Linux Foundation. For more information, see the [Developer Certificate of Origin](https://developercertificate.org/).
+
+Signing off on a commit differs from signing a commit. For more information about signing a commit, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/zh-CN/data/reusables/security-advisory/link-browsing-advisory-db.md
index 7a23691721..c37f7d263c 100644
--- a/translations/zh-CN/data/reusables/security-advisory/link-browsing-advisory-db.md
+++ b/translations/zh-CN/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -1,5 +1 @@
-{% ifversion fpt or ghec %}
-For more information, see "[Browsing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)."
-{% else %}
-For more information about advisory data, see "[Browsing security advisories in the {% data variables.product.prodname_advisory_database %}](/free-pro-team@latest/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the {% data variables.product.prodname_dotcom_the_website %} documentation.
-{% endif %}
+更多信息请参阅“[浏览 {% data variables.product.prodname_advisory_database %} 中的安全通告](/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database)”。
diff --git a/translations/zh-CN/data/reusables/server-statistics/release-phase.md b/translations/zh-CN/data/reusables/server-statistics/release-phase.md
deleted file mode 100644
index 17f100fd26..0000000000
--- a/translations/zh-CN/data/reusables/server-statistics/release-phase.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note:** {% data variables.product.prodname_server_statistics %} is in public beta and subject to change.
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/ssh/about-ssh.md b/translations/zh-CN/data/reusables/ssh/about-ssh.md
new file mode 100644
index 0000000000..b4c0c5361a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/ssh/about-ssh.md
@@ -0,0 +1 @@
+You can access and write data in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} using SSH (Secure Shell Protocol). When you connect via SSH, you authenticate using a private key file on your local machine.
diff --git a/translations/zh-CN/data/reusables/ssh/key-type-support.md b/translations/zh-CN/data/reusables/ssh/key-type-support.md
index 72fbc94fa8..0a6708e3d2 100644
--- a/translations/zh-CN/data/reusables/ssh/key-type-support.md
+++ b/translations/zh-CN/data/reusables/ssh/key-type-support.md
@@ -8,4 +8,21 @@
 在 2021 年 11 月 2 日之前 `valid_after` 的 RSA 密钥 (`ssh-rsa`) 可以继续使用任何签名算法。 在该日期之后生成的 RSA 密钥必须使用 SHA-2 签名算法。 某些较旧的客户端可能需要升级才能使用 SHA-2 签名。
 
 {% endnote %}
-{% endif %}
+
+{% elsif ghes = 3.6 or ghes = 3.7 or ghes = 3.8 %}
+
+{% note %}
+
+**Note**: By default with {% data variables.product.product_name %} 3.6 and later, as of the cutoff date of midnight UTC on August 1, 2022, SSH connections that satisfy **both** of the following conditions will fail.
+
+<br/>
+
+{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %}
+
+{% data variables.product.product_name %} 3.6 and later also does not support SSH connections that use DSA, HMAC-SHA-1, or CBC ciphers. RSA SSH keys uploaded before the cutoff date can continue to authenticate using the SHA-1 hash function as long as the key remains valid. For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
+
+Your site administrator can adjust the cutoff date for connections using RSA-SHA-1, and may block all connections using RSA-SHA-1. For more information, contact your site administrator or see "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md b/translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md
new file mode 100644
index 0000000000..d2c95da8a5
--- /dev/null
+++ b/translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md
@@ -0,0 +1,2 @@
+- The RSA key was added to a user account on {% data variables.product.product_location %} after the cutoff date of midnight UTC on August 1, 2022.
+- The SSH client signs the connection attempt with the SHA-1 hash function.
diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml
index c75962bd34..d6b3733427 100644
--- a/translations/zh-CN/data/ui.yml
+++ b/translations/zh-CN/data/ui.yml
@@ -179,7 +179,7 @@ product_landing:
   try_another: 请尝试另一个过滤器或添加您的代码示例。
   no_result: 抱歉，没有与过滤条件匹配的指南。
   learn: 了解如何添加代码示例
-  communities_using_discussions: 使用讨论的社区
+  communities_using_discussions: Communities on GitHub.com using discussions
   add_your_community: 添加您的社区
   sponsor_community: GitHub Sponsors 社区
   supported_releases: 支持的版本
diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml
index 521bb617b5..e3ae38df29 100644
--- a/translations/zh-CN/data/variables/product.yml
+++ b/translations/zh-CN/data/variables/product.yml
@@ -100,6 +100,8 @@ prodname_github_issues: 'GitHub Issues'
 #GitHub Packages
 prodname_registry: 'GitHub Packages'
 prodname_container_registry: 'Container registry'
+prodname_docker_registry_namespace: '{% ifversion fpt or ghec %}`docker.pkg.github.com`{% elsif ghes or ghae %}<code>docker.<em>HOSTNAME</em></code>{% endif %}'
+prodname_container_registry_namespace: '{% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes or ghae %}<code>containers.<em>HOSTNAME</em></code>{% endif %}'
 #GitHub Insights
 prodname_insights: 'GitHub Insights'
 #GitHub Sponsors
diff --git a/translations/zh-CN/data/variables/release_candidate.yml b/translations/zh-CN/data/variables/release_candidate.yml
index ec65ef6f94..d39e7c0f8d 100644
--- a/translations/zh-CN/data/variables/release_candidate.yml
+++ b/translations/zh-CN/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
 ---
-version: ''
+version: enterprise-server@3.6