Correct the release note on failed edits

0.5.2 already checked a WAV before changing anything, so a non-WAV file
was not a new example. Say what PR 6 changed: a failure partway through
an edit, possible with an unusual project file, no longer leaves it
half done.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

pull-requests/release-0-5-3/release-0-5-3.md

@@ -13,7 +13,7 @@ PR 9 of the review fixes plan (`docs/review-fixes-plan.md`): the 0.5.3 release o
 - **Declining to replace an export forgets the folder or file you picked.** The next export asks again.
 
 **Safer under the hood**
-- **A failed edit no longer leaves a project half-changed.** For example, assigning a file that is not a WAV leaves the pad as it was. A failed tune, mute-group or sequence edit no longer marks the project as having unsaved changes.
+- **A failed edit no longer leaves a project half-changed**, for example on a project file with an unusual pad layout. A failed tune, mute-group or sequence edit no longer marks the project as having unsaved changes.
 - **The window's code can no longer load, assign or export using a file path of its own.** MPCkit only opens and writes files you picked in a dialog or dropped on a pad.
 - **Builds are reproducible:**
   - the frontend's package versions are locked;