Whitespace cleanup

Author: Janusz Mordarski

History.rdoc

@@ -14,7 +14,7 @@
 
 === 0.4.0 / 2011-08-15
 
-* Various fixes for Rails 3.1 compatibility. 
+* Various fixes for Rails 3.1 compatibility.
 * Now requires rgeo-activerecord 0.4.0.
 * INCOMPATIBLE CHANGE: simple queries (e.g. MyClass.where(:latlon => my_point)) use an objective rather than spatial equality test. Earlier versions transformed this form to use st_equals, but now if you need to test for spatial equality, you'll need to call st_equals explicitly. I'm still evaluating which direction we want to go with this in the future, but we may be stuck with the current behavior because the hack required to transform these queries to use spatial equality was egregious and broke in Rails 3.1 with no clear workaround.
 

README.rdoc

@@ -11,7 +11,7 @@ requires the mysql2 gem.
 
 === Spatial Migrations
 
-First, this adapter extends the migration syntax to support creating 
+First, this adapter extends the migration syntax to support creating
 spatial columns and indexes. To create a spatial column, use the
 <tt>:geometry</tt> type, or any of the OGC spatial types such as
 <tt>:point</tt> or <tt>:line_string</tt>. To create a spatial index, set
@@ -55,13 +55,13 @@ the "rgeo-activerecord" gem.
 Examples, given the spatial table defined above:
 
   class MySpatialTable < ActiveRecord::Base
-    
+
     # By default, use the GEOS implementation for spatial columns.
     self.rgeo_factory_generator = RGeo::Geos.method(:factory)
-    
+
     # But use a geographic implementation for the :latlon column.
     set_rgeo_factory_for_column(:latlon, RGeo::Geographic.spherical_factory)
-    
+
   end
 
 Now you can interact with the data using the RGeo types: