diff --git a/README.rdoc b/README.rdoc
index e352a55..de41c2b 100644
--- a/README.rdoc
+++ b/README.rdoc
@@ -6,14 +6,14 @@ A Scope & Engine based, clean, powerful, customizable and sophisticated paginato
 == Features
 
 * Clean
-Does not globally pollute Array, Hash, Object or AR::Base.
+Does not globally pollute +Array+, +Hash+, +Object+ or <tt>AR::Base</tt>.
 
 * Easy to use
 Just bundle the gem, then your models are ready to be paginated. No configuration required. Don't have to define anything in your models or helpers.
 
 * Simple scope-based API
 Everything is method chainable with less "Hasheritis". You know, that's the Rails 3 way.
-No special collection class or anything for the paginated values, instead using a general AR::Relation instance. So, of course you can chain any other conditions before or after the paginator scope.
+No special collection class or anything for the paginated values, instead using a general <tt>AR::Relation</tt> instance. So, of course you can chain any other conditions before or after the paginator scope.
 
 * Customizable engine-based I18n-aware helper
 As the whole pagination helper is basically just a collection of links and non-links, Kaminari renders each of them through its own partial template inside the Engine. So, you can easily modify their behaviour, style or whatever by overriding partial templates.
@@ -48,63 +48,63 @@ Then bundle:
 
 === Query Basics
 
-* the :page scope
-To fetch the 7th page of users (per_page = 25 by default)
+* the +:page+ scope
+To fetch the 7th page of users (default +per_page+ is 25)
   User.page(7)
 
-* the :per scope
-To show a lot more users per each page (change the per_page value)
+* the +:per+ scope
+To show a lot more users per each page (change the +per_page+ value)
   User.page(7).per(50)
-Note that the :per scope is not directly defined on the models but is just a method defined on the page scope. This is absolutely reasonable because you will never actually use "per_page" without specifying the "page" number.
+Note that the +:per+ scope is not directly defined on the models but is just a method defined on the page scope. This is absolutely reasonable because you will never actually use +per_page+ without specifying the +page+ number.
 
-=== Configuring default per_page value for each model
+=== Configuring default +per_page+ value for each model
 
-* paginates_per
-You can specify default per_page value per each model using the following declarative DSL.
+* +paginates_per+
+You can specify default +per_page+ value per each model using the following declarative DSL.
   class User < ActiveRecord::Base
     paginates_per 50
   end
 
 === Controllers
 
-* the page parameter is in params[:page]
+* the page parameter is in <tt>params[:page]</tt>
 Typically, your controller code will look like this:
   @users = User.order(:name).page params[:page]
 
 === Views
 
 * the same old helper method
-Just call the "paginate" helper:
+Just call the +paginate+ helper:
   <%= paginate @users %>
 
-This will render several "?page=N" pagination links surrounded by an HTML5 <nav> tag.
+This will render several <tt>?page=N</tt> pagination links surrounded by an HTML5 <+nav+> tag.
 
 === Helper Options
 
 * specifing the "inner window" size (4 by default)
-This would output something like ... 5 6 7 8 9 ... when 7 is the current page.
+This would output something like <tt>... 5 6 7 8 9 ...</tt> when 7 is the current page.
   <%= paginate @users, :window => 2 %>
 
 * specifing the "outer window" size (1 by default)
-This would output something like 1 2 3 4 ...(snip)... 17 18 19 20 while having 20 pages in total.
+This would output something like <tt>1 2 3 4 ...(snip)... 17 18 19 20</tt> while having 20 pages in total.
   <%= paginate @users, :outer_window => 3 %>
 
-* outer window can be separetely specified by "left", "right" (1 by default)
-This would output something like 1 ...(snip)... 18 19 20 while having 20 pages in total.
+* outer window can be separetely specified by +left+ +right+ (1 by default)
+This would output something like <tt>1 ...(snip)... 18 19 20</tt> while having 20 pages in total.
   <%= paginate @users, :left => 0, :right => 2 %>
 
-* extra parameters (:params) for the links
-This would modify each link's url_option. :controller and :action might be the keys in common.
+* extra parameters (+:params+) for the links
+This would modify each link's +url_option+. +:controller+ and +:action+ might be the keys in common.
   <%= paginate @users, :params => {:controller => 'foo', :action => 'bar'}
 
 * Ajax links (crazy simple, but works perfectly!)
-This would add data-remote="true" to all the links inside.
+This would add <tt>data-remote="true"</tt> to all the links inside.
   <%= paginate @users, :remote => true %>
 
 === I18n and labels
 
 The default labels for 'previous', '...' and 'next' are stored in the I18n yaml inside the engine, and rendered through I18n API. You can switch the label value per I18n.locale for your internationalized application.
-Keys and the default values are the following. You can override them by adding to a YAML file in your Rails.root/config/locales directory.
+Keys and the default values are the following. You can override them by adding to a YAML file in your <tt>Rails.root/config/locales</tt> directory.
 
   en:
     views:
@@ -121,10 +121,10 @@ Kaminari includes a handy template generator.
 Run the generator first,
   % rails g kaminari:views default
 
-then edit the partials in your app's app/views/kaminari/ directory.
+then edit the partials in your app's <tt>app/views/kaminari/</tt> directory.
 
 * for Haml users
-Haml templates generator is also available by adding "-e haml" option (this is automatically invoked when the default template_engine is set to Haml).
+Haml templates generator is also available by adding the <tt>-e haml</tt> option (this is automatically invoked when the default template_engine is set to Haml).
 
   % rails g kaminari:views default -e haml
 
@@ -132,7 +132,7 @@ Haml templates generator is also available by adding "-e haml" option (this is a
 The generator has the ability to fetch several sample template themes from the external repository (https://github.com/amatsuda/kaminari_themes) in addition to the bundled "default" one, which will help you creating a nice looking paginator.
   % rails g kaminari:views THEME
 
-To see the full list of avaliable themes, take a look at the themes repository, or just hit the generator without specifying THEME argument.
+To see the full list of avaliable themes, take a look at the themes repository, or just hit the generator without specifying +THEME+ argument.
   % rails g kaminari:views