A coach edits a training note on screen. The note can exist in working memory before it is saved. If the application closes first, those unsaved edits can be lost.
An activity diagram is useful here because saving and loading are actions in a process. A class diagram can describe the note's fields, but cannot by itself establish whether a save has occurred.
The partitions identify responsibility. The coach chooses Save; the application requests the write; storage either succeeds or fails. A saved confirmation belongs only after success. A file write request alone is not evidence that the file changed.
Saving copies selected current information outward to persistent storage. Loading reads stored information inward. Neither operation needs to be modeled as destroying the other copy. If a later save overwrites the file, the diagram should make that overwrite rule clear.