diff options
| author | Rex Feng <rexfeng@gmail.com> | 2014-01-16 18:52:44 -0500 |
|---|---|---|
| committer | Rex Feng <rexfeng@gmail.com> | 2014-01-16 18:57:21 -0500 |
| commit | beeb8969e0ec623b5221d5b8aa6713d9139c4545 (patch) | |
| tree | 212291d8f53f92009f1588d483fa138547374705 /guides/source | |
| parent | bcd6def32b0970b33a49c721ea247c8360bf8344 (diff) | |
| download | rails-beeb8969e0ec623b5221d5b8aa6713d9139c4545.tar.gz rails-beeb8969e0ec623b5221d5b8aa6713d9139c4545.tar.bz2 rails-beeb8969e0ec623b5221d5b8aa6713d9139c4545.zip | |
clean up security guide: his => their [ci skip]
Diffstat (limited to 'guides/source')
| -rw-r--r-- | guides/source/security.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/security.md b/guides/source/security.md index c367604d6f..cffe7c85f1 100644 --- a/guides/source/security.md +++ b/guides/source/security.md @@ -81,7 +81,7 @@ Here are some general guidelines on sessions. * _Do not store large objects in a session_. Instead you should store them in the database and save their id in the session. This will eliminate synchronization headaches and it won't fill up your session storage space (depending on what session storage you chose, see below). This will also be a good idea, if you modify the structure of an object and old versions of it are still in some user's cookies. With server-side session storages you can clear out the sessions, but with client-side storages, this is hard to mitigate. -* _Critical data should not be stored in session_. If the user clears his cookies or closes the browser, they will be lost. And with a client-side session storage, the user can read the data. +* _Critical data should not be stored in session_. If the user clears their cookies or closes the browser, they will be lost. And with a client-side session storage, the user can read the data. ### Session Storage |