[Checkins] SVN: bluebream/website/docs/v1.0/manual/ bit cleaup

[Baiju M]

Log message for revision 109119:
  bit cleaup
  

Changed:
  U   bluebream/website/docs/v1.0/manual/browserresource.rst
  U   bluebream/website/docs/v1.0/manual/contentcomponent.rst

-=-
Modified: bluebream/website/docs/v1.0/manual/browserresource.rst
===================================================================
--- bluebream/website/docs/v1.0/manual/browserresource.rst	2010-02-18 12:43:43 UTC (rev 109118)
+++ bluebream/website/docs/v1.0/manual/browserresource.rst	2010-02-18 12:44:11 UTC (rev 109119)
@@ -13,8 +13,8 @@
 Certain presentation, like images and style sheets are not associated
 with any other component, so that one cannot create a view.  To solve
 this problem, resources were developed, which are presentation
-components that do not require any context.  This mini-chapter will
-demonstrate how resources are created and registered with Zope 3.
+components that do not require any context.  This chapter will
+demonstrate how resources are created and registered with BlueBream.
 
 The first goal is to register a simple plain-text file called
 ``resource.txt`` as a browser resource.  The first step is to create
@@ -44,7 +44,7 @@
 is added to.  By default, the default layer is selected.
 
 Once you hook up the configuration file to the main configuration
-path and restart Zope 3, you should be able to access the resource
+path and restart BlueBream, you should be able to access the resource
 now via a Browser using http://localhost:8080/@@/resource.txt. The
 @@/ in the URL tells the traversal mechanism that the following
 object is a resource.

Modified: bluebream/website/docs/v1.0/manual/contentcomponent.rst
===================================================================
--- bluebream/website/docs/v1.0/manual/contentcomponent.rst	2010-02-18 12:43:43 UTC (rev 109118)
+++ bluebream/website/docs/v1.0/manual/contentcomponent.rst	2010-02-18 12:44:11 UTC (rev 109119)
@@ -45,38 +45,42 @@
 First look at the user stories, this book will implement these stories in
 coming chapters.
 
-  1. Individual small ticket collector for each project.  Many collectors can
-     be added to one running zope.
+1. Individual small ticket collector for each project.  Many
+   collectors can be added to one running zope.
 
-  2. Any number of tickets can be added to one collector.
+2. Any number of tickets can be added to one collector.
 
-  3. Each ticket will be added with a description and one initial comment.
+3. Each ticket will be added with a description and one initial
+   comment.
 
-  4. Additional comments can be added to tickets.
+4. Additional comments can be added to tickets.
 
 This chapter starts a simple implementation of ticket collector.
 
-As stated above, our goal is to develop a fully functional, though not
-great-looking, web-based ticket collector application.  The root object will be
-the ``Collector``, which can contain ``Ticket`` objects from various users.
-Since you want to allow people to respond to various tickets, you have to allow
-tickets to contain replies, which are ``Comment`` objects.
+As stated above, our goal is to develop a fully functional, though
+not great-looking, web-based ticket collector application.  The root
+object will be the ``Collector``, which can contain ``Ticket``
+objects from various users.  Since you want to allow people to
+respond to various tickets, you have to allow tickets to contain
+replies, which are ``Comment`` objects.
 
-That means you have two container-based components: The ``Collector`` contains
-only tickets and can be added to any Folder or container that wishes to be able
-to contain it.  To make the ticket collector more interesting, it also has a
-description, which briefly introduces the subject/theme of the discussions
-hosted.  ``Tickets``, on the other hand should be only contained by ticket
-collector.  They will each have a summary and a description.  And last
-``Comment`` should be only contained by tickets.
+That means you have two container-based components: The ``Collector``
+contains only tickets and can be added to any Folder or container
+that wishes to be able to contain it.  To make the ticket collector
+more interesting, it also has a description, which briefly introduces
+the subject/theme of the discussions hosted.  ``Tickets``, on the
+other hand should be only contained by ticket collector.  They will
+each have a summary and a description.  And last ``Comment`` should
+be only contained by tickets.
 
-This setup should contain all the essential things that you need to make the
-object usable.  Later on you will associate a lot of other meta-data with these
-components to integrate them even better into Zope 3 and add additional
-functionality.
+This setup should contain all the essential things that you need to
+make the object usable.  Later on you will associate a lot of other
+meta-data with these components to integrate them even better into
+BlueBream and add additional functionality.
 
-The most convenient place to put your package is ``$HOME/myzope/lib/python``.
-To create that package, add a directory using::
+The most convenient place to put your package is
+``$HOME/myzope/lib/python``.  To create that package, add a directory
+using::
 
   $ cd $HOME/myzope/lib/python/
   $ mkdir collector