revised titles of rack guide

railties/guides/source/rails_on_rack.textile

@@ -30,7 +30,7 @@ h4. Rails Application's Rack Object
 
 <tt>ActionController::Dispatcher.new</tt> is the primary Rack application object of a Rails application. Any Rack compliant web server should be using +ActionController::Dispatcher.new+ object to serve a Rails application.</p>
 
-h4. script/server
+h4. +script/server+
 
 <tt>script/server</tt> does the basic job of creating a +Rack::Builder+ object and starting the webserver. This is Rails' equivalent of Rack's +rackup+ script.
 
@@ -55,7 +55,7 @@ Middlewares used in the code above are primarily useful only in the development
 |Rails::Rack::Static|Serves static files inside +RAILS_ROOT/public+ directory|
 |Rails::Rack::Debugger|Starts Debugger|
 
-h4. rackup
+h4. +rackup+
 
 To use +rackup+ instead of Rails' +script/server+, you can put the following inside +config.ru+ of your Rails application's root directory:
 
@@ -151,7 +151,7 @@ You can swap an existing middleware in the middleware stack using +config.middle
 config.middleware.swap ActionController::Failsafe, Lifo::Failsafe
 </ruby>
 
-h5. Middleware stack is an array
+h5. Middleware Stack is an Array
 
 The middleware stack behaves just like a normal +Array+. You can use any +Array+ methods to insert, reorder, or remove items from the stack. Methods described in the section above are just convenience methods.