aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLeandro Santos <lsantos@thescore.com>2011-11-30 14:29:17 -0500
committerLeandro Santos <lsantos@thescore.com>2011-11-30 14:29:17 -0500
commitfca655f391953a1ba02988cb8e74913d4efbcd3a (patch)
tree1ae707ccaa7e303309a1ca3ec772e2faf817bbe3
parent88daf082581bcec5fcdbb92d1fd784188e4d99bd (diff)
downloadrails-fca655f391953a1ba02988cb8e74913d4efbcd3a.tar.gz
rails-fca655f391953a1ba02988cb8e74913d4efbcd3a.tar.bz2
rails-fca655f391953a1ba02988cb8e74913d4efbcd3a.zip
typo in the performance testing rails guide
-rw-r--r--railties/guides/source/performance_testing.textile2
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/performance_testing.textile b/railties/guides/source/performance_testing.textile
index 2440927542..958b13cd9e 100644
--- a/railties/guides/source/performance_testing.textile
+++ b/railties/guides/source/performance_testing.textile
@@ -151,7 +151,7 @@ Performance tests can be run in two modes: Benchmarking and Profiling.
h5. Benchmarking
-Benchmarking makes it easy to quickly gather a few metrics about each test tun. By default, each test case is run *4 times* in benchmarking mode.
+Benchmarking makes it easy to quickly gather a few metrics about each test run. By default, each test case is run *4 times* in benchmarking mode.
To run performance tests in benchmarking mode: