# HG changeset patch
# User Laurent Peuch <cortex@worlddomination.be>
# Date 1550771619 -3600
# Node ID 72536c93f3c1262ae9a35336f3d1275dc9ac2f8b
# Parent  0bb15614e7566406e612f00259bfad5d0b55cee8
[doc] explains what the <X.Y.Z> means

diff -r 0bb15614e756 -r 72536c93f3c1 doc/tutorials/advanced/part02_security.rst
--- a/doc/tutorials/advanced/part02_security.rst	Thu Feb 21 18:53:03 2019 +0100
+++ b/doc/tutorials/advanced/part02_security.rst	Thu Feb 21 18:53:39 2019 +0100
@@ -419,8 +419,9 @@
 don't want to create a new one, but to migrate the existing one. Let's see how to
 do that.
 
-file named file:`<X.Y.Z>_Any.py` ('Any' being there mostly for historical reasons).
 Migration commands should be put in the cube's :file:`migration` directory, in a
+file named :file:`<X.Y.Z>_Any.py` ('Any' being there mostly for historical
+reasons and '<X.Y.Z>' being the version number of the cube we are going to release.)
 
 Here I'll create a :file:`migration/0.2.0_Any.py` file containing the following
 instructions: