aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVipul A M <vipulnsward@gmail.com>2014-01-24 12:40:21 +0530
committerVipul A M <vipulnsward@gmail.com>2014-01-24 12:40:21 +0530
commit3e28b7c2bbd278381e9cf89086c0d3ac62a58f72 (patch)
tree1007406e45a651cd5c134a08f4cd0dcab00bfeb4
parent5b31da48813cb37ca162b3ea7c224018b96f3033 (diff)
downloadrails-3e28b7c2bbd278381e9cf89086c0d3ac62a58f72.tar.gz
rails-3e28b7c2bbd278381e9cf89086c0d3ac62a58f72.tar.bz2
rails-3e28b7c2bbd278381e9cf89086c0d3ac62a58f72.zip
`framwork` => `framework`
-rw-r--r--guides/source/testing.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/testing.md b/guides/source/testing.md
index 165eca739a..b5119829b3 100644
--- a/guides/source/testing.md
+++ b/guides/source/testing.md
@@ -361,7 +361,7 @@ NOTE: The execution of each test method stops as soon as any error or an asserti
When a test fails you are presented with the corresponding backtrace. By default
Rails filters that backtrace and will only print lines relevant to your
-application. This eliminates the framwork noise and helps to focus on your
+application. This eliminates the framework noise and helps to focus on your
code. However there are situations when you want to see the full
backtrace. simply set the `BACKTRACE` environment variable to enable this
behavior: