[libbread-board-perl] 13/66: Improve doc and example code

[Jonas Smedegaard]

This is an automated email from the git hooks/post-receive script.

js pushed a commit to branch master
in repository libbread-board-perl.

commit 2dddf83fc5247c9bf882321731ee5ad83d9c1dc9
Author: zdk <nx2zdk at gmail.com>
Date:   Mon Sep 10 17:12:53 2012 +0700

    Improve doc and example code
---
 lib/Bread/Board/Manual/Concepts.pod |   16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/lib/Bread/Board/Manual/Concepts.pod b/lib/Bread/Board/Manual/Concepts.pod
index 8518a1b..f288b39 100644
--- a/lib/Bread/Board/Manual/Concepts.pod
+++ b/lib/Bread/Board/Manual/Concepts.pod
@@ -313,10 +313,10 @@ whose service is already resolved to that service.
 
 =head2 Hierarchal Containers
 
-Up until now, we have see basic containers which only have a single
-level of components. As you application grows larger it may become
+Up until now, we have seen basic containers which only have a single
+level of components. As your application grows larger it may become
 useful to have a more hierarchal approach to your containers.
-Bread::Board::Container supports this behavior through it's many
+Bread::Board::Container supports this behavior through its many
 subcontainer methods. Here is an example of how we might re-arrange
 the previous examples using subcontainers.
 
@@ -325,7 +325,7 @@ the previous examples using subcontainers.
   my $db_c = Bread::Board::Container->new( name => 'database' );
   $db_c->add_service(
       Bread::Board::BlockInjection->new(
-          name  => 'connection'
+          name  => 'db_conn'
           block => sub {
               my $s = shift;
               return DBI->connect(
@@ -410,9 +410,9 @@ the previous examples using subcontainers.
       )
   );
 
-So as can be seen above, hierarchal containers can be used as a
-form of namespacing to better organize your Bread::Board
-configuration. As is shown with the 'authenticator' service,
+So, as an example that can be seen above, hierarchal containers can be used as a
+form of namespacing to organize your Bread::Board
+configuration better. As it is shown with the 'authenticator' service,
 it is possible to address services outside of your container
 using path notation. In this case the 'authenticator' service
 makes the assumption that it's parent container has both a
@@ -432,7 +432,7 @@ Bread::Board configuration using the sugar layer.
   my $c = container 'app' => as {
 
       container 'database' => as {
-          service 'connection' => (
+          service 'db_conn' => (
               block => sub {
                   my $s = shift;
                   return DBI->connect(

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libbread-board-perl.git