Remove whitespace from the readme

[ci skip]

Author: oestrich

README.md

@@ -23,12 +23,12 @@ Add rspec_api_documentation to your Gemfile
 Bundle it!
 
     $ bundle install
-    
+
 Set up specs.
 
     $ mkdir spec/acceptance
     $ vim spec/acceptance/orders_spec.rb
-    
+
 ```ruby
 require 'spec_helper'
 require 'rspec_api_documentation/dsl'
@@ -37,7 +37,7 @@ resource "Orders" do
   get "/orders" do
     example "Listing orders" do
       do_request
-      
+
       status.should == 200
     end
   end
@@ -59,7 +59,7 @@ Consider adding a viewer to enhance the generated documentation. By itself rspec
 #### Gemfile
 
     gem 'raddocs'
-    
+
 #### spec/spec_helper.rb
 
 ```ruby
@@ -79,24 +79,24 @@ See the `example` folder for a sample Rails app that has been documented.
 RspecApiDocumentation.configure do |config|
   # Set the application that Rack::Test uses
   config.app = Rails.application
-  
+
   # Output folder
   config.docs_dir = Rails.root.join("doc", "api")
-  
+
   # An array of output format(s).
   # Possible values are :json, :html, :combined_text, :combined_json,
   #   :json_iodocs, :textile, :markdown, :append_json
   config.format = [:html]
-  
+
   # Location of templates
   config.template_path = "inside of the gem"
-  
+
   # Filter by example document type
   config.filter = :all
-  
+
   # Filter by example document type
   config.exclusion_filter = nil
-  
+
   # Used when adding a cURL output to the docs
   config.curl_host = nil
 
@@ -114,24 +114,24 @@ RspecApiDocumentation.configure do |config|
   # By default examples and resources are ordered by description. Set to true keep
   # the source order.
   config.keep_source_order = false
-  
+
   # Change the name of the API on index pages
   config.api_name = "API Documentation"
-  
+
   # Redefine what method the DSL thinks is the client
   # This is useful if you need to `let` your own client, most likely a model.
   config.client_method = :client
 
   # Change the IODocs writer protocol
   config.io_docs_protocol = "http"
-  
+
   # You can define documentation groups as well. A group allows you generate multiple
   # sets of documentation.
   config.define_group :public do |config|
     # By default the group's doc_dir is a subfolder under the parent group, based
     # on the group's name.
     config.docs_dir = Rails.root.join("doc", "api", "public")
-    
+
     # Change the filter to only include :public examples
     config.filter = :public
   end
@@ -199,33 +199,33 @@ You tag examples with either a single symbol or an array of symbols.
 resource "Account" do
   get "/accounts" do
     parameter :page, "Page to view"
-    
+
     # default :document is :all
     example "Get a list of all accounts" do
       do_request
       status.should == 200
     end
-    
+
     # Don't actually document this example, purely for testing purposes
     example "Get a list on page 2", :document => false do
       do_request(:page => 2)
       status.should == 404
     end
-    
+
     # With example_request, you can't change the :document
     example_request "Get a list on page 3", :page => 3 do
       status.should == 404
     end
   end
-  
+
   post "/accounts" do
     parameter :email, "User email"
-    
+
     example "Creating an account", :document => :private do
       do_request(:email => "eric@example.com")
       status.should == 201
     end
-    
+
     example "Creating an account - errors", :document => [:private, :developers] do
       do_request
       status.should == 422
@@ -242,12 +242,12 @@ RspecApiDocumentation.configure do |config|
   config.define_group :non_private do |config|
     config.exclusion_filter = :private
   end
-  
+
   # Only document examples marked as 'public'
   config.define_group :public do |config|
     config.filter = :public
   end
-  
+
   # Only document examples marked as 'developer'
   config.define_group :developers do |config|
     config.filter = :developers
@@ -363,7 +363,7 @@ end
 
 #### parameter
 
-This method takes the parameter name, a description, and an optional hash of extra metadata that can be displayed in Raddocs as extra columns. If a method with the parameter name exists, e.g. a `let`, it will send the returned value up to the server as URL encoded data. 
+This method takes the parameter name, a description, and an optional hash of extra metadata that can be displayed in Raddocs as extra columns. If a method with the parameter name exists, e.g. a `let`, it will send the returned value up to the server as URL encoded data.
 
 Special values: