[Checkins] SVN: grok/trunk/ cleanup buildout.cfg, CHANGES.txt, better describe the paster serve --reload option

[Michael Haubenwallner]

Log message for revision 100322:
  cleanup buildout.cfg, CHANGES.txt, better describe the paster serve --reload option

Changed:
  U   grok/trunk/CHANGES.txt
  U   grok/trunk/buildout.cfg
  U   grok/trunk/doc/tutorial.rst

-=-
Modified: grok/trunk/CHANGES.txt
===================================================================
--- grok/trunk/CHANGES.txt	2009-05-23 22:10:13 UTC (rev 100321)
+++ grok/trunk/CHANGES.txt	2009-05-24 08:36:22 UTC (rev 100322)
@@ -4,7 +4,7 @@
 1.0b1 (unreleased)
 ==================
 
-* Corrected Content-type; JSON views now report a 'application/json'.
+* Corrected Content-type; JSON views now report 'application/json'.
 
 
 1.0a4 (2009-05-21)

Modified: grok/trunk/buildout.cfg
===================================================================
--- grok/trunk/buildout.cfg	2009-05-23 22:10:13 UTC (rev 100321)
+++ grok/trunk/buildout.cfg	2009-05-24 08:36:22 UTC (rev 100322)
@@ -13,12 +13,10 @@
     .
     grokdocs
     grokwiki
-    ../grokcore.view-trunk
 versions = versions
 extensions = buildout.dumppickedversions
 
 [versions]
-grokcore.view =
 
 [docs]
 recipe = zc.recipe.egg

Modified: grok/trunk/doc/tutorial.rst
===================================================================
--- grok/trunk/doc/tutorial.rst	2009-05-23 22:10:13 UTC (rev 100321)
+++ grok/trunk/doc/tutorial.rst	2009-05-24 08:36:22 UTC (rev 100322)
@@ -237,7 +237,7 @@
 this tutorial. It's just stopping Zope and starting it again:
 ``CTRL-c`` and then ``bin/paster serve parts/etc/deploy.ini`` from your Sample
 project directory. Alternatively, you can use the --reload flag to start
-up paster with a monitor that scans your code base for changes and 
+up paster with a monitor that scans your code base (python files only) for changes and 
 automatically restart the Zope server every time you make a change::
  
   $ bin/paster serve --reload parts/etc/deploy.ini