reference/ spelling fixes (part 5/n) (#1435)

Author: austinpray-mixpanel

cspell.json

@@ -25,18 +25,23 @@
     "addatatable",
     "Authy",
     "autoprovisioning",
+    "Bamboleo",
     "Bucketize",
     "callout",
     "Cartfile",
     "CCPA",
     "Clickstream",
     "cloudimport",
+    "clsx",
     "Cocoapods",
     "cohorting",
     "concat",
+    "Dagster",
+    "datetimes",
     "Discoverability",
     "docsearch",
     "DWCK",
+    "expirable",
     "falsey",
     "Figjam",
     "Freshpaint",
@@ -46,10 +51,12 @@
     "IDFA",
     "iframe",
     "Isha",
+    "Jayaram",
     "Kapa",
     "Leanplum",
     "Marketo",
     "mixpanelapi",
+    "monoschema",
     "mozallowfullscreen",
     "mparticle",
     "mpcehash",
@@ -61,13 +68,16 @@
     "objc",
     "Onelogin",
     "onesignal",
+    "openapi",
     "pageview",
     "Podfile",
     "postback",
     "projectoken",
     "projecttoken",
     "pubspec",
     "quickstart",
+    "rdme",
+    "redocly",
     "Referer",
     "retryable",
     "ROAS",
@@ -82,12 +92,14 @@
     "Signups",
     "stddev",
     "struct",
+    "tailwindcss",
     "Tealium",
     "Textareas",
     "typeof",
     "uaparser",
     "unitypackage",
     "unmerge",
+    "Unsets",
     "unverify",
     "urlencode",
     "urllib",
@@ -97,6 +109,7 @@
     "waitlist",
     "webkitallowfullscreen",
     "xcworkspace",
+    "XPUT",
     "yourfullname"
   ]
 }

reference/Mixpanel APIs/authentication/request-signature.md

@@ -27,7 +27,7 @@ In order to generate a request signature you will need the following information
 
 Calculating the signature is done in parts:
 1) Alphabetically sort all parameters being used in the request. This excludes your api_secret
-2) alphabetically sorted order, concatenate the parameter and parameter value joined by an equal sign. For example: `param1=paramvalue1param2=paramvalue2` 
+2) alphabetically sorted order, concatenate the parameter and parameter value joined by an equal sign. For example: `param1=value1param2=value2` 
 2) append the api_secret to the string of concatenated parameters.
 3) md5 hash the final string
 
@@ -67,7 +67,7 @@ Request with Signature
 https://mixpanel.com/api/2.0/events/
 		&interval=7
 		&expire=1275624968
-		&api_key=f0aa34668dsadsa231
+		&api_key=xxxxx
 		&type=average
 		&event=%5B%22splash+features<%22%2C+%22account-page%22%5D
 		&unit=day

reference/Mixpanel APIs/rate-limits.md

@@ -6,7 +6,7 @@ categorySlug: "mixpanel-apis"
 createdAt: "2023-10-31T15:28:39.814Z"
 updatedAt: "2023-10-31T15:38:48.152Z"
 ---
-We enforce a rate limit on our API to ensure the integrity of our system as well as prevent a single project from monopolizing the avaialble resources for other projects. Getting a 429 response code from our API means that you have reached our rate-limit.
+We enforce a rate limit on our API to ensure the integrity of our system as well as prevent a single project from monopolizing the available resources for other projects. Getting a 429 response code from our API means that you have reached our rate-limit.
 
 The rate limits are as follows:
 

reference/Mixpanel APIs/segmentation-expressions.md

@@ -52,7 +52,7 @@ The power of segmentation comes from the ability to define custom expressions ba
 [/block]
 ## Typecast Operations
 
-Internally, all properties of events have a type. This type is determined when we parse the event sent to us into a JSON object. Currently, there are three types, string, number, and boolean, which may be specified directly. A property may also have the values null and undefined, which are only handled internally. The default type is string. If you wish to treat an expression as another type, you may use the typecast operators to cast a property to a different type. For example, if `properties["signed up"]` has values of `"true"` and `"false"` as strings, and you wish to intercode them as booleans, you may cast them by using the `boolean() typecast function: boolean(properties["signed up"])`.
+Internally, all properties of events have a type. This type is determined when we parse the event sent to us into a JSON object. Currently, there are three types, string, number, and boolean, which may be specified directly. A property may also have the values null and undefined, which are only handled internally. The default type is string. If you wish to treat an expression as another type, you may use the typecast operators to cast a property to a different type. For example, if `properties["signed up"]` has values of `"true"` and `"false"` as strings, and you wish to encode them as booleans, you may cast them by using the `boolean() typecast function: boolean(properties["signed up"])`.
 
 The typecasting rules are described below.
 

reference/Query API/event-breakdown/query-event-properties.md

@@ -1,5 +1,5 @@
 ---
-title: "Aggregrated Event Property Values"
+title: "Aggregated Event Property Values"
 slug: "query-event-properties"
 excerpt: "Get unique, total, or average data for of a single event and property over days, weeks, or months."
 hidden: false