Update Organization Billing section (#825)

Author: leslie-lau

docs/platform/account-management/organizations.md

@@ -95,28 +95,32 @@ Your billing info including current plan and the payment information associated
 
 On this page you'll be presented with three sections.
 
-1. Your Plan
-2. Payment Method
-3. Cancel Subscription
+1. Current Plan
+2. Payment Settings
+3. Account Usage
 
-**1. Your Plan**
+**1. Current Plan**
 
 This section of the Billing & Plan page shows the currently active plan for your Organization. It provides a description of what's available on that plan and what capacity you can expect.
 
-From this section you can also review other plan tiers and upgrade by clicking the "Change Plan" button.
+From this section you can also review other plan tiers and upgrade by clicking the "Change Plan" button. 
 
-**2. Payment Method**
+**2. Payment Settings**
 
-This section allows you to add a credit card if you have not already done so.
+This section allows you to update the email where invoices will be sent to, and add or update your payment method.
 
 :::tip
 
 If you are currently seeing a notification that you have time remaining in your trial and you would like to stop receiving that notification add a card here and that notification will go away.
 
 :::
 
-If your card has expired or if you would like to switch your payment method you can also update your payment method here.
+**3. Account Usage**
 
-**3. Cancel Subscription**
+This section charts the trailing number of client-side **Monthly Active Users (MAU)** and **Experimentation Events** that have accumulated over the billing period.
+
+| Term | Definition |
+| - | - |
+| Monthly Active Users (MAU) | MAUs are unique users who initialize a client-side SDK at least once within a month. Users are identified by a `userId` which is set during SDK [initialization](/sdk/features#initialization) or via an [identify](/sdk/features#identifying-a-user-or-setting-properties) request. If no `userId` is provided during initialization, an [anonymous userId](/sdk/features#anonymous-users) is assigned automatically. Both identified and anonymous users are included in the MAU calculation. |
+| Experimentation Events | Experimentation events are [Custom Events](/sdk/features#tracking-custom-events) that are initiated via an SDK and serve as a foundation for tracking custom [Metrics](/platform/experimentation/creating-and-managing-metrics/). |
 
-If you need to cancel your subscription for any reason just use the "contact sales" button to send us a message and someone from our customer success team will help you.

docs/sdk/features.md

@@ -236,9 +236,7 @@ identity must be changed during the application's lifecycle.
 
 :::info
 
-If a user id is not supplied, client-side SDKs will automatically generate a user id and assign it to the current user.
-This id will be cached and used between app sessions / website visits until a user id is supplied or [reset](#resetting-a-user) is
-called. This will ensure you will not experience a rise in MAUs if the main experience of your application is in a logged-out or anonymous state.
+If a user id is not supplied, client-side SDKs will automatically generate a user id and assign it to the current user. This id will be cached and used between app sessions / website visits until a user id is supplied or [reset](#resetting-a-user) is called. This ensures that you will not experience a rise in MAUs if the main experience of your application is in a logged-out or anonymous state.
 
 :::
 
@@ -264,7 +262,7 @@ It is then discarded and no record is saved anywhere.
 With regular Custom Data, the data used for evaluation purposes is logged back to DevCycle's events database where
 it can be used for debugging purposes or providing guidance on evaluation reasons.
 
-#### Server-Side SDK Identification
+### Server-Side SDK Identification
 
 Unlike the Client-Side SDKs, Server-Side SDKs work in a multi-user context.
 Because of this, a single Identify function does not make sense.
@@ -290,8 +288,20 @@ stored DevCycle configuration, and no network calls will be made.
 
 ## Tracking Custom Events
 
-The Track function in the DevCycle SDKs allows you to send custom events which can later be used for your own data analysis on enabled Features,
-and metrics on A/B tests and experiments within the DevCycle dashboard.
+The Track function in the DevCycle SDKs allows you to send custom events which can be used for your own data analysis on enabled Features, and [Metrics](/platform/experimentation/creating-and-managing-metrics) on A/B tests and experiments within the DevCycle dashboard. Here is an example of a custom event request and properties that an event may contain.
+
+```javascript
+event = {
+  type: 'button_clicked', // required field
+  date: new Date(),
+  target: 'my_target',
+  value: 5,
+  metaData: {
+    key: 'value',
+  },
+}
+devcycleClient.track(event)
+```
 
 ## Custom Domains