Merge pull request #54547 from github/repo-sync

Repo sync

Author: docs-bot

content/support/learning-about-github-support/about-github-premium-support.md

@@ -44,8 +44,8 @@ There are two {% data variables.contact.premium_support %} plans: Premium and Pr
 | Training | Access to premium content  | <ul><li>Access to premium content</li><li>1 virtual training class per year</li></ul> |
 | Members with support entitlements | 20 | 40 |
 | Resources | Priority ticket handling | <ul><li>Priority ticket handling</li><li>Named Customer Reliability Engineer</li></ul>   |
-Escalation management | For high and urgent priority tickets | For High and Urgent priority tickets
-Incident management | None | For urgent priority tickets, as needed
+| Escalation management | For High and Urgent priority tickets | For High and Urgent priority tickets |
+| Incident management | None | For Urgent priority tickets, as needed |
 | Health checks | {% ifversion not ghes %}None{% else %}Unlimited automated health check reports (see [Generating a health check for your enterprise](/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)){% endif %} | <ul>{% ifversion ghes %}<li>Unlimited automated health check reports. For more information, see [AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise))</li>{% endif %}<li>Quarterly enhanced health checks, with findings, interpretations, and recommendations from your CRE (by request)</li></ul>    |
 | {% ifversion ghes %} |
 | Crisis prevention | None | Yearly participation in guided incident simulations to help you be prepared |

data/reusables/pull_requests/squash_and_merge_summary.md

@@ -4,4 +4,4 @@ To squash and merge pull requests, you must have [write permissions](/organizati
 
 ![Diagram of commit squashing, where multiple commits from a feature branch are combined into only one commit that is added to `main`.](/assets/images/help/pull_requests/commit-squashing-diagram.png)
 
-You can use squash and merge to create a more streamlined Git history in your repository. Work-in-progress commits are helpful when working on a feature branch, but they aren’t necessarily important to retain in the Git history. If you squash these commits into one commit while merging to the default branch, you can retain the original changes with a clear Git history.
+You can use squash and merge to create a more streamlined Git history in your repository. Work-in-progress commits are helpful when working on a feature branch, but they aren’t necessarily important to retain in the Git history. If you squash these commits into one commit when merging to the default branch, the changes are consolidated, leading to a clear Git history.

data/reusables/support/scope-of-support.md

@@ -8,8 +8,8 @@ If your support request is outside of the scope of what our team can help you wi
 * Configuration of external authentication systems, such as SAML identity providers
 * Open source projects
 * Writing or debugging new queries for {% data variables.product.prodname_codeql %}
-* Cloud provider configurations, such as virtual network setup, custom firewall, or proxy rules.
-* Container orchestration, such as Kubernetes setup, networking, etc.
+* Cloud provider configurations, such as virtual network setup, custom firewall, or proxy rules
+* Container orchestration, such as Kubernetes setup, or networking
 * Detailed assistance with workflows and data management
 * {% data variables.release-phases.public_preview_caps %} features. Support for {% data variables.release-phases.public_preview %} features is out of {% data variables.contact.github_support %}'s scope. {% ifversion ghec or ghes %}For support with {% data variables.release-phases.public_preview %} features, you can contact your account manager on {% data variables.contact.contact_enterprise_sales %}.{% endif %}