bold does not look as good in documentation

mojolicious · Mar 14, 2014 · 2a96b93 · 2a96b93
1 parent 4e09068
commit 2a96b93
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 11 deletions.
diff --git a/lib/Mojolicious/Guides/FAQ.pod b/lib/Mojolicious/Guides/FAQ.pod
@@ -16,7 +16,7 @@ L<Mojolicious>.
 
 The short answer is "it doesn't", because we interpret the words
 "web framework" much more literally than others. With the emergence of the
-B<real-time web> and new technologies such as B<WebSockets>, we are facing new
+real-time web and new technologies such as 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 HTTP
 client/server stack called L<Mojo>, which was heavily inspired by the original
@@ -71,13 +71,13 @@ optimize for it, this is currently 5.10.1.
 
 =head2 What is the difference between blocking and non-blocking operations?
 
-A B<blocking> operation is a subroutine that blocks the execution of the
+A C<blocking> operation is a subroutine that blocks the execution of the
 calling subroutine until the subroutine is finished.
 
   my $result = blocking_subroutine();
   ...
 
-A B<non-blocking> operation on the other hand lets the calling subroutine
+A C<non-blocking> operation on the other hand lets the calling subroutine
 continue execution even though the subroutine is not yet finished. Instead of
 waiting, the calling subroutine passes along a callback to be executed once
 the subroutine is finished, this is called continuation-passing style.

diff --git a/lib/Mojolicious/Guides/Growing.pod b/lib/Mojolicious/Guides/Growing.pod
@@ -26,7 +26,7 @@ presentation and input.
            +------------+    +-------+    +------+
 
 A slightly modified version of the pattern moving some application logic into
-the B<controller> is the foundation of pretty much every web framework these
+the I<controller> is the foundation of pretty much every web framework these
 days, including L<Mojolicious>.
 
               +----------------+     +-------+
@@ -37,9 +37,9 @@ days, including L<Mojolicious>.
   Response <- |                | <-> | View  |
               +----------------+     +-------+
 
-The B<controller> receives a request from a user, passes incoming data to the
-B<model> and retrieves data from it, which then gets turned into an actual
-response by the B<view>. But note that this pattern is just a guideline that
+The I<controller> receives a request from a user, passes incoming data to the
+I<model> and retrieves data from it, which then gets turned into an actual
+response by the I<view>. But note that this pattern is just a guideline that
 most of the time results in cleaner more maintainable code, not a rule that
 should be followed at all costs.
 
@@ -48,9 +48,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 HTTP these days. In REST terms, when you are opening a URL like
-B<http://mojolicio.us/foo> with your browser, you are basically asking the web
-server for the HTML B<representation> of the B<http://mojolicio.us/foo>
-B<resource>.
+C<http://mojolicio.us/foo> with your browser, you are basically asking the web
+server for the HTML I<representation> of the C<http://mojolicio.us/foo>
+I<resource>.
 
   +--------+                                +--------+
   |        | -> http://mojolicio.us/foo  -> |        |
@@ -80,7 +80,7 @@ all session state is kept client-side.
   +---------+                        +------------+
 
 While HTTP methods such as PUT, GET and DELETE are not directly part of REST
-they go very well with it and are commonly used to manipulate B<resources>.
+they go very well with it and are commonly used to manipulate I<resources>.
 
 =head2 Sessions