Updated headings to follow Microsoft style guide

Author: wolz-CODElife

learn-pr/github/manage-sensitive-data-security-policies/includes/2-set-security-policies.md

@@ -51,7 +51,7 @@ Enterprise rules override org rules; org owners can’t change locked settings.
 - **All repos:** Access controls, SECURITY.md, Dependabot alerts/updates, advisories
 - **With Advanced Security:** Code scanning, secret scanning, dependency review
 
-## Enhancing Enterprise Security with GitHub
+## Enhancing enterprise security with GitHub
 GitHub’s enterprise features bolster your security posture and compliance.
 
 - Security Features
@@ -60,7 +60,7 @@ GitHub’s enterprise features bolster your security posture and compliance.
 - Compliance Support
   - **Compliance reports:** SOC 1 Type 2, SOC 2 Type 2, ISO/IEC 27001:2013 certifications available for audits and regulatory needs
 
-## Scrubbing Sensitive Data from GitHub Repositories
+## Scrubbing sensitive data from GitHub repositories
 When secrets leak, you must rewrite history or engage GitHub support.
 
 ### Rewrite history
@@ -104,7 +104,7 @@ When vulnerabilities arise, use GitHub security advisories to:
 
 A good advisory lists the affected versions, severity, patch status, and CVE references. Use GitHub’s built-in workflow to manage and publish advisories efficiently.
 
-## Enabling Secure Software Development and Ensuring Compliance
+## Enabling secure software development and ensuring compliance
 
 Each policy is designed to balance security and usability, offering options that range from minimal restrictions to highly controlled environments.
 The table below provides an overview of various security policies categorized by their level of control.
@@ -115,7 +115,7 @@ The table below provides an overview of various security policies categorized by
 | **Moderate Control** (Enforced Rules) | Required branch protection; Commit signing; Org-wide security policies; Monitoring webhooks | Teams needing governance with developer autonomy |
 | **High Control** (Strict Compliance & Governance) | Enforce SAML SSO & 2FA; Restrict visibility & forking; Mandatory PR approvals; Prevent force pushes; CI/CD security checks | Organizations with strict compliance requirements (e.g., SOC 2, ISO 27001) |
 
-### Key Security and Compliance Features in GitHub Enterprise
+### Key security and compliance features in GitHub Enterprise
 
 1. Secure Code Development
    - **Code Scanning (GHAS):** Automatically detect vulnerabilities via CodeQL.
@@ -130,16 +130,16 @@ The table below provides an overview of various security policies categorized by
    - **Restrict Repository Visibility:** Control who can view, fork, or clone.
    - **Fine-Grained Access Control:** Assign roles per team or project.
 
-### When to Use Different Security and Compliance Profiles
+### When to use different security and compliance profiles
 - **Startups & Agile Teams:** Moderate control with branch protection, Dependabot, and secret scanning.
 - **Enterprises & Regulated Industries:** High control with SAML SSO, audit logging, security rulesets, and strict repo controls.
 - **Open Source Projects:** Low to moderate control with code scanning, dependency updates, and community guidance.
 
-## Defining Organization and Enterprise Policies
+## Defining Organization and Enterprise policies
 
 Organization policies and enterprise policies set governance, access, and workflow rules to ensure security and compliance.
 
-### Key Aspects
+### Key aspects
 1. **Security & Access Control:** SAML SSO, 2FA, RBAC, repo visibility.
 2. **Compliance & Governance:** Audit logging, branch protection, commit signing.
 3. **Development Workflow & Automation:** PR approvals, security rulesets, Actions policies.

learn-pr/github/manage-sensitive-data-security-policies/includes/3-scrub-sensitive-data-from-repository.md

@@ -1,10 +1,8 @@
-<!--Manage sensitive data and security policies in GitHub-->
-
 In this unit, you’ll learn how to create and manage rulesets, and understand the advantages they offer over traditional protection rules.
 
 As a GitHub administrator, you need granular control over who can push, delete, or rename branches and tags. **Repository rulesets** let you bundle multiple rules under a single name, apply them to selected branches or tags, and toggle them on or off without deleting them. They complement existing branch- and tag-protection rules, giving you a unified, layered approach to repository security.
 
-## What Are Repository Rulesets?
+## What are repository Rulesets?
 
 A **ruleset** is a named collection of rules that apply to one or more branches or tags in your repository.
 
@@ -14,7 +12,7 @@ A **ruleset** is a named collection of rules that apply to one or more branches
 
 For example, a ruleset for your `feature/*` branches can require signed commits and block force pushes for everyone except admins. You can also import existing tag-protection rules into a ruleset to reuse your current settings.
 
-## Comparing Rulesets, Branch Protection, and Protected Tags
+## Comparing Rulesets, branch protection, and protected tags
 
 | Capability                                   | Protection Rules | Rulesets             |
 |----------------------------------------------|------------------|----------------------|
@@ -28,7 +26,7 @@ For example, a ruleset for your `feature/*` branches can require signed commits
 - **Statuses:** Enable, disable, or evaluate (test) rulesets without deletion.  
 - **Transparency:** Developers and auditors can view active rulesets with read access, without admin rights.  
 
-## Creating Your First Ruleset
+## Creating your first Ruleset
 
 1. On GitHub.com, navigate to **Settings > Code and automation > Rules > Rulesets**.  
 2. Click **New ruleset**, then select **Branch** or **Tag**.  
@@ -42,14 +40,14 @@ For example, a ruleset for your `feature/*` branches can require signed commits
 > [!TIP]  
 > For release branches (`release/*`), require two successful status checks and block force pushes to enforce stability.
 
-## Managing and Editing Rulesets
+## Managing and editing Rulesets
 
 - **View active rulesets:** On the *Rulesets* page, see which sets target a given branch or tag.  
 - **Edit a ruleset:** Click its name, adjust rules or targets, then **Save changes**.  
 - **Toggle status:** Enable or disable a ruleset without deleting it.  
 - **Delete:** Remove obsolete rulesets when they’re no longer needed.
 
-## Available Rules
+## Available rules
 
 Repository rulesets support many of the same protections as branch and tag protection:
 
@@ -64,7 +62,7 @@ Common examples:
 > [!TIP]  
 > Enforce your CI/CD pipeline by requiring key workflows as status checks before merges.
 
-## Layering Rulesets and Protections
+## Layering Rulesets and protections
 
 GitHub aggregates all applicable rules—branch protection, tag protection, and multiple rulesets—and applies the most restrictive setting.
 
@@ -74,47 +72,47 @@ GitHub aggregates all applicable rules—branch protection, tag protection, and
 
 **Outcome:** Pull requests need three reviews, and commits must be both signed and linear.
 
-## Impacts of Policy and Ruleset Choices in GitHub Enterprise
+## Impacts of policy and Ruleset choices in GitHub Enterprise
 
 Your policies and rulesets affect security, compliance, developer experience, and operational efficiency. Finding the right balance between control and flexibility is essential.
 
-### Security and Compliance Enforcement
+### Security and compliance enforcement
 
 | **Pros**                     | **Cons**               |
 |------------------------------|------------------------|
 | SAML SSO & 2FA enforced by rulesets prevent unauthorized access. | Blocking forks or enforcing lengthy approval chains can frustrate developers. |
 | Branch protections ensure every code change is reviewed. | Manual security checks increase administrative overhead.          |
 | Audit-logging rulesets support SOC 2 and ISO 27001 compliance. |               |
 
-### Developer Productivity and Workflow Efficiency
+### Developer productivity and workflow efficiency
 
 | **Pros**                 | **Cons**                |
 |--------------------------|-------------------------|
 | Automated checks (Dependabot, Code Scanning) reduce manual work. | Strict approval policies slow fast-moving teams. |
 | Security rulesets automate compliance without manual steps. | Blocking force pushes can complicate emergency hotfixes. |
 | Flexible protections (e.g., reviews only on critical branches) maintain agility. |              |
 
-### Governance and Access Control
+### Governance and access control
 
 | **Pros**              | **Cons**                  |
 |-----------------------|---------------------------|
 | Visibility rules prevent accidental exposure of private code. | Over-restricting access can create collaboration bottlenecks. |
 | Fine-grained permissions ensure proper access levels. | Blocking forks in open-source projects hinders contributions. |
 | Fork restrictions reduce intellectual property risks.      |         |
 
-### CI/CD and Automation Impact
+### CI/CD and automation impact
 
 | **Pros**             | **Cons**                   |
 |-----------------------|---------------------------|
 | Requiring status checks ensures code is validated before deployment.   | Strict CI approvals can slow down deployments. |
 | Integrating GitHub Actions with rulesets enforces compliance automatically. | Blocking third-party Actions limits automation options. |
 | Built-in Code Scanning and Dependency Management embed security into pipelines. |           |
 
-## GitHub Audit Log APIs for Investigating Missing Assets
+## GitHub audit log APIs for investigating missing assets
 
 Audit logs provide visibility into events such as repository deletions or member removals. Use REST or GraphQL to query and remediate.
 
-### Steps to Troubleshoot Missing Assets
+### Steps to troubleshoot missing assets
 
 1. **Identify the asset:** (e.g., `repository.deleted`).  
 2. **Query the Audit Log API (REST):**  

learn-pr/github/manage-sensitive-data-security-policies/includes/4-report-log.md

@@ -5,7 +5,7 @@ You can access the audit log through GitHub.com, GitHub Enterprise Server, or Gi
 > [!TIP]
 > Suppose a critical repository vanished overnight. You’ll use the audit logs to pinpoint the deletion event and restore continuity.
 
-## What Are Log Records?
+## What are Log Records?
 
 Your organization’s audit log records actions taken by organization members. Available to organization owners, the log provides information about actions that affect the organization, including:
 
@@ -18,7 +18,7 @@ Your organization’s audit log records actions taken by organization members. A
 > [!NOTE]
 > Logs are retained for up to 90 days in GitHub Enterprise Cloud (120 days via GraphQL on Enterprise Server).
 
-## Viewing and Exporting Audit Logs via the GitHub UI
+## Viewing and exporting Audit Logs via the GitHub UI
 
 1. On GitHub.com, navigate to your organization’s **Settings > Audit log**.  
 2. Use the **Filters** field to narrow results by qualifier (actor, repo, action, date).  
@@ -66,7 +66,7 @@ query {
 }
 ```
 
-## Investigating Missing Assets
+## Investigating missing assets
 
 To recover or audit missing resources like repositories or teams:
 
@@ -93,36 +93,36 @@ query {
 }
 ```
 
-## Use Cases for Audit Logs
+## Use cases for Audit Logs
 
 - **Security incidents:** Trace unauthorized access or data exfiltration.  
 - **Compliance audits:** Demonstrate policy enforcement (SOC 2, ISO 27001).  
 - **Operational troubleshooting:** Diagnose CI/CD failures or permission errors.  
 - **Access monitoring:** Review API token usage and SSH/Git activity.  
 
-## Security & Compliance
+## Security and compliance
 
 - **Data Retention:** 90 days on Enterprise Cloud; 120 days on Enterprise Server.  
 - **Access Control:** Only owners and security managers can view logs.  
 - **IP Logging:** Records source IP to detect suspicious access.  
 - **GDPR & Regional Compliance:** Meets data-handling requirements.  
 
-## Audit Log Streaming
+## Audit Log streaming
 
 Stream logs in real time to SIEM platforms (Splunk, Datadog) for long-term storage:
 
 1. Go to **Settings > Audit log**.  
 2. Under **Streaming**, configure a destination (AWS S3, Azure Event Hubs).  
 3. Verify events arrive in your SIEM.  
 
-## Additional Audit Log Types
+## Additional Audit Log types
 
 - **Git Activity Log:** Tracks pushes, pulls, merges (`phrase=git.push`).  
 - **API Activity Log:** Tracks REST/GraphQL requests (`phrase=api.request`).  
 - **Enterprise Managed Users (EMU):** Includes `user.login`, `repository.permissions_updated`, `repository.forked`.  
 - **Token Usage:** Filter by `phrase=token` to identify compromised credentials.  
 
-## Key Security Features of a GitHub Repository
+## Key security features of a GitHub Repository
 
 - **SECURITY.md:** Define reporting process and supported versions.  
 - **Branch Protection:** Enforce reviews, status checks, and commit signing.  
@@ -133,7 +133,7 @@ Stream logs in real time to SIEM platforms (Splunk, Datadog) for long-term stora
 - **Dependency Graph:** Visualize and audit dependencies.  
 - **2FA & RBAC:** Enforce strong authentication and least privilege.  
 
-## API Access and Integrations
+## API access and integrations
 
 | **Token Type**            | **Description**                                                       |
 | ------------------------- | --------------------------------------------------------------------- |