diff --git a/mps/procedure/version-create/index.txt b/mps/procedure/version-create/index.txt
index 9998e848156..a637390e6f6 100644
--- a/mps/procedure/version-create/index.txt
+++ b/mps/procedure/version-create/index.txt
@@ -1,6 +1,6 @@
 How to create a new version
 
-This document tells you how to create a new version from the master sources.  (For example, if the last version of the MPS is 1.105, with a single release 1.105.0, this document tells you how to take a new clone from the master sources to create version 1.106).  
+This document tells you how to create a new version from the master sources.  (For example, if the last version of the MPS is 1.105, with releases 1.105.0 and 1.105.1, this document tells you how to abandon the 1.105 lineage and take a new clone from the master sources to create version 1.106).  
 
 Readership: MPS staff.  Confidential: no.  Status: rough notes, informally peer-reviewed.  Author: RHSK.
 
@@ -32,6 +32,13 @@ Entry in the table at <http://info.ravenbrook.com/project/mps/version/>.
 
 __How to make a new version:__
 
+0. Some files contain an MPS version-name.  What version-name do the *master* copies of these files contain?  It depends.  Some contain the pseudo-version-name "master": you will leave these files unchanged on master, and only update them on the version branch (see step 6 below).  Others, even in master, refer to the expected next version-name: you should update these files before making the branch.  Make these files contain the expected new version-name, and/or information pertinent to the new version:
+  master/readme.txt
+  master/code/version.c
+  master/example/hello-world/index.txt
+  (check the "Setup" section of procedure/release-build for the full list of these files)
+Submit these files before you continue.
+
 1. Make the branch:  p4 branch mps/version/A.BBB
 Description:
   Branching master sources for version A.BBB.
@@ -53,14 +60,20 @@ Always edit version/A.BBB/index.html, eg. (case-sensitive):
   "of the Master version"  ->  "of Version A.BBB"
   "Master"  ->  "Version A.BBB"
 Less importantly, edit various other files.  See change 30260.  
-Please do edit version/A.BBB/example/hello-world/index.txt.
 
-7. Do an empty-integrate of these changes back on to the masters, so P4 thinks it's done and doesn't keep suggesting it:
+7. Do an empty-integrate of this change back on to the masters, so P4 thinks it's done and doesn't keep suggesting it:
   p4 integrate -r -b mps/version/A.BBB <Files Edited Master->Version>
   p4 resolve -ay <Files Edited Master->Version>
 
 END OF PROCEDURE
 
+
+DOCUMENT HISTORY
+
+2005-10-03  RHSK  Created.
+2006-12-27  RHSK  Step 0: edit some files on master before making version branch
+
+
 COPYRIGHT AND LICENSE
 
 Copyright (C) 2005-2006 Ravenbrook Limited.  All rights reserved.