minor FAQ tweaks

mojolicious · Feb 9, 2012 · ee6d13d · ee6d13d
1 parent 49ee04e
commit ee6d13d
Show file tree

Hide file tree

Showing 4 changed files with 13 additions and 10 deletions.
diff --git a/Changes b/Changes
@@ -1,5 +1,8 @@
 This file documents the revision history for Perl extension Mojolicious.
 
+2.49    2012-02-09 00:00:00
+        - Improved documentation.
+
 2.48    2012-02-09 00:00:00
         - Improved documentation.
         - Improved tests.

diff --git a/lib/Mojolicious.pm b/lib/Mojolicious.pm
@@ -32,7 +32,7 @@ has static   => sub { Mojolicious::Static->new };
 has types    => sub { Mojolicious::Types->new };
 
 our $CODENAME = 'Leaf Fluttering In Wind';
-our $VERSION  = '2.48';
+our $VERSION  = '2.49';
 
 # "These old doomsday devices are dangerously unstable.
 #  I'll rest easier not knowing where they are."

diff --git a/lib/Mojolicious/Guides/FAQ.pod b/lib/Mojolicious/Guides/FAQ.pod
@@ -14,9 +14,9 @@ L<Mojolicious> together with the right answers.
 
 The short answer is "it doesn't", because we interpret the words
 "web framework" much more literally than others. With the emergence of the
-C<Real-time Web> and new technologies such as C<WebSockets>, we are facing
+C<real-time web> and new technologies such as C<WebSockets>, we are facing
 new challenges that go way beyond what commonly used modules like L<LWP> were
-designed for. Because of this, L<Mojolicious> contains a whole new C<HTTP>
+designed for. Because of this, L<Mojolicious> contains a whole new HTTP
 client/server stack called L<Mojo>, which was heavily inspired by the
 original C<LWPng> effort and carefully designed with these new requirements
 in mind. So while some of the higher abstraction layers might look similar to
@@ -39,8 +39,8 @@ they are installed.
 Because we can make them rounder. Components specifically designed for
 user-friendliness and development speed are not easy to come by. We are
 strong believers of the Perl mantra "There is more than one way to do it.",
-and our quest is to develop the best possible solutions with these two
-criteria in mind.
+and our quest is to develop the best possible solutions for these two
+criteria.
 
 =head2 What about backwards compatibility?
 
@@ -104,7 +104,7 @@ response.
 =head2 I think i have found a bug, what should i do now?
 
 First make sure you are using the latest version of L<Mojolicious>, it is
-quite likely that the bug has already been fixed. If that doesn't help
+quite likely that the bug has already been fixed. If that doesn't help,
 prepare a test case demonstrating the bug, you are not expected to fix it
 yourself, but you'll have to make sure the developers can replicate your
 problem. Sending in your whole application generally does more harm than
@@ -122,7 +122,7 @@ L<Mojolicious::Guides::CodingGuidelines>.
 
 =head2 Which namespace should i use for Mojolicious plugins?
 
-For all new plugins that you might want to release to CPAN we suggest using
+For all new plugins that you might want to release to CPAN, we suggest using
 the "Mojolicious::Plugin" namespace. While "MojoX" has been used a lot in the
 past, it is now deprecated.
 

diff --git a/lib/Mojolicious/Guides/Growing.pod b/lib/Mojolicious/Guides/Growing.pod
@@ -45,9 +45,9 @@ should be followed at all costs.
 
 REST is a software architectural style for distributed hypermedia systems
 such as the web. While it can be applied to many protocols it is most
-commonly used with C<HTTP> these days. In REST terms, when you are opening a
-URL like C<http://mojolicio.us/foo> with your browser, you are basically
-asking the web server for the HTML C<representation> of the
+commonly used with HTTP these days. In REST terms, when you are opening a URL
+like C<http://mojolicio.us/foo> with your browser, you are basically asking
+the web server for the HTML C<representation> of the
 C<http://mojolicio.us/foo> C<resource>.
 
   .--------.                                .--------.