docs: update tables for clarity in pipeline configuration and framework test IDs

Author: MariusStorhaug

docs/content/Modules/Process-PSModule/guides/configuring-the-pipeline.md

@@ -119,7 +119,7 @@ The workflow can automatically generate GitHub release names and notes from your
 Three parameters control this behavior:
 
 | Parameter | Description |
-|-----------|-------------|
+| ----------- | ------------- |
 | `UsePRTitleAsReleaseName` | Use the PR title as the GitHub release name instead of the version string |
 | `UsePRBodyAsReleaseNotes` | Use the PR body as the release notes content |
 | `UsePRTitleAsNotesHeading` | Prepend PR title as H1 heading with PR number link before the body |

docs/content/Modules/Process-PSModule/reference/framework-test-ids.md

@@ -15,7 +15,7 @@ Run by the [Test source code](pipeline-stages.md#test-source-code) job against f
 [PSModule - SourceCode tests](https://github.com/PSModule/Process-PSModule/blob/main/scripts/tests/SourceCode/PSModule/PSModule.Tests.ps1).
 
 | ID | Category | Description | Example skip comment |
-|----|----------|-------------|----------------------|
+| ---- | ---------- | ------------- | ---------------------- |
 | `NumberOfProcessors` | General | Should use `[System.Environment]::ProcessorCount` instead of `$env:NUMBER_OF_PROCESSORS`. | `#SkipTest:NumberOfProcessors:Legacy code compatibility required` |
 | `Verbose` | General | Should not pass `-Verbose` to other commands (which would override user preference), unless explicitly disabled with `-Verbose:$false`. | `#SkipTest:Verbose:Required for debugging output` |
 | `OutNull` | General | Should use `$null = ...` instead of piping output to `Out-Null`. | `#SkipTest:OutNull:Pipeline processing required` |

docs/content/Modules/Process-PSModule/specification/spec.md

@@ -91,7 +91,7 @@ Scenario: Compute the next version from the PR label
   Given a pull request with the label "Minor"
   When the PR is merged to main and the current version is v1.2.3
   Then the new version is computed as v1.3.0
-  
+
 Scenario: Reject ambiguous version labels
   Given a pull request with both "Major" and "Minor" labels
   When the merge is attempted
@@ -118,7 +118,7 @@ Scenario: Publish a prerelease version
   When the PR runs the pipeline
   Then a prerelease version is published (e.g., v1.2.3-pr.1.N)
   And it is available for testing before the PR is merged
-  
+
 Scenario: Promote a prerelease to stable
   Given a prerelease PR that is merged to main with a version label
   When the PR is merged