--- a/doc/book/admin/create-instance.rst	Wed Mar 27 15:51:50 2019 +0100
+++ b/doc/book/admin/create-instance.rst	Wed Mar 27 15:52:40 2019 +0100
@@ -41,7 +41,7 @@
 located in :file:`~/etc/cubicweb.d/myinstance/*`. To launch it, you
 just type ::
 
-  cubicweb-ctl start -D myinstance
+  cubicweb-ctl pyramid -D myinstance
 
 The option `-D` specifies the *debug mode* : the instance is not
 running in server mode and does not disconnect from the terminal,
@@ -60,9 +60,9 @@
 
 .. note::
 
-  The output of `cubicweb-ctl start -D myinstance` can be
+  The output of `cubicweb-ctl pyramid -D myinstance` can be
   overwhelming. It is possible to reduce the log level with the
-  `--loglevel` parameter as in `cubicweb-ctl start -D myinstance -l
+  `--loglevel` parameter as in `cubicweb-ctl pyramid -D myinstance -l
   info` to filter out all logs under `info` gravity.
 
 upgrade

--- a/doc/book/admin/ldap.rst	Wed Mar 27 15:51:50 2019 +0100
+++ b/doc/book/admin/ldap.rst	Wed Mar 27 15:52:40 2019 +0100
@@ -116,10 +116,9 @@
 Other notes
 -----------
 
-* Cubicweb is able to start if ldap cannot be reached, even on
-  cubicweb-ctl start ... If some source ldap server cannot be used
-  while an instance is running, the corresponding users won't be
-  authenticated but their status will not change (e.g. they will not
+* Cubicweb is able to start if ldap cannot be reached... If some source ldap
+  server cannot be used while an instance is running, the corresponding users
+  won't be authenticated but their status will not change (e.g. they will not
   be deactivated)
 
 * The user-base-dn is a key that helps cubicweb map CWUsers to LDAP

--- a/doc/tutorials/advanced/part01_create-cube.rst	Wed Mar 27 15:51:50 2019 +0100
+++ b/doc/tutorials/advanced/part01_create-cube.rst	Wed Mar 27 15:52:40 2019 +0100
@@ -173,7 +173,7 @@
 
 Once the instance and database are fully initialized, run ::
 
-  cubicweb-ctl start -D sytweb_instance
+  cubicweb-ctl pyramid -D sytweb_instance
 
 to start the instance, check you can connect on it, etc... then go on
 http://localhost:8080 (or with another port if you've modified it)

--- a/doc/tutorials/advanced/part04_ui-base.rst	Wed Mar 27 15:51:50 2019 +0100
+++ b/doc/tutorials/advanced/part04_ui-base.rst	Wed Mar 27 15:52:40 2019 +0100
@@ -327,7 +327,7 @@
 To see if everything is ok on my test instance, I do: ::
 
   $ cubicweb-ctl i18ninstance sytweb_instance
-  $ cubicweb-ctl start -D sytweb_instance
+  $ cubicweb-ctl pyramid -D sytweb_instance
 
 The first command compile i18n catalogs (e.g. generates '.mo' files) for my test
 instance. The second command start it in debug mode, so I can open my browser and

--- a/doc/tutorials/base/customizing-the-application.rst	Wed Mar 27 15:51:50 2019 +0100
+++ b/doc/tutorials/base/customizing-the-application.rst	Wed Mar 27 15:52:40 2019 +0100
@@ -136,7 +136,7 @@
   cubicweb-ctl stop myblog # or Ctrl-C in the terminal running the server in debug mode
   cubicweb-ctl delete myblog
   cubicweb-ctl create myblog myblog
-  cubicweb-ctl start -D myblog
+  cubicweb-ctl pyramid -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
@@ -151,7 +151,7 @@
   type "exit" or Ctrl-D to quit the shell and resume operation
   >>> add_cube('myblog')
   >>>
-  $ cubicweb-ctl start -D myblog
+  $ cubicweb-ctl pyramid -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
@@ -225,7 +225,7 @@
   cubicweb-ctl i18ncube myblog # build/update cube's message catalogs
   # then add translation into .po file into the cube's i18n directory
   cubicweb-ctl i18ninstance myblog # recompile instance's message catalogs
-  cubicweb-ctl restart -D myblog # instance has to be restarted to consider new catalogs
+  # instance has to be restarted to consider new catalogs
 
 You'll then be able to redefine each of them according to your needs and
 preferences. So let's see how to do such thing.