aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKasper Timm Hansen <kaspth@gmail.com>2019-04-21 14:13:00 +0200
committerGitHub <noreply@github.com>2019-04-21 14:13:00 +0200
commitfaf2677c7a6f6c8c947e04505d075da9f761b04d (patch)
tree668128a61339f05a278fc29411c83c35b10a1a2c
parent80b7d58f34a965fc0269ab7e0efa86d39b86be56 (diff)
parentc8bc3c2943b86d26f10d66c97579ea6aa35bb897 (diff)
downloadrails-faf2677c7a6f6c8c947e04505d075da9f761b04d.tar.gz
rails-faf2677c7a6f6c8c947e04505d075da9f761b04d.tar.bz2
rails-faf2677c7a6f6c8c947e04505d075da9f761b04d.zip
Merge pull request #36048 from suretrust/master
Fix typo by changing 'for' to 'from'
-rw-r--r--guides/source/layouts_and_rendering.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/layouts_and_rendering.md b/guides/source/layouts_and_rendering.md
index 2808527141..39935cd2ef 100644
--- a/guides/source/layouts_and_rendering.md
+++ b/guides/source/layouts_and_rendering.md
@@ -689,7 +689,7 @@ Just like the `:status` option for `render`, `:status` for `redirect_to` accepts
#### The Difference Between `render` and `redirect_to`
-Sometimes inexperienced developers think of `redirect_to` as a sort of `goto` command, moving execution from one place to another in your Rails code. This is _not_ correct. Your code stops running and waits for a new request for the browser. It just happens that you've told the browser what request it should make next, by sending back an HTTP 302 status code.
+Sometimes inexperienced developers think of `redirect_to` as a sort of `goto` command, moving execution from one place to another in your Rails code. This is _not_ correct. Your code stops running and waits for a new request from the browser. It just happens that you've told the browser what request it should make next, by sending back an HTTP 302 status code.
Consider these actions to see the difference: