Mentioned how the publication of new revisions works.

manual.tex

@@ -202,6 +202,7 @@ are available at the following Git repository:
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 \subsection{The Process}
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\label{sec:publishing_process}
 
 Writing and publishing your book is a considerable undertaking.
 This part of the manual will walk you through the different stages
@@ -601,7 +602,7 @@ but have a certain potential to make people happy:
 
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\subsection{Numbers and Versions}
+\subsection{Numbers and Revised Versions}
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 \label{sub:numbers_versions}
 
@@ -612,20 +613,39 @@ So a particular work can be referred to by giving its year and that counter with
 The number of a work is placed on the book cover at two locations:
 on the spine and on the front.
 
-The number of a work never changes, even when its content is revised.
-To indicate a new revision, a version number is used.
-When the work is first published, it must have version at least 1.0
-(smaller versions can be used internally during the proof reading stage).
-The number and version appear at the beginning of the work on a page with meta data
-in the form: number, then the letter \enquote{v} followed by the version.
-\Eg \enquote{2011/7 v1.2} designates version 1.2 of the work number 2011/7.
+The number of a work never changes
+because its content can never change
+once it has been published.
+Nevertheless,
+there is the possibility of publishing a revised edition
+under a new KCSS number.\footnote{%
+  In the old days,
+  published edition could be replaced
+  by a new version.
+  This is not possible any more.
+  As explained, a revision requires
+  a new document to be published,
+  along with a new KCSS number.}
+To do so,
+simply announce your intention
+to publish a revised edition to QA.
+The process will for the most part
+be similar to the publishing process
+as described in \autoref{sec:publishing_process}.
+
+The KCSS number appears at the beginning of the work on a page with meta data,
+for example as \enquote{2011/7}.
 This information optionally may be followed by the word \enquote{dated}
 and then a date on which the version was published,
 in order to give the reader an idea of how recent the version is,
-how much time went by during two versions, \etc.
+how much time went by during two revisions, \etc.
 If a date is given, it should be specified in ISO 8601 form, \ie \mbox{YYYY-MM-DD}.
-For example, when version 1.2 of work 2011/7 was first published on the 15th of November 2011,
-then we write \enquote{2011/7 v1.2 dated 2011-11-15}.
+For example, when work 2011/7 was first published on the 15th of November 2011,
+then we write \enquote{2011/7 dated 2011-11-15}.
+If the work is a revision of a previous work,
+the previous work's KCSS number must be mentioned.
+The KCSS style's \lstinline|\metapage| command
+provides an argument to do so.