Commit 381d0851 authored by fdrake's avatar fdrake

fix typos

git-svn-id: http://svn.zope.org/repos/main/zc.buildout/trunk@68495 62d5b8a3-27da-0310-9561-8e5933582275
parent dc507e0a
...@@ -19,7 +19,7 @@ buildout". ...@@ -19,7 +19,7 @@ buildout".
I expect that, for many Zope packages, we'll arrange the package I expect that, for many Zope packages, we'll arrange the package
projects in subversion as buildouts. To work on the package, someone projects in subversion as buildouts. To work on the package, someone
will check the project out of Subversion and build it. Building it will check the project out of Subversion and build it. Building it
will assemble all of packages and progras needed to work on it. For will assemble all of packages and programs needed to work on it. For
example, a buildout for a project to provide a new security policy example, a buildout for a project to provide a new security policy
will include the source of the policy and specifications to build the will include the source of the policy and specifications to build the
application for working on it, including: application for working on it, including:
...@@ -44,7 +44,7 @@ Buildouts are defined using configuration files. These files are ...@@ -44,7 +44,7 @@ Buildouts are defined using configuration files. These files are
based on the Python ConfigParser module with some variable-definition based on the Python ConfigParser module with some variable-definition
and substitution extensions. and substitution extensions.
The detailed documentation for the various parts of bukdout can be The detailed documentation for the various parts of buildout can be
found in the following files: found in the following files:
bootstrap.txt bootstrap.txt
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment