Clarify recursive test entry examples

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: MariusStorhaug

src/docs/Frameworks/Process-PSModule/pipeline-stages.md

@@ -114,9 +114,9 @@ The [PSModule - SourceCode tests](https://github.com/PSModule/Process-PSModule/b
 - Supports two special workflow phase scripts executed via separate dedicated jobs:
   - `tests/BeforeAll.ps1`: Runs once before all module-local test matrix jobs to set up the test environment (e.g., deploy infrastructure, download test data).
   - `tests/AfterAll.ps1`: Runs once after all module-local test matrix jobs complete to clean up the test environment (e.g., remove test resources, clean up databases).
-- The workflow checks only those exact repository-root paths; phase detection is non-recursive. Ordinary Advanced test entries may still be discovered recursively under `tests/`, but nested files named `BeforeAll.ps1` or `AfterAll.ps1` do not create workflow phases.
+- The workflow checks only those exact repository-root paths; phase detection is non-recursive. Ordinary module-local test entries in an Advanced layout (such as `*.Configuration.ps1`, `*.Container.ps1`, and `*.Tests.ps1`) may still be discovered recursively under `tests/`, but nested files named `BeforeAll.ps1` or `AfterAll.ps1` do not create workflow phases.
 - The two phase scripts run with the same environment variables as the tests.
-- This produces a JSON-based report that is used by [Get-PesterTestResults](#get-test-results) evaluate the results of the tests.
+- This produces a JSON-based report that is used by [Get-PesterTestResults](#get-test-results) to evaluate the results of the tests.
 
 ### Setup and Teardown Scripts