diff options
| author | Saheed Oladele <31304943+suretrust@users.noreply.github.com> | 2019-04-21 08:07:42 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-04-21 08:07:42 +0100 |
| commit | c8bc3c2943b86d26f10d66c97579ea6aa35bb897 (patch) | |
| tree | 668128a61339f05a278fc29411c83c35b10a1a2c | |
| parent | 80b7d58f34a965fc0269ab7e0efa86d39b86be56 (diff) | |
| download | rails-c8bc3c2943b86d26f10d66c97579ea6aa35bb897.tar.gz rails-c8bc3c2943b86d26f10d66c97579ea6aa35bb897.tar.bz2 rails-c8bc3c2943b86d26f10d66c97579ea6aa35bb897.zip | |
Fix typo by changing 'for' to 'from'
| -rw-r--r-- | guides/source/layouts_and_rendering.md | 2 |
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: |