--- trunk/lib/Frey/Manual.pod	2008/12/09 20:31:39	778
+++ trunk/lib/Frey/Manual.pod	2008/12/10 20:27:56	801
@@ -2,10 +2,49 @@
 
 This page describes how to use and develop with L<Frey>
 
+=head1 Developer parts
+
+=head2 Moose classes
+
+All Moose classes have simple introspection API which use
+L<Frey::Introspect> to show class and it's pod (using L<Frey::Pod>). 
+
+Example of valid REST URL is
+
+  http://localhost:16001/Frey
+
+which will show L<Frey> class introspection.
+
+You can also add method invocation and optional parameters to C<new>
+constructor like this:
+
+  http://localhost:16001/Frey::Pod/as_markup?class=Frey
+
+this is same using L<Frey::Pod> from perl as
+
+  Frey::Pod->new( class => 'Frey' )->as_markup;
+
+Forms to enter required parameters will be generated automatically, 
+allowing you to explore your data while you are making interface for it.
+
+=head2 Database
+
+FIXME broken if not noted in C<TODO>
+
+For database objects we support L<Fey> and when your objects are created
+C<< with 'Frey::Collection' >> they will have basic CRUD functionality
+implemented by L<Frey::ObjectBrowser>.
+
+=head1 User parts
+
+=head2 Pipes
+
+See L<Frey::Pipe> for now.
+
 =head1 Designing user interaction flows
 
 Frey is all about creating Moose classes as your interaction with pages.
-Each page is instance of class with some parametars received with post or
+Each page is instance of class with some parameters received with post or
 get request.
 
 If you want to access those parameters in your object, you have to define
@@ -50,22 +89,17 @@
 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.
+If I did it right, it should read similar to human language, like Smalltalk.
 
-To make things simple, there are few convertions (with nod to Ruby on Rails)
+To make things simple, there are few conventions (with nod to Ruby on Rails)
 which will help you get started:
 
 
-=head2 default parametars
-
-Default values for
-
-
 =head2 html markup
 
 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
-intermix confitions:
+intermix conditions:
 
   my $html
     = qq|<h1>First</h1>|
@@ -85,14 +119,26 @@
 which is valid perl syntax but doesn't work as expected.
 
 
-=head2 SmallTalk like refactoring
+=head2 Smalltalk like refactoring
 
-Frey is heavily influcenced by SmallTalks, up to the point of syntax. Coding
+Frey is heavily influenced by Smalltalk, up to the point of syntax. Coding
 Frey code should be like playing with L<Frey>. And you might end up with
 result which might surprise you.
 
-Refactoring tools are not new in perl. However,
+Refactoring tools are not new in perl. We have L<PPI>, L<App::Ack> and C<vim>
+so what more do we want?
 
+If you look closely into Smalltalk development work-flow, you really need
+ability to rename class or method without any additional effort. For that,
+we use L<Frey::Class::Refactor> which allows code modifications at source
+level with just few clicks.
+
+=head2 Default values
+
+When L<Frey::Run> tries to create instance of class (usually because of web
+request) it tried to read default values from C<yaml> files in C<etc/> and
+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
 
@@ -118,7 +164,7 @@
 =head1 Command-line integration
 
 One of key points is that L<Frey> runs under your user. This means it has
-access to your termnial, and ssh keys, so beware!
+access to your terminal, and ssh keys, so beware!
 
 =head1 Install
 
@@ -155,7 +201,7 @@
 
 =head2 bin/dev.sh
 
-Recommeded way to start development L<Frey> server since it will restart it
+Recommended way to start development L<Frey> server since it will restart it
 automatically and kill running instance if existing.
 
 =head2 bin/check-syntax.sh
@@ -178,7 +224,7 @@
 =head2 bin/clean-var.sh
 
 Cleanup C<var/> directory which gets a lot of dumps. Most of useful data
-is held forever because I belive that trends are most interesting way to
+is held forever because I believe that trends are most interesting way to
 look at data.
 
 =cut