From b51201242aaf77c6db5a9b2f72e433c521df79c5 Mon Sep 17 00:00:00 2001
From: Vijay Dev <vijaydev.cse@gmail.com>
Date: Sat, 4 Aug 2012 14:30:21 +0530
Subject: copy edits [ci skip]

---
 guides/source/contributing_to_ruby_on_rails.textile | 6 ------
 1 file changed, 6 deletions(-)

(limited to 'guides/source/contributing_to_ruby_on_rails.textile')

diff --git a/guides/source/contributing_to_ruby_on_rails.textile b/guides/source/contributing_to_ruby_on_rails.textile
index 9ae627c237..dd43ef795f 100644
--- a/guides/source/contributing_to_ruby_on_rails.textile
+++ b/guides/source/contributing_to_ruby_on_rails.textile
@@ -184,10 +184,6 @@ We need first to delete +.bundle/config+ because Bundler remembers in that file
 
 In order to be able to run the test suite against MySQL you need to create a user named +rails+ with privileges on the test databases:
 
-<shell>
-mysql -u root mysql -p
-</shell>
-
 <shell>
 mysql> GRANT ALL PRIVILEGES ON activerecord_unittest.*
        to 'rails'@'localhost';
@@ -202,8 +198,6 @@ $ cd activerecord
 $ bundle exec rake mysql:build_databases
 </shell>
 
-NOTE: If you get an error like "Access denied for user 'rails'@'localhost' (using password: YES)" then you most likely have a rails user in the mysql database, that uses a password, or you have a password specified in the my.cnf file of mysql.
-
 PostgreSQL's authentication works differently. A simple way to set up the development environment for example is to run with your development account
 
 <shell>
-- 
cgit v1.2.3

