@@ -1,19 +1,19 @@
 # Get-PesterCodeCoverage
 
-A GitHub Action that aggregates Pester code coverage reports and generates a detailed summary with coverage statistics.
-Fails the workflow if coverage falls below specified targets.
+This GitHub Action collects Pester code coverage reports and writes a summary of coverage statistics.
+If coverage is below the specified target, the action fails the workflow.
 
-This GitHub Action is a part of the [PSModule framework](https://github.com/PSModule). It is recommended to use the
-[Process-PSModule workflow](https://github.com/PSModule/Process-PSModule) to automate the whole process of managing the PowerShell module.
+The [PSModule framework](https://github.com/PSModule) includes this action.
+For the recommended setup, use the [Process-PSModule workflow](https://github.com/PSModule/Process-PSModule) to automate PowerShell module management.
 
 ## Features
 
-- Combines multiple code coverage reports from parallel test runs
-- Generates Markdown/HTML tables showing missed & executed commands
-- Displays analyzed files and coverage statistics
-- Generates a generic missed-path report (Markdown + JSON)
-- Configurable step summary sections
-- Threshold enforcement for minimum code coverage
+- Collects code coverage reports from parallel test runs.
+- Writes Markdown and HTML tables of missed and executed commands.
+- Shows analyzed files and coverage statistics.
+- Writes a missed-path report in Markdown and JSON.
+- Selects step summary sections from the action input.
+- Fails the workflow if coverage is below the target.
 
 ## Usage
 
@@ -26,10 +26,10 @@ This GitHub Action is a part of the [PSModule framework](https://github.com/PSMo
 | `Version` | Version of the GitHub module to install; accepts an exact version or a NuGet version range (for example `[1.2.0, 2.0.0)`) | No | Latest |
 | `Prerelease` | Allow prerelease versions | No | `false` |
 | `WorkingDirectory` | Working directory for the action | No | `.` |
-| `StepSummary_Mode` | Controls which sections to show in the GitHub step summary. Use 'Full' for all sections, 'None' to disable, or a comma-separated list of 'Missed, Executed, Files'. | No | `Missed, Files` |
+| `StepSummary_Mode` | Select the sections in the GitHub step summary. Use 'Full' for all sections, 'None' to disable, or a comma-separated list of 'Missed, Executed, Files'. | No | `Missed, Files` |
 | `CodeCoveragePercentTarget` | Target code coverage percentage | No | Max target from individual reports |
 
-### Example Workflow
+### Example workflow
 
 ```yaml
     - name: Process Code Coverage
@@ -43,22 +43,22 @@ This GitHub Action is a part of the [PSModule framework](https://github.com/PSMo
 
 | Name | Description |
 | ---- | ----------- |
-| `MissedPathReportPath` | Folder path containing `CodeCoverage-MissedPaths.md` and `CodeCoverage-MissedPaths.json` |
+| `MissedPathReportPath` | Path to the folder with `CodeCoverage-MissedPaths.md` and `CodeCoverage-MissedPaths.json` |
 
-### GitHub Step Summary
+### GitHub step summary
 
-The action generates a detailed summary visible in the GitHub Actions UI:
+The action writes a detailed summary to the GitHub Actions UI:
 
-1. **Coverage Overview Table**
-   - Coverage percentage vs target
-   - Analyzed/executed/missed command counts
-   - Number of files analyzed
+1. **Coverage overview table**
+   - Coverage percentage and target
+   - Analyzed, executed, and missed command counts
+   - Number of analyzed files
 
-2. **Expandable Sections**
-   - **Missed Commands**: HTML table with code snippets
-   - **Executed Commands**: HTML table with code snippets
-   - **Analyzed Files**: List of covered files
-   - **Missed Paths**: Aggregated missed-command counts grouped by file path
+2. **Expandable sections**
+   - **Missed commands**: HTML table with code snippets
+   - **Executed commands**: HTML table with code snippets
+   - **Analyzed files**: List of covered files
+   - **Missed paths**: Missed-command counts for each file path
 
 Example summary:
 
@@ -77,10 +77,10 @@ Summary:
 
 ## Requirements
 
-1. **Pester 6.1 Code Coverage Reports**
+1. **Pester 6.1 code coverage reports**
 
-   Preceding steps must generate JSON coverage reports named `*-CodeCoverage*.json`
-   from the Pester 6.1 `CodeCoverage` result object. The action consumes
+   Earlier steps must create JSON coverage reports named `*-CodeCoverage*.json`
+   from the Pester 6.1 `CodeCoverage` result object. The action reads
    `CoveragePercent`, `CoveragePercentTarget`, `CommandsMissed`,
    `CommandsExecuted`, and `FilesAnalyzed` plus their count properties.
 
@@ -89,18 +89,19 @@ Summary:
 
 ## Behavior
 
-1. **Coverage Calculation**
-   - Combines multiple coverage reports
-   - Removes duplicate entries
-   - Calculates aggregate coverage percentage
+1. **Coverage calculation**
+   - Collects multiple coverage reports.
+   - Removes duplicate entries.
+   - Calculates the total coverage percentage across all reports.
 
-2. **Threshold Enforcement**
-   Fails the workflow if coverage is below either:
-   - Explicitly specified `CodeCoveragePercentTarget`
-   - Highest target from individual reports (if no target specified)
+2. **Threshold enforcement**
+   If coverage is below the applicable target, the action fails the workflow.
+   The action uses:
+   - The explicit `CodeCoveragePercentTarget` value, if the input has a value.
+   - The highest target from individual reports, if the input has no value.
 
-3. **Output Control**
-   Configure visibility of sections using `StepSummary_Mode`:
+3. **Output control**
+   Use `StepSummary_Mode` to select the summary sections:
    ```yaml
    # Show all sections
    StepSummary_Mode: Full
@@ -114,7 +115,7 @@ Summary:
 
 ## Troubleshooting
 
-Enable debugging by setting inputs:
+To get debug and verbose output, set these inputs:
 ```yaml
 with:
   Debug: true