fix some issues

Author: Albertyang0

learn-pr/github/github-enterprise-server-developer-fundamentals/6-knowledge-check.yml

@@ -15,13 +15,13 @@ quiz:
   questions:
   - content: "What is a defining characteristic of GitHub Enterprise Server (GHES)?"
     choices:
-    - content: "It is a fully managed Software as a Service (SaaS) platform hosted by GitHub."
+    - content: "It's a fully managed Software as a Service (SaaS) platform hosted by GitHub."
       isCorrect: false
-      explanation: "Incorrect. GitHub Enterprise Server is not a SaaS platform hosted by GitHub."
+      explanation: "Incorrect. GitHub Enterprise Server isn't an SaaS platform hosted by GitHub."
     - content: "It automatically updates with new features as soon as they are released."
       isCorrect: false
-      explanation: "Incorrect. GitHub Enterprise Server follows a scheduled release cycle and does not update automatically with every new feature."
-    - content: "It is self-hosted and managed by the customer."
+      explanation: "Incorrect. GitHub Enterprise Server follows a scheduled release cycle and doesn't update automatically with every new feature."
+    - content: "It's self-hosted and managed by the customer."
       isCorrect: true
       explanation: "Correct. GitHub Enterprise Server is deployed on infrastructure owned and managed by the customer, providing full control over data and operations."
     - content: "It only supports public repositories."
@@ -35,23 +35,23 @@ quiz:
     - content: "GHES follows a quarterly release cadence."
       isCorrect: true
       explanation: "Correct. GitHub Enterprise Server uses a structured quarterly release cycle to ensure stability for self-managed environments."
-    - content: "GHES does not support modern development workflows."
+    - content: "GHES doesn't support modern development workflows."
       isCorrect: false
       explanation: "Incorrect. GitHub Enterprise Server supports modern development workflows."
     - content: "GHES updates are controlled by individual developers."
       isCorrect: false
       explanation: "Incorrect. Updates are managed through official enterprise releases."
-  - content: "Which GitHub feature is not supported on GitHub Enterprise Server?"
+  - content: "Which GitHub feature isn't supported on GitHub Enterprise Server?"
     choices:
     - content: "Pull requests."
       isCorrect: false
       explanation: "Incorrect. Pull requests are supported on GitHub Enterprise Server."
     - content: "GitHub Actions."
       isCorrect: false
-      explanation: "Incorrect. GitHub Actions is supported on GitHub Enterprise Server."
+      explanation: "Incorrect. GitHub Actions are supported on GitHub Enterprise Server."
     - content: "GitHub Codespaces."
       isCorrect: true
-      explanation: "Correct. GitHub Codespaces is a cloud-only feature and is not available on GitHub Enterprise Server."
+      explanation: "Correct. GitHub Codespaces is a cloud-only feature and isn't available on GitHub Enterprise Server."
     - content: "Issues."
       isCorrect: false
       explanation: "Incorrect. Issues are supported on GitHub Enterprise Server."
@@ -68,4 +68,4 @@ quiz:
       explanation: "Incorrect. Features cannot be manually enabled if they are not included in the deployed version."
     - content: "Switch to a public repository so the feature becomes available."
       isCorrect: false
-      explanation: "Incorrect. Repository visibility does not affect feature availability in GHES."
+      explanation: "Incorrect. Repository visibility doesn't affect feature availability in GHES."

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

@@ -16,7 +16,7 @@ From a user interface perspective, GHES looks familiar. However, the developer e
 
 - Your organization is responsible for provisioning, scaling, patching, and maintaining these runners.
 
-- If runners are offline or outdated, workflows will fail-no automatic fallback.
+- If runners are offline or outdated, workflows will fail-no automatic fall back.
 
 - Network restrictions are common; proxies or mirrors may be needed for external access.
 
@@ -26,17 +26,17 @@ From a user interface perspective, GHES looks familiar. However, the developer e
 
 - GitHub Packages (npm, Docker, etc.) are available and hosted internally in GHES.
 
-- Advanced Security features (e.g. code scanning, secret scanning) are supported with proper licensing.
+- Advanced Security features (for example, code scanning, secret scanning) are supported with proper licensing.
 
 - These features often require manual setup-such as installing scanning engines or enabling secret detection-though from a developer perspective, the enablement process is no different than on GitHub Enterprise Cloud (GHEC).
 
 - Many capabilities are disabled by default and depend on coordination with your DevOps or platform teams.
 
 ### Unsupported or limited features
 
-- GitHub Codespaces is not supported as of GHES 3.19.
+- GitHub Codespaces isn't supported as of GHES 3.19.
 
-- GitHub Copilot is not supported on GHES. Copilot can be used as a standalone feature within supported IDEs, but Copilot features are not available on the GHES web interface, and functionality may be further limited in environments with restricted internet access.
+- GitHub Copilot isn't supported on GHES. Copilot can be used as a standalone feature within supported IDEs, but Copilot features aren't available on the GHES web interface, and functionality may be further limited in environments with restricted internet access.
 
 - Accessing the library of public GitHub Actions directly from GitHub.com requires GitHub Connect. Without it, Actions must be manually synced to your local instance.
 
@@ -46,6 +46,6 @@ From a user interface perspective, GHES looks familiar. However, the developer e
 
 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.
+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.