Changed gendered pronouns to be gender neutral

system/application/libraries/Auth/OpenID/Consumer.php

@@ -86,7 +86,7 @@
  * IMMEDIATE MODE
  *
  * In the flow described above, the user may need to confirm to the
- * lidentity server that it's ok to authorize his or her identity.
+ * lidentity server that it's ok to authorize their identity.
  * The server may draw pages asking for information from the user
  * before it redirects the browser back to the consumer's site.  This
  * is generally transparent to the consumer site, so it is typically
@@ -123,9 +123,9 @@
  * Next, the application should call the 'redirectURL' method of the
  * Auth_OpenID_AuthRequest object.  The 'return_to' URL parameter is
  * the URL that the OpenID server will send the user back to after
- * attempting to verify his or her identity.  The 'trust_root' is the
+ * attempting to verify their identity.  The 'trust_root' is the
  * URL (or URL pattern) that identifies your web site to the user when
- * he or she is authorizing it.  Send a redirect to the resulting URL
+ * they are authorizing it.  Send a redirect to the resulting URL
  * to the user's browser.
  *
  * That's the first half of the authentication process.  The second
@@ -1817,7 +1817,7 @@ function setAnonymous($is_anonymous)
      * request.
      *
      * @param string $realm The URL (or URL pattern) that identifies
-     * your web site to the user when she is authorizing it.
+     * your web site to the user when they are authorizing it.
      *
      * @param string $return_to The URL that the OpenID provider will
      * send the user back to after attempting to verify her identity.

system/application/libraries/Auth/OpenID/Server.php

@@ -22,8 +22,8 @@
  * that this user may claim the identity in question.  Exactly how you
  * do that is a matter of application policy, but it generally
  * involves making sure the user has an account with your system and
- * is logged in, checking to see if that identity is hers to claim,
- * and verifying with the user that she does consent to releasing that
+ * is logged in, checking to see if that identity is theirs to claim,
+ * and verifying with the user that they consent to releasing that
  * information to the party making the request.
  *
  * Examine the properties of the {@link Auth_OpenID_CheckIDRequest}

system/application/libraries/geshi/geshi.php

@@ -556,7 +556,7 @@ class GeSHi {
      *   The /e modifier inside <code>preg_replace()</code> allows code execution.
      *   Often it is the cause for remote code execution exploits. It is wise to
      *   deactivate this feature and test where in the application it is used.
-     *   The developer using the /e modifier should be made aware that he should
+     *   The developer using the /e modifier should be made aware that they should
      *   use <code>preg_replace_callback()</code> instead
      * </blockquote>
      *
@@ -4752,4 +4752,4 @@ function geshi_highlight($string, $language, $path = null, $return = false) {
     }
 }
 
-?>
+?>

system/libraries/Email.php

@@ -770,7 +770,7 @@ function clean_email($email)
 	 *
 	 * This function provides the raw message for use
 	 * in plain-text headers of HTML-formatted emails.
-	 * If the user hasn't specified his own alternative message
+	 * If the user hasn't specified their own alternative message
 	 * it creates one by stripping the HTML
 	 *
 	 * @access	private
@@ -2038,4 +2038,4 @@ function _mime_types($ext = "")
 // END CI_Email class
 
 /* End of file Email.php */
-/* Location: ./system/libraries/Email.php */
+/* Location: ./system/libraries/Email.php */