[Checkins] SVN: zc.zope3recipes/trunk/zc/zope3recipes/README.txt normalize whitespace

[Fred Drake]

Log message for revision 130197:
  normalize whitespace
  

Changed:
  U   zc.zope3recipes/trunk/zc/zope3recipes/README.txt

-=-
Modified: zc.zope3recipes/trunk/zc/zope3recipes/README.txt
===================================================================
--- zc.zope3recipes/trunk/zc/zope3recipes/README.txt	2013-04-11 20:25:14 UTC (rev 130196)
+++ zc.zope3recipes/trunk/zc/zope3recipes/README.txt	2013-04-11 20:35:31 UTC (rev 130197)
@@ -8,6 +8,7 @@
 invokes the application with a specific instance configuration.  A
 single application may have many instances.
 
+
 Building Zope 3 applications (from eggs)
 ========================================
 
@@ -23,11 +24,11 @@
 The 'application' recipe accepts the following options:
 
 site.zcml
-  The contents of site.zcml.
+    The contents of site.zcml.
 
 eggs
-  The names of one or more eggs, with their dependencies that should
-  be included in the Python path of the generated scripts.
+    The names of one or more eggs, with their dependencies that should
+    be included in the Python path of the generated scripts.
 
 
 Lets define some (bogus) eggs that we can use in our application:
@@ -399,13 +400,13 @@
 the same configuration options plus the following one:
 
 zope3
-  The name of a section defining a location option that gives the
-  location of a Zope installation.  This can be either a checkout or a
-  distribution.  If the location has a lib/python subdirectory, it is
-  treated as a distribution, otherwise, it must have a src
-  subdirectory and will be treated as a checkout. This option defaults
-  to "zope3".  And if location is empty, the application will run solely
-  from eggs.
+    The name of a section defining a location option that gives the
+    location of a Zope installation.  This can be either a checkout or a
+    distribution.  If the location has a lib/python subdirectory, it is
+    treated as a distribution, otherwise, it must have a src
+    subdirectory and will be treated as a checkout. This option defaults
+    to "zope3".  And if location is empty, the application will run
+    solely from eggs.
 
 Let's look at an example.  We'll make a faux zope installation:
 
@@ -922,6 +923,7 @@
       <grant role="zope.Manager" principal="zope.globalmgr" />
     </configure>
 
+
 Defining Zope3 instances
 ========================
 
@@ -1664,6 +1666,7 @@
       </logfile>
     </eventlog>
 
+
 Instance names
 --------------
 
@@ -1830,6 +1833,7 @@
 http://pypi.python.org/pypi/zc.recipe.deployment#configuration-files,
 to define a site.zcml file using the buildout.)
 
+
 Log files
 ---------
 
@@ -1850,6 +1854,7 @@
 useful when running Zope in foreground mode and where it can be
 captured by the zdaemon transcript log.
 
+
 Unix Deployments
 ----------------
 
@@ -1986,7 +1991,6 @@
     >>> ls(root, 'etc', 'logrotate.d')
     -  myapp-run-instance
 
-
 The configuration files have changed to reflect the deployment
 locations:
 
@@ -2042,7 +2046,6 @@
       endscript
     }
 
-
 If we provide an alternate instance name, that will be reflected in
 the generated files:
 
@@ -3081,6 +3084,7 @@
     # print "starting debugzope..."
     execfile(debugzope)
 
+
 Paste-deployment support
 ========================
 
@@ -3143,7 +3147,6 @@
     Installing instance.
     Generated script '/sample-buildout/bin/instance'.
 
-
     >>> cat('parts', 'myapp', 'runzope')
     #!/usr/local/python/2.6/bin/python2.6
     <BLANKLINE>
@@ -3163,7 +3166,6 @@
     if __name__ == '__main__':
         sys.exit(paste.script.command.run(['serve']+sys.argv[1:]))
 
-
     >>> cat('parts', 'instance', 'zope.conf')
     site-definition /sample-buildout/parts/myapp/site.zcml
     <BLANKLINE>
@@ -3222,7 +3224,7 @@
     <BLANKLINE>
     [server:main]
     use = egg:zope.server
-    host = 
+    host =
     port = 8080
     threads = 1