fix some issues

Author: Albertyang0

learn-pr/github/github-enterprise-server-developer-fundamentals/7-summary.yml

@@ -4,7 +4,7 @@ title: Summary
 metadata:
   unitType: summary
   title: Summary
-  description: 
+  description: This content is a part of the GitHub Enterprise Server Fundamentals for Developers module.
   ms.date: 02/16/2026
   author: camihmerhar
   ms.author: camhernandez

learn-pr/github/github-enterprise-server-developer-fundamentals/includes/1-github-enterprise-server-introduction.md

@@ -8,7 +8,7 @@ This infrastructure may be on-premises, in a private cloud, or hosted with a sup
 
 - Why enterprises choose self-hosted GitHub deployments
 
-- What “self-managed” means for developers and platform teams
+- What "self-managed" means for developers and platform teams
 
 - How GHES fits into regulated and security-sensitive environments
 
@@ -54,16 +54,16 @@ Developer takeaway: GHES prioritizes control and predictability over speed of fe
 In a self-managed GitHub Enterprise Server environment, responsibility for operating GitHub shifts from GitHub to the customer.
 
 - Platform team ownership
- Platform teams manage installation, upgrades, security patching, backups, monitoring, and availability of the GHES instance.
+  Platform teams manage installation, upgrades, security patching, backups, monitoring, and availability of the GHES instance.
 
 - Developer dependencies on platform teams
- Developers rely on internal teams for enabling features, configuring integrations, and resolving infrastructure-related issues.
+  Developers rely on internal teams for enabling features, configuring integrations, and resolving infrastructure-related issues.
 
 - Infrastructure-driven limitations
- Some capabilities-such as GitHub-hosted runners or cloud-native services-are unavailable, requiring developers to adapt workflows.
+  Some capabilities-such as GitHub-hosted runners or cloud-native services-are unavailable, requiring developers to adapt workflows.
 
 - Operational awareness
- Developers must be aware of system constraints, maintenance windows, and version differences that affect day-to-day work.
+  Developers must be aware of system constraints, maintenance windows, and version differences that affect day-to-day work.
 
 ### How GHES fits into regulated and security-sensitive environments
 

learn-pr/github/github-enterprise-server-developer-fundamentals/includes/4-github-enterprise-server-developer-experience.md

@@ -1,6 +1,6 @@
 From a user interface perspective, GHES looks familiar. However, the developer experience differs in meaningful ways, particularly around automation, integrations, and tooling.
 
-### In this unit, you’ll learn
+### In this unit, you'll learn
 
 - How GitHub Actions works on GHES
 
@@ -48,4 +48,4 @@ Developers should verify availability before relying on cloud-first workflows.
 
 Key takeaway: The GHES developer experience is shaped by self-managed infrastructure-automation, integrations, and even “available features” can depend on what is deployed, licensed, and enabled in your environment.
 
-Now that you’ve seen how GHES can differ in everyday development workflows, the next unit introduces GitHub Connect and hybrid scenarios that can extend GHES with selected GitHub.com capabilities.
+Now that you've seen how GHES can differ in everyday development workflows, the next unit introduces GitHub Connect and hybrid scenarios that can extend GHES with selected GitHub.com capabilities.