Fix markdown linting violations in README.md

[Copilot]

What are you trying to accomplish?

Fix failing GitHub Actions markdown workflow caused by 13 linting violations in README.md:

• MD009: Trailing spaces on lines 11, 13, 24
• MD004: Dash markers instead of asterisks in unordered lists
• MD007: Incorrect indentation (3 spaces vs required 2) for nested list items
• MD032: Missing blank line before list content

Integration

Risk Assessment

• Low risk the change is small, highly observable, and easily rolled back.
• Medium risk changes that are isolated, reduced in scope or could impact few users. The change will not impact library availability.
• High risk changes are those that could impact customers and SLOs, low or no test coverage, low observability, or slow to rollback.

What approach did you choose and why?

Applied minimal formatting fixes to match markdownlint-cli2 rules:

• Removed trailing whitespace
• Converted dash list markers (-) to asterisks (*)
• Adjusted nested list indentation to 2 spaces
• Added blank line separator before list

No content modified. Verified with npx markdownlint-cli2 README.md (0 errors).

Anything you want to highlight for special attention from reviewers?

Formatting-only changes. The maintenance mode warning block displays identically before and after.

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Lookbook)
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge

Original prompt

Fix the failing GitHub Actions workflow markdown
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 62385190683
Job URL: https://github.com/primer/view_components/actions/runs/21642342004/job/62385190683

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c5ca12e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR