Use US spelling (#1245)

austinpray-mixpanel · web-flow · commit 956c279d160d · 2024-07-23T14:05:10.000-07:00
diff --git a/pages/docs/boards/advanced.mdx b/pages/docs/boards/advanced.mdx
@@ -125,7 +125,7 @@ For example: a join membership club event happened 100 times yesterday, but 0 so
 Reports are always saved to boards. Previously, reports were separately saved and added to boards. In boards now, when you save a report, you'll be prompted to save it to a specific board. In essence, the board now acts as a folder, with many potential purposes, including:
 
 - A centralized place to track numerous metrics related to a product launch
-- A chain of analyses digging into a particular behaviour or issue
+- A chain of analyses digging into a particular behavior or issue
 - A set of draft reports you're working on
 
 This will make it easy to keep reports organized, and reduce time wasted recreating the same reports again and again.
diff --git a/pages/docs/cohort-sync/overview.md b/pages/docs/cohort-sync/overview.md
@@ -17,7 +17,7 @@ $email
 $phone
 ```
 
-If these properties are not present in your project, users might not be matched in the systems. If an integration partner doesn't use a property to match, it is dropped before ingestion. Please refer to the individual Cohort Sync Help Center pages for the behaviour for specific partners.
+If these properties are not present in your project, users might not be matched in the systems. If an integration partner doesn't use a property to match, it is dropped before ingestion. Please refer to the individual Cohort Sync Help Center pages for the behavior for specific partners.
 
 The email address and phone number properties will only show in the manual CSV exports for Google Ads and Facebook integrations.
 
diff --git a/pages/docs/data-structure/property-reference.md b/pages/docs/data-structure/property-reference.md
@@ -9,7 +9,7 @@ Mixpanel has many Properties defined in its Data Model.
 | [Event Properties](/docs/data-structure/events-and-properties) | Event Properties describes the events that are tracked within your product. |
 | [Super Properties](/docs/tracking-methods/sdks/javascript#super-properties) | Super Properties are a logical term for global Event Properties that, after registration, are saved into the end user's device, and appended to every event from that device until persistence is cleared. This logical term is mostly applicable to our client-side libraries. |
 | [User Profile Properties](/docs/data-structure/user-profiles) | User Profile Properties describe your users (they typically store current demographical information). User profiles are joined to events based on [Distinct ID](/docs/tracking-methods/identifying-users#what-is-distinct-id). |
-| [Group Profile Properties](/docs/data-structure/advanced/group-analytics#group-profiles) | Group Profile Properties describe group level information (similar to User Profiles Properties at user level). With Mixpanel’s [Group Analytics](/docs/data-structure/advanced/group-analytics), multiple users can be grouped and behavioural data analysed at a customised group level (such as company, account). Group profiles are joined to events on your chosen [Group Key](/docs/data-structure/advanced/group-analytics#group-keys-tracked-as-event-properties). |
+| [Group Profile Properties](/docs/data-structure/advanced/group-analytics#group-profiles) | Group Profile Properties describe group level information (similar to User Profiles Properties at user level). With Mixpanel’s [Group Analytics](/docs/data-structure/advanced/group-analytics), multiple users can be grouped and behavioral data analysed at a customised group level (such as company, account). Group profiles are joined to events on your chosen [Group Key](/docs/data-structure/advanced/group-analytics#group-keys-tracked-as-event-properties). |
 | [Lookup Tables](/docs/data-structure/lookup-tables) | Lookup Tables allow you to dynamically extend additional properties mapped to an existing Event or User Property. For example, if you create a lookup table for "Songs" (that contains additional properties like `hash_tags`, `top_10`, `all_time_favorite`) and map it to an event property `song_id`; you can use these additional properties when doing filtering or breakdowns for events that has `song_id` as an event property. |
 | [Default Properties](/docs/data-structure/property-reference#default-properties) | Default Properties (for Events and User Profiles) are collected and populated with values automatically in Mixpanel. This can happen upon data ingestion or when using certain Mixpanel client-side SDKs. Typically, they have a dollar sign ($) or “mp\_” as prefix to distinguish them from normal properties. |
 | Reserved Properties | Mixpanel reserves certain property names (for [Events](/docs/data-structure/events-and-properties#reserved-event-properties) and [User Profiles](/docs/data-structure/user-profiles#reserved-user-properties)) for special use cases, and these may or may not be automatically populated with values. The purpose of such Reserved Properties are for processing (ie event time stamping) or for specific system features (eg: cohort exports). Examples: `time`, `$email`, `$phone`, `$name`, `$created`. |
@@ -152,7 +152,7 @@ Mixpanel supports five data types for properties: String, Numeric, Boolean, Date
 
 ### List
 
-- A list of values as a JSON array e.g Favourite Genres = ["Folk","Alternative"] or Favourite Numbers = [1,5,10.0]
+- A list of values as a JSON array e.g Favorite Genres = ["Folk","Alternative"] or Favorite Numbers = [1,5,10.0]
 - Limits of a List property: Event Property = 8KB, User Profile Property = 256KB
 - Each item in a list would be further limited by their data type's limits; example: a list of strings would be limited by 255 bytes per string. Also refer to [List of Objects](/docs/data-structure/property-reference#list-of-objects) covered below.
 - Mixpanel lists are not ordered (i.e. position of values in a list are not significant in Mixpanel reports) and are useful for grouping or analysing similar values across events. Read more details on [List Property Support](/docs/features/advanced#list-property-support) in reports.
diff --git a/pages/docs/data-structure/user-profiles.md b/pages/docs/data-structure/user-profiles.md
@@ -193,4 +193,4 @@ Mixpanel is 100% compatible with Segment; just follow Segment's best practices.
 User Profiles are mutable, which means new ones can be added and existing ones can be updated or deleted. Mixpanel automatically maintains an "Updated at" (`$last_seen`) property, which contains the last timestamp that a user profile was updated. "Updated at" does not change if the user does a new event; it only changes when the profile is updated. "Updated at" also does not change for profile updates made via the UI or if the `$ignore_time` parameter is set to `true` (see example from [PHP SDK](/docs/tracking-methods/sdks/php#setting-profile-properties)).
 
 ### Where can I learn more about Group Profiles?
-You can get an overview of how Group Profiles relate to Mixpanel's Data Model under the section [Group Level Behaviours and Demographics](/docs/tutorials/plan/tracking-strategy#group-level-behaviours-and-demographics) in our tutorials. A more detailed explanation of [Group Profiles](/docs/data-structure/advanced/group-analytics#group-profiles) is documented under our [Group Analytics](/docs/data-structure/advanced/group-analytics) page.
+You can get an overview of how Group Profiles relate to Mixpanel's Data Model under the section [Group Level Behaviors and Demographics](/docs/tutorials/plan/tracking-strategy#group-level-behaviors-and-demographics) in our tutorials. A more detailed explanation of [Group Profiles](/docs/data-structure/advanced/group-analytics#group-profiles) is documented under our [Group Analytics](/docs/data-structure/advanced/group-analytics) page.
diff --git a/pages/docs/migration/flurry.md b/pages/docs/migration/flurry.md
@@ -56,7 +56,7 @@ We also support additional data for extending your use cases with Mixpanel:
 
 ### ID Management Differences
 
-Mixpanel supports stitching user behaviour pre-login (e.g. traffic from your website, docs, blog) and post-login (once the user has signed up). This helps answer questions like:
+Mixpanel supports stitching user behavior pre-login (e.g. traffic from your website, docs, blog) and post-login (once the user has signed up). This helps answer questions like:
 
 - What % of site visitors end signing up?
 - How much of my Purchase revenue can I attribute to a particular campaign?
@@ -66,7 +66,7 @@ This system is called [ID Merge](/docs/tracking-methods/id-management/identifyin
 
 ![image](/simplified_id_merge_example.png)
 
-Anonymous users on Flurry are also identified based on their device IDs. Similarly, users can be identified using the Flurry.setUserId method to capture the user ID. The key difference here is though: Flurry does not support the stitching of user behaviour pre-login and post. That means in the Charlie example above, we will not be able to match Charlie across the Android or iOS devices. [User IDs are set as user properties only in Flurry on the device level](https://developer.yahoo.com/flurry/docs/analytics/rdd/), and [not applied to multiple devices](https://developer.yahoo.com/flurry/docs/analytics/userproperties/#:~:text=Flurry%20User%20Properties%20are%20captured,devices%20with%20the%20same%20UserID). As a consequence, it can be difficult to do user data reconciliation between Mixpanel and Flurry because users may be overstated on Flurry. 
+Anonymous users on Flurry are also identified based on their device IDs. Similarly, users can be identified using the Flurry.setUserId method to capture the user ID. The key difference here is though: Flurry does not support the stitching of user behavior pre-login and post. That means in the Charlie example above, we will not be able to match Charlie across the Android or iOS devices. [User IDs are set as user properties only in Flurry on the device level](https://developer.yahoo.com/flurry/docs/analytics/rdd/), and [not applied to multiple devices](https://developer.yahoo.com/flurry/docs/analytics/userproperties/#:~:text=Flurry%20User%20Properties%20are%20captured,devices%20with%20the%20same%20UserID). As a consequence, it can be difficult to do user data reconciliation between Mixpanel and Flurry because users may be overstated on Flurry. 
 
 ### Data Capture Differences
 
diff --git a/pages/guides/beyond-onboarding.mdx b/pages/guides/beyond-onboarding.mdx
@@ -13,7 +13,7 @@ Congratulations on completing the onboarding tutorials, you are now equipped wit
       - Conducting quality and audit checks to ensure data governance before going live
 <br />
 - [x] Launch your new tracking, by...
-      - Deploying your new tracking codes to gather user behaviours
+      - Deploying your new tracking codes to gather user behaviors
       - Building new dashboards, reports, and user cohorts to track new metrics and KPIs
 
 ## Keeping Up with Mixpanel
diff --git a/pages/guides/implement/establish-governance.mdx b/pages/guides/implement/establish-governance.mdx
@@ -1,6 +1,6 @@
 # Establish Data Governance
 
-Implementing your tracking plan by sending data into Mixpanel and conducting Quality Assurance test is your first step to getting insights about your users' behaviours. Keeping your data in production clean, concise, and consistent as you add more tracking, requires you to establish a data governance framework.
+Implementing your tracking plan by sending data into Mixpanel and conducting Quality Assurance test is your first step to getting insights about your users' behaviors. Keeping your data in production clean, concise, and consistent as you add more tracking, requires you to establish a data governance framework.
 
 Data governance involves key data stakeholders establishing a methodology, process, or strategy to ensure Mixpanel implementation continues to be consistent, accurate, and trustworthy. It need not be complex, but should focus on the following principles:
 
diff --git a/pages/guides/launch/analyze-conversions.mdx b/pages/guides/launch/analyze-conversions.mdx
@@ -21,7 +21,7 @@ Go beyond looking at overall conversion, view conversion trend over time, distri
 </p>
 
 ## Viewing as a Flow
-Oftentimes, knowing what the conversion is or how it has changed over time is not actionable in of itself. Beyond creating cohorts on users who have dropped off to send them downstream to CRM tools for re-engagement, what marketers and product managers typically want to know is, where precisely did people drop off? What are the typical user flows or behaviour that causes users to drop off? Learn more about it [here](/docs/reports/funnels#view-as-flow).
+Oftentimes, knowing what the conversion is or how it has changed over time is not actionable in of itself. Beyond creating cohorts on users who have dropped off to send them downstream to CRM tools for re-engagement, what marketers and product managers typically want to know is, where precisely did people drop off? What are the typical user flows or behavior that causes users to drop off? Learn more about it [here](/docs/reports/funnels#view-as-flow).
 
 
 
diff --git a/pages/guides/launch/discover-insights.mdx b/pages/guides/launch/discover-insights.mdx
@@ -1,6 +1,6 @@
 # Discover Insights
 
-[Insights](/docs/reports/insights) is a powerful and flexible reporting tool that allows you to easily slice and dice user behaviour on your platforms. You can analyze events, cohorts and user profiles, and display the data in a wide variety of chart types.
+[Insights](/docs/reports/insights) is a powerful and flexible reporting tool that allows you to easily slice and dice user behavior on your platforms. You can analyze events, cohorts and user profiles, and display the data in a wide variety of chart types.
 
 <br />
 <p style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
@@ -44,12 +44,12 @@ The following video looks at how you can leverage formulas, custom events and pr
   <iframe src="https://www.youtube.com/embed/jQ2gJsb83E8?rel=0" title="Insights Formulas, Custom Events and Properties" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowFullScreen style={{position: 'absolute', top: 0, left: 0, width: '100%', height: '100%'}}></iframe>
 </p>
 
-## Behavioural Breakdowns
+## Behavioral Breakdowns
 Other more advanced questions that Insights can help answer include: how you can segment your users not just by who they are (i.e. user attributes), but what they do. This is a common ask from product managers - to be able to understand for example the number of times users typically view a product before purchasing. Or more simply, you might be interested in looking at what the distribution of your cart value per user is, or the distinct number of days a month that a user might come to your site to make a purchase. The following video walks through some of these examples:
 
 <br />
 <p style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
-  <iframe src="https://www.youtube.com/embed/v_SKV3080yg?rel=0" title="Insights Behavioural Segmentation" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowFullScreen style={{position: 'absolute', top: 0, left: 0, width: '100%', height: '100%'}}></iframe>
+  <iframe src="https://www.youtube.com/embed/v_SKV3080yg?rel=0" title="Insights Behavioral Segmentation" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowFullScreen style={{position: 'absolute', top: 0, left: 0, width: '100%', height: '100%'}}></iframe>
 </p>
 
 ## Creating Alerts
diff --git a/pages/guides/plan/setup.mdx b/pages/guides/plan/setup.mdx
@@ -1,6 +1,6 @@
 # Overview
 
-Before you start sending data into your Mixpanel project, it's important to take some time to setup your Mixpanel instance and plan out what actions or behaviours you want to track, in order to achieve your product or business goals.
+Before you start sending data into your Mixpanel project, it's important to take some time to setup your Mixpanel instance and plan out what actions or behaviors you want to track, in order to achieve your product or business goals.
 
 <br />
 - [x] [Setup](/docs/tutorials/plan/setup#setting-up-mixpanel) *(for Organization Owners and Admins)* - takes you through how you should go about setting up your Mixpanel Organization and the underlying Projects. 
@@ -43,7 +43,7 @@ We recommend using the **Simplied API** option as it is a straightforward simple
 
 ## Development and Production Project Setup
 
-We recommend that you minimally setup two Mixpanel projects, one for **Development** data and another for **Production** data. This is to ensure that you keep development test data separate from actual live user behavioural data. Read more details about [Developer Environments](/docs/best-practices/developer-environments).
+We recommend that you minimally setup two Mixpanel projects, one for **Development** data and another for **Production** data. This is to ensure that you keep development test data separate from actual live user behavioral data. Read more details about [Developer Environments](/docs/best-practices/developer-environments).
 
 ![image](/tutorials/create-projects.png "Create Projects")
 
@@ -62,7 +62,7 @@ By default, all data in a Mixpanel project is accessible to all your users in th
 
 ### Data Views
 
-If for instance, you want to provide the web team only with access to web events, and the iOS and Android teams access to their specific events, but still want the business teams to have a single customer view of the customer's behaviour across the different platforms. [Data Views](/docs/data-governance/data-views-and-classification) can help with this. It enables Project Owners and Admins to manage data access for a group of users within a single Mixpanel project for privacy and productivity purposes. 
+If for instance, you want to provide the web team only with access to web events, and the iOS and Android teams access to their specific events, but still want the business teams to have a single customer view of the customer's behavior across the different platforms. [Data Views](/docs/data-governance/data-views-and-classification) can help with this. It enables Project Owners and Admins to manage data access for a group of users within a single Mixpanel project for privacy and productivity purposes. 
 
 ![image](/tutorials/data-views-filter.png "Data Views Filter")
 
diff --git a/pages/guides/plan/tracking-strategy.mdx b/pages/guides/plan/tracking-strategy.mdx
diff --git a/reference/Mixpanel APIs/authentication/project-token.md b/reference/Mixpanel APIs/authentication/project-token.md
