--- trunk/lib/Frey/Manual.pod	2009/01/06 13:18:43	940
+++ trunk/lib/Frey/Manual.pod	2009/01/06 13:20:39	941
@@ -84,18 +84,26 @@
 
 You don't even have to create initial entry form as L<Frey::Run>,
 which will start your L<Moose> classes, will call L<Frey::Action>
-for help and generate initial form for you.
+for help and generate initial form for you. If this magic is wrong,
+just define C<< sub render_pipe { 'radio' } >> to force rending of
+C<pipe> attribute as radio buttons.
+
+=head2 Easy skeletons
 
 Creating files is mess, so L<Frey::Class::Create/create_class_source> will
 create class and test skeleton for you.
 
 If I did it right, it should read similar to human language, like Smalltalk.
 
+L<Frey> is careful to provide enough magic to build skeletons just of files
+which contain some specific logic to your aplication, so it's not massive code
+generation as in Java...
+
 To make things simple, there are few conventions (with nod to Ruby on Rails)
 which will help you get started:
 
 
-=head2 html markup
+=head2 HTML markup convetion
 
 HTML markup should be enclosed in C< qq| > and C< | > quotes. There is also
 funny but very readable convention of multi line html when you have to
@@ -140,7 +148,8 @@
 if it doesn't find all of required values it will invoke L<Frey::Action> to
 create end-user html form with missing fields.
 
-=head2 examples
+
+=head1 Examples
 
 To help you get started, here are few implemented flows in Frey: