Fixed review feedback

Author: wolz-CODElife

learn-pr/github/authenticate-authorize-user-identities-github/includes/3-authentication.md

@@ -19,6 +19,7 @@ You can configure SAML SSO at either the **organization** or **enterprise** leve
 - **Enforcement**: Select **Require SAML SSO authentication** to remove non-compliant members automatically.
 - **Use Case**: Ideal for phased rollouts or testing with limited impact.
 
+> [!NOTE]
 > GitHub removes only organization members who fail to authenticate. Enterprise members remain until they next access the resource.
 
 #### Enterprise-Level SAML SSO
@@ -79,6 +80,7 @@ You can configure SAML SSO at either the **organization** or **enterprise** leve
 #### Github SMS support
 :::image type="content" source="../media/two-factor-authentication-sms-six-digit-code-example.png" alt-text="Screenshot of the SMS code." :::
 
+> [!NOTE]
 > Security keys store credentials locally and never expose secrets. GitHub recommends FIDO2/U2F keys.
 
 ### Auditing 2FA Compliance

learn-pr/github/authenticate-authorize-user-identities-github/includes/4-authorization.md

@@ -119,7 +119,7 @@ Some advantages of using the supported IdPs are:
 - Lower setup effort
 
 ### Bring Your Own IdP:
-Bringing your own IdP requires it isSAML 2.0 support. The advantage of this is that if allows for full flexibility.
+Bringing your own IdP requires it isSAML 2.0 support. The advantage of this is that it allows for full flexibility.
 
 ### Integration Steps
 | Type               | Steps                 |

learn-pr/github/authenticate-authorize-user-identities-github/includes/5-team-synchronization.md

@@ -47,7 +47,8 @@ Consider the following scenario to understand how team synchronization works in
 - Alice is added to the IdP group → automatically added to the GitHub team
 - If she leaves the group → automatically removed from the team
 
-**Note:** Team Sync in GHES doesn’t provision accounts. Users must already be GitHub organization members.
+> [!NOTE]
+> Team Sync in GHES doesn’t provision accounts. Users must already be GitHub organization members.
 
 ### Team Sync Configuration
 
@@ -68,7 +69,8 @@ To disable:
 
 :::image type="content" source="../media/disable-team-synchronization.png" alt-text="Screenshot of the organization setting to disable team synchronization." :::
 
-> Note: Disabling sync removes users from teams if they were added via IdP mapping.
+> [!NOTE]
+> Disabling sync removes users from teams if they were added via IdP mapping.
 
 ### SCIM in GHES
 SCIM is an open standard protocol designed to automate the exchange of user identity information between identity domains and IT systems. In the context of GHES, SCIM enables administrators to provision, update, and deprovision user accounts directly through the GitHub API. This means you can create, update, and delete user accounts, and sync group information to map GitHub team memberships.

learn-pr/github/github-administration-for-enterprise-support-adoption/includes/2-github-enterprise-tools-features.md

@@ -1,5 +1,3 @@
-# GitHub Administration for Enterprise Support and Adoption
-
 As a GitHub Enterprise administrator, you're responsible for establishing development environments that are both secure and scalable. This unit explores how to distinguish between GitHub Enterprise’s *upkeep* and *automation* features, and how to configure your organization for efficient collaboration.
 
 We also introduce standards-based developer workflows and rulesets—powerful tools for centralized policy enforcement.
@@ -19,7 +17,7 @@ Imagine your organization has brought in an external contractor team to deliver
 - Enabling private GitHub Pages for controlled documentation sharing (an upkeep feature).
 - Monitoring GitHub Actions usage to ensure efficient automation across the expanding team (an automation feature).
 
-:::image type="content" source="../media/enterprise-features-dichotomy.png" alt-text="GitHub Enterprise features categories split between Upkeep and Automation":::
+:::image type="content" source="../media/enterprise-features-dichotomy.png" alt-text="Diagram of GitHub Enterprise features categories split between Upkeep and Automation.":::
 
 
 ## Establishing Developer Workflow Standards
@@ -43,7 +41,7 @@ To ensure consistency, security, and scalability, GitHub Enterprise organization
 
 **Rulesets** are GitHub's recommended mechanism for enforcing policy at scale. Unlike traditional branch protection rules, rulesets allow you to centrally manage policies across multiple repositories and teams.
 
-:::image type="content" source="../media/ruleset-primary-foucs.png" alt-text="Rulesets overview":::
+:::image type="content" source="../media/ruleset-primary-focus.png" alt-text="Screenshot of Rulesets overview.":::
 
 ### Benefits of Rulesets
 
@@ -58,7 +56,7 @@ To ensure consistency, security, and scalability, GitHub Enterprise organization
 - Enforce CI/CD checks before merge.
 - Restrict access to protected branches.
 
-:::image type="content" source="../media/example-ruleset-policies.png" alt-text="Example ruleset enforcement dashboard":::
+:::image type="content" source="../media/example-ruleset-policies.png" alt-text="Screenshot of the ruleset enforcement dashboard.":::
 
 #### Combining Rulesets and Branch Protection (Legacy Support)
 
@@ -118,10 +116,10 @@ Automation features help reduce human error, enforce coding standards, and strea
 #### GitHub Advanced Security (GHAS)
 
 1. Navigate to **Your enterprises > Settings**.
-2. Review seat usage under **GitHub Advanced Security**.
+2. Review user usage under **GitHub Advanced Security**.
 3. If nearing limits, evaluate usage by team and prioritize.
 
-:::image type="content" source="../media/enterprise-licensing-tab-ghas.png" alt-text="GHAS usage dashboard":::
+:::image type="content" source="../media/enterprise-licensing-tab-ghas.png" alt-text="Screenshot of GHAS usage dashboard.":::
 
 #### GitHub Actions
 
@@ -132,7 +130,7 @@ Automation features help reduce human error, enforce coding standards, and strea
    - Windows: 2x Linux rate.
    - macOS: 10x Linux rate.
 
-:::image type="content" source="../media/actions-minutes.png" alt-text="GitHub Actions minutes usage":::
+:::image type="content" source="../media/actions-minutes.png" alt-text="Screenshot of GitHub Actions minutes usage.":::
 
 
 ## CI/CD Strategy in GitHub Enterprise
@@ -150,7 +148,8 @@ GitHub Enterprise enables secure and scalable CI/CD practices using **GitHub Act
 - **Security in CI/CD**: Integrate Dependabot, secret scanning, and compliance checks directly into pipelines.
 - **Monitoring & Notifications**: Configure alerts and integrate observability tools to track deployment health and performance.
 
-> **Tip**: Define reusable workflows and environments (e.g., staging, production) to ensure consistency and control.
+> [!TIP]
+> Define reusable workflows and environments (e.g., staging, production) to ensure consistency and control.
 
 ### Getting Started
 
@@ -187,7 +186,7 @@ Administrators can approve, configure, and maintain third-party tools and GitHub
 - Monitor permission changes.
 - Prefer tools with **Verified Creator** badges for higher trust.
 
-:::image type="content" source="../media/apps-with-verified-publisher-badge-tooltip.png" alt-text="Verified Creator badge in GitHub Marketplace":::
+:::image type="content" source="../media/apps-with-verified-publisher-badge-tooltip.png" alt-text="Screenshot of Verified Creator badge in GitHub Marketplace.":::
 
 ### Marketplace Guidelines
 

learn-pr/github/github-administration-for-enterprise-support-adoption/includes/3-support-for-github-enterprise.md

@@ -1,7 +1,5 @@
 :::image type="content" source="../media/premium-support.png" alt-text="A graphic that shows a stylized support engineer, with icons that represent different times of day":::
 
-# GitHub Enterprise Support
-
 This unit explains the enhanced support options available with GitHub Enterprise and outlines key responsibilities of administrators when working with GitHub Support. You'll apply this knowledge whether you're using GitHub Enterprise Server (self-hosted) or GitHub Enterprise Cloud (hosted by GitHub).
 
 
@@ -44,7 +42,8 @@ GitHub Support typically assists with issues across three areas: accounts, secur
 - Security Incidents: GitHub Support can help mitigate damage from compromised accounts, roll back repository changes, and assist with security recovery.
 - Abuse Cases: Support investigates violations of GitHub’s terms, such as harassment or inappropriate content, and can remove users or content as needed.
 
-> ⚠️ Administrators are responsible for infrastructure configuration, CI/CD integrations, third-party auth systems (like SAML), internal scripting, hardware setup, and immediate on-prem issue resolution.
+> [!NOTE]
+> Administrators are responsible for infrastructure configuration, CI/CD integrations, third-party auth systems (like SAML), internal scripting, hardware setup, and immediate on-prem issue resolution.
 
 
 
@@ -58,7 +57,7 @@ Include the following:
 - Context (e.g., first occurrence, frequency, business impact)  
 - Error messages (verbatim)  
 
-### 🔥 GitHub Support Priority Levels
+### GitHub Support Priority Levels
 
 | Priority | Description | Typical Response Time |
 |----------|-------------|------------------------|

learn-pr/github/github-administration-for-enterprise-support-adoption/includes/4-scale-your-github-enterprise-deployment.md

@@ -1,15 +1,15 @@
-# GitHub Enterprise: Scalable Administration and Governance
-
 As your GitHub Enterprise organization grows—whether due to team expansion or new contractor engagements—administrators are responsible for ensuring secure access, managing identity lifecycles, monitoring compliance, and optimizing deployment pipelines. This unit introduces key GitHub Enterprise features and governance tools to help you scale securely and efficiently.
 
 
 ## Secure Access with Single Sign-On (SSO)
 
-To maintain centralized identity control and streamline user management, enable SAML-based single sign-on (SSO) with your identity provider (IdP), such as Okta or Microsoft Entra ID.
+To maintain centralized identity control and streamline user management, enable SAML-based Single Sign-On (SSO) with your identity provider (IdP), such as Okta or Microsoft Entra ID.
 
-> **Tip:** From your organization’s **People** tab, you can review and revoke individual SAML credentials under the **SAML identity linked** section.
+> [!TIP] 
+> From your organization’s **People** tab, you can review and revoke individual SAML credentials under the **SAML identity linked** section.
 
-> **Important:** If you use team synchronization, revoking a user’s SSO identity automatically removes them from any teams mapped to IdP groups.
+> [!IMPORTANT] 
+> If you use team synchronization, revoking a user’s SSO identity automatically removes them from any teams mapped to IdP groups.
 
 
 ## Automate Identity Management with SCIM and APIs
@@ -72,7 +72,7 @@ GraphQL enables you to fetch only the data you need or mutate enterprise setting
 
 Enterprise Apps enhance oversight and control over GitHub Apps installed across your organizations.
 
-### Setup Overview:
+### Setup Overview
 
 | Platform | Steps |
 |----------|-------|
@@ -101,7 +101,8 @@ The [GitHub Marketplace](https://github.com/marketplace) offers reusable automat
 | **Auth Model**  | Uses temporary `GITHUB_TOKEN`              | Uses JWT + installation token                 |
 | **Billing**     | Billed per Action minute                   | SaaS-based (subscription/licensing)           |
 
-> **Tip:** Use GitHub Actions for ephemeral, event-based automation. Choose GitHub Apps when building persistent services with deeper API interactions or advanced permission scopes.
+> [!TIP] 
+> Use GitHub Actions for ephemeral, event-based automation. Choose GitHub Apps when building persistent services with deeper API interactions or advanced permission scopes.
 
 
 ### How Marketplace Tools Work Under the Hood