From 88df7c09480786f912be5e2c88bab1f9f7131849 Mon Sep 17 00:00:00 2001 From: adamp01 <47503375+adamp01@users.noreply.github.com> Date: Mon, 14 Mar 2022 10:18:30 +0000 Subject: [PATCH] [WFX-350] Replace 'his or her' with 'their'. DO NOT modify license notices. --- docs/contributing/Code_Review_FAQ.rst | 2 +- media/libpng/png.h | 2 +- security/nss/lib/pki/nsspki.h | 2 +- toolkit/locales/en-US/toolkit/global/createProfileWizard.ftl | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/contributing/Code_Review_FAQ.rst b/docs/contributing/Code_Review_FAQ.rst index 18fe85a6e2da1..02e957161996f 100644 --- a/docs/contributing/Code_Review_FAQ.rst +++ b/docs/contributing/Code_Review_FAQ.rst @@ -42,7 +42,7 @@ What do reviewers look for? A review is focused on a patch's design, implementation, usefulness in fixing a stated problem, and fit within its module. A reviewer should be someone with domain expertise in the problem area. A reviewer may also -utilize other areas of his or her expertise and comment on other +utilize other areas of their expertise and comment on other possible improvements. There are no inherent limitations on what comments a reviewer might make about improving the code. diff --git a/media/libpng/png.h b/media/libpng/png.h index 6ea3698c20148..3e8628d94bc82 100644 --- a/media/libpng/png.h +++ b/media/libpng/png.h @@ -784,7 +784,7 @@ typedef png_row_info * png_row_infop; typedef png_row_info * * png_row_infopp; /* These are the function types for the I/O functions and for the functions - * that allow the user to override the default I/O functions with his or her + * that allow the user to override the default I/O functions with their * own. The png_error_ptr type should match that of user-supplied warning * and error functions, while the png_rw_ptr type should match that of the * user read/write data functions. Note that the 'write' function must not diff --git a/security/nss/lib/pki/nsspki.h b/security/nss/lib/pki/nsspki.h index 0ecec082608ee..3b32c07fd3b60 100644 --- a/security/nss/lib/pki/nsspki.h +++ b/security/nss/lib/pki/nsspki.h @@ -396,7 +396,7 @@ NSSCertificate_IsPrivateKeyAvailable( * Verify that if this certificate lives on a token, that the token * is still present and the certificate still exists. This is a * lightweight call which should be used whenever it should be - * verified that the user hasn't perhaps popped out his or her + * verified that the user hasn't perhaps popped out their * token and strolled away. */ diff --git a/toolkit/locales/en-US/toolkit/global/createProfileWizard.ftl b/toolkit/locales/en-US/toolkit/global/createProfileWizard.ftl index 9df6b44b87fb6..0a5ee400236a0 100644 --- a/toolkit/locales/en-US/toolkit/global/createProfileWizard.ftl +++ b/toolkit/locales/en-US/toolkit/global/createProfileWizard.ftl @@ -16,7 +16,7 @@ create-profile-first-page-header = profile-creation-explanation-1 = { -brand-short-name } stores information about your settings and preferences in your personal profile. -profile-creation-explanation-2 = If you are sharing this copy of { -brand-short-name } with other users, you can use profiles to keep each user’s information separate. To do this, each user should create his or her own profile. +profile-creation-explanation-2 = If you are sharing this copy of { -brand-short-name } with other users, you can use profiles to keep each user’s information separate. To do this, each user should create their own profile. profile-creation-explanation-3 = If you are the only person using this copy of { -brand-short-name }, you must have at least one profile. If you would like, you can create multiple profiles for yourself to store different sets of settings and preferences. For example, you may want to have separate profiles for business and personal use.