docs(CONTRIBUTING): improve formatting and readability of contribution guidelines

Author: l7aromeo

CONTRIBUTING.md

@@ -1,19 +1,21 @@
 # Contributing to meonode-ui
 
-First off — thank you for considering contributing to meonode-ui! Your help improves the project for everyone. This document describes how to report issues, propose changes, and contribute code in a way that keeps the project healthy and easy to maintain.
+First off — thank you for considering contributing to meonode-ui! Your help improves the project for everyone. This
+document describes how to report issues, propose changes, and contribute code in a way that keeps the project healthy
+and easy to maintain.
 
 ## Table of contents
 
 - [Code of Conduct](#code-of-conduct)
 - [How can I contribute?](#how-can-i-contribute)
-  - [Reporting bugs](#reporting-bugs)
-  - [Suggesting enhancements](#suggesting-enhancements)
-  - [Discussing ideas](#discussing-ideas)
+    - [Reporting bugs](#reporting-bugs)
+    - [Suggesting enhancements](#suggesting-enhancements)
+    - [Discussing ideas](#discussing-ideas)
 - [Development setup](#development-setup)
 - [Making changes (Pull Requests)](#making-changes-pull-requests)
-  - [Branching and commit messages](#branching-and-commit-messages)
-  - [Tests and linting](#tests-and-linting)
-  - [PR checklist](#pr-checklist)
+    - [Branching and commit messages](#branching-and-commit-messages)
+    - [Tests and linting](#tests-and-linting)
+    - [PR checklist](#pr-checklist)
 - [Style guide](#style-guide)
 - [Releasing & changelog](#releasing--changelog)
 - [Getting help / contact](#getting-help--contact)
@@ -22,15 +24,17 @@ First off — thank you for considering contributing to meonode-ui! Your help im
 
 ## Code of Conduct
 
-This project follows a [Code of Conduct]. Please be respectful and kind. If you encounter unacceptable behavior, report it to the maintainers.
+This project follows a [Code of Conduct]. Please be respectful and kind. If you encounter unacceptable behavior, report
+it to the maintainers.
 
 [Code of Conduct]: https://www.contributor-covenant.org/version/2/0/code_of_conduct/
 
 ---
 
 ## How can I contribute?
 
-Contributions are welcome in many forms: filing issues, suggesting features, improving documentation, or sending code changes.
+Contributions are welcome in many forms: filing issues, suggesting features, improving documentation, or sending code
+changes.
 
 ### Reporting bugs
 
@@ -48,33 +52,38 @@ Example issue template (you can copy/paste):
 Title: "Button: style props not applied when using as()"
 
 Body:
+
 - Steps to reproduce:
-  1. Create a Button with prop `color: "red"`.
-  2. Observe styles not applied.
+    1. Create a Button with prop `color: "red"`.
+    2. Observe styles not applied.
 - Expected behavior: Color prop should apply to the rendered element.
 - Environment: Node 22.17.1, Yarn 4.9.1 (stable), macOS 26
 
 ### Suggesting enhancements
 
 Feature requests are welcome. Please open an issue with:
+
 - The problem you're trying to solve,
 - Why the current behavior is insufficient,
 - Example API you'd like to see,
 - Any backward compatibility concerns.
 
 ### Discussing ideas
 
-For larger design discussions or proposals, opening a GitHub Discussion or drafting a proposal in the issue tracker helps get feedback before investing implementation time.
+For larger design discussions or proposals, opening a GitHub Discussion or drafting a proposal in the issue tracker
+helps get feedback before investing implementation time.
 
 ---
 
 ## Development setup
 
 Prerequisites
+
 - Node.js (LTS recommended; >= 22)
 - Yarn (Berry/Plug'n'Play recommended since the repository includes .yarnrc.yml), or use npm if you prefer.
 
 Quick start
+
 ```bash
 # clone
 git clone https://github.com/l7aromeo/meonode-ui.git
@@ -95,8 +104,11 @@ yarn format
 ```
 
 Notes
-- Husky hooks may run on commit (pre-commit / pre-push). If you need to bypass hooks: `git commit --no-verify` (use sparingly).
-- The repository includes a prepublish script; if you plan to test publishing locally, inspect `prepublish.sh` before running it.
+
+- Husky hooks may run on commit (pre-commit / pre-push). If you need to bypass hooks: `git commit --no-verify` (use
+  sparingly).
+- The repository includes a prepublish script; if you plan to test publishing locally, inspect `prepublish.sh` before
+  running it.
 
 ---
 
@@ -151,15 +163,18 @@ Before requesting a review, ensure:
 
 ## Releasing & changelog
 
-Releases should follow semantic versioning. The repository contains a CHANGELOG.md — update it for user-facing changes. Maintainers can use `prepublish.sh` and the release automation configured for publishing.
+Releases should follow semantic versioning. The repository contains a CHANGELOG.md — update it for user-facing changes.
+Maintainers can use `prepublish.sh` and the release automation configured for publishing.
 
-If you contribute a user-facing change, leave a short changelog entry in your PR or mention the relevant entry in the issue.
+If you contribute a user-facing change, leave a short changelog entry in your PR or mention the relevant entry in the
+issue.
 
 ---
 
 ## Getting help / contact
 
 If you need help:
+
 - Open an issue describing the problem and steps you took.
 - Start a discussion for design-level questions.