clarify the example narrative of a version history

json-api · gabesullice · Dec 12, 2018 · Dec 13, 2018 · Dec 13, 2018 · Dec 13, 2018
commit 0feddd68f0307848d51ee53e338a4d6b325b0ae9
diff --git a/_profiles/drupal/resource-versioning/index.md b/_profiles/drupal/resource-versioning/index.md
@@ -60,8 +60,11 @@ before the resource was published may have many revisions. Only the published
 revision would be considered a version. The revisions prior to first version
 would have been known as the working copy as each one was created.
 
-If the version is then checked out for further changes (which may or may not be
-published) each new revision becomes the working copy.
+If the version is then checked out for further changes each new revision becomes
+the working copy. When the working copy is checked in and made the default
+revision, this revision becomes the latest version and the version before it is
+its _predecessor version _. If no other revisions come after the latest version,
+it may also be considered the working copy.
 
 Sophisticated servers may support multiple versions of a resource as well as
 multiple working copies of a resource (e.g., to support multiple