[Catalyst-commits] r14479 - trunk/examples/CatalystAdvent/root/2013

[jnapiorkowski at dev.catalyst.perl.org]

Author: jnapiorkowski
Date: 2013-12-06 20:30:39 +0000 (Fri, 06 Dec 2013)
New Revision: 14479

Modified:
   trunk/examples/CatalystAdvent/root/2013/6.pod
Log:
typo fixes

Modified: trunk/examples/CatalystAdvent/root/2013/6.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2013/6.pod	2013-12-06 16:22:38 UTC (rev 14478)
+++ trunk/examples/CatalystAdvent/root/2013/6.pod	2013-12-06 20:30:39 UTC (rev 14479)
@@ -73,8 +73,8 @@
 is expected to be very large!
 
 Your hashref under C<data_handlers> can include as many types as you deem
-required, and you can override the build in JSON parsing since we apply
-you customizations ontop of the defaults.
+required, and you can override the built in JSON parsing since we apply
+your customizations ontop of the defaults.
 
 So, how do you access this new parsed content?  We've added a new attribute
 to L<Catalyst::Request> called C<body_data>.  This attribute is lazy, so
@@ -83,7 +83,7 @@
 JSON decoding stuff, and/or are using L<Catalyst::Action::REST> you can
 keep on doing that without any impact at all on your request overhead.
 
-Here's how this could look in you controller.  Lets assume the incoming is
+Here's how this could look in your controller.  Lets assume the incoming is
 C<application/json> like "{'name':'Jason','age':'25'}":
 
     sub update_user : POST Path(/User) Consumes(JSON) {