Give change a reference point
A version identifies a particular release or revision. It can help distinguish an older description from a newer one, or explain why two people see different behavior. The label is useful when it can be connected to a clear account of what changed.
Version numbering conventions vary. A larger number does not, by itself, explain whether a change is cosmetic, fixes a defect or affects compatibility. A readable change note supplies context that the number cannot.
Reading and editing can differ
Compatibility is rarely a single yes-or-no question. A tool might open a file while handling some features differently. Reading, editing and saving deserve separate consideration when information moves between versions.
Imagine a document created with a newer annotation feature. An older reader can display the main text but cannot edit those annotations. Saying only that the file “opens” would leave an important part of the experience unexplained.
Keep the description specific
A useful compatibility description names the versions involved, the relevant feature and any limitation. It also distinguishes the original file from a converted copy. Before replacing an important document, retaining an original gives the reader a reference if the converted result behaves differently.
Which version does this explanation describe?