fix blocked issue

Author: Albertyang0

learn-pr/github/github-enterprise-server-repository-workflows/3-branch-protection-rules.yml

@@ -1,6 +1,6 @@
 ### YamlMime:ModuleUnit
 uid: learn.github.github-enterprise-server-repository-workflows.branch-protection-rules
-title: Branch Protection Rules and Review Requirements
+title: Branch protections rules and review requirements
 metadata:
   title: Branch Protection Rules and Review Requirements
   description: This content is a part of the Repositories, Branching & Collaboration on GitHub Enterprise Server module.

learn-pr/github/github-enterprise-server-repository-workflows/4-pull-request-review.yml

@@ -1,6 +1,6 @@
 ### YamlMime:ModuleUnit
 uid: learn.github.github-enterprise-server-repository-workflows.pull-request-review
-title: Pull Requests and Code Review on GHES
+title: Pull requests and code review on GHES
 metadata:
   title: Pull Requests and Code Review on GHES
   description: This content is a part of the Repositories, Branching & Collaboration on GitHub Enterprise Server module.

learn-pr/github/github-enterprise-server-repository-workflows/5-collaboration-constraints.yml

@@ -1,6 +1,6 @@
 ### YamlMime:ModuleUnit
 uid: learn.github.github-enterprise-server-repository-workflows.collaboration-constraints
-title: Collaboration Within GHES Constraints
+title: Collaboration within GHES constraints
 metadata:
   title: Collaboration Within GHES Constraints
   description: This content is a part of the Repositories, Branching & Collaboration on GitHub Enterprise Server module.

learn-pr/github/github-enterprise-server-repository-workflows/includes/1-repository-creation-organization.md

@@ -37,7 +37,7 @@ To further support consistency, many organizations rely on repository templates.
 
 Before creating a new repository on GHES, developers should check whether approved templates exist and follow organizational guidance. Using the correct template is often the fastest path to getting started.
 
-### Step-by-Step: Confirm you're in the right repository and understand its standards
+### Step-by-step: Confirm you're in the right repository and understand its standards
 
 If you are joining an existing project, start by verifying you're working in the correct organization and repository, and identify any standards the repository expects you to follow.
 

learn-pr/github/github-enterprise-server-repository-workflows/includes/2-branch-strategies.md

@@ -26,7 +26,7 @@ Strict branching rules help organizations reduce the risk of unreviewed or unsta
 
 For developers, this discipline can initially feel restrictive. Over time, however, it provides clarity and predictability, especially in large teams where uncontrolled branching quickly leads to confusion.
 
-### Step-by-Step: Create a feature branch and keep it up to date
+### Step-by-step: Create a feature branch and keep it up to date
 
 Your organization may have specific naming conventions and rules, but this flow is a common baseline for working safely with a protected default branch.
 

learn-pr/github/github-enterprise-server-repository-workflows/includes/3-branch-protection-rules.md

@@ -16,7 +16,7 @@ Additional protections may prevent force pushes, restrict who can merge changes,
 
 Organizations may also require review from code owners for specific paths, require conversations to be resolved before merging, enforce a specific merge method (such as squash merging), or require a linear commit history. Some enterprises also restrict who can push to protected branches, even through pull requests, to ensure only approved roles can complete merges.
 
-## Repository rulesets: Policy at Scale
+## Repository rulesets: Policy at scale
 
 In addition to traditional branch protection rules, GitHub Enterprise Server supports repository rulesets. Rulesets allow administrators to enforce policies across multiple branches or repositories from a centralized location.
 
@@ -44,7 +44,7 @@ Planning for these steps reduces last-minute delays.
 
 If merging is blocked, use the pull request details to identify exactly which requirement is unmet (for example, missing approvals, unresolved conversations, or failing status checks) before escalating to others.
 
-## Branch queue (Merge queue) for stable integration
+## Branch queue (merge queue) for stable integration
 
 In high-activity repositories, pull requests that pass checks individually can still break the default branch when merged concurrently. Branch queue (merge queue) reduces this risk by validating pull requests in merge order.
 

learn-pr/github/github-enterprise-server-repository-workflows/includes/4-pull-request-review.md

@@ -36,7 +36,7 @@ Reviewers on GHES play an active role in maintaining quality and compliance. The
 
 Because approvals may carry formal accountability, reviewers should be confident in the changes they approve. This reinforces trust in the collaboration process and the stability of protected branches.
 
-### Step-by-Step: Open a pull request and request review
+### Step-by-step: Open a pull request and request review
 
 Exact steps vary by organization, but this flow works in most GHES environments.
 

learn-pr/github/github-enterprise-server-repository-workflows/includes/5-collaboration-constraints.md

@@ -20,7 +20,7 @@ In self-managed environments, platform and DevOps teams are responsible for the
 
 Effective collaboration includes understanding platform constraints, communicating requirements early, and treating platform teams as partners in the development process rather than external service providers.
 
-### Step-by-Step: Diagnose a failing check or workflow (high-level)
+### Step-by-step: Diagnose a failing check or workflow (high-level)
 
 When a required check fails or stays pending, use a methodical approach before escalating.
 

learn-pr/github/github-enterprise-server-repository-workflows/includes/7-summary.md

@@ -6,9 +6,9 @@ In this module, you learned that:
 - Pull requests act as formal change records that support collaboration, traceability, and auditability in enterprise environments.
 - Operational constraints affect collaboration, including self-hosted automation infrastructure, instance-specific feature availability, and coordination with platform teams.
 
-## Learn More
-- Managing accounts and repositories (GHES 3.19): https://docs.github.com/en/[email protected]/admin/managing-accounts-and-repositories
-- About repositories: https://docs.github.com/en/[email protected]/repositories/creating-and-managing-repositories/about-repositories
-- About branches: https://docs.github.com/en/[email protected]/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches
-- About protected branches: https://docs.github.com/en/[email protected]/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches
-- About pull requests: https://docs.github.com/en/[email protected]/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
+## Learn more
+- [Managing accounts and repositories (GHES 3.19)](https://docs.github.com/en/[email protected]/admin/managing-accounts-and-repositories)
+- [About repositories](https://docs.github.com/en/[email protected]/repositories/creating-and-managing-repositories/about-repositories)
+- [About branches](https://docs.github.com/en/[email protected]/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)
+- [About protected branches](https://docs.github.com/en/[email protected]/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches)
+- [About pull requests](https://docs.github.com/en/[email protected]/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)

learn-pr/github/github-enterprise-server-repository-workflows/index.yml

@@ -1,6 +1,6 @@
 ### YamlMime:Module
 uid: learn.github.github-enterprise-server-repository-workflows
-title: GitHub Enterprise Server Fundamentals for Developers
+title: GitHub Enterprise Server fundamentals for developers
 metadata:
   title: GitHub Enterprise Server Fundamentals for Developers
   description: Overview of collaboration on GitHub Enterprise Server (GHES), focusing on governance, branch policies, and pull request workflows.