Make some code gender neutral.

chrome/common/extensions/api/platform_keys.idl

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // Use the <code>chrome.platformKeys</code> API to access client certificates
 // managed by the platform. If the user or policy grants the permission, an
 // extension can use such a certficate in its custom authentication protocol.
 // E.g. this allows usage of platform managed certificates in third party VPNs
 // (see $(ref:vpnProvider chrome.vpnProvider)).
 namespace platformKeys {
@@ skipping 89 matching lines @@
   callback GetKeyPairCallback = void (object publicKey, 
                                       optional object privateKey);
 
   callback VerificationCallback = void (VerificationResult result);
 
   interface Functions {
     // This function filters from a list of client certificates the ones that
     // are known to the platform, match <code>request</code> and for which the
     // extension has permission to access the certificate and its private key.
     // If <code>interactive</code> is true, the user is presented a dialog where
-    // he can select from matching certificates and grant the extension access
+    // they can select from matching certificates and grant the extension access
     // to the certificate.
     // The selected/filtered client certificates will be passed to
     // <code>callback</code>.
     [nocompile] static void selectClientCertificates(
         SelectDetails details,
         SelectCallback callback);
 
     // Passes the key pair of <code>certificate</code> for usage with
     // $(ref:platformKeys.subtleCrypto) to <code>callback</code>.
     // |certificate|: The certificate of a $(ref:Match) returned by
@@ skipping 27 matching lines @@
     // specified and might change in the future.
     // The API implementation verifies certificate expiration, validates the
     // certification path and checks trust by a known CA.
     // The implementation is supposed to respect the EKU serverAuth and to
     // support subject alternative names.
     static void verifyTLSServerCertificate(VerificationDetails details,
                                            VerificationCallback callback);
   };
 };