# HG changeset patch
# User Sylvain Thénault <sylvain.thenault@logilab.fr>
# Date 1295277441 -3600
# Node ID 829b068eb9c7a3d26ead441b9bfeb33230b7c8c0
# Parent  6c7adf825b3c451b0b5e1fb97423773cec5866e3
[tutorial] make things clearer

diff -r 6c7adf825b3c -r 829b068eb9c7 doc/book/en/tutorials/base/customizing-the-application.rst
--- a/doc/book/en/tutorials/base/customizing-the-application.rst	Mon Jan 17 15:57:26 2011 +0100
+++ b/doc/book/en/tutorials/base/customizing-the-application.rst	Mon Jan 17 16:17:21 2011 +0100
@@ -132,9 +132,10 @@
 
 One easy way, as we've no really valuable data in the instance would be to trash and recreated it::
 
-  cubicweb-ctl stop myblog
+  cubicweb-ctl stop myblog # or Ctrl-C in the terminal running the server in debug mode
   cubicweb-ctl delete myblog
   cubicweb-ctl create myblog
+  cubicweb-ctl start -D myblog
 
 Another way is to add our cube to the instance using the cubicweb-ctl shell
 facility. It's a python shell connected to the instance with some special
@@ -142,13 +143,14 @@
 scripts, which are not covered in this tutorial). In that case, we're interested
 in the `add_cube` command: ::
 
-  $ cubicweb-ctl stop myblog
+  $ cubicweb-ctl stop myblog # or Ctrl-C in the terminal running the server in debug mode
   $ cubicweb-ctl shell myblog
   entering the migration python shell
   just type migration commands or arbitrary python code and type ENTER to execute it
   type "exit" or Ctrl-D to quit the shell and resume operation
   >>> add_cube('myblog')
   >>>
+  $ cubicweb-ctl start -D myblog
 
 The `add_cube` command is enough since it automatically updates our
 application to the cube's schema. There are plenty of other migration