Minor typos: 'built-in' instead of 'built in', 'built into' instead of 'built in to'

activesupport/lib/active_support/core_ext/logger.rb

@@ -18,7 +18,7 @@ def around_#{level}(before_message, after_message, &block)  # def around_debug(b
 
 require 'logger'
 
-# Extensions to the built in Ruby logger.
+# Extensions to the built-in Ruby logger.
 #
 # If you want to use the default log formatter as defined in the Ruby core, then you
 # will need to set the formatter for the logger as in:

railties/guides/source/index.html.erb

@@ -68,7 +68,7 @@ Ruby on Rails Guides
 <% end %>
 
 <%= guide("Action View Form Helpers", 'form_helpers.html', :ticket => 1) do %>
-  <p>Guide to using built in Form helpers.</p>
+  <p>Guide to using built-in Form helpers.</p>
 <% end %>
 </dl>
 

railties/guides/source/layouts_and_rendering.textile

@@ -2,7 +2,7 @@ h2. Layouts and Rendering in Rails
 
 This guide covers the basic layout features of Action Controller and Action View. By referring to this guide, you will be able to:
 
-* Use the various rendering methods built in to Rails
+* Use the various rendering methods built into Rails
 * Create layouts with multiple content sections
 * Use partials to DRY up your views
 * Use nested layouts (sub-templates)

railties/guides/source/plugins.textile

@@ -1284,7 +1284,7 @@ class YaffleMigrationGenerator < Rails::Generator::NamedBase
 end
 </ruby>
 
-The generator creates a new file in 'db/migrate' with a timestamp and an 'add_column' statement.  It reuses the built in rails +migration_template+ method, and reuses the built-in rails migration template.
+The generator creates a new file in 'db/migrate' with a timestamp and an 'add_column' statement.  It reuses the built-in rails +migration_template+ method, and reuses the built-in rails migration template.
 
 It's courteous to check to see if table names are being pluralized whenever you create a generator that needs to be aware of table names.  This way people using your generator won't have to manually change the generated files if they've turned pluralization off.
 

railties/guides/source/security.textile

@@ -670,7 +670,7 @@ Also, the second query renames some columns with the AS statement so that the we
 
 h5(#sql-injection-countermeasures). Countermeasures
 
-Ruby on Rails has a built in filter for special SQL characters, which will escape ' , " , NULL character and line breaks. <em class="highlight">Using +Model.find(id)+ or +Model.find_by_some thing(something)+ automatically applies this countermeasure</em>. But in SQL fragments, especially <em class="highlight">in conditions fragments (+:conditions => "..."+), the +connection.execute()+ or +Model.find_by_sql()+ methods, it has to be applied manually</em>.
+Ruby on Rails has a built-in filter for special SQL characters, which will escape ' , " , NULL character and line breaks. <em class="highlight">Using +Model.find(id)+ or +Model.find_by_some thing(something)+ automatically applies this countermeasure</em>. But in SQL fragments, especially <em class="highlight">in conditions fragments (+:conditions => "..."+), the +connection.execute()+ or +Model.find_by_sql()+ methods, it has to be applied manually</em>.
 
 Instead of passing a string to the conditions option, you can pass an array to sanitize tainted strings like this: