aboutsummaryrefslogtreecommitdiffstats
path: root/railties/guides
diff options
context:
space:
mode:
authorJosiah Ivey <josiah.ivey@gmail.com>2009-08-16 07:22:58 -0500
committerJosiah Ivey <josiah.ivey@gmail.com>2009-08-16 07:22:58 -0500
commit902c78dc268254ff7b10b13aee6caa2c2ab55b39 (patch)
tree93cc42d234599c45a2ef0520d5fe15e2a637fc99 /railties/guides
parentd572bf99ec784dc12f1a993904a0c99fbebd6886 (diff)
downloadrails-902c78dc268254ff7b10b13aee6caa2c2ab55b39.tar.gz
rails-902c78dc268254ff7b10b13aee6caa2c2ab55b39.tar.bz2
rails-902c78dc268254ff7b10b13aee6caa2c2ab55b39.zip
Fix typo in debugging guide
Diffstat (limited to 'railties/guides')
-rw-r--r--railties/guides/source/debugging_rails_applications.textile2
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/debugging_rails_applications.textile b/railties/guides/source/debugging_rails_applications.textile
index 9c0f22724e..94411a560e 100644
--- a/railties/guides/source/debugging_rails_applications.textile
+++ b/railties/guides/source/debugging_rails_applications.textile
@@ -330,7 +330,7 @@ h4. The Context
When you start debugging your application, you will be placed in different contexts as you go through the different parts of the stack.
-ruby-debug creates a content when a stopping point or an event is reached. The context has information about the suspended program which enables a debugger to inspect the frame stack, evaluate variables from the perspective of the debugged program, and contains information about the place where the debugged program is stopped.
+ruby-debug creates a context when a stopping point or an event is reached. The context has information about the suspended program which enables a debugger to inspect the frame stack, evaluate variables from the perspective of the debugged program, and contains information about the place where the debugged program is stopped.
At any time you can call the +backtrace+ command (or its alias +where+) to print the backtrace of the application. This can be very helpful to know how you got where you are. If you ever wondered about how you got somewhere in your code, then +backtrace+ will supply the answer.