Skip to content
Browse files

Use genderless pronouns in API docs

  • Loading branch information...
1 parent 5fb67eb commit f84dbd59301ea4277e6ff83d7244a061e4d646b1 @guilleiguaran guilleiguaran committed Dec 1, 2013
View
2 actionpack/lib/action_controller/base.rb
@@ -85,7 +85,7 @@ module ActionController
# or you can remove the entire session with +reset_session+.
#
# Sessions are stored by default in a browser cookie that's cryptographically signed, but unencrypted.
- # This prevents the user from tampering with the session but also allows him to see its contents.
+ # This prevents the user from tampering with the session but also allows them to see its contents.
#
# Do not put secret information in cookie-based sessions!
#
View
2 activerecord/lib/active_record/validations/uniqueness.rb
@@ -209,7 +209,7 @@ module ClassMethods
# exception. You can either choose to let this error propagate (which
# will result in the default Rails exception page being shown), or you
# can catch it and restart the transaction (e.g. by telling the user
- # that the title already exists, and asking him to re-enter the title).
+ # that the title already exists, and asking them to re-enter the title).
# This technique is also known as
# {optimistic concurrency control}[http://en.wikipedia.org/wiki/Optimistic_concurrency_control].
#

3 comments on commit f84dbd5

@etehtsea

🔥

@shtirlic

@etehtsea 💊 🙆

@why-el
why-el commented on f84dbd5 Dec 6, 2013

A better solution in my opinion is to package these changes in a branch and apply them doc-wide. There is no point in keeping inconsistent gender usage because that could be confusing.

Please sign in to comment.
Something went wrong with that request. Please try again.