doc/book/en/development/datamodel/define-workflows.rst
branchstable
changeset 2175 16d3c37c5d28
parent 2172 cf8f9180e63e
child 2307 060c3f3f7d28
--- a/doc/book/en/development/datamodel/define-workflows.rst	Thu Jun 25 20:29:27 2009 +0200
+++ b/doc/book/en/development/datamodel/define-workflows.rst	Fri Jun 26 13:51:08 2009 +0200
@@ -14,7 +14,7 @@
 
 We will define a simple workflow for a blog, with only the following
 two states: `submitted` and `published`. So first, we create a simple
-`CubicWeb` in ten minutes (see :ref:`BlogTenMinutes`).
+*CubicWeb* in ten minutes (see :ref:`BlogFiveMinutes`).
 
 Set-up a workflow
 -----------------
@@ -60,7 +60,7 @@
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The ``postcreate.py`` script is executed in a special environment, adding
-several `CubicWeb` primitives that can be used.
+several *CubicWeb* primitives that can be used.
 They are all defined in the ``class ServerMigrationHelper``.
 We will only discuss the methods we use to create a workflow in this example.
 
@@ -131,7 +131,7 @@
 ~~~~~~~~~~~~~~
 
 A workflow is a collection of entities of type ``State`` and of type ``Transition``
-which are standard `CubicWeb` entity types.
+which are standard *CubicWeb* entity types.
 For instance, the following lines::
 
   submitted = add_state(_('submitted'), 'BlogEntry', initial=True)