Revert "BD-3237 pt 1 glossary audit (through end user)"

CODE_OF_CONDUCT.md

@@ -47,7 +47,7 @@ threatening, offensive, or harmful.
 
 This Code of Conduct applies both within project spaces and in public spaces
 when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project email
+representing a project or community include using an official project e-mail
 address, posting via an official social media account, or acting as an appointed
 representative at an online or offline event. Representation of a project may be
 further defined and clarified by project maintainers.

_config.yml

@@ -3,8 +3,8 @@ title: Braze Documentation
 email: success@braze.com
 description: >- # this means to ignore newlines until "baseurl:"
   Welcome to Braze Documentation. Braze provides a comprehensive user engagement solution for your mobile apps.
-baseurl: "/docs" # the subpath of your site, such as /blog
-homeurl: "https://www.braze.com" # the base hostname & protocol for your site, such as http://example.com
+baseurl: "/docs" # the subpath of your site, e.g., /blog
+homeurl: "https://www.braze.com" # the base hostname & protocol for your site, e.g., http://example.com
 twitter_username: Braze
 github_username: braze-inc
 

_docs/_api/objects_filters/messaging/android_object.md

@@ -35,7 +35,7 @@ You must include an Android push object in `messages` if you want users you have
    "push_icon_image_url": (optional, string) an image URL for the large icon,
    "accent_color": (optional, integer) accent color to be applied by the standard Style templates when presenting this notification, an RGB integer value,
    "send_to_most_recent_device_only": (optional, boolean) defaults to false, if set to true, Braze will only send this push to a user's most recently used Android device, rather than all eligible Android devices,
-   "buttons" : (optional, array of Android Push action button Objects) push action buttons to display
+   "buttons" : (optional, array of Android Push Action Button Objects) push action buttons to display
    "conversation_data" : (optional, Android Conversation Push Object) the data to be displayed via Conversation Push.
 }
 ```

_docs/_api/objects_filters/messaging/apple_object.md

@@ -35,7 +35,7 @@ description: "This reference article lists and explains the different Apple obje
    "mutable_content": (optional, boolean) if true, Braze will add the mutable-content flag to the payload and set it to 1. The mutable-content flag is automatically set to 1 when sending a rich notification, regardless of the value of this parameter.
    "send_to_most_recent_device_only": (optional, boolean) defaults to false, if set to true, Braze will only send this push to a user's most recently used iOS device, rather than all eligible iOS devices,
    "category": (optional, string) the iOS notification category identifier for displaying push action buttons,
-   "buttons" : (optional, array of Apple Push action button Objects) push action buttons to display
+   "buttons" : (optional, array of Apple Push Action Button Objects) push action buttons to display
 }
 ```
 

_docs/_api/objects_filters/messaging/web_objects.md

@@ -26,7 +26,7 @@ description: "This reference article lists and explains the different web object
    "require_interaction": (optional, boolean) whether to require the user to dismiss the notification, supported on Mac Chrome,
    "time_to_live": (optional, integer (seconds)),
    "send_to_most_recent_device_only" : (optional, boolean) defaults to false, if set to true, Braze will only send this push to a user's most recently used browser, rather than all eligibles browsers,
-   "buttons" : (optional, array of Web Push action button Objects) push action buttons to display
+   "buttons" : (optional, array of Web Push Action Button Objects) push action buttons to display
 }
 ```
 

_docs/_contributing/content_management.md

@@ -98,7 +98,7 @@ Replace the following.
 
 | Placeholder | Description                                                                                                             |
 |-------------|-------------------------------------------------------------------------------------------------------------------------|
-| `ALT_TEXT`  | The alt text for the image. This is required to make sure Braze Docs is equally accessible for those using screen readers. |
+| `ALT_TEXT`  | The alt text for the image. This is required to ensure Braze Docs is equally accessible for those using screen readers. |
 | `IMAGE`     | The relative path to your image starting from the `img` directory.                                                      |
 {: .reset-td-br-1 .reset-td-br-2}
 

_docs/_contributing/content_management/images.md

@@ -62,7 +62,7 @@ Replace the following:
 
 | Placeholder | Description                                                                                                             |
 |-------------|-------------------------------------------------------------------------------------------------------------------------|
-| `ALT_TEXT`  | The alt text for the image. This is required to make sure Braze Docs is equally accessible for those using screen readers. |
+| `ALT_TEXT`  | The alt text for the image. This is required to ensure Braze Docs is equally accessible for those using screen readers. |
 | `IMAGE`     | The relative path to your image starting from the `img` directory.                                                      |
 {: .reset-td-br-1 .reset-td-br-2}
 

_docs/_contributing/yaml_front_matter/metadata.md

@@ -34,7 +34,7 @@ Replace the following:
 
 ### Article title
 
-The `article_title` key is used to set the page title for online search results and the user's browser tab. This key accepts any `string` value. For naming conventions, see the [Braze Docs Style Guide]({{site.baseurl}}/contributing/style_guide/).
+The `article_title` key is used to set the page title for online search results and the end-user's browser tab. This key accepts any `string` value. For naming conventions, see the [Braze Docs Style Guide]({{site.baseurl}}/contributing/style_guide/).
 
 {% tabs local %}
 {% tab usage example %}

_docs/_contributing/your_first_contribution.md

@@ -189,7 +189,7 @@ These comments will guide you through your PR description. When you're finished,
 
 ## Step 4: Review your work
 
-Make sure your content follows the [Braze Docs Style Guide]({{sitebase.url}}/contributing/style_guide/) by reviewing your work in a site preview. If you need to make additional changes, see [Make additional changes](#step-6-make-additional-changes-optional). Otherwise, you can [request a review](#step-5-request-a-review) from the Braze Docs team.
+Ensure your content follows the [Braze Docs Style Guide]({{sitebase.url}}/contributing/style_guide/) by reviewing your work in a site preview. If you need to make additional changes, see [Make additional changes](#step-6-make-additional-changes-optional). Otherwise, you can [request a review](#step-5-request-a-review) from the Braze Docs team.
 
 {% tabs %}
 {% tab github %}

_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/ios_sdk_integration.md

@@ -427,7 +427,7 @@ Proceed to compile your code and run your application.<br><br>Try identifying us
 ### Log analytics
 
 {% tabs local %}
-{% tab Step 1: Custom events %}
+{% tab Step 1: Custom Events %}
 
 ##### Create log custom event method
 

_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/implementation_guide.md

@@ -160,7 +160,7 @@ To set up an information capture capable push in the dashboard, you must registe
 
 Each action button is uniquely identified. The code checks if your response identifier is equal to the `actionIndentifier`, and if so, knows that the user clicked the action button.
 
-**Handling Push Notification action button responses**<br>
+**Handling Push Notification Action Button Responses**<br>
 
 {% tabs %}
 {% tab Swift %}
@@ -227,7 +227,7 @@ Add a capability `App Groups`. If you haven't had any app group in your app, go
 The following code snippets are a helpful reference on how to save and send custom events, custom attributes, and user attributes. This guide will be speaking in terms of UserDefaults, but the code representation will be in the form of a helper file  `RemoteStorage`. There also exist additional helper files `UserAttributes` and `EventName Dictionary` that are used when sending and saving user attributes. All helper files can be found at the end of this guide.
 
 {% tabs local %}
-{% tab Custom events %}
+{% tab Custom Events %}
 
 ##### Saving custom events
 
@@ -368,7 +368,7 @@ func logPendingCustomEventsIfNecessary() {
 {% endsubtab %}
 {% endsubtabs %}
 {% endtab %}
-{% tab Custom attributes %}
+{% tab Custom Attributes %}
 
 ##### Saving custom attributes
 
@@ -485,7 +485,7 @@ func setCustomAttributesWith(keysAndValues: [String: Any]) {
 {% endsubtab %}
 {% endsubtabs %}
 {% endtab %}
-{% tab User attributes %}
+{% tab User Attributes %}
 
 ##### Saving user attributes
 
@@ -611,7 +611,7 @@ func logPendingUserAttributesIfNecessary() {
 {% endsubtab %}
 {% endsubtabs %}
 {% endtab %}
-{% tab Helper files %}
+{% tab Helper Files %}
 
 ##### Helper files
 
@@ -797,7 +797,7 @@ extension UserAttribute: Codable {
 {% endsubtab %}
 {% endsubtabs %}
 {% enddetails %}
-{% details EventName dictionary helper file %}
+{% details EventName Dictionary Helper File %}
 {% subtabs global %}
 {% subtab Swift %}
 ```swift

_docs/_developer_guide/platform_integration_guides/swift/archived_updates/ios_14.md

@@ -82,7 +82,7 @@ Starting in iOS 14.5, a new permission prompt (launched by the new `AppTrackingT
 If a user does not accept the prompt, or if you do not upgrade to Xcode 12's `AppTrackingTransparency` framework, then a blank IDFA value (`00000000-0000-0000-0000-000000000000`) will be returned, and your app will not be allowed to prompt the user again.
 
 {% alert important %}
-These IDFA updates will take effect after your users upgrade their device to iOS 14.5. Ensure your app uses the new `AppTransparencyFramework` with Xcode 12 if you plan to collect IDFA.
+These IDFA updates will take effect after end-users upgrade their device to iOS 14.5. Ensure your app uses the new `AppTransparencyFramework` with Xcode 12 if you plan to collect IDFA.
 {% endalert %}
 
 #### Changes to Braze IDFA collection

_docs/_developer_guide/platform_integration_guides/swift/archived_updates/ios_17.md

@@ -31,7 +31,7 @@ Apple announced its commitment to expand the scope of [Ad Tracking Transparency
 
 #### Privacy manifests
 
-Apple now requires a privacy manifest file that describes the reason your app and third-party SDKs collect data, along with their data-collection methods. Starting with iOS 17.2, Apple will block all declared tracking endpoints in your app until your users accept the ATT prompt.
+Apple now requires a privacy manifest file that describes the reason your app and third-party SDKs collect data, along with their data-collection methods. Starting with iOS 17.2, Apple will block all declared tracking endpoints in your app until the end-user accepts the ATT prompt.
 
 Braze has released our own privacy manifest, along with new flexible APIs that automatically reroute declared tracking data to dedicated `-tracking` endpoints. For more information, see [Braze's privacy manifest]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest).
 

_docs/_developer_guide/platform_integration_guides/swift/push_notifications/implementation_guide.md

@@ -165,7 +165,7 @@ As seen in the example, you may also include an image in your push notification.
 
 Each action button is uniquely identified. The code checks if your response identifier is equal to the `actionIndentifier`, and if so, knows that the user clicked the action button.
 
-**Handling Push Notification action button responses**<br>
+**Handling Push Notification Action Button Responses**<br>
 
 {% tabs %}
 {% tab Swift %}
@@ -228,7 +228,7 @@ In Xcode, add the `App Groups` capability. If you haven’t had any workspaces i
 The following code snippets are a helpful reference on how to save and send custom events, custom attributes, and user attributes. This guide will be speaking in terms of `UserDefaults`, but the code representation will be in the form of the helper file `RemoteStorage`. There are additional helper files, `UserAttributes` and `EventName Dictionary`, that are used when sending and saving user attributes.
 
 {% tabs local %}
-{% tab Custom events %}
+{% tab Custom Events %}
 
 ##### Saving custom events
 
@@ -369,7 +369,7 @@ func logPendingCustomEventsIfNecessary() {
 {% endsubtab %}
 {% endsubtabs %}
 {% endtab %}
-{% tab Custom attributes %}
+{% tab Custom Attributes %}
 
 ##### Saving custom attributes
 
@@ -486,7 +486,7 @@ func setCustomAttributesWith(keysAndValues: [String: Any]) {
 {% endsubtab %}
 {% endsubtabs %}
 {% endtab %}
-{% tab User attributes %}
+{% tab User Attributes %}
 
 ##### Saving user attributes
 
@@ -798,7 +798,7 @@ extension UserAttribute: Codable {
 {% endsubtab %}
 {% endsubtabs %}
 {% enddetails %}
-{% details EventName dictionary helper file %}
+{% details EventName Dictionary Helper File %}
 {% subtabs global %}
 {% subtab Swift %}
 ```swift

_docs/_developer_guide/platform_wide/getting_started/architecture_overview.md

@@ -98,7 +98,7 @@ The [Braze SDK][5] powers additional messaging channels: push, in-app messages,
 ![][13]
 
 ## Exporting data
-Critically, all your users' interactions with Braze are tracked so you can measure your engagement and outreach. And after Braze has aggregated your data from all these sources, it can be exported back to your tech stack using a variety of tools, closing the loop.
+Critically, all end-user interactions with Braze are tracked so you can measure your engagement and outreach. And once Braze has aggregated your data from all these sources, it can be exported back to your tech stack using a variety of tools, closing the loop.
 
 ### Currents
 [Currents][14] is an optional Braze add-on that provides a granular streaming export that continuously feeds other destinations of your stack. Currents is a per user per event raw data feed that exports data every five minutes, or every 15,000 events, whichever comes first. Examples of some downstream destinations for Currents would be Segment, S3, Redshift and Mixpanel, among others. 

_docs/_developer_guide/platform_wide/sdk_authentication.md

@@ -449,7 +449,7 @@ Once disabled, any pending failed SDK requests will eventually be retried by the
 
 #### Why does this feature use public/private keys instead of shared secrets? {#faq-shared-secrets}
 
-When using shared secrets, anyone with access to that shared secret, such as the Braze dashboard page, would be able to generate tokens and impersonate your users.
+When using shared secrets, anyone with access to that shared secret, such as the Braze dashboard page, would be able to generate tokens and impersonate your end-users.
 
 Instead, we use public/private keys so that not even Braze Employees (let alone your dashboard users) have access to your private keys.
 

_docs/_docs_pages/cla.md

@@ -21,7 +21,7 @@ In consideration of the mutual covenants and agreements contained herein and oth
 
 3. **Originality of Work.** You represent that each of Your Submissions is entirely Your original work. Should You wish to Submit materials that are not Your original work, You may Submit them separately to the Project if (a) You retain all copyright and license information that was in the materials as You received them, (b) in the description accompanying Your Submission, You include the phrase "Submission containing materials of a third party" followed by the name(s) of the third party and any licenses or other restrictions of which You are aware, and (c) You follow any other instructions in the Project's written guidelines concerning Submissions.<br><br>
 
-4. **Your Employer.** References to "employer" in this Agreement include Your employer or anyone else for whom You are acting in making Your Submission, e.g., a contractor, vendor, or agent. If Your Submission is made in the course of Your work for an employer or Your employer has intellectual property rights in Your Submission by contract or applicable law, You must secure permission from Your employer to make the Submission before signing this Agreement. In that case, the term "You" in this Agreement will refer to You and the employer collectively. If You change employers in the future and desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement and secure permission from the new employer before Submitting those Submissions.<br><br>
+4. **Your Employer.** References to "employer" in this Agreement include Your employer or anyone else for whom You are acting in making Your Submission, e.g., as a contractor, vendor, or agent. If Your Submission is made in the course of Your work for an employer or Your employer has intellectual property rights in Your Submission by contract or applicable law, You must secure permission from Your employer to make the Submission before signing this Agreement. In that case, the term "You" in this Agreement will refer to You and the employer collectively. If You change employers in the future and desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement and secure permission from the new employer before Submitting those Submissions.<br><br>
 
 5. **Licenses.**<br><br>
 **a. Copyright License.** You grant Braze, and those who receive the Submission directly or indirectly from Braze, a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable license in the Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third parties.<br><br>

_docs/_help/release_notes/2024/6_25_24.md

@@ -37,7 +37,7 @@ Migrate your WhatsApp phone number between WhatsApp Business Accounts by using M
 
 {% multi_lang_include release_type.md release="General availability" %}
 
-The new **Engagement by Device** report provides a breakdown of what devices your users are using to engage with your email. This data tracks email engagement across mobile, desktop, tablet, and other device types. Learn more about [the report and the email performance dashboard]({{site.baseurl}}/user_guide/data_and_analytics/analytics/email_performance_dashboard).
+The new **Engagement by Device** report provides a breakdown of what devices your users are using to engage with your email. This data tracks email engagement across mobile, desktop, tablet, and other device types. Learn more about [the report and the Email Performance Dashboard]({{site.baseurl}}/user_guide/data_and_analytics/analytics/email_performance_dashboard).
 
 ### WhatsApp and SMS Liquid properties in Canvas flow
 

_docs/_hidden/compliance/sms_channel.md

@@ -19,7 +19,7 @@ The following additional terms apply in relation to Customer’s use of the SMS
 
 **"Aggregators"** shall mean third-party intermediaries that transmit SMS/MMS Messages between SMS/MMS Providers and Carriers.
 
-**"Carriers"** shall mean third-party wireless service providers (such as T-Mobile, AT&T, and similar).
+**"Carriers"** shall mean third-party wireless service providers (e.g., T-Mobile, AT&T, etc.).
 
 **"SMS/MMS Providers"** shall mean Braze Sub-processors used in the transmission of SMS/MMS Messages, as identified at [www.braze.com/subprocessors](http://www.braze.com/subprocessors).