[Checkins] SVN: bluebream/website/docs/v1.0/tutorial1.rst bit cleanup 1 (tutoriol 1)

[Baiju M]

Log message for revision 108455:
  bit cleanup 1 (tutoriol 1)
  

Changed:
  U   bluebream/website/docs/v1.0/tutorial1.rst

-=-
Modified: bluebream/website/docs/v1.0/tutorial1.rst
===================================================================
--- bluebream/website/docs/v1.0/tutorial1.rst	2010-01-25 02:51:21 UTC (rev 108454)
+++ bluebream/website/docs/v1.0/tutorial1.rst	2010-01-25 02:57:21 UTC (rev 108455)
@@ -248,7 +248,7 @@
   eggs = ticketcollector
 
 The buildout configuration file is divided into multiple sections
-called parts.  The main part is called ``[buildout]``, and that is
+called *parts*.  The main part is called ``[buildout]``, and that is
 given as the second part in the above configuration file.  We have
 added a part named ``[config]`` for convenience which includes some
 common options referred from other places.  Each part will be handled
@@ -287,7 +287,7 @@
 
 - ``log`` -- All log files goes here.
 
-Let's look at the main ``[buildout]`` part details now::
+Let's look at the main ``[buildout]`` part::
 
   [buildout]
   develop = .
@@ -302,9 +302,9 @@
 create develop egg link inside ``develop-eggs`` directory.  The link
 file should contain path to location where the Python package is
 residing.  So, buildout will make sure that the packages is always
-importable.  The value of ``develop`` option could be a relative
-path, as given above or absolute path to some directory.  You can
-also add multiple lines to ``develop`` option with different paths.
+importable.  The value of ``develop`` option could be a relative path
+as given above or absolute path to some directory.  You can also add
+multiple lines to ``develop`` option with different paths.
 
 The ``extends`` option says buildout to include the full content of
 ``versions.cfg`` file as part the configuration.  The
@@ -346,9 +346,10 @@
   input = templates/zope_conf.in
   output = etc/zope.conf
 
-This part must be very self explanatory, it simply creates a
-``zope.conf`` file from a template.  This template recipe is very
-common among Buildout users.  Here is the template file
+This part must be very self explanatory, it creates a ``zope.conf``
+file from one template file.  This `collective.recipe.template recipe
+<http://pypi.python.org/pypi/collective.recipe.template>`_ is very
+popular among Buildout users.  Here is the template file
 (``templates/zope_conf.in``)::
 
   # Identify the component configuration used to define the site: