<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -1,10 +1,25 @@
 = scoped_search
 
-This simple plugin will make it easy to search your ActiveRecord models. Searching is performed using a query string, which should be passed to the named_scope *search_for* that uses SQL %LIKE% conditions for searching (ILIKE for Postgres). You can specify what fields should be used for searching.
+The &lt;b&gt;scoped_search&lt;/b&gt; Rails plugin makes it easy to search your ActiveRecord models. Searching is 
+performed using a query string, which should be passed to the named_scope *search_for* that uses SQL 
+&lt;tt&gt;LIKE %keyword%&lt;/tt&gt; conditions for searching (ILIKE for Postgres). You can specify what fields 
+should be used for searching.
 
 == Installing
 
-	gem install wvanbergen-scoped_search -s http://gems.github.com
+The recommended method to enable scoped_search in your project is adding the scoped_search gem to your environment. Add the following code to your Rails configuration in &lt;tt&gt;config/environment.rb&lt;/tt&gt;:
+
+  Rails::Initializer.run do |config|
+    ...
+    config.gem 'wvanbergen-scoped_search', :lib =&gt; 'scoped_search', 
+                   source =&gt; 'http://gems.github.com/'
+  end
+
+Run &lt;tt&gt;sudo rake gems:install&lt;/tt&gt; to install the gem.
+
+Another alternative is to install scoped_search as a Rails plugin:
+
+  script/plugin install git://github.com/wvanbergen/scoped_search.git
 
 == Usage
 
@@ -29,16 +44,15 @@ You can also search on associate models.  This works with &lt;b&gt;belongs_to&lt;/b&gt;, &lt;b&gt;
     searchable_on :first_name, :last_name, :notes_title, :notes_content
   end
 
-
 The search query language is simple. It supports these constructs:
-* &lt;b&gt;words:&lt;/b&gt; some search keywords
-* &lt;b&gt;phrases:&lt;/b&gt; &quot;a single search phrase&quot;
-* &lt;b&gt;negation:&lt;/b&gt; &quot;look for this&quot; -&quot;but do not look for this phrase and this&quot; -word
-* &lt;b&gt;OR words/phrases:&lt;/b&gt; word/phrase OR word/phrase.  Example: &quot;Hello World&quot; OR &quot;Hello Moon&quot;
+* &lt;b&gt;words:&lt;/b&gt; &lt;tt&gt;some search keywords&lt;/tt&gt;
+* &lt;b&gt;phrases:&lt;/b&gt; &lt;tt&gt;&quot;a single search phrase&quot;&lt;/tt&gt;
+* &lt;b&gt;negation:&lt;/b&gt; &lt;tt&gt;&quot;look for this&quot; -&quot;but do not look for this phrase and this&quot; -word&lt;/tt&gt;
+* &lt;b&gt;OR words/phrases:&lt;/b&gt; word/phrase OR word/phrase.  Example: &lt;tt&gt;&quot;Hello World&quot; OR &quot;Hello Moon&quot;&lt;/tt&gt;
 * &lt;b&gt;dates:&lt;/b&gt; mm/dd/yyyy, dd/mm/yyyy, yyyy/mm/dd, yyyy-mm-dd
-* &lt;b&gt;date ranges:&lt;/b&gt; &gt; date, &gt;= date, &lt; date, &lt;= date, date TO date.  Examples: &gt; mm/dd/yyyy, &lt; yyyy-mm-dd
+* &lt;b&gt;date ranges:&lt;/b&gt; &gt; date, &gt;= date, &lt; date, &lt;= date, date TO date.  Examples: &lt;tt&gt;&gt; 30/05/1983&lt;/tt&gt;, &lt;tt&gt;&lt; 2009-01-30&lt;/tt&gt;
 
-This functionality is build on named_scope. The searchable_on statement creates 
+This functionality is build on &lt;tt&gt;named_scope&lt;/tt&gt;. The searchable_on statement creates 
 a named_scope *search_for*. Because of this, you can actually chain the call with
 other scopes. For example, this can be very useful if you only want to search in 
 projects that are accessible by a given user.</diff>
      <filename>README.rdoc</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>f6aa4e4add254a08a7eacccaad1ce33cb41e8fdc</id>
    </parent>
  </parents>
  <author>
    <name>Willem van Bergen</name>
    <email>willem@vanbergen.org</email>
  </author>
  <url>http://github.com/wvanbergen/scoped_search/commit/515511aa74460dfa10f862c6f001d5cccee2db6a</url>
  <id>515511aa74460dfa10f862c6f001d5cccee2db6a</id>
  <committed-date>2009-01-29T23:00:23-08:00</committed-date>
  <authored-date>2009-01-29T23:00:23-08:00</authored-date>
  <message>README adjustments</message>
  <tree>c9ee92531fadabc20ff46768f988b0038a024841</tree>
  <committer>
    <name>Willem van Bergen</name>
    <email>willem@vanbergen.org</email>
  </committer>
</commit>
