fixed FAQ links

mojolicious · Mar 26, 2012 · f77e184 · f77e184
1 parent e7cb50a
commit f77e184
Showing 1 changed file with 7 additions and 7 deletions.
diff --git a/lib/Mojolicious/Guides/FAQ.pod b/lib/Mojolicious/Guides/FAQ.pod
@@ -66,9 +66,9 @@ Probably not. While the L<Mojolicious> distribtion covers a wide range of
 features, we are rather conservative when it comes to adding new ones. The
 most important criteria are outlined in
 L<Mojolicious::Guides::CodingGuidelines>. But don't let this discourage you,
-it doesn't hurt to open a GitHub issue
-(L<https://github.com/kraih/mojo/issues>) and ask, just be prepared that it
-might not pass the vote.
+it doesn't hurt to open a
+L<GitHub issue|https://github.com/kraih/mojo/issues> and ask, just be
+prepared that it might not pass the vote.
 
 =head2 What does the error "Maximum message size exceeded." mean?
 
@@ -122,10 +122,10 @@ good, the C<t> directory of this distribution has many good examples for how
 to do it right. Writing a test is usually the hardest part of fixing a bug,
 so the better your test case the faster it can be fixed. ;)
 
-Once that's done you can contact the developers via via GitHub
-(L<https://github.com/kraih/mojo/issues>), mailing list
-(L<http://groups.google.com/group/mojolicious>) or IRC
-(C<#mojo> on C<irc.perl.org>).
+Once that's done you can contact the developers via via
+L<GitHub|https://github.com/kraih/mojo/issues>,
+L<mailing list|http://groups.google.com/group/mojolicious> or IRC (C<#mojo>
+on C<irc.perl.org>).
 
 If you decide to fix the bug yourself make sure to also take a look at
 L<Mojolicious::Guides::CodingGuidelines>.