rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	Improve English	Ruafozy	2013-01-01	1	-5/+7
\| \| \| \| \| \|	* Fix one error * Improve wording * Improve punctuation
*	remove Mass Assignment reference from Form Helpers guide [ci skip]	Francesco Rodriguez	2012-12-10	1	-1/+1
\|
*	Remove references to Rails versions.	Steve Klabnik	2012-12-07	1	-2/+0
\| \| \| \| \| \| \| \|	There's no reason for guides to reference old behaviors. They should be current as of the versions of Rails that they ship with, and including older information just clutters thing. I discussed this change with @fxn and he agrees.
*	Fixed grammar in a lot of guide prologues.	Katie Oldaker	2012-12-07	1	-7/+7
\|
*	Normalize on 'After reading this guide, you will know:'	Steve Klabnik	2012-11-29	1	-1/+1
\| \| \| \| \|	We have three or four different introduction sentences to the guides. After this commit, we use the same one everywhere.
*	Fix title of 'form helpers' guide.	Steve Klabnik	2012-11-29	1	-2/+2
\| \| \| \| \| \|	They're Rails Guides, so obviously we're talking about Rails Form Helpers. Also, 'helpers' should be capitalized.
*	Add periods to the bullet points in guides.	Steve Klabnik	2012-11-29	1	-7/+7
\| \| \| \|	Talked with @fxn about this. Bullet points should have periods at the ends.
*	Switch to 1.9 hash syntax	Agis Anastasopoulos	2012-11-16	1	-30/+30
\| \| \|	I've intentionally left out some spots as they're the expected output, and since Hash#inspect yields `=>` I guess it may be confusing for beginners to see one syntax in the guide and a different one in their system.
*	use em-dashes instead of two minuses in guides	burningTyger	2012-11-10	1	-4/+4
\|
*	Add backticks around link_to example in javascript guide [ci skip]	Carlos Antonio da Silva	2012-10-28	1	-1/+1
\|
*	No more Textile guide generation support	Prem Sichanugrist	2012-09-17	1	-1/+1
\|
*	Fix the usage of `*` in Markdown	Prem Sichanugrist	2012-09-17	1	-7/+7
\| \| \| \| \|	In Textile `` would convert to `<strong>`, but in Markdown we have to use `*` instead.
*	Fix remaining formatting problems in the guide	Prem Sichanugrist	2012-09-17	1	-22/+22
\|
*	Convert all the links into Markdown format	Prem Sichanugrist	2012-09-17	1	-12/+12
\|
*	Convert all inline codes to Markdown syntax	Prem Sichanugrist	2012-09-17	1	-106/+106
\|
*	Convert inline code tags to Markdown	Prem Sichanugrist	2012-09-17	1	-3/+3
\|
*	Convert heading tags and heading section	Prem Sichanugrist	2012-09-17	1	-41/+51
\|
*	Convert code blocks into GFM style	Prem Sichanugrist	2012-09-17	1	-150/+150
\|
*	Rename the rest of the guides to Markdown	Prem Sichanugrist	2012-09-17	1	-0/+945