aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSteve Klabnik <steve@steveklabnik.com>2013-09-09 08:22:21 -0700
committerSteve Klabnik <steve@steveklabnik.com>2013-09-09 08:22:21 -0700
commitff8fac614f04f9cc7bc4ce78f3b9a758814cd0ab (patch)
treed62153369999c00f49e192233bce7585bd90d4ef
parentad6e8a2fec552bf239cb1c059323d93a265c1b18 (diff)
parent84cea5a6d140fe1f855b925ceb8df4dd5a8ae557 (diff)
downloadrails-ff8fac614f04f9cc7bc4ce78f3b9a758814cd0ab.tar.gz
rails-ff8fac614f04f9cc7bc4ce78f3b9a758814cd0ab.tar.bz2
rails-ff8fac614f04f9cc7bc4ce78f3b9a758814cd0ab.zip
Merge pull request #12167 from hannesfostie/grammar-improvement
[ci skip] Improves a sentence in guides/security
-rw-r--r--guides/source/security.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/security.md b/guides/source/security.md
index 97b7355771..4aba39f55a 100644
--- a/guides/source/security.md
+++ b/guides/source/security.md
@@ -481,7 +481,7 @@ A good password is a long alphanumeric combination of mixed cases. As this is qu
INFO: _A common pitfall in Ruby's regular expressions is to match the string's beginning and end by ^ and $, instead of \A and \z._
-Ruby uses a slightly different approach than many other languages to match the end and the beginning of a string. That is why even many Ruby and Rails books make this wrong. So how is this a security threat? Say you wanted to loosely validate a URL field and you used a simple regular expression like this:
+Ruby uses a slightly different approach than many other languages to match the end and the beginning of a string. That is why even many Ruby and Rails books get this wrong. So how is this a security threat? Say you wanted to loosely validate a URL field and you used a simple regular expression like this:
```ruby
/^https?:\/\/[^\n]+$/i