[Checkins] SVN: bluebream/trunk/docs/source/ run ispell :)

Baiju M baiju.m.mail at gmail.com
Wed Jan 13 06:46:53 EST 2010


Log message for revision 108103:
  run ispell :)
  

Changed:
  U   bluebream/trunk/docs/source/gettingstarted.rst
  U   bluebream/trunk/docs/source/glossary.rst
  U   bluebream/trunk/docs/source/howto/defaultview.rst
  U   bluebream/trunk/docs/source/introduction.rst
  U   bluebream/trunk/docs/source/tutorial.rst

-=-
Modified: bluebream/trunk/docs/source/gettingstarted.rst
===================================================================
--- bluebream/trunk/docs/source/gettingstarted.rst	2010-01-13 11:18:51 UTC (rev 108102)
+++ bluebream/trunk/docs/source/gettingstarted.rst	2010-01-13 11:46:53 UTC (rev 108103)
@@ -9,9 +9,9 @@
 ------------
 
 This chapter narrate the process of creating a new web application
-project using BlueBream.  Also it gives few excercises to familiarize
+project using BlueBream.  Also it gives few exercises to familiarize
 the basic concepts in BlueBream.  We suggest you to try out all the
-commands and excercises given here.  Before proceeding, here is an
+commands and exercises given here.  Before proceeding, here is an
 overview of the sections.
 
 - **Preparations:** -- Prerequisites and preparations you need to
@@ -29,7 +29,7 @@
   commands.
 
 - **Package directory structure:** -- Show the directory structure
-  and decribe the purpose of each directories and files.
+  and describe the purpose of each directories and files.
 
 - At the end, few hello world examples are also given.
 
@@ -46,14 +46,14 @@
 distribute is installed you will get an ``easy_install`` command
 which you can use to install ``bluebream`` distribution.
 
-You can also install BlueBream inside an isolated Python enironment
+You can also install BlueBream inside an isolated Python environment
 created by `virtualenv <http://pypi.python.org/pypi/virtualenv>`_.
 Although, *virtualenv* is not necessary as we are going to use
 `Buildout <http://www.buildout.org>`_ for repeatable, isolated
 working environment.  Buildout is a declarative, configuration driven
-build system reccommended by BlueBream.
+build system recommended by BlueBream.
 
-It is reccommended to use a custom built Python for working with
+It is recommended to use a custom built Python for working with
 BlueBream.  You will be required to install a C compiler (gcc) in
 your system.  Internet access to `PyPI <http://pypi.python.org>`_ is
 required to perform installation of ``bluebream`` distribution.
@@ -76,7 +76,7 @@
 As mentioned earlier, Internet access to `PyPI
 <http://pypi.python.org>`_ is required to perform installation of
 ``bluebream`` distribution.  If you use any proxy, make sure it
-works.  The ``easy_install`` will look for the enviroment variable
+works.  The ``easy_install`` will look for the environment variable
 named ``http_proxy`` in GNU/Linux platforms.  You can set it like this::
 
  $ set http_proxy="http://username:password@PROXY-IP-ADDRESS:PORT"
@@ -140,7 +140,7 @@
 - ``license_name`` -- License name
 
 - ``zip_safe`` -- ``True``, if the package can be distributed as a
-  .zip file othewise ``False``.
+  .zip file otherwise ``False``.
 
 If you are in a hurry, you can simply press *Enter/Return* key and
 change the values later.  But it would be a good idea, if you provide
@@ -218,7 +218,7 @@
   |-- var/
   `-- versions.cfg
   
-The name of toplevel directory will be always what you gave as
+The name of top-level directory will be always what you gave as
 project name in the wizard.  The name of egg also will be same as
 that of package name by default.  But if you want, you can change it
 to something else from ``setup.py``.  Here are the details about
@@ -274,9 +274,9 @@
 
 - ``src/mynamespace/main/__init__.py`` -- The main package
 
-- ``src/mynamespace/main/interfaces.py`` -- Interface definitiions
+- ``src/mynamespace/main/interfaces.py`` -- Interface definitions
 
-- ``src/mynamespace/main/README.txt`` -- main packages's readme
+- ``src/mynamespace/main/README.txt`` -- main packages' README
 
 - ``src/mynamespace/main/securitypolicy.zcml`` -- security policy
   declarations which is included from site.zcml
@@ -383,7 +383,7 @@
 Create a page template
 ~~~~~~~~~~~~~~~~~~~~~~
 
-First you need to create a page template file inside your pacakge.
+First you need to create a page template file inside your package.
 You can save it as ``src/mynamespace/main/helloworld.pt``, with the
 following content::
 

Modified: bluebream/trunk/docs/source/glossary.rst
===================================================================
--- bluebream/trunk/docs/source/glossary.rst	2010-01-13 11:18:51 UTC (rev 108102)
+++ bluebream/trunk/docs/source/glossary.rst	2010-01-13 11:46:53 UTC (rev 108103)
@@ -45,5 +45,5 @@
 
   Zope Foundation
     The `Zope Foundation <http://foundation.zope.org>`_ is a
-    not-for-profit organisation that provides support for the Zope
+    not-for-profit organization that provides support for the Zope
     community and the Zope platform and its associated software.

Modified: bluebream/trunk/docs/source/howto/defaultview.rst
===================================================================
--- bluebream/trunk/docs/source/howto/defaultview.rst	2010-01-13 11:18:51 UTC (rev 108102)
+++ bluebream/trunk/docs/source/howto/defaultview.rst	2010-01-13 11:46:53 UTC (rev 108103)
@@ -10,8 +10,8 @@
 provided there is no object with same same exist inside the
 container.  In the above example, If there is no object named
 ``testview`` inside ``myobject`` container, then, the view can be
-accessed like ``myobject/testview``.  However, BlueBream reccommends
-to use ``@@`` symbols always to access view to avoid ambiguity.
+accessed like ``myobject/testview``.  However, BlueBream recommend to
+use ``@@`` symbols always to access view to avoid ambiguity.
 
 If you try to access an object without specifying any view name,
 BlueBream will try to display the default view registered.  You can
@@ -30,7 +30,7 @@
   URL=http://localhost:8080>)
 
 If you have created the application using ``bluebream`` project
-template, you won't get this error.  Beacause there is already a a
+template, you won't get this error.  Because there is already a a
 default view name (``index``) is configured in ``application.zcml``
 configuration file inside the main package.
 
@@ -61,7 +61,7 @@
 If ``index`` is registered as the name for default view, BlueBream
 will try to get ``@@index`` view for any containers, if the view is
 not explicitly mentioned in the URL.  However, you need to have a
-browser view registered to acces the view, otherwise a ``NotFound``
+browser view registered to access the view, otherwise a ``NotFound``
 error will be raised as mentioned above.
 
 More details about registering a browser view using ``browser:page``

Modified: bluebream/trunk/docs/source/introduction.rst
===================================================================
--- bluebream/trunk/docs/source/introduction.rst	2010-01-13 11:18:51 UTC (rev 108102)
+++ bluebream/trunk/docs/source/introduction.rst	2010-01-13 11:46:53 UTC (rev 108103)
@@ -51,7 +51,7 @@
 - BlueBream has schema engine and automatic form generation machinery
   (zope.schema, zope.formlib)
 
-The main aim of this book is to create a free online book about
+The main aim of this book is to create a free on-line book about
 BlueBream.  This book will cover how to develop web applications
 using BlueBream components. You suggestions and edits are always
 welcome.
@@ -80,7 +80,7 @@
 language called Python, and provided a web publishing facility, text
 templating, and an object database, respectively. Digital Creations
 developed a commercial application server based on their three
-opensource components. This product was called Principia. In November
+open source components. This product was called Principia. In November
 of 1998, investor Hadar Pedhazur convinced Digital Creations to open
 source Principia. These packages evolved into what are now the core
 components of Zope 2.
@@ -119,7 +119,7 @@
 
 The :ref:`started-getting` chapter narrate the process of creating a
 new web application project using BlueBream.  Also it gives few
-excercises to familiarize the basic concepts in BlueBream.
+exercises to familiarize the basic concepts in BlueBream.
 
 Tutorial
 ~~~~~~~~
@@ -131,7 +131,7 @@
 FAQ
 ~~~
 
-These are FAQs collected from mailing lists, blogs and other online
+These are FAQs collected from mailing lists, blogs and other on-line
 resources.
 
 HOWTOs

Modified: bluebream/trunk/docs/source/tutorial.rst
===================================================================
--- bluebream/trunk/docs/source/tutorial.rst	2010-01-13 11:18:51 UTC (rev 108102)
+++ bluebream/trunk/docs/source/tutorial.rst	2010-01-13 11:46:53 UTC (rev 108103)
@@ -8,13 +8,13 @@
 Introduction
 ------------
 
-In the :ref:`started-getting` chapater you learned how to install
+In the :ref:`started-getting` chapter you learned how to install
 BlueBream and create a new project using the ``bluebream`` project
 template.  In this chapter, we will explore creating a simple ticket
 collector application.  This will help you to familiarize more
 concepts in BlueBream.
 
-Befire proceeding, we will see the user stories:
+Before proceeding, we will see the user stories:
 
 1. Individual small ticket collector for each project.  Many
    collectors can be added to one running BlueBream.
@@ -114,7 +114,7 @@
 and some are skipped.  If you want, it is possible to change the
 values provided here later.  But changing the package name or
 namespace package name may not be easy as changing the description.
-The reason is that, the name and namepace package might be referred
+The reason is that, the name and namespace package might be referred
 from many places.
 
 If you change directory to ``ticketcollector``, you can see few
@@ -126,7 +126,7 @@
 
 Once the project directory layout is ready, you can add it to your
 version controlling system.  You need **not** to add
-``src/ticketcollector.egg-info`` directory as it is generted by
+``src/ticketcollector.egg-info`` directory as it is generated by
 setuptools.  Here is an example using `bzr
 <http://bazaar.canonical.com/en/>`_::
 
@@ -148,16 +148,16 @@
 After adding code to version controlling system, you need to
 bootstrap the Buildout and run ``buildout`` command to build the
 application.  The purpose of Buildout is to automate all the process
-involved in bulding an Python application/package from scratch.  The
+involved in building an Python application/package from scratch.  The
 only basic requirement for Buildout is a Python installation.
 Buildout provides a bootstrapping script to to initialize Buildout.
 This bootstrap script named ``bootstrap.py`` will do these things:
 
 - Download and install ``setuptools`` package from PyPI
 
-- Download and install ``zc.buildout`` package fron PyPI
+- Download and install ``zc.buildout`` package from PyPI
 
-- Create directory struture eg:- bin/ eggs/ parts/ develop-eggs/
+- Create directory structure eg:- bin/ eggs/ parts/ develop-eggs/
 
 - Create a script inside ``bin`` directory named ``buildout``
 
@@ -178,10 +178,10 @@
 
 - The ``parts`` is where Buildout save all output generated by buildout.
   Buildout expects you to not change anything inside parts directory
-  as it is autogenerated by Buildout.
+  as it is auto generated by Buildout.
 
 - The ``develop-eggs`` directory is where buildout save links to all
-  locally develping Python eggs.
+  locally developing Python eggs.
 
 Now you are ready to run the ``bin/buildout`` to build the
 application.  Before running the buildout, let's see the content of
@@ -218,9 +218,9 @@
   recipe = zc.recipe.testrunner
   eggs = ticketcollector
 
-The buildout configration file is devided into muliple sections
+The buildout configuration file is divided into multiple sections
 called parts.  The main part is called ``[buildout]``, and that is
-given as the second part in the above configration file.  We have
+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
 by the Buildout plugin mechanism called recipes, with few exceptions.
@@ -247,7 +247,7 @@
 
 - ``site_zcml`` -- this is the location where final ``site.zcml``
   file will be residing.  The value of ``${buildout:directory}`` will
-  be the absolute path to the directory where you are runnning
+  be the absolute path to the directory where you are running
   buildout.  In the above example, the value will be:
   ``/projects/ticketcollector``.  So, the value of ``site_zcml`` will
   be: ``/projects/ticketcollector/etc/site.zcml``
@@ -269,7 +269,7 @@
 folder, otherwise it will download and install eggs.  The buildout
 also created three more scripts inside ``bin`` directory.
 
-- The ``paster`` command can be used to run webserver.
+- The ``paster`` command can be used to run web server.
 
 - The ``breampy`` command provides a custom Python interpreter with
   all eggs included in path.



More information about the checkins mailing list