From 7316cb84d410dfe5a27906e8cc8c05b829118ff7 Mon Sep 17 00:00:00 2001
From: Max Karolinskiy <41635752+mkarolin@users.noreply.github.com>
Date: Tue, 19 Nov 2024 20:00:50 -0500
Subject: [PATCH] Fixes aggressive replacements of person/people with
 profile(s) (uplift to 1.74.x). (#26644)

Merge pull request #26540 from brave/maxk-fix-person-people-replacements

Fixes aggressive replacements of person/people with profile(s).
---
 app/brave_strings.grd                         | 10 +++----
 app/generated_resources.grd                   |  6 ++--
 app/generated_resources_override.grd          |  6 ----
 app/nearby_share_strings.grdp                 |  6 ++--
 app/os_settings_strings.grdp                  |  4 +--
 app/os_settings_strings_override.grdp         |  6 ----
 app/settings_brave_strings.grdp               | 12 ++++----
 app/settings_brave_strings_override.grdp      |  4 ---
 app/settings_strings.grdp                     |  6 ++--
 app/settings_strings_override.grdp            |  9 ------
 .../strings/android_chrome_strings.grd        |  4 +--
 .../android_chrome_strings_override.grd       |  7 -----
 components/payments_strings.grdp              | 12 ++++----
 .../privacy_sandbox_chrome_strings.grdp       | 28 +++++++++----------
 .../security_interstitials_strings.grdp       |  2 +-
 components/supervised_user_strings.grdp       |  4 +--
 script/lib/l10n/grd_string_replacements.py    | 25 +++++++++++++++++
 17 files changed, 72 insertions(+), 79 deletions(-)

diff --git a/app/brave_strings.grd b/app/brave_strings.grd
index 851f2f7de566..1d87329a1c6c 100644
--- a/app/brave_strings.grd
+++ b/app/brave_strings.grd
@@ -2096,19 +2096,19 @@ Permissions you've already given to websites and apps may apply to this account.
       <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_1_HEADER" desc="TOPICS API A sub title that describes the first of 2 ways a site can get info from Brave in order to target ads to the user. Topics of interest include things like “Live comedy” and “Rock music”. Brave estimates these interests based on the sites users visit. * “Your”: we need to convey a sense of ownership, even if the user didn’t explicitly choose the interests we’re talking about. Without the “your”, it could sound like Brave is simply building a generic library of interests. * “estimated”: It’s an “estimation”, and we don’t want to suggest that we know with certainty the user’s interests. Avoid words like “guess”, “establish”, “define”, etc. (in place of “estimate”). * “by Brave”: This is new behavior for a browser (Brave) to take an active role in processing user data for the purposes of showing ads. It’s important to convey “Brave”, the actor in this case.">
         Your interests as estimated by Brave
       </message>
-      <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_1_BULLET_POINT_1" desc="TOPICS API Bullet 1 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “What data is used:” is bold and serves as a label to help profiles skimming the page. * “Your browsing history”: The user’s browsing history is available beneath the “History” menu at Brave’s top level. The Topics API estimates topics of interest based on sites in the user’s browsing history that are participating in the trials.">
+      <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_1_BULLET_POINT_1" desc="TOPICS API Bullet 1 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “What data is used:” is bold and serves as a label to help people skimming the page. * “Your browsing history”: The user’s browsing history is available beneath the “History” menu at Brave’s top level. The Topics API estimates topics of interest based on sites in the user’s browsing history that are participating in the trials.">
         <ph name="BEGIN_BOLD">&lt;b&gt;</ph>What data is used:<ph name="END_BOLD">&lt;/b&gt;</ph> Your browsing history, a record of sites you’ve visited using Brave on this device.
       </message>
-      <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_1_BULLET_POINT_2" desc="TOPICS API Bullet 2 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How we use this data:” is bold and serves as a label to help profiles skimming the page. * “estimate your interests”: Topics of interest include things like “Live comedy” and “Rock music”. Brave estimates these interests based on the sites users visit. It’s an “estimation”, and we don’t want to suggest that we know with certainty the user’s interests. Avoid words like “guess”, “establish”, “define”, etc. (in place of “estimate”).">
+      <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_1_BULLET_POINT_2" desc="TOPICS API Bullet 2 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How we use this data:” is bold and serves as a label to help people skimming the page. * “estimate your interests”: Topics of interest include things like “Live comedy” and “Rock music”. Brave estimates these interests based on the sites users visit. It’s an “estimation”, and we don’t want to suggest that we know with certainty the user’s interests. Avoid words like “guess”, “establish”, “define”, etc. (in place of “estimate”).">
         <ph name="BEGIN_BOLD">&lt;b&gt;</ph>How we use this data:<ph name="END_BOLD">&lt;/b&gt;</ph> Brave can estimate your interests. Later, a site you visit can ask Brave to see your interests in order to personalize the ads you see.
       </message>
-      <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_1_BULLET_POINT_3" desc="TOPICS API Bullet 3 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How you can manage your data:” is bold and serves as a label to help profiles skimming the page. * “To protect your privacy”: Today, most data is kept for long periods of time. This new Topics API doesn’t retain estimated topics for more than 3 weeks. The only reason for this feature is to protect the user’s privacy. * “auto”: isn’t strictly necessary, but it conveys that this feature is an ongoing part of the service. This isn’t describing, for example, a one-time deletion. * “older than 3 weeks”: We’re trying to convey a rolling delete. Imagine a user opens a browser for the very first time. As the user browses, Brave will estimate up to 5 topics of interest in the first week. In the second week, Brave will estimate up to 5 additional topics of interest. The same for the third week, for a total of 15 potential interests. In week 4, Brave will automatically delete the 5 interests from week 1 so that there aren’t ever more than 15 topics associated with a user at any given time. * “interests can refresh”: If a user loves horror films and reads about them for months on end, the interest “Horror movies” might get deleted and refreshed in the same week, so that “Horror movies” doesn’t ever disappear from the user’s list of interests. * “Or you can…”: A user might love horror movies but can’t stand the idea of seeing ads about horror movies (because even the visuals will ruin the surprise of opening night). In this case, the user can remove “Horror movies” from the list of interests Brave will consider. This removal remains in place indefinitely. Note that the user might still see ads about Horror movies from different ad networks or by other means than Brave’s “Browser-based ad personalization” setting.">
+      <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_1_BULLET_POINT_3" desc="TOPICS API Bullet 3 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How you can manage your data:” is bold and serves as a label to help people skimming the page. * “To protect your privacy”: Today, most data is kept for long periods of time. This new Topics API doesn’t retain estimated topics for more than 3 weeks. The only reason for this feature is to protect the user’s privacy. * “auto”: isn’t strictly necessary, but it conveys that this feature is an ongoing part of the service. This isn’t describing, for example, a one-time deletion. * “older than 3 weeks”: We’re trying to convey a rolling delete. Imagine a user opens a browser for the very first time. As the user browses, Brave will estimate up to 5 topics of interest in the first week. In the second week, Brave will estimate up to 5 additional topics of interest. The same for the third week, for a total of 15 potential interests. In week 4, Brave will automatically delete the 5 interests from week 1 so that there aren’t ever more than 15 topics associated with a user at any given time. * “interests can refresh”: If a user loves horror films and reads about them for months on end, the interest “Horror movies” might get deleted and refreshed in the same week, so that “Horror movies” doesn’t ever disappear from the user’s list of interests. * “Or you can…”: A user might love horror movies but can’t stand the idea of seeing ads about horror movies (because even the visuals will ruin the surprise of opening night). In this case, the user can remove “Horror movies” from the list of interests Brave will consider. This removal remains in place indefinitely. Note that the user might still see ads about Horror movies from different ad networks or by other means than Brave’s “Browser-based ad personalization” setting.">
         <ph name="BEGIN_BOLD">&lt;b&gt;</ph>How you can manage your data:<ph name="END_BOLD">&lt;/b&gt;</ph> To protect your privacy, we auto-delete your interests that are older than 4 weeks. As you keep browsing, an interest might appear on the list again. Or you can remove interests you don’t want Brave to consider.
       </message>
-      <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_2_BULLET_POINT_1" desc="FLEDGE APIBullet 1 of 3 that appear beneath the “Sites you visit that define your interests” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “What data is used:” is bold and serves as a label to help profiles skimming the page. * “Your browsing history”: The user’s browsing history is available beneath the “History” menu at Brave’s top level. This content taken in isolation is somewhat misleading. With FLEDGE, a site can store information in Brave about the user’s visit to their site. For example, the site might store “running_shoes_red_size_35” to indicate that the user showed interest in a particular shoe. We’re OK with the simplification in this bullet because 1) we explain it in the next bullet and 2) we want the user to understand that at the top level, both Topics &amp; Fledge are based on the same thing and that is the user’s browsing history.">
+      <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_2_BULLET_POINT_1" desc="FLEDGE APIBullet 1 of 3 that appear beneath the “Sites you visit that define your interests” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “What data is used:” is bold and serves as a label to help people skimming the page. * “Your browsing history”: The user’s browsing history is available beneath the “History” menu at Brave’s top level. This content taken in isolation is somewhat misleading. With FLEDGE, a site can store information in Brave about the user’s visit to their site. For example, the site might store “running_shoes_red_size_35” to indicate that the user showed interest in a particular shoe. We’re OK with the simplification in this bullet because 1) we explain it in the next bullet and 2) we want the user to understand that at the top level, both Topics &amp; Fledge are based on the same thing and that is the user’s browsing history.">
         <ph name="BEGIN_BOLD">&lt;b&gt;</ph>What data is used:<ph name="END_BOLD">&lt;/b&gt;</ph> Your browsing history, a record of sites you’ve visited using Brave on this device.
       </message>
-      <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_2_BULLET_POINT_2" desc="FLEDGE API Bullet 2 of 3 that appear beneath the “Sites you visit that define your interests” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How we use this data:” is bold and serves as a label to help profiles skimming the page.">
+      <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_2_BULLET_POINT_2" desc="FLEDGE API Bullet 2 of 3 that appear beneath the “Sites you visit that define your interests” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How we use this data:” is bold and serves as a label to help people skimming the page.">
         <ph name="BEGIN_BOLD">&lt;b&gt;</ph>How we use this data:<ph name="END_BOLD">&lt;/b&gt;</ph> Sites can store information with Brave about your interests. For example, if you visit a site to buy shoes for a marathon, the site might define your interest as running marathons. Later, if you visit a different site to register for a race, that site can show you an ad for running shoes based on your interests.
       </message>
       <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_BOTTOM_SUMMARY" desc="A conclusion paragraph for the entire page. It sits beneath the “More control over the ads you see” subtitle but it’s no more associated with that topic than “Limit sharing between sites”. * “You can change your mind”: When writing a consent moment, we have a legal obligation to inform the user how they can “revoke their consent” or “opt out”. A friendlier way to say this is “change your mind”. * “in Brave settings”: The URL is chrome://settings/privacySandbox. We don’t make it a live link because we need the users to stay in this moment until they make a choice. * “The trials run alongside…”: The trials happen in addition to today’s current system based on third-party cookies. In other words, even by accepting in this consent moment, the user’s core experience doesn’t change much. This is an experiment, and we need the user to understand as much. ">
diff --git a/app/generated_resources.grd b/app/generated_resources.grd
index 03db76d2cc68..a00d1aa47adb 100644
--- a/app/generated_resources.grd
+++ b/app/generated_resources.grd
@@ -3730,10 +3730,10 @@ are declared in tools/grit/grit_rule.gni.
         You usually block notifications. To let this site notify you, click here.
       </message>
       <message name="IDS_NOTIFICATIONS_QUIET_PERMISSION_BUBBLE_CROWD_DENY_DESCRIPTION" desc="Subtitle for the Notifications permission prompt, shown when a user clicks on a site's notifications permission request that is automatically blocked by Brave, as this permission prompt is often denied by other users for this site.">
-        Most profiles block notifications from this site
+        Most people block notifications from this site
       </message>
       <message name="IDS_GEOLOCATION_QUIET_PERMISSION_BUBBLE_CROWD_DENY_DESCRIPTION" desc="Subtitle for the Geolocation permission prompt, shown when a user clicks on a site's geolocation permission request that is automatically blocked by Brave, as this permission prompt is often denied by other users for this site.">
-        Most profiles block sharing precise location for this site
+        Most people block sharing precise location for this site
       </message>
       <message name="IDS_NOTIFICATIONS_QUIET_PERMISSION_BUBBLE_ABUSIVE_DESCRIPTION" desc="Subtitle for the Notifications permission prompt, shown when a user clicks on a site's notifications permission request that is automatically blocked by Brave because the site is known to employ dark patterns to trick users into accepting the permission.">
         This site may be trying to trick you into allowing intrusive notifications
@@ -17260,7 +17260,7 @@ Please help our engineers fix this problem. Tell us what happened right before y
     <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_2_HEADER" desc="FLEDGE API. A sub title that describes the second of 2 ways a site can get info from Brave in order to target ads to the user.">
       Sites you visit that define your interests
     </message>
-    <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_2_BULLET_POINT_3" desc="FLEDGE API Bullet 3 of 3 that appear beneath the “Sites you visit that define your interests” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How you can manage your data:” is bold and serves as a label to help profiles skimming the page. * “To protect your privacy”: Today, most data is kept for long periods of time. This new Topics API doesn’t retain estimated topics for more than 3 weeks. The only reason for this feature is to protect the user’s privacy. * “auto”: isn’t strictly necessary, but it conveys that this feature is an ongoing part of the service. This isn’t describing, for example, a one-time deletion. * “older than 4 weeks”: We’re trying to convey a rolling delete. Imagine a user opens a browser for the very first time. As the user browses, sites can store info with Brave for up to 4 weeks. So in week 1, the user visits site A. When week 5 starts, site A is removed from the list of sites. * “a site you visit…”: If a user visits site A every week for months on end, that site will remain on the user’s list of sites for months on end. * “Or you can…”: Say a user strongly dislikes www.siteB.com. But that user might visit siteB.com as part of their job, or just to see how bad it really is. The user can stop siteB from defining interests for them. This block lasts indefinitely.">
+    <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_LEARN_MORE_SECTION_2_BULLET_POINT_3" desc="FLEDGE API Bullet 3 of 3 that appear beneath the “Sites you visit that define your interests” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How you can manage your data:” is bold and serves as a label to help people skimming the page. * “To protect your privacy”: Today, most data is kept for long periods of time. This new Topics API doesn’t retain estimated topics for more than 3 weeks. The only reason for this feature is to protect the user’s privacy. * “auto”: isn’t strictly necessary, but it conveys that this feature is an ongoing part of the service. This isn’t describing, for example, a one-time deletion. * “older than 4 weeks”: We’re trying to convey a rolling delete. Imagine a user opens a browser for the very first time. As the user browses, sites can store info with Brave for up to 4 weeks. So in week 1, the user visits site A. When week 5 starts, site A is removed from the list of sites. * “a site you visit…”: If a user visits site A every week for months on end, that site will remain on the user’s list of sites for months on end. * “Or you can…”: Say a user strongly dislikes www.siteB.com. But that user might visit siteB.com as part of their job, or just to see how bad it really is. The user can stop siteB from defining interests for them. This block lasts indefinitely.">
       <ph name="BEGIN_BOLD">&lt;b&gt;</ph>How you can manage your data:<ph name="END_BOLD">&lt;/b&gt;</ph> To protect your privacy, we auto-delete sites from the list that are older than 4 weeks. A site you visit again might appear on the list again. Or you can remove a site if you don’t want that site to ever define interests for you.
     </message>
     <message name="IDS_PRIVACY_SANDBOX_DIALOG_CONSENT_ACCEPT_BUTTON" desc="A button that allows the user to accept joining the Privacy Sandbox trials. If the user chooses “Yes, I’m in”: 1)  this consent page disappears and the flow is complete 2) The Privacy Sandbox trials are turned on for this user. These features include everything described above. The page that hosts the settings will appear at chrome://settings/privacySandbox. Saying “Yes, I’m in” is like turning the toggle on. “No thanks” is like keeping the toggle off.">
diff --git a/app/generated_resources_override.grd b/app/generated_resources_override.grd
index 67f509ca44d2..262d9de96879 100644
--- a/app/generated_resources_override.grd
+++ b/app/generated_resources_override.grd
@@ -401,12 +401,6 @@ are declared in tools/grit/grit_rule.gni.
       <if expr="is_win or is_linux">
         </if>
 
-      <message name="IDS_NOTIFICATIONS_QUIET_PERMISSION_BUBBLE_CROWD_DENY_DESCRIPTION" desc="Subtitle for the Notifications permission prompt, shown when a user clicks on a site's notifications permission request that is automatically blocked by Brave, as this permission prompt is often denied by other users for this site.">
-        Most profiles block notifications from this site
-      </message>
-      <message name="IDS_GEOLOCATION_QUIET_PERMISSION_BUBBLE_CROWD_DENY_DESCRIPTION" desc="Subtitle for the Geolocation permission prompt, shown when a user clicks on a site's geolocation permission request that is automatically blocked by Brave, as this permission prompt is often denied by other users for this site.">
-        Most profiles block sharing precise location for this site
-      </message>
       <if expr="toolkit_views">
         </if>
 
diff --git a/app/nearby_share_strings.grdp b/app/nearby_share_strings.grdp
index 698a9661a64f..278842b77e92 100644
--- a/app/nearby_share_strings.grdp
+++ b/app/nearby_share_strings.grdp
@@ -405,13 +405,13 @@
     Decline
   </message>
   <message name="IDS_NEARBY_NOTIFICATION_ONBOARDING_MESSAGE" desc="Text shown as the message of a notification when a nearby device is attempting to share data via Nearby Share but the user has not yet set up the Nearby Share feature.">
-    Set up Nearby Share to receive and send files with profiles around you
+    Set up Nearby Share to receive and send files with people around you
   </message>
   <message name="IDS_NEARBY_NOTIFICATION_ONBOARDING_MESSAGE_PH" desc="Feature name placeholder: Text shown as the message of a notification when a nearby device is attempting to share data but the user has not yet set up sharing.">
-    Set up <ph name="FEATURE_NAME">$1<ex>Nearby Share</ex></ph> to receive and send files with profiles around you
+    Set up <ph name="FEATURE_NAME">$1<ex>Nearby Share</ex></ph> to receive and send files with people around you
   </message>
   <message name="IDS_NEARBY_NOTIFICATION_GO_VISIBLE_MESSAGE" desc="Text shown as the message of a notification when a nearby device is attempting to share data via Nearby Share. This notification is a prompt that the user can click to become visible to nearby devices that are trying to share.">
-    To receive and accept files with profiles around you, become visible
+    To receive and accept files with people around you, become visible
   </message>
   <message name="IDS_NEARBY_NOTIFICATION_ONBOARDING_TITLE" desc="Text shown as the title of a notification when a nearby device is attempting to share data via Nearby Share.">
     Device nearby is sharing
diff --git a/app/os_settings_strings.grdp b/app/os_settings_strings.grdp
index 865e3bd17dd0..6ca147bd95a8 100644
--- a/app/os_settings_strings.grdp
+++ b/app/os_settings_strings.grdp
@@ -7148,7 +7148,7 @@ Press &amp; hold keyboard keys to see accent marks and special characters. This
     Use secure connections to look up sites
   </message>
   <message name="IDS_OS_SETTINGS_SECURE_DNS_DESCRIPTION" desc="Description of secure DNS in Privacy options">
-    Make it harder for profiles with access to your internet traffic to see which sites you visit. <ph name="PRODUCT_NAME">$1<ex>ChromeOS</ex></ph> uses a secure connection to look up a site's IP address in the DNS (Domain Name System).
+    Make it harder for people with access to your internet traffic to see which sites you visit. <ph name="PRODUCT_NAME">$1<ex>ChromeOS</ex></ph> uses a secure connection to look up a site's IP address in the DNS (Domain Name System).
   </message>
   <message name="IDS_OS_SETTINGS_REVAMP_SECURE_DNS_DIALOG_TITLE" desc="Text for secure DNS dialog title in Privacy options for ChromeOS">
     Turn off URL encryption?
@@ -7169,7 +7169,7 @@ Press &amp; hold keyboard keys to see accent marks and special characters. This
     Secure connections might not always be available when using the network default. Consider selecting a different provider to ensure you're always using a secure connection.
   </message>
   <message name="IDS_OS_SETTINGS_SECURE_DNS_WITH_DOMAIN_CONFIG_DESCRIPTION" desc="Description of secure DNS in Privacy options when included or excluded domains configuration is set">
-    Make it harder for profiles with access to your internet traffic to see which sites you visit. <ph name="PRODUCT_NAME">$1<ex>ChromeOS</ex></ph> uses a secure connection to look up a site's IP address in the DNS (Domain Name System). Secure connections are not used for some domains configured by your administrator.
+    Make it harder for people with access to your internet traffic to see which sites you visit. <ph name="PRODUCT_NAME">$1<ex>ChromeOS</ex></ph> uses a secure connection to look up a site's IP address in the DNS (Domain Name System). Secure connections are not used for some domains configured by your administrator.
   </message>
   <message name="IDS_OS_SETTINGS_SECURE_DNS_WITH_IDENTIFIERS_AND_DOMAIN_CONFIG_DESCRIPTION" desc="Description of secure DNS in Privacy options when DoH identifiers and included or excluded domains configuration is set">
     Use a secure connection to look up a site’s IP address in the DNS (Domain Name System). This uses a managed service provider at <ph name="DNS_SERVER_TEMPLATE_WITH_IDENTIFIER">$1<ex>https://dns.example.net/dns-query{?dns}</ex></ph>. Secure connections are not used for some domains configured by your administrator.
diff --git a/app/os_settings_strings_override.grdp b/app/os_settings_strings_override.grdp
index 7957e94c8963..a52d6d203981 100644
--- a/app/os_settings_strings_override.grdp
+++ b/app/os_settings_strings_override.grdp
@@ -23,11 +23,5 @@
   <message name="IDS_OS_SETTINGS_SMART_PRIVACY_DESC" desc="The text explaining to the user the manner in which their presence is sensed and data usage policy.">
     Your <ph name="DEVICE_TYPE">$1<ex>Chromebook</ex></ph> uses a built-in sensor to detect profiles in front of your device. All data is processed on your device immediately and then deleted. Sensor data is never sent to Brave. <ph name="LINK_BEGIN">&lt;a&gt;</ph>Learn more<ph name="LINK_END">&lt;/a&gt;</ph>
   </message>
-  <message name="IDS_OS_SETTINGS_SECURE_DNS_DESCRIPTION" desc="Description of secure DNS in Privacy options">
-    Make it harder for profiles with access to your internet traffic to see which sites you visit. <ph name="PRODUCT_NAME">$1<ex>ChromeOS</ex></ph> uses a secure connection to look up a site's IP address in the DNS (Domain Name System).
-  </message>
-  <message name="IDS_OS_SETTINGS_SECURE_DNS_WITH_DOMAIN_CONFIG_DESCRIPTION" desc="Description of secure DNS in Privacy options when included or excluded domains configuration is set">
-    Make it harder for profiles with access to your internet traffic to see which sites you visit. <ph name="PRODUCT_NAME">$1<ex>ChromeOS</ex></ph> uses a secure connection to look up a site's IP address in the DNS (Domain Name System). Secure connections are not used for some domains configured by your administrator.
-  </message>
   </if>
 </grit-part>
diff --git a/app/settings_brave_strings.grdp b/app/settings_brave_strings.grdp
index f3035909e92c..97e36d7fbe3e 100644
--- a/app/settings_brave_strings.grdp
+++ b/app/settings_brave_strings.grdp
@@ -216,19 +216,19 @@
   <message name="IDS_SETTINGS_PRIVACY_SANDBOX_LEARN_MORE_DIALOG_TOPICS_TITLE" desc="TOPICS API A sub title that describes the first of 2 ways a site can get info from Brave in order to target ads to the user. Topics of interest include things like “Live comedy” and “Rock music”. Brave estimates these interests based on the sites users visit. * “Your”: we need to convey a sense of ownership, even if the user didn’t explicitly choose the interests we’re talking about. Without the “your”, it could sound like Brave is simply building a generic library of interests. * “estimated”: It’s an “estimation”, and we don’t want to suggest that we know with certainty the user’s interests. Avoid words like “guess”, “establish”, “define”, etc. (in place of “estimate”). * “by Brave”: This is new behavior for a browser (Brave) to take an active role in processing user data for the purposes of showing ads. It’s important to convey “chrome”, the actor in this case.">
     Your interests as estimated by Brave
   </message>
-  <message name="IDS_SETTINGS_PRIVACY_SANDBOX_LEARN_MORE_DIALOG_TOPICS_DATA_TYPES" desc="TOPICS API Bullet 1 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “What data is used:” is bold and serves as a label to help profiles skimming the page. * “Your browsing history”: The user’s browsing history is available beneath the “History” menu at Brave’s top level. The Topics API estimates topics of interest based on sites in the user’s browsing history that are participating in the trials.">
+  <message name="IDS_SETTINGS_PRIVACY_SANDBOX_LEARN_MORE_DIALOG_TOPICS_DATA_TYPES" desc="TOPICS API Bullet 1 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “What data is used:” is bold and serves as a label to help people skimming the page. * “Your browsing history”: The user’s browsing history is available beneath the “History” menu at Brave’s top level. The Topics API estimates topics of interest based on sites in the user’s browsing history that are participating in the trials.">
     Your browsing history, a record of sites you've visited using Brave on this device.
   </message>
-  <message name="IDS_SETTINGS_PRIVACY_SANDBOX_LEARN_MORE_DIALOG_TOPICS_DATA_USAGE" desc="TOPICS API Bullet 2 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How we use this data:” is bold and serves as a label to help profiles skimming the page. * “estimate your interests”: Topics of interest include things like “Live comedy” and “Rock music”. Brave estimates these interests based on the sites users visit. It’s an “estimation”, and we don’t want to suggest that we know with certainty the user’s interests. Avoid words like “guess”, “establish”, “define”, etc. (in place of “estimate”).">
+  <message name="IDS_SETTINGS_PRIVACY_SANDBOX_LEARN_MORE_DIALOG_TOPICS_DATA_USAGE" desc="TOPICS API Bullet 2 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How we use this data:” is bold and serves as a label to help people skimming the page. * “estimate your interests”: Topics of interest include things like “Live comedy” and “Rock music”. Brave estimates these interests based on the sites users visit. It’s an “estimation”, and we don’t want to suggest that we know with certainty the user’s interests. Avoid words like “guess”, “establish”, “define”, etc. (in place of “estimate”).">
     Brave can estimate your interests. Later, a site you visit can ask Brave to see your interests in order to personalize the ads you see.
   </message>
-  <message name="IDS_SETTINGS_PRIVACY_SANDBOX_LEARN_MORE_DIALOG_TOPICS_DATA_MANAGEMENT" desc="TOPICS API Bullet 3 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How you can manage your data:” is bold and serves as a label to help profiles skimming the page. * “To protect your privacy”: Today, most data is kept for long periods of time. This new Topics API doesn’t retain estimated topics for more than 3 weeks. The only reason for this feature is to protect the user’s privacy. * “auto”: isn’t strictly necessary, but it conveys that this feature is an ongoing part of the service. This isn’t describing, for example, a one-time deletion. * “older than 4 weeks”: We’re trying to convey a rolling delete. Imagine a user opens a browser for the very first time. As the user browses, Brave will estimate up to 5 topics of interest in the first week. In the second week, Brave will estimate up to 5 additional topics of interest. The same for the third week, for a total of 15 potential interests. In week 4, Brave will automatically delete the 5 interests from week 1 so that there aren’t ever more than 15 topics associated with a user at any given time. * “interests can refresh”: If a user loves horror films and reads about them for months on end, the interest “Horror movies” might get deleted and refreshed in the same week, so that “Horror movies” doesn’t ever disappear from the user’s list of interests. * “Or you can…”: A user might love horror movies but can’t stand the idea of seeing ads about horror movies (because even the visuals will ruin the surprise of opening night). In this case, the user can remove “Horror movies” from the list of interests Brave will consider. This removal remains in place indefinitely. Note that the user might still see ads about Horror movies from different ad networks or by other means than Brave’s “Browser-based ad personalization” setting.">
+  <message name="IDS_SETTINGS_PRIVACY_SANDBOX_LEARN_MORE_DIALOG_TOPICS_DATA_MANAGEMENT" desc="TOPICS API Bullet 3 of 3 that appear beneath the “Your interests as estimated by Brave” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How you can manage your data:” is bold and serves as a label to help people skimming the page. * “To protect your privacy”: Today, most data is kept for long periods of time. This new Topics API doesn’t retain estimated topics for more than 3 weeks. The only reason for this feature is to protect the user’s privacy. * “auto”: isn’t strictly necessary, but it conveys that this feature is an ongoing part of the service. This isn’t describing, for example, a one-time deletion. * “older than 4 weeks”: We’re trying to convey a rolling delete. Imagine a user opens a browser for the very first time. As the user browses, Brave will estimate up to 5 topics of interest in the first week. In the second week, Brave will estimate up to 5 additional topics of interest. The same for the third week, for a total of 15 potential interests. In week 4, Brave will automatically delete the 5 interests from week 1 so that there aren’t ever more than 15 topics associated with a user at any given time. * “interests can refresh”: If a user loves horror films and reads about them for months on end, the interest “Horror movies” might get deleted and refreshed in the same week, so that “Horror movies” doesn’t ever disappear from the user’s list of interests. * “Or you can…”: A user might love horror movies but can’t stand the idea of seeing ads about horror movies (because even the visuals will ruin the surprise of opening night). In this case, the user can remove “Horror movies” from the list of interests Brave will consider. This removal remains in place indefinitely. Note that the user might still see ads about Horror movies from different ad networks or by other means than Brave’s “Browser-based ad personalization” setting.">
     To protect your privacy, we auto-delete your interests that are older than 4 weeks. As you keep browsing, an interest might appear on the list again. Or you can remove interests you don't want Brave to consider.
   </message>
-  <message name="IDS_SETTINGS_PRIVACY_SANDBOX_LEARN_MORE_DIALOG_FLEDGE_DATA_TYPES" desc="FLEDGE API Bullet 1 of 3 that appear beneath the “Sites you visit that define your interests” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “What data is used:” is bold and serves as a label to help profiles skimming the page. * “Your browsing history”: The user’s browsing history is available beneath the “History” menu at Brave’s top level. This content taken in isolation is somewhat misleading. With FLEDGE, a site can store information in Brave about the user’s visit to their site. For example, the site might store “running_shoes_red_size_35” to indicate that the user showed interest in a particular shoe. We’re OK with the simplification in this bullet because 1) we explain it in the next bullet and 2) we want the user to understand that at the top level, both Topics &amp; Fledge are based on the same thing and that is the user’s browsing history.">
+  <message name="IDS_SETTINGS_PRIVACY_SANDBOX_LEARN_MORE_DIALOG_FLEDGE_DATA_TYPES" desc="FLEDGE API Bullet 1 of 3 that appear beneath the “Sites you visit that define your interests” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “What data is used:” is bold and serves as a label to help people skimming the page. * “Your browsing history”: The user’s browsing history is available beneath the “History” menu at Brave’s top level. This content taken in isolation is somewhat misleading. With FLEDGE, a site can store information in Brave about the user’s visit to their site. For example, the site might store “running_shoes_red_size_35” to indicate that the user showed interest in a particular shoe. We’re OK with the simplification in this bullet because 1) we explain it in the next bullet and 2) we want the user to understand that at the top level, both Topics &amp; Fledge are based on the same thing and that is the user’s browsing history.">
     Your browsing history, a record of sites you've visited using Brave on this device.
   </message>
-  <message name="IDS_SETTINGS_PRIVACY_SANDBOX_LEARN_MORE_DIALOG_FLEDGE_DATA_USAGE" desc="FLEDGE API Bullet 2 of 3 that appear beneath the “Sites you visit that define your interests” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How we use this data:” is bold and serves as a label to help profiles skimming the page. With FLEDGE, a site can store information in Brave about the user’s visit to their site. For example, the site might store “running_shoes_red_size_35” to indicate that the user showed interest in a particular shoe. We’re OK with the simplification in this bullet because 1) we explain it in the next bullet and 2) we want the user to understand that at the top level, both Topics &amp; Fledge are based on the same thing and that is the user’s browsing history. * “Later”:  is important to convey the passage of time. We don’t want to convey how much time (it could be tiny). What’s important is that the user understands this is essentially a two-step process. They browse, and Brave might estimate their interests as they do so. At a later point when they continue to visit a site, that’s when the estimated interests might come into play.">
+  <message name="IDS_SETTINGS_PRIVACY_SANDBOX_LEARN_MORE_DIALOG_FLEDGE_DATA_USAGE" desc="FLEDGE API Bullet 2 of 3 that appear beneath the “Sites you visit that define your interests” subtitle. We break the description into the 3 pieces users most care about: 1) what data, 2) why this data, 3) what can I do about it? * “How we use this data:” is bold and serves as a label to help people skimming the page. With FLEDGE, a site can store information in Brave about the user’s visit to their site. For example, the site might store “running_shoes_red_size_35” to indicate that the user showed interest in a particular shoe. We’re OK with the simplification in this bullet because 1) we explain it in the next bullet and 2) we want the user to understand that at the top level, both Topics &amp; Fledge are based on the same thing and that is the user’s browsing history. * “Later”:  is important to convey the passage of time. We don’t want to convey how much time (it could be tiny). What’s important is that the user understands this is essentially a two-step process. They browse, and Brave might estimate their interests as they do so. At a later point when they continue to visit a site, that’s when the estimated interests might come into play.">
     Sites can store information with Brave about your interests. For example, if you visit a site to buy shoes for a marathon, the site might define your interest as running marathons. Later, if you visit a different site to register for a race, that site can show you an ad for running shoes based on your interests.
   </message>
   <message name="IDS_SETTINGS_PRIVACY_SANDBOX_AD_PERSONALIZATION_DIALOG_DESCRIPTION" desc="A paragraph beneath the card title. Note that this paragraph is written so that it describes both the Topics API and the FLEDGE API. Some things are described slightly differently for this reason. Version 1 of 3 of this paragraph.  1) The first line is written with the assumption that the user a) has Privacy Sandbox trials turned on and b) has been randomly selected by Brave to be in  an active experiment. As a result of both conditions, this user should have data on this page (a list of interests and a list of sites). 2) NOT THE CASE FOR THIS STRING: A different version of  this first line is written for the case that a user has the Privacy Sandbox trials turned on but they haven’t been randomly selected to be in a trial. 3) NOT THE CASE FOR THIS STRING: A different version of  this first line is written for the case that a user doesn’t have the Privacy Sandbox trials turned on. * “browsing history”:  “a record of sites you’ve visited using Brave on this device.” * “affects the ads you see and the interests as estimated below”: browsing history leads to Brave establishing user interests leads to 1) the ads you see are different, and 2) the list of things on this page changes based on what Brave establishes.* “To protect your privacy”: Today, most data is kept for long periods of time. This new Topics API doesn’t retain estimated topics for more than 3 weeks. The only reason for this feature is to protect the user’s privacy. * “auto”: isn’t strictly necessary, but it conveys that this feature is an ongoing part of the service. This isn’t describing, for example, a one-time deletion. * “rolling basis each month”: Information associated with Topics and FLEDGE are deleted on a rolling basis at least once per month. It’s simpler to talk about “once per month” rather than 3 weeks for Topics and 4 weeks for FLEDGE. * “Interests can refresh…”: We intend for this line to cover both Topics and FLEDGE. It’s slightly messy, because there is a suggestion that this line is more about Topics than FLEDGE (“interests” is more prominent in the Topics subtitle).">
@@ -299,7 +299,7 @@
     Learn more about <ph name="BEGIN_LINK">&lt;a href="#" id="enhancedProtectionLearnMoreLink" on-click="onEnhancedProtectionLearnMoreClick_"&gt;</ph>how Brave keeps your data private<ph name="END_LINK">&lt;/a&gt;<ex>&lt;/a&gt;</ex></ph>
   </message>
   <message name="IDS_SETTINGS_SECURE_DNS_DESCRIPTION" desc="Secondary, continued explanation of secure DNS in Privacy options">
-    Make it harder for profiles with access to your internet traffic to see which sites you visit. Brave uses a secure connection to look up a site's IP address in the DNS (Domain Name System).
+    Make it harder for people with access to your internet traffic to see which sites you visit. Brave uses a secure connection to look up a site's IP address in the DNS (Domain Name System).
   </message>
 
   <!-- Profiles Page -->
diff --git a/app/settings_brave_strings_override.grdp b/app/settings_brave_strings_override.grdp
index da4461f73309..6d476d9f08f5 100644
--- a/app/settings_brave_strings_override.grdp
+++ b/app/settings_brave_strings_override.grdp
@@ -26,10 +26,6 @@
   <if expr="not is_chromeos">
     </if>
 
-  <message name="IDS_SETTINGS_SECURE_DNS_DESCRIPTION" desc="Secondary, continued explanation of secure DNS in Privacy options">
-    Make it harder for profiles with access to your internet traffic to see which sites you visit. Brave uses a secure connection to look up a site's IP address in the DNS (Domain Name System).
-  </message>
-
   <if expr="not chromeos_ash">
   </if>
   <if expr="chromeos_ash">
diff --git a/app/settings_strings.grdp b/app/settings_strings.grdp
index 639b63a36483..bcbccd07fa9d 100644
--- a/app/settings_strings.grdp
+++ b/app/settings_strings.grdp
@@ -1504,16 +1504,16 @@
     Sites can't help verify you're not a bot
   </message>
   <message name="IDS_SETTINGS_ANTI_ABUSE_DESCRIPTION" desc="The label used for the anti-abuse site settings description.">
-    Sites you visit can verify that you're a real profile and not a bot
+    Sites you visit can verify that you're a real person and not a bot
   </message>
   <message name="IDS_SETTINGS_ANTI_ABUSE_WHEN_ON_SECTION_ONE" desc="A description that informs users that Brave saves a small amount of data when the anti-abuse features are enabled.">
     A site you visit can save a small amount of info with Brave, mainly to validate you're not a bot
   </message>
   <message name="IDS_SETTINGS_ANTI_ABUSE_WHEN_ON_SECTION_TWO" desc="A description that informs users how the anti-abuse features work.">
-    As you keep browsing, sites can check with Brave and verify with a previous site you've visited that you're likely a real profile
+    As you keep browsing, sites can check with Brave and verify with a previous site you've visited that you're likely a real person
   </message>
   <message name="IDS_SETTINGS_ANTI_ABUSE_WHEN_ON_SECTION_THREE" desc="A description that informs users how their browsing could be helped by the anti-abuse features.">
-    Browsing is faster because a site is less likely to ask you to verify you're a real profile
+    Browsing is faster because a site is less likely to ask you to verify you're a real person
   </message>
   <message name="IDS_SETTINGS_ANTI_ABUSE_THINGS_TO_CONSIDER_SECTION_ONE" desc="A description that informs users that the anti-abuse features do not reveal their browsing history.">
     This setting works without identifying you or allowing sites to see your browsing history, though sites can share a small amount of info as part of the verification
diff --git a/app/settings_strings_override.grdp b/app/settings_strings_override.grdp
index 180cd51e8421..9be6c376e460 100644
--- a/app/settings_strings_override.grdp
+++ b/app/settings_strings_override.grdp
@@ -96,15 +96,6 @@
       </if>
   </if>
 
-  <message name="IDS_SETTINGS_ANTI_ABUSE_DESCRIPTION" desc="The label used for the anti-abuse site settings description.">
-    Sites you visit can verify that you're a real profile and not a bot
-  </message>
-  <message name="IDS_SETTINGS_ANTI_ABUSE_WHEN_ON_SECTION_TWO" desc="A description that informs users how the anti-abuse features work.">
-    As you keep browsing, sites can check with Brave and verify with a previous site you've visited that you're likely a real profile
-  </message>
-  <message name="IDS_SETTINGS_ANTI_ABUSE_WHEN_ON_SECTION_THREE" desc="A description that informs users how their browsing could be helped by the anti-abuse features.">
-    Browsing is faster because a site is less likely to ask you to verify you're a real profile
-  </message>
   <message name="IDS_SETTINGS_PRIVACY_GUIDE_COOKIES_CARD_BLOCK_TPC_INCOGNITO_SUBHEADER" desc="A subheader for the cookies card of the 'Privacy guide', for blocking third party cookies in private.">
     Block third-party cookies in Private
   </message>
diff --git a/browser/ui/android/strings/android_chrome_strings.grd b/browser/ui/android/strings/android_chrome_strings.grd
index 9eeb0315e07d..20175bc2d425 100644
--- a/browser/ui/android/strings/android_chrome_strings.grd
+++ b/browser/ui/android/strings/android_chrome_strings.grd
@@ -3632,7 +3632,7 @@ To change this setting, <ph name="BEGIN_LINK">BEGIN_LINK</ph>delete the Brave da
         When on
       </message>
       <message name="IDS_SIGNIN_FRE_UMA_DIALOG_FIRST_SECTION_BODY" desc="Text that describes the benefits users will get if they turn on the metrics sharing option.">
-        Help make Brave better for profiles who use it the way you do
+        Help make Brave better for people who use it the way you do
       </message>
       <message name="IDS_SIGNIN_FRE_UMA_DIALOG_SECOND_SECTION_HEADER" desc="Header of the section with info about the data that users share with Brave if they turn on the metric sharing option.">
         Things to consider
@@ -5985,7 +5985,7 @@ To change this setting, <ph name="BEGIN_LINK">BEGIN_LINK</ph>delete the Brave da
       </message>
 
       <message name="IDS_QR_CODE_SHARE_DESCRIPTION" desc="Text on QR Code sharing tab describing how to use the QR Code.">
-        To share with profiles nearby, let them scan this QR Code
+        To share with people nearby, let them scan this QR Code
       </message>
 
       <message name="IDS_QR_CODE_DOWNLOAD" desc="Text on QR Code download button.">
diff --git a/browser/ui/android/strings/android_chrome_strings_override.grd b/browser/ui/android/strings/android_chrome_strings_override.grd
index c0a02f7333ae..99a041d19c6a 100644
--- a/browser/ui/android/strings/android_chrome_strings_override.grd
+++ b/browser/ui/android/strings/android_chrome_strings_override.grd
@@ -186,9 +186,6 @@ CHAR_LIMIT guidelines:
         Private tabs will be locked when you leave Brave
      </message>
 
-      <message name="IDS_SIGNIN_FRE_UMA_DIALOG_FIRST_SECTION_BODY" desc="Text that describes the benefits users will get if they turn on the metrics sharing option.">
-        Help make Brave better for profiles who use it the way you do
-      </message>
       <message name="IDS_NEW_INCOGNITO_TAB_TITLE" desc="Title in tab strip when opening a new Private tab.">
         New Private tab
       </message>
@@ -278,10 +275,6 @@ CHAR_LIMIT guidelines:
       <message name="IDS_QUICK_ACTION_SEARCH_WIDGET_MESSAGE_NO_INCOGNITO" desc="Toast message shown when the user tries to open Private tab which is disabled on the device.">
         Private is not available on this device
       </message>
-      <message name="IDS_QR_CODE_SHARE_DESCRIPTION" desc="Text on QR Code sharing tab describing how to use the QR Code.">
-        To share with profiles nearby, let them scan this QR Code
-      </message>
-
       <message name="IDS_NOTIFICATION_PERMISSION_RATIONALE_DIALOG_MESSAGE" desc="The body text of a dialog explaining the benefits of enabling Brave notifications.">
         You’ll be able to easily manage media controls, Private sessions, downloads and more
       </message>
diff --git a/components/payments_strings.grdp b/components/payments_strings.grdp
index db2525deb21a..ae521cde27a3 100644
--- a/components/payments_strings.grdp
+++ b/components/payments_strings.grdp
@@ -32,7 +32,7 @@
     <message name="IDS_PAYMENTS_ADD_PHONE_NUMBER" desc="The title of the dialog for user to add phone number to the shipping address or contact info. This phone number can be used, for example, if there's a problem with shipping a package to its destination. Sentence-cased." formatter_data="android_java">
       Add phone number
     </message>
-    <message name="IDS_PAYMENTS_ADD_RECIPIENT" desc="The title of the dialog for user to add the name in the shipping address. This name identifies the profile that will receive the shipped package. Sentence-cased." formatter_data="android_java">
+    <message name="IDS_PAYMENTS_ADD_RECIPIENT" desc="The title of the dialog for user to add the name in the shipping address. This name identifies the person that will receive the shipped package. Sentence-cased." formatter_data="android_java">
       Add name
     </message>
     <message name="IDS_PAYMENTS_ADD_VALID_ADDRESS" desc="The title of the dialog for user to add valid shipping address. For example, missing state or city name. Sentence-cased." formatter_data="android_java">
@@ -41,7 +41,7 @@
     <message name="IDS_PAYMENTS_ADD_EMAIL" desc="The title of the dialog for user to add email to the contact details. This email can be used to contact the payer. Sentence-cased." formatter_data="android_java">
       Add email
     </message>
-    <message name="IDS_PAYMENTS_ADD_NAME" desc="The title of the dialog for user to add name to the contact details. This name could be a profile or institute name of the payer. Sentence-cased." formatter_data="android_java">
+    <message name="IDS_PAYMENTS_ADD_NAME" desc="The title of the dialog for user to add name to the contact details. This name could be a person or institute name of the payer. Sentence-cased." formatter_data="android_java">
       Add name
     </message>
     <message name="IDS_PAYMENTS_ORDER_SUMMARY_LABEL" desc="The title of the section that shows the summary of the order, including names and prices of individual line items, i.e. the bill. Sentence-cased." formatter_data="android_java">
@@ -83,7 +83,7 @@
     <message name="IDS_PAYMENTS_ADD_PHONE_NUMBER" desc="The title of the dialog for user to add phone number to the shipping address or contact info. This phone number can be used, for example, if there's a problem with shipping a package to its destination. Title-Cased.">
       Add Phone Number
     </message>
-    <message name="IDS_PAYMENTS_ADD_RECIPIENT" desc="The title of the dialog for user to add the name in the shipping address. This name identifies the profile that will receive the shipped package. Title-Cased.">
+    <message name="IDS_PAYMENTS_ADD_RECIPIENT" desc="The title of the dialog for user to add the name in the shipping address. This name identifies the person that will receive the shipped package. Title-Cased.">
       Add Name
     </message>
     <message name="IDS_PAYMENTS_ADD_VALID_ADDRESS" desc="The title of the dialog for user to add valid shipping address. For example, missing state or city name. Title-Cased.">
@@ -92,7 +92,7 @@
     <message name="IDS_PAYMENTS_ADD_EMAIL" desc="The title of the dialog for user to add email to the contact details. This email can be used to contact the payer. Title-Cased.">
       Add Email
     </message>
-    <message name="IDS_PAYMENTS_ADD_NAME" desc="The title of the dialog for user to add name to the contact details. This name could be a profile or institute name of the payer. Title-Cased.">
+    <message name="IDS_PAYMENTS_ADD_NAME" desc="The title of the dialog for user to add name to the contact details. This name could be a person or institute name of the payer. Title-Cased.">
       Add Name
     </message>
     <message name="IDS_PAYMENTS_ORDER_SUMMARY_LABEL" desc="The title of the section that shows the summary of the order, including names and prices of individual line items, i.e. the bill. Title-Cased.">
@@ -324,13 +324,13 @@
   <message name="IDS_PAYMENTS_PHONE_NUMBER_REQUIRED" desc="The label to indicate phone number is required in the shipping address or contact info. This phone number can be used, for example, if there's a problem with shipping a package to its destination." formatter_data="android_java">
     Phone number required
   </message>
-  <message name="IDS_PAYMENTS_RECIPIENT_REQUIRED" desc="The label to indicate recipient name is required in the shipping address. This name identifies the profile that will receive the shipped package." formatter_data="android_java">
+  <message name="IDS_PAYMENTS_RECIPIENT_REQUIRED" desc="The label to indicate recipient name is required in the shipping address. This name identifies the person that will receive the shipped package." formatter_data="android_java">
     Name required
   </message>
   <message name="IDS_PAYMENTS_EMAIL_REQUIRED" desc="The label to indicate email is required for the contact details. This email can be used to contact the payer." formatter_data="android_java">
     Email required
   </message>
-  <message name="IDS_PAYMENTS_NAME_REQUIRED" desc="The label to indicate name is required for the contact details. This name could be a profile or institute name of the payer." formatter_data="android_java">
+  <message name="IDS_PAYMENTS_NAME_REQUIRED" desc="The label to indicate name is required for the contact details. This name could be a person or institute name of the payer." formatter_data="android_java">
     Name required
   </message>
 
diff --git a/components/privacy_sandbox_chrome_strings.grdp b/components/privacy_sandbox_chrome_strings.grdp
index 0ef26204da7d..1937872ea06a 100644
--- a/components/privacy_sandbox_chrome_strings.grdp
+++ b/components/privacy_sandbox_chrome_strings.grdp
@@ -58,7 +58,7 @@
   <message name="IDS_PRIVACY_SANDBOX_M1_NOTICE_EEA_DESCRIPTION_1" desc="* 'we' refers to Brave. We're using a personal pronoun to improve tone and make the moment more conversational, but that's not required and you can replace this with 'Brave is launching new ways...' * 'limit': Don't use a word like 'prevent', because we can't promise that. A site can still learn something about a user when they use these new settings, but it's relatively little compared to what a site can learn using third-party cookies. * 'when they show you personalized ads': We're referring to the ad-personalization system broadly. Arguably, a site doesn't learn anything about a user when that user is shown a single ad (except if the user clicks on the ad), but in the process of learning about their users and showing them ads, a site learns something about specific users. * 'for example:': 2 bullets follow these words. We're suggesting that the bullets describe ways we limit what sites can learn but that these 2 things aren't the only ways. In fact, the Ad topics setting described on the first screen of this Consent/Notice moment also helps limit what sites can learn about you as part of the ad personalization system. **** CONTEXT PRIVACY SANDBOX **** Brave’s Privacy Sandbox initiative 1) deprecates third-party cookies in Brave, 2) supports free and open content on the web (by finding better ways to support ads online), 3) while providing stronger privacy protections for users. You can see a high-level description of this public project at www.privacysanbox.com. **** CONTEXT EEA NOTICE **** 1) This screen provides notice to Brave users in the European Economic Area (EEA). It follows guidelines established by the GDPR.  2) This screen is the second of 2 screens. This second screen describes 2 settings: “Site-suggested ads” and “Ad measurement”. The first screen describes the “Ad topics” setting.  **** CONTEXT PRIVACY SANDBOX **** Brave’s Privacy Sandbox initiative 1) deprecates third-party cookies in Brave, 2) supports free and open content on the web (by finding better ways to support ads online), 3) while providing stronger privacy protections for users. You can see a high-level description of this public project at www.privacysanbox.com. **** CONTEXT EEA NOTICE **** 1) This screen provides notice to Brave users in the European Economic Area (EEA). It follows guidelines established by the GDPR.  2) This screen is the second of 2 screens. This second screen describes 2 settings: “Site-suggested ads” and “Ad measurement”. The first screen describes the “Ad topics” setting. " formatter_data="android_java">
     We’re launching new ways to limit what sites can learn about you when they show you personalized ads, for example:
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_M1_NOTICE_EEA_BULLET_1" desc="* This is 1 of 2 bullets that site beneath the sentence: 'We’re launching new ways to limit what sites can learn about you when they show you personalized ads, for example:' * 'Site-suggested ads' is the name of a new setting we're launching and that appears on the Ad privacy page of Brave settings.  * 'help protect your browsing history and identity': Today, with third-party cookies, an ad company can track a user from site to site, and often know who the user is by name. The new settings help sites maintain personalized ads while limiting sites from tracking users from site to site, another way to say 'protecting your browsing history'.  * 'while enabling sites': When this new setting is on, a site can ask Brave for information that helps the site show the user personalized ads. Brave is helping the site show personalized ads (and thus helping sites earn money and keep the Internet free to profiles browsing). * 'Based on your activity' this sentence explains how this setting works. 'your activity' refers to your activity on a specific site, not to your browsing history. * 'a site you visited': This setting is about the user's interaction with a single site; not the user's browsing history. This string is intentionally in the past tense to help the reader understand that there are 2 stages associated with this setting: 1) a user interacts with a site and the site (or an advertiser associated with the site), gets a sense for the user based on that interaction. And then 2) later, as the user engages with a different site, the user might see ads suggested by the first site. * 'can suggest related ads': Say you visit a site that sells shoes. That site can store info with Brave, such as the fact that you nearly purchased running shoes on the first site. Then as you keep browsing, other sites can ask Brave for this info saved by the first site and show you ads related to running shows suggested by the first site. * 'You can see...' this sentence gives the user a sense of control. The user can always turn this setting off and not receive 'site-suggested ads'. Or, if this setting is on, a user can block a specific site from suggesting ads. **** CONTEXT PRIVACY SANDBOX **** Brave’s Privacy Sandbox initiative 1) deprecates third-party cookies in Brave, 2) supports free and open content on the web (by finding better ways to support ads online), 3) while providing stronger privacy protections for users. You can see a high-level description of this public project at www.privacysanbox.com. **** CONTEXT EEA NOTICE **** 1) This screen provides notice to Brave users in the European Economic Area (EEA). It follows guidelines established by the GDPR.  2) This screen is the second of 2 screens. This second screen describes 2 settings: “Site-suggested ads” and “Ad measurement”. The first screen describes the “Ad topics” setting. " formatter_data="android_java">
+  <message name="IDS_PRIVACY_SANDBOX_M1_NOTICE_EEA_BULLET_1" desc="* This is 1 of 2 bullets that site beneath the sentence: 'We’re launching new ways to limit what sites can learn about you when they show you personalized ads, for example:' * 'Site-suggested ads' is the name of a new setting we're launching and that appears on the Ad privacy page of Brave settings.  * 'help protect your browsing history and identity': Today, with third-party cookies, an ad company can track a user from site to site, and often know who the user is by name. The new settings help sites maintain personalized ads while limiting sites from tracking users from site to site, another way to say 'protecting your browsing history'.  * 'while enabling sites': When this new setting is on, a site can ask Brave for information that helps the site show the user personalized ads. Brave is helping the site show personalized ads (and thus helping sites earn money and keep the Internet free to people browsing). * 'Based on your activity' this sentence explains how this setting works. 'your activity' refers to your activity on a specific site, not to your browsing history. * 'a site you visited': This setting is about the user's interaction with a single site; not the user's browsing history. This string is intentionally in the past tense to help the reader understand that there are 2 stages associated with this setting: 1) a user interacts with a site and the site (or an advertiser associated with the site), gets a sense for the user based on that interaction. And then 2) later, as the user engages with a different site, the user might see ads suggested by the first site. * 'can suggest related ads': Say you visit a site that sells shoes. That site can store info with Brave, such as the fact that you nearly purchased running shoes on the first site. Then as you keep browsing, other sites can ask Brave for this info saved by the first site and show you ads related to running shows suggested by the first site. * 'You can see...' this sentence gives the user a sense of control. The user can always turn this setting off and not receive 'site-suggested ads'. Or, if this setting is on, a user can block a specific site from suggesting ads. **** CONTEXT PRIVACY SANDBOX **** Brave’s Privacy Sandbox initiative 1) deprecates third-party cookies in Brave, 2) supports free and open content on the web (by finding better ways to support ads online), 3) while providing stronger privacy protections for users. You can see a high-level description of this public project at www.privacysanbox.com. **** CONTEXT EEA NOTICE **** 1) This screen provides notice to Brave users in the European Economic Area (EEA). It follows guidelines established by the GDPR.  2) This screen is the second of 2 screens. This second screen describes 2 settings: “Site-suggested ads” and “Ad measurement”. The first screen describes the “Ad topics” setting. " formatter_data="android_java">
     Site-suggested ads help protect your browsing history and identity while enabling sites to show you relevant ads. Based on your activity, a site you visited can suggest related ads as you continue browsing. You can see a list of these sites and block the ones you don’t want in settings.
   </message>
   <message name="IDS_PRIVACY_SANDBOX_M1_NOTICE_EEA_BULLET_2" desc="* This is 2 of 2 bullets that site beneath the sentence: 'We’re launching new ways to limit what sites can learn about you when they show you personalized ads, for example:' * 'ad measurement' is the name of a new setting we're launching and that appears on the Ad privacy page of Brave settings.  * 'limited types of data': This setting helps an advertiser associate a user's actions on one site with their actions on another. For example, a user sees an ad on one site and then later buys that product from the company that sells the product. The ad measurement setting allows Brave to help a company make the association between the two sites so that the first site can be fairly compensated for showing an ad. Compared with third-party cookies, very little info is shared between sites to support this functionality.  **** CONTEXT PRIVACY SANDBOX **** Brave’s Privacy Sandbox initiative 1) deprecates third-party cookies in Brave, 2) supports free and open content on the web (by finding better ways to support ads online), 3) while providing stronger privacy protections for users. You can see a high-level description of this public project at www.privacysanbox.com. **** CONTEXT EEA NOTICE **** 1) This screen provides notice to Brave users in the European Economic Area (EEA). It follows guidelines established by the GDPR.  2) This screen is the second of 2 screens. This second screen describes 2 settings: “Site-suggested ads” and “Ad measurement”. The first screen describes the “Ad topics” setting. ">
@@ -447,7 +447,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_38" desc="Taxonomy Member. Meaning: [film, television or video game music and themes; film, tv, and video game music composers] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/1271305976669033594">
     Soundtracks
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_39" desc="Taxonomy Member. Meaning: [Radio programs in which profiles talk about politics, sports, current affairs, etc., and listeners can make phone calls to give their opinions; talk radio shows, networks and personalities.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/2579922399234486228">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_39" desc="Taxonomy Member. Meaning: [Radio programs in which people talk about politics, sports, current affairs, etc., and listeners can make phone calls to give their opinions; talk radio shows, networks and personalities.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/2579922399234486228">
     Talk Radio
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_40" desc="Taxonomy Member. Meaning: [Regional and ethnic music of various genres, specifically non-Western popular and traditional music; also, a catch-all marketing term for popularized folk traditions and ethnic music, or pop from outside of the Anglo traditions of the United States, Canada, Australia, New Zealand and the United Kingdom; the world music section in a record store might include albums of Hawaiian slack-key guitar, Cajun zydeco, Dominican merengue and Algerian ra?, among others (source: Wikipedia).] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/3402857732233686445">
@@ -456,7 +456,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_41" desc="Taxonomy Member. Meaning: [The music of the Caribbean; some of the styles to gain wide popularity outside of the Caribbean include reggae, zouk, calypso, and punta; Reggae more properly denotes a particular music style that originated following on the development of ska and rocksteady (source: Wikipedia).] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/2346297341997046685">
     Reggae &amp; Caribbean Music
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_42" desc="Taxonomy Member. Meaning: [online image-based content; online galleries of images and photos with minimal text; collections of images or photos of famous profiles, places and events, or items of interest; typically, static hosted image content, not necessarily user-uploaded or shared content] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/6886302747700347831">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_42" desc="Taxonomy Member. Meaning: [online image-based content; online galleries of images and photos with minimal text; collections of images or photos of famous people, places and events, or items of interest; typically, static hosted image content, not necessarily user-uploaded or shared content] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/6886302747700347831">
     Online Image Galleries
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_43" desc="Taxonomy Member. Meaning: [online digital video content] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/5096385157103445048">
@@ -483,7 +483,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_50" desc="Taxonomy Member. Meaning: [family-oriented television shows that are made for, and whose primary audiences are, parents, teens and children] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/544990757699326442">
     TV Familly-oriented Shows
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_51" desc="Taxonomy Member. Meaning: [a genre of (generally episodic) television programming that presents purportedly unscripted dramatic or humorous situations, documents actual events, and usually features ordinary profiles instead of professional actors (Source: Wikipedia)] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/2228280087691900252">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_51" desc="Taxonomy Member. Meaning: [a genre of (generally episodic) television programming that presents purportedly unscripted dramatic or humorous situations, documents actual events, and usually features ordinary people instead of professional actors (Source: Wikipedia)] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/2228280087691900252">
     TV Reality Shows
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_52" desc="Taxonomy Member. Meaning: [TV sci-fi shows featuring futuristic elements such as spacecraft, robots, cyborgs, interstellar space travel or other technologies; fantasy shows featuring magic, supernatural events, mythology, folklore, or exotic fantasy worlds (source: Wikipedia).] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/1831820498314087291">
@@ -585,7 +585,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_84" desc="Taxonomy Member. Meaning: [pre-owned vehicle listings, automotive classifieds and used vehicle dealers] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/6039885784743740565">
     Used Vehicles
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_85" desc="Taxonomy Member. Meaning: [vehicles shows, expos, and conferences for manufacturers and other profiles in the industry, the specialized press, and/or enthusiasts] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/7339196590922475651">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_85" desc="Taxonomy Member. Meaning: [vehicles shows, expos, and conferences for manufacturers and other people in the industry, the specialized press, and/or enthusiasts] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/7339196590922475651">
     Vehicle Shows
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_86" desc="Taxonomy Member. Meaning: [beauty, style, fashion and fitness; self-care, hygiene, body-image and wellness] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/4884736190847523854">
@@ -717,7 +717,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_128" desc="Taxonomy Member. Meaning: [computer devices that are not part of the essential computer (the processor, memory, and data paths) but are situated relatively close by; typically, input and output devices to a host computer, expanding the host's capabilities, but not forming part of the core computer architecture (Source: Wikipedia)] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/1309547678103520411">
     Computer Peripherals
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_129" desc="Taxonomy Member. Meaning: [electronic equipment intended for use by everyday profiles, not including computers] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/3831373972074857037">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_129" desc="Taxonomy Member. Meaning: [electronic equipment intended for use by everyday people, not including computers] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/3831373972074857037">
     Consumer Electronics
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_130" desc="Taxonomy Member. Meaning: [cameras and camcorders, including retailers, related information, etc.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/4178771562445010882">
@@ -783,7 +783,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_150" desc="Taxonomy Member. Meaning: [services that combine various kinds of bookkeeping and accounting activities; products and services aiming at tracking business income and expenses and answer specific questions about the financial and tax status of an individual or business] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/956251474921720097">
     Accounting &amp; Auditing
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_151" desc="Taxonomy Member. Meaning: [services that provide tax preparation or prepare taxes for profiles; includes advice and tips for both tax preparation.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/4760464649248515637">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_151" desc="Taxonomy Member. Meaning: [services that provide tax preparation or prepare taxes for people; includes advice and tips for both tax preparation.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/4760464649248515637">
     Tax Preparation &amp; Planning
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_152" desc="Taxonomy Member. Meaning: [credit and debit card companies, offers and reviews] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/3200267103650246507">
@@ -816,7 +816,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_161" desc="Taxonomy Member. Meaning: [the type of property insurance that covers private homes; fire insurance, burglary insurance, earthquake insurance, flood insurance, acts of god insurance, tornado insurance, weather-related insurance, hurricane insurance, breaking and entry insurance, b &amp; e insurance, property insurance, renters insurance] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/9147523895969579006">
     Home Insurance
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_162" desc="Taxonomy Member. Meaning: [a contract between an insurance policy holder and an insurer, where the insurer promises to pay a designated beneficiary a sum of money (the &quot;benefits&quot;) upon the death of the insured profile (Source: Wikipedia)] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/8531475784994978055">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_162" desc="Taxonomy Member. Meaning: [a contract between an insurance policy holder and an insurer, where the insurer promises to pay a designated beneficiary a sum of money (the &quot;benefits&quot;) upon the death of the insured person (Source: Wikipedia)] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/8531475784994978055">
     Life Insurance
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_163" desc="Taxonomy Member. Meaning: [insurance that is intended to cover medical expenses, financial default of travel suppliers, and other losses incurred while traveling, either within one's own country, or internationally  (Source: Wikipedia)] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/637641992572614367">
@@ -1083,7 +1083,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_250" desc="Taxonomy Member. Meaning: [Groups of profiles, usually with common interests, whose members interact with each other primarily via the internet. Online communities can act as information systems where members can post, comment on discussions, give advice or collaborate. Commonly, profiles communicate through social networking sites, chat rooms, forums, email lists and discussion boards. Profiles may also join online communities through video games, blogs and virtual worlds.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/6671943044295819214">
     Online Communities
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_251" desc="Taxonomy Member. Meaning: [services and networks that help profiles find partners; dating chats, personal ads, photo rating, matchmaking services] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/467538341939407273">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_251" desc="Taxonomy Member. Meaning: [services and networks that help people find partners; dating chats, personal ads, photo rating, matchmaking services] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/467538341939407273">
     Dating &amp; Personals
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_252" desc="Taxonomy Member. Meaning: [A space for holding discussions and posting user-generated content. Providers of message board and chat services; not to be confused with single-topic forums.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/8377469718949969520">
@@ -1092,7 +1092,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_253" desc="Taxonomy Member. Meaning: [A dedicated website or application built around a network of linked user profiles; users communicate with each other by posting information, comments, messages, images, etc. Well-known examples include Facebook, VKontakte, LinkedIn etc.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/2936561296339527677">
     Social Networks
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_254" desc="Taxonomy Member. Meaning: [Umbrella category that encompasses social groups and social issues based on personal identity, cultural traditions, family, faith and personal beliefs; &quot;special interest&quot; groups and communities; communities based on age, gender, ethnicity, religion, political affiliation or lifestyle choice; the scientific study of profiles and social groups in the &quot;social sciences&quot;.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/5098251294806643822">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_254" desc="Taxonomy Member. Meaning: [Umbrella category that encompasses social groups and social issues based on personal identity, cultural traditions, family, faith and personal beliefs; &quot;special interest&quot; groups and communities; communities based on age, gender, ethnicity, religion, political affiliation or lifestyle choice; the scientific study of people and social groups in the &quot;social sciences&quot;.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/5098251294806643822">
     People &amp; Society
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_255" desc="Taxonomy Member. Meaning: [interpersonal relationships, including family, friendship and romance] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/1748891129952062597">
@@ -1113,7 +1113,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_260" desc="Taxonomy Member. Meaning: [products and services for newborns, babies, and children between the ages of one and three; content related to care and nurture of children in the first years of their life] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/4781411966627663176">
     Babies &amp; Toddlers
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_261" desc="Taxonomy Member. Meaning: [Content about making the internet a safe place for children and young profiles. Includes parental controls, monitoring services, educational resources, etc.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/5965261215029338496">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_261" desc="Taxonomy Member. Meaning: [Content about making the internet a safe place for children and young people. Includes parental controls, monitoring services, educational resources, etc.] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/5965261215029338496">
     Child Internet Safety
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_262" desc="Taxonomy Member. Meaning: [content appealing to science fiction and fantasy fans] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/279327516333715085">
@@ -1248,7 +1248,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_305" desc="Taxonomy Member. Meaning: [the sport of bowling, with particular emphasis on ten-pin bowling] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/312182251545064223">
     Bowling
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_306" desc="Taxonomy Member. Meaning: [a combat sport in which two profiles throw punches at each other] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/8111928385046363700">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_306" desc="Taxonomy Member. Meaning: [a combat sport in which two people throw punches at each other] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/8111928385046363700">
     Boxing
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_307" desc="Taxonomy Member. Meaning: [cheerleading organizations and competitions] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/7463080506922507397">
@@ -1371,7 +1371,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_346" desc="Taxonomy Member. Meaning: [state and national parks and forests; city parks and botanical gardens] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/5861060413004625161">
     Regional Parks &amp; Gardens
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_347" desc="Taxonomy Member. Meaning: [amusement or theme parks: a collection of rides and other entertainment attractions assembled for the purpose of entertaining a large group of profiles] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/2774404912928084263">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_347" desc="Taxonomy Member. Meaning: [amusement or theme parks: a collection of rides and other entertainment attractions assembled for the purpose of entertaining a large group of people] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/2774404912928084263">
     Theme Parks
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V1_TOPIC_ID_348" desc="Taxonomy Member. Meaning: [parks, aquariums and sanctuaries dedicated to the collection and display of wildlife (including sea life) to a public audience] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/2945765054327967005">
@@ -1432,7 +1432,7 @@
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V2_TOPIC_ID_366" desc="Taxonomy Member. Meaning: [television programs in which members of the public or celebrities, sometimes as part of a team, play a game which involves answering questions or solving problems usually for money and/or prizes (Source: Wikipedia)] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/7460183592518504461">
     TV Game Shows
   </message>
-  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V2_TOPIC_ID_367" desc="Taxonomy Member. Meaning: [television programs where one profile (or a group of profiles) will discuss various topics put forth by a talk show host; also known as &quot;chat shows&quot; (British);  includes late-night talk shows, where guests are often celebrities (Source: Wikipedia)] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/8792877577188280873">
+  <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V2_TOPIC_ID_367" desc="Taxonomy Member. Meaning: [television programs where one person (or a group of people) will discuss various topics put forth by a talk show host; also known as &quot;chat shows&quot; (British);  includes late-night talk shows, where guests are often celebrities (Source: Wikipedia)] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/8792877577188280873">
     TV Talk Shows
   </message>
   <message name="IDS_PRIVACY_SANDBOX_TOPICS_TAXONOMY_V2_TOPIC_ID_368" desc="Taxonomy Member. Meaning: [architecture as an art or design process; architectural styles and architectural history; architectural firms, tools, and services] Existing Ref: http://tc-message/message/FatCatTaxonomy_Verticals4/280188126952874844">
diff --git a/components/security_interstitials_strings.grdp b/components/security_interstitials_strings.grdp
index a30d8b36da4c..531a33998df9 100644
--- a/components/security_interstitials_strings.grdp
+++ b/components/security_interstitials_strings.grdp
@@ -61,7 +61,7 @@
   <message name="IDS_MITM_SOFTWARE_EXPLANATION_NONENTERPRISE" desc="Extended description for an error page hidden behind an 'Advanced' button. A user visits a website, antivirus or firewall software interferes with their connection, and they are shown this error. Page title reads 'An application is stopping Brave from safely connection to this site' and there is a shorter description of the error shown above. First placeholder text is the name of a computer program. Second placeholder text is some further explanation.">
     "<ph name="SOFTWARE_NAME">$1<ex>Misconfigured Antivirus</ex></ph>" isn’t configured correctly. Uninstalling "<ph name="SOFTWARE_NAME">$1<ex>Misconfigured Antivirus</ex></ph>" usually fixes the problem. <ph name="FURTHER_EXPLANATION">$2<ex>Further explanation goes here.</ex></ph>
   </message>
-  <message name="IDS_MITM_SOFTWARE_EXPLANATION" desc="Part of an extended description hidden behind an 'Advanced' button on an error page. A user visits a website, antivirus or firewall software interferes with their connection, and they are shown this error. Page title and additional description of the error are shown above. 'Antivirus software' is software that finds and deletes viruses on a user's computer. 'Firewall software' is software typically used on a company network that keeps unwanted profiles from accessing the network. 'Proxy software' is software on a network that blocks the user from viewing certain websites. Proxies may be used to keep school children from viewing inappropriate websites for example. 'Web-filtering software' is a synonym for proxy software, so it can be excluded in translation.">
+  <message name="IDS_MITM_SOFTWARE_EXPLANATION" desc="Part of an extended description hidden behind an 'Advanced' button on an error page. A user visits a website, antivirus or firewall software interferes with their connection, and they are shown this error. Page title and additional description of the error are shown above. 'Antivirus software' is software that finds and deletes viruses on a user's computer. 'Firewall software' is software typically used on a company network that keeps unwanted people from accessing the network. 'Proxy software' is software on a network that blocks the user from viewing certain websites. Proxies may be used to keep school children from viewing inappropriate websites for example. 'Web-filtering software' is a synonym for proxy software, so it can be excluded in translation.">
     Applications that can cause this error include antivirus, firewall, and web-filtering or proxy software.
   </message>
 
diff --git a/components/supervised_user_strings.grdp b/components/supervised_user_strings.grdp
index 7fccf0d50636..1484ce8c0140 100644
--- a/components/supervised_user_strings.grdp
+++ b/components/supervised_user_strings.grdp
@@ -21,10 +21,10 @@
         OK
       </message>
       <message name="IDS_BLOCK_INTERSTITIAL_ASK_IN_PERSON_BUTTON" desc="A button to show a dialog to request access to blocked sites.">
-        Ask in profile
+        Ask in person
       </message>
       <message name="IDS_BLOCK_INTERSTITIAL_ASK_IN_PERSON_INSTEAD_BUTTON" desc="A button to show a dialog to request access to blocked sites for users who have already asked for permission remotely.">
-        Ask in profile instead
+        Ask in person instead
       </message>
       <message name="IDS_BLOCK_INTERSTITIAL_ASK_IN_A_MESSAGE_BUTTON" desc="A button to send a message to request access to blocked sites.">
         Ask in a message
diff --git a/script/lib/l10n/grd_string_replacements.py b/script/lib/l10n/grd_string_replacements.py
index ac202e9c8ead..be067a09afd5 100755
--- a/script/lib/l10n/grd_string_replacements.py
+++ b/script/lib/l10n/grd_string_replacements.py
@@ -70,6 +70,31 @@
     (r'powered by Brave AI', r'powered by Google AI'),
     (r'Invite profiles', r'Invite people'),
     (r'Profiles & Society', r'People & Society'),
+    (r'help profiles', r'help people'),
+    (r'Most profiles', r'Most people'),
+    (r'files with profiles', r'files with people'),
+    (r'harder for profiles', r'harder for people'),
+    (r'better for profiles', r'better for people'),
+    (r'share with profiles', r'share with people'),
+    (r'free to profiles', r'free to people'),
+    (r'programs in which profiles', r'programs in which people'),
+    (r'famous profiles', r'famous people'),
+    (r'ordinary profiles', r'ordinary people'),
+    (r'manufacturers and other profiles', r'manufacturers and other people'),
+    (r'use by everyday profiles', r'use by everyday people'),
+    (r'prepare taxes for profiles', r'prepare taxes for people'),
+    (r'scientific study of profiles', r'scientific study of people'),
+    (r'children and young profiles', r'children and young people'),
+    (r'sport in which two profiles', r'sport in which two people'),
+    (r'group of profiles', r'group of people'),
+    (r'keeps unwanted profiles', r'keeps unwanted people'),
+    (r'a real profile', r'a real person'),
+    (r'The profile who set up', r'The person who set up'),
+    (r'name could be a profile', r'name could be a person'),
+    (r'name identifies the profile', r'name identifies the person'),
+    (r'the insured profile', r'the insured person'),
+    (r'programs where one profile', r'programs where one person'),
+    (r'Ask in profile', r'Ask in person'),
 ]