Update ONBOARDING.md

Author: GsCommand

ONBOARDING.md

@@ -96,27 +96,27 @@ If a change is not consistent with these files, it is non-compliant, even if CI
 
 ## 4. How To Propose a Change
 
-Never just “fix a schema” in a drive-by PR.
+**Never** just “fix a schema” in a drive-by PR.
 
 For any change (new verb, bugfix, tightening, etc.):
 
-Open an Issue
+### 1. Open an Issue
 
 Describe the problem / use case.
 
 Specify which verb(s) and version(s) are affected.
 
 Describe expected behavior vs current behavior.
 
-Design the Change
+### 2. Design the Change
 
 Decide if this is breaking (shape or semantics) or additive.
 
 Map it onto versioning rules in POLICY.md and SPEC.md.
 
 For new verbs, justify why it belongs in Commons (not Commercial).
 
-Implement
+### 3. Implement
 
 Modify or add schemas under schemas/vX.Y.Z/...
 
@@ -129,23 +129,23 @@ npm run validate
 npm run validate:examples
 
 
-Update Provenance
+### 4. Update Provenance
 
 Append entries to RESOLUTION.md (what changed and why).
 
 Prepare new checksums and manifest updates (if version changes).
 
 Ensure new CIDs are ready to be pinned (IPFS).
 
-Submit PR
+### 5. Submit PR
 
 Link the Issue in the PR description.
 
 Include validation output (or CI link).
 
 Call out whether this is MAJOR/MINOR/PATCH in semantic-version terms.
 
-Governance Review
+### 6. Governance Review
 
 Maintainers check: