Fix inaccurate description of none bump type

`none` doesn't suppress propagation — it acknowledges a change without
triggering a direct bump. Cascading bumps still apply normally.

Author: theoephraim

docs/differences-from-changesets.md

@@ -21,7 +21,7 @@ Key differences from changesets:
 - Out-of-range peer dep bumps match the triggering bump level (not always major) — a minor bump on `core` → minor bump on `plugin`, not major
 - Dev deps never propagate by default (configurable per-package for bundled devDeps)
 - `cascadeTo` config for source-side "when I change, cascade to these packages"
-- Per-bump-file `none` to suppress propagation on specific changes
+- Per-bump-file `none` to acknowledge changes without triggering a direct bump
 - Warns about `^0.x` caret range gotchas and `workspace:*` on peer deps
 
 See [docs/version-propagation.md](./version-propagation.md) for the full algorithm.