markdown table format fixes

[DaanHoogland]

Description

This PR… follows on #12943 after the extra markdown lint rule came into effect.

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)
• Build/CI
• Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 3.41%. Comparing base (cced071) to head (83b8eb2).
⚠️ Report is 1 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (cced071) and HEAD (83b8eb2). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (cced071)	HEAD (83b8eb2)
unittests	1	0

Additional details and impacted files

@@              Coverage Diff              @@
##               main   #13848       +/-   ##
=============================================
- Coverage     19.64%    3.41%   -16.24%     
=============================================
  Files          6368      487     -5881     
  Lines        574889    41867   -533022     
  Branches      70353     7912    -62441     
=============================================
- Hits         112957     1429   -111528     
+ Misses       449660    40238   -409422     
+ Partials      12272      200    -12072     

Flag	Coverage Δ
uitests	3.41% <ø> (ø)
unittests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 2 changed files in this pull request and generated no new comments.

Suppressed comments (2)

plugins/storage/volume/ontap/README.md:41

• These tables use a double leading pipe (||), which in standard GitHub/CommonMark table parsing renders as an extra empty first column. If the intent is a 2-column table, switch rows to a single leading pipe (| Package | Description |) throughout the table (and similarly for the other tables in this README) so the rendered documentation doesn’t include a blank column.

| Package | Description |
| --- | --- |
| `driver` | Primary datastore driver implementation |

plugins/storage/volume/ontap/README.md:74

• The PR description/template appears unfilled (no change type selected, no testing notes). Since the template explicitly notes automation relies on it, please select the appropriate change type and add a brief testing note (even if it’s just “markdownlint only”).

When creating an ONTAP primary storage pool, provide the following details in the URL field (semicolon-separated key=value pairs):