Updating Currents docs

[ian-absher]

Pull Request/Issue Resolution

Description of Change:

This updates the Currents docs to:

• Fix an issue with the mParticle example event
• Add enriched fields that were missing
• Alphabetize the fields in the events

Closes #ISSUE_NUMBER_HERE

Is this change associated with a Braze feature/product release?

• Yes (Insert Feature Release Date Here)
• No

---

✔️ Pull Request Checklist

• Check that you haven't removed any images (replacing an image with an updated one of the same name is fine), as this breaks the French site
• Check that all links work.
• Ensure you have completed our Contributors License Agreement.
• Tag @josh-mccrowell-braze and @internetisaiah as a reviewer when your work is done and ready to be reviewed for merge. Are you an internal product manager? Reference the internal reviewing chart to tag the appropriate reviewer.
• If the documentation involves a 1) paid SKU, 2) a third party, 3) SMS, 4) AI, or 5) privacy, ensure that Ana Teresa Serafino on the Legal team has signed off.
• Tag others as reviewers as necessary.
• If you have modified any links, be sure to add redirects to assets > js > broken_redirect_list.js

⭐ Helpful Wiki Shortcuts

• Writing Style Guide
• Image Style Guide
• Styling Test Page

❗ ATTN: For PR Reviewers

• Read our Reviewing a PR page for more on our reviewing suggestions.
• Read our Previewing Documentation page to see how to check the deployment.
  • Preview all changes in the linked Vercel environment by clicking the preview link in the vercel-bot comment in your PR.

❗ ATTN: Internal Reviewing Chart

Work at Braze and not sure who to tag for review?
Before tagging @josh-mccrowell-braze or @internetisaiah for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.

Reviewer	Product Vertical
@josh-mccrowell-braze	Monolith Deployments Quality Infrastructure Platform Infrastructure Datalake SDKs Currents
@internetisaiah	Developer Guide Technology partners Channels
@bre-fitzgerald	Intelligence In-App Messages Channels Frontend Infrastructure & Experience (FIX)
@lydia-xie	Ingestion Core Objects Core Messaging Messaging Experience Message Components Email (Composition and Infrastructure) (tag @rachel-feinberg for Liquid use cases)
@rachel-feinberg	Customer Lifecycle, Identity and Permissions SMS User Targeting Reporting

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have you on file. In order for us to review and merge your code, please fill out the information here. To re-call the cla-bot, comment @cla-bot check.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have you on file. In order for us to review and merge your code, please fill out the information here. To re-call the cla-bot, comment @cla-bot check.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have you on file. In order for us to review and merge your code, please fill out the information here. To re-call the cla-bot, comment @cla-bot check.

[internetisaiah]

@ian-absher , left one comment for you. also, you will need to sign the CLA agreement before continuing! If you get stuck, just let me know and I'm happy to help out 👍🏽

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have you on file. In order for us to review and merge your code, please fill out the information here. To re-call the cla-bot, comment @cla-bot check.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have you on file. In order for us to review and merge your code, please fill out the information here. To re-call the cla-bot, comment @cla-bot check.

[internetisaiah]

LGTM. Just waiting on CLA to be signed 👍🏽

[josh-mccrowell-braze]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!