Merge pull request jsonwebtoken#133 from lloydwatkin/patch-1

Trivial change... be more inclusive :)

Author: woloski

views/md/introduction.md

@@ -12,7 +12,7 @@ There are some scenarios where JSON Web Tokens are useful:
 
 - **Authentication**: This is the typical scenario for using JWT, once the user is logged in, each subsequent request will include the JWT, allowing the user to access routes, services, and resources that are permitted with that token. Single Sign On is a feature that widely uses JWT nowadays, because of its small overhead and its ability to be easily used among systems of different domains.
 
-- **Information Exchange**: JSON Web Tokens are a good way of securely transmitting information between parties, because as they can be signed, for example using a public/private key pair, you can be sure that the sender is who he says he is. Additionally, as the signature is calculated using the header and the payload, you can also verify that the content hasn't changed.
+- **Information Exchange**: JSON Web Tokens are a good way of securely transmitting information between parties, because as they can be signed, for example using a public/private key pair, you can be sure that the sender is who they say they are. Additionally, as the signature is calculated using the header and the payload, you can also verify that the content hasn't changed.
 
 ## Which is the JSON Web Token structure?
 JSON Web Tokens consist of three parts separated by dots (`.`), which are: