[Jifty-commit] r2330 - jifty/trunk/lib/Jifty/Manual

[jifty-commit at lists.jifty.org]

Author: agentz
Date: Tue Dec  5 03:44:27 2006
New Revision: 2330

Modified:
   jifty/trunk/lib/Jifty/Manual/Continuations.pod

Log:
[Jifty::Manual::Continuations]
- typo fixes.

Modified: jifty/trunk/lib/Jifty/Manual/Continuations.pod
==============================================================================
--- jifty/trunk/lib/Jifty/Manual/Continuations.pod	(original)
+++ jifty/trunk/lib/Jifty/Manual/Continuations.pod	Tue Dec  5 03:44:27 2006
@@ -10,7 +10,7 @@
 that state at any later time, by calling the continuation with, and
 evaluation of that interpreter state will resume.  They're a concept
 that first arose in LISP, but has implementations these days in Ruby,
-Scheme, Haskell, Smalltalk, to name a few.
+Scheme, Haskell, Smalltalk (just to name a few).
 
 Thus, continuations allow you to preserve context, and return to it
 later.  This is amazingly useful in web programming, which is limited
@@ -116,7 +116,7 @@
 
 The first page renders the entry box for the first number; the second
 input is hidden because Jifty notices that it is based on a mapped
-value: i.e., its default is set to C<{request_argument => "number"}>
+value: i.e., its default is set to C<< {request_argument => "number"} >>
 instead of a plain scalar value.
 
 Pressing the button validates the action but does not complete
@@ -168,7 +168,7 @@
 to C</protected>.
 
 As currently impelented, these redirect-from-dispatcher tangents works
-exactly like like rendered-as-links tangents, in that when they return,
+exactly like rendered-as-links tangents, in that when they return,
 I<all> rules in the dispatcher are still executed from the start.
 Therefore the C<unless> guard in the C<before '/protected'> rule above
 is neccessary to prevent recursion.