diff --git a/.acrolinx-config.edn b/.acrolinx-config.edn
index cddebf863..7ca95fa35 100644
--- a/.acrolinx-config.edn
+++ b/.acrolinx-config.edn
@@ -1,5 +1,5 @@
 {:allowed-branchname-matches ["main"]
- :allowed-filename-matches ["playfab-docs/features" "playfab-docs/data-analytics" "playfab-docs/playstream" "playfab-docs/gamemanager" "playfab-docs/miscellaneous" "playfab-docs/release-notes" "playfab-docs/resources" "playfab-docs/sdks"]
+ :allowed-filename-matches ["playfab-docs/data-analytics" "playfab-docs/demo-game" "playfab-docs/economy-monetization" "playfab-docs/get-started" "playfab-docs/identity" "playfab-docs/includes" "playfab-docs/live-service-management"  "playfab-docs/media"  "playfab-docs/miscellaneous"  "playfab-docs/multiplayer" "playfab-docs/player-progression"  "playfab-docs/pricing"  "playfab-docs/release-notes"  "playfab-docs/resources"  "playfab-docs/sdks"  "playfab-docs/test-documents"  "playfab-docs/whats-new"]
  
    :targets 
    {
@@ -11,7 +11,7 @@
              }
      :scores {
               ;;:terminology 100
-              :qualityscore 70
+              :qualityscore 80
               ;;:spelling 40
              }
    }
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 6b7393165..0ba70ebab 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -5,4 +5,4 @@
 
 # The '*' pattern is global owners.
 
-/playfab-docs/ @KevinAsgari @williacj @thomasgu
+/playfab-docs/ @MicrosoftDocs/xbox-learning-resources
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 000000000..198e45db6
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,23 @@
+## What changed
+<!-- Brief description of your changes -->
+
+
+## Related work items
+<!-- Link to any related work items, issues, or requests. Delete this section if not applicable. -->
+
+
+## Checklist
+
+- [ ] All new/modified articles have complete frontmatter (`author`, `title`, `description`, `ms.author`, `ms.topic`, `ms.date`, `ms.service`)
+- [ ] `title` field is present (required for builds)
+- [ ] `ms.date` updated on edited articles
+- [ ] New articles added to the relevant `toc.yml`
+- [ ] Images have descriptive alt-text for accessibility
+- [ ] No raw HTML — use only standard Markdown and Learn extensions
+- [ ] No broken links to other articles
+- [ ] Cross-repo links use site-relative paths (no `.md` extension)
+- [ ] Content is public-friendly (no confidential info or codenames)
+- [ ] Build validation email reviewed — errors and warnings resolved
+- [ ] Acrolinx score is 80+ (check automated PR test results)
+- [ ] Ran `.\scripts\validate-docs.ps1` locally
+- [ ] PR targets **main**
diff --git a/.github/agents/docs-reviewer.md b/.github/agents/docs-reviewer.md
new file mode 100644
index 000000000..77ba80b77
--- /dev/null
+++ b/.github/agents/docs-reviewer.md
@@ -0,0 +1,248 @@
+---
+name: docs-reviewer
+description: >
+  Reviews changed PlayFab documentation files for compliance with authoring standards.
+  Validates frontmatter fields, markdown restrictions, TOC consistency, image alt-text,
+  heading structure, cross-repo linking rules, and writing style (Acrolinx). Reports
+  issues without modifying files.
+tools:
+  - grep
+  - glob
+  - view
+  - powershell
+---
+
+# PlayFab Documentation Reviewer Agent
+
+You are a documentation reviewer for the PlayFab docs repo. Your job is to **review changed files** and **report issues** — never modify files.
+
+## How to Run a Review
+
+1. Get the list of changed `.md` and `toc.yml` files relative to `main`:
+
+```
+git --no-pager diff --name-only main -- 'playfab-docs/**/*.md' 'playfab-docs/**/toc.yml'
+```
+
+If that fails (e.g., no `main` branch locally), fall back to uncommitted changes:
+
+```
+git --no-pager diff --name-only HEAD -- 'playfab-docs/**/*.md' 'playfab-docs/**/toc.yml'
+```
+
+2. For each changed file, run the applicable checks below.
+3. Produce a summary report at the end.
+
+---
+
+## Checks for Markdown Files (`playfab-docs/**/*.md`)
+
+### 1. Required Frontmatter Fields
+
+Every `.md` file must have YAML frontmatter (`---` delimiters). The following fields are **always** required:
+
+| Field | Validation |
+|---|---|
+| `author` | Must be present and non-empty |
+| `ms.author` | Must be present and non-empty |
+| `ms.topic` | Must be one of: `article`, `conceptual`, `reference`, `include`, `hub-page`, `overview`, `release-notes` |
+| `ms.date` | Must be present, format `MM/DD/YYYY` |
+| `ms.service` | Must be `azure-playfab` |
+
+The following fields are required for **article pages** (any `ms.topic` value except `include`):
+
+| Field | Validation |
+|---|---|
+| `title` | Must be present and non-empty. **Build fails without it on article pages.** |
+| `description` | Must be present, under 160 characters |
+
+> **Note:** `title` and `description` are not required for `ms.topic: include` files but are still allowed.
+
+Flag: `MISSING_FIELD`, `INVALID_VALUE`, or `EMPTY_FIELD` with the field name.
+
+### 2. Raw HTML Detection
+
+Scan the body (below frontmatter) for raw HTML tags. HTML is not permitted — only standard Markdown and Learn extensions.
+
+Skip content inside fenced code blocks (` ``` `).
+
+Common tags to detect: `<div>`, `<span>`, `<table>`, `<tr>`, `<td>`, `<br>`, `<p>`, `<a>`, `<img>`, `<ul>`, `<ol>`, `<li>`, `<h1>`-`<h6>`, `<strong>`, `<em>`, `<b>`, `<i>`, `<style>`, `<script>`.
+
+Flag: `RAW_HTML` with the line number and tag found.
+
+### 3. Image Alt-Text
+
+Find all image references: `![alt-text](path)`. Flag if alt-text is empty: `![](path)`.
+
+Flag: `MISSING_ALT_TEXT` with the line number.
+
+### 4. Heading Structure
+
+- Flag if there are multiple H1 headings (`# `) in the same file: `DUPLICATE_H1`
+- Flag if H2 headings (`## `) are duplicated within the same file: `DUPLICATE_H2`
+- Flag heading level skips (e.g., `##` followed by `####` with no `###`): `HEADING_SKIP`
+
+### 5. Cross-Repo Linking Rules
+
+- Check that cross-repo links (starting with `/gaming/`) do NOT end with `.md`:
+  Flag: `CROSS_REPO_MD_EXTENSION` with the line number.
+- Check for links to non-existent internal files (relative `.md` links):
+  Flag: `BROKEN_INTERNAL_LINK` with the line number and target path.
+
+### 6. Content Sensitivity
+
+Since all PlayFab documentation is public:
+- Check that `title` and `description` don't contain obvious codenames or NDA-sounding terms.
+- This is a best-effort heuristic check — flag as `REVIEW_SENSITIVE_METADATA` (suggestion, not error).
+
+---
+
+## Checks for TOC Files (`toc.yml`)
+
+### 7. TOC Entry Validation
+
+For each `href` that points to a `.md` file (not another `toc.yml`):
+- Verify the file exists at the resolved relative path.
+  Flag: `BROKEN_TOC_LINK` with the href and expected path.
+
+### 8. Orphaned Articles
+
+For each changed `.md` file, check that it appears in the nearest parent `toc.yml`.
+Flag: `ORPHANED_ARTICLE` — article exists but has no TOC entry.
+
+---
+
+## Writing Style Checks (`playfab-docs/**/*.md`)
+
+These checks help achieve the Acrolinx quality gate (target score: 80). All writing style issues are **suggestions (⚠️)**, not errors. Skip content inside fenced code blocks (` ``` `) and inline code (`` ` ``).
+
+### 9. Latin Abbreviations
+
+Flag use of "e.g.", "i.e.", "etc.", or "vs." — should be "for example,", "that is,", "and so on", or "compared to".
+
+Flag: `LATIN_ABBREVIATION` with the line number.
+
+### 10. Heading Capitalization
+
+Flag headings that use title-style capitalization instead of sentence-style. Sentence-style means: capitalize the first word, proper nouns, and the first word after a colon; lowercase everything else.
+
+Flag: `HEADING_CAPITALIZATION` with the line number.
+
+### 11. Spaced Em Dashes
+
+Flag em dashes (`—`) with spaces before or after them. Correct: "works—and". Incorrect: "works — and".
+
+Flag: `SPACED_EM_DASH` with the line number.
+
+### 12. Missing Contractions
+
+Flag uncontracted forms like "cannot", "does not", "do not" — should use "can't", "doesn't", "don't" for conversational tone.
+
+Flag: `MISSING_CONTRACTION` with the line number and the suggested contraction.
+
+### 13. Filler Words
+
+Flag qualifiers like "strongly", "very", "really".
+
+Flag: `FILLER_WORD` with the line number and word found.
+
+### 14. Terminology
+
+Flag "login" used as a user action — should be "sign-in". Keep "login" only when it appears in API names (e.g., `ReLoginWith*Async`) or inside code blocks/inline code.
+
+Flag: `TERMINOLOGY` with the line number.
+
+### 15. Hyphenated Prefixes
+
+Flag unnecessary hyphens after common prefixes. Correct: "reauthenticate", "reinitialize". Incorrect: "re-authenticate", "re-initialize".
+
+Flag: `HYPHENATED_PREFIX` with the line number and word found.
+
+### 16. Unexpanded Acronyms
+
+Flag acronyms (2+ consecutive uppercase letters) that appear without a prior expansion in the document. Ignore common acronyms that don't need expansion: API, URL, HTTP, HTTPS, REST, JSON, XML, SDK, ID, UI, UX, HTML, CSS, IP, OS, etc.
+
+Flag: `UNEXPANDED_ACRONYM` with the line number and acronym.
+
+### 17. Dangling Demonstratives
+
+Flag "this", "that", "these", "those" when used as standalone pronouns not followed by a noun — should be "this request", "these tokens", etc.
+
+Flag: `DANGLING_DEMONSTRATIVE` with the line number.
+
+### 18. Compound Adjectives
+
+Flag common compound modifiers before a noun that are missing a hyphen — e.g., "first party title" should be "first-party title", "free to play game" should be "free-to-play game", "cross platform identity" should be "cross-platform identity".
+
+Flag: `MISSING_HYPHEN` with the line number and phrase found.
+
+### 19. Verb Tense
+
+Flag present perfect ("has expired", "has been configured") and future tense ("will call", "will return") — prefer simple present or past tense.
+
+Flag: `TENSE` with the line number and phrase found.
+
+### 20. API Reference Links
+
+Flag the first occurrence of a `PF*` function name (e.g., `PFAuthenticationLoginWithCustomIDAsync`) in body text that is not linked to its API reference page. Don't flag function names inside code blocks or inline code. Don't flag `HC*` (libHttpClient) functions.
+
+Flag: `UNLINKED_API_REFERENCE` with the line number and function name.
+
+---
+
+## Report Format
+
+After running all checks, produce a report in this format:
+
+```
+## 📋 PlayFab Docs Review Report
+
+### Summary
+- Files reviewed: X
+- Issues found: Y (Z errors, W suggestions)
+
+### Issues
+
+#### filename.md
+- ❌ MISSING_FIELD: `title` field is missing from frontmatter
+- ❌ RAW_HTML (line 52): `<div>` — HTML is not permitted
+- ⚠️ MISSING_ALT_TEXT (line 72): Image has empty alt-text
+
+#### toc.yml
+- ❌ BROKEN_TOC_LINK: `./nonexistent-file.md` does not exist
+
+### ✅ Clean Files
+- clean-file.md — no issues found
+```
+
+Use ❌ for errors (must fix) and ⚠️ for suggestions (should fix).
+
+### Severity Guide
+
+**Errors (❌) — must fix before PR:**
+- `MISSING_FIELD` (title, ms.service)
+- `RAW_HTML`
+- `BROKEN_TOC_LINK`
+- `DUPLICATE_H1`
+- `BROKEN_INTERNAL_LINK`
+
+**Suggestions (⚠️) — should fix:**
+- `MISSING_ALT_TEXT`
+- `DUPLICATE_H2`
+- `HEADING_SKIP`
+- `ORPHANED_ARTICLE`
+- `CROSS_REPO_MD_EXTENSION`
+- `REVIEW_SENSITIVE_METADATA`
+- `MISSING_FIELD` (for non-critical fields like `keywords`)
+- `LATIN_ABBREVIATION`
+- `HEADING_CAPITALIZATION`
+- `SPACED_EM_DASH`
+- `MISSING_CONTRACTION`
+- `FILLER_WORD`
+- `TERMINOLOGY`
+- `HYPHENATED_PREFIX`
+- `UNEXPANDED_ACRONYM`
+- `DANGLING_DEMONSTRATIVE`
+- `MISSING_HYPHEN`
+- `TENSE`
+- `UNLINKED_API_REFERENCE`
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
new file mode 100644
index 000000000..add0998c3
--- /dev/null
+++ b/.github/copilot-instructions.md
@@ -0,0 +1,185 @@
+# PlayFab Documentation
+
+Public documentation for Microsoft PlayFab, published to [learn.microsoft.com/gaming/playfab](https://learn.microsoft.com/gaming/playfab/). Built with DocFX (Markdig engine) and Microsoft Open Publishing System (OPS).
+
+## Build & Validation
+
+There is no local build. OPS builds on every push:
+
+1. Push your branch → Learn Build Service emails you results + preview URLs
+2. Fix all **errors** (block build). Note any **warnings** in files you touched — fix them in a follow-up PR to keep diffs clean
+3. Preview on review.learn.microsoft.com using the emailed links
+
+Run local validation before submitting a PR:
+
+```powershell
+.\scripts\validate-docs.ps1              # changed files vs main
+.\scripts\validate-docs.ps1 -All         # entire docs folder
+.\scripts\validate-docs.ps1 -Path playfab-docs/economy-monetization
+```
+
+Acrolinx content quality score ≥ 80 is required for merge to main.
+
+**Recommended editor:** VS Code with the Learn Authoring Pack extension.
+See `CONTRIBUTING.md` for the full contributor workflow.
+
+## Branch Workflow
+
+- Create working branches from `main`
+- All PRs target `main` — never commit directly
+- "Xbox learning resources" reviewer is auto-assigned (CODEOWNERS) and must approve
+- `main` → `live` is merged on the 2nd and 4th Tuesday of each month via automated PR
+
+## Project Structure
+
+```
+playfab-docs/                    ← All documentation content
+├── docfx.json                   ← DocFX build config
+├── index.yml                    ← Hub landing page (YamlMime:Hub)
+├── toc.yml                      ← Top-level table of contents
+├── includes/                    ← Reusable include files (_name.md)
+├── media/                       ← Images (PNG, SVG, JPG)
+├── breadcrumb/                  ← Breadcrumb navigation
+├── get-started/                 ← Onboarding & fundamentals
+├── economy-monetization/        ← Economy, catalogs, stores, UGC
+├── multiplayer/                 ← Servers, matchmaking, lobbies, networking
+├── identity/                    ← Authentication, player profiles
+├── player-progression/          ← Leaderboards, achievements, rules
+├── live-service-management/     ← Title config, experiments, insights
+├── data-analytics/              ← PlayStream, events, data connections
+├── sdks/                        ← SDK guides (C++, Unity, Unreal, etc.)
+├── api-references/              ← API reference docs (multiple formats — see L2)
+├── release-notes/               ← Version history (different format — see L2)
+├── pricing/                     ← Pricing tiers and meters
+├── resources/                   ← Limits, best practices
+├── community/                   ← Forums, support
+└── whats-new/                   ← Feature announcements
+```
+
+## Required YAML Frontmatter
+
+Every `.md` file must begin with YAML frontmatter (`---` delimiters). Article pages require all these fields:
+
+```yaml
+---
+title: "Page Title"
+description: "Brief SEO description of the page"
+author: githubUsername
+ms.author: microsoftAlias
+ms.date: MM/DD/YYYY
+ms.topic: article
+ms.service: azure-playfab
+---
+```
+
+> [!NOTE]
+> `ms.topic: include` files (under `playfab-docs/includes/`) do not require `title` or `description`. All other fields are still required.
+
+- `ms.topic` values: `article` (most content), `reference` (API docs), `include` (include files), `hub-page` (index.yml), `overview`, `release-notes`
+- `ms.service`: always `azure-playfab`
+- Date format: `MM/DD/YYYY`
+- All documentation is public — never include internal or confidential content
+
+## Markdown Conventions
+
+DocFX-flavored Markdown (Markdig engine). Key rules:
+
+- **One H1 per page**, matching the frontmatter `title`
+- **Never skip heading levels** — go H1 → H2 → H3, never H1 → H3
+- **No duplicate H2 headings** within a single topic
+- **Always specify language** on code blocks: ` ```json `, ` ```csharp `, ` ```cpp `
+
+### Alerts
+
+```markdown
+> [!NOTE]
+> Informational content
+
+> [!IMPORTANT]
+> Critical information
+
+> [!TIP]
+> Helpful suggestion
+
+> [!WARNING]
+> Risk or danger
+```
+
+### Video embeds
+
+```markdown
+> [!VIDEO video-id-here]
+>
+```
+
+### API cross-references (xref)
+
+```markdown
+[Display text](xref:titleid.playfabapi.com.admin.authentication.getpolicy)
+```
+
+## Links
+
+### Internal (same repo)
+
+Use relative paths **with** `.md` extension:
+
+```markdown
+[Link text](../section/file.md)
+```
+
+### Cross-repo (other Learn docsets)
+
+Use site-relative paths **without** `.md` extension:
+
+```markdown
+[Link text](/gaming/playfab/features/multiplayer/servers/overview)
+```
+
+Cross-repo links are validated at build time but are NOT click-navigable on the staging site.
+
+## Images
+
+- Store in `media/` directory relative to the content section
+- **Always include descriptive alt text** (accessibility requirement)
+- Supported formats: PNG, JPG, SVG, GIF
+
+```markdown
+![Descriptive alt text for screen readers](./media/filename.png)
+```
+
+## TOC Files
+
+YAML format with `name`/`href` pairs — see `playfab-docs/toc.yml` for the pattern:
+
+```yaml
+items:
+- name: Overview
+  href: overview.md
+- name: Section Name
+  items:
+  - name: Sub-page
+    href: sub-page.md
+```
+
+## Include Files
+
+- Stored in `playfab-docs/includes/`
+- Named with underscore prefix: `_name.md`
+- Use `ms.topic: include` in frontmatter
+
+## Content Quality
+
+- Acrolinx minimum score: **80** (enforced on merge)
+- All images must have alt text
+- Fix all build warnings in files you touch
+- No duplicate H1 titles across topics
+- Validate all links (build validates automatically)
+- Domain-specific spelling → add to `.vscode/settings.json` cSpell words list
+
+## Key Patterns
+
+- New conceptual article → follow `playfab-docs/get-started/what-is-playfab.md`
+- New TOC entry → follow `playfab-docs/toc.yml`
+- New include file → follow `playfab-docs/includes/_economy-deprecation.md`
+- Hub/landing page → follow `playfab-docs/index.yml` (YamlMime:Hub format)
diff --git a/.github/instructions/api-references.instructions.md b/.github/instructions/api-references.instructions.md
new file mode 100644
index 000000000..a95e5a157
--- /dev/null
+++ b/.github/instructions/api-references.instructions.md
@@ -0,0 +1,75 @@
+---
+applyTo: "playfab-docs/api-references/**"
+---
+
+# API Reference Conventions
+
+API reference pages use `ms.topic: reference` (not `conceptual`).
+
+> [!NOTE]
+> Many PlayFab API reference pages are machine-generated from a reference source. When reviewing or editing generated reference pages, respect the existing structure and conventions of the generated output. These conventions primarily apply to human-authored and AI-authored reference pages.
+
+## API Function Pages
+
+Follow this section structure for API function reference pages:
+
+```markdown
+# FunctionName
+
+One-sentence summary.
+
+## Syntax
+
+\`\`\`cpp
+ReturnType FunctionName(
+    ParamType param1,
+    const ParamType* param2
+)
+\`\`\`
+
+### Parameters
+
+**`param1`** &nbsp; ParamType
+Description of parameter.
+
+### Return value
+
+Type: ReturnType
+Description.
+
+## Remarks
+
+Detailed explanation.
+
+## Requirements
+
+**Header:** HeaderFile.h
+
+## See also
+
+[Related members](../members.md)
+```
+
+## Members Overview Pages
+
+Use markdown tables with two columns:
+
+```markdown
+| Function | Description |
+|---|---|
+| [FunctionName](functions/functionname.md) | Brief description |
+```
+
+## API Cross-References
+
+Use xref syntax for links to PlayFab REST API docs:
+
+```markdown
+[Display text](xref:titleid.playfabapi.com.admin.authentication.getpolicy)
+[With anchor](xref:titleid.playfabapi.com.admin.authentication.updatepolicy#permissionstatement)
+```
+
+## Pattern Files
+
+- Function page → see `playfab-docs/api-references/c/pfaccountmanagement/functions/pfaccountmanagementclientaddorupdatecontactemailasync.md`
+- Members overview → see `playfab-docs/api-references/c/pfaccountmanagement/pfaccountmanagement_members.md`
diff --git a/.github/instructions/release-notes.instructions.md b/.github/instructions/release-notes.instructions.md
new file mode 100644
index 000000000..7daddfbef
--- /dev/null
+++ b/.github/instructions/release-notes.instructions.md
@@ -0,0 +1,65 @@
+---
+applyTo: "playfab-docs/release-notes/**"
+---
+
+# Release Notes Conventions
+
+## Entry Format
+
+Each release is an H2 heading with a version identifier, followed by the date and a bullet list of changes:
+
+```markdown
+## <version>
+
+Date: Month Day, Year
+
+- Change description with relevant details
+- Another change
+```
+
+## Version Formats
+
+Different libraries use different version formats. **Always follow the existing version format used in the file you are editing.**
+
+| Library | Format | Example |
+|---|---|---|
+| PlayFab Services SDK | `YYMMDD` (year-month-day, no separators) | `251219` |
+| PlayFab C/C++ SDK | Semver-style | `2504.0.0` |
+
+If you are unsure which format to use, check the most recent H2 heading already in the file and match it.
+
+## Examples
+
+### PlayFab Services SDK (`YYMMDD`)
+
+```markdown
+## 251219
+
+Date: December 19, 2025
+
+- Added StartDate field to Economy API SearchItems response
+- Fixed issue with multiplayer server allocation in East US region
+```
+
+### PlayFab C/C++ SDK (semver)
+
+```markdown
+## 2504.0.0
+
+Date: April 25, 2025
+
+- Added new PFAccountManagement APIs for contact email management
+- Fixed memory leak in PFMultiplayerServer cleanup
+```
+
+## Rules
+
+- Date line uses full month name: `Date: March 15, 2025`
+- Each bullet is a concise, complete sentence fragment describing one change
+- Newest releases go at the top of the file
+- Each calendar year gets its own file (`2024.md`, `2025.md`, etc.)
+
+## Pattern Files
+
+- PlayFab Services SDK → `playfab-docs/release-notes/2025.md`
+- PlayFab C/C++ SDK → `playfab-docs/release-notes/playfab-c/index.md`
diff --git a/.github/instructions/toc-files.instructions.md b/.github/instructions/toc-files.instructions.md
new file mode 100644
index 000000000..8555d0239
--- /dev/null
+++ b/.github/instructions/toc-files.instructions.md
@@ -0,0 +1,28 @@
+---
+applyTo: "playfab-docs/**/toc.yml"
+---
+
+# toc.yml Editing Instructions
+
+## Format
+
+```yaml
+- name: "Display Name"
+  href: ./article.md          # link to article or child toc.yml
+  items:                       # optional nested entries
+    - name: "Child Entry"
+      href: ./child/article.md
+```
+
+## Rules
+
+- `name` — quote if it contains special characters
+- `href` — use relative paths (`./`, `../`) or site-absolute paths starting with `/playfab-docs/...`
+- Link to child `toc.yml` files for sub-sections, or directly to `.md` files
+- Maintain ordering consistent with sibling entries
+- Every article in the directory should have a TOC entry — orphaned pages won't appear in navigation
+- Test that all `href` paths resolve to existing files
+
+## Pattern File
+
+Follow `playfab-docs/toc.yml` for top-level structure.
diff --git a/.github/workflows/merge-main-to-live.yml b/.github/workflows/merge-main-to-live.yml
new file mode 100644
index 000000000..678ce98dc
--- /dev/null
+++ b/.github/workflows/merge-main-to-live.yml
@@ -0,0 +1,184 @@
+name: Merge Main to Live
+
+on:
+  schedule:
+    # Run at 9:00 AM UTC every Tuesday
+    - cron: '0 9 * * 2'
+  workflow_dispatch: # Allow manual trigger for testing
+    inputs:
+      skip_date_check:
+        description: 'Skip the Tuesday date check for testing (select true to test immediately)'
+        required: false
+        default: 'false'
+        type: choice
+        options:
+          - 'false'
+          - 'true'
+
+jobs:
+  merge:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write      # Required for creating pull requests via REST API
+      pull-requests: write # Required for creating pull requests
+      issues: write        # Required for creating issues on failure
+    
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.GITHUB_TOKEN }}
+      
+      - name: Check if it's 2nd or 4th Tuesday
+        id: check_date
+        run: |
+          # Check if we should skip the date check (for testing)
+          if [ "${{ github.event.inputs.skip_date_check }}" = "true" ]; then
+            echo "should_merge=true" >> $GITHUB_OUTPUT
+            echo "⚠️ TESTING MODE: Skipping date check as requested via workflow input"
+            exit 0
+          fi
+          
+          # Get the current day of the month
+          day=$(date +%d)
+          # Remove leading zero if present
+          day=$((10#$day))
+          
+          # Calculate which week of the month we're in (1-5)
+          week=$(( (day - 1) / 7 + 1 ))
+          
+          # Get the current day of week (1=Monday, 2=Tuesday, ..., 7=Sunday)
+          dow=$(date +%u)
+          
+          echo "Day of month: $day"
+          echo "Week of month: $week"
+          echo "Day of week: $dow"
+          
+          # Check if today is Tuesday (dow=2) and it's the 2nd or 4th week
+          if [ "$dow" = "2" ] && ([ "$week" = "2" ] || [ "$week" = "4" ]); then
+            echo "should_merge=true" >> $GITHUB_OUTPUT
+            echo "This is the 2nd or 4th Tuesday of the month. Proceeding with merge."
+          else
+            echo "should_merge=false" >> $GITHUB_OUTPUT
+            echo "Not the 2nd or 4th Tuesday. Skipping merge."
+          fi
+      
+      - name: Check for existing PR
+        if: steps.check_date.outputs.should_merge == 'true'
+        id: check_pr
+        uses: actions/github-script@v7
+        with:
+          script: |
+            // Check for open PR from main to live (lowercase for testing)
+            const { data: pulls } = await github.rest.pulls.list({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              state: 'open',
+              head: `${context.repo.owner}:main`,
+              base: 'live'
+            });
+            
+            if (pulls.length > 0) {
+              core.setOutput('pr_exists', 'true');
+              core.setOutput('pr_number', pulls[0].number);
+              core.setOutput('pr_url', pulls[0].html_url);
+              console.log(`Existing PR found: ${pulls[0].html_url}`);
+            } else {
+              core.setOutput('pr_exists', 'false');
+              console.log('No existing PR found. Will create a new one.');
+            }
+
+      - name: Create Pull Request
+        if: steps.check_date.outputs.should_merge == 'true' && steps.check_pr.outputs.pr_exists == 'false'
+        id: create_pr
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const date = new Date().toISOString().split('T')[0];
+            const title = `Scheduled Merge: main to live on ${date}`;
+            const body = [
+              'This is an automated pull request to merge main branch into live branch.',
+              '',
+              `**Scheduled merge date:** ${date}`,
+              `**Schedule:** This PR is created on the 2nd and 4th Tuesday of each month.`,
+              `**Workflow run:** ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}`,
+              '',
+              '**Instructions:**',
+              '- Review the changes',
+              '- Ensure all checks pass',
+              '- Code owners should approve this PR',
+              '- Merge when ready',
+              '',
+              'If there are conflicts, they can be resolved in the GitHub UI or locally.',
+              '',
+              '---',
+              '*This PR was automatically created by the scheduled merge workflow.*'
+            ].join('\n');
+            
+            try {
+              const { data: pr } = await github.rest.pulls.create({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                title: title,
+                body: body,
+                head: 'main',
+                base: 'live'
+              });
+              
+              core.setOutput('pr_number', pr.number);
+              core.setOutput('pr_url', pr.html_url);
+              console.log(`Pull request created: ${pr.html_url}`);
+            } catch (error) {
+              core.setFailed(`Failed to create pull request: ${error.message}`);
+              throw error;
+            }
+
+      - name: Comment on existing PR
+        if: steps.check_date.outputs.should_merge == 'true' && steps.check_pr.outputs.pr_exists == 'true'
+        uses: actions/github-script@v7
+        env:
+          PR_NUMBER: ${{ steps.check_pr.outputs.pr_number }}
+        with:
+          script: |
+            const date = new Date().toISOString().split('T')[0];
+            const prNumber = parseInt(process.env.PR_NUMBER);
+            const comment = [
+              `♻️ Scheduled merge workflow ran again on ${date}.`,
+              '',
+              'This PR is still open and ready for review.',
+              '',
+              `**Workflow run:** ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}`
+            ].join('\n');
+            
+            await github.rest.issues.createComment({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: prNumber,
+              body: comment
+            });
+            
+            console.log(`Comment added to existing PR #${prNumber}`);
+
+      - name: Create Issue on Failure
+        if: failure() && steps.check_date.outputs.should_merge == 'true'
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const date = new Date().toISOString().split('T')[0];
+            const title = `Scheduled Merge PR Creation Failed: Main to Live on ${date}`;
+            const body = [
+              'The scheduled merge workflow failed to create a pull request from Main to Live branch.',
+              '',
+              `**Workflow Run:** ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}`,
+              '',
+              'Please review the workflow logs and create the pull request manually if needed.'
+            ].join('\n');
+            
+            await github.rest.issues.create({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              title: title,
+              body: body,
+              labels: ['merge-conflict', 'automated']
+            });
diff --git a/.github/workflows/validate-docs.yml b/.github/workflows/validate-docs.yml
new file mode 100644
index 000000000..d97d69eb7
--- /dev/null
+++ b/.github/workflows/validate-docs.yml
@@ -0,0 +1,27 @@
+name: Validate Docs
+
+on:
+  pull_request:
+    branches: [main]
+    paths:
+      - 'playfab-docs/**'
+      - 'scripts/validate-docs.ps1'
+      - '.github/workflows/validate-docs.yml'
+
+jobs:
+  validate:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Run validation on changed files
+        shell: pwsh
+        run: |
+          # Default mode diffs against 'main' and validates only changed files
+          ./scripts/validate-docs.ps1
diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json
index bbf91ea6f..fb744d2ef 100644
--- a/.openpublishing.publish.config.json
+++ b/.openpublishing.publish.config.json
@@ -38,9 +38,7 @@
   "branches_to_filter": [],
   "git_repository_url_open_to_public_contributors": "https://github.com/MicrosoftDocs/playfab-docs",
   "git_repository_branch_open_to_public_contributors": "docs",
-  "skip_source_output_uploading": false,
   "need_preview_pull_request": true,
-  "contribution_branch_mappings": {},
   "dependent_repositories": [
     {
       "path_to_root": "_themes",
@@ -69,12 +67,15 @@
       "Pdf"
     ]
   },
-  "need_generate_pdf_url_template": true,
   "targets": {
     "pdf": {
       "template_folder": "_themes.pdf"
     }
   },
+  "docs_build_engine": {},
+  "skip_source_output_uploading": false,
+  "contribution_branch_mappings": {},
+  "need_generate_pdf_url_template": true,
   "dependent_packages": [
     {
       "id": "Microsoft.OpenPublishing.CommonPlugins",
@@ -83,8 +84,5 @@
       "target_framework": "net45",
       "version": "latest"
     }
-  ],
-  "docs_build_engine": {
-    "name": "docfx_v3"
-  }
-}
+  ]
+}
\ No newline at end of file
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
index a88c70d12..0e982c4ae 100644
--- a/.openpublishing.redirection.json
+++ b/.openpublishing.redirection.json
@@ -1,6 +1,11 @@
 {
     "redirections": [
          {
+            "source_path": "playfab-docs/api-references/events/player-action-executed.md",
+            "redirect_url": "/gaming/playfab/api-references/events/playstream/player-action-executed",
+            "redirect_document_id": true
+        },
+        {
             "source_path": "playfab-docs/sdks/objective-c/quickstart.md",
             "redirect_url": "/gaming/playfab/sdks/c/quickstart-ios",
             "redirect_document_id": false
@@ -217,57 +222,57 @@
         },
         {
             "source_path": "playfab-docs/api-references/events/gamelobby-ended.md",
-            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
         },
         {
             "source_path": "playfab-docs/api-references/events/gamelobby-started.md",
-            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
         },
         {
             "source_path": "playfab-docs/api-references/events/gameserverhost-started.md",
-            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
         },
         {
             "source_path": "playfab-docs/api-references/events/gameserverhost-stopped.md",
-            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
         },
         {
             "source_path": "playfab-docs/api-references/events/player-joined-lobby.md",
-            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
         },
         {
             "source_path": "playfab-docs/api-references/events/player-left-lobby.md",
-            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
         },
         {
             "source_path": "playfab-docs/api-references/events/player-matched-with-lobby.md",
-            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
         },
         {
             "source_path": "playfab-docs/api-references/events/session-ended.md",
-            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
         },
         {
             "source_path": "playfab-docs/api-references/events/session-started.md",
-            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
         },
         {
             "source_path": "playfab-docs/api-references/events/title-game-build-added.md",
-            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
         },
         {
             "source_path": "playfab-docs/api-references/events/title-game-build-modified.md",
-            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/features/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
         },
         {
@@ -1065,7 +1070,7 @@
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/server-methods/add-entity-to-session.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/server-methods/add-entity-to-session",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/server-methods/add-entity-to-session",
             "redirect_document_id": false
           },
           {
@@ -1580,17 +1585,17 @@
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/types/end-session-request.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/types/end-session-request",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/end-session-request",
             "redirect_document_id": false
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/types/end-session-response.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/types/end-session-response",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/end-session-response",
             "redirect_document_id": false
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/server-methods/end-session.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/server-methods/end-session",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/server-methods/end-session",
             "redirect_document_id": false
           },
           {
@@ -2025,7 +2030,7 @@
           },
           {
             "source_path": "playfab-docs/features/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications.md",
-            "redirect_url": "/gaming/playfab/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications",
+            "redirect_url": "/gaming/playfab/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
             "redirect_document_id": false
           },
           {
@@ -2275,7 +2280,7 @@
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/types/message.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/types/message",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/message",
             "redirect_document_id": false
           },
           {
@@ -5365,12 +5370,12 @@
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/client-methods/receive-message.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/client-methods/receive-message",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/client-methods/receive-message",
             "redirect_document_id": false
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/client-methods/receive-subscription-change-message.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/client-methods/receive-subscription-change-message",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/client-methods/receive-subscription-change-message",
             "redirect_document_id": false
           },
           {
@@ -5395,7 +5400,7 @@
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/server-methods/remove-entity-from-session.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/server-methods/remove-entity-from-session",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/server-methods/remove-entity-from-session",
             "redirect_document_id": false
           },
           {
@@ -5405,7 +5410,7 @@
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/types/response-status.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/types/response-status",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/response-status",
             "redirect_document_id": false
           },
           {
@@ -5575,17 +5580,17 @@
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/types/shared-session-request.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/types/shared-session-request",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/shared-session-request",
             "redirect_document_id": false
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/types/shared-session-response.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/types/shared-session-response",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/shared-session-response",
             "redirect_document_id": false
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/signalr-hub.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/signalr-hub",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/signalr-hub",
             "redirect_document_id": false
           },
           {
@@ -5600,17 +5605,17 @@
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/types/start-or-recover-session-request.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/types/start-or-recover-session-request",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/start-or-recover-session-request",
             "redirect_document_id": false
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/types/start-or-recover-session-response.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/types/start-or-recover-session-response",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/start-or-recover-session-response",
             "redirect_document_id": false
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/server-methods/start-or-recover-session.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/server-methods/start-or-recover-session",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/server-methods/start-or-recover-session",
             "redirect_document_id": false
           },
           {
@@ -5650,12 +5655,12 @@
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/subscribing-to-resources.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/subscribing-to-resources",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/subscribing-to-resources",
             "redirect_document_id": false
           },
           {
             "source_path": "playfab-docs/features/real-time-notifications/types/subscription-change-message.md",
-            "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/types/subscription-change-message",
+            "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/subscription-change-message",
             "redirect_document_id": false
           },
           {
@@ -6790,7 +6795,7 @@
             },
             {
               "source_path": "features/multiplayer/lobby/notifications-overview.md",
-              "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/overview.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/overview",
               "redirect_document_id": false
             },
             {
@@ -6805,7 +6810,7 @@
             },
             {
               "source_path": "playfab-docs/features/real-time-notifications/overview.md",
-              "redirect_url": "/gaming/playfab/multiplayer/real-time-notifications/overview",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/overview",
               "redirect_document_id": false
             },
             {
@@ -6862,6 +6867,101 @@
               "source_path": "playfab-docs/features/economy/index.yml",
               "redirect_url": "/gaming/playfab/economy-monetization/",
               "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/overview.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/overview",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/signalr-hub.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/signalr-hub",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/subscribing-to-resources.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/subscribing-to-resources",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/client-methods/receive-message.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/client-methods/receive-message",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/client-methods/receive-subscription-change-message.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/client-methods/receive-subscription-change-message",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/server-methods/start-or-recover-session.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/server-methods/start-or-recover-session",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/server-methods/end-session.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/server-methods/end-session",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/server-methods/add-entity-to-session.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/server-methods/add-entity-to-session",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/server-methods/remove-entity-from-session.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/server-methods/remove-entity-from-session",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/types/message.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/message",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/types/subscription-change-message.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/subscription-change-message",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/types/response-status.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/response-status",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/types/start-or-recover-session-request.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/start-or-recover-session-request",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/types/start-or-recover-session-response.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/start-or-recover-session-response",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/types/end-session-request.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/end-session-request",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/types/end-session-response.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/end-session-response",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/types/shared-session-request.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/shared-session-request",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/real-time-notifications/types/shared-session-response.md",
+              "redirect_url": "/gaming/playfab/multiplayer/real-time-messages/types/shared-session-response",
+              "redirect_document_id": false
+            },
+            {
+              "source_path": "playfab-docs/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications.md",
+              "redirect_url": "/gaming/playfab/multiplayer/lobby/lobby-and-matchmaking-real-time-messages",
+              "redirect_document_id": false
             }
         ]
 }
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 000000000..3f184ee23
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,126 @@
+# Contributing to PlayFab Documentation
+
+## Branch Strategy
+
+```
+main → live
+```
+
+- Create working branches from **main**
+- **All PRs must target `main`** — never commit to main directly
+- Automated merges promote content: main → live (2nd and 4th Tuesday of each month)
+- "Xbox learning resources" reviewer is automatically assigned via CODEOWNERS and must approve
+
+## Documentation URL
+
+Published to: https://learn.microsoft.com/gaming/playfab/
+
+## Article Requirements
+
+Every Markdown article in `playfab-docs/` must include YAML frontmatter with these required fields:
+
+| Field | Format | Example |
+|---|---|---|
+| `author` | GitHub username | `joannaleecy` |
+| `title` | Quoted string | `"Overview of Economy features"` |
+| `description` | Quoted string (<160 chars) | `"Learn about PlayFab Economy..."` |
+| `ms.author` | MS alias | `joanlee` |
+| `ms.topic` | Enum | `article`, `conceptual`, `reference`, `include`, `hub-page`, `overview`, `release-notes` |
+| `ms.date` | `MM/DD/YYYY` | `03/19/2025` |
+| `ms.service` | Always | `azure-playfab` |
+
+Optional but recommended: `keywords` (SEO terms), `ms.localizationpriority`.
+
+## Markdown Conventions
+
+PlayFab docs use **DocFX-flavored Markdown** (Markdig engine). Supported extensions:
+
+```markdown
+> [!NOTE]           > [!IMPORTANT]
+> [!TIP]            > [!WARNING]
+> [!VIDEO id]       (video embeds)
+```
+
+Cross-reference syntax for API links:
+```markdown
+[Display text](xref:titleid.playfabapi.com.admin.authentication.getpolicy)
+```
+
+### Rules
+
+- **One H1 per page**, matching the frontmatter `title`
+- **Never skip heading levels** — go H1 → H2 → H3, not H1 → H3
+- **No duplicate H2 headings** within a single topic
+- **Always specify language** on code blocks: ` ```json `, ` ```csharp `, ` ```cpp `
+- **No raw HTML** — use only standard Markdown and Learn extensions
+- **All images must have alt-text** for accessibility
+
+## File Naming
+
+- Use **kebab-case** for Markdown files: `economy-what-is.md`
+- TOC files are always `toc.yml` (lowercase)
+- Images go in `media/` directory relative to the content section
+
+## Linking
+
+### Internal (same repo)
+
+Use relative paths **with** `.md` extension:
+
+```markdown
+[Link text](../section/file.md)
+```
+
+### Cross-repo (other Learn docsets)
+
+Use site-relative paths **without** `.md` extension:
+
+```markdown
+[Link text](/gaming/playfab/features/multiplayer/servers/overview)
+```
+
+Cross-repo links are validated at build time but are NOT click-navigable on the staging site.
+
+## Validation Workflow
+
+1. Push your branch to the server
+2. The **Learn Build Service** runs validation and sends you an email
+3. Review the build status:
+   - **Failed** — must fix before content can build
+   - **Succeeded With Warning** — fix warnings in your topics before PR
+   - **Succeeded With Suggestion** — fix if possible (aliases, table headers)
+   - **Succeeded** — ideal state ✅
+4. Use the preview URLs in the email to verify rendering
+
+### Local Validation
+
+Run the validation script before submitting a PR:
+
+```powershell
+.\scripts\validate-docs.ps1              # changed files vs main
+.\scripts\validate-docs.ps1 -All         # entire docs folder
+.\scripts\validate-docs.ps1 -Path playfab-docs/economy-monetization
+```
+
+### Local Preview
+
+Install the **Learn Authoring Pack** VS Code extension for local markdown preview.
+
+## Checklist Before Submitting a PR
+
+- [ ] All new/modified articles have complete frontmatter
+- [ ] `title` field is present (required for builds)
+- [ ] `ms.date` is updated on edited articles
+- [ ] New articles are added to the relevant `toc.yml`
+- [ ] Images have descriptive alt-text for accessibility
+- [ ] No broken links to other articles
+- [ ] No raw HTML — use only standard Markdown and Learn extensions
+- [ ] Cross-repo links use site-relative paths (no `.md` extension)
+- [ ] Content is public-friendly (no confidential info or codenames)
+- [ ] Build validation email reviewed — errors and warnings resolved
+- [ ] Acrolinx score is 80+ (check automated PR test results)
+- [ ] PR targets **main**
+
+## Code Owners
+
+All content is owned by **@MicrosoftDocs/xbox-learning-resources** (see `CODEOWNERS`).
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 000000000..e138ec5d6
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,41 @@
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.8 BLOCK -->
+
+## Security
+
+Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
+
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
+
+## Reporting Security Issues
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
+
+If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
+
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd).
+
+<!-- END MICROSOFT SECURITY.MD BLOCK -->
diff --git a/playfab-docs/api-references/events/AdPlacement/player-ad-closed.md b/playfab-docs/api-references/events/AdPlacement/player-ad-closed.md
new file mode 100644
index 000000000..72c7bfca8
--- /dev/null
+++ b/playfab-docs/api-references/events/AdPlacement/player-ad-closed.md
@@ -0,0 +1,30 @@
+---
+title: player_ad_closed
+author: joannaleecy
+description: player_ad_closed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_ad_closed
+
+This event is triggered when a player closes an ad.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AdPlacementId|String|Id of the placement|
+|AdPlacementName|String|Name of the placement|
+|AdUnit|String|Ad unit type|
+|RewardId|String|Id of the reward|
+|RewardName|String|Name of the reward|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/AdPlacement/player-ad-ended.md b/playfab-docs/api-references/events/AdPlacement/player-ad-ended.md
new file mode 100644
index 000000000..4ae866eee
--- /dev/null
+++ b/playfab-docs/api-references/events/AdPlacement/player-ad-ended.md
@@ -0,0 +1,30 @@
+---
+title: player_ad_ended
+author: joannaleecy
+description: player_ad_ended event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_ad_ended
+
+This event is triggered when a player finishes an ad.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AdPlacementId|String|Id of the placement|
+|AdPlacementName|String|Name of the placement|
+|AdUnit|String|Ad unit type|
+|RewardId|String|Id of the reward|
+|RewardName|String|Name of the reward|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/AdPlacement/player-ad-opened.md b/playfab-docs/api-references/events/AdPlacement/player-ad-opened.md
new file mode 100644
index 000000000..5759ce16d
--- /dev/null
+++ b/playfab-docs/api-references/events/AdPlacement/player-ad-opened.md
@@ -0,0 +1,30 @@
+---
+title: player_ad_opened
+author: joannaleecy
+description: player_ad_opened event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_ad_opened
+
+This event is triggered when a player opens an ad.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AdPlacementId|String|Id of the placement|
+|AdPlacementName|String|Name of the placement|
+|AdUnit|String|Ad unit type|
+|RewardId|String|Id of the reward|
+|RewardName|String|Name of the reward|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/AdPlacement/player-ad-rewarded.md b/playfab-docs/api-references/events/AdPlacement/player-ad-rewarded.md
new file mode 100644
index 000000000..2f9cc9a77
--- /dev/null
+++ b/playfab-docs/api-references/events/AdPlacement/player-ad-rewarded.md
@@ -0,0 +1,32 @@
+---
+title: player_ad_rewarded
+author: joannaleecy
+description: player_ad_rewarded event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_ad_rewarded
+
+This event is triggered when a player recieves an ad reward.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ActionGroupDebugMessages|[]|Debug messages from the reward actions|
+|AdPlacementId|String|Id of the placement|
+|AdPlacementName|String|Name of the placement|
+|AdUnit|String|Ad unit type|
+|RewardId|String|Id of the reward|
+|RewardName|String|Name of the reward|
+|TitleId|String|The ID of the title to which this player event applies.|
+|ViewsRemainingThisPeriod|int32|Views this player has remaining for the placement's window, if applicable|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/AdPlacement/player-ad-started.md b/playfab-docs/api-references/events/AdPlacement/player-ad-started.md
new file mode 100644
index 000000000..c85ae5e2f
--- /dev/null
+++ b/playfab-docs/api-references/events/AdPlacement/player-ad-started.md
@@ -0,0 +1,30 @@
+---
+title: player_ad_started
+author: joannaleecy
+description: player_ad_started event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_ad_started
+
+This event is triggered when a player starts an ad.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AdPlacementId|String|Id of the placement|
+|AdPlacementName|String|Name of the placement|
+|AdUnit|String|Ad unit type|
+|RewardId|String|Id of the reward|
+|RewardName|String|Name of the reward|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Addons/title-addon-changed.md b/playfab-docs/api-references/events/Addons/title-addon-changed.md
new file mode 100644
index 000000000..78f3a6b5a
--- /dev/null
+++ b/playfab-docs/api-references/events/Addons/title-addon-changed.md
@@ -0,0 +1,29 @@
+---
+title: title_addon_changed
+author: ronnyparedes
+description: title_addon_changed event.
+ms.author: ronnyparedes
+ms.date: 02/06/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_addon_changed
+
+This event is triggered when a marketplace AddOn is installed, or changes state.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AddOnId|String|Unique identifier of the AddOn affected.|
+|AddOnName|String|Name of the AddOn affected.|
+|DeveloperId|String|Developer/Studio ID.|
+|State|[AddOnProvisioningState](../data-types/addonprovisioningstate.md)|Current state of the AddOn. Values include Inactive, Paused, Active, Pending, and PendingWithError.|
+|UserId|String|May be null if user is unknown (Admin API, partner source).|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/ApiAccessPolicy/title-api-settings-changed.md b/playfab-docs/api-references/events/ApiAccessPolicy/title-api-settings-changed.md
new file mode 100644
index 000000000..13d7309a1
--- /dev/null
+++ b/playfab-docs/api-references/events/ApiAccessPolicy/title-api-settings-changed.md
@@ -0,0 +1,28 @@
+---
+title: title_api_settings_changed
+author: joannaleecy
+description: title_api_settings_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_api_settings_changed
+
+This event is triggered when an API Features setting is changed for the title.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|PreviousSettingsValues|[APISettings](../data-types/apisettings.md)|Settings values before the change.|
+|SettingsValues|[APISettings](../data-types/apisettings.md)|Settings values after the change.|
+|UserId|String||
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/ApiAccessPolicy/title-permission-policy-changed.md b/playfab-docs/api-references/events/ApiAccessPolicy/title-permission-policy-changed.md
new file mode 100644
index 000000000..f287f2d6e
--- /dev/null
+++ b/playfab-docs/api-references/events/ApiAccessPolicy/title-permission-policy-changed.md
@@ -0,0 +1,28 @@
+---
+title: title_permission_policy_changed
+author: joannaleecy
+description: title_permission_policy_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_permission_policy_changed
+
+This event is triggered when an update occurs to a title's permission policies.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|NewPolicy|String|The contents new policy.|
+|PolicyName|String|The name of the policy that was changed|
+|UserId|String||
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/CatalogV1/title-catalog-updated.md b/playfab-docs/api-references/events/CatalogV1/title-catalog-updated.md
new file mode 100644
index 000000000..2723f0881
--- /dev/null
+++ b/playfab-docs/api-references/events/CatalogV1/title-catalog-updated.md
@@ -0,0 +1,28 @@
+---
+title: title_catalog_updated
+author: joannaleecy
+description: title_catalog_updated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_catalog_updated
+
+This event is triggered when a catalog is changed.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| CatalogVersion | String | Version of the catalog that was updated. |
+| Deleted | Boolean | Was the catalog deleted. |
+| DeveloperId | String |  |
+| UserId | String |  |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/CatalogV1/title-store-updated.md b/playfab-docs/api-references/events/CatalogV1/title-store-updated.md
new file mode 100644
index 000000000..64c101858
--- /dev/null
+++ b/playfab-docs/api-references/events/CatalogV1/title-store-updated.md
@@ -0,0 +1,29 @@
+---
+title: title_store_updated
+author: ernestoc
+description: title_store_updated event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_store_updated
+
+This event is triggered when a store is changed.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| CatalogVersion | String | Catalog version that the updated store belongs to. |
+| Deleted | Boolean | Was the store deleted. |
+| DeveloperId | String |  |
+| StoreId | String | ID of the updated store. |
+| UserId | String |  |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/CatalogV2/item-created.md b/playfab-docs/api-references/events/CatalogV2/item-created.md
new file mode 100644
index 000000000..824c1fe32
--- /dev/null
+++ b/playfab-docs/api-references/events/CatalogV2/item-created.md
@@ -0,0 +1,26 @@
+---
+title: item_created
+author: ernestoc
+description: ItemCreated event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# item_created
+
+This event is triggered when an item is created.
+
+## Properties
+
+| Name     | Type   | Description                                   |
+| :------- | :----- | :-------------------------------------------- |
+| ItemId   | String | The string of the item that was created.      |
+| ItemType | String | The string type of the item that was created. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/CatalogV2/item-deleted.md b/playfab-docs/api-references/events/CatalogV2/item-deleted.md
new file mode 100644
index 000000000..fd61676b3
--- /dev/null
+++ b/playfab-docs/api-references/events/CatalogV2/item-deleted.md
@@ -0,0 +1,26 @@
+---
+title: item_deleted
+author: ernestoc
+description: ItemDeleted event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# item_deleted
+
+This event is triggered when an item is deleted.
+
+## Properties
+
+| Name     | Type   | Description                                   |
+| :------- | :----- | :-------------------------------------------- |
+| ItemId   | String | The string ID of the item that was deleted.   |
+| ItemType | String | The string type of the item that was deleted. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/CatalogV2/item-moderation-state-changed.md b/playfab-docs/api-references/events/CatalogV2/item-moderation-state-changed.md
new file mode 100644
index 000000000..52ebb4501
--- /dev/null
+++ b/playfab-docs/api-references/events/CatalogV2/item-moderation-state-changed.md
@@ -0,0 +1,27 @@
+---
+title: item_moderation_state_changed
+author: fprotti96
+description: ItemModerationStateChanged event.
+ms.author: fprotti
+ms.date: 09/29/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# item_moderation_state_changed
+
+This event is triggered when an item moderation state is changed.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| ItemId | String | The string ID of the item whos state was changed. |
+| TargetStatus | String | The updated moderation status of the item. |
+| Reason | String | The current stated reason for the associated item being moderated. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/CatalogV2/item-publish-requested.md b/playfab-docs/api-references/events/CatalogV2/item-publish-requested.md
new file mode 100644
index 000000000..5251a95d5
--- /dev/null
+++ b/playfab-docs/api-references/events/CatalogV2/item-publish-requested.md
@@ -0,0 +1,26 @@
+---
+title: item-publish-requested
+author: fprotti96
+description: ItemPublishRequested event.
+ms.author: fprotti
+ms.date: 09/29/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# item_publish_requested
+
+This event is triggered when an publishing is started.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| ItemId | String | The string ID of the item that is to be published. |
+| ItemType | String | The string type of the item that is to be published. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/CatalogV2/item-purchased.md b/playfab-docs/api-references/events/CatalogV2/item-purchased.md
new file mode 100644
index 000000000..329f9cc46
--- /dev/null
+++ b/playfab-docs/api-references/events/CatalogV2/item-purchased.md
@@ -0,0 +1,37 @@
+---
+title: item_purchased
+author: ernestoc
+description: item_purchased event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# item_purchased
+
+This event is triggered when an item is purchased.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| CollectionId | String | The id of the collection the item was added to. |
+| Currencies | List<[ItemPurchasedCurrency](../data-types/itempurchasedcurrency.md)> | The set of currencies used to pay for the item. |
+| IdempotencyId | String | The idempotency id. |
+| ItemId | String | The id of the purchased item. |
+| ItemsAmountsOverrides | List<[ItemPurchasedOverride](../data-types/itempurchasedoverride.md)> | The set of overrides used to alter item amounts. |
+| ItemType | String | The type of the purchased item. |
+| OverrideSource | String | The source of the overrides used in the purchase. |
+| PayoutAmountOverride | [ItemPurchasedOverride](../data-types/itempurchasedoverride.md) | The override used to alter the payout of the purchase. |
+| PriceAmountsOverrides | List<[ItemPurchasedOverride](../data-types/itempurchasedoverride.md)> | The set of overrides used to alter the price in the purchase. |
+| Quantity | uint64 | The quantity of purchased items. |
+| StoreId | String | The optional id of the store. |
+| TransactionDateTime | String | Timestamp of the transaction in ISO-8601 format. |
+| TransactionId | String | The id of the transaction which added this item. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/CatalogV2/item-reported.md b/playfab-docs/api-references/events/CatalogV2/item-reported.md
new file mode 100644
index 000000000..07b2750ae
--- /dev/null
+++ b/playfab-docs/api-references/events/CatalogV2/item-reported.md
@@ -0,0 +1,29 @@
+---
+title: item_reported
+author: ernestoc
+description: ItemReported event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# item_reported
+
+This event is triggered when an item is reported.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| ItemId | String | The string ID of the item that was reported. |
+| ItemType | String | The string type of the item that was reported. |
+| CreatorEntityKey | [EntityKey](../data-types/entitykey.md) | The item's creator. |
+| ConcernCategory | String | The category for which this item was reported. |
+| Reason | String | The reason for which this item was reported. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/CatalogV2/item-updated.md b/playfab-docs/api-references/events/CatalogV2/item-updated.md
new file mode 100644
index 000000000..2e1c8c64b
--- /dev/null
+++ b/playfab-docs/api-references/events/CatalogV2/item-updated.md
@@ -0,0 +1,26 @@
+---
+title: item_updated
+author: fprotti96
+description: ItemUpdated event.
+ms.author: fprotti
+ms.date: 09/29/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# item_updated
+
+This event is triggered when an item is updated.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| ItemId | String | The string ID of the item that was updated. |
+| ItemType | String | The string type of the item that was updated. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/CatalogV2/review-reported.md b/playfab-docs/api-references/events/CatalogV2/review-reported.md
new file mode 100644
index 000000000..1c5f1ecba
--- /dev/null
+++ b/playfab-docs/api-references/events/CatalogV2/review-reported.md
@@ -0,0 +1,29 @@
+---
+title: review_reported
+author: ernestoc
+description: ReviewReported event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# review_reported
+
+This event is triggered when a review is reported.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| ItemId | String | The string ID of the item associated with the review. |
+| ReviewId | String | The string ID of the review being reported. |
+| ConcernCategory | String | The category for which this review was reported. |
+| Reason | String | The string reason for this report. |
+| CreatorEntityKey | [EntityKey](../data-types/entitykey.md) | The EntityKey of the creator of the review that was reported. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/CatalogV2/reviews-takedown-requested.md b/playfab-docs/api-references/events/CatalogV2/reviews-takedown-requested.md
new file mode 100644
index 000000000..37ce51c63
--- /dev/null
+++ b/playfab-docs/api-references/events/CatalogV2/reviews-takedown-requested.md
@@ -0,0 +1,25 @@
+---
+title: reviews_takedown_requested
+author: fprotti96
+description: ReviewsTakedownRequested event.
+ms.author: fprotti
+ms.date: 09/29/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# reviews_takedown_requested
+
+Event trigged when a takedown of reviews is requested.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| Reviews | List<[ReviewTakedown](../data-types/review-takedown.md)> | The reviews to be taken down. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Character/character-consumed-item.md b/playfab-docs/api-references/events/Character/character-consumed-item.md
new file mode 100644
index 000000000..7c05b5185
--- /dev/null
+++ b/playfab-docs/api-references/events/Character/character-consumed-item.md
@@ -0,0 +1,31 @@
+---
+title: character_consumed_item
+author: ernestoc
+description: character_consumed_item event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# character_consumed_item
+
+This event is triggered when a character consumes an item from their inventory.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| CatalogVersion | String | Version of the catalog from which the consumed inventory item was created. |
+| ItemId | String | ID of the catalog item from which the consumed inventory item was created. This can be used to look up the item from the catalog. |
+| ItemInstanceId | String | The specific ID of the item that was consumed. |
+| PlayerId | String |  |
+| PreviousUsesRemaining | uint32 | For multiple use items, the number of uses that remained before the item was consumed. |
+| TitleId | String |  |
+| UsesRemaining | uint32 | For multiple use items, the number of uses remaining after the item was consumed. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Character/character-inventory-item-added.md b/playfab-docs/api-references/events/Character/character-inventory-item-added.md
new file mode 100644
index 000000000..00accff65
--- /dev/null
+++ b/playfab-docs/api-references/events/Character/character-inventory-item-added.md
@@ -0,0 +1,36 @@
+---
+title: character_inventory_item_added
+author: ernestoc
+description: character_inventory_item_added event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# character_inventory_item_added
+
+This event is triggered when an item is granted to a character.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| Annotation | String | Optional details about the inventory item. |
+| BundleContents | [] | Catalog item IDs of any other items granted to the character along with this one as part of a bundle. |
+| CatalogVersion | String | Catalog version in which the item that was added is defined. |
+| Class | String | Class of the item that was added. |
+| CouponCode | String | Redeemed coupon (if any) that granted the item. |
+| DisplayName | String | Display name of the item that was added. |
+| Expiration | DateTime | When the item expires. The value is null if the item does not expire. |
+| InstanceId | String | Unique instance ID of the inventory item that was added. |
+| ItemId | String | Catalog item ID of the inventory item that was added. |
+| PlayerId | String |  |
+| RemainingUses | uint32 | How many uses the item has, if it has a limited number of uses. |
+| TitleId | String |  |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Character/character-vc-item-purchased.md b/playfab-docs/api-references/events/Character/character-vc-item-purchased.md
new file mode 100644
index 000000000..7a60cfa50
--- /dev/null
+++ b/playfab-docs/api-references/events/Character/character-vc-item-purchased.md
@@ -0,0 +1,33 @@
+---
+title: character_vc_item_purchased
+author: ernestoc
+description: character_vc_item_purchased event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# character_vc_item_purchased
+
+This event is triggered when the character makes a purchase using virtual currency.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| CatalogVersion | String | Version of the catalog from which the item was purchased. |
+| CurrencyCode | String | Currency that was used to purchase the item. |
+| ItemId | String | Identifier of the catalog item that was purchased. |
+| PlayerId | String |  |
+| PurchaseId | String | Unique identifier of the purchase transaction. |
+| Quantity | int32 | Quantity of items that were purchased. |
+| StoreId | String | The StoreId where the item was purchased. |
+| TitleId | String |  |
+| UnitPrice | uint32 | Price paid per item, expressed in the virtual currency. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Character/character-virtual-currency-balance-changed.md b/playfab-docs/api-references/events/Character/character-virtual-currency-balance-changed.md
new file mode 100644
index 000000000..17935b139
--- /dev/null
+++ b/playfab-docs/api-references/events/Character/character-virtual-currency-balance-changed.md
@@ -0,0 +1,30 @@
+---
+title: character_virtual_currency_balance_changed
+author: ernestoc
+description: character_virtual_currency_balance_changed event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# character_virtual_currency_balance_changed
+
+This event is triggered when a character's virtual currency balance changes.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| OrderId | String | ID of the order that triggered the balance changes. |
+| PlayerId | String |  |
+| TitleId | String |  |
+| VirtualCurrencyBalance | int32 | New virtual currency balance after the change. |
+| VirtualCurrencyName | String | Virtual currency whose balance changed. |
+| VirtualCurrencyPreviousBalance | int32 | Old virtual currency balance before the change. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/CloudScript/cloudscript-executed.md b/playfab-docs/api-references/events/CloudScript/cloudscript-executed.md
new file mode 100644
index 000000000..04ebaba06
--- /dev/null
+++ b/playfab-docs/api-references/events/CloudScript/cloudscript-executed.md
@@ -0,0 +1,27 @@
+---
+title: cloudscript_executed
+author: ronnyparedes
+description: cloudscript_executed event.
+ms.author: ronnyparedes
+ms.date: 02/06/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# cloudscript_executed
+
+This event is triggered when a CloudScript function is executed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CloudScriptExecutionResult|[ExecuteCloudScriptResult](../data-types/executecloudscriptresult.md)|The details of the execution result.|
+|FunctionName|String|Name of the CloudScript function that was executed.|
+|Source|String|The source that caused the function to be executed; PlayStreamV2, Task.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/CloudScript/entity-executed-cloud-script.md b/playfab-docs/api-references/events/CloudScript/entity-executed-cloud-script.md
new file mode 100644
index 000000000..d11f611b6
--- /dev/null
+++ b/playfab-docs/api-references/events/CloudScript/entity-executed-cloud-script.md
@@ -0,0 +1,28 @@
+---
+title: entity_executed_cloud_script
+author: joannaleecy
+description: entity_executed_cloud_script event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# entity_executed_cloud_script
+
+This event is optionally triggered when a CloudScript function is executed by calling the ExecuteEntityCloudScript API. If you want the Event logged, you can pass in GeneratePlayStreamEvent.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CloudScriptExecutionResult|[ExecuteCloudScriptResult](../data-types/executecloudscriptresult.md)|Result of the CloudScript function, including diagnostic information that's useful for debugging.|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|FunctionName|String|Name of the CloudScript function that was called.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/CloudScript/player-executed-cloudscript.md b/playfab-docs/api-references/events/CloudScript/player-executed-cloudscript.md
new file mode 100644
index 000000000..08579b360
--- /dev/null
+++ b/playfab-docs/api-references/events/CloudScript/player-executed-cloudscript.md
@@ -0,0 +1,27 @@
+---
+title: player_executed_cloudscript
+author: joannaleecy
+description: player_executed_cloudscript event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_executed_cloudscript
+
+This event is optionally triggered when a CloudScript function is executed, either by calling the ExecuteCloudScript API with the GeneratePlayStreamEvent option or triggered by a PlayStream event action with the 'Publish results as a PlayStream Event' box checked.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CloudScriptExecutionResult|[ExecuteCloudScriptResult](../data-types/executecloudscriptresult.md)|Result of the CloudScript function, including diagnostic information that's useful for debugging.|
+|FunctionName|String|Name of the CloudScript function that was called.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/CloudScript/player-triggered-action-executed-cloudscript.md b/playfab-docs/api-references/events/CloudScript/player-triggered-action-executed-cloudscript.md
new file mode 100644
index 000000000..55cf4e3c0
--- /dev/null
+++ b/playfab-docs/api-references/events/CloudScript/player-triggered-action-executed-cloudscript.md
@@ -0,0 +1,30 @@
+---
+title: player_triggered_action_executed_cloudscript
+author: joannaleecy
+description: player_triggered_action_executed_cloudscript event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_triggered_action_executed_cloudscript
+
+This event is triggered when a CloudScript function is run as the result of a PlayStream action, and the 'Publish results as a PlayStream Event' box was checked.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CloudScriptExecutionResult|[ExecuteCloudScriptResult](../data-types/executecloudscriptresult.md)|Result of the CloudScript function, including an error information. Useful for debugging.|
+|FunctionName|String|Name of the CloudScript function that was called.|
+|TitleId|String|The ID of the title to which this player event applies.|
+|TriggeringEventData|object|The full JSON data of the event that triggered this CloudScript function to run. Useful for debugging.|
+|TriggeringEventName|String|Name of the event that triggered this CloudScript function to run.|
+|TriggeringPlayer|[PlayerProfile](../data-types/playerprofile.md)|JSON data profile of the player that triggered this CloudScript function to run.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/CloudScript/title-added-cloudscript.md b/playfab-docs/api-references/events/CloudScript/title-added-cloudscript.md
new file mode 100644
index 000000000..18f22de08
--- /dev/null
+++ b/playfab-docs/api-references/events/CloudScript/title-added-cloudscript.md
@@ -0,0 +1,30 @@
+---
+title: title_added_cloudscript
+author: joannaleecy
+description: title_added_cloudscript event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_added_cloudscript
+
+This event is triggered when new CloudScript is uploaded to PlayFab.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|Published|Boolean|Whether the CloudScript that was uploaded is live.|
+|Revision|int32|Revision number of the CloudScript file that was added.|
+|ScriptNames|[]|Names of the individual script files modified. Currently this is just 'CloudScript.js' but later we'll support multiple files.|
+|UserId|String||
+|Version|int32|Version number of the CloudScript file that was added.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/CloudScript/title-published-cloudscript.md b/playfab-docs/api-references/events/CloudScript/title-published-cloudscript.md
new file mode 100644
index 000000000..ef282187f
--- /dev/null
+++ b/playfab-docs/api-references/events/CloudScript/title-published-cloudscript.md
@@ -0,0 +1,27 @@
+---
+title: title_published_cloudscript
+author: joannaleecy
+description: title_published_cloudscript event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_published_cloudscript
+
+An inactive revision of CloudScript has been made into the active 'live' version.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|Revision|int32|Revision number of the CloudScript that was activated.|
+|UserId|String||
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/CloudScript/title-scheduled-cloudscript-executed.md b/playfab-docs/api-references/events/CloudScript/title-scheduled-cloudscript-executed.md
new file mode 100644
index 000000000..bf3e55063
--- /dev/null
+++ b/playfab-docs/api-references/events/CloudScript/title-scheduled-cloudscript-executed.md
@@ -0,0 +1,27 @@
+---
+title: title_scheduled_cloudscript_executed
+author: joannaleecy
+description: title_scheduled_cloudscript_executed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_scheduled_cloudscript_executed
+
+This event is triggered when a CloudScript function is run by a scheduled task.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CloudScriptExecutionResult|[ExecuteCloudScriptResult](../data-types/executecloudscriptresult.md)|Result of the CloudScript function, including an error information. Useful for debugging.|
+|FunctionName|String|Name of the CloudScript function that was called.|
+|ScheduledTask|[NameId](../data-types/nameid.md)|Scheduled task that called the CloudScript|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/DeveloperIdentity/studio-created.md b/playfab-docs/api-references/events/DeveloperIdentity/studio-created.md
new file mode 100644
index 000000000..96542a1f8
--- /dev/null
+++ b/playfab-docs/api-references/events/DeveloperIdentity/studio-created.md
@@ -0,0 +1,27 @@
+---
+title: studio_created
+author: joannaleecy
+description: studio_created event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# studio_created
+
+This event is triggered when a studio is created.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CreatorAuthenticationId|String|Authentication provider's id for the user who created the studio|
+|CreatorPlayFabId|String|PlayFab id of the user who created the studio|
+|StudioName|String|Name of the new studio|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/DeveloperIdentity/studio-user-added.md b/playfab-docs/api-references/events/DeveloperIdentity/studio-user-added.md
new file mode 100644
index 000000000..167183312
--- /dev/null
+++ b/playfab-docs/api-references/events/DeveloperIdentity/studio-user-added.md
@@ -0,0 +1,30 @@
+---
+title: studio_user_added
+author: joannaleecy
+description: studio_user_added event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# studio_user_added
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AuthenticationId|String|Authentication provider's ID for this user|
+|AuthenticationProvider|[AuthenticationProvider](../data-types/authenticationprovider.md)|Authentication provider for the user|
+|AuthenticationProviderId|String|Authentication provider entity id, if needed by the provider|
+|Email|String|User's email|
+|InvitationId|String|Id of the invitation record if user needed to register|
+|PlayFabId|String|PlayFab ID for this user|
+|StudioPermissions|[]|Array of studio permissions that were be granted to the user|
+|TitlePermissions|Object|Dictionary of title id, title permissions that were granted to the user|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/DeveloperIdentity/studio-user-invited.md b/playfab-docs/api-references/events/DeveloperIdentity/studio-user-invited.md
new file mode 100644
index 000000000..8b7d90640
--- /dev/null
+++ b/playfab-docs/api-references/events/DeveloperIdentity/studio-user-invited.md
@@ -0,0 +1,33 @@
+---
+title: studio_user_invited
+author: joannaleecy
+description: studio_user_invited event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# studio_user_invited
+
+This event is triggererd when a user is invited to a studio.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AuthenticationProvider|[AuthenticationProvider](../data-types/authenticationprovider.md)|Authentication provider type required for user to register with|
+|AuthenticationProviderId|String|Authentication provider entity id, if needed by the provider.|
+|Email|String|Email the invitation was sent to|
+|InvitationExpires|DateTime|Expiration of the invitation|
+|InvitationId|String|Id of the invitation if user needed to register|
+|InvitedExistingUser|Boolean|Indicates if the user invited already existed, if so no invitation record was created and the user was automatically attached|
+|InvitorPlayFabId|String|Identity of the user who created the invitation|
+|StudioPermissions|[]|Array of studio permissions which will be granted to the user when registering|
+|TitlePermissions|Object|Dictionary of title id, title permissions which will be granted to the user when registering|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/DeveloperIdentity/studio-user-removed.md b/playfab-docs/api-references/events/DeveloperIdentity/studio-user-removed.md
new file mode 100644
index 000000000..0acee9dc5
--- /dev/null
+++ b/playfab-docs/api-references/events/DeveloperIdentity/studio-user-removed.md
@@ -0,0 +1,31 @@
+---
+title: studio_user_removed
+author: joannaleecy
+description: studio_user_removed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# studio_user_removed
+
+This event is triggered when a user is removed from a studio.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AuthenticationId|String|Authentication provider's ID for this user|
+|AuthenticationProvider|[AuthenticationProvider](../data-types/authenticationprovider.md)|Authentication provider for the user|
+|AuthenticationProviderId|String|Authentication provider entity id, if needed by the provider|
+|PlayFabId|String|PlayFab ID for this user|
+|StudioPermissions|[]|Array of studio permissions that the user had|
+|TitlePermissions|Object|Dictionary of title id, title permissions that the user had|
+
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Experimentation/exclusion-group-created.md b/playfab-docs/api-references/events/Experimentation/exclusion-group-created.md
new file mode 100644
index 000000000..e0648f95c
--- /dev/null
+++ b/playfab-docs/api-references/events/Experimentation/exclusion-group-created.md
@@ -0,0 +1,27 @@
+---
+title: exclusion_group_created
+author: joelku
+description: exclusion_group_created event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# exclusion_group_created
+
+This event is triggered when an exclusion group is created.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|The unique identifier of the exclusion group.|
+|Name|String|Friendly name of the exclusion group.|
+|Description|String|Description of the exclusion group.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Experimentation/exclusion-group-deleted.md b/playfab-docs/api-references/events/Experimentation/exclusion-group-deleted.md
new file mode 100644
index 000000000..0eddc7b9f
--- /dev/null
+++ b/playfab-docs/api-references/events/Experimentation/exclusion-group-deleted.md
@@ -0,0 +1,25 @@
+---
+title: exclusion_group_deleted
+author: joelku
+description: exclusion_group_deleted event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# exclusion_group_deleted
+
+This event is triggered when an exclusion group is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|The unique identifier of the exclusion group.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Experimentation/exclusion-group-updated.md b/playfab-docs/api-references/events/Experimentation/exclusion-group-updated.md
new file mode 100644
index 000000000..2e4eb7a74
--- /dev/null
+++ b/playfab-docs/api-references/events/Experimentation/exclusion-group-updated.md
@@ -0,0 +1,27 @@
+---
+title: exclusion_group_updated
+author: joelku
+description: exclusion_group_updated event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# exclusion_group_updated
+
+This event is triggered when an exclusion group is updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|The unique identifier of the exclusion group.|
+|Name|String|Friendly name of the exclusion group.|
+|Description|String|Description of the exclusion group.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Experimentation/experiment-created.md b/playfab-docs/api-references/events/Experimentation/experiment-created.md
new file mode 100644
index 000000000..4c1050afd
--- /dev/null
+++ b/playfab-docs/api-references/events/Experimentation/experiment-created.md
@@ -0,0 +1,29 @@
+---
+title: experiment_created
+author: joelku
+description: experiment_created event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# experiment_created
+
+This event is triggered when an experiment is created.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|The unique identifier of the experiment.|
+|Name|String|The friendly name of the experiment.|
+|UsesOverrides|Boolean|Specifies whether the experiment uses title data overrides.|
+|UsesExclusionGroup|Boolean|Specifies whether the experiment uses an exclusion group.|
+|Experiment|[Experiment](../data-types/experiment.md)|The experiment configuration payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Experimentation/experiment-deleted.md b/playfab-docs/api-references/events/Experimentation/experiment-deleted.md
new file mode 100644
index 000000000..85ff9eb78
--- /dev/null
+++ b/playfab-docs/api-references/events/Experimentation/experiment-deleted.md
@@ -0,0 +1,26 @@
+---
+title: experiment_deleted
+author: joelku
+description: experiment_deleted event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# experiment_deleted
+
+This event is triggered when an experiment is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|The unique identifier of the experiment.|
+|Name|String|The friendly name of the experiment.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Experimentation/experiment-start-requested.md b/playfab-docs/api-references/events/Experimentation/experiment-start-requested.md
new file mode 100644
index 000000000..337d0c305
--- /dev/null
+++ b/playfab-docs/api-references/events/Experimentation/experiment-start-requested.md
@@ -0,0 +1,30 @@
+---
+title: experiment_start_requested
+author: joelku
+description: experiment_start_requested event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# experiment_start_requested
+
+This event is triggered when an experiment is requested to start.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|The unique identifier of the experiment.|
+|Name|String|The friendly name of the experiment.|
+|UsesOverrides|Boolean|Specifies whether the experiment uses title data overrides.|
+|UsesExclusionGroup|Boolean|Specifies whether the experiment uses an exclusion group.|
+|RequestOrigin|[ExperimentRequestOrigin](../data-types/experimentrequestorigin.md)|The origin of the request to start the experiment.|
+|Experiment|[Experiment](../data-types/experiment.md)|The experiment configuration payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Experimentation/experiment-stop-requested.md b/playfab-docs/api-references/events/Experimentation/experiment-stop-requested.md
new file mode 100644
index 000000000..df990f6ed
--- /dev/null
+++ b/playfab-docs/api-references/events/Experimentation/experiment-stop-requested.md
@@ -0,0 +1,27 @@
+---
+title: experiment_stop_requested
+author: joelku
+description: experiment_stop_requested event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# experiment_stop_requested
+
+This event is triggered when an experiment is requested to stop.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|The unique identifier of the experiment.|
+|Name|String|The friendly name of the experiment.|
+|RequestOrigin|[ExperimentRequestOrigin](../data-types/experimentrequestorigin.md)|The origin of the request to stop the experiment.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Experimentation/experiment-updated.md b/playfab-docs/api-references/events/Experimentation/experiment-updated.md
new file mode 100644
index 000000000..ecaaef18c
--- /dev/null
+++ b/playfab-docs/api-references/events/Experimentation/experiment-updated.md
@@ -0,0 +1,29 @@
+---
+title: experiment_updated
+author: joelku
+description: experiment_updated event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# experiment_updated
+
+This event is triggered when an experiment is updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|The unique identifier of the experiment.|
+|Name|String|The friendly name of the experiment.|
+|UsesOverrides|Boolean|Specifies whether the experiment uses title data overrides.|
+|UsesExclusionGroup|Boolean|Specifies whether the experiment uses an exclusion group.|
+|Experiment|[Experiment](../data-types/experiment.md)|The experiment configuration payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Experimentation/player-experiment-variants-changed.md b/playfab-docs/api-references/events/Experimentation/player-experiment-variants-changed.md
new file mode 100644
index 000000000..d96ab8827
--- /dev/null
+++ b/playfab-docs/api-references/events/Experimentation/player-experiment-variants-changed.md
@@ -0,0 +1,26 @@
+---
+title: player_experiment_variants_changed
+author: joelku
+description: player_experiment_variants_changed event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_experiment_variants_changed
+
+This event is triggered when a player's set of experiment variants is changed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|PreviousExperimentVariants|String[]|Previous experiment variant list.|
+|ExperimentVariants|String[]|New experiment variant list.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Extension/export-completed.md b/playfab-docs/api-references/events/Extension/export-completed.md
new file mode 100644
index 000000000..f5b0ab4f2
--- /dev/null
+++ b/playfab-docs/api-references/events/Extension/export-completed.md
@@ -0,0 +1,30 @@
+---
+title: export_completed
+author: ronnyparedes
+description: export_completed event.
+ms.author: ronnyparedes
+ms.date: 02/09/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# export_completed
+
+This event is triggered when an export operation is completed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Artifacts|[Artifact](../data-types/artifact.md)[]|An array of artifact objects representing the exported files or resources.|
+|FailureReason|String|The reason for the export failure, if the export did not succeed.|
+|Id|String|The unique identifier for this export operation.|
+|Name|String|The name of the export operation.|
+|StartTime|DateTime|The timestamp when the export operation started.|
+|Status|[EventExportCompletionStatus](../data-types/eventexportcompletionstatus.md)|The status of the export operation indicating whether it succeeded, failed, or was cancelled.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Extension/title-aborted-task.md b/playfab-docs/api-references/events/Extension/title-aborted-task.md
new file mode 100644
index 000000000..af0b74882
--- /dev/null
+++ b/playfab-docs/api-references/events/Extension/title-aborted-task.md
@@ -0,0 +1,27 @@
+---
+title: title_aborted_task
+author: joannaleecy
+description: title_aborted_task event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_aborted_task
+
+This event is triggered when a task instance is aborted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|TaskInstanceId|String|ID of the aborted task instance|
+|UserId|String||
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Extension/title-completed-task.md b/playfab-docs/api-references/events/Extension/title-completed-task.md
new file mode 100644
index 000000000..01a0be65a
--- /dev/null
+++ b/playfab-docs/api-references/events/Extension/title-completed-task.md
@@ -0,0 +1,30 @@
+---
+title: title_completed_task
+author: joannaleecy
+description: title_completed_task event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_completed_task
+
+This event is triggered when a scheduled task has completed
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AbortedAt|DateTime|Timestamp on when the task was aborted. Null if task never was aborted.|
+|IsAborted|Boolean|Whether the task was aborted.|
+|Result|[TaskInstanceStatus](../data-types/taskinstancestatus.md)|Result of the task run, whether it has succeeded, failed or aborted.|
+|Summary|object|Summary of the task run. Different task types have different summary structure.|
+|TaskInstanceId|String|ID of the running instance of the task|
+|TaskType|String|Type of the scheduled task|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Extension/title-created-task.md b/playfab-docs/api-references/events/Extension/title-created-task.md
new file mode 100644
index 000000000..baa3a757f
--- /dev/null
+++ b/playfab-docs/api-references/events/Extension/title-created-task.md
@@ -0,0 +1,26 @@
+---
+title: title_created_task
+author: joannaleecy
+description: title_created_task event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_created_task
+
+This event is triggered when a task is created.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|ScheduledTask|[NameIdentifier](../data-types/nameidentifier.md)|Identity of the scheduled task|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Extension/title-deleted-task.md b/playfab-docs/api-references/events/Extension/title-deleted-task.md
new file mode 100644
index 000000000..562a0e672
--- /dev/null
+++ b/playfab-docs/api-references/events/Extension/title-deleted-task.md
@@ -0,0 +1,28 @@
+---
+title: title_deleted_task
+author: joannaleecy
+description: title_deleted_task event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_deleted_task
+
+This event is triggered when a task is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|ScheduledTask|[NameIdentifier](../data-types/nameidentifier.md)|Identity of the scheduled task|
+|UserId|String||
+
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Extension/title-exceeded-limit.md b/playfab-docs/api-references/events/Extension/title-exceeded-limit.md
new file mode 100644
index 000000000..25a501a11
--- /dev/null
+++ b/playfab-docs/api-references/events/Extension/title-exceeded-limit.md
@@ -0,0 +1,30 @@
+---
+title: title_exceeded_limit
+author: joannaleecy
+description: title_exceeded_limit event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_exceeded_limit
+
+This event is triggered when a title exceeds a service limit and receives an error.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Details|Object|Additional details about the exceeded limit|
+|LimitDisplayName|String|The display name of the limit that was exceeded.|
+|LimitId|String|The unique identifier of the limit that was exceeded.|
+|LimitValue|double|The limit value that was exceeded.|
+|Unit|[MetricUnit](../data-types/metricunit.md)|The unit of the limit that was exceeded.|
+|Value|double|The value that exceeded the limit.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Extension/title-limit-changed.md b/playfab-docs/api-references/events/Extension/title-limit-changed.md
new file mode 100644
index 000000000..5bed689a0
--- /dev/null
+++ b/playfab-docs/api-references/events/Extension/title-limit-changed.md
@@ -0,0 +1,32 @@
+---
+title: title_limit_changed
+author: joannaleecy
+description: title_limit_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_limit_changed
+
+This event is triggered when a title changes a service limit.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|LimitDisplayName|String|The display name of the limit that changed.|
+|LimitId|String|The unique identifier of the limit that changed.|
+|PreviousPriceUSD|double|The price of the limit level in US Dollars before the change, if any.|
+|PreviousValue|double|The limit value before the change, if any.|
+|PriceUSD|double|The price of the limit level in US Dollars, if any.|
+|TransactionId|String|The unique identifier of the limit change transaction.|
+|Unit|[MetricUnit](../data-types/metricunit.md)|The unit of the limit that changed.|
+|Value|double|The limit value after the change, if any.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Extension/title-started-task.md b/playfab-docs/api-references/events/Extension/title-started-task.md
new file mode 100644
index 000000000..a9ffb5cc3
--- /dev/null
+++ b/playfab-docs/api-references/events/Extension/title-started-task.md
@@ -0,0 +1,31 @@
+---
+title: title_started_task
+author: joannaleecy
+description: title_started_task event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_started_task
+
+This event is triggered when a task is scheduled to run.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|Parameter|object|Parameter of the scheduled task|
+|ScheduledByUserId|String|ID of user who manually scheduled the task, null if scheduled automatically|
+|ScheduledTask|[NameIdentifier](../data-types/nameidentifier.md)|Identity of the scheduled task|
+|TaskInstanceId|String|ID of the running instance of the task|
+|TaskType|String|Type of the scheduled task|
+|UserId|String||
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Extension/title-updated-task.md b/playfab-docs/api-references/events/Extension/title-updated-task.md
new file mode 100644
index 000000000..603940b6f
--- /dev/null
+++ b/playfab-docs/api-references/events/Extension/title-updated-task.md
@@ -0,0 +1,28 @@
+---
+title: title_updated_task
+author: joannaleecy
+description: title_updated_task event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_updated_task
+
+This event is triggered when a task is updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|HasRenamed|Boolean||
+|ScheduledTask|[NameIdentifier](../data-types/nameidentifier.md)|Identity of the scheduled task|
+|UserId|String||
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Functions/function-executed.md b/playfab-docs/api-references/events/Functions/function-executed.md
new file mode 100644
index 000000000..73095f966
--- /dev/null
+++ b/playfab-docs/api-references/events/Functions/function-executed.md
@@ -0,0 +1,29 @@
+---
+title: function_executed
+author: joannaleecy
+description: function_executed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# function_executed
+
+This event is triggered when a CloudScript function is executed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ExecutionTimeMilliseconds|int|The execution time of the function in milliseconds.|
+|FunctionName|String|The name of the function that was executed.|
+|Result|[ExecuteFunctionResult](../data-types/executefunctionresult.md)|The result returned by the function execution.|
+|ResultTooLarge|Boolean|Indicates if the result was too large to return and was truncated.|
+|Source|String|The source or trigger that caused the function to execute.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Functions/function-registered.md b/playfab-docs/api-references/events/Functions/function-registered.md
new file mode 100644
index 000000000..238697ce6
--- /dev/null
+++ b/playfab-docs/api-references/events/Functions/function-registered.md
@@ -0,0 +1,25 @@
+---
+title: function_registered
+author: joannaleecy
+description: function_registered event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# function_registered
+
+This event is triggered when a CloudScript function is registered.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|FunctionName|String|The name of the function that was registered.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Functions/function-unregistered.md b/playfab-docs/api-references/events/Functions/function-unregistered.md
new file mode 100644
index 000000000..a75e9db6a
--- /dev/null
+++ b/playfab-docs/api-references/events/Functions/function-unregistered.md
@@ -0,0 +1,25 @@
+---
+title: function_unregistered
+author: joannaleecy
+description: function_unregistered event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# function_unregistered
+
+This event is triggered when a CloudScript function is unregistered.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|FunctionName|String|The name of the function that was unregistered.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Functions/player-triggered-action-executed-function.md b/playfab-docs/api-references/events/Functions/player-triggered-action-executed-function.md
new file mode 100644
index 000000000..42cbf7518
--- /dev/null
+++ b/playfab-docs/api-references/events/Functions/player-triggered-action-executed-function.md
@@ -0,0 +1,30 @@
+---
+title: player_triggered_action_executed_function
+author: joannaleecy
+description: player_triggered_action_executed_function event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_triggered_action_executed_function
+
+This event is triggered when a CloudScript Azure Function is run as the result of a PlayStream action, and the 'Publish results as a PlayStream Event' box was checked.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|FunctionExecutionResult|[ExecuteFunctionResult](../data-types/executefunctionresult.md)|Result of the CloudScript Azure Function.|
+|FunctionName|String|Name of the CloudScript Azure Function that was called.|
+|TriggeringEventData|Object|The full JSON data of the event that triggered this CloudScript function to run. Useful for debugging.|
+|TriggeringEventName|String|Name of the event that triggered this CloudScript function to run.|
+|TriggeringPlayer|[PlayerProfile](../data-types/playerprofile.md)|JSON data profile of the player that triggered this CloudScript function to run.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Functions/title-scheduled-function-executed.md b/playfab-docs/api-references/events/Functions/title-scheduled-function-executed.md
new file mode 100644
index 000000000..4da6bd7bf
--- /dev/null
+++ b/playfab-docs/api-references/events/Functions/title-scheduled-function-executed.md
@@ -0,0 +1,27 @@
+---
+title: title_scheduled_function_executed
+author: joannaleecy
+description: title_scheduled_function_executed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_scheduled_function_executed
+
+This event is triggered when a scheduled CloudScript function is executed for a title.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|FunctionExecutionResult|[ExecuteFunctionResult](../data-types/executefunctionresult.md)|The result returned from executing the scheduled function.|
+|FunctionName|String|The name of the scheduled function that was executed.|
+|ScheduledTask|[NameId](../data-types/nameid.md)|The scheduled task that triggered this function execution.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/GameSave/gamesave-version-finalized.md b/playfab-docs/api-references/events/GameSave/gamesave-version-finalized.md
new file mode 100644
index 000000000..d885ea78c
--- /dev/null
+++ b/playfab-docs/api-references/events/GameSave/gamesave-version-finalized.md
@@ -0,0 +1,34 @@
+---
+title: gamesave_version_finalized
+author: alzakrze
+description: gamesave_version_finalized event.
+ms.author: alzakrze
+ms.date: 01/22/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events, gamesave
+ms.localizationpriority: medium
+---
+
+# gamesave_version_finalized
+
+This event is triggered when a game save version is finalized with all the files fully uploaded.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Version|Int64|The version of the game save that was finalized.|
+|PlayerIdentityProvider|String|The login identity provider used by the player uploading the game save.|
+|DeviceType|String|The type of device used for this game save version.|
+|FinalizedAt|DateTime|The time at which the game save version was finalized.|
+|NewFileCount|Int32|The number of new files that were added to the game save store for this version.|
+|NewFilesSizeBytes|Int64|The size in bytes of the new files that were added to the game save store for this version.|
+|TotalFileCount|Int32|The total number of files that were included in the finalized game save version.|
+|TotalSizeBytes|Int64|The total size in bytes of the finalized game save version, including all files.|
+|IsGeneratedByRollback|Boolean|Whether the version was generated and finalized by a rollback operation.|
+|Conflict|[GameSaveConflict](../data-types/gamesaveconflict.md)|Data about any conflict that occurred during the finalization of the game save version. This will usually be null if the version was not finalized during a conflict resolution operation.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/GameSave/gamesave-version-marked-known-good.md b/playfab-docs/api-references/events/GameSave/gamesave-version-marked-known-good.md
new file mode 100644
index 000000000..0bf2fbc91
--- /dev/null
+++ b/playfab-docs/api-references/events/GameSave/gamesave-version-marked-known-good.md
@@ -0,0 +1,26 @@
+---
+title: gamesave_version_marked_known_good
+author: alzakrze
+description: gamesave_version_marked_known_good event.
+ms.author: alzakrze
+ms.date: 01/22/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events, gamesave
+ms.localizationpriority: medium
+---
+
+# gamesave_version_marked_known_good
+
+This event is triggered when a game save version is marked as known good.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|MarkedAt|DateTime|The time at which the game save version was marked as known good.|
+|Version|Int64|The version of the game save that was marked as known good.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/General/entity-virtual-currency-balances-changed.md b/playfab-docs/api-references/events/General/entity-virtual-currency-balances-changed.md
new file mode 100644
index 000000000..8aa3135fc
--- /dev/null
+++ b/playfab-docs/api-references/events/General/entity-virtual-currency-balances-changed.md
@@ -0,0 +1,30 @@
+---
+title: entity_virtual_currency_balances_changed
+author: joannaleecy
+description: entity_virtual_currency_balances_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# entity_virtual_currency_balances_changed
+
+This event is triggered when an entity's virtual currency balance changes.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|SequenceId|String|Sequence id of the balance change to ensure updates are processed in order.|
+|VirtualCurrencyBalances|Object|New virtual currency balances after the change. Only shows currencies that were updated.|
+|VirtualCurrencyContainerId|String|Container whose balances changed.|
+|VirtualCurrencyPreviousBalances|Object|Old virtual currency balances before the change. Only shows currencies that were updated.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/General/studio-tier-updated.md b/playfab-docs/api-references/events/General/studio-tier-updated.md
new file mode 100644
index 000000000..ae6017eda
--- /dev/null
+++ b/playfab-docs/api-references/events/General/studio-tier-updated.md
@@ -0,0 +1,37 @@
+---
+title: studio_tier_updated
+author: joannaleecy
+description: studio_tier_updated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# studio_tier_updated
+
+This event is triggered when a studio tier is updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ContactCompanyName|String|Contact Company Name|
+|IsPayAsYouGo|Boolean|IsPayAsYouGo PaymentOption|
+|IsReservedCapacity|Boolean|IsReservedCapacity PaymentOption|
+|IsReservedCapacityAnnual|Boolean|IsReservedCapacityAnnual PaymentOption|
+|MonthlyMinimumUSD|double|Monthly Minimum Price in USD|
+|OveragePricePerMauTiers|[PaymentOptionPerMauPriceTier](../data-types/paymentoptionpermaupricetier.md)|OveragePricePerMauTiers Definitions|
+|PaymentSystemAccountId|String|Payment System AccountId|
+|PricePerMauTiers|[PaymentOptionPerMauPriceTier](../data-types/paymentoptionpermaupricetier.md)|PricePerMauTiers Definitions|
+|ReservedMAU|int32|Reserved Capacity MAU|
+|StudioIds|IEnumerable_String|Studio Ids|
+|TierDisplayName|String|Tier Display Name|
+|TierId|String|Tier Id|
+|TransactionId|String|Transaction Id|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/General/tenancy-connector-onboard.md b/playfab-docs/api-references/events/General/tenancy-connector-onboard.md
new file mode 100644
index 000000000..dc088a253
--- /dev/null
+++ b/playfab-docs/api-references/events/General/tenancy-connector-onboard.md
@@ -0,0 +1,26 @@
+---
+title: tenancy_connector_onboard
+author: joannaleecy
+description: tenancy_connector_onboard event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# tenancy_connector_onboard
+
+This event is triggered when a tenancy connector is onboarded.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Groups/group-created.md b/playfab-docs/api-references/events/Groups/group-created.md
new file mode 100644
index 000000000..9f9683c83
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/group-created.md
@@ -0,0 +1,30 @@
+---
+title: group_created
+author: joannaleecy
+description: group_created event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# group_created
+
+This event is triggered when an entity group is created.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CreatorEntityId|String|The identifier for the entity that created the group to which this event applies.|
+|CreatorEntityType|String|The type of entity that created the group to which this event applies.|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|GroupName|String|The name of the group to which this event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
+
diff --git a/playfab-docs/api-references/events/Groups/group-members-added.md b/playfab-docs/api-references/events/Groups/group-members-added.md
new file mode 100644
index 000000000..33d5eda4c
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/group-members-added.md
@@ -0,0 +1,31 @@
+---
+title: group_members_added
+author: joannaleecy
+description: group_members_added event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# group_members_added
+
+This event is triggered when a member is added to an entity group. 
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|GroupName|String|The name of the group to which this event applies.|
+|Members|[Member](../data-types/member.md)|The list of entities that were added to the group and role to which this event applies.|
+|RoleId|String|The role ID of the role to which this event applies.|
+|RoleName|String|The display name of the role to which this event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
+
diff --git a/playfab-docs/api-references/events/Groups/group-members-removed.md b/playfab-docs/api-references/events/Groups/group-members-removed.md
new file mode 100644
index 000000000..2185c99c0
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/group-members-removed.md
@@ -0,0 +1,28 @@
+---
+title: group_members_removed
+author: joannaleecy
+description: group_members_removed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# group_members_removed
+
+This event is triggered when a member is removed from an entity group
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|GroupName|String|The name of the group to which this event applies.|
+|Members|[Member](../data-types/member.md)|The list of entities that were removed from the group to which this event applies|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Groups/group-role-created.md b/playfab-docs/api-references/events/Groups/group-role-created.md
new file mode 100644
index 000000000..2b9433a8c
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/group-role-created.md
@@ -0,0 +1,35 @@
+---
+title: group_role_created
+author: joannaleecy
+description: group_role_created event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# group_role_created
+
+This event is triggered when a role is created for a group.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CreatorEntityId|String|The identifier for that the entity that created the role to which this event applies.|
+|CreatorEntityType|String|The type of entity that created the role to which this event applies.|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|GroupName|String|The name of the group to which this event applies.|
+|RoleId|String|The role ID of the role to which this event applies.|
+|RoleName|String|The display name of the role to which this event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
+
+
+
+
diff --git a/playfab-docs/api-references/events/Groups/group-role-deleted.md b/playfab-docs/api-references/events/Groups/group-role-deleted.md
new file mode 100644
index 000000000..0c885d63a
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/group-role-deleted.md
@@ -0,0 +1,34 @@
+---
+title: group_role_deleted
+author: joannaleecy
+description: group_role_deleted event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# group_role_deleted
+
+This event is triggered when a role is deleted from a group.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeleterEntityId|String|The identifier for the entity that deleted the role to which this event applies.|
+|DeleterEntityType|String|The type of entity that deleted the role to which this event applies.|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|GroupName|String|The name of the group to which this event applies.|
+|RoleId|String|The role ID of the role to which this event applies.|
+|RoleName|String|The display name of the role to which this event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
+
+
+
diff --git a/playfab-docs/api-references/events/Groups/group-role-members-added.md b/playfab-docs/api-references/events/Groups/group-role-members-added.md
new file mode 100644
index 000000000..87251e7ad
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/group-role-members-added.md
@@ -0,0 +1,33 @@
+---
+title: group_role_members_added
+author: joannaleecy
+description: group_role_members_added event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# group_role_members_added
+
+This event is triggered when a list of entities are added to a role within a group.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|GroupName|String|The name of the group to which this event applies.|
+|Members|[Member](../data-types/member.md)|The list of entities that were added to the group and role to which this event applies|
+|RoleId|String|The role ID of the role to which this event applies.|
+|RoleName|String|The display name of the role to which this event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
+
+
+
diff --git a/playfab-docs/api-references/events/Groups/group-role-members-removed.md b/playfab-docs/api-references/events/Groups/group-role-members-removed.md
new file mode 100644
index 000000000..8712f082f
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/group-role-members-removed.md
@@ -0,0 +1,33 @@
+---
+title: group_role_members_removed
+author: joannaleecy
+description: group_role_members_removed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# group_role_members_removed
+
+This event is triggered when a list of entities are removed from a role within a group.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|GroupName|String|The name of the group to which this event applies.|
+|Members|[Member](../data-types/member.md)|The list of entities that were removed from the group to which this event applies|
+|RoleId|String|The role ID of the role to which this event applies.|
+|RoleName|String|The display name of the role to which this event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
+
+
+
diff --git a/playfab-docs/api-references/events/Groups/group-role-updated.md b/playfab-docs/api-references/events/Groups/group-role-updated.md
new file mode 100644
index 000000000..1a4f5d154
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/group-role-updated.md
@@ -0,0 +1,35 @@
+---
+title: group_role_updated
+author: joannaleecy
+description: group_role_updated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# group_role_updated
+
+This event is triggered when a role is updated within a group.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|GroupName|String|The name of the group to which this event applies.|
+|NewValues|[RolePropertyValues](../data-types/rolepropertyvalues.md)|The new values of the role's changed properties|
+|OldValues|[RolePropertyValues](../data-types/rolepropertyvalues.md)|The previous values of the role's changed properties|
+|RoleId|String|The role ID of the role to which this event applies.|
+|RoleName|String|The display name of the role to which this event applies.|
+|UpdaterEntityId|String|The identifier for the entity that updated the container to which this event applies.|
+|UpdaterEntityType|String|The type of entity that updated the container to which this event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
+
+
diff --git a/playfab-docs/api-references/events/Groups/group-updated.md b/playfab-docs/api-references/events/Groups/group-updated.md
new file mode 100644
index 000000000..fd55e7a9d
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/group-updated.md
@@ -0,0 +1,33 @@
+---
+title: group_updated
+author: joannaleecy
+description: group_updated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# group_updated
+
+This event is triggered when an entity group is updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|GroupName|String|The name of the group to which this event applies.|
+|NewValues|[GroupPropertyValues](../data-types/grouppropertyvalues.md)|The new values of the group's changed properties|
+|OldValues|[GroupPropertyValues](../data-types/grouppropertyvalues.md)|The previous values of the group's changed properties|
+|UpdaterEntityId|String|The identifier for the entity that updated the group to which this event applies.|
+|UpdaterEntityType|String|The type of entity that updated the group to which this event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
+
diff --git a/playfab-docs/api-references/events/Groups/members-added.md b/playfab-docs/api-references/events/Groups/members-added.md
new file mode 100644
index 000000000..5309a7ffc
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/members-added.md
@@ -0,0 +1,27 @@
+---
+title: members_added
+author: joannaleecy
+description: members_added event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# members_added
+
+This event is triggered when members are added to a group role.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Members|[EntityKey](../data-types/entitykey.md)[]|Entity keys of all members that were added to the role.|
+|RoleId|String|Id of role members were added to.|
+|RoleName|String|Name of role members were added to.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Groups/members-removed.md b/playfab-docs/api-references/events/Groups/members-removed.md
new file mode 100644
index 000000000..a339bb0c1
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/members-removed.md
@@ -0,0 +1,27 @@
+---
+title: members_removed
+author: joannaleecy
+description: members_removed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# members_removed
+
+This event is triggered when members are removed from a group role.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Members|[EntityKey](../data-types/entitykey.md)[]|Entity keys of all members that were removed from the role.|
+|RoleId|String|Id of role members were removed from.|
+|RoleName|String|Name of role members were removed from.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Groups/members-role-updated.md b/playfab-docs/api-references/events/Groups/members-role-updated.md
new file mode 100644
index 000000000..6fcea50e2
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/members-role-updated.md
@@ -0,0 +1,28 @@
+---
+title: members_role_updated
+author: joannaleecy
+description: members_role_updated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# members_role_updated
+
+This event is triggered when existing group members change from one role to another.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Members|[EntityKey](../data-types/entitykey.md)[]|Entity keys of all members that were updated with the role.|
+|Operation|[OperationTypes](../data-types/operationtypes.md)|The operation that was performed.|
+|RoleId|String|Id of the role.|
+|RoleName|String|Name of the role.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Groups/player-updated-membership.md b/playfab-docs/api-references/events/Groups/player-updated-membership.md
new file mode 100644
index 000000000..73d02b8a9
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/player-updated-membership.md
@@ -0,0 +1,31 @@
+---
+title: player_updated_membership
+author: joannaleecy
+description: player_updated_membership event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_updated_membership
+
+This event is triggered when a player's membership is updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|MembershipId|String|The unique identifier for the membership.|
+|MembershipName|String|The name of the membership.|
+|MembershipValue|[PlayerMemberships](../data-types/playermemberships.md)|The current membership value after the update.|
+|PreviousMembershipValue|[PlayerMemberships](../data-types/playermemberships.md)|The previous membership value before the update.|
+|SetViaOverride|Boolean|Whether the membership was set via an override.|
+|TitleId|String|The ID of the title to which this player event applies.|
+|UpdatedSubscription|[Subscriptions](../data-types/subscriptions.md)|The subscription that was updated.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Groups/role-updated.md b/playfab-docs/api-references/events/Groups/role-updated.md
new file mode 100644
index 000000000..8c7a2c12a
--- /dev/null
+++ b/playfab-docs/api-references/events/Groups/role-updated.md
@@ -0,0 +1,28 @@
+---
+title: role_updated
+author: joannaleecy
+description: role_updated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# role_updated
+
+This event is triggered when a group role is updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Operation|[OperationTypes](../data-types/operationtypes.md)|The operation that was performed.|
+|PreviousRoleName|String|Previous name of the role.|
+|RoleId|String|Id of the role to update.|
+|RoleName|String|New name of the role.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Inventory/items-added.md b/playfab-docs/api-references/events/Inventory/items-added.md
new file mode 100644
index 000000000..07fbedefd
--- /dev/null
+++ b/playfab-docs/api-references/events/Inventory/items-added.md
@@ -0,0 +1,32 @@
+---
+title: items_added
+author: ernestoc
+description: ItemsAdded event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# items_added
+
+Event raised when items have been added to an inventory.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| TransactionId | String | The transaction id. |
+| CollectionId | String | The collection id. |
+| ItemId | String | The item id. |
+| StackId | String | The stack id. |
+| Amount | int? | The amount of items that were added. |
+| DurationInSeconds | long? | The duration of the item that was added. |
+| ItemType | String | The type of the catalog item that was modified in the transaction. |
+| Balance | int? | The balance of the items changed as a result of the transaction. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Inventory/items-clawback-completed.md b/playfab-docs/api-references/events/Inventory/items-clawback-completed.md
new file mode 100644
index 000000000..07d769e2c
--- /dev/null
+++ b/playfab-docs/api-references/events/Inventory/items-clawback-completed.md
@@ -0,0 +1,29 @@
+---
+title: items_clawback_completed
+author: ernestoc
+description: items_clawback_completed event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# items_clawback_completed
+
+This event is triggered when an items clawback operation is completed.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| EntityLineage | [EntityLineage](../data-types/entitylineage.md) | Entities that this entity is a child of. |
+| OriginalEventId | String | The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server. |
+| OriginalTimestamp | DateTime | The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server. |
+| Payload | [ItemsClawbackCompletedPayload](../data-types/itemsclawbackcompletedpayload.md) | The items clawback completed event payload. |
+| WriterEntity | [EntityKey](../data-types/entitykey.md) | Entity that wrote this event, included only if different than the event's entity. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Inventory/items-clawback-reversal-completed.md b/playfab-docs/api-references/events/Inventory/items-clawback-reversal-completed.md
new file mode 100644
index 000000000..406dc1ef0
--- /dev/null
+++ b/playfab-docs/api-references/events/Inventory/items-clawback-reversal-completed.md
@@ -0,0 +1,29 @@
+---
+title: items_clawback_reversal_completed
+author: ernestoc
+description: items_clawback_reversal_completed event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# items_clawback_reversal_completed
+
+This event is triggered when an items clawback reversal operation is completed.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| EntityLineage | [EntityLineage](../data-types/entitylineage.md) | Entities that this entity is a child of. |
+| OriginalEventId | String | The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server. |
+| OriginalTimestamp | DateTime | The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server. |
+| Payload | [ItemsClawbackReversalCompletedPayload](../data-types/itemsclawbackreversalcompletedpayload.md) | The items clawback reversal completed event payload. |
+| WriterEntity | [EntityKey](../data-types/entitykey.md) | Entity that wrote this event, included only if different than the event's entity. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Inventory/items-deleted.md b/playfab-docs/api-references/events/Inventory/items-deleted.md
new file mode 100644
index 000000000..10137d99e
--- /dev/null
+++ b/playfab-docs/api-references/events/Inventory/items-deleted.md
@@ -0,0 +1,29 @@
+---
+title: items_deleted
+author: ernestoc
+description: ItemsDeleted event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# items_deleted
+
+Event raised when items have been deleted from an inventory.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| TransactionId | String | The transaction id. |
+| CollectionId | String | The collection id. |
+| ItemId | String | The item id. |
+| StackId | String | The stack id. |
+| ItemType | String | The type of the catalog item that was modified in the transaction. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Inventory/items-expired.md b/playfab-docs/api-references/events/Inventory/items-expired.md
new file mode 100644
index 000000000..38cb15e38
--- /dev/null
+++ b/playfab-docs/api-references/events/Inventory/items-expired.md
@@ -0,0 +1,29 @@
+---
+title: items_expired
+author: ernestoc
+description: items_expired event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# items_expired
+
+This event is triggered when items have expired in an inventory.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| EntityLineage | [EntityLineage](../data-types/entitylineage.md) | Entities that this entity is a child of. |
+| OriginalEventId | String | The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server. |
+| OriginalTimestamp | DateTime | The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server. |
+| Payload | [ItemsExpiredPayload](../data-types/itemsexpiredpayload.md) | The items expired event payload. |
+| WriterEntity | [EntityKey](../data-types/entitykey.md) | Entity that wrote this event, included only if different than the event's entity. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Inventory/items-purchased.md b/playfab-docs/api-references/events/Inventory/items-purchased.md
new file mode 100644
index 000000000..c4f2b8d7b
--- /dev/null
+++ b/playfab-docs/api-references/events/Inventory/items-purchased.md
@@ -0,0 +1,34 @@
+---
+title: items_purchased
+author: ernestoc
+description: ItemsPurchased event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# items_purchased
+
+Event raised when items have been purchased from an inventory.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| TransactionId | String | The transaction id. |
+| CollectionId | String | The collection id. |
+| ItemId | String | The item id. |
+| StackId | String | The stack id. |
+| Amount | int? | The amount of items that were puchased. |
+| DurationInSeconds | long? | The duration of the item that was purchased. |
+| SalePriceAmounts | List<[PurchasePriceAmount](../data-types/purchasepriceamount.md)> | The per-item price amounts the item was purchased at. |
+| StoreId | String | The id of the Store the item was purchased from or null. |
+| ItemType | String | The type of the catalog item that was modified in the transaction. |
+| Balance | int? | The balance of the items changed as a result of the transaction. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Inventory/items-redeemed.md b/playfab-docs/api-references/events/Inventory/items-redeemed.md
new file mode 100644
index 000000000..b79573595
--- /dev/null
+++ b/playfab-docs/api-references/events/Inventory/items-redeemed.md
@@ -0,0 +1,34 @@
+---
+title: items_redeemed
+author: ernestoc
+description: ItemsRedeemed event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# items_redeemed
+
+Event raised when items have been redeemed to an inventory.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| TransactionId | String | The transaction id. |
+| CollectionId | String | The collection id. |
+| ItemId | String | The item id. |
+| StackId | String | The stack id. |
+| Amount | int? | The amount of items that were redeemed. |
+| DurationInSeconds | long? | The duration of the item that was redeemed. |
+| Marketplace | String | The name of the marketplace that the items were redeemed from. |
+| MarketplaceTransactionId | String | The transaction id in the marketplace that the items were redeemed from. |
+| ItemType | String | The type of the catalog item that was modified in the transaction. |
+| Balance | int? | The balance of the items changed as a result of the transaction. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Inventory/items-subtracted.md b/playfab-docs/api-references/events/Inventory/items-subtracted.md
new file mode 100644
index 000000000..0e4cd05eb
--- /dev/null
+++ b/playfab-docs/api-references/events/Inventory/items-subtracted.md
@@ -0,0 +1,32 @@
+---
+title: items_subtracted
+author: ernestoc
+description: ItemsSubtracted event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# items_subtracted
+
+Event raised when items have been subtracted from an inventory.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| TransactionId | String | The transaction id. |
+| CollectionId | String | The collection id. |
+| ItemId | String | The item id. |
+| StackId | String | The stack id. |
+| Amount | int? | The amount of items that were subtracted. |
+| DurationInSeconds | long? | The duration of the item that was subtracted. |
+| ItemType | String | The type of the catalog item that was modified in the transaction. |
+| Balance | int? | The balance of the items changed as a result of the transaction. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Inventory/items-transferred.md b/playfab-docs/api-references/events/Inventory/items-transferred.md
new file mode 100644
index 000000000..701dcabac
--- /dev/null
+++ b/playfab-docs/api-references/events/Inventory/items-transferred.md
@@ -0,0 +1,36 @@
+---
+title: items_transferred
+author: ernestoc
+description: ItemsTransferred event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# items_transferred
+
+Event raised when items have been transferred to or from an inventory.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| TransactionId | String | The transaction id. |
+| CollectionId | String | The collection id. |
+| ItemId | String | The item id. |
+| StackId | String | The stack id. |
+| Amount | int? | The amount of items that were transferred. |
+| DurationInSeconds | long? | The duration of the item that was transferred. |
+| GivingEntity | [EntityKey](../data-types/entitykey.md)? | The entity the items were transferred from or null if it was the current entity. |
+| ReceivingEntity | [EntityKey](../data-types/entitykey.md)? | The entity the items were transferred to or null if it was the current entity. |
+| GivingCollectionId | String | The collection if the items were transferred from or null if it was the current collection. |
+| ReceivingCollectionId | String | The collection id the items were transferred to or null if it was the current collection. |
+| ItemType | String | The type of the catalog item that was modified in the transaction. |
+| Balance | int? | The balance of the items changed as a result of the transaction. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Inventory/items-updated.md b/playfab-docs/api-references/events/Inventory/items-updated.md
new file mode 100644
index 000000000..7b91f8d08
--- /dev/null
+++ b/playfab-docs/api-references/events/Inventory/items-updated.md
@@ -0,0 +1,31 @@
+---
+title: items_updated
+author: ernestoc
+description: ItemsUpdated event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# items_updated
+
+Event raised when items have been updated in an inventory.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| TransactionId | String | The transaction id. |
+| CollectionId | String | The collection id. |
+| ItemId | String | The item id. |
+| StackId | String | The stack id. |
+| Amount | int? | The amount of item. |
+| Expiration | String | The date the item expires. |
+| ItemType | String | The type of the catalog item that was modified in the transaction. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Inventory/marketplace-transaction-redeemed.md b/playfab-docs/api-references/events/Inventory/marketplace-transaction-redeemed.md
new file mode 100644
index 000000000..4a0c91967
--- /dev/null
+++ b/playfab-docs/api-references/events/Inventory/marketplace-transaction-redeemed.md
@@ -0,0 +1,32 @@
+---
+title: marketplace_transaction_redeemed
+author: ernestoc
+description: marketplace_transaction_redeemed event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# marketplace_transaction_redeemed
+
+This event is triggered when a bundle or subscription has been redeemed to an inventory.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| Marketplace | String | The name of the marketplace the items were redeemed from. |
+| MarketplaceTransctionId | String | The transaction Id from the marketplace the items were redeemed from. |
+| MarketplaceAlternateId | String | The alternate Id of the item for the marketplace. |
+| Amount | int? | The amount that was redeemed. |
+| DurationInSeconds | long? | The amount of subscription that was redeemed. |
+| ItemId | String | The identifier of the item that was redeemed. |
+| ItemType | String | The type of the catalog item that was redeemed. |
+| RealMoneyPrices | Dictionary<string, int> | The multi-currency unit price, in real money, of the item that was redeemed. The property is a dictionary where the key is the three-letter currency code as defined in ISO 4217, and the value is the currency amount in the smallest unit (for example, cents, pence) in accordance with ISO 4217. Only United States Dollar (USD) is currently supported. Example: If the product price in USD is $1.39, the dictionary entry would be: ["USD"] = 139; |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Leaderboards/character-statistic-changed.md b/playfab-docs/api-references/events/Leaderboards/character-statistic-changed.md
new file mode 100644
index 000000000..4d0c696fc
--- /dev/null
+++ b/playfab-docs/api-references/events/Leaderboards/character-statistic-changed.md
@@ -0,0 +1,30 @@
+---
+title: character_statistic_changed
+author: joannaleecy
+description: character_statistic_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# character_statistic_changed
+
+This event is triggered when a character statistic is changed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|PlayerId|String||
+|StatisticName|String|Name of the statistic that changed.|
+|StatisticPreviousValue|int32|Old value of the statistic, before the change.|
+|StatisticValue|int32|New value of the statistic, after the change.|
+|TitleId|String||
+|Version|uint32|Version of the statistic that changed. This is relevant for statistics that reset, since each time the statistic resets the version increments.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Leaderboards/character-statistic-deleted.md b/playfab-docs/api-references/events/Leaderboards/character-statistic-deleted.md
new file mode 100644
index 000000000..f28c6d970
--- /dev/null
+++ b/playfab-docs/api-references/events/Leaderboards/character-statistic-deleted.md
@@ -0,0 +1,28 @@
+---
+title: character_statistic_deleted
+author: joannaleecy
+description: character_statistic_deleted event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# character_statistic_deleted
+
+This event is triggered when a character statistic is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|PlayerId|String||
+|StatisticName|String|Name of the statistic that was deleted.|
+|TitleId|String||
+|Version|uint32|Version of the statistic that changed. This is relevant for statistics that reset, since each time the statistic resets the version increments.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Leaderboards/entity-rank-on-leaderboard-version-ended.md b/playfab-docs/api-references/events/Leaderboards/entity-rank-on-leaderboard-version-ended.md
new file mode 100644
index 000000000..4241e0017
--- /dev/null
+++ b/playfab-docs/api-references/events/Leaderboards/entity-rank-on-leaderboard-version-ended.md
@@ -0,0 +1,29 @@
+---
+title: entity_rank_on_leaderboard_version_ended
+author: t-sandersg-gith
+description: entity_rank_on_leaderboard_version_ended event.
+ms.author: t-sandersg
+ms.date: 8/14/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# entity_rank_on_leaderboard_version_ended
+
+This event is triggered when a leaderboard version is reset to a new version for a game title, containing the entity's rank and score data from the ended version.
+
+## Properties
+
+| Name | Type | Description |
+| --- | --- | --- |
+| Name | String | The name of the leaderboard |
+| Version | int32 | The version of the leaderboard |
+| Metadata | String | Custom metadata associated with the entity |
+| Rank | int32 | The rank of the entity in the leaderboard |
+| Scores | int32[] | The scores of the entity in the leaderboard |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Leaderboards/leaderboard-version-ended.md b/playfab-docs/api-references/events/Leaderboards/leaderboard-version-ended.md
new file mode 100644
index 000000000..dd3e33bdc
--- /dev/null
+++ b/playfab-docs/api-references/events/Leaderboards/leaderboard-version-ended.md
@@ -0,0 +1,27 @@
+---
+title: leaderboard_version_ended
+author: t-sandersg-gith
+description: leaderboard_version_ended event.
+ms.author: t-sandersg
+ms.date: 08/14/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# leaderboard_version_ended
+
+This event is triggered when a leaderboard version is reset to a new version for a game title.
+
+## Properties
+
+| Name | Type | Description |
+| --- | --- | --- |
+| Name | String | The name of the leaderboard |
+| Version | int32 | The version of the leaderboard |
+| TimeStamp | DateTime | The time at which the leaderboard version was changed |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Leaderboards/player-ranked-on-leaderboard-version.md b/playfab-docs/api-references/events/Leaderboards/player-ranked-on-leaderboard-version.md
new file mode 100644
index 000000000..81994a4ff
--- /dev/null
+++ b/playfab-docs/api-references/events/Leaderboards/player-ranked-on-leaderboard-version.md
@@ -0,0 +1,30 @@
+---
+title: player_ranked_on_leaderboard_version
+author: joannaleecy
+description: player_ranked_on_leaderboard_version event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_ranked_on_leaderboard_version
+
+This event is triggered when a leaderboard version changes, generating events for top‑ranked players up to the limit defined by the "Leaderboard version change top rank events sent" setting.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|LeaderboardSource|[LeaderboardSource](../data-types/leaderboardsource.md)|Source of the values for the leaderboard.|
+|Rank|uint32|Player's rank on the leaderboard.|
+|TitleId|String|The ID of the title to which this player event applies.|
+|Value|int32|Player's leaderboard value.|
+|Version|uint32|Version of the leaderboard on which the player is ranked. For player statistic leaderboards, this matches the version of the statistic.|
+|VersionChangeBehavior|[LeaderboardVersionChangeBehavior](../data-types/leaderboardversionchangebehavior.md)|Behavior with respect to the leaderboard values when the version changed.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Leaderboards/player-statistic-changed.md b/playfab-docs/api-references/events/Leaderboards/player-statistic-changed.md
new file mode 100644
index 000000000..37645a98a
--- /dev/null
+++ b/playfab-docs/api-references/events/Leaderboards/player-statistic-changed.md
@@ -0,0 +1,31 @@
+---
+title: player_statistic_changed
+author: joannaleecy
+description: player_statistic_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_statistic_changed
+
+This event is triggered when a player statistic is changed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AggregationMethod|[StatisticAggregationMethod](../data-types/statisticaggregationmethod.md)|Aggregation method applied for calculating the new value of the statistic.|
+|StatisticId|uint32|Unique ID of the statistic that changed.|
+|StatisticName|String|Name of the statistic that changed.|
+|StatisticPreviousValue|int32|Old value of the statistic, before the change.|
+|StatisticValue|int32|New value of the statistic, after the change.|
+|TitleId|String|The ID of the title to which this player event applies.|
+|Version|uint32|Version of the statistic that changed. This is relevant for statistics that reset, since each time the statistic resets the version increments.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Leaderboards/player-statistic-deleted.md b/playfab-docs/api-references/events/Leaderboards/player-statistic-deleted.md
new file mode 100644
index 000000000..cd787f919
--- /dev/null
+++ b/playfab-docs/api-references/events/Leaderboards/player-statistic-deleted.md
@@ -0,0 +1,29 @@
+---
+title: player_statistic_deleted
+author: joannaleecy
+description: player_statistic_deleted event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_statistic_deleted
+
+This event is triggered when a player statistic is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|StatisticId|uint32|Unique ID of the statistic that was deleted.|
+|StatisticName|String|Name of the statistic that was deleted.|
+|StatisticPreviousValue|int32|Old value of the statistic, before being deleted.|
+|TitleId|String|The ID of the title to which this player event applies.|
+|Version|uint32|Version of the statistic. This is relevant for statistics that reset, since each time the statistic resets the version increments.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Leaderboards/title-statistic-deleted.md b/playfab-docs/api-references/events/Leaderboards/title-statistic-deleted.md
new file mode 100644
index 000000000..19f4ec5d1
--- /dev/null
+++ b/playfab-docs/api-references/events/Leaderboards/title-statistic-deleted.md
@@ -0,0 +1,26 @@
+---
+title: title_statistic_deleted
+author: anaislawson
+description: title_statistic_deleted event.
+ms.author: anaislawson
+ms.date: 02/05/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_statistic_deleted
+
+This event is triggered when a title statistic is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|StatisticName|String|Unique name of the statistic.|
+|StatisticVersion|uint32|Version of the statistic.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Leaderboards/title-statistic-version-changed.md b/playfab-docs/api-references/events/Leaderboards/title-statistic-version-changed.md
new file mode 100644
index 000000000..4a06fdc96
--- /dev/null
+++ b/playfab-docs/api-references/events/Leaderboards/title-statistic-version-changed.md
@@ -0,0 +1,28 @@
+---
+title: title_statistic_version_changed
+author: joannaleecy
+description: title_statistic_version_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_statistic_version_changed
+
+This event is triggered when the version of a statistic changes, causing its leaderboard to reset.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ScheduledResetInterval|[StatisticResetIntervalOption](../data-types/statisticresetintervaloption.md)|The interval on which the statistic leaderboard was configured to reset, if any.|
+|ScheduledResetTime|DateTime|The time at which the statistic leaderboard was configured to reset, if any.|
+|StatisticName|String|Unique name of the statistic.|
+|StatisticVersion|uint32|Version of the statistic, following the update.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Matchmaking/match-found.md b/playfab-docs/api-references/events/Matchmaking/match-found.md
new file mode 100644
index 000000000..c0b51ba40
--- /dev/null
+++ b/playfab-docs/api-references/events/Matchmaking/match-found.md
@@ -0,0 +1,27 @@
+---
+title: match_found
+author: anaislawson
+description: match_found event.
+ms.author: anaislawson
+ms.date: 02/05/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events, matchmaking
+ms.localizationpriority: medium
+---
+
+# match_found
+
+This event is triggered when matchmaking successfully forms a match for a set of tickets.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|MatchId|String|The unique identifier for the match that was created.|
+|QueueName|String|The name of the matchmaking queue in which the match was formed.|
+|TicketIds|String[]|An array of ticket IDs that were matched together to form the match.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Matchmaking/ticket-completed.md b/playfab-docs/api-references/events/Matchmaking/ticket-completed.md
new file mode 100644
index 000000000..d0e5f5eca
--- /dev/null
+++ b/playfab-docs/api-references/events/Matchmaking/ticket-completed.md
@@ -0,0 +1,33 @@
+---
+title: ticket_completed
+author: anaislawson
+description: ticket_completed event.
+ms.author: anaislawson
+ms.date: 02/05/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events, matchmaking
+ms.localizationpriority: medium
+---
+
+# ticket_completed
+
+This event is triggered when a matchmaking ticket reaches a terminal state (for example, it is matched or canceled).
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CancellationReason|String|If the ticket result is Canceled then this string provides the reason why the ticket was canceled otherwise it is null. Possible values: Requested, Internal, Timeout, ServerAllocationFailed.|
+|CompletionTime|DateTime|Time at which this ticket was completed.|
+|CreationTime|DateTime|Time at which this ticket was created.|
+|MatchId|String|The identifier for the match that the ticket got matched into. This field is only set if the ticket got matched otherwise it will be null.|
+|QueueName|String|The name of the queue the ticket was created in.|
+|Result|String|The final state of the ticket. It could be Matched or Canceled.|
+|SubmissionTime|DateTime|Time at which this ticket was submitted into the matchmaking queue.|
+|TicketEntities|[EntityKey](../data-types/entitykey.md)[]|The list of entities that are part of this ticket.|
+|TicketId|String|Id of the ticket that was completed.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Matchmaking/title-queue-config-updated.md b/playfab-docs/api-references/events/Matchmaking/title-queue-config-updated.md
new file mode 100644
index 000000000..cf324273c
--- /dev/null
+++ b/playfab-docs/api-references/events/Matchmaking/title-queue-config-updated.md
@@ -0,0 +1,28 @@
+---
+title: title_queue_config_updated
+author: anaislawson
+description: title_queue_config_updated event.
+ms.author: anaislawson
+ms.date: 02/10/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events, matchmaking
+ms.localizationpriority: medium
+---
+
+# title_queue_config_updated
+
+This event is triggered when a queue config is changed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Deleted|Boolean|Was the queue config deleted.|
+|DeveloperId|String||
+|MatchQueueName|String|Name of the queue config that was updated.|
+|UserId|String||
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Matchmaking/user-ticket-invited.md b/playfab-docs/api-references/events/Matchmaking/user-ticket-invited.md
new file mode 100644
index 000000000..ec1b31e5a
--- /dev/null
+++ b/playfab-docs/api-references/events/Matchmaking/user-ticket-invited.md
@@ -0,0 +1,26 @@
+---
+title: user_ticket_invited
+author: anaislawson
+description: user_ticket_invited event.
+ms.author: anaislawson
+ms.date: 02/10/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events, matchmaking
+ms.localizationpriority: medium
+---
+
+# user_ticket_invited
+
+This event is triggered when a user is invited to a ticket.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|QueueName|String|The name of the queue the ticket was created in.|
+|TicketId|String|Id of the ticket that the user was invited to.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/MultiplayerServers/build-alias-created.md b/playfab-docs/api-references/events/MultiplayerServers/build-alias-created.md
new file mode 100644
index 000000000..dc6876e83
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/build-alias-created.md
@@ -0,0 +1,26 @@
+---
+title: build_alias_created
+author: valexao
+description: build_alias_created event.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# build_alias_created 
+
+This event is triggered when a multiplayer server build alias is created.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[BuildAliasCreatedEventPayload](../data-types/buildaliascreatedeventpayload.md)|The multiplayer server build alias created event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/MultiplayerServers/build-alias-deleted.md b/playfab-docs/api-references/events/MultiplayerServers/build-alias-deleted.md
new file mode 100644
index 000000000..2efb262db
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/build-alias-deleted.md
@@ -0,0 +1,26 @@
+---
+title: build_alias_deleted
+author: valexao
+description: build_alias_deleted event.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# build_alias_deleted 
+
+This event is triggered when a multiplayer server build alias is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[BuildAliasDeletedEventPayload](../data-types/buildaliasdeletedeventpayload.md)|The multiplayer server build alias deleted event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/MultiplayerServers/build-alias-updated.md b/playfab-docs/api-references/events/MultiplayerServers/build-alias-updated.md
new file mode 100644
index 000000000..f38ba6ddc
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/build-alias-updated.md
@@ -0,0 +1,27 @@
+---
+title: build_alias_updated
+author: valexao
+description: build_alias_updated event.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# build_alias_updated 
+
+This event is triggered when a multiplayer server build alias is updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[BuildAliasUpdatedEventPayload](../data-types/buildaliasupdatedeventpayload.md)|The multiplayer server build alias updated event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/build-deleted.md b/playfab-docs/api-references/events/MultiplayerServers/build-deleted.md
new file mode 100644
index 000000000..879a71f2a
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/build-deleted.md
@@ -0,0 +1,28 @@
+---
+title: build_deleted
+author: joannaleecy
+description: build_deleted event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# build_deleted
+
+This event is triggered when a multiplayer server build is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[BuildDeletedEventPayload](../data-types/builddeletedeventpayload.md)|The multiplayer server build deleted event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/build-region-status-changed.md b/playfab-docs/api-references/events/MultiplayerServers/build-region-status-changed.md
new file mode 100644
index 000000000..9fbde8d41
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/build-region-status-changed.md
@@ -0,0 +1,28 @@
+---
+title: build_region_status_changed
+author: joannaleecy
+description: build_region_status_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# build_region_status_changed 
+
+This event is triggered when a multiplayer server's build region status is changed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[BuildRegionStatusChangedEventPayload](../data-types/buildregionstatuschangedeventpayload.md)|The multiplayer server build region status changed event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/build-region-updated.md b/playfab-docs/api-references/events/MultiplayerServers/build-region-updated.md
new file mode 100644
index 000000000..d218f959a
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/build-region-updated.md
@@ -0,0 +1,27 @@
+---
+title: build_region_updated
+author: joannaleecy
+description: build_region_updated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# build_region_updated
+
+This event is triggered when a multiplayer server build region is updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[BuildRegionUpdatedEventPayload](../data-types/buildregionupdatedeventpayload.md)|The multiplayer server build region updated event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/build-region-utilization.md b/playfab-docs/api-references/events/MultiplayerServers/build-region-utilization.md
new file mode 100644
index 000000000..5b75dddae
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/build-region-utilization.md
@@ -0,0 +1,27 @@
+---
+title: build_region_utilization
+author: valexao
+description: build_region_utilization event.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# build_region_utilization
+
+This event is triggered to display the utilization of servers for a build in each region.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[BuildRegionUtilizationEventPayload](../data-types/buildregionutilizationeventpayload.md)|The multiplayer server build region utilization event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/certificate-deleted.md b/playfab-docs/api-references/events/MultiplayerServers/certificate-deleted.md
new file mode 100644
index 000000000..bd0b45ac5
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/certificate-deleted.md
@@ -0,0 +1,26 @@
+---
+title: certificate_deleted
+author: joannaleecy
+description: certificate_deleted event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# certificate_deleted
+
+This event is triggered when a multiplayer server certificate is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[CertificateDeletedEventPayload](../data-types/certificatedeletedeventpayload.md)|The multiplayer server certificate deleted event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/MultiplayerServers/certificate-uploaded.md b/playfab-docs/api-references/events/MultiplayerServers/certificate-uploaded.md
new file mode 100644
index 000000000..242515001
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/certificate-uploaded.md
@@ -0,0 +1,27 @@
+---
+title: certificate_uploaded
+author: joannaleecy
+description: certificate_uploaded event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# certificate_uploaded
+
+This event is triggered when a multiplayer server certificate is uploaded.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[CertificateUploadedEventPayload](../data-types/certificateuploadedeventpayload.md)|The multiplayer server certificate uploaded event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/crash-detected.md b/playfab-docs/api-references/events/MultiplayerServers/crash-detected.md
new file mode 100644
index 000000000..97aa6da30
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/crash-detected.md
@@ -0,0 +1,27 @@
+---
+title: crash_detected
+author: valexao
+description: crash_detected event.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# crash_detected
+
+This event triggered when a crash dump is found on a terminating server.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[CrashDetectedEventPayload](../data-types/crashdetectedeventpayload.md)|The multiplayer server crash detected event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/create-build-initiated.md b/playfab-docs/api-references/events/MultiplayerServers/create-build-initiated.md
new file mode 100644
index 000000000..6b4178de0
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/create-build-initiated.md
@@ -0,0 +1,27 @@
+---
+title: create_build_initiated
+author: joannaleecy
+description: create_build_initiated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# create_build_initiated
+
+This event is triggered when a multiplayer server build is initiated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[CreateBuildInitiatedEventPayload](../data-types/createbuildinitiatedeventpayload.md)|The multiplayer server create build initiated event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/enabled-for-title.md b/playfab-docs/api-references/events/MultiplayerServers/enabled-for-title.md
new file mode 100644
index 000000000..aede9c264
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/enabled-for-title.md
@@ -0,0 +1,26 @@
+---
+title: enabled_for_title
+author: valexao
+description: enabled_for_title event.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# enabled_for_title
+
+This event is triggered when a title enables PlayFab multiplayer servers.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/game-asset-deleted.md b/playfab-docs/api-references/events/MultiplayerServers/game-asset-deleted.md
new file mode 100644
index 000000000..233d75081
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/game-asset-deleted.md
@@ -0,0 +1,26 @@
+---
+title: game_asset_deleted
+author: joannaleecy
+description: game_asset_deleted event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# game_asset_deleted
+This event is triggered when a multiplayer server game asset is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[GameAssetDeletedEventPayload](../data-types/gameassetdeletedeventpayload.md)|The multiplayer server game asset deleted event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/monitoring-output-saved.md b/playfab-docs/api-references/events/MultiplayerServers/monitoring-output-saved.md
new file mode 100644
index 000000000..cb925f258
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/monitoring-output-saved.md
@@ -0,0 +1,27 @@
+---
+title: monitoring_output_saved
+author: valexao
+description: monitoring_output_saved event.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# monitoring_output_saved
+
+This event is triggered when the output of a monitoring application has been saved and can be downloaded.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[MonitoringOutputSavedEventPayload](../data-types/monitoringoutputsavedeventpayload.md)|The multiplayer server monitoring output saved event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/secret-added.md b/playfab-docs/api-references/events/MultiplayerServers/secret-added.md
new file mode 100644
index 000000000..a2b6e452f
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/secret-added.md
@@ -0,0 +1,27 @@
+---
+title: secret_added
+author: valexao
+description: secret_added event.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# secret_added
+
+This event is triggered when a multiplayer server secret is added.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[SecretAddedEventPayload](../data-types/secretaddedeventpayload.md)|The multiplayer server secret added event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/secret-deleted.md b/playfab-docs/api-references/events/MultiplayerServers/secret-deleted.md
new file mode 100644
index 000000000..9d77ea608
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/secret-deleted.md
@@ -0,0 +1,27 @@
+---
+title: secret_deleted
+author: valexao
+description: secret_deleted event.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# secret_deleted
+
+This event is triggered when a multiplayer server secret is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[SecretDeletedEventPayload](../data-types/secretdeletedeventpayload.md)|The multiplayer server secret deleted event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/server-requested.md b/playfab-docs/api-references/events/MultiplayerServers/server-requested.md
new file mode 100644
index 000000000..027a8b192
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/server-requested.md
@@ -0,0 +1,30 @@
+---
+title: server_requested
+author: joannaleecy
+description: server_requested event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# server_requested
+
+This event is triggered when a multiplayer server is requested. 
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+
+|Payload|[ServerRequestedEventPayload](../data-types/serverrequestedeventpayload.md)|The multiplayer server requested event payload.|
+
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/server-state-changed.md b/playfab-docs/api-references/events/MultiplayerServers/server-state-changed.md
new file mode 100644
index 000000000..3497ef503
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/server-state-changed.md
@@ -0,0 +1,28 @@
+---
+title: server_state_changed
+author: joannaleecy
+description: server_state_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# server_state_changed
+
+This event is triggered when a multiplayer server's state is changed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+
+|Payload|[ServerStateChangedEventPayload](../data-types/serverstatechangedeventpayload.md)|The multiplayer server state changed event payload.|
+
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/MultiplayerServers/vm-assigned.md b/playfab-docs/api-references/events/MultiplayerServers/vm-assigned.md
new file mode 100644
index 000000000..c93fe6935
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/vm-assigned.md
@@ -0,0 +1,26 @@
+---
+title: vm_assigned
+author: joannaleecy
+description: vm_assigned event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# vm_assigned
+
+This event is triggered when a virtual machine is assigned to a multiplayer server build.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[VmAssignedEventPayload](../data-types/vmassignedeventpayload.md)|The multiplayer server virtual machine assigned event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/MultiplayerServers/vm-game-certificates-deployed.md b/playfab-docs/api-references/events/MultiplayerServers/vm-game-certificates-deployed.md
new file mode 100644
index 000000000..464d13966
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/vm-game-certificates-deployed.md
@@ -0,0 +1,26 @@
+---
+title: vm_game_certificates_deployed
+author: valexao
+description: vm_game_certificates_deployed event.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# vm_game_certificates_deployed
+
+This event is triggered when game certificates are deployed in a game virtual machine.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[VmGameCertificatesDeployedEventPayload](../data-types/vmgamecertificatesdeployedeventpayload.md)|The multiplayer server vm game certificates deployed event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/MultiplayerServers/vm-remote-user-created.md b/playfab-docs/api-references/events/MultiplayerServers/vm-remote-user-created.md
new file mode 100644
index 000000000..88b86a32f
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/vm-remote-user-created.md
@@ -0,0 +1,26 @@
+---
+title: vm_remote_user_created
+author: joannaleecy
+description: vm_remote_user_created event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# vm_remote_user_created
+
+This event is triggered when a multiplayer server virtual machine remote user is created.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[VmRemoteUserCreatedEventPayload](../data-types/vmremoteusercreatedeventpayload.md)|The multiplayer server virtual machine remote user created event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/MultiplayerServers/vm-remote-user-deleted.md b/playfab-docs/api-references/events/MultiplayerServers/vm-remote-user-deleted.md
new file mode 100644
index 000000000..2e82fb175
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/vm-remote-user-deleted.md
@@ -0,0 +1,26 @@
+---
+title: vm_remote_user_deleted
+author: joannaleecy
+description: vm_remote_user_deleted event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# vm_remote_user_deleted
+
+This event is triggered when a multiplayer server virtual machine remote user is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[VmRemoteUserDeletedEventPayload](../data-types/vmremoteuserdeletedeventpayload.md)|The multiplayer server virtual machine remote user deleted event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/MultiplayerServers/vm-state-change.md b/playfab-docs/api-references/events/MultiplayerServers/vm-state-change.md
new file mode 100644
index 000000000..6a6222891
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/vm-state-change.md
@@ -0,0 +1,27 @@
+---
+title: vm_state_change
+author: valexao
+description: vm_state_change event.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# vm_state_change
+
+This event is triggered when a multiplayer virtual machine's state is changed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[VmStateChangeEventPayload](../data-types/vmstatechangeeventpayload.md)|The multiplayer server vm state change event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
+
diff --git a/playfab-docs/api-references/events/MultiplayerServers/vm-unassignment-started.md b/playfab-docs/api-references/events/MultiplayerServers/vm-unassignment-started.md
new file mode 100644
index 000000000..8de176d81
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/vm-unassignment-started.md
@@ -0,0 +1,25 @@
+---
+title: vm_unassignment_started
+author: joannaleecy
+description: vm_unassignment_started event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# vm_unassignment_started
+This event is triggered when a virtual machine is unassigned from a multiplayer server build.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[VmUnassignmentStartedEventPayload](../data-types/vmunassignmentstartedeventpayload.md)|The multiplayer server virtual machine unassignment started event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/MultiplayerServers/vm-unhealthy.md b/playfab-docs/api-references/events/MultiplayerServers/vm-unhealthy.md
new file mode 100644
index 000000000..2034fcf5a
--- /dev/null
+++ b/playfab-docs/api-references/events/MultiplayerServers/vm-unhealthy.md
@@ -0,0 +1,25 @@
+---
+title: vm_unhealthy
+author: joannaleecy
+description: vm_unhealthy event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# vm_unhealthy
+This event is triggered when a virtual machine is found to be unhealthy.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Payload|[VmUnhealthyEventPayload](../data-types/vmunhealthyeventpayload.md)|The multiplayer server virtual machine unhealthy event payload.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/Networking/client-authentication-completed.md b/playfab-docs/api-references/events/Networking/client-authentication-completed.md
new file mode 100644
index 000000000..d990a6cc1
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/client-authentication-completed.md
@@ -0,0 +1,32 @@
+---
+title: client_authentication_completed
+author: raulalbertog
+description: client_authentication_completed event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# client_authentication_completed
+
+This event is triggered when client authentication is completed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ClientInstanceId|String|The client-generated globally unique identifier of this instance of the Party library.|
+|NetworkIdentifier|String|The network's unique identifier at the time of this event.|
+|AuthDurationInMs|uint32|The duration of the isolated authentication operation in milliseconds.|
+|TotalDurationInMs|uint32|The duration of the authentication operation and all associated operations queued before it in milliseconds.|
+|LocalConnectionId|uint32|A local identifier to disambiguate multiple connections to the same network from a single client.|
+|Result|int32|The PartyStateChangeResult of the operation.|
+|ResultMessage|String|A human-readable representation of the Result value.|
+|ErrorDetail|uint32|The PartyError error detail code.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/client-connected-to-network.md b/playfab-docs/api-references/events/Networking/client-connected-to-network.md
new file mode 100644
index 000000000..e43473039
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/client-connected-to-network.md
@@ -0,0 +1,35 @@
+---
+title: client_connected_to_network
+author: raulalbertog
+description: client_connected_to_network event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# client_connected_to_network
+
+This event is triggered when a client connects to a network.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ClientInstanceId|String|The client-generated globally unique identifier of this instance of the Party library.|
+|NetworkIdentifier|String|The network's unique identifier.|
+|RegionName|String|The region name associated with the underlying relay for the network.|
+|HostName|String|The hostname of the relay the client is connecting to.|
+|Port|uint16|The port the client is connecting to.|
+|ConnectDurationInMs|uint32|The duration of the isolated connection operation in milliseconds.|
+|TotalDurationInMs|uint32|The duration of the connection operation and all associated operations queued before it in milliseconds.|
+|LocalConnectionId|uint32|A local identifier to disambiguate multiple connections to the same network from a single client.|
+|Result|int32|The PartyStateChangeResult of the operation.|
+|ResultMessage|String|A human-readable representation of the Result value.|
+|ErrorDetail|uint32|The PartyError error detail code.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/client-initialization-completed.md b/playfab-docs/api-references/events/Networking/client-initialization-completed.md
new file mode 100644
index 000000000..d8baf8f87
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/client-initialization-completed.md
@@ -0,0 +1,26 @@
+---
+title: client_initialization_completed
+author: raulalbertog
+description: client_initialization_completed event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# client_initialization_completed
+
+This event is triggered when client initialization is completed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ClientInstanceId|String|The client-generated globally unique identifier of this instance of the Party library.|
+|BuildId|String|The identifier of the build that produced this binary.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/client-network-created.md b/playfab-docs/api-references/events/Networking/client-network-created.md
new file mode 100644
index 000000000..a024cc84a
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/client-network-created.md
@@ -0,0 +1,42 @@
+---
+title: client_network_created
+author: raulalbertog
+description: client_network_created event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# client_network_created
+
+This event is triggered when a client network is created.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ClientInstanceId|String|The client-generated globally unique identifier of this instance of the Party library.|
+|NetworkIdentifier|String|The network's unique identifier.|
+|RegionName|String|The region name associated with the newly created network. Empty if the creation failed.|
+|ServerId|String|The ServerId field from the PlayFab RequestPartyResponse.|
+|VmId|String|The VmId field from the PlayFab RequestPartyResponse.|
+|DurationInMs|uint32|The duration of this request in milliseconds.|
+|Result|int32|The PartyStateChangeResult of the operation.|
+|ResultMessage|String|A human-readable representation of the Result value.|
+|ErrorDetail|uint32|The PartyError error detail code.|
+|RegionCount|uint32|The count of regions specified when creating the network.|
+|MaxUserCount|uint32|The maximum user count specified in the network configuration.|
+|MaxDeviceCount|uint32|The maximum device count specified in the network configuration.|
+|MaxUsersPerDeviceCount|uint32|The maximum users per device count specified in the network configuration.|
+|MaxDevicesPerUserCount|uint32|The maximum devices per user count specified in the network configuration.|
+|MaxEndpointsPerDeviceCount|uint32|The maximum endpoints per device count specified in the network configuration.|
+|DirectPeerConnectivityOptions|int32|The direct peer connectivity options specified when creating the network.|
+|RequestedRelayVersion|String|The requested relay protocol version.|
+|RequestedRelayBuildAliasId|String|The requested relay build alias ID.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/client-network-destroyed.md b/playfab-docs/api-references/events/Networking/client-network-destroyed.md
new file mode 100644
index 000000000..342af177a
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/client-network-destroyed.md
@@ -0,0 +1,33 @@
+---
+title: client_network_destroyed
+author: raulalbertog
+description: client_network_destroyed event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# client_network_destroyed
+
+This event is triggered when a client network is destroyed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ClientInstanceId|String|The client-generated globally unique identifier of this instance of the Party library.|
+|NetworkIdentifier|String|The network's unique identifier at the time it was destroyed.|
+|RegionName|String|The region name associated with the underlying relay for the network.|
+|HostName|String|The relay's hostname.|
+|Port|uint16|The relay's port.|
+|LocalConnectionId|uint32|A local identifier to disambiguate multiple connections to the same network from a single client.|
+|Reason|int32|The PartyDestroyedReason that the network was destroyed.|
+|ReasonMessage|String|A human-readable representation of the Reason value.|
+|ErrorDetail|uint32|The PartyError error detail code.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/client-network-information-received.md b/playfab-docs/api-references/events/Networking/client-network-information-received.md
new file mode 100644
index 000000000..db236fe29
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/client-network-information-received.md
@@ -0,0 +1,35 @@
+---
+title: client_network_information_received
+author: raulalbertog
+description: client_network_information_received event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# client_network_information_received
+
+This event is triggered when client network information is received.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ClientInstanceId|String|The client-generated globally unique identifier of this instance of the Party library.|
+|NetworkIdentifier|String|The network's unique identifier.|
+|NetworkInformationDurationInMs|uint32|The duration of the connection operation up to the point of receiving the network information, in milliseconds.|
+|TotalDurationInMs|uint32|The duration of the connection operation, receiving the network information, and all associated operations queued before it in milliseconds.|
+|MaxUserCount|uint32|The maximum user count specified in the network configuration.|
+|MaxDeviceCount|uint32|The maximum device count specified in the network configuration.|
+|MaxUsersPerDeviceCount|uint32|The maximum users per device count specified in the network configuration.|
+|MaxDevicesPerUserCount|uint32|The maximum devices per user count specified in the network configuration.|
+|MaxEndpointsPerDeviceCount|uint32|The maximum endpoints per device count specified in the network configuration.|
+|NetworkDirectPeerConnectivityOptions|int32|The direct peer connectivity options specified in the network configuration.|
+|LocalDeviceDirectPeerConnectivityOptions|int32|The direct peer connectivity options specified by the local device when connecting to the network.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/client-request-failed.md b/playfab-docs/api-references/events/Networking/client-request-failed.md
new file mode 100644
index 000000000..794f89704
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/client-request-failed.md
@@ -0,0 +1,31 @@
+---
+title: client_request_failed
+author: raulalbertog
+description: client_request_failed event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# client_request_failed
+
+This event is triggered when a client request fails.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ClientInstanceId|String|The client-generated globally unique identifier of this instance of the Party library.|
+|RequestType|String|The type of the request that failed.|
+|HttpStatusCode|int32|The HTTP status code of the failed request.|
+|HttpStatusString|String|The HTTP status string of the failed request.|
+|PlayFabErrorCode|int32|The PlayFab error code.|
+|ErrorName|String|The PlayFab error name.|
+|ErrorMessage|String|The PlayFab error message.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/data-received-by-clients.md b/playfab-docs/api-references/events/Networking/data-received-by-clients.md
new file mode 100644
index 000000000..eb1ee2736
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/data-received-by-clients.md
@@ -0,0 +1,27 @@
+---
+title: data_received_by_clients
+author: raulalbertog
+description: data_received_by_clients event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# data_received_by_clients
+
+This event is triggered when data is received by clients.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|LoginIdentityProvider|String|The identity provider used for login.|
+|RegionName|String|The region name associated with the relay.|
+|DataSizeInBytes|uint64|The total data size in bytes received by clients from the cloud service.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/data-sent-by-clients.md b/playfab-docs/api-references/events/Networking/data-sent-by-clients.md
new file mode 100644
index 000000000..fd55f6da5
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/data-sent-by-clients.md
@@ -0,0 +1,27 @@
+---
+title: data_sent_by_clients
+author: raulalbertog
+description: data_sent_by_clients event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# data_sent_by_clients
+
+This event is triggered when data is sent by clients.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|LoginIdentityProvider|String|The identity provider used for login.|
+|RegionName|String|The region name associated with the relay.|
+|DataSizeInBytes|uint64|The total data size in bytes sent by clients to the cloud service.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/moderation-service-request-count.md b/playfab-docs/api-references/events/Networking/moderation-service-request-count.md
new file mode 100644
index 000000000..3ae8d17cf
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/moderation-service-request-count.md
@@ -0,0 +1,27 @@
+---
+title: moderation_service_request_count
+author: raulalbertog
+description: moderation_service_request_count event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# moderation_service_request_count
+
+This event is triggered when moderation service request count is reported.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|LoginIdentityProvider|String|The identity provider used for login.|
+|RegionName|String|The region name associated with the relay.|
+|DataSizeInBytes|uint64|The total count of moderation service requests.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/player-disconnected-from-network.md b/playfab-docs/api-references/events/Networking/player-disconnected-from-network.md
new file mode 100644
index 000000000..8c9267502
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/player-disconnected-from-network.md
@@ -0,0 +1,28 @@
+---
+title: player_disconnected_from_network
+author: raulalbertog
+description: player_disconnected_from_network event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_disconnected_from_network
+
+This event is triggered when a player disconnects from a network.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|LoginIdentityProvider|String|The identity provider used for login.|
+|RegionName|String|The region name associated with the relay.|
+|ChatDurationInMs|uint64|The total duration of chat time in milliseconds.|
+|ConnectedDurationInMs|uint64|The total duration the player was connected to the network in milliseconds.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/unity-client-initialization-completed.md b/playfab-docs/api-references/events/Networking/unity-client-initialization-completed.md
new file mode 100644
index 000000000..084656ea5
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/unity-client-initialization-completed.md
@@ -0,0 +1,34 @@
+---
+title: unity_client_initialization_completed
+author: raulalbertog
+description: unity_client_initialization_completed event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# unity_client_initialization_completed
+
+This event is triggered when Unity client initialization is completed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ClientInstanceId|String|A unique identifier for this game session.|
+|PartyVersion|String|The version of the Party native library.|
+|PartyUnityVersion|String|The version of the Party Unity SDK.|
+|UnityVersion|String|The version of the Unity engine.|
+|OSName|String|The name of the operating system.|
+|DeviceMake|String|The device manufacturer name.|
+|DeviceModel|String|The device model name.|
+|Platform|String|The Unity runtime platform.|
+|AppName|String|The application product name.|
+|AppVersion|String|The application version.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Networking/unreal-client-initialization-completed.md b/playfab-docs/api-references/events/Networking/unreal-client-initialization-completed.md
new file mode 100644
index 000000000..84fcbe122
--- /dev/null
+++ b/playfab-docs/api-references/events/Networking/unreal-client-initialization-completed.md
@@ -0,0 +1,37 @@
+---
+title: unreal_client_initialization_completed
+author: raulalbertog
+description: unreal_client_initialization_completed event.
+ms.author: raulalbertog
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# unreal_client_initialization_completed
+
+This event is triggered when Unreal client initialization is completed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ClientInstanceId|String|A unique identifier for this game session.|
+|PartyVersion|String|The version of the Party native library.|
+|UnrealEngineVersion|String|The version of the Unreal Engine.|
+|PlatformSDKVersion|String|The version of the platform SDK.|
+|OSSPlayFabVersion|String|The version of the OnlineSubsystemPlayFab plugin.|
+|TitleID|String|The PlayFab title ID.|
+|OSName|String|The name of the operating system.|
+|OSVersion|String|The version of the operating system.|
+|DeviceMake|String|The device manufacturer name.|
+|DeviceModel|String|The device model name.|
+|PlatformName|String|The name of the platform.|
+|AppName|String|The application name.|
+|AppVersion|String|The application version.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Partner/display-name-filtered.md b/playfab-docs/api-references/events/Partner/display-name-filtered.md
new file mode 100644
index 000000000..40bfb0168
--- /dev/null
+++ b/playfab-docs/api-references/events/Partner/display-name-filtered.md
@@ -0,0 +1,26 @@
+---
+title: display_name_filtered
+author: joannaleecy
+description: display_name_filtered event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# display_name_filtered
+
+This event is triggered when a display name is filtered by community sift.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DisplayName|String|Value of the display name that was filtered|
+|PlayerId|String|If event occurs at account creation, then no player exists yet. Otherwise, the player whose displayname update was filtered|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Partner/player-display-name-filtered.md b/playfab-docs/api-references/events/Partner/player-display-name-filtered.md
new file mode 100644
index 000000000..7230f362c
--- /dev/null
+++ b/playfab-docs/api-references/events/Partner/player-display-name-filtered.md
@@ -0,0 +1,26 @@
+---
+title: player_display_name_filtered
+author: joannaleecy
+description: player_display_name_filtered event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_display_name_filtered
+
+This event is triggered when a display name is filtered by community sift only if there is an associated player EntityId for the event.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DisplayName|String|Value of the display name that was filtered|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Partner/player-photon-session-authenticated.md b/playfab-docs/api-references/events/Partner/player-photon-session-authenticated.md
new file mode 100644
index 000000000..33d37d248
--- /dev/null
+++ b/playfab-docs/api-references/events/Partner/player-photon-session-authenticated.md
@@ -0,0 +1,27 @@
+---
+title: player_photon_session_authenticated
+author: joannaleecy
+description: player_photon_session_authenticated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_photon_session_authenticated
+
+This event is triggered when a player connects to a Photon Cloud application and authenticates with PlayFab using Photon custom authentication.
+
+Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|PhotonApplicationId|String|Unique identifier of the Photon Cloud application to which the player is connected|
+|PhotonApplicationType|[PhotonServicesEnum](../data-types/photonservicesenum.md)|Type of Photon Cloud application to which the player is connected|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayStream/action-executed.md b/playfab-docs/api-references/events/PlayStream/action-executed.md
new file mode 100644
index 000000000..4de21e18f
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayStream/action-executed.md
@@ -0,0 +1,27 @@
+---
+title: action_executed
+author: joelku
+description: action_executed event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# action_executed
+
+This event is emitted when an action is executed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Data|[ActionResultDetails](../data-types/actionresultdetails.md)|The result of the action.|
+|Trigger|[ActionTrigger](../data-types/actiontrigger.md)|Information about the trigger that initiated the action.|
+|EventDetails|[ActionEventDetails](../data-types/actioneventdetails.md)|Information about the event that triggered the action.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayStream/action-failed.md b/playfab-docs/api-references/events/PlayStream/action-failed.md
new file mode 100644
index 000000000..be1b4102d
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayStream/action-failed.md
@@ -0,0 +1,27 @@
+---
+title: action_failed
+author: joelku
+description: action_failed event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# action_failed
+
+This event is emitted when an action failed to execute.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Error|[ActionFailure](../data-types/actionfailure.md)|Information about the error that occurred during execution.|
+|Trigger|[ActionTrigger](../data-types/actiontrigger.md)|Information about the trigger that initiated the action.|
+|EventDetails|[ActionEventDetails](../data-types/actioneventdetails.md)|Information about the event that triggered the action.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Player/player-action-executed.md b/playfab-docs/api-references/events/Player/player-action-executed.md
new file mode 100644
index 000000000..f90fa1a56
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-action-executed.md
@@ -0,0 +1,33 @@
+---
+title: player_action_executed
+author: joannaleecy
+description: player_action_executed event.
+ms.author: jenelleb
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_action_executed
+
+This event is triggered when an action linked to a segmentation change or event rule executes on a player.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ActionName|String|Name of the action that was triggered.|
+|Error|[ActionExecutionError](../data-types/actionexecutionerror.md)|Information about the error that occurred during execution, if it failed to complete.|
+|ExecutionDuration|double|Action execution time in milliseconds.|
+|ExecutionResult|object|The object returned from the action execution, if it completed.|
+|ScheduledTimestamp|DateTime|Time that the action was scheduled for execution.|
+|TitleId|String|The ID of the title to which this player event applies.|
+|TriggeredTimestamp|DateTime|Time that the triggering event or segmentation change occurred.|
+|TriggeringEventRuleMatch|[EventRuleMatch](../data-types/eventrulematch.md)|Event rule match, if any, that triggered the action.|
+|TriggeringSegmentMembershipChange|[SegmentMembershipChange](../data-types/segmentmembershipchange.md)|Player segmentation change, if any, that triggered the action.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Player/player-ad-campaign-attribution.md b/playfab-docs/api-references/events/Player/player-ad-campaign-attribution.md
new file mode 100644
index 000000000..63492ad71
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-ad-campaign-attribution.md
@@ -0,0 +1,26 @@
+---
+title: player_ad_campaign_attribution
+author: joannaleecy
+description: player_ad_campaign_attribution event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_ad_campaign_attribution
+
+This event is triggered by an attribution tracking Add-on when a player is matched to a paid acquisition campaign.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CampaignId|String|The ID of the campaign, as passed in by the attribution provider.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Player/player-consumed-item.md b/playfab-docs/api-references/events/Player/player-consumed-item.md
new file mode 100644
index 000000000..177165e65
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-consumed-item.md
@@ -0,0 +1,30 @@
+---
+title: player_consumed_item
+author: ernestoc
+description: player_consumed_item event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_consumed_item
+
+This event is triggered when a player consumes an item from their inventory.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| CatalogVersion | String | Version of the catalog from which the consumed inventory item was created. |
+| ItemId | String | ID of the catalog item from which the consumed inventory item was created. This can be used to look up the item from the catalog. |
+| ItemInstanceId | String | The specific ID of the item that was consumed. |
+| PreviousUsesRemaining | uint32 | For multiple use items, the number of uses that remained before the item was consumed. |
+| TitleId | String | The ID of the title to which this player event applies. |
+| UsesRemaining | uint32 | For multiple use items, the number of uses remaining after the item was consumed. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Player/player-inventory-item-added.md b/playfab-docs/api-references/events/Player/player-inventory-item-added.md
new file mode 100644
index 000000000..caf7ac919
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-inventory-item-added.md
@@ -0,0 +1,35 @@
+---
+title: player_inventory_item_added
+author: ernestoc
+description: player_inventory_item_added event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_inventory_item_added
+
+This event is triggered when an item is granted to a player.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| Annotation | String | Optional details about the inventory item. |
+| BundleContents | [] | Catalog item IDs of any other items granted to the player along with this one as part of a bundle. |
+| CatalogVersion | String | Catalog version in which the item that was added is defined. |
+| Class | String | Class of the item that was added. |
+| CouponCode | String | Redeemed coupon (if any) that granted the item. |
+| DisplayName | String | Display name of the item that was added. |
+| Expiration | DateTime | When the item expires. The value is null if the item does not expire. |
+| InstanceId | String | Unique instance ID of the inventory item that was added. |
+| ItemId | String | Catalog item ID of the inventory item that was added. |
+| RemainingUses | uint32 | How many uses the item has, if it has a limited number of uses. |
+| TitleId | String | The ID of the title to which this player event applies. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Player/player-paid-for-purchase.md b/playfab-docs/api-references/events/Player/player-paid-for-purchase.md
new file mode 100644
index 000000000..159bd5b68
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-paid-for-purchase.md
@@ -0,0 +1,35 @@
+---
+title: player_paid_for_purchase
+author: ernestoc
+description: player_paid_for_purchase event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_paid_for_purchase
+
+This event is triggered when the second step of the payment process completes, paying for the purchase.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| OrderId | String | Purchase order identifier. |
+| ProviderData | String | Provider used for the transaction. |
+| ProviderName | String | Payment provider to use to fund the purchase. |
+| ProviderToken | String | A token generated by the provider to authenticate the request (provider-specific). |
+| PurchaseConfirmationPageURL | String | URL to the purchase provider page that details the purchase. |
+| PurchaseCurrency | String | Currency for the transaction, may be a virtual currency or real money. |
+| PurchasePrice | uint32 | Cost of the transaction. |
+| Status | [TransactionStatus](../data-types/transactionstatus.md) | Status of the transaction. |
+| TitleId | String | The ID of the title to which this player event applies. |
+| VirtualCurrencyBalances | Object | Current virtual currency balances for the user. |
+| VirtualCurrencyGrants | Object | Virtual currencies granted by the transaction, if any. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Player/player-realmoney-purchase.md b/playfab-docs/api-references/events/Player/player-realmoney-purchase.md
new file mode 100644
index 000000000..496b4a8db
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-realmoney-purchase.md
@@ -0,0 +1,33 @@
+---
+title: player_realmoney_purchase
+author: ernestoc
+description: player_realmoney_purchase event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_realmoney_purchase
+
+This event is triggered when a player makes a real money purchase, and generates revenue for the game.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| OrderId | String | Unique identifier of the order. |
+| OrderTotal | uint32 | Total value of the purchase in the system currency (defaults to USD). |
+| PaymentProvider | String | Payment provider used to make the purchase. |
+| PaymentType | [PaymentType](../data-types/paymenttype.md) | Type of payment used to make the purchase. |
+| PurchasedProduct | [] | The ItemIds from the catalog of the purchased items, if applicable. |
+| TitleId | String | The ID of the title to which this player event applies. |
+| TransactionCurrency | [Currency](../data-types/currency.md) | Local currency used to make the purchase, if applicable. |
+| TransactionId | String | Unique identifier of the transaction. |
+| TransactionTotal | uint32 | Total value of the purchase in the local currency used to make the purchase, if applicable. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Player/player-receipt-validation.md b/playfab-docs/api-references/events/Player/player-receipt-validation.md
new file mode 100644
index 000000000..51900258d
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-receipt-validation.md
@@ -0,0 +1,30 @@
+---
+title: player_receipt_validation
+author: ernestoc
+description: player_receipt_validation event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_receipt_validation
+
+This event is triggered when a player attempts to make a real money purchase and the purchase receipt is being validated.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| Error | String | The error that occurred during a receipt validation. |
+| PaymentProvider | String | Payment provider used to make the purchase attempt. |
+| PaymentType | [PaymentType](../data-types/paymenttype.md) | Type of payment used to make the purchase attempt. |
+| ReceiptContent | String | The receipt data during a real money purchase event attempt. |
+| TitleId | String | The ID of the title to which this player event applies. |
+| Valid | Boolean | Indicates if the receipt is valid. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Player/player-redeemed-coupon.md b/playfab-docs/api-references/events/Player/player-redeemed-coupon.md
new file mode 100644
index 000000000..57019e80a
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-redeemed-coupon.md
@@ -0,0 +1,27 @@
+---
+title: player_redeemed_coupon
+author: ernestoc
+description: player_redeemed_coupon event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_redeemed_coupon
+
+This event is triggered when a player redeems a coupon.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| CouponCode | String | Coupon code the player redeemed. |
+| GrantedInventoryItems | [CouponGrantedInventoryItem](../data-types/coupongrantedinventoryitem.md) | Items added to the player's inventory by redeeming the coupon. |
+| TitleId | String | The ID of the title to which this player event applies. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Player/player-set-profile-property.md b/playfab-docs/api-references/events/Player/player-set-profile-property.md
new file mode 100644
index 000000000..ff32528c2
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-set-profile-property.md
@@ -0,0 +1,27 @@
+---
+title: player_set_profile_property
+author: joannaleecy
+description: player_set_profile_property event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_set_profile_property
+
+This event is triggered when PlayFab makes an internal adjustment to a player profile.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Property|[PlayerProfileProperty](../data-types/playerprofileproperty.md)|Property of the profile to be set|
+|TitleId|String|The ID of the title to which this player event applies.|
+|Value|object|Value to set to|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Player/player-started-purchase.md b/playfab-docs/api-references/events/Player/player-started-purchase.md
new file mode 100644
index 000000000..7ae855413
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-started-purchase.md
@@ -0,0 +1,29 @@
+---
+title: player_started_purchase
+author: ernestoc
+description: player_started_purchase event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_started_purchase
+
+This event is triggered when a player starts a purchase.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| CatalogVersion | String | Catalog version for the items to be purchased. Defaults to most recent catalog. |
+| Contents | [CartItem](../data-types/cartitem.md) | Cart items to be purchased. |
+| OrderId | String | Purchase order identifier. |
+| StoreId | String | Store through which to purchase items. If not set, prices will be pulled from the catalog itself. |
+| TitleId | String | The ID of the title to which this player event applies. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Player/player-vc-item-purchased.md b/playfab-docs/api-references/events/Player/player-vc-item-purchased.md
new file mode 100644
index 000000000..33cc2f3ec
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-vc-item-purchased.md
@@ -0,0 +1,32 @@
+---
+title: player_vc_item_purchased
+author: ernestoc
+description: player_vc_item_purchased event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_vc_item_purchased
+
+This event is triggered when the player makes a purchase using virtual currency.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| CatalogVersion | String | Version of the catalog from which the item was purchased. |
+| CurrencyCode | String | Currency that was used to purchase the item. |
+| ItemId | String | Identifier of the catalog item that was purchased. |
+| PurchaseId | String | Unique identifier of the purchase transaction. |
+| Quantity | int32 | Quantity of items that were purchased. |
+| StoreId | String | The StoreId where the item was purchased. |
+| TitleId | String | The ID of the title to which this player event applies. |
+| UnitPrice | uint32 | Price paid per item, expressed in the virtual currency. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Player/player-virtual-currency-balance-changed.md b/playfab-docs/api-references/events/Player/player-virtual-currency-balance-changed.md
new file mode 100644
index 000000000..dc0d14f2f
--- /dev/null
+++ b/playfab-docs/api-references/events/Player/player-virtual-currency-balance-changed.md
@@ -0,0 +1,29 @@
+---
+title: player_virtual_currency_balance_changed
+author: ernestoc
+description: player_virtual_currency_balance_changed event.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_virtual_currency_balance_changed
+
+This event is triggered when a player's virtual currency balance changes.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| OrderId | String | Id of the order that triggered the balance changes |
+| TitleId | String | The ID of the title to which this player event applies. |
+| VirtualCurrencyBalance | int32 | New virtual currency balance after the change. |
+| VirtualCurrencyName | String | Virtual currency whose balance changed. |
+| VirtualCurrencyPreviousBalance | int32 | Old virtual currency balance before the change. |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/auth-token-validated.md b/playfab-docs/api-references/events/PlayerIdentity/auth-token-validated.md
new file mode 100644
index 000000000..ea069fd13
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/auth-token-validated.md
@@ -0,0 +1,27 @@
+---
+title: auth_token_validated
+author: joannaleecy
+description: auth_token_validated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# auth_token_validated
+
+This event is triggered when an email confirmation link is clicked.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EmailTemplateId|String|The email template id, if the auth token was sent via an email template.|
+|TitleId|String|The ID of the title to which this player event applies.|
+|Token|String|The email token in the confirmation link that was clicked.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/character-created.md b/playfab-docs/api-references/events/PlayerIdentity/character-created.md
new file mode 100644
index 000000000..f505551b9
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/character-created.md
@@ -0,0 +1,28 @@
+---
+title: character_created
+author: joannaleecy
+description: character_created event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# character_created
+
+## Properties
+
+This event is triggered when a character is created for the first time. 
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CharacterName|String|Name of the character.|
+|Created|DateTime|When the character was created.|
+|PlayerId|String||
+|TitleId|String||
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/entity-created.md b/playfab-docs/api-references/events/PlayerIdentity/entity-created.md
new file mode 100644
index 000000000..9676df678
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/entity-created.md
@@ -0,0 +1,26 @@
+---
+title: entity_created
+author: joannaleecy
+description: entity_created event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# entity_created
+
+This event is triggered when an entity is created.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/entity-deleted.md b/playfab-docs/api-references/events/PlayerIdentity/entity-deleted.md
new file mode 100644
index 000000000..e7972fcee
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/entity-deleted.md
@@ -0,0 +1,23 @@
+---
+title: entity_deleted
+author: ronnyparedes
+description: entity_deleted event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# entity_deleted
+
+This event is triggered upon deletion of an entity.
+
+## Properties
+
+This event has no additional properties beyond the common properties. The entity context is provided in the common properties.
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/entity-logged-in.md b/playfab-docs/api-references/events/PlayerIdentity/entity-logged-in.md
new file mode 100644
index 000000000..8f1b80b56
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/entity-logged-in.md
@@ -0,0 +1,28 @@
+---
+title: entity_logged_in
+author: joannaleecy
+description: entity_logged_in event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# entity_logged_in
+
+This event is triggered when an entity has logged in.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
+
+
diff --git a/playfab-docs/api-references/events/PlayerIdentity/logged-in-to-title.md b/playfab-docs/api-references/events/PlayerIdentity/logged-in-to-title.md
new file mode 100644
index 000000000..0d3d9b110
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/logged-in-to-title.md
@@ -0,0 +1,25 @@
+---
+title: logged_in_to_title
+author: ronnyparedes
+description: logged_in_to_title event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# logged_in_to_title
+
+This event is triggered when a master_player_account entity logs in to a title to obtain a title_player_account entity token.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityTokenId|String|Unique identifier for the generated title_player_account entity token.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-added-title.md b/playfab-docs/api-references/events/PlayerIdentity/player-added-title.md
new file mode 100644
index 000000000..68357d292
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-added-title.md
@@ -0,0 +1,28 @@
+---
+title: player_added_title
+author: joannaleecy
+description: player_added_title event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_added_title
+
+This event is triggered when a player creates a new account for a title. Note: this event is triggered once per title rather than once per publisher.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DisplayName|String|Player's display name when they added this title.|
+|Platform|[LoginIdentityProvider](../data-types/loginidentityprovider.md)|Authentication method used to register player's account.|
+|PlatformUserId|String|Unique ID for the player's account associated with the Origination authentication method.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-authenticated.md b/playfab-docs/api-references/events/PlayerIdentity/player-authenticated.md
new file mode 100644
index 000000000..62aabb8be
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-authenticated.md
@@ -0,0 +1,27 @@
+---
+title: player_authenticated
+author: ronnyparedes
+description: player_authenticated event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_authenticated
+
+This event is triggered when a player account (master_player_account entity) is authenticated using a player identity from a player identity provider.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityTokenId|String|Unique identifier for the generated master_player_account entity token for authenticating subsequent API calls.|
+|IdentityProvider|String|Name of the player identity provider used to authenticate the player identity.|
+|IdentityProviderIssuedId|String|Unique ID of the player identity within the player identity provider.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-banned.md b/playfab-docs/api-references/events/PlayerIdentity/player-banned.md
new file mode 100644
index 000000000..96f646051
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-banned.md
@@ -0,0 +1,29 @@
+---
+title: player_banned
+author: joannaleecy
+description: player_banned event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_banned
+
+This event is triggered when a player is banned.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|BanExpiration|DateTime|When the ban expires. The value is null if the ban is permanent.|
+|BanId|String|ID of the ban. Useful for tracking unique bans, if the player has been banned before.|
+|BanReason|String|The reason why the player was banned.|
+|PermanentBan|Boolean|Whether this ban is permanent.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-changed-avatar.md b/playfab-docs/api-references/events/PlayerIdentity/player-changed-avatar.md
new file mode 100644
index 000000000..cba786a9d
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-changed-avatar.md
@@ -0,0 +1,27 @@
+---
+title: player_changed_avatar
+author: joannaleecy
+description: player_changed_avatar event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_changed_avatar
+
+This event is triggered when a player's avatar URL is changed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ImageUrl|String|URL of the avatar image.|
+|PreviousImageUrl|String|Previous URL of the avatar image.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-completed-password-reset.md b/playfab-docs/api-references/events/PlayerIdentity/player-completed-password-reset.md
new file mode 100644
index 000000000..3e54c89b6
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-completed-password-reset.md
@@ -0,0 +1,33 @@
+---
+title: player_completed_password_reset
+author: joannaleecy
+description: player_completed_password_reset event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_completed_password_reset
+
+This event is triggered when a player completes the password reset process by visiting the link URL that was sent to them and choosing a new password.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|CompletedFromIPAddress|String|IP address from which the password reset process was completed.|
+|CompletionTimestamp|DateTime|When the password reset process was completed.|
+|InitiatedBy|[PasswordResetInitiationSource](../data-types/passwordresetinitiationsource.md)|Source that initiated the password reset process.|
+|InitiatedFromIPAddress|String|IP address from which the password reset process was initiated.|
+|InitiationTimestamp|DateTime|When the password reset process was initiated.|
+|LinkExpiration|DateTime|Expiration time for the password reset link.|
+|PasswordResetId|String|Unique identifier for the password reset link. This cannot be used to complete the reset.|
+|RecoveryEmailAddress|String|Email address to which the password reset link was sent.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-created.md b/playfab-docs/api-references/events/PlayerIdentity/player-created.md
new file mode 100644
index 000000000..0b20f2e33
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-created.md
@@ -0,0 +1,27 @@
+---
+title: player_created
+author: joannaleecy
+description: player_created event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_created
+
+This event is triggered when a player account is created for the first time. Note: this event is only triggered once per publisher, not once per title.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Created|DateTime|When the player account was created.|
+|PublisherId|String|Unique ID for the publisher account under which this player account is created.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/auth-token-validated.md b/playfab-docs/api-references/events/PlayerIdentity/player-custom-properties-changed.md
similarity index 66%
rename from playfab-docs/api-references/events/auth-token-validated.md
rename to playfab-docs/api-references/events/PlayerIdentity/player-custom-properties-changed.md
index 0e3c0b93c..7668c2b6a 100644
--- a/playfab-docs/api-references/events/auth-token-validated.md
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-custom-properties-changed.md
@@ -1,26 +1,25 @@
 ---
-title: auth_token_validated
-author: joannaleecy
-description: auth_token_validated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
+title: player_custom_properties_changed
+author: ronnyparedes
+description: player_custom_properties_changed event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
 ms.topic: article
 ms.service: azure-playfab
 keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# auth_token_validated
+# player_custom_properties_changed
 
-This event is triggered when an email confirmation link is clicked.
+This event is triggered when a player's custom properties are altered.
 
 ## Properties
 
 |Name|Type|Description|
 | :--------------------|:-------------------|:----------------------|
-|EmailTemplateId|String|The email template id, if the auth token was sent via an email template.|
+|ChangeDetails|[PlayerCustomPropertiesChangedDetails](../data-types/playercustompropertieschangeddetails.md)[]|Set of changes being applied to the player's custom properties.|
 |TitleId|String|The ID of the title to which this player event applies.|
-|Token|String|The email token in the confirmation link that was clicked.|
 
 ## Common Properties
 
@@ -34,8 +33,8 @@ All PlayStream events are formatted as JSON objects and share the following comm
 |EventId|String|PlayFab-assigned unique identifier for this event.|
 |EventName|String|The name of this event.|
 |EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
+|History|[PlayStreamEventHistory](../data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
 |Reserved|object|Reserved exclusively for PlayFab internal use.|
 |Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
+|SourceType|[SourceType](../data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
 |Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-data-exported.md b/playfab-docs/api-references/events/PlayerIdentity/player-data-exported.md
new file mode 100644
index 000000000..56f9944b3
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-data-exported.md
@@ -0,0 +1,28 @@
+---
+title: player_data_exported
+author: joannaleecy
+description: player_data_exported event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_data_exported
+
+This event is triggered when a player's data is exported.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ExportDownloadUrl|String|URL to download the export.|
+|JobReceiptId|String|Receipt ID of the export job. This should correspond to the receipt ID returned by the export API call.|
+|RequestTime|DateTime|The time of export request.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-device-info.md b/playfab-docs/api-references/events/PlayerIdentity/player-device-info.md
new file mode 100644
index 000000000..32462d47f
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-device-info.md
@@ -0,0 +1,26 @@
+---
+title: player_device_info
+author: joannaleecy
+description: player_device_info event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_device_info
+
+This event is triggered once after the player logs in based on the settings for your title.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeviceInfo|Object||
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-displayname-changed.md b/playfab-docs/api-references/events/PlayerIdentity/player-displayname-changed.md
new file mode 100644
index 000000000..7a0f2d82d
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-displayname-changed.md
@@ -0,0 +1,27 @@
+---
+title: player_displayname_changed
+author: joannaleecy
+description: player_displayname_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_displayname_changed
+
+This event is triggered when a player's display name is changed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DisplayName|String|New display name after the change.|
+|PreviousDisplayName|String|Previous display name before the change.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-identity-link-added.md b/playfab-docs/api-references/events/PlayerIdentity/player-identity-link-added.md
new file mode 100644
index 000000000..4a6d9c645
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-identity-link-added.md
@@ -0,0 +1,27 @@
+---
+title: player_identity_link_added
+author: ronnyparedes
+description: player_identity_link_added event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_identity_link_added
+
+This event is triggered when a player identity from a player identity provider is linked to a master_player_account entity. After linking, the player identity may be used to authenticate the master_player_account.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|IdentityLinkId|String|Unique identifier of the added link between the player identity and master_player_account.|
+|IdentityProvider|String|Name of the player identity provider in which the linked identity exists.|
+|IdentityProviderIssuedId|String|Unique identifier of the linked player identity, as assigned by the player identity provider.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-identity-link-removed.md b/playfab-docs/api-references/events/PlayerIdentity/player-identity-link-removed.md
new file mode 100644
index 000000000..6b23983f0
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-identity-link-removed.md
@@ -0,0 +1,27 @@
+---
+title: player_identity_link_removed
+author: ronnyparedes
+description: player_identity_link_removed event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_identity_link_removed
+
+This event is triggered when a player identity from a player identity provider is unlinked from a master_player_account entity. After unlinking, the player identity may no longer be used to authenticate the master_player_account.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|IdentityLinkId|String|Unique identifier of the removed link between the player identity and master_player_account.|
+|IdentityProvider|String|Name of the player identity provider in which the unlinked identity exists.|
+|IdentityProviderIssuedId|String|Unique identifier of the unlinked player identity, as assigned by the player identity provider.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-linked-account.md b/playfab-docs/api-references/events/PlayerIdentity/player-linked-account.md
new file mode 100644
index 000000000..7c71f0eef
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-linked-account.md
@@ -0,0 +1,29 @@
+---
+title: player_linked_account
+author: joannaleecy
+description: player_linked_account event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_linked_account
+
+This event is triggered when a new authentication method is linked to a player's account.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Email|String|Player's email linked with the given provider|
+|Origination|[LoginIdentityProvider](../data-types/loginidentityprovider.md)|Authentication method being linked to a player's account.|
+|OriginationUserId|String|Player's identity under authentication method being linked to player's account.|
+|TitleId|String|The ID of the title to which this player event applies.|
+|Username|String|Player's username linked with the given provider|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-logged-in.md b/playfab-docs/api-references/events/PlayerIdentity/player-logged-in.md
new file mode 100644
index 000000000..a2cdf2bd7
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-logged-in.md
@@ -0,0 +1,29 @@
+---
+title: player_logged_in
+author: joannaleecy
+description: player_logged_in event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_logged_in
+
+This event is triggered when a player logs in.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Location|[EventLocation](../data-types/eventlocation.md)|Player's geographic location, if known. Location is estimated from factors such as IP address and is not always available or accurate.|
+|Platform|[LoginIdentityProvider](../data-types/loginidentityprovider.md)|Authentication method used to login the player.|
+|PlatformUserId|String|Player's identity under the authentication method used to login the player.|
+|PlatformUserName|String|The display name that's set in the identity provider that the player is authenticated with.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-password-reset-link-sent.md b/playfab-docs/api-references/events/PlayerIdentity/player-password-reset-link-sent.md
new file mode 100644
index 000000000..2173727a5
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-password-reset-link-sent.md
@@ -0,0 +1,30 @@
+---
+title: player_password_reset_link_sent
+author: joannaleecy
+description: player_password_reset_link_sent event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_password_reset_link_sent
+
+This event is triggered when a player is sent a link to reset their password.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|InitiatedBy|[PasswordResetInitiationSource](../data-types/passwordresetinitiationsource.md)|Source that initiated the password reset process.|
+|InitiatedFromIPAddress|String|IP address from which the password reset process was initiated.|
+|LinkExpiration|DateTime|Expiration time for the password reset link.|
+|PasswordResetId|String|Unique identifier for the password reset link. This cannot be used to complete the reset.|
+|RecoveryEmailAddress|String|Email address to which the password reset link was sent.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-removed-title.md b/playfab-docs/api-references/events/PlayerIdentity/player-removed-title.md
new file mode 100644
index 000000000..e90f7563a
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-removed-title.md
@@ -0,0 +1,25 @@
+---
+title: player_removed_title
+author: joannaleecy
+description: player_removed_title event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_removed_title
+
+This event is triggered when a player account for a title is removed. Note: this event is triggered once per title rather than once per publisher.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-reported-as-abusive.md b/playfab-docs/api-references/events/PlayerIdentity/player-reported-as-abusive.md
new file mode 100644
index 000000000..311513ea1
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-reported-as-abusive.md
@@ -0,0 +1,27 @@
+---
+title: player_reported_as_abusive
+author: joannaleecy
+description: player_reported_as_abusive event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_reported_as_abusive
+
+This event is triggered when a player is reported by another player as abusive.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Comment|String|Comment submitted by the player who made the report.|
+|ReportedByPlayer|String|Player ID of the player who made the report.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-tag-added.md b/playfab-docs/api-references/events/PlayerIdentity/player-tag-added.md
new file mode 100644
index 000000000..f9b6db274
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-tag-added.md
@@ -0,0 +1,27 @@
+---
+title: player_tag_added
+author: joannaleecy
+description: player_tag_added event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_tag_added
+
+This event is triggered when a tag is added to a player profile.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Namespace|String|Namespace for this tag|
+|TagName|String|Name of the tag that is added.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-tag-removed.md b/playfab-docs/api-references/events/PlayerIdentity/player-tag-removed.md
new file mode 100644
index 000000000..c63c7b304
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-tag-removed.md
@@ -0,0 +1,27 @@
+---
+title: player_tag_removed
+author: joannaleecy
+description: player_tag_removed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_tag_removed
+
+This event is triggered when a tag is removed from a player profile.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Namespace|String|Namespace for this tag|
+|TagName|String|Name of the tag that is removed.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-unlinked-account.md b/playfab-docs/api-references/events/PlayerIdentity/player-unlinked-account.md
new file mode 100644
index 000000000..c6e6846b7
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-unlinked-account.md
@@ -0,0 +1,27 @@
+---
+title: player_unlinked_account
+author: joannaleecy
+description: player_unlinked_account event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_unlinked_account
+
+This event is triggered when an authentication method is unlinked from a player's account.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Origination|[LoginIdentityProvider](../data-types/loginidentityprovider.md)|Authentication method being unlinked from a player's account.|
+|OriginationUserId|String|Player's identity under authentication method being unlinked from player's account.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-updated-contact-email.md b/playfab-docs/api-references/events/PlayerIdentity/player-updated-contact-email.md
new file mode 100644
index 000000000..282168e4e
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-updated-contact-email.md
@@ -0,0 +1,28 @@
+---
+title: player_updated_contact_email
+author: joannaleecy
+description: player_updated_contact_email event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_updated_contact_email
+
+This event is triggered when a player updates a contact email on their profile.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EmailName|String|The name of the contact email that was updated or added in the player's profile.|
+|NewEmailAddress|String|The contact email updated or added in the player's profile.|
+|PreviousEmailAddress|String|The previous contact email updated in the player's profile.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-updated-login-email.md b/playfab-docs/api-references/events/PlayerIdentity/player-updated-login-email.md
new file mode 100644
index 000000000..58abb1238
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-updated-login-email.md
@@ -0,0 +1,27 @@
+---
+title: player_updated_login_email
+author: ronnyparedes
+description: player_updated_login_email event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_updated_login_email
+
+This event is triggered when a player's login email is updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|NewEmailAddress|String|The login email updated in the player's profile.|
+|PreviousEmailAddress|String|The previous login email updated in the player's profile.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/player-verified-contact-email.md b/playfab-docs/api-references/events/PlayerIdentity/player-verified-contact-email.md
new file mode 100644
index 000000000..810fb54b5
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/player-verified-contact-email.md
@@ -0,0 +1,27 @@
+---
+title: player_verified_contact_email
+author: joannaleecy
+description: player_verified_contact_email event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_verified_contact_email
+
+This event is triggered when a contact email is verified for a player.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EmailAddress|String|The email address of the player's contact email that was verified.|
+|EmailName|String|The name of the player's contact email that was verified.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/title-deleted-master-player.md b/playfab-docs/api-references/events/PlayerIdentity/title-deleted-master-player.md
new file mode 100644
index 000000000..49f879ad3
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/title-deleted-master-player.md
@@ -0,0 +1,27 @@
+---
+title: title_deleted_master_player
+author: joannaleecy
+description: title_deleted_master_player event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_deleted_master_player
+
+This event is triggered when a GDPR delete is finished.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|MetaData|String|Identifying information for title entered by developer.|
+|PlayerId|String|Master Player ID who was deleted.|
+|ReceiptId|String|Receipt ID of the delete that has been finished.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/title-initiated-player-password-reset.md b/playfab-docs/api-references/events/PlayerIdentity/title-initiated-player-password-reset.md
new file mode 100644
index 000000000..e454a687f
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/title-initiated-player-password-reset.md
@@ -0,0 +1,29 @@
+---
+title: title_initiated_player_password_reset
+author: joannaleecy
+description: title_initiated_player_password_reset event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_initiated_player_password_reset
+
+This event is triggered when a title initiates the account recovery process for a player.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|PasswordResetId|String|Unique identifier for the password reset link. This cannot be used to complete the reset.|
+|PlayerId|String|Player's account ID.|
+|PlayerRecoveryEmailAddress|String|Email address to which the account recovery email was sent.|
+|UserId|String||
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerIdentity/title-profile-view-constraints-changed.md b/playfab-docs/api-references/events/PlayerIdentity/title-profile-view-constraints-changed.md
new file mode 100644
index 000000000..2a719433e
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerIdentity/title-profile-view-constraints-changed.md
@@ -0,0 +1,29 @@
+---
+title: title_profile_view_constraints_changed
+author: joannaleecy
+description: title_profile_view_constraints_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_profile_view_constraints_changed
+
+This event is triggered when a profile view constraint is changed for the title.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|PreviousProfileViewConstraints|String|Profile view constraints before the change as a JSON string.|
+|ProfileType|String|The profile type of the profile view constraints.|
+|ProfileViewConstraints|String|Profile view constraints after the change as a JSON string.|
+|UserId|String||
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerProfile/access-policy-updated.md b/playfab-docs/api-references/events/PlayerProfile/access-policy-updated.md
new file mode 100644
index 000000000..10a9f331d
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerProfile/access-policy-updated.md
@@ -0,0 +1,27 @@
+---
+title: access_policy_updated
+author: ronnyparedes
+description: access_policy_updated event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# access_policy_updated
+
+This event is triggered when a profile access policy has been updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AccessPolicy|String[]|The new access policy statements.|
+|Operation|[OperationTypes](../data-types/operationtypes.md)|The type of operation that was performed on the access policy.|
+|PreviousAccessPolicy|String[]|The previous access policy statements.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerProfile/avatar-url-updated.md b/playfab-docs/api-references/events/PlayerProfile/avatar-url-updated.md
new file mode 100644
index 000000000..111cde07b
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerProfile/avatar-url-updated.md
@@ -0,0 +1,25 @@
+---
+title: avatar_url_updated
+author: ronnyparedes
+description: avatar_url_updated event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# avatar_url_updated
+
+This event is triggered when the avatar URL of a profile has been updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AvatarUrl|String|The new avatar URL for the profile.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerProfile/contact-email-updated.md b/playfab-docs/api-references/events/PlayerProfile/contact-email-updated.md
new file mode 100644
index 000000000..1b0ea3278
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerProfile/contact-email-updated.md
@@ -0,0 +1,27 @@
+---
+title: contact_email_updated
+author: ronnyparedes
+description: contact_email_updated event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# contact_email_updated
+
+This event is triggered when the contact email addresses of a profile have been updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ContactEmails|[ContactEmailDetails](../data-types/contactemaildetails.md)[]|The new contact email addresses for the profile.|
+|Operation|[OperationTypes](../data-types/operationtypes.md)|The type of operation that was performed on the contact emails.|
+|PreviousContactEmails|[ContactEmailDetails](../data-types/contactemaildetails.md)[]|The previous contact email addresses for the profile.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerProfile/entity-files-set.md b/playfab-docs/api-references/events/PlayerProfile/entity-files-set.md
new file mode 100644
index 000000000..ac39c47ab
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerProfile/entity-files-set.md
@@ -0,0 +1,27 @@
+---
+title: entity_files_set
+author: joannaleecy
+description: entity_files_set event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# entity_files_set
+
+This event is triggered when files are attached to an entity.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Files|[FileSet](../data-types/fileset.md)|The files that were updated.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/PlayerProfile/entity-language-updated.md b/playfab-docs/api-references/events/PlayerProfile/entity-language-updated.md
new file mode 100644
index 000000000..8d58a181c
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerProfile/entity-language-updated.md
@@ -0,0 +1,28 @@
+---
+title: entity_language_updated
+author: joannaleecy
+description: entity_language_updated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# entity_language_updated
+
+This event is triggered when the language associated with an entity is changed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Language|String|Language that was updated|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
+
diff --git a/playfab-docs/api-references/events/PlayerProfile/entity-objects-set.md b/playfab-docs/api-references/events/PlayerProfile/entity-objects-set.md
new file mode 100644
index 000000000..6eb65e038
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerProfile/entity-objects-set.md
@@ -0,0 +1,27 @@
+---
+title: entity_objects_set
+author: joannaleecy
+description: entity_objects_set event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# entity_objects_set
+
+This event is triggered when objects are attached to an entity.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityChain|String|The chain of ownership for this entity.|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|Objects|[ObjectSet](../data-types/objectset.md)|Objects that were updated|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/PlayerProfile/files-changed.md b/playfab-docs/api-references/events/PlayerProfile/files-changed.md
new file mode 100644
index 000000000..6f3c947ee
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerProfile/files-changed.md
@@ -0,0 +1,25 @@
+---
+title: files_changed
+author: ronnyparedes
+description: files_changed event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# files_changed
+
+This event summarizes the changes to files that are attached to an entity.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Files|[FileDetails](../data-types/filedetails.md)[]|The files that were updated.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerProfile/language-updated.md b/playfab-docs/api-references/events/PlayerProfile/language-updated.md
new file mode 100644
index 000000000..08e1b8595
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerProfile/language-updated.md
@@ -0,0 +1,25 @@
+---
+title: language_updated
+author: ronnyparedes
+description: language_updated event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# language_updated
+
+This event is triggered when the language of a profile has been updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Language|String|The new language for the profile.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/PlayerProfile/objects-updated.md b/playfab-docs/api-references/events/PlayerProfile/objects-updated.md
new file mode 100644
index 000000000..94f8ee526
--- /dev/null
+++ b/playfab-docs/api-references/events/PlayerProfile/objects-updated.md
@@ -0,0 +1,25 @@
+---
+title: objects_updated
+author: ronnyparedes
+description: objects_updated event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# objects_updated
+
+This event summarizes the changes to objects that are attached to an entity.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Objects|[ObjectDetails](../data-types/objectdetails.md)[]|The objects that were updated.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Segmentation/api-operation.md b/playfab-docs/api-references/events/Segmentation/api-operation.md
new file mode 100644
index 000000000..3587cf341
--- /dev/null
+++ b/playfab-docs/api-references/events/Segmentation/api-operation.md
@@ -0,0 +1,33 @@
+---
+title: api_operation
+author: joelku
+description: api_operation event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# api_operation
+
+This event is triggered to summarize the actions taken during an invocation of the segmentation CRUD API.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Created|DateTime|The date and time when the operation was submitted.|
+|Completed|DateTime|The date and time when the operation was completed.|
+|Operation|[SegmentOperation](../data-types/segmentoperation.md)|The segment operation that was performed.|
+|OperationStatus|[SegmentOperationStatus](../data-types/segmentoperationstatus.md)|The status of the operation.|
+|SegmentId|String|The ID of the segment.|
+|SegmentName|String|The name of the segment.|
+|SegmentDefinition|String|The segment definition.|
+|EnteredSegmentActions|String|The actions triggered when a profile enters the segment.|
+|LeftSegmentActions|String|The actions triggered when a profile exits the segment.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Segmentation/segment-entered.md b/playfab-docs/api-references/events/Segmentation/segment-entered.md
new file mode 100644
index 000000000..c06460d3e
--- /dev/null
+++ b/playfab-docs/api-references/events/Segmentation/segment-entered.md
@@ -0,0 +1,26 @@
+---
+title: segment_entered
+author: joelku
+description: segment_entered event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# segment_entered
+
+This event is triggered when a profile enters a segment.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|SegmentId|String|The ID of the segment that had a status change.|
+|SegmentName|String|The friendly name of the segment.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Segmentation/segment-exited.md b/playfab-docs/api-references/events/Segmentation/segment-exited.md
new file mode 100644
index 000000000..5e9eb3e0d
--- /dev/null
+++ b/playfab-docs/api-references/events/Segmentation/segment-exited.md
@@ -0,0 +1,26 @@
+---
+title: segment_exited
+author: joelku
+description: segment_exited event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# segment_exited
+
+This event is triggered when a profile exits a segment.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|SegmentId|String|The ID of the segment that had a status change.|
+|SegmentName|String|The friendly name of the segment.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Session/client-focus-change.md b/playfab-docs/api-references/events/Session/client-focus-change.md
new file mode 100644
index 000000000..a237869b7
--- /dev/null
+++ b/playfab-docs/api-references/events/Session/client-focus-change.md
@@ -0,0 +1,29 @@
+---
+title: client_focus_change
+author: joannaleecy
+description: client_focus_change event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# client_focus_change
+
+This event is triggered every time the application enters or exits focus on the player's device.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
+|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
+|Payload|[ClientFocusChangePayload](../data-types/clientfocuschangepayload.md)|Payload that this entity is a child of.|
+|WriterEntity|[EntityKey](../data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Session/client-session-start.md b/playfab-docs/api-references/events/Session/client-session-start.md
new file mode 100644
index 000000000..99048619c
--- /dev/null
+++ b/playfab-docs/api-references/events/Session/client-session-start.md
@@ -0,0 +1,29 @@
+---
+title: client_session_start
+author: joannaleecy
+description: client_session_start event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# client_session_start
+
+This event is triggered when a new client session starts.
+
+Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
+|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
+|Payload|[ClientSessionStartPayload](../data-types/clientsessionstartpayload.md)|Payload that this entity is a child of.|
+|WriterEntity|[EntityKey](../data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Statistics/statistic-updated.md b/playfab-docs/api-references/events/Statistics/statistic-updated.md
new file mode 100644
index 000000000..b7122e375
--- /dev/null
+++ b/playfab-docs/api-references/events/Statistics/statistic-updated.md
@@ -0,0 +1,31 @@
+---
+title: statistic_updated
+author: t-sandersg-gith
+description: statistic_updated event
+ms.author: t-sandersg
+ms.date: 8/18/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# statistic_updated
+
+This event is triggered when a statistic is updated for a given entity.
+
+## Properties
+
+| Name | Type | Description |
+| --- | --- | --- |
+| Name | String | The name of the statistic |
+| Version | int32 | The version of the statistic |
+| Scores | int64[] | The current scores for the statistic, after the change |
+| PreviousScores | int64[] | The previous scores for the statistic, before the change |
+| Metadata | String | The metadata associated with the statistic, after the change |
+| PreviousMetadata | String | The metadata associated with the statistic, before the change |
+| Operation | String | The operation that was performed: `Created`, `Updated`, or `Deleted` |
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/TargetedConfiguration/player-churn-prediction-changed.md b/playfab-docs/api-references/events/TargetedConfiguration/player-churn-prediction-changed.md
new file mode 100644
index 000000000..110eda25a
--- /dev/null
+++ b/playfab-docs/api-references/events/TargetedConfiguration/player-churn-prediction-changed.md
@@ -0,0 +1,25 @@
+---
+title: player_churn_prediction_changed
+author: joelku
+description: player_churn_prediction_changed event.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_churn_prediction_changed
+
+This event is triggered when a player's churn prediction is changed.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ChurnPrediction|[ChurnRiskLevel](../data-types/churnrisklevel.md)|New churn prediction value.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Telemetry/apikey-activated.md b/playfab-docs/api-references/events/Telemetry/apikey-activated.md
new file mode 100644
index 000000000..4405bc510
--- /dev/null
+++ b/playfab-docs/api-references/events/Telemetry/apikey-activated.md
@@ -0,0 +1,29 @@
+---
+title: apikey_activated
+author: ronnyparedes
+description: apikey_activated event.
+ms.author: ronnyparedes
+ms.date: 02/09/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# apikey_activated
+
+This event is triggered when an API key is activated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
+|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
+|Payload|[APIKeyActivatedPayload](../data-types/apikeyactivatedpayload.md)|The payload of this event.|
+|WriterEntity|[EntityKey](../data-types/entitykey.md)|The entity that wrote this event, included only if different from the entity specified on the event.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Telemetry/apikey-created.md b/playfab-docs/api-references/events/Telemetry/apikey-created.md
new file mode 100644
index 000000000..e247557b4
--- /dev/null
+++ b/playfab-docs/api-references/events/Telemetry/apikey-created.md
@@ -0,0 +1,29 @@
+---
+title: apikey_created
+author: ronnyparedes
+description: apikey_created event.
+ms.author: ronnyparedes
+ms.date: 02/09/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# apikey_created
+
+This event is triggered when an API key is created.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
+|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
+|Payload|[APIKeyCreatedPayload](../data-types/apikeycreatedpayload.md)|The payload of this event.|
+|WriterEntity|[EntityKey](../data-types/entitykey.md)|The entity that wrote this event, included only if different from the entity specified on the event.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Telemetry/apikey-deactivated.md b/playfab-docs/api-references/events/Telemetry/apikey-deactivated.md
new file mode 100644
index 000000000..63ab66a8a
--- /dev/null
+++ b/playfab-docs/api-references/events/Telemetry/apikey-deactivated.md
@@ -0,0 +1,29 @@
+---
+title: apikey_deactivated
+author: ronnyparedes
+description: apikey_deactivated event.
+ms.author: ronnyparedes
+ms.date: 02/09/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# apikey_deactivated
+
+This event is triggered when an API key is deactivated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
+|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
+|Payload|[APIKeyDeactivatedPayload](../data-types/apikeydeactivatedpayload.md)|The payload of this event.|
+|WriterEntity|[EntityKey](../data-types/entitykey.md)|The entity that wrote this event, included only if different from the entity specified on the event.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Telemetry/apikey-deleted.md b/playfab-docs/api-references/events/Telemetry/apikey-deleted.md
new file mode 100644
index 000000000..1f110fd17
--- /dev/null
+++ b/playfab-docs/api-references/events/Telemetry/apikey-deleted.md
@@ -0,0 +1,29 @@
+---
+title: apikey_deleted
+author: ronnyparedes
+description: apikey_deleted event.
+ms.author: ronnyparedes
+ms.date: 02/09/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# apikey_deleted
+
+This event is triggered when an API key is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityLineage|[EntityLineage](../data-types/entitylineage.md)|Entities that this entity is a child of.|
+|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
+|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
+|Payload|[APIKeyDeletedPayload](../data-types/apikeydeletedpayload.md)|The payload of this event.|
+|WriterEntity|[EntityKey](../data-types/entitykey.md)|The entity that wrote this event, included only if different from the entity specified on the event.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/Title/title-client-rate-limited-alert.md b/playfab-docs/api-references/events/Title/title-client-rate-limited-alert.md
new file mode 100644
index 000000000..fc6af2867
--- /dev/null
+++ b/playfab-docs/api-references/events/Title/title-client-rate-limited-alert.md
@@ -0,0 +1,30 @@
+---
+title: title_client_rate_limited_alert
+author: joannaleecy
+description: title_client_rate_limited_alert event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_client_rate_limited_alert
+
+This event is triggered when a single IP address generates too many API calls to PlayFab and is throttled.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AlertEventId|String|Unique identifier of the alert that triggered this event.|
+|AlertState|[AlertStates](../data-types/alertstates.md)|State of the alert. Values include Triggered, Recovered, ReTriggered.|
+|API|String|The PlayFab API that was called too frequently.|
+|ErrorCode|String|Error message that was returned to the client.|
+|GraphUrl|String|URL of an image graph of the counter that triggered the alert.|
+|Level|[AlertLevel](../data-types/alertlevel.md)|Level of the alert. Values include Warn, Alert, Critical.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Title/title-high-error-rate-alert.md b/playfab-docs/api-references/events/Title/title-high-error-rate-alert.md
new file mode 100644
index 000000000..cb6bbf794
--- /dev/null
+++ b/playfab-docs/api-references/events/Title/title-high-error-rate-alert.md
@@ -0,0 +1,30 @@
+---
+title: title_high_error_rate_alert
+author: joannaleecy
+description: title_high_error_rate_alert event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_high_error_rate_alert
+
+This event is triggered when a game title experiences a high rate of errors.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AlertEventId|String|Unique identifier of the alert that triggered this event.|
+|AlertState|[AlertStates](../data-types/alertstates.md)|State of the alert. Values include Triggered, Recovered, ReTriggered.|
+|API|String|The PlayFab API that is generating the high rate of errors.|
+|ErrorCode|String|Error message that was returned to the client.|
+|GraphUrl|String|URL of an image graph of the counter that triggered the alert.|
+|Level|[AlertLevel](../data-types/alertlevel.md)|Level of the alert. Values include Warn, Alert, Critical.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Title/title-requested-limit-change.md b/playfab-docs/api-references/events/Title/title-requested-limit-change.md
new file mode 100644
index 000000000..a8b358f27
--- /dev/null
+++ b/playfab-docs/api-references/events/Title/title-requested-limit-change.md
@@ -0,0 +1,36 @@
+---
+title: title_requested_limit_change
+author: joannaleecy
+description: title_requested_limit_change event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_requested_limit_change
+
+This event is triggered when a title requests a service limit change.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeveloperId|String||
+|LevelName|String|The name of the requested limit level.|
+|LimitDisplayName|String|The display name of the limit requested to change.|
+|LimitId|String|The unique identifier of the limit requested to change.|
+|PreviousLevelName|String|The name of the limit level at the time of the requested change, if any.|
+|PreviousPriceUSD|double|The price of the limit level in US Dollars at the time of the requested change, if any.|
+|PreviousValue|double|The limit value at the time of the requested change, if any.|
+|PriceUSD|double|The price of the requested limit level in US Dollars, if any.|
+|TransactionId|String|The unique identifier of the requested limit change transaction.|
+|Unit|[MetricUnit](../data-types/metricunit.md)|The unit of the limit requested to change.|
+|UserId|String||
+|Value|double|The limit value of the requested change, if any.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/Title/title-saved-survey.md b/playfab-docs/api-references/events/Title/title-saved-survey.md
new file mode 100644
index 000000000..28834ba88
--- /dev/null
+++ b/playfab-docs/api-references/events/Title/title-saved-survey.md
@@ -0,0 +1,30 @@
+---
+title: title_saved_survey
+author: joannaleecy
+description: title_saved_survey event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_saved_survey
+
+This event is triggered when a game's survey is saved.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Genre|String|Title Genre|
+|Monetization|[]|Array of Monetization methods used by the Title|
+|Platforms|[]|Array of Platforms used by the Title|
+|PlayerModes|[]|Array of PlayerModes used by the Title|
+|TitleName|String|Name of the Title|
+|TitleWebsite|String|Website for the Title|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/TitleCommunications/email-sent.md b/playfab-docs/api-references/events/TitleCommunications/email-sent.md
new file mode 100644
index 000000000..a9765a98b
--- /dev/null
+++ b/playfab-docs/api-references/events/TitleCommunications/email-sent.md
@@ -0,0 +1,29 @@
+---
+title: email_sent
+author: ronnyparedes
+description: email_sent event.
+ms.author: ronnyparedes
+ms.date: 02/09/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# email_sent
+
+This event is triggered when an email is sent to a player.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EmailName|String|The name of the player's contact email.|
+|EmailTemplateId|String|The email template id.|
+|EmailTemplateName|String|The friendly name of the Template.|
+|ErrorMessage|String|The error that occurred if failed.|
+|Succeeded|Boolean|Whether the email was sent successfully.|
+
+## Common Properties
+
+[!INCLUDE [playstream-events-common-properties-v2](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/TitleCommunications/player-registered-push-notifications.md b/playfab-docs/api-references/events/TitleCommunications/player-registered-push-notifications.md
new file mode 100644
index 000000000..22c06d0fb
--- /dev/null
+++ b/playfab-docs/api-references/events/TitleCommunications/player-registered-push-notifications.md
@@ -0,0 +1,27 @@
+---
+title: player_registered_push_notifications
+author: joannaleecy
+description: player_registered_push_notifications event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# player_registered_push_notifications
+
+This event is triggered when a player registers for push notifications.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DeviceToken|String|Unique device token registered for push notifications.|
+|Platform|[PushNotificationPlatform](../data-types/pushnotificationplatform.md)|Platform on which the player is registering for push notifications.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/TitleCommunications/push-notification-sent.md b/playfab-docs/api-references/events/TitleCommunications/push-notification-sent.md
new file mode 100644
index 000000000..efd85760a
--- /dev/null
+++ b/playfab-docs/api-references/events/TitleCommunications/push-notification-sent.md
@@ -0,0 +1,28 @@
+---
+title: push_notification_sent
+author: joannaleecy
+description: push_notification_sent event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# push_notification_sent
+
+This event is triggered when a push notification is sent to a player.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ErrorMessage|String|The error that occurred if failed.|
+|PushNotificationTemplateId|String|The push notification template id.|
+|PushNotificationTemplateName|String|The friendly name of the push notification template.|
+|Success|Boolean|Whether the push notification was sent successfully.|
+
+## Common Properties
+
+[!INCLUDE [playstream-events-common-properties-v2](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/TitleCommunications/sent-email.md b/playfab-docs/api-references/events/TitleCommunications/sent-email.md
new file mode 100644
index 000000000..d870e93f2
--- /dev/null
+++ b/playfab-docs/api-references/events/TitleCommunications/sent-email.md
@@ -0,0 +1,36 @@
+---
+title: sent_email
+author: ronnyparedes
+description: sent_email event.
+ms.author: ronnyparedes
+ms.date: 02/09/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# sent_email
+
+This event is triggered when an email is sent or fails to send to a player.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Body|String|The content of the email body, truncated to 4096 characters.|
+|EmailName|String|The name of the player's contact email the email was sent to.|
+|EmailTemplateId|String|The email template id during a send email attempt.|
+|EmailTemplateName|String|The email template name during a send email attempt.|
+|EmailTemplateType|[EmailTemplateType](../data-types/emailtemplatetype.md)|The email template type during a send email attempt.|
+|ErrorMessage|String|The error that occurred if an email failed to send.|
+|ErrorName|String|The name of the error that occurred if an email failed to send.|
+|Language|String|The language the email was sent in|
+|Subject|String|The content of the email subject, truncated to 1024 characters.|
+|Success|Boolean|Indicates if the email was successfully sent.|
+|TitleId|String|The ID of the title to which this player event applies.|
+|Token|String|The auth token included in the sent email as part of a confirmation URL.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/TitleCommunications/sent-push-notification.md b/playfab-docs/api-references/events/TitleCommunications/sent-push-notification.md
new file mode 100644
index 000000000..6daa0839d
--- /dev/null
+++ b/playfab-docs/api-references/events/TitleCommunications/sent-push-notification.md
@@ -0,0 +1,33 @@
+---
+title: sent_push_notification
+author: joannaleecy
+description: sent_push_notification event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# sent_push_notification
+
+This event is triggered when a push notification is sent or fails to be sent to a player.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Body|String|The content of the push notification body, truncated to 4096 characters.|
+|ErrorMessage|String|The error that occurred if the push notification failed to be sent.|
+|ErrorName|String|The name of the error that occurred if the push notification failed to be sent.|
+|Language|String|The language the push notification was sent in if a matching localized template was used.|
+|PushNotificationTemplateId|String|The push notification template id during a send push notification attempt.|
+|PushNotificationTemplateName|String|The push notification template name during a send push notification attempt.|
+|Subject|String|The content of the push notification subject, truncated to 1024 characters.|
+|Success|Boolean|Indicates whether the push notification was successfully sent.|
+|TitleId|String|The ID of the title to which this player event applies.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/TitleData/title-activated.md b/playfab-docs/api-references/events/TitleData/title-activated.md
new file mode 100644
index 000000000..ba66b33ba
--- /dev/null
+++ b/playfab-docs/api-references/events/TitleData/title-activated.md
@@ -0,0 +1,19 @@
+---
+title: title_activated
+author: ronnyparedes
+description: title_activated event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_activated
+
+This event is triggered when a title is activated.
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/TitleData/title-data-override-deleted.md b/playfab-docs/api-references/events/TitleData/title-data-override-deleted.md
new file mode 100644
index 000000000..ffcb98d7b
--- /dev/null
+++ b/playfab-docs/api-references/events/TitleData/title-data-override-deleted.md
@@ -0,0 +1,26 @@
+---
+title: title_data_override_deleted
+author: ronnyparedes
+description: title_data_override_deleted event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_data_override_deleted
+
+This event is triggered when a title data override is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|OverrideLabel|String|The override label that was deleted.|
+|TitleDataType|[TitleDataType](../data-types/titledatatype.md)|The type of title data.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/TitleData/title-data-updated.md b/playfab-docs/api-references/events/TitleData/title-data-updated.md
new file mode 100644
index 000000000..2d212f190
--- /dev/null
+++ b/playfab-docs/api-references/events/TitleData/title-data-updated.md
@@ -0,0 +1,27 @@
+---
+title: title_data_updated
+author: ronnyparedes
+description: title_data_updated event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_data_updated
+
+This event is triggered when title data is updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Keys|String[]|The keys that were updated.|
+|OverrideLabel|String|The override label. Empty if primary title data.|
+|TitleDataType|[TitleDataType](../data-types/titledatatype.md)|The type of title data.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/TitleData/title-deactivated.md b/playfab-docs/api-references/events/TitleData/title-deactivated.md
new file mode 100644
index 000000000..2a76c8673
--- /dev/null
+++ b/playfab-docs/api-references/events/TitleData/title-deactivated.md
@@ -0,0 +1,19 @@
+---
+title: title_deactivated
+author: ronnyparedes
+description: title_deactivated event.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_deactivated
+
+This event is triggered when a title is deactivated.
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv2.md)]
diff --git a/playfab-docs/api-references/events/TitleData/title-news-updated.md b/playfab-docs/api-references/events/TitleData/title-news-updated.md
new file mode 100644
index 000000000..501eeec5d
--- /dev/null
+++ b/playfab-docs/api-references/events/TitleData/title-news-updated.md
@@ -0,0 +1,28 @@
+---
+title: title_news_updated
+author: joannaleecy
+description: title_news_updated event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_news_updated
+
+This event is triggered when a title news is created or updated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DateCreated|DateTime|When the title news was initially created.|
+|NewsId|String|Id of the news that is new or updated.|
+|NewsTitle|String|The current title of the news that is new or updated.|
+|Status|[NewsStatus](../data-types/newsstatus.md)|The current status of the news that is new or updated.|
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/TitleData/title-secret-key-changed.md b/playfab-docs/api-references/events/TitleData/title-secret-key-changed.md
new file mode 100644
index 000000000..61065b9df
--- /dev/null
+++ b/playfab-docs/api-references/events/TitleData/title-secret-key-changed.md
@@ -0,0 +1,31 @@
+---
+title: title_secret_key_changed
+author: joannaleecy
+description: title_secret_key_changed event.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# title_secret_key_changed
+
+This event is triggered when a title adds or updates a Secret Key
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Deleted|Boolean|Flag indicating if the key was deleted by this operation. Either true or null.|
+|DeveloperId|String||
+|Disabled|Boolean|Flag indicating if the key is disabled|
+|ExpiryDate|DateTime|Optional UTC date time that the secret key will expire at.|
+|SecretKeyId|String|Id of the secret key affected.|
+|SecretKeyName|String|Name of the secret key affected.|
+|UserId|String||
+
+## Common Properties
+
+[!INCLUDE [common-properties](../../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/character-consumed-item.md b/playfab-docs/api-references/events/character-consumed-item.md
deleted file mode 100644
index b2ad18335..000000000
--- a/playfab-docs/api-references/events/character-consumed-item.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: character_consumed_item
-author: joannaleecy
-description: character_consumed_item event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# character_consumed_item
-
-This event is triggered when a character consumes an item from their inventory.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CatalogVersion|String|Version of the catalog from which the consumed inventory item was created.|
-|ItemId|String|ID of the catalog item from which the consumed inventory item was created. This can be used to look up the item from the catalog.|
-|ItemInstanceId|String|The specific ID of the item that was consumed.|
-|PlayerId|String||
-|PreviousUsesRemaining|uint32|For multiple use items, the number of uses that remained before the item was consumed.|
-|TitleId|String||
-|UsesRemaining|uint32|For multiple use items, the number of uses remaining after the item was consumed.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/character-created.md b/playfab-docs/api-references/events/character-created.md
deleted file mode 100644
index f47f302a0..000000000
--- a/playfab-docs/api-references/events/character-created.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: character_created
-author: joannaleecy
-description: character_created event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# character_created
-
-## Properties
-
-This event is triggered when a character is created for the first time. 
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CharacterName|String|Name of the character.|
-|Created|DateTime|When the character was created.|
-|PlayerId|String||
-|TitleId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/character-inventory-item-added.md b/playfab-docs/api-references/events/character-inventory-item-added.md
deleted file mode 100644
index 87e2edbe4..000000000
--- a/playfab-docs/api-references/events/character-inventory-item-added.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: character_inventory_item_added
-author: joannaleecy
-description: character_inventory_item_added event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# character_inventory_item_added
-
-This event is triggered when an item is granted to a character.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Annotation|String|Optional details about the inventory item.|
-|BundleContents|[]|Catalog item IDs of any other items granted to the character along with this one as part of a bundle.|
-|CatalogVersion|String|Catalog version in which the item that was added is defined.|
-|Class|String|Class of the item that was added.|
-|CouponCode|String|Redeemed coupon (if any) that granted the item.|
-|DisplayName|String|Display name of the item that was added.|
-|Expiration|DateTime|When the item expires. The value is null if the item does not expire.|
-|InstanceId|String|Unique instance ID of the inventory item that was added.|
-|ItemId|String|Catalog item ID of the inventory item that was added.|
-|PlayerId|String||
-|RemainingUses|uint32|How many uses the item has, if it has a limited number of uses.|
-|TitleId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/character-statistic-changed.md b/playfab-docs/api-references/events/character-statistic-changed.md
deleted file mode 100644
index 6d36ea590..000000000
--- a/playfab-docs/api-references/events/character-statistic-changed.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: character_statistic_changed
-author: joannaleecy
-description: character_statistic_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# character_statistic_changed
-
-This event is triggered when a character statistic is changed.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|PlayerId|String||
-|StatisticName|String|Name of the statistic that changed.|
-|StatisticPreviousValue|int32|Old value of the statistic, before the change.|
-|StatisticValue|int32|New value of the statistic, after the change.|
-|TitleId|String||
-|Version|uint32|Version of the statistic that changed. This is relevant for statistics that reset, since each time the statistic resets the version increments.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/character-statistic-deleted.md b/playfab-docs/api-references/events/character-statistic-deleted.md
deleted file mode 100644
index a971bb771..000000000
--- a/playfab-docs/api-references/events/character-statistic-deleted.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: character_statistic_deleted
-author: joannaleecy
-description: character_statistic_deleted event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# character_statistic_deleted
-
-This event is triggered when a character statistic is deleted.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|PlayerId|String||
-|StatisticName|String|Name of the statistic that was deleted.|
-|TitleId|String||
-|Version|uint32|Version of the statistic that changed. This is relevant for statistics that reset, since each time the statistic resets the version increments.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/character-vc-item-purchased.md b/playfab-docs/api-references/events/character-vc-item-purchased.md
deleted file mode 100644
index f145fbbc0..000000000
--- a/playfab-docs/api-references/events/character-vc-item-purchased.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: character_vc_item_purchased
-author: joannaleecy
-description: character_vc_item_purchased event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# character_vc_item_purchased
-
-This event is triggered when the character makes a purchase using virtual currency.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CatalogVersion|String|Version of the catalog from which the item was purchased.|
-|CurrencyCode|String|Currency that was used to purchase the item.|
-|ItemId|String|Identifier of the catalog item that was purchased.|
-|PlayerId|String||
-|PurchaseId|String|Unique identifier of the purchase transaction.|
-|Quantity|int32|Quantity of items that were purchased.|
-|StoreId|String|The StoreId where the item was purchased.|
-|TitleId|String||
-|UnitPrice|uint32|Price paid per item, expressed in the virtual currency.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/character-virtual-currency-balance-changed.md b/playfab-docs/api-references/events/character-virtual-currency-balance-changed.md
deleted file mode 100644
index e94de6bc3..000000000
--- a/playfab-docs/api-references/events/character-virtual-currency-balance-changed.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: character_virtual_currency_balance_changed
-author: joannaleecy
-description: character_virtual_currency_balance_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# character_virtual_currency_balance_changed
-
-This event is triggered when a character's virtual currency balance changes.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|OrderId|String|ID of the order that triggered the balance changes.|
-|PlayerId|String||
-|TitleId|String||
-|VirtualCurrencyBalance|int32|New virtual currency balance after the change.|
-|VirtualCurrencyName|String|Virtual currency whose balance changed.|
-|VirtualCurrencyPreviousBalance|int32|Old virtual currency balance before the change.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/client-focus-change.md b/playfab-docs/api-references/events/client-focus-change.md
deleted file mode 100644
index 83f0f472f..000000000
--- a/playfab-docs/api-references/events/client-focus-change.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: client_focus_change
-author: joannaleecy
-description: client_focus_change event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# client_focus_change
-
-This event is triggered every time the application enters or exits focus on the player's device.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[ClientFocusChangePayload](data-types/clientfocuschangepayload.md)|Payload that this entity is a child of.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/client-session-start.md b/playfab-docs/api-references/events/client-session-start.md
deleted file mode 100644
index c459a1cb7..000000000
--- a/playfab-docs/api-references/events/client-session-start.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: client_session_start
-author: joannaleecy
-description: client_session_start event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# client_session_start
-
-This event is triggered when a new client session starts.
-
-Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[ClientSessionStartPayload](data-types/clientsessionstartpayload.md)|Payload that this entity is a child of.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/data-types/actioneventdetails.md b/playfab-docs/api-references/events/data-types/actioneventdetails.md
new file mode 100644
index 000000000..269f477ec
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/actioneventdetails.md
@@ -0,0 +1,23 @@
+---
+title: ActionEventDetails
+author: joelku
+description: ActionEventDetails data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ActionEventDetails
+
+Information about the event that triggered the action.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|The ID of the triggering event.|
+|FullName|[FullNameObject](fullnameobject.md)|The fully qualified name of the triggering event.|
+|Timestamp|DateTime|The server timestamp of the triggering event.|
diff --git a/playfab-docs/api-references/events/data-types/actionfailure.md b/playfab-docs/api-references/events/data-types/actionfailure.md
new file mode 100644
index 000000000..25948e36b
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/actionfailure.md
@@ -0,0 +1,22 @@
+---
+title: ActionFailure
+author: joelku
+description: ActionFailure data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ActionFailure
+
+Information about the error that occurred during action execution.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|FriendlyMessage|String|The friendly message of the action failure.|
+|ErrorCode|int32|The error code of the failure.|
diff --git a/playfab-docs/api-references/events/data-types/actionresultdetails.md b/playfab-docs/api-references/events/data-types/actionresultdetails.md
new file mode 100644
index 000000000..e3d3f051f
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/actionresultdetails.md
@@ -0,0 +1,22 @@
+---
+title: ActionResultDetails
+author: joelku
+description: ActionResultDetails data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ActionResultDetails
+
+The result of an action, if it succeeded.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ActionResult|object|The result of the action.|
+|FriendlyResult|String|The friendly message of the result.|
diff --git a/playfab-docs/api-references/events/data-types/actiontrigger.md b/playfab-docs/api-references/events/data-types/actiontrigger.md
new file mode 100644
index 000000000..d83f91a85
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/actiontrigger.md
@@ -0,0 +1,27 @@
+---
+title: ActionTrigger
+author: joelku
+description: ActionTrigger data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ActionTrigger
+
+Information about the trigger that initiated the action.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|RuleId|String|The ID of the rule that triggered the action.|
+|RuleName|String|The friendly name of the rule that triggered the action.|
+|Timestamp|DateTime|The server time when the rule was evaluated.|
+|ActionIndex|int32|The position of the action within the rule, starting from 0.|
+|ActionId|String|The ID of the action.|
+|ActionName|String|The friendly name of the action.|
+|ActionType|[ActionType](actiontype.md)|The type of the action.|
diff --git a/playfab-docs/api-references/events/data-types/actiontype.md b/playfab-docs/api-references/events/data-types/actiontype.md
new file mode 100644
index 000000000..6e5cdceaf
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/actiontype.md
@@ -0,0 +1,31 @@
+---
+title: ActionType
+author: joelku
+description: ActionType data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ActionType
+
+The possible types of actions.
+
+## Values
+
+|Value|Description|
+| :--------------------|:----------------------|
+|ExecuteFunction|Execute an Azure Function.|
+|AddVirtualCurrencies|Add virtual currencies.|
+|GrantInventoryItems|Grant inventory items.|
+|SendEntityPushNotification|Send an entity push notification.|
+|SendEntityEmail|Send an entity email.|
+|ExecuteEntityCloudScript|Execute entity CloudScript.|
+|UpdatePlayerCustomProperties|Update player custom properties.|
+|DeletePlayerCustomProperties|Delete player custom properties.|
+|AddInventoryItemsV2|Add inventory items (V2).|
+|SubtractInventoryItemsV2|Subtract inventory items (V2).|
+|DeleteInventoryItemsV2|Delete inventory items (V2).|
diff --git a/playfab-docs/api-references/events/data-types/addonprovisioningstate.md b/playfab-docs/api-references/events/data-types/addonprovisioningstate.md
new file mode 100644
index 000000000..7de52da43
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/addonprovisioningstate.md
@@ -0,0 +1,27 @@
+---
+title: AddOnProvisioningState
+author: playfab
+description: AddOnProvisioningState data type.
+ms.author: playfab
+ms.date: 01/27/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# AddOnProvisioningState
+
+Represents the provisioning state of an AddOn.
+
+## Values
+
+|Value|Description|
+| :--------------------|:----------------------|
+|Inactive|The AddOn is inactive.|
+|Active|The AddOn is active.|
+|Pending|The AddOn is pending provisioning.|
+|PendingWithError|The AddOn is pending with an error.|
+|Paused|The AddOn is paused.|
+|Waitlist|The AddOn is on a waitlist.|
+|Unknown|None of the above states.|
diff --git a/playfab-docs/api-references/events/data-types/apikeyactivatedpayload.md b/playfab-docs/api-references/events/data-types/apikeyactivatedpayload.md
new file mode 100644
index 000000000..6d224a0ea
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/apikeyactivatedpayload.md
@@ -0,0 +1,17 @@
+---
+author: WarrenAlpert
+title: APIKeyActivatedPayload
+description: Payload for when an entity API key is activated.
+ms.author: waralper
+ms.topic: reference
+---
+
+# APIKeyActivatedPayload
+
+Payload for when an entity API key is activated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|APIKeyId|String|Unique identifier for the entity API key.|
diff --git a/playfab-docs/api-references/events/data-types/apikeycreatedpayload.md b/playfab-docs/api-references/events/data-types/apikeycreatedpayload.md
new file mode 100644
index 000000000..35e670a2e
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/apikeycreatedpayload.md
@@ -0,0 +1,18 @@
+---
+author: WarrenAlpert
+title: APIKeyCreatedPayload
+description: Payload for when an entity API key is created.
+ms.author: waralper
+ms.topic: reference
+---
+
+# APIKeyCreatedPayload
+
+Payload for when an entity API key is created.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|APIKeyId|String|Unique identifier for the entity API key.|
+|Active|Boolean|Indicates whether the API key is active or not.|
diff --git a/playfab-docs/api-references/events/data-types/apikeydeactivatedpayload.md b/playfab-docs/api-references/events/data-types/apikeydeactivatedpayload.md
new file mode 100644
index 000000000..487df9ac9
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/apikeydeactivatedpayload.md
@@ -0,0 +1,17 @@
+---
+author: WarrenAlpert
+title: APIKeyDeactivatedPayload
+description: Payload for when an entity API key is deactivated.
+ms.author: waralper
+ms.topic: reference
+---
+
+# APIKeyDeactivatedPayload
+
+Payload for when an entity API key is deactivated.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|APIKeyId|String|Unique identifier for the entity API key.|
diff --git a/playfab-docs/api-references/events/data-types/apikeydeletedpayload.md b/playfab-docs/api-references/events/data-types/apikeydeletedpayload.md
new file mode 100644
index 000000000..5752b890c
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/apikeydeletedpayload.md
@@ -0,0 +1,17 @@
+---
+author: WarrenAlpert
+title: APIKeyDeletedPayload
+description: Payload for when an entity API key is deleted.
+ms.author: waralper
+ms.topic: reference
+---
+
+# APIKeyDeletedPayload
+
+Payload for when an entity API key is deleted.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|APIKeyId|String|Unique identifier for the entity API key.|
diff --git a/playfab-docs/api-references/events/data-types/artifact.md b/playfab-docs/api-references/events/data-types/artifact.md
new file mode 100644
index 000000000..b88edde1e
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/artifact.md
@@ -0,0 +1,23 @@
+---
+title: Artifact
+author: ronnyparedes
+description: Artifact data type.
+ms.author: ronnyparedes
+ms.date: 02/09/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# Artifact
+
+Provides details about an exported artifact (e.g Azure blob, Amazon S3 object, etc.)
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|NumberOfEvents|int64|The number of events in the artifact.|
+|Path|String|The location in storage where the artifact was written to.|
+|SizeInBytes|int64|The size of the artifact in bytes.|
diff --git a/playfab-docs/api-references/events/data-types/buildaliascreatedeventpayload.md b/playfab-docs/api-references/events/data-types/buildaliascreatedeventpayload.md
new file mode 100644
index 000000000..c6cb27d95
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/buildaliascreatedeventpayload.md
@@ -0,0 +1,20 @@
+---
+title: BuildAliasCreatedEventPayload
+author: valexao
+description: BuildAliasCreatedEventPayload data type.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# BuildAliasCreatedEventPayload
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AliasName|String|The name of the build alias that was created.|
+|AliasId|String|The Guid ID of the  build alias that was created.|
diff --git a/playfab-docs/api-references/events/data-types/buildaliasdeletedeventpayload.md b/playfab-docs/api-references/events/data-types/buildaliasdeletedeventpayload.md
new file mode 100644
index 000000000..a585f18ff
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/buildaliasdeletedeventpayload.md
@@ -0,0 +1,19 @@
+---
+title: BuildAliasDeletedEventPayload
+author: valexao
+description: BuildAliasDeletedEventPayload data type.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# BuildAliasDeletedEventPayload
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AliasId|String|The Guid ID of the  build alias that was deleted.|
diff --git a/playfab-docs/api-references/events/data-types/buildaliasupdatedeventpayload.md b/playfab-docs/api-references/events/data-types/buildaliasupdatedeventpayload.md
new file mode 100644
index 000000000..67c1eab2e
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/buildaliasupdatedeventpayload.md
@@ -0,0 +1,20 @@
+---
+title: BuildAliasUpdatedEventPayload
+author: valexao
+description: BuildAliasUpdatedEventPayload data type.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# BuildAliasUpdatedEventPayload
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|AliasName|String|The name of the build alias that was updated.|
+|AliasId|String|The Guid ID of the  build alias that was updated.|
diff --git a/playfab-docs/api-references/events/data-types/multiplayerserverbuilddeletedeventpayload.md b/playfab-docs/api-references/events/data-types/builddeletedeventpayload.md
similarity index 70%
rename from playfab-docs/api-references/events/data-types/multiplayerserverbuilddeletedeventpayload.md
rename to playfab-docs/api-references/events/data-types/builddeletedeventpayload.md
index 264ec7491..50343df28 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerserverbuilddeletedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/builddeletedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerBuildDeletedEventPayload
+title: BuildDeletedEventPayload
 author: joannaleecy
-description: MultiplayerServerBuildDeletedEventPayload data type.
+description: BuildDeletedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerBuildDeletedEventPayload
+# BuildDeletedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/multiplayerserverbuildregionstatuschangedeventpayload.md b/playfab-docs/api-references/events/data-types/buildregionstatuschangedeventpayload.md
similarity index 74%
rename from playfab-docs/api-references/events/data-types/multiplayerserverbuildregionstatuschangedeventpayload.md
rename to playfab-docs/api-references/events/data-types/buildregionstatuschangedeventpayload.md
index 58c5bf085..d55fae1eb 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerserverbuildregionstatuschangedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/buildregionstatuschangedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerBuildRegionStatusChangedEventPayload
+title: BuildRegionStatusChangedEventPayload
 author: joannaleecy
-description: MultiplayerServerBuildRegionStatusChangedEventPayload data type.
+description: BuildRegionStatusChangedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerBuildRegionStatusChangedEventPayload
+# BuildRegionStatusChangedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/multiplayerserverbuildregionupdatedeventpayload.md b/playfab-docs/api-references/events/data-types/buildregionupdatedeventpayload.md
similarity index 74%
rename from playfab-docs/api-references/events/data-types/multiplayerserverbuildregionupdatedeventpayload.md
rename to playfab-docs/api-references/events/data-types/buildregionupdatedeventpayload.md
index 46c25e274..49533b362 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerserverbuildregionupdatedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/buildregionupdatedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerBuildRegionUpdatedEventPayload
+title: BuildRegionUpdatedEventPayload
 author: joannaleecy
-description: MultiplayerServerBuildRegionUpdatedEventPayload data type.
+description: BuildRegionUpdatedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerBuildRegionUpdatedEventPayload
+# BuildRegionUpdatedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/buildregionutilizationeventpayload.md b/playfab-docs/api-references/events/data-types/buildregionutilizationeventpayload.md
new file mode 100644
index 000000000..f59a30494
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/buildregionutilizationeventpayload.md
@@ -0,0 +1,25 @@
+---
+title: BuildRegionUtilizationEventPayload
+author: valexao
+description: BuildRegionUtilizationEventPayload data type.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# BuildRegionUtilizationEventPayload
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|BuildId|String|The guid string ID of the multiplayer server build that regions were updated on.|
+|Region|[AzureRegion](azureregion.md)|The build region.|
+|Active|Int|The number of active servers.|
+|StandingBy|Int|The number of standingby servers.|
+|Propping|Int|The number of servers still downloading game resources.|
+|Total|Int|The total number of servers.|
+|VmCount|Int|The total number of running virtual machines.|
diff --git a/playfab-docs/api-references/events/data-types/multiplayerservercertificatedeletedeventpayload.md b/playfab-docs/api-references/events/data-types/certificatedeletedeventpayload.md
similarity index 67%
rename from playfab-docs/api-references/events/data-types/multiplayerservercertificatedeletedeventpayload.md
rename to playfab-docs/api-references/events/data-types/certificatedeletedeventpayload.md
index 0de591ca1..a6c2fd2db 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerservercertificatedeletedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/certificatedeletedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerCertificateDeletedEventPayload
+title: CertificateDeletedEventPayload
 author: joannaleecy
-description: MultiplayerServerCertificateDeletedEventPayload data type.
+description: CertificateDeletedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerCertificateDeletedEventPayload
+# CertificateDeletedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/multiplayerservercertificateuploadedeventpayload.md b/playfab-docs/api-references/events/data-types/certificateuploadedeventpayload.md
similarity index 66%
rename from playfab-docs/api-references/events/data-types/multiplayerservercertificateuploadedeventpayload.md
rename to playfab-docs/api-references/events/data-types/certificateuploadedeventpayload.md
index e85c07fac..cd663316e 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerservercertificateuploadedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/certificateuploadedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MMultiplayerServerCertificateUploadedEventPayload
+title: CertificateUploadedEventPayload
 author: joannaleecy
-description: MultiplayerServerCertificateUploadedEventPayload data type.
+description: CertificateUploadedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerCertificateUploadedEventPayload
+# CertificateUploadedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/churnrisklevel.md b/playfab-docs/api-references/events/data-types/churnrisklevel.md
new file mode 100644
index 000000000..8e00d2efa
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/churnrisklevel.md
@@ -0,0 +1,24 @@
+---
+title: ChurnRiskLevel
+author: joelku
+description: ChurnRiskLevel data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ChurnRiskLevel
+
+Defines values for the churn risk level of a player.
+
+## Values
+
+|Value|Description|
+| :--------------------|:----------------------|
+|NoData|Not enough data to make a prediction.|
+|LowRisk|The player has a low risk of churning.|
+|MediumRisk|The player has a medium risk of churning.|
+|HighRisk|The player has a high risk of churning.|
diff --git a/playfab-docs/api-references/events/data-types/contactemaildetails.md b/playfab-docs/api-references/events/data-types/contactemaildetails.md
new file mode 100644
index 000000000..a7411677b
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/contactemaildetails.md
@@ -0,0 +1,22 @@
+---
+title: ContactEmailDetails
+author: ronnyparedes
+description: ContactEmailDetails data type.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ContactEmailDetails
+
+Details about a contact email address associated with an entity profile.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EmailAddress|String|The email address.|
+|EmailType|String|The type of contact email (e.g., primary, backup).|
diff --git a/playfab-docs/api-references/events/data-types/crashdetectedeventpayload.md b/playfab-docs/api-references/events/data-types/crashdetectedeventpayload.md
new file mode 100644
index 000000000..38ce9d734
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/crashdetectedeventpayload.md
@@ -0,0 +1,24 @@
+---
+title: CrashDetectedEventPayload
+author: valexao
+description: CrashDetectedEventPayload data type.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# CrashDetectedEventPayload
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|BuildId|String|The guid string ID of the multiplayer server build that regions were updated on.|
+|Region|[AzureRegion](azureregion.md)|The build region.|
+|ServerId|String|The guid string ID of the session.|
+|VmId|String|The virtual machine ID the multiplayer server is located on.|
+|CrashDumpUploaded|bool|If true, the crash dump was uploaded with the server's logs.|
+|CrashDumpStatus|String|The reason a crash dump wasn't uploaded. If null, assume no crash dump was found.|
diff --git a/playfab-docs/api-references/events/data-types/multiplayerservercreatebuildinitiatedeventpayload.md b/playfab-docs/api-references/events/data-types/createbuildinitiatedeventpayload.md
similarity index 73%
rename from playfab-docs/api-references/events/data-types/multiplayerservercreatebuildinitiatedeventpayload.md
rename to playfab-docs/api-references/events/data-types/createbuildinitiatedeventpayload.md
index 0a3b999be..d4827582c 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerservercreatebuildinitiatedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/createbuildinitiatedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerCreateBuildInitiatedEventPayload
+title: CreateBuildInitiatedEventPayload
 author: joannaleecy
-description: MultiplayerServerCreateBuildInitiatedEventPayload data type.
+description: CreateBuildInitiatedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerCreateBuildInitiatedEventPayload
+# CreateBuildInitiatedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/entityobject.md b/playfab-docs/api-references/events/data-types/entityobject.md
new file mode 100644
index 000000000..3367f81c2
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/entityobject.md
@@ -0,0 +1,20 @@
+---
+title: EntityObject
+author: valexao
+description: EntityObject data type.
+ms.author: vorelien
+ms.date: 01/21/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# EntityObject
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|Unique ID of the entity.|
+|Type|String|One of the [available built-in entity types](../../../live-service-management/game-configuration/entities/available-built-in-entity-types.md).|
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/data-types/eventexportcompletionstatus.md b/playfab-docs/api-references/events/data-types/eventexportcompletionstatus.md
new file mode 100644
index 000000000..413ecfb9e
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/eventexportcompletionstatus.md
@@ -0,0 +1,22 @@
+---
+title: EventExportCompletionStatus
+author: joannaleecy
+description: EventExportCompletionStatus data type.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# EventExportCompletionStatus
+
+The possible status upon completion of an event export execution.
+
+## Values
+
+|Name|Description|
+| :--------------------|:----------------------|
+|Failed|The export execution failed.|
+|Succeeded|The export execution succeeded.|
diff --git a/playfab-docs/api-references/events/data-types/executefunctionresult.md b/playfab-docs/api-references/events/data-types/executefunctionresult.md
new file mode 100644
index 000000000..f095ec221
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/executefunctionresult.md
@@ -0,0 +1,26 @@
+---
+title: ExecuteFunctionResult
+author: joannaleecy
+description: ExecuteFunctionResult data type.
+ms.author: jenelleb
+ms.date: 02/19/2019
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ExecuteFunctionResult
+
+The result from executing a CloudScript Azure Function.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Error|[FunctionExecutionError](functionexecutionerror.md)|Error from the CloudScript Azure Function, if any.|
+|ExecutionTimeMilliseconds|int|The amount of time the function took to execute in milliseconds.|
+|FunctionName|String|The name of the function that executed.|
+|FunctionResult|Object|The object returned from the function, if any.|
+|FunctionResultSize|int|The size in bytes of the object returned from the function, if any.|
+|FunctionResultTooLarge|Boolean|Flag indicating if the FunctionResult was too large and was subsequently dropped from this event.|
diff --git a/playfab-docs/api-references/events/data-types/experiment.md b/playfab-docs/api-references/events/data-types/experiment.md
new file mode 100644
index 000000000..aa64d7bbe
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/experiment.md
@@ -0,0 +1,26 @@
+---
+title: Experiment
+author: joelku
+description: Experiment data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# Experiment
+
+Payload representing updates to experiment configuration.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|StartTime|DateTime|When the experiment should start or was started.|
+|DurationInDays|int32|The duration of the experiment in days.|
+|SegmentId|String|The ID of the segment to which this experiment applies.|
+|ExclusionGroupId|String|The ID of the exclusion group to which this experiment applies.|
+|ExclusionGroupTrafficAllocation|int32|Percentage of exclusion-group traffic seen by this experiment.|
+|Variants|[ExperimentVariant](experimentvariant.md)[]|List of variants for the experiment.|
diff --git a/playfab-docs/api-references/events/data-types/experimentrequestorigin.md b/playfab-docs/api-references/events/data-types/experimentrequestorigin.md
new file mode 100644
index 000000000..24ccb6223
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/experimentrequestorigin.md
@@ -0,0 +1,22 @@
+---
+title: ExperimentRequestOrigin
+author: joelku
+description: ExperimentRequestOrigin data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ExperimentRequestOrigin
+
+The set of origins from which experiment requests can be issued.
+
+## Values
+
+|Value|Description|
+| :--------------------|:----------------------|
+|Scheduled|The request was issued by a scheduled process.|
+|Manual|The request was issued manually.|
diff --git a/playfab-docs/api-references/events/data-types/experimentvariable.md b/playfab-docs/api-references/events/data-types/experimentvariable.md
new file mode 100644
index 000000000..5333cd74d
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/experimentvariable.md
@@ -0,0 +1,22 @@
+---
+title: ExperimentVariable
+author: joelku
+description: ExperimentVariable data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ExperimentVariable
+
+A variable (key-value pair) within an experiment variant.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Name|String|Name of the variable.|
+|Value|String|Value of the variable.|
diff --git a/playfab-docs/api-references/events/data-types/experimentvariant.md b/playfab-docs/api-references/events/data-types/experimentvariant.md
new file mode 100644
index 000000000..8e73dbd54
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/experimentvariant.md
@@ -0,0 +1,26 @@
+---
+title: ExperimentVariant
+author: joelku
+description: ExperimentVariant data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ExperimentVariant
+
+A variant within an experiment.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|The unique identifier of the variant.|
+|Name|String|The name of the variant.|
+|TrafficPercentage|int32|The percentage (0 to 100) of players in the experiment that will see this variant.|
+|IsControl|Boolean|Specifies if variant is the control for the experiment.|
+|TitleDataOverrideLabel|String|The title data override label.|
+|Variables|[ExperimentVariable](experimentvariable.md)[]|The variables returned by this variant.|
diff --git a/playfab-docs/api-references/events/data-types/filedetails.md b/playfab-docs/api-references/events/data-types/filedetails.md
new file mode 100644
index 000000000..4e8bce7ae
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/filedetails.md
@@ -0,0 +1,29 @@
+---
+title: FileDetails
+author: ronnyparedes
+description: FileDetails data type.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# FileDetails
+
+Details about a file attached to an entity.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ByteCount|int32|The current size of the file in bytes.|
+|Checksum|String|The current checksum of the file.|
+|FileName|String|The name of the file.|
+|Operation|[OperationTypes](operationtypes.md)|The type of operation that was performed on the file.|
+|PreviousByteCount|int32|The previous size of the file in bytes.|
+|PreviousChecksum|String|The previous checksum of the file.|
+|PreviousStoragePath|String|The previous storage path of the file.|
+|StoragePath|String|The current storage path of the file.|
+|StorageSystem|[ProfileFileStorage](profilefilestorage.md)|The storage system where the file is stored.|
diff --git a/playfab-docs/api-references/events/data-types/fullnameobject.md b/playfab-docs/api-references/events/data-types/fullnameobject.md
new file mode 100644
index 000000000..15824cd78
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/fullnameobject.md
@@ -0,0 +1,20 @@
+---
+title: FullNameObject
+author: valexao
+description: FullNameObject data type.
+ms.author: vorelien
+ms.date: 01/21/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# FullNameObject
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EventName|String|The name of this event.|
+|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/data-types/multiplayerservergameassetdeletedeventpayload.md b/playfab-docs/api-references/events/data-types/gameassetdeletedeventpayload.md
similarity index 67%
rename from playfab-docs/api-references/events/data-types/multiplayerservergameassetdeletedeventpayload.md
rename to playfab-docs/api-references/events/data-types/gameassetdeletedeventpayload.md
index 3c90072f2..12cdf018b 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerservergameassetdeletedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/gameassetdeletedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerGameAssetDeletedEventPayload
+title: GameAssetDeletedEventPayload
 author: joannaleecy
-description: MMultiplayerServerGameAssetDeletedEventPayload data type.
+description: GameAssetDeletedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerGameAssetDeletedEventPayload
+# GameAssetDeletedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/gamecertificatedeployed.md b/playfab-docs/api-references/events/data-types/gamecertificatedeployed.md
new file mode 100644
index 000000000..c5356515f
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/gamecertificatedeployed.md
@@ -0,0 +1,24 @@
+---
+title: GameCertificateDeployed
+author: valexao
+description: GameCertificateDeployed data type.
+ms.author: vorelien
+ms.date: 12/10/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# GameCertificateDeployed
+
+Information about the game certificate deployed in the VM.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Name|String|The certificate name.|
+|Thumbprint|String|The certificate thumbprint.|
+|Version|String|The certificate version.|
+|Expiration|String|The certificate expiration date.|
diff --git a/playfab-docs/api-references/events/data-types/gamesaveconflict.md b/playfab-docs/api-references/events/data-types/gamesaveconflict.md
new file mode 100644
index 000000000..3ad1941e1
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/gamesaveconflict.md
@@ -0,0 +1,20 @@
+---
+title: GameSaveConflict
+author: alzakrze
+description: GameSaveConflict data type.
+ms.author: alzakrze
+ms.date: 01/22/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events, gamesave
+ms.localizationpriority: medium
+---
+
+# GameSaveConflict
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|ConflictingVersion|Int64|The ID of the version that was in conflict with this version. That version should be assumed to have the opposite IsWinner value.|
+|IsWinner|Boolean|Whether this version is the winner of the conflict resolution process.|
diff --git a/playfab-docs/api-references/events/data-types/itempurchasedcurrency.md b/playfab-docs/api-references/events/data-types/itempurchasedcurrency.md
new file mode 100644
index 000000000..a68ad922c
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/itempurchasedcurrency.md
@@ -0,0 +1,22 @@
+---
+title: ItemPurchasedCurrency
+author: ernestoc
+description: ItemPurchasedCurrency data type.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ItemPurchasedCurrency
+
+Represents a currency used during a purchase event.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| CurrencyId | String | The id of the currency. |
+| Quantity | uint64 | The quantity of the currency. |
diff --git a/playfab-docs/api-references/events/data-types/itempurchasedoverride.md b/playfab-docs/api-references/events/data-types/itempurchasedoverride.md
new file mode 100644
index 000000000..a5ada8405
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/itempurchasedoverride.md
@@ -0,0 +1,23 @@
+---
+title: ItemPurchasedOverride
+author: ernestoc
+description: ItemPurchasedOverride data type.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ItemPurchasedOverride
+
+Represents an override used during a purchase event.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| FixedValue | double | The fixed value of the override. |
+| ItemId | String | The id of the item. |
+| Multiplier | double | The multiplier of the override. |
diff --git a/playfab-docs/api-references/events/data-types/itemsclawbackcompletedpayload.md b/playfab-docs/api-references/events/data-types/itemsclawbackcompletedpayload.md
new file mode 100644
index 000000000..211e379bf
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/itemsclawbackcompletedpayload.md
@@ -0,0 +1,32 @@
+---
+title: ItemsClawbackCompletedPayload
+author: ernestoc
+description: ItemsClawbackCompletedPayload data type.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ItemsClawbackCompletedPayload
+
+Items clawback completed event payload.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| Amount | int | The amount of items that were clawed back. |
+| Balance | int | The balance of the item after the transaction. |
+| CollectionId | String | The collection ID the item was clawed back from. |
+| ItemId | String | The ID of the item that was clawed back. |
+| ItemType | String | The type of the catalog item that was clawed back. |
+| Marketplace | String | The name of the marketplace the items were clawed back from. |
+| MarketplaceAlternateId | String | The alternate ID of the item for the marketplace. |
+| MarketplaceEventId | String | The event ID from the marketplace that triggered this clawback. |
+| MarketplaceTransactionId | String | The ID of the marketplace transaction. |
+| RedemptionDetails | RedemptionDetails | The details of the original redeem operation. |
+| StackId | String | The stack ID that the item was clawed back from. |
+| TransactionId | String | ID of the transaction which clawed back this item. |
diff --git a/playfab-docs/api-references/events/data-types/itemsclawbackreversalcompletedpayload.md b/playfab-docs/api-references/events/data-types/itemsclawbackreversalcompletedpayload.md
new file mode 100644
index 000000000..e1ad5c9ba
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/itemsclawbackreversalcompletedpayload.md
@@ -0,0 +1,32 @@
+---
+title: ItemsClawbackReversalCompletedPayload
+author: ernestoc
+description: ItemsClawbackReversalCompletedPayload data type.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ItemsClawbackReversalCompletedPayload
+
+Items clawback reversal completed event payload.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| Amount | int | The amount of items that were added. |
+| Balance | int | The balance of the item after the transaction. |
+| ClawbackDetails | ClawbackDetails | The details of the original clawback operation. |
+| CollectionId | String | The collection ID the item was added to. |
+| ItemId | String | The ID of the item that was added. |
+| ItemType | String | The type of the catalog item. |
+| Marketplace | String | The name of the marketplace that triggered this clawback reversal. |
+| MarketplaceAlternateId | String | The alternate ID of the item for the marketplace. |
+| MarketplaceEventId | String | The event ID from the marketplace that triggered this clawback reversal. |
+| MarketplaceTransactionId | String | The ID of the marketplace transaction. |
+| StackId | String | The stack ID that the item was added to. |
+| TransactionId | String | ID of the transaction which performed a clawback reversal on this item. |
diff --git a/playfab-docs/api-references/events/data-types/itemsexpiredpayload.md b/playfab-docs/api-references/events/data-types/itemsexpiredpayload.md
new file mode 100644
index 000000000..5d10f586d
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/itemsexpiredpayload.md
@@ -0,0 +1,27 @@
+---
+title: ItemsExpiredPayload
+author: ernestoc
+description: ItemsExpiredPayload data type.
+ms.author: ernestoc
+ms.date: 02/18/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ItemsExpiredPayload
+
+Items expired event payload.
+
+## Properties
+
+| Name | Type | Description |
+| :--- | :--- | :--- |
+| CollectionId | String | The collection ID. |
+| ExpirationDate | String | The expiration date in ISO-8601 format. |
+| ItemId | String | The item ID. |
+| ItemType | String | The type of the catalog item that was modified. |
+| StackId | String | The stack ID. |
+| StartDate | String | The start date in ISO-8601 format. |
+| TransactionId | String | The transaction ID. |
diff --git a/playfab-docs/api-references/events/data-types/loginidentityprovider.md b/playfab-docs/api-references/events/data-types/loginidentityprovider.md
index 13cad61f2..d4e6cc636 100644
--- a/playfab-docs/api-references/events/data-types/loginidentityprovider.md
+++ b/playfab-docs/api-references/events/data-types/loginidentityprovider.md
@@ -1,9 +1,9 @@
 ---
 title: LoginIdentityProvider
-author: joannaleecy
+author: yuto chikazawa
 description: LoginIdentityProvider data type.
-ms.author: jenelleb
-ms.date: 02/19/2019
+ms.author: ychikazawa
+ms.date: 08/19/2025
 ms.topic: article
 ms.service: azure-playfab
 keywords: playfab, playstream events
@@ -35,3 +35,9 @@ ms.localizationpriority: medium
 |NintendoSwitch|
 |FacebookInstantGames|
 |OpenIdConnect|
+|Apple|
+|NintendoSwitchAccount|
+|GooglePlayGames|
+|XboxMobileStore|
+|King|
+|BattleNet|
diff --git a/playfab-docs/api-references/events/data-types/monitoringoutputsavedeventpayload.md b/playfab-docs/api-references/events/data-types/monitoringoutputsavedeventpayload.md
new file mode 100644
index 000000000..08c74dc0c
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/monitoringoutputsavedeventpayload.md
@@ -0,0 +1,24 @@
+---
+title: MonitoringOutputSavedEventPayload
+author: valexao
+description: MonitoringOutputSavedEventPayload data type.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# MonitoringOutputSavedEventPayload
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|BuildId|String|The Guid string ID of the build.|
+|Region|[AzureRegion](azureregion.md)|The build region.|
+|ServerId|String|The multiplayer server ID.|
+|SessionId|String|The Guid string ID of the session.|
+|VmId|String|The virtual machine ID the multiplayer server is located on.|
+|IsVmLevel|bool|True if the monitoring output was not associated with a running server.|
diff --git a/playfab-docs/api-references/events/data-types/objectdetails.md b/playfab-docs/api-references/events/data-types/objectdetails.md
new file mode 100644
index 000000000..776abb60e
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/objectdetails.md
@@ -0,0 +1,23 @@
+---
+title: ObjectDetails
+author: ronnyparedes
+description: ObjectDetails data type.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# ObjectDetails
+
+Details about an object attached to an entity.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|DataObject|object|The data object content.|
+|Name|String|The name of the object.|
+|Operation|[OperationTypes](operationtypes.md)|The type of operation that was performed on the object.|
diff --git a/playfab-docs/api-references/events/data-types/originatorobject.md b/playfab-docs/api-references/events/data-types/originatorobject.md
new file mode 100644
index 000000000..40a3560c7
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/originatorobject.md
@@ -0,0 +1,20 @@
+---
+title: OriginatorObject
+author: valexao
+description: OriginatorObject data type.
+ms.author: vorelien
+ms.date: 01/21/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# OriginatorObject
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Id|String|Source of the Playstream event - will be PlayFab if the event originated from us.|
+|Type|String|The type of the source of this event. List of possible values found here: [SourceType](../data-types/sourcetype.md)|
\ No newline at end of file
diff --git a/playfab-docs/api-references/events/data-types/playercustompropertieschangeddetails.md b/playfab-docs/api-references/events/data-types/playercustompropertieschangeddetails.md
new file mode 100644
index 000000000..a5f08c22a
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/playercustompropertieschangeddetails.md
@@ -0,0 +1,23 @@
+---
+title: PlayerCustomPropertiesChangedDetails
+author: ronnyparedes
+description: PlayerCustomPropertiesChangedDetails data type.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# PlayerCustomPropertiesChangedDetails
+
+Details about a custom property change.
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|Name|String|The name of the custom property that was changed.|
+|OperationType|[PlayerCustomPropertiesChangedOperationTypes](playercustompropertieschangedoperationtypes.md)|The operation that was performed.|
+|Value|object|The last set value of the custom property.|
diff --git a/playfab-docs/api-references/events/data-types/secretaddedeventpayload.md b/playfab-docs/api-references/events/data-types/secretaddedeventpayload.md
new file mode 100644
index 000000000..07c3fa7c3
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/secretaddedeventpayload.md
@@ -0,0 +1,19 @@
+---
+title: SecretAddedEventPayload
+author: valexao
+description: SecretAddedEventPayload data type.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# SecretAddedEventPayload
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|SecretName|String|The name of the secret that was added.|
diff --git a/playfab-docs/api-references/events/data-types/secretdeletedeventpayload.md b/playfab-docs/api-references/events/data-types/secretdeletedeventpayload.md
new file mode 100644
index 000000000..83aa53d1a
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/secretdeletedeventpayload.md
@@ -0,0 +1,19 @@
+---
+title: SecretDeletedEventPayload
+author: valexao
+description: SecretDeletedEventPayload data type.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# SecretDeletedEventPayload
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|SecretName|String|The name of the secret that was deleted.|
diff --git a/playfab-docs/api-references/events/data-types/segmentoperation.md b/playfab-docs/api-references/events/data-types/segmentoperation.md
new file mode 100644
index 000000000..61cb82436
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/segmentoperation.md
@@ -0,0 +1,24 @@
+---
+title: SegmentOperation
+author: joelku
+description: SegmentOperation data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# SegmentOperation
+
+The type of segment operation that was performed.
+
+## Values
+
+|Value|Description|
+| :--------------------|:----------------------|
+|LookUp|A segment lookup operation.|
+|Create|A segment creation operation.|
+|Delete|A segment deletion operation.|
+|Update|A segment update operation.|
diff --git a/playfab-docs/api-references/events/data-types/segmentoperationstatus.md b/playfab-docs/api-references/events/data-types/segmentoperationstatus.md
new file mode 100644
index 000000000..ce31ab831
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/segmentoperationstatus.md
@@ -0,0 +1,24 @@
+---
+title: SegmentOperationStatus
+author: joelku
+description: SegmentOperationStatus data type.
+ms.author: joelku
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# SegmentOperationStatus
+
+The status of a segment operation.
+
+## Values
+
+|Value|Description|
+| :--------------------|:----------------------|
+|Start|The operation has started.|
+|Success|The operation completed successfully.|
+|Failed|The operation failed.|
+|ValidationError|The operation failed due to a validation error.|
diff --git a/playfab-docs/api-references/events/data-types/multiplayerserverrequestedeventpayload.md b/playfab-docs/api-references/events/data-types/serverrequestedeventpayload.md
similarity index 86%
rename from playfab-docs/api-references/events/data-types/multiplayerserverrequestedeventpayload.md
rename to playfab-docs/api-references/events/data-types/serverrequestedeventpayload.md
index d0fbbf6d0..d710af185 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerserverrequestedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/serverrequestedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerRequestedEventPayload
+title: ServerRequestedEventPayload
 author: joannaleecy
-description: MultiplayerServerRequestedEventPayload data type.
+description: ServerRequestedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerRequestedEventPayload
+# ServerRequestedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/multiplayerserverstatechangedeventpayload.md b/playfab-docs/api-references/events/data-types/serverstatechangedeventpayload.md
similarity index 80%
rename from playfab-docs/api-references/events/data-types/multiplayerserverstatechangedeventpayload.md
rename to playfab-docs/api-references/events/data-types/serverstatechangedeventpayload.md
index ff1961a84..82840961c 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerserverstatechangedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/serverstatechangedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerStateChangedEventPayload
+title: ServerStateChangedEventPayload
 author: joannaleecy
-description: MultiplayerServerStateChangedEventPayload data type.
+description: ServerStateChangedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerStateChangedEventPayload
+# ServerStateChangedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/titledatatype.md b/playfab-docs/api-references/events/data-types/titledatatype.md
new file mode 100644
index 000000000..c364a92e3
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/titledatatype.md
@@ -0,0 +1,22 @@
+---
+title: TitleDataType
+author: ronnyparedes
+description: TitleDataType data type.
+ms.author: ronnyparedes
+ms.date: 02/12/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# TitleDataType
+
+Specifies the type of title data.
+
+## Values
+
+|Name|Value|Description|
+| :--------------------|:-------------------|:----------------------|
+|TitleData|0|Public title data accessible to all clients.|
+|TitleInternalData|1|Internal title data only accessible server-side.|
diff --git a/playfab-docs/api-references/events/data-types/multiplayerservervmassignedeventpayload.md b/playfab-docs/api-references/events/data-types/vmassignedeventpayload.md
similarity index 81%
rename from playfab-docs/api-references/events/data-types/multiplayerservervmassignedeventpayload.md
rename to playfab-docs/api-references/events/data-types/vmassignedeventpayload.md
index 051ec25a4..71ed8541c 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerservervmassignedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/vmassignedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerVmAssignedEventPayload
+title: VmAssignedEventPayload
 author: joannaleecy
-description: MultiplayerServerVmAssignedEventPayload data type.
+description: VmAssignedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerVmAssignedEventPayload
+# VmAssignedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/vmgamecertificatesdeployedeventpayload.md b/playfab-docs/api-references/events/data-types/vmgamecertificatesdeployedeventpayload.md
new file mode 100644
index 000000000..bf2559090
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/vmgamecertificatesdeployedeventpayload.md
@@ -0,0 +1,22 @@
+---
+title: VmGameCertificatesDeployedEventPayload
+author: valexao
+description: VmGameCertificatesDeployedEventPayload data type.
+ms.author: vorelien
+ms.date: 12/30/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# VmGameCertificatesDeployedEventPayload
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|BuildId|String|The GUID string ID of the build.|
+|Region|[AzureRegion](azureregion.md)|The build region.|
+|VmId|String|The ID of the virtual machine that was assigned.|
+|GameCertificates|[List\<GameCertificateDeployed>](gamecertificatedeployed.md)|The list of game certificates deployed.|
diff --git a/playfab-docs/api-references/events/data-types/multiplayerservervmremoteusercreatedeventpayload.md b/playfab-docs/api-references/events/data-types/vmremoteusercreatedeventpayload.md
similarity index 74%
rename from playfab-docs/api-references/events/data-types/multiplayerservervmremoteusercreatedeventpayload.md
rename to playfab-docs/api-references/events/data-types/vmremoteusercreatedeventpayload.md
index 1b8cfcaad..e8b5f7a32 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerservervmremoteusercreatedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/vmremoteusercreatedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerVmRemoteUserCreatedEventPayload
+title: VmRemoteUserCreatedEventPayload
 author: joannaleecy
-description: MultiplayerServerVmRemoteUserCreatedEventPayload data type.
+description: VmRemoteUserCreatedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerVmRemoteUserCreatedEventPayload
+# VmRemoteUserCreatedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/multiplayerservervmremoteuserdeletedeventpayload.md b/playfab-docs/api-references/events/data-types/vmremoteuserdeletedeventpayload.md
similarity index 76%
rename from playfab-docs/api-references/events/data-types/multiplayerservervmremoteuserdeletedeventpayload.md
rename to playfab-docs/api-references/events/data-types/vmremoteuserdeletedeventpayload.md
index 23f32a80a..8f32e251a 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerservervmremoteuserdeletedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/vmremoteuserdeletedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerVmRemoteUserDeletedEventPayload
+title: VmRemoteUserDeletedEventPayload
 author: joannaleecy
-description: MultiplayerServerVmRemoteUserDeletedEventPayload data type.
+description: VmRemoteUserDeletedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerVmRemoteUserDeletedEventPayload
+# VmRemoteUserDeletedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/vmstatechangeeventpayload.md b/playfab-docs/api-references/events/data-types/vmstatechangeeventpayload.md
new file mode 100644
index 000000000..76a303e7a
--- /dev/null
+++ b/playfab-docs/api-references/events/data-types/vmstatechangeeventpayload.md
@@ -0,0 +1,23 @@
+---
+title: VmStateChangeEventPayload
+author: valexao
+description: VmStateChangeEventPayload data type.
+ms.author: vorelien
+ms.date: 12/10/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playstream events
+ms.localizationpriority: medium
+---
+
+# VmStateChangeEventPayload
+
+## Properties
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|BuildId|String|The guid string ID of the multiplayer server build that regions were updated on.|
+|Region|[AzureRegion](azureregion.md)|The build region.|
+|VmId|String|The virtual machine ID of the multiplayer vm.|
+|State|String|The multiplayer virtual machine's state to report on.|
+|DurationSeconds|ulong|The amount of time spent getting to this state.|
diff --git a/playfab-docs/api-references/events/data-types/multiplayerservervmunassignmentstartedeventpayload.md b/playfab-docs/api-references/events/data-types/vmunassignmentstartedeventpayload.md
similarity index 81%
rename from playfab-docs/api-references/events/data-types/multiplayerservervmunassignmentstartedeventpayload.md
rename to playfab-docs/api-references/events/data-types/vmunassignmentstartedeventpayload.md
index bc7181532..4c6ebc46e 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerservervmunassignmentstartedeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/vmunassignmentstartedeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerVmUnassignmentStartedEventPayload
+title: VmUnassignmentStartedEventPayload
 author: joannaleecy
-description: MultiplayerServerVmUnassignmentStartedEventPayload data type.
+description: VmUnassignmentStartedEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerVmUnassignmentStartedEventPayload
+# VmUnassignmentStartedEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/data-types/multiplayerservervmunhealthyeventpayload.md b/playfab-docs/api-references/events/data-types/vmunhealthyeventpayload.md
similarity index 76%
rename from playfab-docs/api-references/events/data-types/multiplayerservervmunhealthyeventpayload.md
rename to playfab-docs/api-references/events/data-types/vmunhealthyeventpayload.md
index a02a85421..c0c3f5898 100644
--- a/playfab-docs/api-references/events/data-types/multiplayerservervmunhealthyeventpayload.md
+++ b/playfab-docs/api-references/events/data-types/vmunhealthyeventpayload.md
@@ -1,7 +1,7 @@
 ---
-title: MultiplayerServerVmUnhealthyEventPayload
+title: VmUnhealthyEventPayload
 author: joannaleecy
-description: MultiplayerServerVmUnhealthyEventPayload data type.
+description: VmUnhealthyEventPayload data type.
 ms.author: jenelleb
 ms.date: 02/19/2019
 ms.topic: article
@@ -10,7 +10,7 @@ keywords: playfab, playstream events
 ms.localizationpriority: medium
 ---
 
-# MultiplayerServerVmUnhealthyEventPayload
+# VmUnhealthyEventPayload
 
 ## Properties
 
diff --git a/playfab-docs/api-references/events/display-name-filtered.md b/playfab-docs/api-references/events/display-name-filtered.md
deleted file mode 100644
index 598a70cad..000000000
--- a/playfab-docs/api-references/events/display-name-filtered.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: display_name_filtered
-author: joannaleecy
-description: display_name_filtered event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# display_name_filtered
-
-This event is triggered when a display name is filtered by community sift.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DisplayName|String|Value of the display name that was filtered|
-|PlayerId|String|If event occurs at account creation, then no player exists yet. Otherwise, the player whose displayname update was filtered|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/entity-created.md b/playfab-docs/api-references/events/entity-created.md
deleted file mode 100644
index e31748aeb..000000000
--- a/playfab-docs/api-references/events/entity-created.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: entity_created
-author: joannaleecy
-description: entity_created event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# entity_created
-
-This event is triggered when an entity is created.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/entity-executed-cloud-script.md b/playfab-docs/api-references/events/entity-executed-cloud-script.md
deleted file mode 100644
index 7af06cdc4..000000000
--- a/playfab-docs/api-references/events/entity-executed-cloud-script.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: entity_executed_cloud_script
-author: joannaleecy
-description: entity_executed_cloud_script event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# entity_executed_cloud_script
-
-This event is optionally triggered when a CloudScript function is executed by calling the ExecuteEntityCloudScript API. If you want the Event logged, you can pass in GeneratePlayStreamEvent.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CloudScriptExecutionResult|[ExecuteCloudScriptResult](data-types/executecloudscriptresult.md)|Result of the CloudScript function, including diagnostic information that is useful for debugging.|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|FunctionName|String|Name of the CloudScript function that was called.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/entity-files-set.md b/playfab-docs/api-references/events/entity-files-set.md
deleted file mode 100644
index 19fe45733..000000000
--- a/playfab-docs/api-references/events/entity-files-set.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: entity_files_set
-author: joannaleecy
-description: entity_files_set event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# entity_files_set
-
-This event is triggered when files are attached to an entity.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|Files|[FileSet](data-types/fileset.md)|The files that were updated.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/entity-language-updated.md b/playfab-docs/api-references/events/entity-language-updated.md
deleted file mode 100644
index 0cc84461b..000000000
--- a/playfab-docs/api-references/events/entity-language-updated.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: entity_language_updated
-author: joannaleecy
-description: entity_language_updated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# entity_language_updated
-
-This event is triggered when the language associated with an entity is changed.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|Language|String|Language that was updated|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
diff --git a/playfab-docs/api-references/events/entity-logged-in.md b/playfab-docs/api-references/events/entity-logged-in.md
deleted file mode 100644
index 3c702c600..000000000
--- a/playfab-docs/api-references/events/entity-logged-in.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: entity_logged_in
-author: joannaleecy
-description: entity_logged_in event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# entity_logged_in
-
-This event is triggered when an entity has logged in.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
diff --git a/playfab-docs/api-references/events/entity-objects-set.md b/playfab-docs/api-references/events/entity-objects-set.md
deleted file mode 100644
index a72ef17b4..000000000
--- a/playfab-docs/api-references/events/entity-objects-set.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: entity_objects_set
-author: joannaleecy
-description: entity_objects_set event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# entity_objects_set
-
-This event is triggered when objects are attached to an entity.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md|Entities that this entity is a child of.|
-|Objects|[ObjectSet](data-types/objectset.md)|Objects that were updated|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
diff --git a/playfab-docs/api-references/events/entity-rank-on-leaderboard-version-ended.md b/playfab-docs/api-references/events/entity-rank-on-leaderboard-version-ended.md
deleted file mode 100644
index c6f922269..000000000
--- a/playfab-docs/api-references/events/entity-rank-on-leaderboard-version-ended.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: entity_rank_on_leaderboard_version_ended
-author: t-sandersg-gith
-description: entity_rank_on_leaderboard_version_ended event.
-ms.author: t-sandersg
-ms.date: 8/14/2025
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# entity_rank_on_leaderboard_version_ended
-
-This event is triggered when a leaderboard version is reset to a new version for a game title, containing the entity's rank and score data from the ended version.
-
-## Properties
-
-| Name | Type | Description |
-| --- | --- | --- |
-| Name | String | The name of the leaderboard |
-| Version | int32 | The version of the leaderboard |
-| Metadata | String | Custom metadata associated with the entity |
-| Rank | int32 | The rank of the entity in the leaderboard |
-| Scores | int32[] | The scores of the entity in the leaderboard |
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"items_purchased"|
-|EventNamespace|String|"playfab.inventory"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/entity-virtual-currency-balances-changed.md b/playfab-docs/api-references/events/entity-virtual-currency-balances-changed.md
deleted file mode 100644
index d4260dfe8..000000000
--- a/playfab-docs/api-references/events/entity-virtual-currency-balances-changed.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: entity_virtual_currency_balances_changed
-author: joannaleecy
-description: entity_virtual_currency_balances_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# entity_virtual_currency_balances_changed
-
-This event is triggered when an entity's virtual currency balance changes.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|SequenceId|String|Sequence id of the balance change to ensure updates are processed in order.|
-|VirtualCurrencyBalances|Object|New virtual currency balances after the change. Only shows currencies that were updated.|
-|VirtualCurrencyContainerId|String|Container whose balances changed.|
-|VirtualCurrencyPreviousBalances|Object|Old virtual currency balances before the change. Only shows currencies that were updated.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-
diff --git a/playfab-docs/api-references/events/group-created.md b/playfab-docs/api-references/events/group-created.md
deleted file mode 100644
index 96ee40393..000000000
--- a/playfab-docs/api-references/events/group-created.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: group_created
-author: joannaleecy
-description: group_created event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# group_created
-
-This event is triggered when an entity group is created.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CreatorEntityId|String|The identifier for the entity that created the group to which this event applies.|
-|CreatorEntityType|String|The type of entity that created the group to which this event applies.|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|GroupName|String|The name of the group to which this event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
diff --git a/playfab-docs/api-references/events/group-deleted.md b/playfab-docs/api-references/events/group-deleted.md
deleted file mode 100644
index 1cace51e0..000000000
--- a/playfab-docs/api-references/events/group-deleted.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: group_deleted
-author: joannaleecy
-description: group_deleted event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# group_deleted
-
-This event is triggered when an entity group is deleted. 
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeleterEntityId|String|The identifier for the entity that deleted the group to which this event applies.|
-|DeleterEntityType|String|The type of entity that deleted the group to which this event applies.|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|GroupName|String|The name of the group to which this event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
diff --git a/playfab-docs/api-references/events/group-members-added.md b/playfab-docs/api-references/events/group-members-added.md
deleted file mode 100644
index 294ea9c04..000000000
--- a/playfab-docs/api-references/events/group-members-added.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: group_members_added
-author: joannaleecy
-description: group_members_added event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# group_members_added
-
-This event is triggered when a member is added to an entity group. 
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|GroupName|String|The name of the group to which this event applies.|
-|Members|[Member](data-types/member.md)|The list of entities that were added to the group and role to which this event applies.|
-|RoleId|String|The role ID of the role to which this event applies.|
-|RoleName|String|The display name of the role to which this event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
diff --git a/playfab-docs/api-references/events/group-members-removed.md b/playfab-docs/api-references/events/group-members-removed.md
deleted file mode 100644
index 8d1d8f6d9..000000000
--- a/playfab-docs/api-references/events/group-members-removed.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: group_members_removed
-author: joannaleecy
-description: group_members_removed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# group_members_removed
-
-This event is triggered when a member is removed from an entity group
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|GroupName|String|The name of the group to which this event applies.|
-|Members|[Member](data-types/member.md)|The list of entities that were removed from the group to which this event applies|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/group-role-created.md b/playfab-docs/api-references/events/group-role-created.md
deleted file mode 100644
index b6f1ebf65..000000000
--- a/playfab-docs/api-references/events/group-role-created.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: group_role_created
-author: joannaleecy
-description: group_role_created event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# group_role_created
-
-This event is triggered when a role is created for a group.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CreatorEntityId|String|The identifier for that the entity that created the role to which this event applies.|
-|CreatorEntityType|String|The type of entity that created the role to which this event applies.|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|GroupName|String|The name of the group to which this event applies.|
-|RoleId|String|The role ID of the role to which this event applies.|
-|RoleName|String|The display name of the role to which this event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
-
-
diff --git a/playfab-docs/api-references/events/group-role-deleted.md b/playfab-docs/api-references/events/group-role-deleted.md
deleted file mode 100644
index 4c3791c30..000000000
--- a/playfab-docs/api-references/events/group-role-deleted.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: group_role_deleted
-author: joannaleecy
-description: group_role_deleted event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# group_role_deleted
-
-This event is triggered when a role is deleted from a group.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeleterEntityId|String|The identifier for the entity that deleted the role to which this event applies.|
-|DeleterEntityType|String|The type of entity that deleted the role to which this event applies.|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|GroupName|String|The name of the group to which this event applies.|
-|RoleId|String|The role ID of the role to which this event applies.|
-|RoleName|String|The display name of the role to which this event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
-
diff --git a/playfab-docs/api-references/events/group-role-members-added.md b/playfab-docs/api-references/events/group-role-members-added.md
deleted file mode 100644
index 4b8347620..000000000
--- a/playfab-docs/api-references/events/group-role-members-added.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: group_role_members_added
-author: joannaleecy
-description: group_role_members_added event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# group_role_members_added
-
-This event is triggered when a list of entities are added to a role within a group.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|GroupName|String|The name of the group to which this event applies.|
-|Members|[Member](data-types/member.md)|The list of entities that were added to the group and role to which this event applies|
-|RoleId|String|The role ID of the role to which this event applies.|
-|RoleName|String|The display name of the role to which this event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
-
diff --git a/playfab-docs/api-references/events/group-role-members-removed.md b/playfab-docs/api-references/events/group-role-members-removed.md
deleted file mode 100644
index 6207f4561..000000000
--- a/playfab-docs/api-references/events/group-role-members-removed.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: group_role_members_removed
-author: joannaleecy
-description: group_role_members_removed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# group_role_members_removed
-
-This event is triggered when a list of entities are removed from a role within a group.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|GroupName|String|The name of the group to which this event applies.|
-|Members|[Member](data-types/member.md)|The list of entities that were removed from the group to which this event applies|
-|RoleId|String|The role ID of the role to which this event applies.|
-|RoleName|String|The display name of the role to which this event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
-
diff --git a/playfab-docs/api-references/events/group-role-updated.md b/playfab-docs/api-references/events/group-role-updated.md
deleted file mode 100644
index bcc168f28..000000000
--- a/playfab-docs/api-references/events/group-role-updated.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: group_role_updated
-author: joannaleecy
-description: group_role_updated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# group_role_updated
-
-This event is triggered when a role is updated within a group.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|GroupName|String|The name of the group to which this event applies.|
-|NewValues|[RolePropertyValues](data-types/rolepropertyvalues.md)|The new values of the role's changed properties|
-|OldValues|[RolePropertyValues](data-types/rolepropertyvalues.md)|The previous values of the role's changed properties|
-|RoleId|String|The role ID of the role to which this event applies.|
-|RoleName|String|The display name of the role to which this event applies.|
-|UpdaterEntityId|String|The identifier for the entity that updated the container to which this event applies.|
-|UpdaterEntityType|String|The type of entity that updated the container to which this event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
diff --git a/playfab-docs/api-references/events/group-updated.md b/playfab-docs/api-references/events/group-updated.md
deleted file mode 100644
index ac9b3ed90..000000000
--- a/playfab-docs/api-references/events/group-updated.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: group_updated
-author: joannaleecy
-description: group_updated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# group_updated
-
-This event is triggered when an entity group is updated.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|GroupName|String|The name of the group to which this event applies.|
-|NewValues|[GroupPropertyValues](data-types/grouppropertyvalues.md)|The new values of the group's changed properties|
-|OldValues|[GroupPropertyValues](data-types/grouppropertyvalues.md)|The previous values of the group's changed properties|
-|UpdaterEntityId|String|The identifier for the entity that updated the group to which this event applies.|
-|UpdaterEntityType|String|The type of entity that updated the group to which this event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
diff --git a/playfab-docs/api-references/events/index.md b/playfab-docs/api-references/events/index.md
index 95c293b53..a8181cde3 100644
--- a/playfab-docs/api-references/events/index.md
+++ b/playfab-docs/api-references/events/index.md
@@ -14,453 +14,733 @@ ms.localizationpriority: medium
 
 These are the built-in PlayStream events which are automatically generated by PlayFab Game Services APIs and written to the event pipeline. In addition to these events, you can create your own custom events using the [WriteEvents](xref:titleid.playfabapi.com.events.playstreamevents.writeevents) API.
 
-Each event type has a set of properties that are included as part of event's data wherever it is sent. You can view these properties and build rules for triggering actions based on their values in the PlayStream tab of the Game Manager.
+Each event type has a set of properties that are included as part of event's data wherever it's sent. You can view these properties and build rules for triggering actions based on their values in the PlayStream tab of the Game Manager.
 
-## General
+## AdPlacement
 
-- [entity_created](entity-created.md)  
-  This event is triggered when an entity is created.  
+- [player_ad_closed](AdPlacement/player-ad-closed.md)  
+  This event is triggered when a player closes an ad.
+
+- [player_ad_ended](AdPlacement/player-ad-ended.md)  
+  This event is triggered when a player finishes an ad.
+
+- [player_ad_opened](AdPlacement/player-ad-opened.md)  
+  This event is triggered when a player opens an ad.
+
+- [player_ad_rewarded](AdPlacement/player-ad-rewarded.md)  
+  This event is triggered when a player receives an ad reward.
+
+- [player_ad_started](AdPlacement/player-ad-started.md)  
+  This event is triggered when a player starts an ad.
+
+## Addons
+
+- [title_addon_changed](Addons/title-addon-changed.md)  
+  This event is triggered when a title addon is changed.
 
-- [entity_executed_cloud_script](entity-executed-cloud-script.md)  
+## ApiAccessPolicy
+
+- [title_api_settings_changed](ApiAccessPolicy/title-api-settings-changed.md)  
+  This event is triggered when an API Features setting is changed for the title.
+
+- [title_permission_policy_changed](ApiAccessPolicy/title-permission-policy-changed.md)  
+  This event is triggered when an update occurs to a title's permission policies.
+
+## CloudScript
+
+- [entity_executed_cloud_script](CloudScript/entity-executed-cloud-script.md)  
   This event is optionally triggered when an Entity CloudScript function is executed, either by calling the ExecuteCloudScript API with the GeneratePlayStreamEvent option or triggered by a PlayStream event action with the 'Publish results as a PlayStream Event' box checked.  
 
-- [entity_files_set](entity-files-set.md)  
-  This event is triggered when files are attached to an entity.
+- [player_executed_cloudscript](CloudScript/player-executed-cloudscript.md)  
+  This event is optionally triggered when a CloudScript function is executed, either by calling the ExecuteCloudScript API with the GeneratePlayStreamEvent option or triggered by a PlayStream event action with the 'Publish results as a PlayStream Event' box checked.
 
-- [entity_language_updated](entity-language-updated.md)  
-  This event is triggered when the language associated with an entity is changed.
+- [player_triggered_action_executed_cloudscript](CloudScript/player-triggered-action-executed-cloudscript.md)  
+  This event is triggered when a CloudScript function is run as the result of a PlayStream action, and the 'Publish results as a PlayStream Event' box was checked.
 
-- [entity_logged_in](entity-logged-in.md)  
-  This event is triggered when an entity has logged in.
+- [title_added_cloudscript](CloudScript/title-added-cloudscript.md)  
+  This event is triggered when new CloudScript is uploaded to PlayFab.
 
-- [entity_objects_set](entity-objects-set.md)  
-  This event is triggered when objects are attached to an entity.
+- [title_published_cloudscript](CloudScript/title-published-cloudscript.md)  
+  An inactive revision of CloudScript has been made into the active 'live' version.
 
-- [entity_virtual_currency_balances_changed](entity-virtual-currency-balances-changed.md)  
-  This event is triggered when an entity's virtual currency balance changes.
+- [title_scheduled_cloudscript_executed](CloudScript/title-scheduled-cloudscript-executed.md)  
+  This event is triggered when a CloudScript function is run by a scheduled task.  
 
-- [group_created](group-created.md)
-  This event is triggered when an entity group is created.
+- [cloudscript_executed](CloudScript/cloudscript-executed.md)  
+  This event is triggered when a CloudScript function is executed.
+
+## DeveloperIdentity
+
+- [studio_created](DeveloperIdentity/studio-created.md)  
+  This event is triggered when a studio is created.
+
+- [studio_user_added](DeveloperIdentity/studio-user-added.md)
+  This event is triggered when a user accepts a studio invitation.  
+
+- [studio_user_invited](DeveloperIdentity/studio-user-invited.md)  
+  This event is triggered when a user is invited to a studio.
+
+- [studio_user_removed](DeveloperIdentity/studio-user-removed.md)  
+  This event is triggered when a user is removed from a studio.
+
+## Experimentation
+
+- [exclusion_group_created](Experimentation/exclusion-group-created.md)
+  This event is triggered when an exclusion group is created.
+
+- [exclusion_group_deleted](Experimentation/exclusion-group-deleted.md)
+  This event is triggered when an exclusion group is deleted.
+
+- [exclusion_group_updated](Experimentation/exclusion-group-updated.md)
+  This event is triggered when an exclusion group is updated.
+
+- [experiment_created](Experimentation/experiment-created.md)
+  This event is triggered when an experiment is created.
+
+- [experiment_deleted](Experimentation/experiment-deleted.md)
+  This event is triggered when an experiment is deleted.
+
+- [experiment_start_requested](Experimentation/experiment-start-requested.md)
+  This event is triggered when an experiment start is requested.
+
+- [experiment_stop_requested](Experimentation/experiment-stop-requested.md)
+  This event is triggered when an experiment stop is requested.
+
+- [experiment_updated](Experimentation/experiment-updated.md)
+  This event is triggered when an experiment is updated.
+
+- [player_experiment_variants_changed](Experimentation/player-experiment-variants-changed.md)
+  This event is triggered when a player's experiment variants are changed.
+
+
+## Extension
+
+- [title_aborted_task](Extension/title-aborted-task.md)  
+  This event is triggered when a task instance is aborted.
+
+- [title_completed_task](Extension/title-completed-task.md)  
+  This event is triggered when a scheduled task has completed
+
+- [title_created_task](Extension/title-created-task.md)  
+  This event is triggered when a task is created.
+
+- [title_deleted_task](Extension/title-deleted-task.md)  
+  This event is triggered when a task is deleted.
+
+- [title_exceeded_limit](Extension/title-exceeded-limit.md)  
+  This event is triggered when a title exceeds a service limit and receives an error.
+
+- [title_limit_changed](Extension/title-limit-changed.md)  
+  This event is triggered when a title changes a service limit.
+
+- [title_started_task](Extension/title-started-task.md)  
+  This event is triggered when a task is scheduled to run.
+
+- [title_updated_task](Extension/title-updated-task.md)  
+  This event is triggered when a task is updated.
+
+- [export_completed](Extension/export-completed.md)  
+  This event is triggered when an export operation is completed.
+
+## Functions
+
+- [function_executed](Functions/function-executed.md)  
+  This event is triggered when a function is executed.
+
+- [function_registered](Functions/function-registered.md)  
+  This event is triggered when a function is registered.
+
+- [function_unregistered](Functions/function-unregistered.md)  
+  This event is triggered when a function is unregistered.
 
-- [group_deleted](group-deleted.md)  
-  This event is triggered when an entity group is deleted.
+- [player_triggered_action_executed_function](Functions/player-triggered-action-executed-function.md)  
+  This event is triggered when a function is run as the result of a PlayStream action.
 
-- [group_members_added](group-members-added.md)  
+- [title_scheduled_function_executed](Functions/title-scheduled-function-executed.md)  
+  This event is triggered when a function is run by a scheduled task.
+
+## Groups
+
+- [group_created](Groups/group-created.md)
+  This event is triggered when an entity group is created.
+
+- [group_members_added](Groups/group-members-added.md)  
   This event is triggered when a member is added to an entity group.
 
-- [group_members_removed](group-members-removed.md)  
+- [group_members_removed](Groups/group-members-removed.md)  
   This event is triggered when a member is removed from an entity group.
 
-- [group_role_created](group-role-created.md)  
+- [group_role_created](Groups/group-role-created.md)  
   This event is triggered when a role is created for a group.
 
-- [group_role_deleted](group-role-deleted.md)  
+- [group_role_deleted](Groups/group-role-deleted.md)  
   This event is triggered when a role is deleted from a group.
 
-- [group_role_members_added](group-role-members-added.md)  
+- [group_role_members_added](Groups/group-role-members-added.md)  
   This event is triggered when a list of entities are added to a role within a group.
 
-- [group_role_members_removed](group-role-members-removed.md)  
+- [group_role_members_removed](Groups/group-role-members-removed.md)  
   This event is triggered when a list of entities are removed from a role within a group.
 
-- [group_role_updated](group-role-updated.md)  
+- [group_role_updated](Groups/group-role-updated.md)  
   This event is triggered when a role is updated within a group.
 
-- [group_updated](group-updated.md)  
+- [group_updated](Groups/group-updated.md)  
   This event is triggered when an entity group is updated.
 
-- [matchmaking_match_found](matchmaking-match-found.md)  
-  This event is triggered when a group of tickets are matched together.  
-  
-- [matchmaking_ticket_completed](matchmaking-ticket-completed.md)  
-  This event is triggered when a matchmaking ticket reaches a completion state.  
-  
-- [matchmaking_user_ticket_completed](matchmaking-user-ticket-completed.md)  
-  This event is sent to each of the users in the completed ticket.
+- [members_added](Groups/members-added.md)  
+  This event is triggered when members are added to a group.
+
+- [members_removed](Groups/members-removed.md)  
+  This event is triggered when members are removed from a group.
+
+- [members_role_updated](Groups/members-role-updated.md)  
+  This event is triggered when members' roles are updated in a group.
+
+- [player_updated_membership](Groups/player-updated-membership.md)  
+  This event is triggered when a player's membership is updated.
+
+- [role_updated](Groups/role-updated.md)  
+  This event is triggered when a role is updated.
+
+## Telemetry
+
+- [apikey_activated](Telemetry/apikey-activated.md)  
+  This event is triggered when an API key is activated.
+
+- [apikey_created](Telemetry/apikey-created.md)  
+  This event is triggered when an API key is created.
+
+- [apikey_deactivated](Telemetry/apikey-deactivated.md)  
+  This event is triggered when an API key is deactivated.
+
+- [apikey_deleted](Telemetry/apikey-deleted.md)  
+  This event is triggered when an API key is deleted.
+
+## TitleCommunications
+
+- [player_registered_push_notifications](TitleCommunications/player-registered-push-notifications.md)  
+  This event is triggered when a player registers for push notifications.
+
+- [sent_email](TitleCommunications/sent-email.md)  
+  This event is triggered when an email is sent or fails to send to a player.
+
+- [sent_push_notification](TitleCommunications/sent-push-notification.md)  
+  This event is triggered when a push notification is sent or fails to be sent to a player.
+
+- [email_sent](TitleCommunications/email-sent.md)  
+  This event is triggered when an email is sent.
+
+- [push_notification_sent](TitleCommunications/push-notification-sent.md)  
+  This event is triggered when a push notification is sent.
+
+## General
+
+- [entity_virtual_currency_balances_changed](General/entity-virtual-currency-balances-changed.md)  
+  This event is triggered when an entity's virtual currency balance changes.
+
+- [tenancy_connector_onboard](General/tenancy-connector-onboard.md)  
+  This event is triggered when a tenancy connector is onboarded.
+
+- [studio_tier_updated](General/studio-tier-updated.md)  
+  This event is triggered when a studio tier is updated.
+
+## Matchmaking
+- [title_queue_config_updated](Matchmaking/title-queue-config-updated.md)  
+  This event is triggered when a queue config is changed.
+
+- [match_found](Matchmaking/match-found.md)  
+  This event is triggered when a match is found.
+
+- [ticket_completed](Matchmaking/ticket-completed.md)  
+  This event is triggered when a ticket is completed.
+
+- [user_ticket_invited](Matchmaking/user-ticket-invited.md)  
+  This event is triggered when a user is invited to a ticket.
 
-- [matchmaking_user_ticket_invite](matchmaking-user-ticket-invite.md)  
-  This event is triggered when a ticket with an invited user is created. The event will be sent to the invited user.  
+## Multiplayer Servers
 
-- [multiplayer_server_build_deleted](multiplayer-server-build-deleted.md)  
+- [build_alias_created](MultiplayerServers/build-alias-created.md)  
+  This event is triggered when a multiplayer server build alias is created.
+
+- [build_alias_deleted](MultiplayerServers/build-alias-deleted.md)  
+  This event is triggered when a multiplayer server build alias is deleted.
+
+- [build_alias_updated](MultiplayerServers/build-alias-updated.md)  
+  This event is triggered when a multiplayer server build alias is updated.
+
+- [build_deleted](MultiplayerServers/build-deleted.md)  
   This event is triggered when a multiplayer server build is deleted.  
 
-- [multiplayer_server_build_region_status_changed](multiplayer-server-build-region-status-changed.md)  
-  This event is triggered when a multiplayer server's build region status is changed.  
+- [build_region_status_changed](MultiplayerServers/build-region-status-changed.md)  
+  This event is triggered when a multiplayer server build region status is changed.  
 
-- [multiplayer_server_build_region_updated](multiplayer-server-build-region-updated.md)  
+- [build_region_updated](MultiplayerServers/build-region-updated.md)  
   This event is triggered when a multiplayer server build region is updated.
 
-- [multiplayer_server_certificate_deleted](multiplayer-server-certificate-deleted.md)  
+- [build_region_utilization](MultiplayerServers/build-region-utilization.md)  
+  This event is triggered to display the utilization of servers for a build in each region.
+
+- [certificate_deleted](MultiplayerServers/certificate-deleted.md)  
   This event is triggered when a multiplayer server certificate is deleted.
 
-- [multiplayer_server_certificate_uploaded](multiplayer-server-certificate-uploaded.md)  
+- [certificate_uploaded](MultiplayerServers/certificate-uploaded.md)  
   This event is triggered when a multiplayer server certificate is uploaded.  
 
-- [multiplayer_server_create_build_initiated](multiplayer-server-create-build-initiated.md)  
+- [crash_detected](MultiplayerServers/crash-detected.md)  
+  This event triggered when a crash dump is found on a terminating server.
+
+- [create_build_initiated](MultiplayerServers/create-build-initiated.md)  
   This event is triggered when a multiplayer server build is initiated.
 
-- [multiplayer_server_game_asset_deleted](multiplayer-server-game-asset-deleted.md)  
+- [enabled_for_title](MultiplayerServers/enabled-for-title.md)  
+  This event is triggered when a title enables PlayFab servers
+
+- [game_asset_deleted](MultiplayerServers/game-asset-deleted.md)  
   This event is triggered when a multiplayer server game asset is deleted.  
 
-- [multiplayer_server_requested](multiplayer-server-requested.md)  
-  This event is triggered when a multiplayer server shutdown is requested.  
+- [monitoring_output_saved](MultiplayerServers/monitoring-output-saved.md)  
+  This event is triggered when the output of a monitoring application has been saved and can be downloaded.
+
+- [secret_added](MultiplayerServers/secret-added.md)  
+  This event is triggered when a multiplayer server secret is added.
+
+- [secret_deleted](MultiplayerServers/secret-deleted.md)  
+  This event is triggered when a multiplayer server secret is deleted.
+
+- [server_requested](MultiplayerServers/server-requested.md)  
+  This event is triggered when a multiplayer server is requested.    
 
-- [multiplayer_server_state_changed](multiplayer-server-state-changed.md)  
+- [server_state_changed](MultiplayerServers/server-state-changed.md)  
   This event is triggered when a multiplayer server's state is changed.
 
-- [multiplayer_server_vm_assigned](multiplayer-server-vm-assigned.md)  
+- [vm_assigned](MultiplayerServers/vm-assigned.md)  
   This event is triggered when a virtual machine is assigned to a multiplayer server build.  
 
-- [multiplayer_server_vm_remote_user_created](multiplayer-server-vm-remote-user-created.md)  
+- [vm_game_certificates_deployed](MultiplayerServers/vm-game-certificates-deployed.md)   
+  This event is triggered when game certificates are deployed in a game virtual machine.
+
+- [vm_remote_user_created](MultiplayerServers/vm-remote-user-created.md)  
   This event is triggered when a multiplayer server virtual machine remote user is created.
 
-- [multiplayer_server_vm_remote_user_deleted](multiplayer-server-vm-remote-user-deleted.md)  
+- [vm_remote_user_deleted](MultiplayerServers/vm-remote-user-deleted.md)  
   This event is triggered when a multiplayer server virtual machine remote user is deleted.  
 
-- [multiplayer_server_vm_unassignment_started](multiplayer-server-vm-unassignment-started.md)  
+- [vm_state_change](MultiplayerServers/vm-state-change.md)  
+  This event is triggered when a multiplayer virtual machine's state is changed.
+
+- [vm_unassignment_started](MultiplayerServers/vm-unassignment-started.md)  
   This event is triggered when a virtual machine is unassigned from a multiplayer server build.  
 
-- [multiplayer_server_vm_unhealthy](multiplayer-server-vm-unhealthy.md)  
+- [vm_unhealthy](MultiplayerServers/vm-unhealthy.md)  
   This event is triggered when a virtual machine is found to be unhealthy.
 
-- [studio_created](studio-created.md)  
-  This event is triggered when a studio is created.
-
-- [studio_user_added](studio-user-added.md)
-  This event is triggered when a user accepts a studio invitation.  
-
-- [studio_user_invited](studio-user-invited.md)  
-  This event is triggered when a user is invited to a studio.
-
-- [studio_user_removed](studio-user-removed.md)  
-  This event is triggered when a user is removed from a studio.
+## CatalogV1
 
-- [tenancy_connector_onboard](tenancy-connector-onboard.md)  
-  This event is triggered when a tenancy connector is onboarded.
+- [title_catalog_updated](CatalogV1/title-catalog-updated.md)  
+  This event is triggered when a catalog is changed.
 
-- [studio_tier_updated](studio-tier-updated.md)  
-  This event is triggered when a studio tier is updated.
+- [title_store_updated](CatalogV1/title-store-updated.md)  
+  This event is triggered when a store is changed.
 
-## Catalog
+## CatalogV2
 
-- [item_created](item-created.md)  
+- [item_created](catalogv2/item-created.md)  
   This event is triggered when an item is created.
 
-- [item_deleted](item-deleted.md)  
+- [item_deleted](catalogv2/item-deleted.md)  
   This event is triggered when an item is deleted.
 
-- [item_moderation_state_changed](item-moderation-state-changed.md)  
+- [item_moderation_state_changed](catalogv2/item-moderation-state-changed.md)  
   This event is triggered when an item moderation state is changed.
 
-- [item_publish_requested](item-publish-requested.md)  
-  This event is triggered when an publishing is started.
+- [item_publish_requested](catalogv2/item-publish-requested.md)  
+  This event is triggered when publishing is started.
 
-- [item_reported](item-reported.md)  
+- [item_purchased](catalogv2/item-purchased.md)  
+  This event is triggered when an item is purchased.
+
+- [item_reported](catalogv2/item-reported.md)  
   This event is triggered when an item is reported.
 
-- [item_updated](item-updated.md)  
+- [item_updated](catalogv2/item-updated.md)  
   This event is triggered when an item is updated.
 
-- [review_reported](review-reported.md)  
+- [review_reported](catalogv2/review-reported.md)  
   This event is triggered when a review is reported.
 
-- [reviews_takedown_requested](reviews-takedown-requested.md)  
-  Event trigged when a takedown of reviews is requested.
+- [reviews_takedown_requested](catalogv2/reviews-takedown-requested.md)  
+  This event is triggered when a takedown of reviews is requested.
 
 ## Character
 
-- [character_consumed_item](character-consumed-item.md)  
+- [character_consumed_item](Character/character-consumed-item.md)  
   This event is triggered when a character consumes an item from their inventory.  
 
-- [character_created](character-created.md)  
-  This event is triggered when a character is created for the first time.  
-
-- [character_inventory_item_added](character-inventory-item-added.md)  
+- [character_inventory_item_added](Character/character-inventory-item-added.md)  
   This event is triggered when an item is granted to a character.
 
-- [character_statistic_changed](character-statistic-changed.md)  
-  This event is triggered when a character statistic is changed.  
-
-- [character_statistic_deleted](character-statistic-deleted.md)  
-  This event is triggered when a character statistic is deleted.  
-
-- [character_vc_item_purchased](character-vc-item-purchased.md)  
+- [character_vc_item_purchased](Character/character-vc-item-purchased.md)  
   This event is triggered when the character makes a purchase using virtual currency.
 
-- [character_virtual_currency_balance_changed](character-virtual-currency-balance-changed.md)  
+- [character_virtual_currency_balance_changed](Character/character-virtual-currency-balance-changed.md)  
   This event is triggered when a character's virtual currency balance changes.  
 
 ## Inventory
 
-- [items_added](items-added.md)  
+- [items_added](Inventory/items-added.md)  
   Event raised when items have been added to an inventory.
 
-- [items_deleted](items-deleted.md)  
+- [items_clawback_completed](Inventory/items-clawback-completed.md)  
+  This event is triggered when an items clawback operation is completed.
+
+- [items_clawback_reversal_completed](Inventory/items-clawback-reversal-completed.md)  
+  This event is triggered when an items clawback reversal operation is completed.
+
+- [items_deleted](Inventory/items-deleted.md)  
   Event raised when items have been deleted from an inventory.
 
-- [items_purchased](items-purchased.md)  
+- [items_expired](Inventory/items-expired.md)  
+  This event is triggered when items have expired in an inventory.
+
+- [items_purchased](Inventory/items-purchased.md)  
   Event raised when items have been purchased from an inventory.
 
-- [items_redeemed](items-redeemed.md)  
+- [items_redeemed](Inventory/items-redeemed.md)  
   Event raised when items have been redeemed to an inventory.
 
-- [items_subtracted](items-subtracted.md)  
+- [items_subtracted](Inventory/items-subtracted.md)  
   Event raised when items have been subtracted from an inventory.
 
-- [items_transferred](items-transferred.md)  
+- [items_transferred](Inventory/items-transferred.md)  
   Event raised when items have been transferred to or from an inventory.
 
-- [items_updated](items-updated.md)  
+- [items_updated](Inventory/items-updated.md)  
   Event raised when items have been updated in an inventory.
 
+- [marketplace_transaction_redeemed](Inventory/marketplace-transaction-redeemed.md)  
+  This event is triggered when a marketplace transaction is redeemed.
+
+## GameSave
+
+- [gamesave_version_finalized](GameSave/gamesave-version-finalized.md)  
+  This event is triggered when a game save version is finalized with all the files fully uploaded.
+
+- [gamesave_version_marked_known_good](GameSave/gamesave-version-marked-known-good.md)  
+  This event is triggered when a game save version is marked as known good.
+
+## Networking
+
+- [client_authentication_completed](Networking/client-authentication-completed.md)  
+  This event is triggered when client authentication is completed.
+
+- [client_connected_to_network](Networking/client-connected-to-network.md)  
+  This event is triggered when a client connects to a network.
+
+- [client_initialization_completed](Networking/client-initialization-completed.md)  
+  This event is triggered when client initialization is completed.
+
+- [client_network_created](Networking/client-network-created.md)  
+  This event is triggered when a client network is created.
+
+- [client_network_destroyed](Networking/client-network-destroyed.md)  
+  This event is triggered when a client network is destroyed.
+
+- [client_network_information_received](Networking/client-network-information-received.md)  
+  This event is triggered when client network information is received.
+
+- [client_request_failed](Networking/client-request-failed.md)  
+  This event is triggered when a client request fails.
+
+- [data_received_by_clients](Networking/data-received-by-clients.md)  
+  This event is triggered when data is received by clients.
+
+- [data_sent_by_clients](Networking/data-sent-by-clients.md)  
+  This event is triggered when data is sent by clients.
+
+- [moderation_service_request_count](Networking/moderation-service-request-count.md)  
+  This event is triggered when moderation service request count is reported.
+
+- [player_disconnected_from_network](Networking/player-disconnected-from-network.md)  
+  This event is triggered when a player disconnects from a network.
+
+- [unity_client_initialization_completed](Networking/unity-client-initialization-completed.md)  
+  This event is triggered when Unity client initialization is completed.
+
+- [unreal_client_initialization_completed](Networking/unreal-client-initialization-completed.md)  
+  This event is triggered when Unreal client initialization is completed.
+
 ## Partner
 
-- [display_name_filtered](display-name-filtered.md)  
+- [display_name_filtered](Partner/display-name-filtered.md)  
   This event is triggered when a display name is filtered by community sift.  
 
-- [player_display_name_filtered](player-display-name-filtered.md)  
-  This event is triggered when a display name is filtered by community sift only if there is an associated player EntityId for the event.
+- [player_display_name_filtered](Partner/player-display-name-filtered.md)  
+  This event is triggered when a display name is filtered by community sift only if there's an associated player EntityId for the event.
 
-- [player_photon_session_authenticated](player-photon-session-authenticated.md)  
+- [player_photon_session_authenticated](Partner/player-photon-session-authenticated.md)  
   This event is triggered when a player connects to a Photon Cloud application and authenticates with PlayFab using Photon custom authentication.
 
 ## Player
+- [player_action_executed](Player/player-action-executed.md)  
+  This event is triggered when an action linked to a segmentation change or event rule executes on a player.
 
-- [auth_token_validated](auth-token-validated.md)  
-  This event is triggered when an email confirmation link is clicked.
+- [player_ad_campaign_attribution](Player/player-ad-campaign-attribution.md)  
+  This event is triggered by an attribution tracking Add-on when a player is matched to a paid acquisition campaign.
 
-- [title_deleted_master_player](title-deleted-master-player.md)  
-  This event is triggered when a GDPR delete is finished.
+- [player_consumed_item](Player/player-consumed-item.md)  
+  This event is triggered when a player consumes an item from their inventory.
 
-- [player_action_executed](player-action-executed.md)  
-  This event is triggered when an action linked to a segmentation change or event rule executes on a player.
+- [player_inventory_item_added](Player/player-inventory-item-added.md)  
+  This event is triggered when an item is granted to a player.
 
-- [player_ad_campaign_attribution](player-ad-campaign-attribution.md)  
-  This event is triggered by an attribution tracking Add-on when a player is matched to a paid acquisition campaign.
+- [player_paid_for_purchase](Player/player-paid-for-purchase.md)  
+  This event is triggered when the second step of the payment process completes, paying for the purchase.
 
-- [player_ad_closed](player-ad-closed.md)  
-  This event is triggered when a player closes an ad.
+- [player_realmoney_purchase](Player/player-realmoney-purchase.md)  
+  This event is triggered when a player makes a real money purchase, and generates revenue for the game.
 
-- [player_added_title](player-added-title.md)  
-  This event is triggered when a player creates a new account for a title. Note: this event is triggered once per title rather than once per publisher.
+- [player_receipt_validation](Player/player-receipt-validation.md)  
+  This event is triggered when a player attempts to make a real money purchase and the purchase receipt is being validated.
 
-- [player_ad_ended](player-ad-ended.md)  
-  This event is triggered when a player finishes an ad.
+- [player_redeemed_coupon](Player/player-redeemed-coupon.md)  
+  This event is triggered when a player redeems a coupon.
 
-- [player_ad_opened](player-ad-opened.md)  
-  This event is triggered when a player opens an ad.
+- [player_set_profile_property](Player/player-set-profile-property.md)  
+  This event is triggered when PlayFab makes an internal adjustment to a player profile.
 
-- [player_ad_rewarded](player-ad-rewarded.md)  
-  This event is triggered when a player recieves an ad reward.
+- [player_started_purchase](Player/player-started-purchase.md)  
+  This event is triggered when a player starts a purchase.
 
-- [player_ad_activity_valued](player-ad-activity-valued.md)  
-  Event triggered when reported value of ad view is recorded
+- [player_vc_item_purchased](Player/player-vc-item-purchased.md)  
+  This event is triggered when the player makes a purchase using virtual currency.
 
-- [player_ad_started](player-ad-started.md)  
-  This event is triggered when a player starts an ad.
+- [player_virtual_currency_balance_changed](Player/player-virtual-currency-balance-changed.md)  
+  This event is triggered when a player's virtual currency balance changes.
+
+## PlayerIdentity
+
+- [auth_token_validated](PlayerIdentity/auth-token-validated.md)  
+  This event is triggered when an email confirmation link is clicked.
+
+- [character_created](PlayerIdentity/character-created.md)  
+  This event is triggered when a character is created for the first time.  
+
+- [entity_created](PlayerIdentity/entity-created.md)  
+  This event is triggered when an entity is created.  
 
-- [player_banned](player-banned.md)  
+- [entity_logged_in](PlayerIdentity/entity-logged-in.md)  
+  This event is triggered when an entity has logged in.
+
+- [player_added_title](PlayerIdentity/player-added-title.md)  
+  This event is triggered when a player creates a new account for a title. Note: this event is triggered once per title rather than once per publisher.
+
+- [player_banned](PlayerIdentity/player-banned.md)  
   This event is triggered when a player is banned.
 
-- [player_changed_avatar](player-changed-avatar.md)  
+- [player_changed_avatar](PlayerIdentity/player-changed-avatar.md)  
   This event is triggered when a player's avatar URL is changed.
 
-- [player_completed_password_reset](player-completed-password-reset.md)  
+- [player_completed_password_reset](PlayerIdentity/player-completed-password-reset.md)  
   This event is triggered when a player completes the password reset process by visiting the link URL that was sent to them and choosing a new password.
 
-- [player_consumed_item](player-consumed-item.md)  
-  This event is triggered when a player consumes an item from their inventory.
-
-- [player_created](player-created.md)  
+- [player_created](PlayerIdentity/player-created.md)  
   This event is triggered when a player account is created for the first time. Note: this event is only triggered once per publisher, not once per title.
 
-- [player_data_exported](player-data-exported.md)  
+- [player_data_exported](PlayerIdentity/player-data-exported.md)  
   This event is triggered when a player's data is exported.
 
-- [player_device_info](player-device-info.md)  
+- [player_device_info](PlayerIdentity/player-device-info.md)  
   This event is triggered once after the player logs in based on the settings for your title.
 
-- [player_displayname_changed](player-displayname-changed.md)  
+- [player_displayname_changed](PlayerIdentity/player-displayname-changed.md)  
   This event is triggered when a player's display name is changed.
 
-- [player_executed_cloudscript](player-executed-cloudscript.md)  
-  This event is optionally triggered when a CloudScript function is executed, either by calling the ExecuteCloudScript API with the GeneratePlayStreamEvent option or triggered by a PlayStream event action with the 'Publish results as a PlayStream Event' box checked.
-
-- [player_inventory_item_added](player-inventory-item-added.md)  
-  This event is triggered when an item is granted to a player.
-
-- [player_linked_account](player-linked-account.md)  
+- [player_linked_account](PlayerIdentity/player-linked-account.md)  
   This event is triggered when a new authentication method is linked to a player's account.
 
-- [player_logged_in](player-logged-in.md)  
+- [player_logged_in](PlayerIdentity/player-logged-in.md)  
   This event is triggered when a player logs in.
 
-- [player_password_reset_link_sent](player-password-reset-link-sent.md)  
+- [player_password_reset_link_sent](PlayerIdentity/player-password-reset-link-sent.md)  
   This event is triggered when a player is sent a link to reset their password.
 
-- [player_paid_for_purchase](player-paid-for-purchase.md)  
-  This event is triggered when the second step of the payment process completes, paying for the purchase.
-
-- [player_ranked_on_leaderboard_version](player-ranked-on-leaderboard-version.md)  
-  This event is triggered for the top-ranked players on a leaderboard when the leaderboard version changes (e.g. when a leaderboard statistic version is incremented). The maximum number of leaderboard entries for which the event is generated is controlled by the "Leaderboard version change top rank events sent" title limit.
-
-- [player_realmoney_purchase](player-realmoney-purchase.md)  
-  This event is triggered when a player makes a real money purchase, and generates revenue for the game.
-
-- [player_receipt_validation](player-receipt-validation.md)  
-  This event is triggered when a player attempts to make a real money purchase and the purchase receipt is being validated.
-
-- [player_redeemed_coupon](player-redeemed-coupon.md)  
-  This event is triggered when a player redeems a coupon.
-
-- [player_registered_push_notifications](player-registered-push-notifications.md)  
-  This event is triggered when a player registers for push notifications.
-
-- [player_removed_title](player-removed-title.md)  
+- [player_removed_title](PlayerIdentity/player-removed-title.md)  
   This event is triggered when a player account for a title is removed. Note: this event is triggered once per title rather than once per publisher.
 
-- [player_reported_as_abusive](player-reported-as-abusive.md)  
+- [player_reported_as_abusive](PlayerIdentity/player-reported-as-abusive.md)  
   This event is triggered when a player is reported by another player as abusive.
 
-- [player_set_profile_property](player-set-profile-property.md)  
-  This event is triggered when PlayFab makes an internal adjustment to a player profile.
+- [player_tag_added](PlayerIdentity/player-tag-added.md)  
+  This event is triggered when a tag is added to a player profile.
 
-- [player_started_purchase](player-started-purchase.md)  
-  This event is triggered when a player starts a purchase.
+- [player_tag_removed](PlayerIdentity/player-tag-removed.md)  
+  This event is triggered when a tag is removed from a player profile.
 
-- [player_statistic_changed](player-statistic-changed.md)  
-  This event is triggered when a player statistic is changed.
+- [player_unlinked_account](PlayerIdentity/player-unlinked-account.md)  
+  This event is triggered when an authentication method is unlinked from a player's account.
 
-- [player_statistic_deleted](player-statistic-deleted.md)  
-  This event is triggered when a player statistic is deleted.
+- [player_updated_contact_email](PlayerIdentity/player-updated-contact-email.md)  
+  This event is triggered when a player updates a contact email on their profile.
 
-- [player_tag_added](player-tag-added.md)  
-  This event is triggered when a tag is added to a player profile.
+- [player_verified_contact_email](PlayerIdentity/player-verified-contact-email.md)  
+  This event is triggered when a contact email is verified for a player.
 
-- [player_tag_removed](player-tag-removed.md)  
-  This event is triggered when a tag is removed from a player profile.
+- [title_deleted_master_player](PlayerIdentity/title-deleted-master-player.md)  
+  This event is triggered when a GDPR delete is finished.
 
-- [player_triggered_action_executed_cloudscript](player-triggered-action-executed-cloudscript.md)  
-  This event is triggered when a CloudScript function is run as the result of a PlayStream action, and the 'Publish results as a PlayStream Event' box was checked.
+- [title_initiated_player_password_reset](PlayerIdentity/title-initiated-player-password-reset.md)  
+  This event is triggered when a title initiates the account recovery process for a player.
 
-- [player_unlinked_account](player-unlinked-account.md)  
-  This event is triggered when an authentication method is unlinked from a player's account.
+- [title_profile_view_constraints_changed](PlayerIdentity/title-profile-view-constraints-changed.md)  
+  This event is triggered when a profile view constraint is changed for the title.
 
-- [player_updated_contact_email](player-updated-contact-email.md)  
-  This event is triggered when a player updates a contact email on their profile.
+- [entity_deleted](PlayerIdentity/entity-deleted.md)  
+  This event is triggered when an entity is deleted.
 
-- [player_vc_item_purchased](player-vc-item-purchased.md)  
-  This event is triggered when the player makes a purchase using virtual currency.
+- [logged_in_to_title](PlayerIdentity/logged-in-to-title.md)  
+  This event is triggered when a user logs in to a title.
 
-- [player_verified_contact_email](player-verified-contact-email.md)  
-  This event is triggered when a contact email is verified for a player.
+- [player_authenticated](PlayerIdentity/player-authenticated.md)  
+  This event is triggered when a player is authenticated.
 
-- [player_virtual_currency_balance_changed](player-virtual-currency-balance-changed.md)  
-  This event is triggered when a player's virtual currency balance changes.
+- [player_custom_properties_changed](PlayerIdentity/player-custom-properties-changed.md)  
+  This event is triggered when a player's custom properties are changed.
 
-- [sent_push_notification](sent-push-notification.md)  
-  This event is triggered when a push notification is sent or fails to be sent to a player.
+- [player_identity_link_added](PlayerIdentity/player-identity-link-added.md)  
+  This event is triggered when a player identity link is added.
 
-- [sent_email](sent-email.md)  
-  This event is triggered when an email is sent or fails to send to a player.
+- [player_identity_link_removed](PlayerIdentity/player-identity-link-removed.md)  
+  This event is triggered when a player identity link is removed.
 
-## Session
+- [player_updated_login_email](PlayerIdentity/player-updated-login-email.md)  
+  This event is triggered when a player updates their login email.
 
-- [client_focus_change](client-focus-change.md)  
-  This event is triggered every time the application enters or exits focus on the player's device.
+## PlayerProfile
 
-- [client_session_start](client-session-start.md)  
-  This event is triggered when a new client session starts.
+- [entity_files_set](PlayerProfile/entity-files-set.md)  
+  This event is triggered when files are attached to an entity.
 
-## Title
+- [entity_language_updated](PlayerProfile/entity-language-updated.md)  
+  This event is triggered when the language associated with an entity is changed.
 
-- [title_aborted_task](title-aborted-task.md)  
-  This event is triggered when a task instance is aborted.
+- [entity_objects_set](PlayerProfile/entity-objects-set.md)  
+  This event is triggered when objects are attached to an entity.
 
-- [title_added_cloudscript](title-added-cloudscript.md)  
-  This event is triggered when new CloudScript is uploaded to PlayFab.
+- [access_policy_updated](PlayerProfile/access-policy-updated.md)  
+  This event is triggered when an access policy is updated.
 
-- [title_api_settings_changed](title-api-settings-changed.md)  
-  This event is triggered when an API Features setting is changed for the title.
+- [avatar_url_updated](PlayerProfile/avatar-url-updated.md)  
+  This event is triggered when an avatar URL is updated.
 
-- [title_catalog_updated](title-catalog-updated.md)  
-  This event is triggered when a catalog is changed.
+- [contact_email_updated](PlayerProfile/contact-email-updated.md)  
+  This event is triggered when a contact email is updated.
 
-- [title_client_rate_limited_alert](title-client-rate-limited-alert.md)  
-  This event is triggered when a single IP address generates too many API calls to PlayFab and is throttled.
+- [files_changed](PlayerProfile/files-changed.md)  
+  This event is triggered when files are changed.
 
-- [title_completed_task](title-completed-task.md)  
-  This event is triggered when a scheduled task has completed
+- [language_updated](PlayerProfile/language-updated.md)  
+  This event is triggered when a language setting is updated.
 
-- [title_created_task](title-created-task.md)  
-  This event is triggered when a task is created.
+- [objects_updated](PlayerProfile/objects-updated.md)  
+  This event is triggered when objects are updated.
 
-- [title_deleted](title-deleted.md)  
-  This event is triggered when a game title is deleted.
+## PlayStream
 
-- [title_deleted_task](title-deleted-task.md)  
-  This event is triggered when a task is deleted.
+- [action_executed](PlayStream/action-executed.md)  
+  This event is emitted when an action is executed.
 
-- [title_exceeded_limit](title-exceeded-limit.md)  
-  This event is triggererd when a title exceeds a service limit and receives an error.
+- [action_failed](PlayStream/action-failed.md)  
+  This event is emitted when an action failed to execute.
 
-- [title_high_error_rate_alert](title-high-error-rate-alert.md)  
-  This event is triggered when a game title experiences a high rate of errors.
+## Segmentation
 
-- [title_initiated_player_password_reset](title-initiated-player-password-reset.md)  
-  This event is triggered when a title initiates the account recovery process for a player.
+- [segment_entered](Segmentation/segment-entered.md)  
+  This event is triggered when a profile enters a segment.
 
-- [title_limit_changed](title-limit-changed.md)  
-  This event is triggered when a title changes a service limit.
+- [segment_exited](Segmentation/segment-exited.md)  
+  This event is triggered when a profile exits a segment.
 
-- [title_news_updated](title-news-updated.md)  
-  This event is triggered when a title news is created or updated.
+- [api_operation](Segmentation/api-operation.md)  
+  This event is triggered to summarize the actions taken during an invocation of the segmentation CRUD API.
 
-- [title_permission_policy_changed](title-permission-policy-changed.md)  
-  This event is triggered when an update occurs to a a title's permission policies.
+## Session
 
-- [title_profile_view_constraints_changed](title-profile-view-constraints-changed.md)  
-  This event is triggered when a profile view constraint is changed for the title.
+- [client_focus_change](Session/client-focus-change.md)  
+  This event is triggered every time the application enters or exits focus on the player's device.
 
-- [title_published_cloudscript](title-published-cloudscript.md)  
-  An inactive revision of CloudScript has been made into the active 'live' version.
+- [client_session_start](Session/client-session-start.md)  
+  This event is triggered when a new client session starts.
 
-- [title_queue_config_updated](title-queue-config-updated.md)  
-  This event is triggered when a queue config is changed.
+## Title
 
-- [title_requested_limit_change](title-requested-limit-change.md)  
+- [title_client_rate_limited_alert](Title/title-client-rate-limited-alert.md)  
+  This event is triggered when a single IP address generates too many API calls to PlayFab and is throttled.
+
+- [title_high_error_rate_alert](Title/title-high-error-rate-alert.md)  
+  This event is triggered when a game title experiences a high rate of errors.
+
+- [title_requested_limit_change](Title/title-requested-limit-change.md)  
   This event is triggered when a title requests a service limit change.
 
-- [title_saved_survey](title-saved-survey.md)  
+- [title_saved_survey](Title/title-saved-survey.md)  
   This event is triggered when a game's survey is saved.
 
-- [title_scheduled_cloudscript_executed](title-scheduled-cloudscript-executed.md)  
-  This event is triggered when a CloudScript function is run by a scheduled task.  
+## TitleData
+
+- [title_news_updated](TitleData/title-news-updated.md)  
+  This event is triggered when a title news is created or updated.
 
-- [title_secret_key_changed](title-secret-key-changed.md)  
+- [title_secret_key_changed](TitleData/title-secret-key-changed.md)  
   This event is triggered when a title adds or updates a Secret Key
 
-- [title_started_task](title-started-task.md)  
-  This event is triggered when a task is scheduled to run.
+- [title_activated](TitleData/title-activated.md)  
+  This event is triggered when a title is activated.
 
-- [title_statistic_version_changed](title-statistic-version-changed.md)  
-  This event is triggered when the version of a statistic changes, causing its leaderboard to reset.
+- [title_data_override_deleted](TitleData/title-data-override-deleted.md)  
+  This event is triggered when a title data override is deleted.
 
-- [title_store_updated](title-store-updated.md)  
-  This event is triggered when a store is changed.
+- [title_data_updated](TitleData/title-data-updated.md)  
+  This event is triggered when title data is updated.
 
-- [title_updated_task](title-updated-task.md)  
-  This event is triggered when a task is updated.
+- [title_deactivated](TitleData/title-deactivated.md)  
+  This event is triggered when a title is deactivated.
+
+## TargetedConfiguration
+
+- [player_churn_prediction_changed](TargetedConfiguration/player-churn-prediction-changed.md)  
+  This event is triggered when a player's churn prediction is changed.
 
 ## Statistics
 
-- [statistic_updated](statistic-updated.md)  
+- [statistic_updated](Statistics/statistic-updated.md)  
   This event is triggered when a statistic is updated.
 
 ## Leaderboards
 
-- [leaderboard_version_ended](leaderboard-version-ended.md)  
+- [character_statistic_changed](Leaderboards/character-statistic-changed.md)  
+  This event is triggered when a character statistic is changed.  
+
+- [character_statistic_deleted](Leaderboards/character-statistic-deleted.md)  
+  This event is triggered when a character statistic is deleted.  
+
+- [entity_rank_on_leaderboard_version_ended](Leaderboards/entity-rank-on-leaderboard-version-ended.md)  
   This event is triggered when a leaderboard version is reset
 
-- [entity_rank_on_leaderboard_version_ended](entity-rank-on-leaderboard-version-ended.md)  
+- [leaderboard_version_ended](Leaderboards/leaderboard-version-ended.md)  
   This event is triggered when a leaderboard version is reset
+
+- [player_ranked_on_leaderboard_version](Leaderboards/player-ranked-on-leaderboard-version.md)  
+  This event is triggered when a leaderboard version changes, generating events for top‑ranked players up to the limit defined by the "Leaderboard version change top rank events sent" setting.
+
+- [player_statistic_changed](Leaderboards/player-statistic-changed.md)  
+  This event is triggered when a player statistic is changed.
+
+- [player_statistic_deleted](Leaderboards/player-statistic-deleted.md)  
+  This event is triggered when a player statistic is deleted.
+
+- [title_statistic_version_changed](Leaderboards/title-statistic-version-changed.md)  
+  This event is triggered when the version of a statistic changes, causing its leaderboard to reset.
+
+- [title_statistic_deleted](Leaderboards/title-statistic-deleted.md)  
+  This event is triggered when a title statistic is deleted.
diff --git a/playfab-docs/api-references/events/item-created.md b/playfab-docs/api-references/events/item-created.md
deleted file mode 100644
index 8e4f50bf2..000000000
--- a/playfab-docs/api-references/events/item-created.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: item_created
-author: fprotti96
-description: ItemCreated event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# item_created
-
-This event is triggered when an item is created.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ItemId|String|The string of the item that was created.|
-|ItemType|String|The string type of the item that was created.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"item_created"|
-|EventNamespace|String|"playfab.catalog"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/item-deleted.md b/playfab-docs/api-references/events/item-deleted.md
deleted file mode 100644
index c41bfa6a2..000000000
--- a/playfab-docs/api-references/events/item-deleted.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: item_deleted
-author: fprotti96
-description: ItemDeleted event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# item_deleted
-
-This event is triggered when an item is deleted.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ItemId|String|The string ID of the item that was deleted.|
-|ItemType|String|The string type of the item that was deleted.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"item_deleted"|
-|EventNamespace|String|"playfab.catalog"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/item-moderation-state-changed.md b/playfab-docs/api-references/events/item-moderation-state-changed.md
deleted file mode 100644
index 388a59382..000000000
--- a/playfab-docs/api-references/events/item-moderation-state-changed.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: item_moderation_state_changed
-author: fprotti96
-description: ItemModerationStateChanged event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# item_moderation_state_changed
-
-This event is triggered when an item moderation state is changed.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ItemId|String|The string ID of the item whos state was changed.|
-|TargetStatus|String|The updated moderation status of the item.|
-|Reason|String|The current stated reason for the associated item being moderated.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"tem_moderation_state_changed"|
-|EventNamespace|String|"playfab.catalog"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/item-publish-requested.md b/playfab-docs/api-references/events/item-publish-requested.md
deleted file mode 100644
index ccbbbccda..000000000
--- a/playfab-docs/api-references/events/item-publish-requested.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: item-publish-requested
-author: fprotti96
-description: ItemPublishRequested event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# item_publish_requested
-
-This event is triggered when an publishing is started.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ItemId|String|The string ID of the item that is to be published.|
-|ItemType|String|The string type of the item that is to be published.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"item_publish_requested"|
-|EventNamespace|String|"playfab.catalog"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/item-reported.md b/playfab-docs/api-references/events/item-reported.md
deleted file mode 100644
index 5fc0b6fcc..000000000
--- a/playfab-docs/api-references/events/item-reported.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: item_reported
-author: fprotti96
-description: ItemReported event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# item_reported
-
-This event is triggered when an item is reported.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ItemId|String|The string ID of the item that was reported.|
-|ItemType|String|The string type of the item that was reported.|
-|CreatorEntityKey|[EntityKey](data-types/entitykey.md)|The item's creator.|
-|ConcernCategory|String|The category for which this item was reported.|
-|Reason|String|The reason for which this item was reported.|
-
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"item_reported"|
-|EventNamespace|String|"playfab.catalog"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/item-updated.md b/playfab-docs/api-references/events/item-updated.md
deleted file mode 100644
index a4fe04de2..000000000
--- a/playfab-docs/api-references/events/item-updated.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: item_updated
-author: fprotti96
-description: ItemUpdated event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# item_updated
-
-This event is triggered when an item is updated.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ItemId|String|The string ID of the item that was updated.|
-|ItemType|String|The string type of the item that was updated.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"item_updated"|
-|EventNamespace|String|"playfab.catalog"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/items-added.md b/playfab-docs/api-references/events/items-added.md
deleted file mode 100644
index 9b943c2d9..000000000
--- a/playfab-docs/api-references/events/items-added.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: items_added
-author: fprotti96
-description: ItemsAdded event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# items_added
-
-Event raised when items have been added to an inventory.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|TransactionId|String|The transaction id.|
-|CollectionId|String|The collection id.|
-|ItemId|String|The item id.|
-|StackId|String|The stack id.|
-|Amount|int?|The amount of items that were added.|
-|DurationInSeconds|long?|The duration of the item that was added.|
-|ItemType|String|The type of the catalog item that was modified in the transaction.|
-|Balance|int?|The balance of the items changed as a result of the transaction.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"items_added"|
-|EventNamespace|String|"playfab.inventory"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/items-deleted.md b/playfab-docs/api-references/events/items-deleted.md
deleted file mode 100644
index 2499d290a..000000000
--- a/playfab-docs/api-references/events/items-deleted.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: items_deleted
-author: fprotti96
-description: ItemsDeleted event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# items_deleted
-
-Event raised when items have been deleted from an inventory.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|TransactionId|String|The transaction id.|
-|CollectionId|String|The collection id.|
-|ItemId|String|The item id.|
-|StackId|String|The stack id.|
-|ItemType|String|The type of the catalog item that was modified in the transaction.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"items_deleted"|
-|EventNamespace|String|"playfab.inventory"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/items-purchased.md b/playfab-docs/api-references/events/items-purchased.md
deleted file mode 100644
index 4cc777fd5..000000000
--- a/playfab-docs/api-references/events/items-purchased.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: items_purchased
-author: fprotti96
-description: ItemsPurchased event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# items_purchased
-
-Event raised when items have been purchased from an inventory.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|TransactionId|String|The transaction id.|
-|CollectionId|String|The collection id.|
-|ItemId|String|The item id.|
-|StackId|String|The stack id.|
-|Amount|int?|The amount of items that were puchased.|
-|DurationInSeconds|long?|The duration of the item that was purchased.|
-|SalePriceAmounts|List<[PurchasePriceAmount](data-types/purchasepriceamount.md)>|The per-item price amounts the item was purchased at.|
-|StoreId|String|The id of the Store the item was purchased from or null.|
-|ItemType|String|The type of the catalog item that was modified in the transaction.|
-|Balance|int?|The balance of the items changed as a result of the transaction.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"items_purchased"|
-|EventNamespace|String|"playfab.inventory"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/items-redeemed.md b/playfab-docs/api-references/events/items-redeemed.md
deleted file mode 100644
index a0e446086..000000000
--- a/playfab-docs/api-references/events/items-redeemed.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: items_redeemed
-author: fprotti96
-description: ItemsRedeemed event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# items_redeemed
-
-Event raised when items have been redeemed to an inventory.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|TransactionId|String|The transaction id.|
-|CollectionId|String|The collection id.|
-|ItemId|String|The item id.|
-|StackId|String|The stack id.|
-|Amount|int?|The amount of items that were redeemed.|
-|DurationInSeconds|long?|The duration of the item that was redeemed.|
-|Marketplace|String|The name of the marketplace that the items were redeemed from.|
-|MarketplaceTransactionId|String|The transaction id in the marketplace that the items were redeemed from.|
-|ItemType|String|The type of the catalog item that was modified in the transaction.|
-|Balance|int?|The balance of the items changed as a result of the transaction.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"items_redeemed"|
-|EventNamespace|String|"playfab.inventory"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/items-subtracted.md b/playfab-docs/api-references/events/items-subtracted.md
deleted file mode 100644
index 4413b7eb9..000000000
--- a/playfab-docs/api-references/events/items-subtracted.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: items_subtracted
-author: fprotti96
-description: ItemsSubtracted event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# items_subtracted
-
-Event raised when items have been subtracted from an inventory.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|TransactionId|String|The transaction id.|
-|CollectionId|String|The collection id.|
-|ItemId|String|The item id.|
-|StackId|String|The stack id.|
-|Amount|int?|The amount of items that were subtracted.|
-|DurationInSeconds|long?|The duration of the item that was subtracted.|
-|ItemType|String|The type of the catalog item that was modified in the transaction.|
-|Balance|int?|The balance of the items changed as a result of the transaction.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"items_subtracted"|
-|EventNamespace|String|"playfab.inventory"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/items-transferred.md b/playfab-docs/api-references/events/items-transferred.md
deleted file mode 100644
index 886e05720..000000000
--- a/playfab-docs/api-references/events/items-transferred.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: items_transferred
-author: fprotti96
-description: ItemsTransferred event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# items_transferred
-
-Event raised when items have been transferred to or from an inventory.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|TransactionId|String|The transaction id.|
-|CollectionId|String|The collection id.|
-|ItemId|String|The item id.|
-|StackId|String|The stack id.|
-|Amount|int?|The amount of items that were transferred.|
-|DurationInSeconds|long?|The duration of the item that was transferred.|
-|GivingEntity|[EntityKey](data-types/entitykey.md)?|The entity the items were transferred from or null if it was the current entity.|
-|ReceivingEntity|[EntityKey](data-types/entitykey.md)?|The entity the items were transferred to or null if it was the current entity.|
-|GivingCollectionId|String|The collection if the items were transferred from or null if it was the current collection.|
-|ReceivingCollectionId|String|The collection id the items were transferred to or null if it was the current collection.|
-|ItemType|String|The type of the catalog item that was modified in the transaction.|
-|Balance|int?|The balance of the items changed as a result of the transaction.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"items_transferred"|
-|EventNamespace|String|"playfab.inventory"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/items-updated.md b/playfab-docs/api-references/events/items-updated.md
deleted file mode 100644
index ea21edc3c..000000000
--- a/playfab-docs/api-references/events/items-updated.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: items_updated
-author: fprotti96
-description: ItemsUpdated event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# items_updated
-
-Event raised when items have been updated in an inventory.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|TransactionId|String|The transaction id.|
-|CollectionId|String|The collection id.|
-|ItemId|String|The item id.|
-|StackId|String|The stack id.|
-|Amount|int?|The amount of item.|
-|Expiration|String|The date the item expires.|
-|ItemType|String|The type of the catalog item that was modified in the transaction.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"items_updated"|
-|EventNamespace|String|"playfab.inventory"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/leaderboard-version-ended.md b/playfab-docs/api-references/events/leaderboard-version-ended.md
deleted file mode 100644
index 5f6f6d3ac..000000000
--- a/playfab-docs/api-references/events/leaderboard-version-ended.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: leaderboard_version_ended
-author: t-sandersg-gith
-description: leaderboard_version_ended event.
-ms.author: t-sandersg
-ms.date: 08/14/2025
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# leaderboard_version_ended
-
-This event is triggered when a leaderboard version is reset to a new version for a game title.
-
-## Properties
-
-| Name | Type | Description |
-| --- | --- | --- |
-| Name | String | The name of the leaderboard |
-| Version | int32 | The version of the leaderboard |
-| TimeStamp | DateTime | The time at which the leaderboard version was changed |
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"items_purchased"|
-|EventNamespace|String|"playfab.inventory"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/marketplace-transaction-redeemed.md b/playfab-docs/api-references/events/marketplace-transaction-redeemed.md
deleted file mode 100644
index 5690fefc9..000000000
--- a/playfab-docs/api-references/events/marketplace-transaction-redeemed.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: marketplace_transaction_redeemed
-author: fprotti96
-description: marketplace_transaction_redeemed event.
-ms.author: fprotti
-ms.date: 04/26/2024
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# marketplace_transaction_redeemed
-
-This event is triggered when a bundle or subscription has been redeemed to an inventory.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Marketplace|String|The name of the marketplace the items were redeemed from.|
-|MarketplaceTransctionId|String|The transaction Id from the marketplace the items were redeemed from.|
-|MarketplaceAlternateId|String|The alternate Id of the item for the marketplace.|
-|Amount|int?|The amount that was redeemed.|
-|DurationInSeconds|long?|The amount of subscription that was redeemed.|
-|ItemId|String|The identifier of the item that was redeemed.|
-|ItemType|String|The type of the catalog item that was redeemed.|
-|RealMoneyPrices|Dictionary<string, int>|The multi-currency unit price, in real money, of the item that was redeemed. The property is a dictionary where the key is the three-letter currency code as defined in ISO 4217, and the value is the currency amount in the smallest unit (for example, cents, pence) in accordance with ISO 4217. Only United States Dollar (USD) is currently supported. Example: If the product price in USD is $1.39, the dictionary entry would be: ["USD"] = 139;|
-
-## Common properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties.
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (such as title and player) to which this event applies.|
-|EntityType|String|The type of entity (such as player and title) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like **com.mygame.guild**) as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: **com.myprogram.ads**|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
diff --git a/playfab-docs/api-references/events/matchmaking-match-found.md b/playfab-docs/api-references/events/matchmaking-match-found.md
deleted file mode 100644
index b4c560961..000000000
--- a/playfab-docs/api-references/events/matchmaking-match-found.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: matchmaking_match_found
-author: joannaleecy
-description: matchmaking_match_found event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# matchmaking_match_found
-
-This event is triggered when a group of tickets are matched together.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|Payload|[MatchmakingMatchFoundPayload](data-types/matchmakingmatchfoundpayload.md)|Payload that this entity is a child of.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
diff --git a/playfab-docs/api-references/events/matchmaking-ticket-completed.md b/playfab-docs/api-references/events/matchmaking-ticket-completed.md
deleted file mode 100644
index 628961d66..000000000
--- a/playfab-docs/api-references/events/matchmaking-ticket-completed.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: matchmaking_ticket_completed
-author: joannaleecy
-description: matchmaking_ticket_completed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# matchmaking_ticket_completed
-
-This event is triggered when a matchmaking ticket reaches a completion state.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|Payload|[MatchmakingTicketCompletePayload](data-types/matchmakingticketcompletepayload.md)|Payload that this entity is a child of.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/matchmaking-user-ticket-completed.md b/playfab-docs/api-references/events/matchmaking-user-ticket-completed.md
deleted file mode 100644
index 0a924fdb6..000000000
--- a/playfab-docs/api-references/events/matchmaking-user-ticket-completed.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: matchmaking_user_ticket_completed 
-author: joannaleecy
-description: matchmaking_user_ticket_completed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# matchmaking_user_ticket_completed 
-
-This event is triggered when a matchmaking ticket reaches a completion state. This event is sent to each of the users in the completed ticket
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|Payload|[MatchmakingUserTicketCompletePayload](data-types/matchmakinguserticketcompletepayload.md)|Payload that this entity is a child of.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
diff --git a/playfab-docs/api-references/events/matchmaking-user-ticket-invite.md b/playfab-docs/api-references/events/matchmaking-user-ticket-invite.md
deleted file mode 100644
index b1c10ebcc..000000000
--- a/playfab-docs/api-references/events/matchmaking-user-ticket-invite.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: matchmaking_user_ticket_invite  
-author: joannaleecy
-description: matchmaking_user_ticket_invite event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# matchmaking_user_ticket_invite  
-
-This event is triggered when a ticket with an invited user is created. The event will be sent to the invited user.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|Payload|[MatchmakingUserTicketInvitePayload](data-types/matchmakinguserticketinvitepayload.md)|Payload that this entity is a child of.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
diff --git a/playfab-docs/api-references/events/multiplayer-server-build-deleted.md b/playfab-docs/api-references/events/multiplayer-server-build-deleted.md
deleted file mode 100644
index 9871653e3..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-build-deleted.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: multiplayer_server_build_deleted 
-author: joannaleecy
-description: multiplayer_server_build_deleted event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_build_deleted
-
-This event is triggered when a multiplayer server build is deleted.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerBuildDeletedEventPayload](data-types/multiplayerserverbuilddeletedeventpayload.md)|The multiplayer server build region deleted event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
diff --git a/playfab-docs/api-references/events/multiplayer-server-build-region-status-changed.md b/playfab-docs/api-references/events/multiplayer-server-build-region-status-changed.md
deleted file mode 100644
index ece9c11ce..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-build-region-status-changed.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: multiplayer_server_build_region_status_changed 
-author: joannaleecy
-description: multiplayer_server_build_region_status_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_build_region_status_changed 
-
-This event is triggered when a multiplayer server's build region status is changed.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerBuildRegionStatusChangedEventPayload](data-types/multiplayerserverbuildregionstatuschangedeventpayload.md)|The multiplayer server build region status changed event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
diff --git a/playfab-docs/api-references/events/multiplayer-server-build-region-updated.md b/playfab-docs/api-references/events/multiplayer-server-build-region-updated.md
deleted file mode 100644
index 049fc51ec..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-build-region-updated.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: multiplayer_server_build_region_updated 
-author: joannaleecy
-description: multiplayer_server_build_region_updated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_build_region_updated
-
-This event is triggered when a multiplayer server build region is updated.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerBuildRegionUpdatedEventPayload](data-types/multiplayerserverbuildregionupdatedeventpayload.md)|The multiplayer server build region updated event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
diff --git a/playfab-docs/api-references/events/multiplayer-server-certificate-deleted.md b/playfab-docs/api-references/events/multiplayer-server-certificate-deleted.md
deleted file mode 100644
index 3c3b36856..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-certificate-deleted.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: multiplayer_server_certificate_deleted 
-author: joannaleecy
-description: multiplayer_server_certificate_deleted event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_certificate_deleted
-
-This event is triggered when a multiplayer server certificate is deleted.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerCertificateDeletedEventPayload](data-types/multiplayerservercertificatedeletedeventpayload.md)|The multiplayer server certificate deleted event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/multiplayer-server-certificate-uploaded.md b/playfab-docs/api-references/events/multiplayer-server-certificate-uploaded.md
deleted file mode 100644
index f7a797151..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-certificate-uploaded.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: multiplayer_server_certificate_uploaded
-author: joannaleecy
-description: multiplayer_server_certificate_uploaded event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_certificate_uploaded
-
-This event is triggered when a multiplayer server certificate is uploaded.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerCertificateUploadedEventPayload](data-types/multiplayerservercertificateuploadedeventpayload.md)|The multiplayer server certificate uploaded event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
diff --git a/playfab-docs/api-references/events/multiplayer-server-create-build-initiated.md b/playfab-docs/api-references/events/multiplayer-server-create-build-initiated.md
deleted file mode 100644
index c0065eeda..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-create-build-initiated.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: multiplayer_server_create_build_initiated
-author: joannaleecy
-description: multiplayer_server_create_build_initiated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_create_build_initiated
-
-This event is triggered when a multiplayer server build is initiated.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerCreateBuildInitiatedEventPayload](data-types/multiplayerservercreatebuildinitiatedeventpayload.md)|The multiplayer server create build initiated event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
diff --git a/playfab-docs/api-references/events/multiplayer-server-game-asset-deleted.md b/playfab-docs/api-references/events/multiplayer-server-game-asset-deleted.md
deleted file mode 100644
index dcbbecbdd..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-game-asset-deleted.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: multiplayer_server_game_asset_deleted
-author: joannaleecy
-description: multiplayer_server_game_asset_deleted event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_game_asset_deleted
-
-This event is triggered when a multiplayer server game asset is deleted.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerGameAssetDeletedEventPayload](data-types/multiplayerservergameassetdeletedeventpayload.md)|The multiplayer server game asset deleted event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
diff --git a/playfab-docs/api-references/events/multiplayer-server-requested.md b/playfab-docs/api-references/events/multiplayer-server-requested.md
deleted file mode 100644
index 30a437724..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-requested.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: multiplayer_server_requested
-author: joannaleecy
-description: multiplayer_server_requested event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_requested
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerRequestedEventPayload](data-types/multiplayerserverrequestedeventpayload.md)|The multiplayer server requested event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
-
-
diff --git a/playfab-docs/api-references/events/multiplayer-server-state-changed.md b/playfab-docs/api-references/events/multiplayer-server-state-changed.md
deleted file mode 100644
index 5750987f8..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-state-changed.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: multiplayer_server_state_changed
-author: joannaleecy
-description: multiplayer_server_state_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_state_changed
-
-This event is triggered when a multiplayer server's state is changed.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerStateChangedEventPayload](data-types/multiplayerserverstatechangedeventpayload.md)|The multiplayer server state changed event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/multiplayer-server-vm-assigned.md b/playfab-docs/api-references/events/multiplayer-server-vm-assigned.md
deleted file mode 100644
index 7f68abd32..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-vm-assigned.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: multiplayer_server_vm_assigned
-author: joannaleecy
-description: multiplayer_server_vm_assigned event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_vm_assigned
-
-This event is triggered when a virtual machine is assigned to a multiplayer server build.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerVmAssignedEventPayload](data-types/multiplayerservervmassignedeventpayload.md)|The multiplayer server virtual machine assigned event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/multiplayer-server-vm-remote-user-created.md b/playfab-docs/api-references/events/multiplayer-server-vm-remote-user-created.md
deleted file mode 100644
index 032231d44..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-vm-remote-user-created.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: multiplayer_server_vm_remote_user_created
-author: joannaleecy
-description: multiplayer_server_vm_remote_user_created event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_vm_remote_user_created
-
-This event is triggered when a multiplayer server virtual machine remote user is created.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerVmRemoteUserCreatedEventPayload](data-types/multiplayerservervmremoteusercreatedeventpayload.md)|The multiplayer server virtual machine remote user created event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/multiplayer-server-vm-remote-user-deleted.md b/playfab-docs/api-references/events/multiplayer-server-vm-remote-user-deleted.md
deleted file mode 100644
index 7040e3064..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-vm-remote-user-deleted.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: multiplayer_server_vm_remote_user_deleted
-author: joannaleecy
-description: multiplayer_server_vm_remote_user_deleted event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_vm_remote_user_deleted
-
-This event is triggered when a multiplayer server virtual machine remote user is deleted.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerVmRemoteUserDeletedEventPayload](data-types/multiplayerservervmremoteuserdeletedeventpayload.md)|The multiplayer server virtual machine remote user deleted event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/multiplayer-server-vm-unassignment-started.md b/playfab-docs/api-references/events/multiplayer-server-vm-unassignment-started.md
deleted file mode 100644
index 415967b86..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-vm-unassignment-started.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: multiplayer_server_vm_unassignment_started
-author: joannaleecy
-description: multiplayer_server_vm_unassignment_started event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_vm_unassignment_started
-
-This event is triggered when a virtual machine is unassigned from a multiplayer server build.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerVmUnassignmentStartedEventPayload](data-types/multiplayerservervmunassignmentstartedeventpayload.md)|The multiplayer server virtual machine unassignment started event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/multiplayer-server-vm-unhealthy.md b/playfab-docs/api-references/events/multiplayer-server-vm-unhealthy.md
deleted file mode 100644
index 4a0244945..000000000
--- a/playfab-docs/api-references/events/multiplayer-server-vm-unhealthy.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: multiplayer_server_vm_unhealthy
-author: joannaleecy
-description: multiplayer_server_vm_unhealthy event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# multiplayer_server_vm_unhealthy
-
-This event is triggered when a virtual machine is found to be unhealthy.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-|OriginalEventId|String|The original unique identifier associated with this event before it was posted to PlayFab. The value might differ from the EventId value, which is assigned when the event is received by the server.|
-|OriginalTimestamp|DateTime|The original time (in UTC) associated with this event before it was posted to PlayFab. The value might differ from the Timestamp value, which is set at the time the event is received by the server.|
-|Payload|[MultiplayerServerVmUnhealthyEventPayload](data-types/multiplayerservervmunhealthyeventpayload.md)|The multiplayer server virtual machine unassignment started event payload.|
-|WriterEntity|[EntityKey](data-types/entitykey.md)|Entity that wrote this event, included only if different than the event's entity.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-action-executed.md b/playfab-docs/api-references/events/player-action-executed.md
deleted file mode 100644
index bb22dc707..000000000
--- a/playfab-docs/api-references/events/player-action-executed.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: player_action_executed
-author: joannaleecy
-description: player_action_executed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_action_executed
-
-This event is triggered when an action linked to a segmentation change or event rule executes on a player.
-
-Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ActionName|String|Name of the action that was triggered.|
-|Error|[ActionExecutionError](data-types/actionexecutionerror.md)|Information about the error that occurred during execution, if it failed to complete.|
-|ExecutionDuration|double|Action execution time in milliseconds.|
-|ExecutionResult|object|The object returned from the action execution, if it completed.|
-|ScheduledTimestamp|DateTime|Time that the action was scheduled for execution.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|TriggeredTimestamp|DateTime|Time that the triggering event or segmentation change occurred.|
-|TriggeringEventRuleMatch|[EventRuleMatch](data-types/eventrulematch.md)|Event rule match, if any, that triggered the action.|
-|TriggeringSegmentMembershipChange|[SegmentMembershipChange](data-types/segmentmembershipchange.md)|Player segmentation change, if any, that triggered the action.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-ad-activity-valued.md b/playfab-docs/api-references/events/player-ad-activity-valued.md
deleted file mode 100644
index ce0e6d6e2..000000000
--- a/playfab-docs/api-references/events/player-ad-activity-valued.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: player_ad_activity_valued
-author: joannaleecy
-description: player_ad_activity_valued event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_ad_activity_valued
-
-Event triggered when reported value of ad view is recorded
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AdPlacementId|String|Id of the placement|
-|AdPlacementName|String|Name of the placement|
-|AdUnit|String|Ad unit type|
-|RevenueShare|double|Share of the revenue for this ad view (calculated as total revenue for placement divided by total views for that placement in that time window)|
-|RewardId|String|Id of the reward|
-|RewardName|String|Name of the reward|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-ad-campaign-attribution.md b/playfab-docs/api-references/events/player-ad-campaign-attribution.md
deleted file mode 100644
index 46972b2c8..000000000
--- a/playfab-docs/api-references/events/player-ad-campaign-attribution.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: player_ad_campaign_attribution
-author: joannaleecy
-description: player_ad_campaign_attribution event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_ad_campaign_attribution
-
-This event is triggered by an attribution tracking Add-on when a player is matched to a paid acquisition campaign.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CampaignId|String|The ID of the campaign, as passed in by the attribution provider.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-ad-closed.md b/playfab-docs/api-references/events/player-ad-closed.md
deleted file mode 100644
index 626aff6d9..000000000
--- a/playfab-docs/api-references/events/player-ad-closed.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: player_ad_closed
-author: joannaleecy
-description: player_ad_closed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_ad_closed
-
-This event is triggered when a player closes an ad.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AdPlacementId|String|Id of the placement|
-|AdPlacementName|String|Name of the placement|
-|AdUnit|String|Ad unit type|
-|RewardId|String|Id of the reward|
-|RewardName|String|Name of the reward|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-ad-ended.md b/playfab-docs/api-references/events/player-ad-ended.md
deleted file mode 100644
index 75b605939..000000000
--- a/playfab-docs/api-references/events/player-ad-ended.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: player_ad_ended
-author: joannaleecy
-description: player_ad_ended event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_ad_ended
-
-This event is triggered when a player finishes an ad.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AdPlacementId|String|Id of the placement|
-|AdPlacementName|String|Name of the placement|
-|AdUnit|String|Ad unit type|
-|RewardId|String|Id of the reward|
-|RewardName|String|Name of the reward|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-ad-opened.md b/playfab-docs/api-references/events/player-ad-opened.md
deleted file mode 100644
index d7d920f63..000000000
--- a/playfab-docs/api-references/events/player-ad-opened.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: player_ad_opened
-author: joannaleecy
-description: player_ad_opened event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_ad_opened
-
-This event is triggered when a player opens an ad.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AdPlacementId|String|Id of the placement|
-|AdPlacementName|String|Name of the placement|
-|AdUnit|String|Ad unit type|
-|RewardId|String|Id of the reward|
-|RewardName|String|Name of the reward|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-ad-rewarded.md b/playfab-docs/api-references/events/player-ad-rewarded.md
deleted file mode 100644
index 453325d00..000000000
--- a/playfab-docs/api-references/events/player-ad-rewarded.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: player_ad_rewarded
-author: joannaleecy
-description: player_ad_rewarded event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_ad_rewarded
-
-This event is triggered when a player recieves an ad reward.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ActionGroupDebugMessages|[]|Debug messages from the reward actions|
-|AdPlacementId|String|Id of the placement|
-|AdPlacementName|String|Name of the placement|
-|AdUnit|String|Ad unit type|
-|RewardId|String|Id of the reward|
-|RewardName|String|Name of the reward|
-|TitleId|String|The ID of the title to which this player event applies.|
-|ViewsRemainingThisPeriod|int32|Views this player has remaining for the placement's window, if applicable|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-ad-started.md b/playfab-docs/api-references/events/player-ad-started.md
deleted file mode 100644
index add24300e..000000000
--- a/playfab-docs/api-references/events/player-ad-started.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: player_ad_started
-author: joannaleecy
-description: player_ad_started event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_ad_started
-
-This event is triggered when a player starts an ad.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AdPlacementId|String|Id of the placement|
-|AdPlacementName|String|Name of the placement|
-|AdUnit|String|Ad unit type|
-|RewardId|String|Id of the reward|
-|RewardName|String|Name of the reward|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-added-title.md b/playfab-docs/api-references/events/player-added-title.md
deleted file mode 100644
index f128034b1..000000000
--- a/playfab-docs/api-references/events/player-added-title.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: player_added_title
-author: joannaleecy
-description: player_added_title event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_added_title
-
-This event is triggered when a player creates a new account for a title. Note: this event is triggered once per title rather than once per publisher.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DisplayName|String|Player's display name when they added this title.|
-|Platform|[LoginIdentityProvider](data-types/loginidentityprovider.md)|Authentication method used to register player's account.|
-|PlatformUserId|String|Unique ID for the player's account associated with the Origination authentication method.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-banned.md b/playfab-docs/api-references/events/player-banned.md
deleted file mode 100644
index 40f8b69e1..000000000
--- a/playfab-docs/api-references/events/player-banned.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: player_banned
-author: joannaleecy
-description: player_banned event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_banned
-
-This event is triggered when a player is banned.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|BanExpiration|DateTime|When the ban expires. The value is null if the ban is permanent.|
-|BanId|String|ID of the ban. Useful for tracking unique bans, if the player has been banned before.|
-|BanReason|String|The reason why the player was banned.|
-|PermanentBan|Boolean|Whether this ban is permanent.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-changed-avatar.md b/playfab-docs/api-references/events/player-changed-avatar.md
deleted file mode 100644
index 036e59076..000000000
--- a/playfab-docs/api-references/events/player-changed-avatar.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_changed_avatar
-author: joannaleecy
-description: player_changed_avatar event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_changed_avatar
-
-This event is triggered when a player's avatar URL is changed.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ImageUrl|String|URL of the avatar image.|
-|PreviousImageUrl|String|Previous URL of the avatar image.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-completed-password-reset.md b/playfab-docs/api-references/events/player-completed-password-reset.md
deleted file mode 100644
index 83d212481..000000000
--- a/playfab-docs/api-references/events/player-completed-password-reset.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: player_completed_password_reset
-author: joannaleecy
-description: player_completed_password_reset event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_completed_password_reset
-
-This event is triggered when a player completes the password reset process by visiting the link URL that was sent to them and choosing a new password.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CompletedFromIPAddress|String|IP address from which the password reset process was completed.|
-|CompletionTimestamp|DateTime|When the password reset process was completed.|
-|InitiatedBy|[PasswordResetInitiationSource](data-types/passwordresetinitiationsource.md)|Source that initiated the password reset process.|
-|InitiatedFromIPAddress|String|IP address from which the password reset process was initiated.|
-|InitiationTimestamp|DateTime|When the password reset process was initiated.|
-|LinkExpiration|DateTime|Expiration time for the password reset link.|
-|PasswordResetId|String|Unique identifier for the password reset link. This cannot be used to complete the reset.|
-|RecoveryEmailAddress|String|Email address to which the password reset link was sent.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-consumed-item.md b/playfab-docs/api-references/events/player-consumed-item.md
deleted file mode 100644
index b3aa4fcda..000000000
--- a/playfab-docs/api-references/events/player-consumed-item.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: player_consumed_item
-author: joannaleecy
-description: player_consumed_item event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_consumed_item
-
-This event is triggered when a player consumes an item from their inventory.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CatalogVersion|String|Version of the catalog from which the consumed inventory item was created.|
-|ItemId|String|ID of the catalog item from which the consumed inventory item was created. This can be used to look up the item from the catalog.|
-|ItemInstanceId|String|The specific ID of the item that was consumed.|
-|PreviousUsesRemaining|uint32|For multiple use items, the number of uses that remained before the item was consumed.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|UsesRemaining|uint32|For multiple use items, the number of uses remaining after the item was consumed.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-created.md b/playfab-docs/api-references/events/player-created.md
deleted file mode 100644
index 83d7d4197..000000000
--- a/playfab-docs/api-references/events/player-created.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_created
-author: joannaleecy
-description: player_created event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_created
-
-This event is triggered when a player account is created for the first time. Note: this event is only triggered once per publisher, not once per title.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Created|DateTime|When the player account was created.|
-|PublisherId|String|Unique ID for the publisher account under which this player account is created.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-data-exported.md b/playfab-docs/api-references/events/player-data-exported.md
deleted file mode 100644
index 0250cc535..000000000
--- a/playfab-docs/api-references/events/player-data-exported.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: player_data_exported
-author: joannaleecy
-description: player_data_exported event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_data_exported
-
-This event is triggered when a player's data is exported.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ExportDownloadUrl|String|URL to download the export.|
-|JobReceiptId|String|Receipt ID of the export job. This should correspond to the receipt ID returned by the export API call.|
-|RequestTime|DateTime|The time of export request.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-device-info.md b/playfab-docs/api-references/events/player-device-info.md
deleted file mode 100644
index ef5fc87b0..000000000
--- a/playfab-docs/api-references/events/player-device-info.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: player_device_info
-author: joannaleecy
-description: player_device_info event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_device_info
-
-This event is triggered once after the player logs in based on the settings for your title.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeviceInfo|Object||
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-display-name-filtered.md b/playfab-docs/api-references/events/player-display-name-filtered.md
deleted file mode 100644
index d31e81661..000000000
--- a/playfab-docs/api-references/events/player-display-name-filtered.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: player_display_name_filtered
-author: joannaleecy
-description: player_display_name_filtered event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_display_name_filtered
-
-This event is triggered when a display name is filtered by community sift only if there is an associated player EntityId for the event.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DisplayName|String|Value of the display name that was filtered|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-displayname-changed.md b/playfab-docs/api-references/events/player-displayname-changed.md
deleted file mode 100644
index 17bdbd85c..000000000
--- a/playfab-docs/api-references/events/player-displayname-changed.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_displayname_changed
-author: joannaleecy
-description: player_displayname_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_displayname_changed
-
-This event is triggered when a player's display name is changed.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DisplayName|String|New display name after the change.|
-|PreviousDisplayName|String|Previous display name before the change.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-executed-cloudscript.md b/playfab-docs/api-references/events/player-executed-cloudscript.md
deleted file mode 100644
index 71e1778ce..000000000
--- a/playfab-docs/api-references/events/player-executed-cloudscript.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_executed_cloudscript
-author: joannaleecy
-description: player_executed_cloudscript event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_executed_cloudscript
-
-This event is optionally triggered when a CloudScript function is executed, either by calling the ExecuteCloudScript API with the GeneratePlayStreamEvent option or triggered by a PlayStream event action with the 'Publish results as a PlayStream Event' box checked.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CloudScriptExecutionResult|[ExecuteCloudScriptResult](data-types/executecloudscriptresult.md)|Result of the CloudScript function, including diagnostic information that is useful for debugging.|
-|FunctionName|String|Name of the CloudScript function that was called.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-inventory-item-added.md b/playfab-docs/api-references/events/player-inventory-item-added.md
deleted file mode 100644
index c719d6049..000000000
--- a/playfab-docs/api-references/events/player-inventory-item-added.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: player_inventory_item_added
-author: joannaleecy
-description: player_inventory_item_added event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_inventory_item_added
-
-This event is triggered when an item is granted to a player.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Annotation|String|Optional details about the inventory item.|
-|BundleContents|[]|Catalog item IDs of any other items granted to the player along with this one as part of a bundle.|
-|CatalogVersion|String|Catalog version in which the item that was added is defined.|
-|Class|String|Class of the item that was added.|
-|CouponCode|String|Redeemed coupon (if any) that granted the item.|
-|DisplayName|String|Display name of the item that was added.|
-|Expiration|DateTime|When the item expires. The value is null if the item does not expire.|
-|InstanceId|String|Unique instance ID of the inventory item that was added.|
-|ItemId|String|Catalog item ID of the inventory item that was added.|
-|RemainingUses|uint32|How many uses the item has, if it has a limited number of uses.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-linked-account.md b/playfab-docs/api-references/events/player-linked-account.md
deleted file mode 100644
index 75147cb6b..000000000
--- a/playfab-docs/api-references/events/player-linked-account.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: player_linked_account
-author: joannaleecy
-description: player_linked_account event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_linked_account
-
-This event is triggered when a new authentication method is linked to a player's account.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Email|String|Player's email linked with the given provider|
-|Origination|[LoginIdentityProvider](data-types/loginidentityprovider.md)|Authentication method being linked to a player's account.|
-|OriginationUserId|String|Player's identity under authentication method being linked to player's account.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|Username|String|Player's username linked with the given provider|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-logged-in.md b/playfab-docs/api-references/events/player-logged-in.md
deleted file mode 100644
index fa2b19cf9..000000000
--- a/playfab-docs/api-references/events/player-logged-in.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: player_logged_in
-author: joannaleecy
-description: player_logged_in event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_logged_in
-
-This event is triggered when a player logs in.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Location|[EventLocation](data-types/eventlocation.md)|Player's geographic location, if known. Location is estimated from factors such as IP address and is not always available or accurate.|
-|Platform|[LoginIdentityProvider](data-types/loginidentityprovider.md)|Authentication method used to login the player.|
-|PlatformUserId|String|Player's identity under the authentication method used to login the player.|
-|PlatformUserName|String|The display name that's set in the identity provider that the player is authenticated with.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-paid-for-purchase.md b/playfab-docs/api-references/events/player-paid-for-purchase.md
deleted file mode 100644
index b6fd32bd3..000000000
--- a/playfab-docs/api-references/events/player-paid-for-purchase.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: player_paid_for_purchase
-author: joannaleecy
-description: player_paid_for_purchase event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_paid_for_purchase
-
-This event is triggered when the second step of the payment process completes, paying for the purchase.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|OrderId|String|Purchase order identifier.|
-|ProviderData|String|Provider used for the transaction.|
-|ProviderName|String|Payment provider to use to fund the purchase.|
-|ProviderToken|String|A token generated by the provider to authenticate the request (provider-specific).|
-|PurchaseConfirmationPageURL|String|URL to the purchase provider page that details the purchase.|
-|PurchaseCurrency|String|Currency for the transaction, may be a virtual currency or real money.|
-|PurchasePrice|uint32|Cost of the transaction.|
-|Status|[TransactionStatus](data-types/transactionstatus.md)|Status of the transaction.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|VirtualCurrencyBalances|Object|Current virtual currency balances for the user.|
-|VirtualCurrencyGrants|Object|Virtual currencies granted by the transaction, if any.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-password-reset-link-sent.md b/playfab-docs/api-references/events/player-password-reset-link-sent.md
deleted file mode 100644
index 162a629f8..000000000
--- a/playfab-docs/api-references/events/player-password-reset-link-sent.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: player_password_reset_link_sent
-author: joannaleecy
-description: player_password_reset_link_sent event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_password_reset_link_sent
-
-This event is triggered when a player is sent a link to reset their password.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|InitiatedBy|[PasswordResetInitiationSource](data-types/passwordresetinitiationsource.md)|Source that initiated the password reset process.|
-|InitiatedFromIPAddress|String|IP address from which the password reset process was initiated.|
-|LinkExpiration|DateTime|Expiration time for the password reset link.|
-|PasswordResetId|String|Unique identifier for the password reset link. This cannot be used to complete the reset.|
-|RecoveryEmailAddress|String|Email address to which the password reset link was sent.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-photon-session-authenticated.md b/playfab-docs/api-references/events/player-photon-session-authenticated.md
deleted file mode 100644
index 214ae0e69..000000000
--- a/playfab-docs/api-references/events/player-photon-session-authenticated.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_photon_session_authenticated
-author: joannaleecy
-description: player_photon_session_authenticated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_photon_session_authenticated
-
-This event is triggered when a player connects to a Photon Cloud application and authenticates with PlayFab using Photon custom authentication.
-
-Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|PhotonApplicationId|String|Unique identifier of the Photon Cloud application to which the player is connected|
-|PhotonApplicationType|[PhotonServicesEnum](data-types/photonservicesenum.md)|Type of Photon Cloud application to which the player is connected|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-ranked-on-leaderboard-version.md b/playfab-docs/api-references/events/player-ranked-on-leaderboard-version.md
deleted file mode 100644
index 879e3be6c..000000000
--- a/playfab-docs/api-references/events/player-ranked-on-leaderboard-version.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: player_ranked_on_leaderboard_version
-author: joannaleecy
-description: player_ranked_on_leaderboard_version event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_ranked_on_leaderboard_version
-
-This event is triggered for the top-ranked players on a leaderboard when the leaderboard version changes (e.g. when a leaderboard statistic version is incremented). The maximum number of leaderboard entries for which the event is generated is controlled by the "Leaderboard version change top rank events sent" title limit.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|LeaderboardSource|[LeaderboardSource](data-types/leaderboardsource.md)|Source of the values for the leaderboard.|
-|Rank|uint32|Player's rank on the leaderboard.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|Value|int32|Player's leaderboard value.|
-|Version|uint32|Version of the leaderboard on which the player is ranked. For player statistic leaderboards, this matches the version of the statistic.|
-|VersionChangeBehavior|[LeaderboardVersionChangeBehavior](data-types/leaderboardversionchangebehavior.md)|Behavior with respect to the leaderboard values when the version changed.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-realmoney-purchase.md b/playfab-docs/api-references/events/player-realmoney-purchase.md
deleted file mode 100644
index b244930f6..000000000
--- a/playfab-docs/api-references/events/player-realmoney-purchase.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: player_realmoney_purchase
-author: joannaleecy
-description: player_realmoney_purchase event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_realmoney_purchase
-
-This event is triggered when a player makes a real money purchase, and generates revenue for the game.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|OrderId|String|Unique identifier of the order.|
-|OrderTotal|uint32|Total value of the purchase in the system currency (defaults to USD).|
-|PaymentProvider|String|Payment provider used to make the purchase.|
-|PaymentType|[PaymentType](data-types/paymenttype.md)|Type of payment used to make the purchase.|
-|PurchasedProduct|[]|The ItemIds from the catalog of the purchased items, if applicable.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|TransactionCurrency|[Currency](data-types/currency.md)|Local currency used to make the purchase, if applicable.|
-|TransactionId|String|Unique identifier of the transaction.|
-|TransactionTotal|uint32|Total value of the purchase in the local currency used to make the purchase, if applicable.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-receipt-validation.md b/playfab-docs/api-references/events/player-receipt-validation.md
deleted file mode 100644
index d7dfcab6f..000000000
--- a/playfab-docs/api-references/events/player-receipt-validation.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: player_receipt_validation
-author: joannaleecy
-description: player_receipt_validation event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_receipt_validation
-
-This event is triggered when a player attempts to make a real money purchase and the purchase receipt is being validated.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Error|String|The error that occurred during a receipt validation.|
-|PaymentProvider|String|Payment provider used to make the purchase attempt.|
-|PaymentType|[PaymentType](data-types/paymenttype.md)|Type of payment used to make the purchase attempt.|
-|ReceiptContent|String|The receipt data during a real money purchase event attempt.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|Valid|Boolean|Indicates if the receipt is valid.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-redeemed-coupon.md b/playfab-docs/api-references/events/player-redeemed-coupon.md
deleted file mode 100644
index 1dccbeb9c..000000000
--- a/playfab-docs/api-references/events/player-redeemed-coupon.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_redeemed_coupon
-author: joannaleecy
-description: player_redeemed_coupon event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_redeemed_coupon
-
-This event is triggered when a player redeems a coupon.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CouponCode|String|Coupon code the player redeemed.|
-|GrantedInventoryItems|[CouponGrantedInventoryItem](data-types/coupongrantedinventoryitem.md)|Items added to the player's inventory by redeeming the coupon.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-registered-push-notifications.md b/playfab-docs/api-references/events/player-registered-push-notifications.md
deleted file mode 100644
index fc91dfa49..000000000
--- a/playfab-docs/api-references/events/player-registered-push-notifications.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_registered_push_notifications
-author: joannaleecy
-description: player_registered_push_notifications event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_registered_push_notifications
-
-This event is triggered when a player registers for push notifications.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeviceToken|String|Unique device token registered for push notifications.|
-|Platform|[PushNotificationPlatform](data-types/pushnotificationplatform.md)|Platform on which the player is registering for push notifications.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-removed-title.md b/playfab-docs/api-references/events/player-removed-title.md
deleted file mode 100644
index 9f9880c55..000000000
--- a/playfab-docs/api-references/events/player-removed-title.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: player_removed_title
-author: joannaleecy
-description: player_removed_title event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_removed_title
-
-This event is triggered when a player account for a title is removed. Note: this event is triggered once per title rather than once per publisher.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-reported-as-abusive.md b/playfab-docs/api-references/events/player-reported-as-abusive.md
deleted file mode 100644
index 27ccae2fc..000000000
--- a/playfab-docs/api-references/events/player-reported-as-abusive.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_reported_as_abusive
-author: joannaleecy
-description: player_reported_as_abusive event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_reported_as_abusive
-
-This event is triggered when a player is reported by another player as abusive.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Comment|String|Comment submitted by the player who made the report.|
-|ReportedByPlayer|String|Player ID of the player who made the report.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-set-profile-property.md b/playfab-docs/api-references/events/player-set-profile-property.md
deleted file mode 100644
index c3af40086..000000000
--- a/playfab-docs/api-references/events/player-set-profile-property.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_set_profile_property
-author: joannaleecy
-description: player_set_profile_property event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_set_profile_property
-
-This event is triggered when PlayFab makes an internal adjustment to a player profile.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Property|[PlayerProfileProperty](data-types/playerprofileproperty.md)|Property of the profile to be set|
-|TitleId|String|The ID of the title to which this player event applies.|
-|Value|object|Value to set to|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-started-purchase.md b/playfab-docs/api-references/events/player-started-purchase.md
deleted file mode 100644
index 5a724bc8e..000000000
--- a/playfab-docs/api-references/events/player-started-purchase.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: player_started_purchase
-author: joannaleecy
-description: player_started_purchase event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_started_purchase
-
-This event is triggered when a player starts a purchase.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CatalogVersion|String|Catalog version for the items to be purchased. Defaults to most recent catalog.|
-|Contents|[CartItem](data-types/cartitem.md)|Cart items to be purchased.|
-|OrderId|String|Purchase order identifier.|
-|StoreId|String|Store through which to purchase items. If not set, prices will be pulled from the catalog itself.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-statistic-changed.md b/playfab-docs/api-references/events/player-statistic-changed.md
deleted file mode 100644
index befbfdc9f..000000000
--- a/playfab-docs/api-references/events/player-statistic-changed.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: player_statistic_changed
-author: joannaleecy
-description: player_statistic_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_statistic_changed
-
-This event is triggered when a player statistic is changed.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AggregationMethod|[StatisticAggregationMethod](data-types/statisticaggregationmethod.md)|Aggregation method applied for calculating the new value of the statistic.|
-|StatisticId|uint32|Unique ID of the statistic that changed.|
-|StatisticName|String|Name of the statistic that changed.|
-|StatisticPreviousValue|int32|Old value of the statistic, before the change.|
-|StatisticValue|int32|New value of the statistic, after the change.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|Version|uint32|Version of the statistic that changed. This is relevant for statistics that reset, since each time the statistic resets the version increments.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-statistic-deleted.md b/playfab-docs/api-references/events/player-statistic-deleted.md
deleted file mode 100644
index dae5187aa..000000000
--- a/playfab-docs/api-references/events/player-statistic-deleted.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: player_statistic_deleted
-author: joannaleecy
-description: player_statistic_deleted event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_statistic_deleted
-
-This event is triggered when a player statistic is deleted.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|StatisticId|uint32|Unique ID of the statistic that was deleted.|
-|StatisticName|String|Name of the statistic that was deleted.|
-|StatisticPreviousValue|int32|Old value of the statistic, before being deleted.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|Version|uint32|Version of the statistic. This is relevant for statistics that reset, since each time the statistic resets the version increments.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-tag-added.md b/playfab-docs/api-references/events/player-tag-added.md
deleted file mode 100644
index eb7d9f58f..000000000
--- a/playfab-docs/api-references/events/player-tag-added.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_tag_added
-author: joannaleecy
-description: player_tag_added event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_tag_added
-
-This event is triggered when a tag is added to a player profile.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Namespace|String|Namespace for this tag|
-|TagName|String|Name of the tag that is added.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-tag-removed.md b/playfab-docs/api-references/events/player-tag-removed.md
deleted file mode 100644
index 377e3886a..000000000
--- a/playfab-docs/api-references/events/player-tag-removed.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_tag_removed
-author: joannaleecy
-description: player_tag_removed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_tag_removed
-
-This event is triggered when a tag is removed from a player profile.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Namespace|String|Namespace for this tag|
-|TagName|String|Name of the tag that is removed.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-triggered-action-executed-cloudscript.md b/playfab-docs/api-references/events/player-triggered-action-executed-cloudscript.md
deleted file mode 100644
index a72dbe173..000000000
--- a/playfab-docs/api-references/events/player-triggered-action-executed-cloudscript.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: player_triggered_action_executed_cloudscript
-author: joannaleecy
-description: player_triggered_action_executed_cloudscript event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_triggered_action_executed_cloudscript
-
-This event is triggered when a CloudScript function is run as the result of a PlayStream action, and the 'Publish results as a PlayStream Event' box was checked.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CloudScriptExecutionResult|[ExecuteCloudScriptResult](data-types/executecloudscriptresult.md)|Result of the CloudScript function, including an error information. Useful for debugging.|
-|FunctionName|String|Name of the CloudScript function that was called.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|TriggeringEventData|object|The full JSON data of the event that triggered this CloudScript function to run. Useful for debugging.|
-|TriggeringEventName|String|Name of the event that triggered this CloudScript function to run.|
-|TriggeringPlayer|[PlayerProfile](data-types/playerprofile.md)|JSON data profile of the player that triggered this CloudScript function to run.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-unlinked-account.md b/playfab-docs/api-references/events/player-unlinked-account.md
deleted file mode 100644
index 2341570f7..000000000
--- a/playfab-docs/api-references/events/player-unlinked-account.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_unlinked_account
-author: joannaleecy
-description: player_unlinked_account event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_unlinked_account
-
-This event is triggered when an authentication method is unlinked from a player's account.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Origination|[LoginIdentityProvider](data-types/loginidentityprovider.md)|Authentication method being unlinked from a player's account.|
-|OriginationUserId|String|Player's identity under authentication method being unlinked from player's account.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-updated-contact-email.md b/playfab-docs/api-references/events/player-updated-contact-email.md
deleted file mode 100644
index 9e0a48510..000000000
--- a/playfab-docs/api-references/events/player-updated-contact-email.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: player_updated_contact_email
-author: joannaleecy
-description: player_updated_contact_email event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_updated_contact_email
-
-This event is triggered when a player updates a contact email on their profile.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EmailName|String|The name of the contact email that was updated or added in the player's profile.|
-|NewEmailAddress|String|The contact email updated or added in the player's profile.|
-|PreviousEmailAddress|String|The previous contact email updated in the player's profile.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-vc-item-purchased.md b/playfab-docs/api-references/events/player-vc-item-purchased.md
deleted file mode 100644
index 0d6c0ad25..000000000
--- a/playfab-docs/api-references/events/player-vc-item-purchased.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: player_vc_item_purchased
-author: joannaleecy
-description: player_vc_item_purchased event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_vc_item_purchased
-
-This event is triggered when the player makes a purchase using virtual currency.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CatalogVersion|String|Version of the catalog from which the item was purchased.|
-|CurrencyCode|String|Currency that was used to purchase the item.|
-|ItemId|String|Identifier of the catalog item that was purchased.|
-|PurchaseId|String|Unique identifier of the purchase transaction.|
-|Quantity|int32|Quantity of items that were purchased.|
-|StoreId|String|The StoreId where the item was purchased.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|UnitPrice|uint32|Price paid per item, expressed in the virtual currency.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-verified-contact-email.md b/playfab-docs/api-references/events/player-verified-contact-email.md
deleted file mode 100644
index 6dc84d36f..000000000
--- a/playfab-docs/api-references/events/player-verified-contact-email.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: player_verified_contact_email
-author: joannaleecy
-description: player_verified_contact_email event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_verified_contact_email
-
-This event is triggered when a contact email is verified for a player.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EmailAddress|String|The email address of the player's contact email that was verified.|
-|EmailName|String|The name of the player's contact email that was verified.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/player-virtual-currency-balance-changed.md b/playfab-docs/api-references/events/player-virtual-currency-balance-changed.md
deleted file mode 100644
index 040e347e0..000000000
--- a/playfab-docs/api-references/events/player-virtual-currency-balance-changed.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: player_virtual_currency_balance_changed
-author: joannaleecy
-description: player_virtual_currency_balance_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# player_virtual_currency_balance_changed
-
-This event is triggered when a player's virtual currency balance changes.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|OrderId|String|Id of the order that triggered the balance changes|
-|TitleId|String|The ID of the title to which this player event applies.|
-|VirtualCurrencyBalance|int32|New virtual currency balance after the change.|
-|VirtualCurrencyName|String|Virtual currency whose balance changed.|
-|VirtualCurrencyPreviousBalance|int32|Old virtual currency balance before the change.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/review-reported.md b/playfab-docs/api-references/events/review-reported.md
deleted file mode 100644
index f381e5a28..000000000
--- a/playfab-docs/api-references/events/review-reported.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: review_reported
-author: fprotti96
-description: ReviewReported event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# review_reported
-
-This event is triggered when a review is reported.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ItemId|String|The string ID of the item associated with the review.|
-|ReviewId|String|The string ID of the review being reported.|
-|ConcernCategory|String|The category for which this review was reported.|
-|Reason|String|The string reason for this report.|
-|CreatorEntityKey|[EntityKey](data-types/entitykey.md)|The EntityKey of the creator of the review that was reported.|
-
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"review_reported"|
-|EventNamespace|String|"playfab.catalog"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/reviews-takedown-requested.md b/playfab-docs/api-references/events/reviews-takedown-requested.md
deleted file mode 100644
index 62966a3a3..000000000
--- a/playfab-docs/api-references/events/reviews-takedown-requested.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: reviews_takedown_requested
-author: fprotti96
-description: ReviewsTakedownRequested event.
-ms.author: fprotti
-ms.date: 09/29/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# reviews_takedown_requested
-
-Event trigged when a takedown of reviews is requested.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Reviews|List<[ReviewTakedown](data-types/review-takedown.md)>|The reviews to be taken down.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|"reviews_takedown_requested"|
-|EventNamespace|String|"playfab.catalog"|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/sent-email.md b/playfab-docs/api-references/events/sent-email.md
deleted file mode 100644
index ce0008772..000000000
--- a/playfab-docs/api-references/events/sent-email.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: sent_email
-author: joannaleecy
-description: sent_email event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# sent_email
-
-This event is triggered when an email is sent or fails to send to a player.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Body|String|The content of the email body, truncated to 4096 characters.|
-|EmailName|String|The name of the player's contact email the email was sent to.|
-|EmailTemplateId|String|The email template id during a send email attempt.|
-|EmailTemplateName|String|The email template name during a send email attempt.|
-|EmailTemplateType|[EmailTemplateType](data-types/emailtemplatetype.md)|The email template type during a send email attempt.|
-|ErrorMessage|String|The error that occurred if an email failed to send.|
-|ErrorName|String|The name of the error that occurred if an email failed to send.|
-|Language|String|The language the email was sent in|
-|Subject|String|The content of the email subject, truncated to 1024 characters.|
-|Success|Boolean|Indicates if the email was successfully sent.|
-|TitleId|String|The ID of the title to which this player event applies.|
-|Token|String|The auth token included in the sent email as part of a confirmation URL.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/sent-push-notification.md b/playfab-docs/api-references/events/sent-push-notification.md
deleted file mode 100644
index a990fbd6f..000000000
--- a/playfab-docs/api-references/events/sent-push-notification.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: sent_push_notification
-author: joannaleecy
-description: sent_push_notification event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# sent_push_notification
-
-This event is triggered when a push notification is sent or fails to be sent to a player.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Body|String|The content of the push notification body, truncated to 4096 characters.|
-|ErrorMessage|String|The error that occurred if the push notification failed to be sent.|
-|ErrorName|String|The name of the error that occurred if the push notification failed to be sent.|
-|Language|String|The language the push notification was sent in if a matching localized template was used.|
-|PushNotificationTemplateId|String|The push notification template id during a send push notification attempt.|
-|PushNotificationTemplateName|String|The push notification template name during a send push notification attempt.|
-|Subject|String|The content of the push notification subject, truncated to 1024 characters.|
-|Success|Boolean|Indicates whether the push notification was successfully sent.|
-|TitleId|String|The ID of the title to which this player event applies.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/statistic-updated.md b/playfab-docs/api-references/events/statistic-updated.md
deleted file mode 100644
index c9b35dff4..000000000
--- a/playfab-docs/api-references/events/statistic-updated.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: statistic_updated
-author: t-sandersg-gith
-description: statistic_updated event
-ms.author: t-sandersg
-ms.date: 8/18/2025
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# statistic_updated
-
-This event is triggered when a statistic is updated for a given entity.
-
-## Properties
-
-| Name | Type | Description |
-| --- | --- | --- |
-| Name | String | The name of the statistic |
-| Version | int32 | The version of the statistic |
-| Scores | int64[] | The current scores for the statistic, after the change |
-| PreviousScores | int64[] | The previous scores for the statistic, before the change |
-| Metadata | String | The metadata associated with the statistic, after the change |
-| PreviousMetadata | String | The metadata associated with the statistic, before the change |
-| Operation | String | The operation that was performed: `Created`, `Updated`, or `Deleted` |
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/studio-created.md b/playfab-docs/api-references/events/studio-created.md
deleted file mode 100644
index 72a361834..000000000
--- a/playfab-docs/api-references/events/studio-created.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: studio_created
-author: joannaleecy
-description: studio_created event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# studio_created
-
-This event is triggered when a studio is created.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CreatorAuthenticationId|String|Authentication provider's id for the user who created the studio|
-|CreatorPlayFabId|String|PlayFab id of the user who created the studio|
-|StudioName|String|Name of the new studio|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/studio-tier-updated.md b/playfab-docs/api-references/events/studio-tier-updated.md
deleted file mode 100644
index 10cede10d..000000000
--- a/playfab-docs/api-references/events/studio-tier-updated.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: studio_tier_updated
-author: joannaleecy
-description: studio_tier_updated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# studio_tier_updated
-
-This event is triggered when a studio tier is updated.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ContactCompanyName|String|Contact Company Name|
-|IsPayAsYouGo|Boolean|IsPayAsYouGo PaymentOption|
-|IsReservedCapacity|Boolean|IsReservedCapacity PaymentOption|
-|IsReservedCapacityAnnual|Boolean|IsReservedCapacityAnnual PaymentOption|
-|MonthlyMinimumUSD|double|Monthly Minimum Price in USD|
-|OveragePricePerMauTiers|[PaymentOptionPerMauPriceTier](data-types/paymentoptionpermaupricetier.md)|OveragePricePerMauTiers Definitions|
-|PaymentSystemAccountId|String|Payment System AccountId|
-|PricePerMauTiers|[PaymentOptionPerMauPriceTier](data-types/paymentoptionpermaupricetier.md)|PricePerMauTiers Definitions|
-|ReservedMAU|int32|Reserved Capacity MAU|
-|StudioIds|IEnumerable_String|Studio Ids|
-|TierDisplayName|String|Tier Display Name|
-|TierId|String|Tier Id|
-|TransactionId|String|Transaction Id|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/studio-user-added.md b/playfab-docs/api-references/events/studio-user-added.md
deleted file mode 100644
index 5c58581a6..000000000
--- a/playfab-docs/api-references/events/studio-user-added.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: studio_user_added
-author: joannaleecy
-description: studio_user_added event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# studio_user_added
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AuthenticationId|String|Authentication provider's ID for this user|
-|AuthenticationProvider|[AuthenticationProvider](data-types/authenticationprovider.md)|Authentication provider for the user|
-|AuthenticationProviderId|String|Authentication provider entity id, if needed by the provider|
-|Email|String|User's email|
-|InvitationId|String|Id of the invitation record if user needed to register|
-|PlayFabId|String|PlayFab ID for this user|
-|StudioPermissions|[]|Array of studio permissions that were be granted to the user|
-|TitlePermissions|Object|Dictionary of title id, title permissions that were granted to the user|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/studio-user-invited.md b/playfab-docs/api-references/events/studio-user-invited.md
deleted file mode 100644
index 0133dc54a..000000000
--- a/playfab-docs/api-references/events/studio-user-invited.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: studio_user_invited
-author: joannaleecy
-description: studio_user_invited event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# studio_user_invited
-
-This event is triggererd when a user is invited to a studio.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AuthenticationProvider|[AuthenticationProvider](data-types/authenticationprovider.md)|Authentication provider type required for user to register with|
-|AuthenticationProviderId|String|Authentication provider entity id, if needed by the provider.|
-|Email|String|Email the invitation was sent to|
-|InvitationExpires|DateTime|Expiration of the invitation|
-|InvitationId|String|Id of the invitation if user needed to register|
-|InvitedExistingUser|Boolean|Indicates if the user invited already existed, if so no invitation record was created and the user was automatically attached|
-|InvitorPlayFabId|String|Identity of the user who created the invitation|
-|StudioPermissions|[]|Array of studio permissions which will be granted to the user when registering|
-|TitlePermissions|Object|Dictionary of title id, title permissions which will be granted to the user when registering|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/studio-user-removed.md b/playfab-docs/api-references/events/studio-user-removed.md
deleted file mode 100644
index 9bc47c94c..000000000
--- a/playfab-docs/api-references/events/studio-user-removed.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: studio_user_removed
-author: joannaleecy
-description: studio_user_removed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# studio_user_removed
-
-This event is triggered when a user is removed from a studio.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AuthenticationId|String|Authentication provider's ID for this user|
-|AuthenticationProvider|[AuthenticationProvider](data-types/authenticationprovider.md)|Authentication provider for the user|
-|AuthenticationProviderId|String|Authentication provider entity id, if needed by the provider|
-|PlayFabId|String|PlayFab ID for this user|
-|StudioPermissions|[]|Array of studio permissions that the user had|
-|TitlePermissions|Object|Dictionary of title id, title permissions that the user had|
-
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/tenancy-connector-onboard.md b/playfab-docs/api-references/events/tenancy-connector-onboard.md
deleted file mode 100644
index eb347e6b4..000000000
--- a/playfab-docs/api-references/events/tenancy-connector-onboard.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: tenancy_connector_onboard
-author: joannaleecy
-description: tenancy_connector_onboard event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# tenancy_connector_onboard
-
-This event is triggered when a tenancy connector is onboarded.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|EntityChain|String|The chain of ownership for this entity.|
-|EntityLineage|[EntityLineage](data-types/entitylineage.md)|Entities that this entity is a child of.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-aborted-task.md b/playfab-docs/api-references/events/title-aborted-task.md
deleted file mode 100644
index 199247ca3..000000000
--- a/playfab-docs/api-references/events/title-aborted-task.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: title_aborted_task
-author: joannaleecy
-description: title_aborted_task event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_aborted_task
-
-This event is triggered when a task instance is aborted.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|TaskInstanceId|String|ID of the aborted task instance|
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-added-cloudscript.md b/playfab-docs/api-references/events/title-added-cloudscript.md
deleted file mode 100644
index ae46e7de5..000000000
--- a/playfab-docs/api-references/events/title-added-cloudscript.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: title_added_cloudscript
-author: joannaleecy
-description: title_added_cloudscript event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_added_cloudscript
-
-This event is triggered when new CloudScript is uploaded to PlayFab.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|Published|Boolean|Whether the CloudScript that was uploaded is live.|
-|Revision|int32|Revision number of the CloudScript file that was added.|
-|ScriptNames|[]|Names of the individual script files modified. Currently this is just 'CloudScript.js' but later we will support multiple files.|
-|UserId|String||
-|Version|int32|Version number of the CloudScript file that was added.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-api-settings-changed.md b/playfab-docs/api-references/events/title-api-settings-changed.md
deleted file mode 100644
index d833ef143..000000000
--- a/playfab-docs/api-references/events/title-api-settings-changed.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: title_api_settings_changed
-author: joannaleecy
-description: title_api_settings_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_api_settings_changed
-
-This event is triggered when an API Features setting is changed for the title.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|PreviousSettingsValues|[APISettings](data-types/apisettings.md)|Settings values before the change.|
-|SettingsValues|[APISettings](data-types/apisettings.md)|Settings values after the change.|
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-catalog-updated.md b/playfab-docs/api-references/events/title-catalog-updated.md
deleted file mode 100644
index 391eeb1ae..000000000
--- a/playfab-docs/api-references/events/title-catalog-updated.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: title_catalog_updated
-author: joannaleecy
-description: title_catalog_updated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_catalog_updated
-
-This event is triggered when a catalog is changed.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CatalogVersion|String|Version of the catalog that was updated.|
-|Deleted|Boolean|Was the catalog deleted.|
-|DeveloperId|String||
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-client-rate-limited-alert.md b/playfab-docs/api-references/events/title-client-rate-limited-alert.md
deleted file mode 100644
index ac556030a..000000000
--- a/playfab-docs/api-references/events/title-client-rate-limited-alert.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: title_client_rate_limited_alert
-author: joannaleecy
-description: title_client_rate_limited_alert event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_client_rate_limited_alert
-
-This event is triggered when a single IP address generates too many API calls to PlayFab and is throttled.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AlertEventId|String|Unique identifier of the alert that triggered this event.|
-|AlertState|[AlertStates](data-types/alertstates.md)|State of the alert. Values include Triggered, Recovered, ReTriggered.|
-|API|String|The PlayFab API that was called too frequently.|
-|ErrorCode|String|Error message that was returned to the client.|
-|GraphUrl|String|URL of an image graph of the counter that triggered the alert.|
-|Level|[AlertLevel](data-types/alertlevel.md)|Level of the alert. Values include Warn, Alert, Critical.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-completed-task.md b/playfab-docs/api-references/events/title-completed-task.md
deleted file mode 100644
index 02b774b92..000000000
--- a/playfab-docs/api-references/events/title-completed-task.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: title_completed_task
-author: joannaleecy
-description: title_completed_task event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_completed_task
-
-This event is triggered when a scheduled task has completed
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AbortedAt|DateTime|Timestamp on when the task was aborted. Null if task never was aborted.|
-|IsAborted|Boolean|Whether the task was aborted.|
-|Result|[TaskInstanceStatus](data-types/taskinstancestatus.md)|Result of the task run, whether it has succeeded, failed or aborted.|
-|Summary|object|Summary of the task run. Different task types have different summary structure.|
-|TaskInstanceId|String|ID of the running instance of the task|
-|TaskType|String|Type of the scheduled task|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-created-task.md b/playfab-docs/api-references/events/title-created-task.md
deleted file mode 100644
index c322a4363..000000000
--- a/playfab-docs/api-references/events/title-created-task.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: title_created_task
-author: joannaleecy
-description: title_created_task event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_created_task
-
-This event is triggered when a task is created.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|ScheduledTask|[NameIdentifier](data-types/nameidentifier.md)|Identity of the scheduled task|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-deleted-master-player.md b/playfab-docs/api-references/events/title-deleted-master-player.md
deleted file mode 100644
index 8ea9bfcc1..000000000
--- a/playfab-docs/api-references/events/title-deleted-master-player.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: title_deleted_master_player
-author: joannaleecy
-description: title_deleted_master_player event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_deleted_master_player
-
-This event is triggered when a GDPR delete is finished.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|MetaData|String|Identifying information for title entered by developer.|
-|PlayerId|String|Master Player ID who was deleted.|
-|ReceiptId|String|Receipt ID of the delete that has been finished.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-deleted-task.md b/playfab-docs/api-references/events/title-deleted-task.md
deleted file mode 100644
index f35609a0c..000000000
--- a/playfab-docs/api-references/events/title-deleted-task.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: title_deleted_task
-author: joannaleecy
-description: title_deleted_task event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_deleted_task
-
-This event is triggered when a task is deleted.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|ScheduledTask|[NameIdentifier](data-types/nameidentifier.md)|Identity of the scheduled task|
-|UserId|String||
-
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-deleted.md b/playfab-docs/api-references/events/title-deleted.md
index 7dae3e639..39d5aba34 100644
--- a/playfab-docs/api-references/events/title-deleted.md
+++ b/playfab-docs/api-references/events/title-deleted.md
@@ -16,18 +16,4 @@ This event is triggered when a game title is deleted.
 
 ## Common Properties
 
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
+[!INCLUDE [common-properties](../../includes/_common-properties-eventsv1.md)]
diff --git a/playfab-docs/api-references/events/title-exceeded-limit.md b/playfab-docs/api-references/events/title-exceeded-limit.md
deleted file mode 100644
index e202620ef..000000000
--- a/playfab-docs/api-references/events/title-exceeded-limit.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: title_exceeded_limit
-author: joannaleecy
-description: title_exceeded_limit event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_exceeded_limit
-
-This event is triggererd when a title exceeds a service limit and receives an error.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Details|Object|Additional details about the exceeded limit|
-|LimitDisplayName|String|The display name of the limit that was exceeded.|
-|LimitId|String|The unique identifier of the limit that was exceeded.|
-|LimitValue|double|The limit value that was exceeded.|
-|Unit|[MetricUnit](data-types/metricunit.md)|The unit of the limit that was exceeded.|
-|Value|double|The value that exceeded the limit.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-high-error-rate-alert.md b/playfab-docs/api-references/events/title-high-error-rate-alert.md
deleted file mode 100644
index 39e6c7cd5..000000000
--- a/playfab-docs/api-references/events/title-high-error-rate-alert.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: title_high_error_rate_alert
-author: joannaleecy
-description: title_high_error_rate_alert event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_high_error_rate_alert
-
-This event is triggered when a game title experiences a high rate of errors.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|AlertEventId|String|Unique identifier of the alert that triggered this event.|
-|AlertState|[AlertStates](data-types/alertstates.md)|State of the alert. Values include Triggered, Recovered, ReTriggered.|
-|API|String|The PlayFab API that is generating the high rate of errors.|
-|ErrorCode|String|Error message that was returned to the client.|
-|GraphUrl|String|URL of an image graph of the counter that triggered the alert.|
-|Level|[AlertLevel](data-types/alertlevel.md)|Level of the alert. Values include Warn, Alert, Critical.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-initiated-player-password-reset.md b/playfab-docs/api-references/events/title-initiated-player-password-reset.md
deleted file mode 100644
index b350fff6b..000000000
--- a/playfab-docs/api-references/events/title-initiated-player-password-reset.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: title_initiated_player_password_reset
-author: joannaleecy
-description: title_initiated_player_password_reset event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_initiated_player_password_reset
-
-This event is triggered when a title initiates the account recovery process for a player.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|PasswordResetId|String|Unique identifier for the password reset link. This cannot be used to complete the reset.|
-|PlayerId|String|Player's account ID.|
-|PlayerRecoveryEmailAddress|String|Email address to which the account recovery email was sent.|
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-limit-changed.md b/playfab-docs/api-references/events/title-limit-changed.md
deleted file mode 100644
index aa58ef5bf..000000000
--- a/playfab-docs/api-references/events/title-limit-changed.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: title_limit_changed
-author: joannaleecy
-description: title_limit_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_limit_changed
-
-This event is triggered when a title changes a service limit.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|LimitDisplayName|String|The display name of the limit that changed.|
-|LimitId|String|The unique identifier of the limit that changed.|
-|PreviousPriceUSD|double|The price of the limit level in US Dollars before the change, if any.|
-|PreviousValue|double|The limit value before the change, if any.|
-|PriceUSD|double|The price of the limit level in US Dollars, if any.|
-|TransactionId|String|The unique identifier of the limit change transaction.|
-|Unit|[MetricUnit](data-types/metricunit.md)|The unit of the limit that changed.|
-|Value|double|The limit value after the change, if any.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-news-updated.md b/playfab-docs/api-references/events/title-news-updated.md
deleted file mode 100644
index e8a4d7c0d..000000000
--- a/playfab-docs/api-references/events/title-news-updated.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: title_news_updated
-author: joannaleecy
-description: title_news_updated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_news_updated
-
-This event is triggered when a title news is created or updated.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DateCreated|DateTime|When the title news was initially created.|
-|NewsId|String|Id of the news that is new or updated.|
-|NewsTitle|String|The current title of the news that is new or updated.|
-|Status|[NewsStatus](data-types/newsstatus.md)|The current status of the news that is new or updated.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-permission-policy-changed.md b/playfab-docs/api-references/events/title-permission-policy-changed.md
deleted file mode 100644
index 0e0addc01..000000000
--- a/playfab-docs/api-references/events/title-permission-policy-changed.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: title_permission_policy_changed
-author: joannaleecy
-description: title_permission_policy_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_permission_policy_changed
-
-This event is triggered when an update occurs to a a title's permission policies.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|NewPolicy|String|The contents new policy.|
-|PolicyName|String|The name of the policy that was changed|
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-profile-view-constraints-changed.md b/playfab-docs/api-references/events/title-profile-view-constraints-changed.md
deleted file mode 100644
index e8ddc6ba7..000000000
--- a/playfab-docs/api-references/events/title-profile-view-constraints-changed.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: title_profile_view_constraints_changed
-author: joannaleecy
-description: title_profile_view_constraints_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_profile_view_constraints_changed
-
-This event is triggered when a profile view constraint is changed for the title.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|PreviousProfileViewConstraints|String|Profile view constraints before the change as a JSON string.|
-|ProfileType|String|The profile type of the profile view constraints.|
-|ProfileViewConstraints|String|Profile view constraints after the change as a JSON string.|
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-published-cloudscript.md b/playfab-docs/api-references/events/title-published-cloudscript.md
deleted file mode 100644
index 8cd6c515f..000000000
--- a/playfab-docs/api-references/events/title-published-cloudscript.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: title_published_cloudscript
-author: joannaleecy
-description: title_published_cloudscript event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_published_cloudscript
-
-An inactive revision of CloudScript has been made into the active 'live' version.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|Revision|int32|Revision number of the CloudScript that was activated.|
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-queue-config-updated.md b/playfab-docs/api-references/events/title-queue-config-updated.md
deleted file mode 100644
index 3f2e8a888..000000000
--- a/playfab-docs/api-references/events/title-queue-config-updated.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: title_queue_config_updated
-author: joannaleecy
-description: title_queue_config_updated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_queue_config_updated
-
-This event is triggered when a queue config is changed.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Deleted|Boolean|Was the queue config deleted.|
-|DeveloperId|String||
-|MatchQueueName|String|Name of the queue config that was updated.|
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-requested-limit-change.md b/playfab-docs/api-references/events/title-requested-limit-change.md
deleted file mode 100644
index 0f35391fd..000000000
--- a/playfab-docs/api-references/events/title-requested-limit-change.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: title_requested_limit_change
-author: joannaleecy
-description: title_requested_limit_change event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_requested_limit_change
-
-This event is triggered when a title requests a service limit change.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|LevelName|String|The name of the requested limit level.|
-|LimitDisplayName|String|The display name of the limit requested to change.|
-|LimitId|String|The unique identifier of the limit requested to change.|
-|PreviousLevelName|String|The name of the limit level at the time of the requested change, if any.|
-|PreviousPriceUSD|double|The price of the limit level in US Dollars at the time of the requested change, if any.|
-|PreviousValue|double|The limit value at the time of the requested change, if any.|
-|PriceUSD|double|The price of the requested limit level in US Dollars, if any.|
-|TransactionId|String|The unique identifier of the requested limit change transaction.|
-|Unit|[MetricUnit](data-types/metricunit.md)|The unit of the limit requested to change.|
-|UserId|String||
-|Value|double|The limit value of the requested change, if any.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-saved-survey.md b/playfab-docs/api-references/events/title-saved-survey.md
deleted file mode 100644
index f5aae4c76..000000000
--- a/playfab-docs/api-references/events/title-saved-survey.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: title_saved_survey
-author: joannaleecy
-description: title_saved_survey event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_saved_survey
-
-This event is triggered when a game's survey is saved.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Genre|String|Title Genre|
-|Monetization|[]|Array of Monetization methods used by the Title|
-|Platforms|[]|Array of Platforms used by the Title|
-|PlayerModes|[]|Array of PlayerModes used by the Title|
-|TitleName|String|Name of the Title|
-|TitleWebsite|String|Website for the Title|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-scheduled-cloudscript-executed.md b/playfab-docs/api-references/events/title-scheduled-cloudscript-executed.md
deleted file mode 100644
index 58dd5bc5f..000000000
--- a/playfab-docs/api-references/events/title-scheduled-cloudscript-executed.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: title_scheduled_cloudscript_executed
-author: joannaleecy
-description: title_scheduled_cloudscript_executed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_scheduled_cloudscript_executed
-
-This event is triggered when a CloudScript function is run by a scheduled task.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CloudScriptExecutionResult|[ExecuteCloudScriptResult](data-types/executecloudscriptresult.md)|Result of the CloudScript function, including an error information. Useful for debugging.|
-|FunctionName|String|Name of the CloudScript function that was called.|
-|ScheduledTask|[NameId](data-types/nameid.md)|Scheduled task that called the CloudScript|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-secret-key-changed.md b/playfab-docs/api-references/events/title-secret-key-changed.md
deleted file mode 100644
index c7c9d7831..000000000
--- a/playfab-docs/api-references/events/title-secret-key-changed.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: title_secret_key_changed
-author: joannaleecy
-description: title_secret_key_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_secret_key_changed
-
-This event is triggered when a title adds or updates a Secret Key
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|Deleted|Boolean|Flag indicating if the key was deleted by this operation. Either true or null.|
-|DeveloperId|String||
-|Disabled|Boolean|Flag indicating if the key is disabled|
-|ExpiryDate|DateTime|Optional UTC date time that the secret key will expire at.|
-|SecretKeyId|String|Id of the secret key affected.|
-|SecretKeyName|String|Name of the secret key affected.|
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-started-task.md b/playfab-docs/api-references/events/title-started-task.md
deleted file mode 100644
index 16f5a3bf5..000000000
--- a/playfab-docs/api-references/events/title-started-task.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: title_started_task
-author: joannaleecy
-description: title_started_task event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_started_task
-
-This event is triggered when a task is scheduled to run.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|Parameter|object|Parameter of the scheduled task|
-|ScheduledByUserId|String|ID of user who manually scheduled the task, null if scheduled automatically|
-|ScheduledTask|[NameIdentifier](data-types/nameidentifier.md)|Identity of the scheduled task|
-|TaskInstanceId|String|ID of the running instance of the task|
-|TaskType|String|Type of the scheduled task|
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-statistic-version-changed.md b/playfab-docs/api-references/events/title-statistic-version-changed.md
deleted file mode 100644
index 8f0706151..000000000
--- a/playfab-docs/api-references/events/title-statistic-version-changed.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: title_statistic_version_changed
-author: joannaleecy
-description: title_statistic_version_changed event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_statistic_version_changed
-
-This event is triggered when the version of a statistic changes, causing its leaderboard to reset.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|ScheduledResetInterval|[StatisticResetIntervalOption](data-types/statisticresetintervaloption.md)|The interval on which the statistic leaderboard was configured to reset, if any.|
-|ScheduledResetTime|DateTime|The time at which the statistic leaderboard was configured to reset, if any.|
-|StatisticName|String|Unique name of the statistic.|
-|StatisticVersion|uint32|Version of the statistic, following the update.|
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-store-updated.md b/playfab-docs/api-references/events/title-store-updated.md
deleted file mode 100644
index d872b8d6b..000000000
--- a/playfab-docs/api-references/events/title-store-updated.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: title_store_updated
-author: joannaleecy
-description: title_store_updated event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_store_updated
-
-This event is triggered when a store is changed.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CatalogVersion|String|Catalog version that the updated store belongs to.|
-|Deleted|Boolean|Was the store deleted.|
-|DeveloperId|String||
-|StoreId|String|ID of the updated store.|
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/events/title-updated-task.md b/playfab-docs/api-references/events/title-updated-task.md
deleted file mode 100644
index 39a2b55a2..000000000
--- a/playfab-docs/api-references/events/title-updated-task.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: title_updated_task
-author: joannaleecy
-description: title_updated_task event.
-ms.author: jenelleb
-ms.date: 02/19/2019
-ms.topic: article
-ms.service: azure-playfab
-keywords: playfab, playstream events
-ms.localizationpriority: medium
----
-
-# title_updated_task
-
-This event is triggered when a task is updated.
-
-## Properties
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|DeveloperId|String||
-|HasRenamed|Boolean||
-|ScheduledTask|[NameIdentifier](data-types/nameidentifier.md)|Identity of the scheduled task|
-|UserId|String||
-
-## Common Properties
-
-All PlayStream events are formatted as JSON objects and share the following common properties:
-
-|Name|Type|Description|
-| :--------------------|:-------------------|:----------------------|
-|CustomTags|Object|Key-Value pair storage. Any provider of this event schema is allowed to send additional values in this property.|
-|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
-|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
-|EventId|String|PlayFab-assigned unique identifier for this event.|
-|EventName|String|The name of this event.|
-|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
-|History|[PlayStreamEventHistory](data-types/playstreameventhistory.md)|The history of events associated with this event. This is set in cases where an event has generated children events via a trigger action.|
-|Reserved|object|Reserved exclusively for PlayFab internal use.|
-|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
-|SourceType|[SourceType](data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
-|Timestamp|DateTime|The time (in UTC) associated with this event.|
diff --git a/playfab-docs/api-references/toc.yml b/playfab-docs/api-references/toc.yml
index b1afb264f..0e1c66245 100644
--- a/playfab-docs/api-references/toc.yml
+++ b/playfab-docs/api-references/toc.yml
@@ -4,8 +4,8 @@
     href: index.md
   - name: Reference
     href: /rest/api/playfab/admin/
-  - name: Real-time notifications for Lobby and Matchmaking
-    href: ../multiplayer/real-time-notifications/toc.yml
+  - name: Real-time messages for Lobby and Matchmaking
+    href: ../multiplayer/real-time-messages/toc.yml
 - name: Services C API
   href: c/toc.yml
 - name: Party C/C++ API
@@ -22,292 +22,507 @@
   items:
   - name: Model reference
     href: events/index.md
+  - name: AdPlacement
+    items:
+    - name: player_ad_closed
+      href: events/AdPlacement/player-ad-closed.md
+    - name: player_ad_ended
+      href: events/AdPlacement/player-ad-ended.md
+    - name: player_ad_opened
+      href: events/AdPlacement/player-ad-opened.md
+    - name: player_ad_rewarded
+      href: events/AdPlacement/player-ad-rewarded.md
+    - name: player_ad_started
+      href: events/AdPlacement/player-ad-started.md
+  - name: Addons
+    items:
+    - name: title_addon_changed
+      href: events/Addons/title-addon-changed.md
+  - name: ApiAccessPolicy
+    items:
+    - name: title_api_settings_changed
+      href: events/ApiAccessPolicy/title-api-settings-changed.md
+    - name: title_permission_policy_changed
+      href: events/ApiAccessPolicy/title-permission-policy-changed.md
+  - name: CloudScript
     items:
-    - name: auth_token_validated
-      href: events/auth-token-validated.md
-    - name: character_consumed_item    
-      href: events/character-consumed-item.md
-    - name: character_created
-      href: events/character-created.md
-    - name: character_inventory_item_added
-      href: events/character-inventory-item-added.md
-    - name: character_statistic_changed
-      href: events/character-statistic-changed.md
-    - name: character_statistic_deleted
-      href: events/character-statistic-deleted.md
-    - name: character_vc_item_purchased
-      href: events/character-vc-item-purchased.md
-    - name: character_virtual_currency_balance_changed
-      href: events/character-virtual-currency-balance-changed.md
-    - name: client_focus_change
-      href: events/client-focus-change.md
-    - name: client_session_start
-      href: events/client-session-start.md
-    - name: entity_created
-      href: events/entity-created.md
     - name: entity_executed_cloud_script
-      href: events/entity-executed-cloud-script.md
-    - name: entity_files_set
-      href: events/entity-files-set.md
-    - name: entity_language_updated
-      href: events/entity-language-updated.md
-    - name: entity_logged_in
-      href: events/entity-logged-in.md
-    - name: entity_objects_set
-      href: events/entity-objects-set.md
-    - name: entity_virtual_currency_balances_changed
-      href: events/entity-virtual-currency-balances-changed.md
+      href: events/CloudScript/entity-executed-cloud-script.md
+    - name: player_executed_cloudscript
+      href: events/CloudScript/player-executed-cloudscript.md
+    - name: player_triggered_action_executed_cloudscript
+      href: events/CloudScript/player-triggered-action-executed-cloudscript.md
+    - name: title_added_cloudscript
+      href: events/CloudScript/title-added-cloudscript.md
+    - name: title_published_cloudscript
+      href: events/CloudScript/title-published-cloudscript.md
+    - name: title_scheduled_cloudscript_executed
+      href: events/CloudScript/title-scheduled-cloudscript-executed.md
+    - name: cloudscript_executed
+      href: events/CloudScript/cloudscript-executed.md
+  - name: DeveloperIdentity
+    items:
+    - name: studio_created
+      href: events/DeveloperIdentity/studio-created.md
+    - name: studio_user_added
+      href: events/DeveloperIdentity/studio-user-added.md
+    - name: studio_user_invited
+      href: events/DeveloperIdentity/studio-user-invited.md
+    - name: studio_user_removed
+      href: events/DeveloperIdentity/studio-user-removed.md
+  - name: Extension
+    items:
+    - name: title_aborted_task
+      href: events/Extension/title-aborted-task.md
+    - name: title_completed_task
+      href: events/Extension/title-completed-task.md
+    - name: title_created_task
+      href: events/Extension/title-created-task.md
+    - name: title_deleted_task
+      href: events/Extension/title-deleted-task.md
+    - name: title_exceeded_limit
+      href: events/Extension/title-exceeded-limit.md
+    - name: title_limit_changed
+      href: events/Extension/title-limit-changed.md
+    - name: title_started_task
+      href: events/Extension/title-started-task.md
+    - name: title_updated_task
+      href: events/Extension/title-updated-task.md
+    - name: export_completed
+      href: events/Extension/export-completed.md
+  - name: Experimentation
+    items:
+    - name: exclusion_group_created
+      href: events/Experimentation/exclusion-group-created.md
+    - name: exclusion_group_deleted
+      href: events/Experimentation/exclusion-group-deleted.md
+    - name: exclusion_group_updated
+      href: events/Experimentation/exclusion-group-updated.md
+    - name: experiment_created
+      href: events/Experimentation/experiment-created.md
+    - name: experiment_deleted
+      href: events/Experimentation/experiment-deleted.md
+    - name: experiment_start_requested
+      href: events/Experimentation/experiment-start-requested.md
+    - name: experiment_stop_requested
+      href: events/Experimentation/experiment-stop-requested.md
+    - name: experiment_updated
+      href: events/Experimentation/experiment-updated.md
+    - name: player_experiment_variants_changed
+      href: events/Experimentation/player-experiment-variants-changed.md
+  - name: Functions
+    items:
+    - name: function_executed
+      href: events/Functions/function-executed.md
+    - name: function_registered
+      href: events/Functions/function-registered.md
+    - name: function_unregistered
+      href: events/Functions/function-unregistered.md
+    - name: player_triggered_action_executed_function
+      href: events/Functions/player-triggered-action-executed-function.md
+    - name: title_scheduled_function_executed
+      href: events/Functions/title-scheduled-function-executed.md
+  - name: Groups
+    items:
     - name: group_created
-      href: events/group-created.md
-    - name: group_deleted
-      href: events/group-deleted.md
+      href: events/Groups/group-created.md
     - name: group_members_added
-      href: events/group-members-added.md
+      href: events/Groups/group-members-added.md
     - name: group_members_removed
-      href: events/group-members-removed.md
+      href: events/Groups/group-members-removed.md
     - name: group_role_created
-      href: events/group-role-created.md
+      href: events/Groups/group-role-created.md
     - name: group_role_deleted
-      href: events/group-role-deleted.md
+      href: events/Groups/group-role-deleted.md
     - name: group_role_members_added
-      href: events/group-role-members-added.md
+      href: events/Groups/group-role-members-added.md
     - name: group_role_members_removed
-      href: events/group-role-members-removed.md
+      href: events/Groups/group-role-members-removed.md
     - name: group_role_updated
-      href: events/group-role-updated.md
+      href: events/Groups/group-role-updated.md
     - name: group_updated
-      href: events/group-updated.md
+      href: events/Groups/group-updated.md
+    - name: members_added
+      href: events/Groups/members-added.md
+    - name: members_removed
+      href: events/Groups/members-removed.md
+    - name: members_role_updated
+      href: events/Groups/members-role-updated.md
+    - name: player_updated_membership
+      href: events/Groups/player-updated-membership.md
+    - name: role_updated
+      href: events/Groups/role-updated.md
+  - name: Telemetry
+    items:
+    - name: apikey_activated
+      href: events/Telemetry/apikey-activated.md
+    - name: apikey_created
+      href: events/Telemetry/apikey-created.md
+    - name: apikey_deactivated
+      href: events/Telemetry/apikey-deactivated.md
+    - name: apikey_deleted
+      href: events/Telemetry/apikey-deleted.md
+  - name: TitleCommunications
+    items:
+    - name: player_registered_push_notifications
+      href: events/TitleCommunications/player-registered-push-notifications.md
+    - name: sent_email
+      href: events/TitleCommunications/sent-email.md
+    - name: sent_push_notification
+      href: events/TitleCommunications/sent-push-notification.md
+    - name: email_sent
+      href: events/TitleCommunications/email-sent.md
+    - name: push_notification_sent
+      href: events/TitleCommunications/push-notification-sent.md
+  - name: General
+    items:
+    - name: entity_virtual_currency_balances_changed
+      href: events/General/entity-virtual-currency-balances-changed.md
+    - name: tenancy_connector_onboard
+      href: events/General/tenancy-connector-onboard.md
+    - name: studio_tier_updated
+      href: events/General/studio-tier-updated.md
+  - name: Matchmaking
+    items:
+    - name: title_queue_config_updated
+      href: events/Matchmaking/title-queue-config-updated.md
+    - name: match_found
+      href: events/Matchmaking/match-found.md
+    - name: ticket_completed
+      href: events/Matchmaking/ticket-completed.md
+    - name: user_ticket_invited
+      href: events/Matchmaking/user-ticket-invited.md
+  - name: Multiplayer Servers
+    items:
+    - name: build_alias_created
+      href: events/MultiplayerServers/build-alias-created.md
+    - name: build_alias_deleted
+      href: events/MultiplayerServers/build-alias-deleted.md
+    - name: build_alias_updated
+      href: events/MultiplayerServers/build-alias-updated.md
+    - name: build_deleted
+      href: events/MultiplayerServers/build-deleted.md
+    - name: build_region_status_changed
+      href: events/MultiplayerServers/build-region-status-changed.md
+    - name: build_region_updated
+      href: events/MultiplayerServers/build-region-updated.md
+    - name: build_region_utilization
+      href: events/MultiplayerServers/build-region-utilization.md
+    - name: certificate_deleted
+      href: events/MultiplayerServers/certificate-deleted.md
+    - name: certificate_uploaded
+      href: events/MultiplayerServers/certificate-uploaded.md
+    - name: crash_detected
+      href: events/MultiplayerServers/crash-detected.md
+    - name: create_build_initiated
+      href: events/MultiplayerServers/create-build-initiated.md
+    - name: enabled_for_title
+      href: events/MultiplayerServers/enabled-for-title.md
+    - name: game_asset_deleted
+      href: events/MultiplayerServers/game-asset-deleted.md
+    - name: monitoring_output_saved
+      href: events/MultiplayerServers/monitoring-output-saved.md
+    - name: secret_added
+      href: events/MultiplayerServers/secret-added.md
+    - name: secret_deleted
+      href: events/MultiplayerServers/secret-deleted.md
+    - name: server_requested
+      href: events/MultiplayerServers/server-requested.md
+    - name: server_state_changed
+      href: events/MultiplayerServers/server-state-changed.md
+    - name: vm_assigned
+      href: events/MultiplayerServers/vm-assigned.md
+    - name: vm_game_certificates_deployed
+      href: events/MultiplayerServers/vm-game-certificates-deployed.md
+    - name: vm_remote_user_created
+      href: events/MultiplayerServers/vm-remote-user-created.md
+    - name: vm_remote_user_deleted
+      href: events/MultiplayerServers/vm-remote-user-deleted.md
+    - name: vm_state_change
+      href: events/MultiplayerServers/vm-state-change.md
+    - name: vm_unassignment_started
+      href: events/MultiplayerServers/vm-unassignment-started.md
+    - name: vm_unhealthy
+      href: events/MultiplayerServers/vm-unhealthy.md
+  - name: CatalogV1
+    items:
+    - name: title_catalog_updated
+      href: events/CatalogV1/title-catalog-updated.md
+    - name: title_store_updated
+      href: events/CatalogV1/title-store-updated.md
+  - name: CatalogV2
+    items:
     - name: item_created
-      href: events/item-created.md
+      href: events/CatalogV2/item-created.md
     - name: item_deleted
-      href: events/item-deleted.md
+      href: events/CatalogV2/item-deleted.md
     - name: item_moderation_state_changed
-      href: events/item-moderation-state-changed.md
+      href: events/CatalogV2/item-moderation-state-changed.md
     - name: item_publish_requested
-      href: events/item-publish-requested.md
+      href: events/CatalogV2/item-publish-requested.md
     - name: item_reported
-      href: events/item-reported.md
+      href: events/CatalogV2/item-reported.md
     - name: item_updated
-      href: events/item-updated.md
+      href: events/CatalogV2/item-updated.md
+    - name: review_reported
+      href: events/CatalogV2/review-reported.md
+    - name: reviews_takedown_requested
+      href: events/CatalogV2/reviews-takedown-requested.md
+  - name: Character
+    items:
+    - name: character_consumed_item
+      href: events/Character/character-consumed-item.md
+    - name: character_inventory_item_added
+      href: events/Character/character-inventory-item-added.md
+    - name: character_vc_item_purchased
+      href: events/Character/character-vc-item-purchased.md
+    - name: character_virtual_currency_balance_changed
+      href: events/Character/character-virtual-currency-balance-changed.md
+  - name: Inventory
+    items:
     - name: items_added
-      href: events/items-added.md
+      href: events/Inventory/items-added.md
+    - name: items_clawback_completed
+      href: events/Inventory/items-clawback-completed.md
+    - name: items_clawback_reversal_completed
+      href: events/Inventory/items-clawback-reversal-completed.md
     - name: items_deleted
-      href: events/items-deleted.md
+      href: events/Inventory/items-deleted.md
+    - name: items_expired
+      href: events/Inventory/items-expired.md
     - name: items_purchased
-      href: events/items-purchased.md
+      href: events/Inventory/items-purchased.md
     - name: items_redeemed
-      href: events/items-redeemed.md
+      href: events/Inventory/items-redeemed.md
     - name: items_subtracted
-      href: events/items-subtracted.md
+      href: events/Inventory/items-subtracted.md
     - name: items_transferred
-      href: events/items-transferred.md
+      href: events/Inventory/items-transferred.md
     - name: items_updated
-      href: events/items-updated.md
-    - name: matchmaking_match_found
-      href: events/matchmaking-match-found.md
-    - name: matchmaking_ticket_completed
-      href: events/matchmaking-ticket-completed.md
-    - name: matchmaking_user_ticket_completed
-      href: events/matchmaking-user-ticket-completed.md
-    - name: matchmaking_user_ticket_invite 
-      href: events/matchmaking-user-ticket-invite.md
-    - name: multiplayer_server_build_deleted
-      href: events/multiplayer-server-build-deleted.md
-    - name: multiplayer_server_build_region_status_changed
-      href: events/multiplayer-server-build-region-status-changed.md
-    - name: multiplayer_server_build_region_updated
-      href: events/multiplayer-server-build-region-updated.md
-    - name: multiplayer_server_certificate_deleted
-      href: events/multiplayer-server-certificate-deleted.md
-    - name: multiplayer_server_certificate_uploaded
-      href: events/multiplayer-server-certificate-uploaded.md
-    - name: multiplayer_server_create_build_initiated
-      href: events/multiplayer-server-create-build-initiated.md
-    - name: multiplayer_server_game_asset_deleted 
-      href: events/multiplayer-server-game-asset-deleted.md
-    - name: multiplayer_server_requested 
-      href: events/multiplayer-server-requested.md
-    - name: multiplayer_server_state_changed  
-      href: events/multiplayer-server-state-changed.md
-    - name: multiplayer_server_vm_assigned 
-      href: events/multiplayer-server-vm-assigned.md
-    - name: multiplayer_server_vm_remote_user_created 
-      href: events/multiplayer-server-vm-remote-user-created.md
-    - name: multiplayer_server_vm_remote_user_deleted 
-      href: events/multiplayer-server-vm-remote-user-deleted.md
-    - name: multiplayer_server_vm_unassignment_started 
-      href: events/multiplayer-server-vm-unassignment-started.md
-    - name: player_action_executed 
-      href: events/player-action-executed.md
-    - name: player_ad_activity_valued  
-      href: events/player-ad-activity-valued.md
-    - name: player_ad_campaign_attribution 
-      href: events/player-ad-campaign-attribution.md
-    - name: player_ad_closed  
-      href: events/player-ad-closed.md
-    - name: player_ad_ended  
-      href: events/player-ad-ended.md
-    - name: player_ad_opened 
-      href: events/player-ad-opened.md
-    - name: display_name_filtered  
-      href: events/display-name-filtered.md
-    - name: player_ad_rewarded 
-      href: events/player-ad-rewarded.md
-    - name: player_ad_started 
-      href: events/player-ad-started.md
-    - name: player_added_title  
-      href: events/player-added-title.md
-    - name: player_banned  
-      href: events/player-banned.md
-    - name: player_changed_avatar  
-      href: events/player-changed-avatar.md
-    - name: player_completed_password_reset 
-      href: events/player-completed-password-reset.md
-    - name: player_consumed_item  
-      href: events/player-consumed-item.md
-    - name: player_created  
-      href: events/player-created.md
-    - name: player_data_exported 
-      href: events/player-data-exported.md
-    - name: player_device_info 
-      href: events/player-device-info.md
-    - name: player_display_name_filtered 
-      href: events/player-display-name-filtered.md
-    - name: player_displayname_changed  
-      href: events/player-displayname-changed.md
-    - name: player_executed_cloudscript  
-      href: events/player-executed-cloudscript.md
-    - name: player_inventory_item_added   
-      href: events/player-inventory-item-added.md
-    - name: player_linked_account 
-      href: events/player-linked-account.md
-    - name: player_logged_in 
-      href: events/player-logged-in.md
-    - name: player_profile_memberships
-      href: events/data-types/playermemberships.md
-    - name: player_profile_subscriptions
-      href: events/data-types/subscriptions.md
-    - name: player_paid_for_purchase  
-      href: events/player-paid-for-purchase.md
-    - name: player_password_reset_link_sent 
-      href: events/player-password-reset-link-sent.md
-    - name: player_photon_session_authenticated 
-      href: events/player-photon-session-authenticated.md
-    - name: player_ranked_on_leaderboard_version 
-      href: events/player-ranked-on-leaderboard-version.md
-    - name: player_realmoney_purchase  
-      href: events/player-realmoney-purchase.md
-    - name: player_receipt_validation  
-      href: events/player-receipt-validation.md
-    - name: player_redeemed_coupon 
-      href: events/player-redeemed-coupon.md
-    - name: player_registered_push_notifications
-      href: events/player-registered-push-notifications.md
-    - name: player_removed_title 
-      href: events/player-removed-title.md
-    - name: player_reported_as_abusive 
-      href: events/player-reported-as-abusive.md
-    - name: player_set_profile_property  
-      href: events/player-set-profile-property.md
-    - name: player_started_purchase  
-      href: events/player-started-purchase.md
-    - name: player_statistic_changed   
-      href: events/player-statistic-changed.md
-    - name: player_statistic_deleted  
-      href: events/player-statistic-deleted.md
-    - name: player_tag_added   
-      href: events/player-tag-added.md
-    - name: player_tag_removed  
-      href: events/player-tag-removed.md
-    - name: player_triggered_action_executed_cloudscript 
-      href: events/player-triggered-action-executed-cloudscript.md
-    - name: player_unlinked_account 
-      href: events/player-unlinked-account.md
-    - name: player_updated_contact_email  
-      href: events/player-updated-contact-email.md
-    - name: player_vc_item_purchased 
-      href: events/player-vc-item-purchased.md
-    - name: player_verified_contact_email  
-      href: events/player-verified-contact-email.md
-    - name: player_virtual_currency_balance_changed  
-      href: events/player-virtual-currency-balance-changed.md
-    - name: review_reported
-      href: events/review-reported.md
-    - name: reviews_takedown_requested
-      href: events/reviews-takedown-requested.md
-    - name: sent_email  
-      href: events/sent-email.md
-    - name: sent_push_notification  
-      href: events/sent-push-notification.md
-    - name: studio_created  
-      href: events/studio-created.md
-    - name: studio_tier_updated  
-      href: events/studio-tier-updated.md
-    - name: studio_user_added 
-      href: events/studio-user-added.md
-    - name: studio_user_invited  
-      href: events/studio-user-invited.md
-    - name: studio_user_removed  
-      href: events/studio-user-removed.md
-    - name: tenancy_connector_onboard 
-      href: events/tenancy-connector-onboard.md
-    - name: title_aborted_task  
-      href: events/title-aborted-task.md
-    - name: title_added_cloudscript  
-      href: events/title-added-cloudscript.md
-    - name: title_api_settings_changed  
-      href: events/title-api-settings-changed.md
-    - name: title_catalog_updated  
-      href: events/title-catalog-updated.md
-    - name: title_client_rate_limited_alert  
-      href: events/title-client-rate-limited-alert.md
-    - name: title_completed_task 
-      href: events/title-completed-task.md
-    - name: title_created_task 
-      href: events/title-created-task.md
-    - name: title_deleted 
-      href: events/title-deleted.md
-    - name: title_deleted_master_player  
-      href: events/title-deleted-master-player.md
-    - name: title_deleted_task  
-      href: events/title-deleted-task.md
-    - name: title_exceeded_limit  
-      href: events/title-exceeded-limit.md
-    - name: title_high_error_rate_alert 
-      href: events/title-high-error-rate-alert.md
-    - name: title_initiated_player_password_reset  
-      href: events/title-initiated-player-password-reset.md
-    - name: title_limit_changed 
-      href: events/title-limit-changed.md
-    - name: title_news_updated 
-      href: events/title-news-updated.md
-    - name: title_permission_policy_changed 
-      href: events/title-permission-policy-changed.md
-    - name: title_profile_view_constraints_changed   
-      href: events/title-profile-view-constraints-changed.md
-    - name: title_published_cloudscript   
-      href: events/title-published-cloudscript.md
-    - name: title_queue_config_updated  
-      href: events/title-queue-config-updated.md
-    - name: title_requested_limit_change 
-      href: events/title-requested-limit-change.md
-    - name: title_saved_survey 
-      href: events/title-saved-survey.md
-    - name: title_scheduled_cloudscript_executed 
-      href: events/title-scheduled-cloudscript-executed.md
-    - name: title_secret_key_changed 
-      href: events/title-secret-key-changed.md
-    - name: title_started_task 
-      href: events/title-started-task.md
+      href: events/Inventory/items-updated.md
+    - name: marketplace_transaction_redeemed
+      href: events/Inventory/marketplace-transaction-redeemed.md
+  - name: GameSave
+    items:
+    - name: gamesave_version_finalized
+      href: events/GameSave/gamesave-version-finalized.md
+    - name: gamesave_version_marked_known_good
+      href: events/GameSave/gamesave-version-marked-known-good.md
+  - name: Partner
+    items:
+    - name: display_name_filtered
+      href: events/Partner/display-name-filtered.md
+    - name: player_display_name_filtered
+      href: events/Partner/player-display-name-filtered.md
+    - name: player_photon_session_authenticated
+      href: events/Partner/player-photon-session-authenticated.md
+  - name: Player
+    items:
+    - name: player_action_executed
+      href: events/Player/player-action-executed.md
+    - name: player_ad_campaign_attribution
+      href: events/Player/player-ad-campaign-attribution.md
+    - name: player_consumed_item
+      href: events/Player/player-consumed-item.md
+    - name: player_inventory_item_added
+      href: events/Player/player-inventory-item-added.md
+    - name: player_paid_for_purchase
+      href: events/Player/player-paid-for-purchase.md
+    - name: player_set_profile_property
+      href: events/Player/player-set-profile-property.md
+    - name: player_started_purchase
+      href: events/Player/player-started-purchase.md
+    - name: player_vc_item_purchased
+      href: events/Player/player-vc-item-purchased.md
+    - name: player_virtual_currency_balance_changed
+      href: events/Player/player-virtual-currency-balance-changed.md
+  - name: PlayerIdentity
+    items:
+    - name: auth_token_validated
+      href: events/PlayerIdentity/auth-token-validated.md
+    - name: character_created
+      href: events/PlayerIdentity/character-created.md
+    - name: entity_created
+      href: events/PlayerIdentity/entity-created.md
+    - name: entity_logged_in
+      href: events/PlayerIdentity/entity-logged-in.md
+    - name: player_added_title
+      href: events/PlayerIdentity/player-added-title.md
+    - name: player_banned
+      href: events/PlayerIdentity/player-banned.md
+    - name: player_changed_avatar
+      href: events/PlayerIdentity/player-changed-avatar.md
+    - name: player_completed_password_reset
+      href: events/PlayerIdentity/player-completed-password-reset.md
+    - name: player_created
+      href: events/PlayerIdentity/player-created.md
+    - name: player_data_exported
+      href: events/PlayerIdentity/player-data-exported.md
+    - name: player_device_info
+      href: events/PlayerIdentity/player-device-info.md
+    - name: player_displayname_changed
+      href: events/PlayerIdentity/player-displayname-changed.md
+    - name: player_linked_account
+      href: events/PlayerIdentity/player-linked-account.md
+    - name: player_logged_in
+      href: events/PlayerIdentity/player-logged-in.md
+    - name: player_password_reset_link_sent
+      href: events/PlayerIdentity/player-password-reset-link-sent.md
+    - name: player_removed_title
+      href: events/PlayerIdentity/player-removed-title.md
+    - name: player_reported_as_abusive
+      href: events/PlayerIdentity/player-reported-as-abusive.md
+    - name: player_tag_added
+      href: events/PlayerIdentity/player-tag-added.md
+    - name: player_tag_removed
+      href: events/PlayerIdentity/player-tag-removed.md
+    - name: player_unlinked_account
+      href: events/PlayerIdentity/player-unlinked-account.md
+    - name: player_updated_contact_email
+      href: events/PlayerIdentity/player-updated-contact-email.md
+    - name: player_verified_contact_email
+      href: events/PlayerIdentity/player-verified-contact-email.md
+    - name: title_deleted_master_player
+      href: events/PlayerIdentity/title-deleted-master-player.md
+    - name: title_initiated_player_password_reset
+      href: events/PlayerIdentity/title-initiated-player-password-reset.md
+    - name: title_profile_view_constraints_changed
+      href: events/PlayerIdentity/title-profile-view-constraints-changed.md
+    - name: entity_deleted
+      href: events/PlayerIdentity/entity-deleted.md
+    - name: logged_in_to_title
+      href: events/PlayerIdentity/logged-in-to-title.md
+    - name: player_authenticated
+      href: events/PlayerIdentity/player-authenticated.md
+    - name: player_custom_properties_changed
+      href: events/PlayerIdentity/player-custom-properties-changed.md
+    - name: player_identity_link_added
+      href: events/PlayerIdentity/player-identity-link-added.md
+    - name: player_identity_link_removed
+      href: events/PlayerIdentity/player-identity-link-removed.md
+    - name: player_updated_login_email
+      href: events/PlayerIdentity/player-updated-login-email.md
+  - name: PlayerProfile
+    items:
+    - name: entity_files_set
+      href: events/PlayerProfile/entity-files-set.md
+    - name: entity_language_updated
+      href: events/PlayerProfile/entity-language-updated.md
+    - name: entity_objects_set
+      href: events/PlayerProfile/entity-objects-set.md
+    - name: access_policy_updated
+      href: events/PlayerProfile/access-policy-updated.md
+    - name: avatar_url_updated
+      href: events/PlayerProfile/avatar-url-updated.md
+    - name: contact_email_updated
+      href: events/PlayerProfile/contact-email-updated.md
+    - name: files_changed
+      href: events/PlayerProfile/files-changed.md
+    - name: language_updated
+      href: events/PlayerProfile/language-updated.md
+    - name: objects_updated
+      href: events/PlayerProfile/objects-updated.md
+  - name: PlayStream
+    items:
+    - name: action_executed
+      href: events/PlayStream/action-executed.md
+    - name: action_failed
+      href: events/PlayStream/action-failed.md
+  - name: Segmentation
+    items:
+    - name: api_operation
+      href: events/Segmentation/api-operation.md
+    - name: segment_entered
+      href: events/Segmentation/segment-entered.md
+    - name: segment_exited
+      href: events/Segmentation/segment-exited.md
+  - name: Session
+    items:
+    - name: client_focus_change
+      href: events/Session/client-focus-change.md
+    - name: client_session_start
+      href: events/Session/client-session-start.md
+  - name: Title
+    items:
+    - name: title_client_rate_limited_alert
+      href: events/Title/title-client-rate-limited-alert.md
+    - name: title_high_error_rate_alert
+      href: events/Title/title-high-error-rate-alert.md
+    - name: title_requested_limit_change
+      href: events/Title/title-requested-limit-change.md
+    - name: title_saved_survey
+      href: events/Title/title-saved-survey.md
+  - name: TitleData
+    items:
+    - name: title_news_updated
+      href: events/TitleData/title-news-updated.md
+    - name: title_secret_key_changed
+      href: events/TitleData/title-secret-key-changed.md
+    - name: title_activated
+      href: events/TitleData/title-activated.md
+    - name: title_data_override_deleted
+      href: events/TitleData/title-data-override-deleted.md
+    - name: title_data_updated
+      href: events/TitleData/title-data-updated.md
+    - name: title_deactivated
+      href: events/TitleData/title-deactivated.md
+  - name: TargetedConfiguration
+    items:
+    - name: player_churn_prediction_changed
+      href: events/TargetedConfiguration/player-churn-prediction-changed.md
+  - name: Statistics
+    items:
+    - name: statistic_updated
+      href: events/Statistics/statistic-updated.md
+  - name: Leaderboards
+    items:
+    - name: character_statistic_changed
+      href: events/Leaderboards/character-statistic-changed.md
+    - name: character_statistic_deleted
+      href: events/Leaderboards/character-statistic-deleted.md
+    - name: client_authentication_completed
+      href: events/Networking/client-authentication-completed.md
+    - name: client_connected_to_network
+      href: events/Networking/client-connected-to-network.md
+    - name: client_initialization_completed
+      href: events/Networking/client-initialization-completed.md
+    - name: client_network_created
+      href: events/Networking/client-network-created.md
+    - name: client_network_destroyed
+      href: events/Networking/client-network-destroyed.md
+    - name: client_network_information_received
+      href: events/Networking/client-network-information-received.md
+    - name: client_request_failed
+      href: events/Networking/client-request-failed.md
+    - name: data_received_by_clients
+      href: events/Networking/data-received-by-clients.md
+    - name: data_sent_by_clients
+      href: events/Networking/data-sent-by-clients.md
+    - name: moderation_service_request_count
+      href: events/Networking/moderation-service-request-count.md
+    - name: player_disconnected_from_network
+      href: events/Networking/player-disconnected-from-network.md
+    - name: unity_client_initialization_completed
+      href: events/Networking/unity-client-initialization-completed.md
+    - name: unreal_client_initialization_completed
+      href: events/Networking/unreal-client-initialization-completed.md
+    - name: entity_rank_on_leaderboard_version_ended
+      href: events/Leaderboards/entity-rank-on-leaderboard-version-ended.md
+    - name: leaderboard_version_ended
+      href: events/Leaderboards/leaderboard-version-ended.md
+    - name: player_ranked_on_leaderboard_version
+      href: events/Leaderboards/player-ranked-on-leaderboard-version.md
+    - name: player_statistic_changed
+      href: events/Leaderboards/player-statistic-changed.md
+    - name: player_statistic_deleted
+      href: events/Leaderboards/player-statistic-deleted.md
     - name: title_statistic_version_changed
-      href: events/title-statistic-version-changed.md
-    - name: title_store_updated  
-      href: events/title-store-updated.md
-    - name: title_updated_task  
-      href: events/title-updated-task.md
+      href: events/Leaderboards/title-statistic-version-changed.md
+    - name: title_statistic_deleted
+      href: events/Leaderboards/title-statistic-deleted.md
 - name: API access policy
   href: api-access-policy.md
 - name: Global API method error codes
   href: global-api-method-error-codes.md
 - name: HTTP response status codes
-  href: http-response-status-codes.md  
+  href: http-response-status-codes.md
\ No newline at end of file
diff --git a/playfab-docs/breadcrumb/toc.yml b/playfab-docs/breadcrumb/toc.yml
index 0b4ca3ed8..309e333fb 100644
--- a/playfab-docs/breadcrumb/toc.yml
+++ b/playfab-docs/breadcrumb/toc.yml
@@ -1,37 +1,33 @@
 items:
-- name: Azure
+- name: PlayFab
   tocHref: /gaming/playfab/
-  topicHref: /azure/
+  topicHref: /gaming/playfab/
   items:
-  - name: PlayFab
-    tocHref: /gaming/playfab/
-    topicHref: /gaming/playfab/
-    items:
-    - name: Fundamentals
-      topicHref: /gaming/playfab/get-started/
-    - name: Fundamentals
-      topicHref: /gaming/playfab/whats-new/
-    - name: Fundamentals
-      topicHref: /gaming/playfab/demo-game/
-    - name: Fundamentals
-      topicHref: /gaming/playfab/resources/
-    - name: Fundamentals
-      topicHref: /gaming/playfab/pricing/
-    - name: Fundamentals
-      topicHref: /gaming/playfab/sdks/
-    - name: Live service management
-      topicHref: /gaming/playfab/live-service-management/
-    - name: Fundamentals
-      topicHref: /gaming/playfab/api-references/
-    - name: Identity
-      topicHref: /gaming/playfab/identity/
-    - name: Economy, Monetization, & UGC.
-      topicHref: /gaming/playfab/economy-monetization/
-    - name: Multiplayer
-      topicHref: /gaming/playfab/multiplayer/
-    - name: Community
-      topicHref: /gaming/playfab/community/
-    - name: Player progression
-      topicHref: /gaming/playfab/player-progression/
-    - name: Game Data
-      topicHref: /gaming/playfab/data-analytics/
+  - name: Fundamentals
+    topicHref: /gaming/playfab/get-started/
+  - name: Fundamentals
+    topicHref: /gaming/playfab/whats-new/
+  - name: Fundamentals
+    topicHref: /gaming/playfab/demo-game/
+  - name: Fundamentals
+    topicHref: /gaming/playfab/resources/
+  - name: Fundamentals
+    topicHref: /gaming/playfab/pricing/
+  - name: Fundamentals
+    topicHref: /gaming/playfab/sdks/
+  - name: Live service management
+    topicHref: /gaming/playfab/live-service-management/
+  - name: Fundamentals
+    topicHref: /gaming/playfab/api-references/
+  - name: Identity
+    topicHref: /gaming/playfab/identity/
+  - name: Economy, Monetization, & UGC.
+    topicHref: /gaming/playfab/economy-monetization/
+  - name: Multiplayer
+    topicHref: /gaming/playfab/multiplayer/
+  - name: Community
+    topicHref: /gaming/playfab/community/
+  - name: Player progression
+    topicHref: /gaming/playfab/player-progression/
+  - name: Game Data
+    topicHref: /gaming/playfab/data-analytics/
diff --git a/playfab-docs/community/index.yml b/playfab-docs/community/index.yml
index e0875faf9..540538db9 100644
--- a/playfab-docs/community/index.yml
+++ b/playfab-docs/community/index.yml
@@ -1,6 +1,6 @@
 ### YamlMime:Landing
 
-title: Azure PlayFab Community documentation
+title: PlayFab Community documentation
 summary: PlayFab Community is a set of cross-platform tools and services that enable game creators to build engaging social experiences and foster long term player connections and communities.
 
 metadata:
diff --git a/playfab-docs/community/leaderboards/index.md b/playfab-docs/community/leaderboards/index.md
index c17cf486b..9f5f74232 100644
--- a/playfab-docs/community/leaderboards/index.md
+++ b/playfab-docs/community/leaderboards/index.md
@@ -1,7 +1,7 @@
 ---
-title: Azure PlayFab Leaderboards overview
+title: PlayFab Leaderboards overview
 author: braulioal
-description: Learn about Azure PlayFab Leaderboard.
+description: Learn about PlayFab Leaderboard.
 ms.author: braulioal
 ms.date: 09/01/2024
 ms.topic: article
@@ -10,9 +10,9 @@ keywords: playfab, multiplayer, leaderboard, stats
 ms.localizationpriority: medium
 ---
 
-# Azure PlayFab Leaderboards overview
+# PlayFab Leaderboards overview
 
-Azure Playfab Leaderboards is a cross-platform service that creates a sorted list of players with the purpose
+PlayFab Leaderboards is a cross-platform service that creates a sorted list of players with the purpose
 of ranking them by scores. Leaderboards can be used as a standalone service or be linked with Statistics (so that updates to statistics feed into the entries on the leaderboard).
 
 ![PlayFab Leaderboards Architecture](media/leaderboards-relationship.png)
@@ -72,4 +72,5 @@ has a Statistics engine doing the aggregation.
 - [API reference](api-reference.md)  
 - [Quota](quota-leaderboards.md)  
 - [Leaderboard meters](../../pricing/Meters/leaderboard-meters.md)
+- [Leaderboards and Cloudscript](leaderboards-cloudscript.md).
 - [Leaderboards With PlayStream and Telemetry](./leaderboards-with-playstream-and-telemetry.md)
diff --git a/playfab-docs/community/leaderboards/leaderboards-cloudscript.md b/playfab-docs/community/leaderboards/leaderboards-cloudscript.md
index a6afa3237..3bae2b510 100644
--- a/playfab-docs/community/leaderboards/leaderboards-cloudscript.md
+++ b/playfab-docs/community/leaderboards/leaderboards-cloudscript.md
@@ -1,5 +1,5 @@
 ---
-title: Leaderboards Using Azure Functions
+title: Leaderboards using Azure Functions
 author: braulioal
 description: Learn how to create and manage leaderboards using Azure Functions in PlayFab.
 ms.author: braulioal
@@ -10,23 +10,23 @@ keywords: playfab, multiplayer, leaderboard, stats
 ms.localizationpriority: medium
 ---
 
-# Leaderboards Using Azure Functions 
+# Leaderboards using Azure Functions 
 
 In this tutorial, you'll learn how to implement leaderboards using Cloudscript, specifically through [Azure Functions](../../live-service-management/service-gateway/automation/cloudscript-af/index.md). 
-This approach is particularly powerful because it enables you to create custom server-side logic without requiring client updates.
+This approach is powerful because it enables you to create custom server-side logic without requiring client updates.
 
 By defining leaderboard-related logic within an Azure Function, your client can invoke that function to execute the code. If changes are needed later, you can update the Azure Function independently—often without modifying the client—depending on the complexity of the update.
 
 ## Prerequisites
-To follow this tutorial you need to have:
-- An Azure PlayFab account, if you don't have one you can create it [here](https://playfab.com/).
-- An Azure subscription, if you don't have one you can create it [here](https://azure.microsoft.com/free/).
+To follow this tutorial, you need:
+- A PlayFab account. If you don't have one, you can create it [here](https://developer.playfab.com/).
+- An Azure subscription. If you don't have one, you can create it [here](https://azure.microsoft.com/free/).
 
 For more details on how to create an Azure Function check this guide. [Create your first function in Azure using Visual Studio](https://learn.microsoft.com/azure/azure-functions/functions-create-your-first-function-visual-studio)
 
-## Create a Leaderboard using Azure Functions
+## Create a leaderboard using Azure Functions
 
-In this section we're going to create a simple leaderboard that will allow us to submit scores and retrieve the top scores. 
+In this section, we're going to create a leaderboard that allows you to submit scores and retrieve the top scores. 
 
 ``` C#
 [Function("LeaderboardExample")]
@@ -82,12 +82,12 @@ public async Task<HttpResponseData> RunAsync([HttpTrigger(AuthorizationLevel.Ano
 }
 
 ```
-- This function attribute ```[Function("LeaderboardExample")]``` defines the name of the function, in this case "LeaderboardExample".
+- This function attribute ```[Function("LeaderboardExample")]``` defines the name of the function, in this case `LeaderboardExample`.
 - The function is triggered by an HTTP request, as indicated by the ```[HttpTrigger(AuthorizationLevel.Anonymous, "get", "post")]``` attribute. This means that the function can be accessed via HTTP GET and POST methods without any authentication.
-- Within the function, we set the PlayFab Title ID and Developer Secret Key to authenticate our requests to PlayFab services. You can change the way you want to access this values based on what fits best for your particular case and security requirements.
+- Within the function, we set the PlayFab Title ID and Developer Secret Key to authenticate our requests to PlayFab services. You can change the way you want to access these values based on what fits best for your particular case and security requirements.
 - The function checks if the query parameter "leaderboardName" is provided in the request.
 - Then we call the method ```LoginAsTitleEntity``` to authenticate as a title entity, which is necessary to create leaderboard definitions.
-- Finally, we call the method ```CreateLeaderboardDefinitionAsync``` to create a leaderboard definition with the provided name. To find more about creation of leaderboard you can check [Create basic leaderboard](create-basic-leaderboard.md) and [Doing more with leaderboards](doing-more-with-leaderboards.md).
+- Finally, we call the method ```CreateLeaderboardDefinitionAsync``` to create a leaderboard definition with the provided name. To find more about creation of leaderboard, you can check [Create basic leaderboard](create-basic-leaderboard.md) and [Doing more with leaderboards](doing-more-with-leaderboards.md).
 
 The RunAsync method serves as the entry point for your Azure Function. From there, you can define and call additional methods to build out your custom game logic. How you handle errors or interact with multiple PlayFab services is entirely up to you, giving you full flexibility in your implementation.
 
@@ -97,8 +97,8 @@ Additionally, you can configure automation rules to trigger this Azure Function
 - [Doing more with leaderboards](doing-more-with-leaderboards.md).
 - [Create basic leaderboard](create-basic-leaderboard.md).
 - [Manual tiers](manual-tiers.md).
-- [Limits ](limits-leaderboards.md).
-- [Quota ](quota-leaderboards.md).
+- [Limits](limits-leaderboards.md).
+- [Quota](quota-leaderboards.md).
 - [Seasonal leaderboards](seasonal-leaderboards.md).
 - [Ranking players by statistics](leaderboards-linked-to-stats.md).
 - [Add contextual data to leaderboards](metadata-leaderboards.md).
diff --git a/playfab-docs/community/leaderboards/leaderboards-linked-to-stats.md b/playfab-docs/community/leaderboards/leaderboards-linked-to-stats.md
index bf584b8ec..a61550237 100644
--- a/playfab-docs/community/leaderboards/leaderboards-linked-to-stats.md
+++ b/playfab-docs/community/leaderboards/leaderboards-linked-to-stats.md
@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 # Ranking players by statistics
 
 In this tutorial, we're going to learn how to use both Leaderboards and Statistics services together. The end result is that, when a statistic is updated on an entity, is automatically reflected on the corresponding leaderboard.
-For more information about Azure PlayFab Statistics, see [Statistics Overview]([Azure PlayFab Statistics overview](../../player-progression/statistics/index.md)).
+For more information about PlayFab Statistics, see [Statistics Overview]([PlayFab Statistics overview](../../player-progression/statistics/index.md)).
 
 
 Let's start with an example of a shooter game that uses both services. Here we're going to take advantage of the 
diff --git a/playfab-docs/community/leaderboards/leaderboards-with-playstream-and-telemetry.md b/playfab-docs/community/leaderboards/leaderboards-with-playstream-and-telemetry.md
index c290be105..baa6d95d7 100644
--- a/playfab-docs/community/leaderboards/leaderboards-with-playstream-and-telemetry.md
+++ b/playfab-docs/community/leaderboards/leaderboards-with-playstream-and-telemetry.md
@@ -18,8 +18,8 @@ And if you want just the data analytics and warehousing without the real-time ev
 
 Leaderboards provides two optional events:
 
-- [`playfab.leaderboard.leaderboard_version_ended`](../../api-references/events/leaderboard-version-ended.md)
-- [`playfab.leaderboard.entity_rank_on_leaderboard_version_ended`](../../api-references/events/entity-rank-on-leaderboard-version-ended.md)
+- [`playfab.leaderboard.leaderboard_version_ended`](../../api-references/events/Leaderboards/leaderboard-version-ended.md)
+- [`playfab.leaderboard.entity_rank_on_leaderboard_version_ended`](../../api-references/events/Leaderboards/entity-rank-on-leaderboard-version-ended.md)
 
 These two events allow you to quickly know when a leaderboard version has ended and allow you to query previous data as soon as you want. With entity rank on leaderboard version ended, you can get the rank and score of the top entity for a leaderboard when that leaderboard version ended.
 
@@ -51,8 +51,8 @@ For learning more about how to leverage these events to preform different action
 
 ## See Also 
 
-- [`playfab.leaderboard.leaderboard_version_ended`](../../api-references/events/leaderboard-version-ended.md)
-- [`playfab.leaderboard.entity_rank_on_leaderboard_version_ended`](../../api-references/events/entity-rank-on-leaderboard-version-ended.md)
+- [`playfab.leaderboard.leaderboard_version_ended`](../../api-references/events/Leaderboards/leaderboard-version-ended.md)
+- [`playfab.leaderboard.entity_rank_on_leaderboard_version_ended`](../../api-references/events/Leaderboards/entity-rank-on-leaderboard-version-ended.md)
 - [PlayStream Overview](../../data-analytics/ingest-data/playstream-overview.md)
 - [Statistics with PlayStream and Telemetry](../../player-progression/statistics/statistics-with-playstream-and-telemetry.md).
 - [Telemetry Overview](../../data-analytics/ingest-data/telemetry-overview.md)
diff --git a/playfab-docs/community/leaderboards/quickstart-leaderboards.md b/playfab-docs/community/leaderboards/quickstart-leaderboards.md
index 9c8130bde..30a165b78 100644
--- a/playfab-docs/community/leaderboards/quickstart-leaderboards.md
+++ b/playfab-docs/community/leaderboards/quickstart-leaderboards.md
@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 # Quickstart leaderboards
 
 In this guide, we're going to see how to set up the development environment for the Leaderboard service. We're also going
-to learn how to create a quick leaderboard from our website [Game Manager](https://developer.playfab.com/en-US/login).
+to learn how to create a quick leaderboard from our website [Game Manager](https://developer.playfab.com).
 
 ## Prerequisites
 
@@ -59,7 +59,7 @@ PlayFabSettings.staticSettings.DeveloperSecretKey = ""; // Change this to your t
 
 ## Creating a title and getting the secret key
 
-- Log in to https://playfab.com/
+- Log in to https://developer.playfab.com/
 - Create a title
     - Find the Title ID in the API Features section under settings.   
 - Generate secret key:
diff --git a/playfab-docs/community/leaderboards/quota-leaderboards.md b/playfab-docs/community/leaderboards/quota-leaderboards.md
index a235b679c..bdd894bb4 100644
--- a/playfab-docs/community/leaderboards/quota-leaderboards.md
+++ b/playfab-docs/community/leaderboards/quota-leaderboards.md
@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 # Quota limits leaderboards
 
 The Leaderboard service is designed to align with PlayFab's pricing models, offering two distinct modes: 
-development and live. The development mode allows titles to test each feature and begin development. 
+development and live. The Development Mode allows titles to test each feature and begin development. 
 The live mode, on the other hand, is optimized for handling larger traffic loads typical of a live game.
 
 The following tables outline the limits for each of these modes:
diff --git a/playfab-docs/community/leaderboards/toc.yml b/playfab-docs/community/leaderboards/toc.yml
index fddb12bd9..f5b84daaa 100644
--- a/playfab-docs/community/leaderboards/toc.yml
+++ b/playfab-docs/community/leaderboards/toc.yml
@@ -25,6 +25,8 @@ items:
     href: manual-tiers.md
   - name: Leaderboards with PlayStream and Telemetry
     href: leaderboards-with-playstream-and-telemetry.md
+  - name: Leaderboards with Cloud Script
+    href: leaderboards-cloudscript.md
   - name: API reference 
     href: api-reference.md
 - name: Tournaments & Leaderboards (Deprecated)
diff --git a/playfab-docs/data-analytics/acting-data/action-rules-using-cloudscript-actions-with-playstream.md b/playfab-docs/data-analytics/acting-data/action-rules-using-cloudscript-actions-with-playstream.md
index acc9104e2..7d93e6a3c 100644
--- a/playfab-docs/data-analytics/acting-data/action-rules-using-cloudscript-actions-with-playstream.md
+++ b/playfab-docs/data-analytics/acting-data/action-rules-using-cloudscript-actions-with-playstream.md
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 
 # Using CloudScript actions with PlayStream
 
-When a CloudScript handler is launched from a PlayStream action, that handler has access to additional data on why it is being run - the *context* - which you can use to drive your server-side logic.
+When a CloudScript handler is launched from a PlayStream action, that handler has access to more data on why It's being run - the *context* - which you can use to drive your server-side logic.
 
 This tutorial walks you through what all is available in the context, and how to make use of it in your CloudScript handlers.
 
@@ -85,9 +85,9 @@ handlers.handlePlayStreamEventAndProfile = function (args, context) {
 
 In the case of a PlayStream-triggered CloudScript call, the context contains 3 elements that can be used to drive your server-authoritative handler's logic.
 
-1. There’s the `playStreamEvent`, which you can see in the example code above. The `playStreamEvent` contains the complete event which triggered the handler as a JSON object, with all the parameters you see in the [PlayStream event documentation](../../api-references/events/index.md). So for example, if you set up a rule in your title that called `handlePlayStreamEventAndProfile` on any `player_logged_in event`, `playStreamEvent.EventName` would be `player_logged_in`, etc. ([here’s the complete set of parameters for that event](../../api-references/events/player-logged-in.md)).
+1. There’s the `playStreamEvent`, which you can see in the example code above. The `playStreamEvent` contains the complete event which triggered the handler as a JSON object, with all the parameters you see in the [PlayStream event documentation](../../api-references/events/index.md). So for example, if you set up a rule in your title that called `handlePlayStreamEventAndProfile` on any `player_logged_in event`, `playStreamEvent.EventName` would be `player_logged_in`, etc. ([here’s the complete set of parameters for that event](../../api-references/events/PlayerIdentity/player-logged-in.md)).
 
-1. Next, there’s the `playerProfile`, also shown in the previous example. This contains information about the player that triggered the event. You can find all the details of the profile parameters here, but among other things, it contains the complete set of statistics for the player in your title, as well as any custom tags you have assigned to the player, so that you can use that data for very rich decision-making.
+1. Next, there’s the `playerProfile`, also shown in the previous example. This contains information about the player that triggered the event. You can find all the details of the profile parameters here, but among other things, it contains the complete set of statistics for the player in your title, and any custom tags you have assigned to the player, so that you can use that data for rich decision-making.
 
 1. The last element of context is `triggeredByTask`. Unlike the first two, which are set when using Rules and Segment Enter/Exit triggers, `triggeredByTask` is only applicable when the handler is running as a result of a task, whether manual or on a timer. It contains only two parameters:
 
@@ -105,6 +105,6 @@ So *name* is the element you’ll want to use to use in your handler’s code fl
 
 In many ways, CloudScript handlers triggered by PlayStream actions have even more potential functionality than those triggered directly through calls to `ExecuteCloudScript`, since there’s a rich set of data made available via the context.
 
-This gives you the ability to update your handlers post-launch with *additional* logic that makes use of elements of the event or player profile that you hadn’t originally anticipated, *without* needing to update your client code in any way.
+This gives you the ability to update your handlers post-launch with *more* logic that makes use of elements of the event or player profile that you hadn’t originally anticipated, *without* needing to update your client code in any way.
 
 In addition, we’ll continue to make additions to the player profile in future updates of the PlayFab service, which will provide even *more* options for server-side logic.
diff --git a/playfab-docs/data-analytics/acting-data/media/get-segment-player-count.png b/playfab-docs/data-analytics/acting-data/media/get-segment-player-count.png
new file mode 100644
index 000000000..21c366bb5
Binary files /dev/null and b/playfab-docs/data-analytics/acting-data/media/get-segment-player-count.png differ
diff --git a/playfab-docs/data-analytics/export-data/data-connection-azure-blob.md b/playfab-docs/data-analytics/export-data/data-connection-azure-blob.md
index 6e2945b81..4eea129ea 100644
--- a/playfab-docs/data-analytics/export-data/data-connection-azure-blob.md
+++ b/playfab-docs/data-analytics/export-data/data-connection-azure-blob.md
@@ -11,21 +11,21 @@ ms.localizationpriority: medium
 ---
 # Configuring your Azure Storage Data Connection
 
-First, you need an Azure subscription and a storage account. 
+First, you need an Azure subscription and a storage account.
 
-For existing PlayFab and Azure customers, you can create a storage container on the [Azure portal](https://ms.portal.azure.com/#allservices) and get started with Data Connections on [Azure PlayFab](https://developer.playfab.com/en-US/sign-up).
+For existing PlayFab and Azure customers, you can create a storage container on the [Azure portal](https://ms.portal.azure.com/#allservices) and get started with Data Connections on [PlayFab](https://developer.playfab.com/en-US/sign-up).
 
 For existing PlayFab who are new to Azure, you can sign up for an [Azure subscription](https://ms.portal.azure.com/).
 
-> [!Note]
+> [!NOTE]
 > Make sure to create your Storage Account in the West US 2, otherwise, egress cost will be applied to your storage account. You can configure up to three Azure Blob Storage accounts in the WestUS2 region.
 
 ## Setting up your Storage in Azure
 
-For PlayFab to ingest data in your storage account, container details along with authorization using a SAS token are required. To create a SAS token using the Microsoft Azure portal, follow the steps below.
+For PlayFab to ingest data in your storage account, container details along with authorization using a SAS token are required. To create a SAS token using the Microsoft Azure portal, use the following steps.
 
-> [!Note]
-> A Storage Account with a restricted network is not supported. All networks must be allowed in the firewall.
+> [!NOTE]
+> A storage account with a restricted network isn't supported. You must allow all networks in the firewall.
 
 ### Option 1: Create the SAS token on the container level. 
 > [!Important]
@@ -36,57 +36,57 @@ For PlayFab to ingest data in your storage account, container details along with
 - Go to the right of the main window and select the three ellipses associated with your chosen container.
 - Select **Generate SAS** from the dropdown menu to open the **Generate SAS** window.
 
-![Screenshot of SAS token on the container level - Option 1](media/SAS-token-on-the-container-level-1.png "SAS token on the container level - Option 1") 
+![Screenshot of SAS token on the container level - Option 1](media/SAS-token-on-the-container-level-1.png "SAS token on the container level - Option 1")
 
 - Define **Permissions** by selecting or clearing the appropriate checkbox. Make sure the **Create** and **Write** permissions are selected.
 
-![Screenshot of Generate SAS token - Option 1](media/Generate-SAS-token-level.png "Generate SAS token - Option 1") 
+![Screenshot of Generate SAS token - Option 1](media/Generate-SAS-token-level.png "Generate SAS token - Option 1")
 
-- Specify the signed key **Start** and **Expiry** times. 
+- Specify the signed key **Start** and **Expiry** times.
 - Select **Generate SAS token and URL**.
 - The **Blob SAS token** query string appears in the lower area of the window.
-- Copy and paste the **Blob SAS token** values into a **secure location for use in the Azure PlayFab Data Connections**. It's displayed only once and can't be retrieved after the window is closed.
+- Copy and paste the **Blob SAS token** values into a **secure location for use in the PlayFab Data Connections**. It's displayed only once and can't be retrieved after the window is closed.
 
-### Option 2: Create the SAS token on the account level.
+### Option 2: Create the SAS token at the account level
 > [!Important]
-> Generate and retrieve the shared access signature for your storage account itself.
-
-- In the [Azure portal](https://ms.portal.azure.com/#allservices), select **Your storage account** 
-- Select a **Shared access signature** from the list under **Security + Networking**.
-- Define **Services** by selecting **blob** and clearing other checkboxes. 
-- Define **Resource Type** by selecting **Object** and clearing other checkboxes. 
-- Make sure the **Create** and **Write** permissions are selected.
-- Specify the signed key **Start** and **Expiry** times. 
+> Generate and retrieve the shared access signature for your storage account.
+
+- In the [Azure portal](https://ms.portal.azure.com/#allservices), select **Your storage account**
+- Select **Shared access signature** from the list under **Security + Networking**.
+- Define **Services** by selecting **blob** and clearing other checkboxes.
+- Define **Resource Type** by selecting **Container** and **Object** (clear other checkboxes).
+- Make sure the **Create**, **Write**, and **List** permissions are selected.
+- Specify the signed key **Start** and **Expiry** times.
 - Select **Generate SAS token and URL**.
 - The Blob SAS token query string appears in the lower area of the window.
-- Copy and paste the **Blob SAS token** values into a **secure location for use in the Azure PlayFab Data Connections**. It's displayed only once and can't be retrieved after the window is closed.
+- Copy and paste the **Blob SAS token** values into a **secure location for use in the PlayFab Data Connections**. It's displayed only once and can't be retrieved after the window is closed.
 
-![Screenshot of SAS token on the account level - Option 2](media/SAS-token-on-the-account-level.png "SAS token on the account level - Option 2") 
+![Screenshot of SAS token on the account level - Option 2](media/SAS-token-on-the-account-level.png "SAS token on the account level - Option 2")
 
 ## Create an Azure Blob Data Connection in PlayFab
 
-### Step 1: Navigate to the data connections tab
+### Step 1: Navigate to the Data Connections tab
 
-![Screenshot of PlayFab data connections tab](media/navigate-to-data-connections-tab.png "PlayFab data connections tab") 
+![Screenshot of PlayFab data connections tab](media/navigate-to-data-connections-tab.png "PlayFab data connections tab")
 
 - Login to PlayFab and navigate to your title.
-- Click on the “Data” section in the left-hand menu
-- Click on the “Data Connections” tab
+- Select the **Data** section in the left-hand menu.
+- Select the **Data Connections** tab.
 
 ### Step 2: Configure a new Data Connection
 
-- Click “New Connection” button.
-- Choose the “Destination Type” to be “Azure Blob Storage”
-- Populate the fields using the following values  
+- Select **New Connection**.
+- Choose **Azure Blob Storage** as the **Destination Type**.
+- Enter the following values for each field:  
 
 | Value | Details |
 |:-----------|:-----------|
-|Name | The friendly name of your data connection. This name will allow you to find the data connection later to edit it. Put a descriptive name here. 
+|Name | The friendly name of your data connection. This name allows you to find the data connection later to edit it. Put a descriptive name here.
 | Account name  | The Azure Storage Account. |
 | Container name | The Azure Storage Account Container. |
 | Sas token |  Either the SAS token generated by the container, or the Blob SAS token query string.  |
 
-![Screenshot of configuring and ADX data connection](media/configure-new-data-connection-blob.PNG "ADX data connection configuration") 
+![Screenshot of configuring and ADX data connection](media/configure-new-data-connection-blob.PNG "ADX data connection configuration")
 
-> [!Note]
-> We recommend using a table name that does not exist. If you use an existing table and the schema is not what PlayFab is expecting, then the schema will be modified. 
+> [!NOTE]
+> We recommend using a table name that doesn't exist. If you use an existing table and the schema isn't what PlayFab is expecting, then the schema will be modified.
diff --git a/playfab-docs/data-analytics/export-data/data-connection-overview.md b/playfab-docs/data-analytics/export-data/data-connection-overview.md
index b65aaa26a..488427553 100644
--- a/playfab-docs/data-analytics/export-data/data-connection-overview.md
+++ b/playfab-docs/data-analytics/export-data/data-connection-overview.md
@@ -1,7 +1,7 @@
 ---
-title: Data connections - Overview
+title: Data Connections - Overview
 author: sofiamarinv
-description: Data connections
+description: Data Connections
 ms.author: sofiamarin
 ms.date: 11/27/2023
 ms.topic: article
@@ -10,31 +10,35 @@ keywords: playfab, data connections, byos, connections, event ingestion
 ms.localizationpriority: medium
 ---
 
-# Data connections
+# Data Connections
 
-**Data connections** enables the continuous near real-time distribution and ingestion of PlayStream and Telemetry data into your chosen and authorized storage resource in your Azure subscription. Today it works with Azure Blob Storage, Azure Data Explorer (ADX) and Microsoft Fabric KQL databases.
+**Data Connections** enables continuous, near-real-time ingestion of PlayStream and Telemetry data into your authorized storage resource in your Azure subscription. This feature works with Azure Blob Storage, Azure Data Explorer (ADX), Microsoft Fabric KQL databases, and Amazon Web Services S3.
 
-It provides control of your data in your storage account with less than 5-minute data ingestion latency. The architecture is designed for better batch processing that facilitates Parquet files in blob storage with the highest throughput, low storage cost, and most flexibility. In case of failure in data distribution, a built-in automatic retry mechanism is in place to ensure data quality.
+It provides control of your data in your storage account with less than five-minute data ingestion latency. The architecture is designed for batch processing and supports Parquet files in Blob Storage with higher throughput, lower storage cost, and greater flexibility. In case of data distribution failure, a built-in automatic retry mechanism helps ensure data is delivered successfully.
 
-You can get started with data connections for event ingestion using PlayFab’s Game Manager portal or scalable APIs.
+You can get started with Data Connections for event ingestion by using PlayFab’s Game Manager portal or scalable APIs.
 
 > [!Note]
-> Although you can use either ADX, Blob or Fabric KQL, these have different potential use cases. Blob may be preferred if you are leveraging synapse for ML modelling and batch processing, while ADX supports ad-hoc querying and real-time debugging of your live services with analytics.
+> Although you can use either ADX, Blob, or Fabric KQL, these options have different potential use cases. You might prefer Blob if you’re using Synapse for ML modeling and batch processing, while ADX supports ad-hoc analytics, querying, and real-time debugging of live services.
 
-![Screenshot of data connections Overview](media/data-connections-overview.png "Data Connections Overview")
+![Screenshot of Data Connections Overview](media/data-connections-overview.png "Data Connections Overview")
 
 ## Why do you need it?
 
-Data connections is the replacement for the Event Export and Export to S3 features that currently PlayFab supports. Data connections allow for faster export in preferred formats for offline processing. You get to bring your storage account for data to be ingested and distributed. That means you get to manage and control the encryption-at-rest policy, the lifetime management policy, and network access. The billing becomes simplified as the costs associated with that storage account are accounted for centrally in your all-up Azure account billing.  
+Data Connections replaces the Event Export and Export to S3 features that PlayFab currently supports. It allows for faster export in supported formats for offline processing. You provide the storage account where the data is ingested and delivered. That means you control encryption at rest, lifecycle management, and network access. Billing is simplified because the storage costs are included centrally in your overall Azure account billing.
 
 ### Azure Blob Data Connection
-The data is readily available in Parquet blob format. Parquet is a column-oriented data file format designed for efficient data storage and retrieval. It provides efficient data compression and encoding schemes with enhanced performance to handle complex data in bulk, resulting in low latency, higher throughput, and low cost of data storage. It's designed to be a common interchange format for both batch and interactive workloads. Thus, data connections enables your endeavors for custom advanced analytics and reporting, to run ad-hoc queries in a cost-optimized manner.
+The data is readily available in Parquet blob format. Parquet is a column-oriented data file format designed for efficient data storage and retrieval. It provides efficient data compression and encoding schemes with enhanced performance to handle complex data in bulk, resulting in low latency, higher throughput, and low cost of data storage. It's designed to be a common interchange format for both batch and interactive workloads. This makes Blob Storage a good fit for offline processing and cost-optimized analytics and reporting (including ad-hoc queries over stored files).
 
 ### Azure Data Explorer Data Connection
-Data Connections allows you to export to Azure Data Explorer for near-real time ingestion and distribution of your data. Azure Data Explorer can query millions of records in a few seconds enabling you to gain invaluable insights and make informed decisions swiftly and efficiently. 
+Data Connections allows you to export to Azure Data Explorer for near-real-time ingestion and distribution of your data. Azure Data Explorer can query millions of records in a few seconds, enabling you to gain invaluable insights and make informed decisions swiftly and efficiently.
 
-For more optimized cost and data control, you can make use of data connections with [Event Sampling](event-sampling-overview.md) - Sampling enables you to configure the percentage of events data that you want to receive.
+For more optimized cost and data control, you can make use of Data Connections with [Event Sampling](event-sampling-overview.md). Sampling enables you to configure the percentage of events data that you want to receive.
 
 ### Microsoft Fabric KQL database Data Connection
 
-You can utilize PlayFab's Data Connections service to distribute game events to Real-Time Analytics (RTA) databases, allowing you to generate near-real-time analytics and insights in Power BI or through KQL queries on your Microsoft Fabric workspace.
+Use PlayFab’s Data Connections to send game events to Real-Time Analytics (RTA) databases, so you can generate near-real-time insights in Power BI or run KQL queries in your Microsoft Fabric workspace.
+
+### Amazon AWS S3 Data Connection (PREVIEW)
+
+The AWS S3 Data Connection provides a secure, scalable way to stream your PlayFab telemetry and event data directly into your own Amazon S3 bucket. Designed for reliability and high throughput workloads, it uses a robust pipeline to validate, transport, and land game data in an open, analytics ready format. By using your own AWS storage and IAM roles, you retain control over data governance, encryption, access policies, lifecycle management, and cost visibility. This also enables downstream workflows such as BI reporting, machine learning, and large-scale data processing in your AWS environment. 
\ No newline at end of file
diff --git a/playfab-docs/data-analytics/export-data/data-connection-quickstart.md b/playfab-docs/data-analytics/export-data/data-connection-quickstart.md
index aa4cc1ecc..6be35c8d8 100644
--- a/playfab-docs/data-analytics/export-data/data-connection-quickstart.md
+++ b/playfab-docs/data-analytics/export-data/data-connection-quickstart.md
@@ -6,24 +6,25 @@ ms.author: sofiamarin
 ms.date: 11/27/2023
 ms.topic: article
 ms.service: azure-playfab
-keywords: playfab, data connections, byos, connections, event ingestion, bring your own stoarge
+keywords: playfab, data connections, byos, connections, event ingestion, bring your own storage
 ms.localizationpriority: medium
 ---
 
 # Data Connections quickstart
 
 ## Prerequisites
-- For Data Connections, you need an Azure subscription and a storage account. 
-- For PlayFab to ingest data in your storage account, container details along with authorization using a SAS token are required. To create a SAS token using Microsoft Azure portal, follow the steps below.
+- For Data Connections, you need an Azure or Amazon subscription and a storage account. 
+- For PlayFab to ingest data in your storage account, you need container details along with authorization using a SAS token.
+- To create a SAS token using Microsoft Azure portal, follow the steps in the next section.
 
 ## Create a Data Connection
 
-A Connection is created to integrate your storage resource with PlayFab and retrieve the PlayStream and Telemetry data. You can configure up to three data connections in the “enabled (active)” state. 
+Create a connection to integrate your storage resource with PlayFab and retrieve the PlayStream and telemetry data. You can configure up to three data connections in the **enabled (active)** state.
 
-### Azure Blog Storage
+### Azure Blob Storage
 
 From the Game Manager:
-- Navigate to your **Title**
+- Go to your **Title**
 - Select **Data** from the menu on the left
 - Select **Data Connections** from the **Data** tabs
 - Select **New Connection**, new data connections configuration page is opened
@@ -33,8 +34,8 @@ From the Game Manager:
     *	Enter **Container Name**
     *	Enter **SAS Token** as generated in the Azure portal
 - Select **Save**
-    *	With the default check on **Enabled**, the connection between PlayFab and the customer’s resource is established once saved.
-    *	With uncheck on **Enabled**, the connection between PlayFab and the customer’s resource is validated but not established until saved.
+    *	By using the default check on **Enabled**, the connection between PlayFab and your resource is established once saved.
+    *	By using uncheck on **Enabled**, the connection between PlayFab and your resource is validated but not established until saved.
 
 ![Screenshot of Create Data Connection](media/create-data-connection.png "Create Data Connection")
 
@@ -42,12 +43,12 @@ From the Game Manager:
 
 From PlayFab Game Manager:
 
-- Navigate to your **Title**
+- Go to your **Title**
 - Select **Data** from the menu on the left
 - Select **Data Connections** from the **Data** tabs
 - Select **New Connection**, new data connections configuration page is opened
 - On the **Destination type** dropdown, select the **Fabric KQL Database** option 
-- Give your **Data Connection** a name on the **Name** field 
+- Enter a name for your **Data Connection** in the **Name** field 
 - Make sure the **Enabled** box is checked 
 - Go to [Microsoft Fabric](https://msit.powerbi.com/home)
 - Select **Workspaces** on the left panel and select **Your Workspace** 
@@ -56,14 +57,65 @@ From PlayFab Game Manager:
 - Go back to Data Connections on PlayFab's Game Manager
 - Paste the **Query URI** you got from Fabric into the **Ingestion URI** field
 - In the **Database** field, enter the name of the **KQL Database** you created in Fabric
-- Fill the **Table** field with a significant name. Example: **Events** 
+- Fill the **Table** field with a significant name (for example, **Events**) 
 
 > [!Note]
 > To optimize your use of a Fabric KQL Data Connection and gain valuable insights into your game data, follow the tutorial on PlayFab and Microsoft Fabric Real-Time Analytics (RTA) for game creators: [PlayFab and Microsoft Fabric Real-Time Analytics (RTA) for game creators](../learn-data/reports/real-time-analytics-tutorial.md)
 
+### Amazon Web Services S3 (PREVIEW)
+From PlayFab Game Manager:
+-	Navigate to your title
+-	Select Data from the menu on the left
+-	Select Data Connections from the Data tabs
+-	Select New Connection; the new data connections configuration page opens
+-	On the Destination type dropdown, select the AWS S3 option
+-	Give your Data Connection a name on the Name field
+-	Make sure the Enabled box is checked
+-	In the AWS console:
+    *	Navigate to IAM
+    *	Navigate to Identity Providers
+    *	Select Add Provider
+    *	Select OpenID Connect
+    *	In the form:
+        *	For the provider URL, input `https://login.microsoftonline.com/72f988bf-86f1-41af-91ab-2d7cd011db47/v2.0`
+        *	For the Audience, input `e12f8069-1801-4f61-9b5f-446d8bd57e8b`
+    *	Select Add Provider
+    *	Navigate back to IAM
+    *	Navigate to policies
+    *	Select Create policy
+    *	In the form:
+        *	Select JSON to switch to the JSON view.
+        *	Input the following policy: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "s3:*" ], "Resource": [ "arn:aws:s3:::test/*", "arn:aws:s3:::test" ] } ] }
+        *	Select Next
+        *	Enter a name for your policy – take note of it for later        
+        *	Select Create policy
+    *	Navigate back to IAM
+    *	Navigate to Roles
+    *	In the form:
+        *	Select Web Identity 
+        *	From the Identity provider dropdown, select the previously registered https://login.microsoftonline.com/72f988bf-86f1-41af-91ab-2d7cd011db47/v2.0 provider
+        *	From the Audience dropdown, select the previously registered e12f8069-1801-4f61-9b5f-446d8bd57e8b audience
+        *	Select Next
+        *	In the search field, enter the name of the previously registered policy
+        *	Check the box to the left of the policy
+        *	Select Next
+        *	Enter a name for the role – noting the name
+        *	Select Create role
+    *	Navigate to the general purpose S3 Bucket you want to use for your Connection
+    *	Select Properties
+    *	Scroll to the Tags section
+    *	Select Add new Tag
+    *	In the form:
+        *	For the key field, input playfab:titleids
+        *	For the value field, input your playfab TitleID
+        *	Select Save changes
+    *	Ensure you have your S3 Bucket name, Role ARN, and S3 Bucket Region used in the prior steps
+    *	Enter those into the appropriate fields in the Game Manager
+
+
 ## Manage connections
 
-The Data Connections overview (landing) page displays the available connections categorized as **enabled** or **disabled** as a **status**. You can have up to 3 enabled connections to the blob storage account at any time. 
-The Data Connections overview page can also be used to manage connections by selecting any Connections’ ellipsis (…). Two actions comprising Edit and Delete can be taken on the connections. 
+The Data Connections overview (landing) page displays the available connections categorized as **enabled** or **disabled** as a **status**. You can have up to three enabled connections to the blob storage account at any time. 
+You can also use the Data Connections overview page to manage connections. Select the ellipsis (...) next to any connection. You can take two actions: **Edit** and **Delete**.
 
 ![Screenshot of Modify Data Connections](media/modify-data-connections.png "Modify Data Connections")
diff --git a/playfab-docs/data-analytics/index.yml b/playfab-docs/data-analytics/index.yml
index cd03df823..5bce4b403 100644
--- a/playfab-docs/data-analytics/index.yml
+++ b/playfab-docs/data-analytics/index.yml
@@ -1,6 +1,6 @@
 ### YamlMime:Landing
 
-title: Azure PlayFab data and analytics documentation
+title: PlayFab data and analytics documentation
 summary: PlayFab data and analytics helps you manage game data. It provides reporting functions for generating weekly reports and trends, tools for segmenting data and running experiments, and data management tools for ingesting, exporting, and managing data. # < 160 chars
 
 metadata:
diff --git a/playfab-docs/data-analytics/ingest-data/ht-activate-deactivate-telemetry-keys.md b/playfab-docs/data-analytics/ingest-data/ht-activate-deactivate-telemetry-keys.md
index c1ee81760..0d0f52f2f 100644
--- a/playfab-docs/data-analytics/ingest-data/ht-activate-deactivate-telemetry-keys.md
+++ b/playfab-docs/data-analytics/ingest-data/ht-activate-deactivate-telemetry-keys.md
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 
 # How to activate or deactivate Telemetry Keys in Game Manager
 
-- Sign in to [Game Manager](https://developer.playfab.com/en-US/login).
+- Sign in to [Game Manager](https://developer.playfab.com).
 - Go to **My Studios and Titles** page and select your game title to display the dashboard.
 - Select **Data** from the menu on the left.
 - Select the **Telemetry Keys** tab.
@@ -25,11 +25,11 @@ To **deactivate** a Telemetry Key:
 - Expand the **three-dot menu** at the top right corner of the Telemetry Key. 
 - Select the **Deactivate** action.
 - Select the **Deactivate** button to confirm.
-- Once the Telemetry Key has been deactivated you will notice the status will change to Deactivated.
+- Once the Telemetry Key has been deactivated you'll notice the status changes to Deactivated.
 
 To **activate** a Telemetry Key:
 
 - Expand the **three-dot** menu at the top right corner of the Telemetry Key. 
 - Select the **Activate** action.
 - Select the **Activate** button to confirm. 
-The status will change to **Active**.
+The status changes to **Active**.
diff --git a/playfab-docs/data-analytics/ingest-data/ht-telemetry-keys-delete.md b/playfab-docs/data-analytics/ingest-data/ht-telemetry-keys-delete.md
index b1feea986..5871318e3 100644
--- a/playfab-docs/data-analytics/ingest-data/ht-telemetry-keys-delete.md
+++ b/playfab-docs/data-analytics/ingest-data/ht-telemetry-keys-delete.md
@@ -13,9 +13,9 @@ ms.localizationpriority: medium
 # How to delete Telemetry Keys in Game Manager
 
 > [!WARNING]
-> Deleting a Telemetry Key is not reversible. Please be aware that even if you create another key with the same name, the new key will be different from the original one that was deleted.
+> Deleting a Telemetry Key isn't reversible. Even if you create another key with the same name, the new key will be different from the original one that was deleted.
 
-- Sign in to [Game Manager](https://developer.playfab.com/en-US/login).
+- Sign in to [Game Manager](https://developer.playfab.com).
 - Go to **My Studios and Titles** page and select your game title to display the dashboard.
 - Select **Data** from the menu on the left.
 - Select the **Telemetry Keys** tab.
diff --git a/playfab-docs/data-analytics/ingest-data/opt-in-events.md b/playfab-docs/data-analytics/ingest-data/opt-in-events.md
new file mode 100644
index 000000000..8a8e990a7
--- /dev/null
+++ b/playfab-docs/data-analytics/ingest-data/opt-in-events.md
@@ -0,0 +1,115 @@
+---
+title: Enable or Disable Service Generated Events
+description: "Learn how to configure PlayStream, Telemetry, and disabled event types in PlayFab Game Manager to optimize data collection and automation."
+author: anaisnlawson
+ms.author: anaislawson
+ms.service: azure-playfab
+ms.topic: tutorial
+ms.date: 03/26/2026
+---
+
+# Enable or Disable Service Generated Events
+
+PlayFab events capture player and game data for analytics and automation. Understanding how to configure event types in Game Manager helps you optimize data collection costs while meeting your game's needs. All events that are [generated by PlayFab services](../../api-references/events/index.md) can be enabled or disabled using the Event Configuration settings.
+
+## Navigate to Event Configuration
+
+Event Configuration is located in the Settings area of Game Manager:
+
+1. Sign in to [Game Manager](https://developer.playfab.com).
+1. Select your title from the title list.
+1. In the left navigation, select **Settings** > **Event Configuration**.
+
+The Event Configuration page displays all available events organized by PlayFab product (Data, Economy, Multiplayer, etc.).
+
+## Understand event types
+
+Each event can be toggled on or off using the **event emission toggle**:
+
+- **On** — The event is processed. It defaults to **Telemetry** and can be changed to **PlayStream**.
+- **Off** — The event is ignored and not collected or processed.
+
+**PlayStream events:**
+
+- Process in real-time for immediate automation
+- Trigger rules, CloudScript, and segment updates
+- Higher metering cost per event
+- Best for LiveOps, rewards, and real-time reactions
+
+**Telemetry events:**
+
+- Send directly to data lake for analytics only
+- Lower metering cost per event
+- No real-time automation capabilities
+- Best for metrics, logging, and deferred analysis
+
+## Filter and search events
+
+The Event Configuration interface provides several ways to find specific events:
+
+- **Search:** Enter part of an event name or namespace in the search box.
+- **Filter by type:** Select the filter dropdown and choose **All event types**, **PlayStream**, or **Telemetry**.
+- **Apply:** Select the **Apply** button to apply both search text and filter selections across all product tabs.
+
+## Change event types
+
+Events are organized by PlayFab product (Data, Economy, Multiplayer, etc.). Each product tab shows the count of events it contains.
+
+To enable an event:
+
+1. Select the product tab containing your event.
+1. Locate the event you want to configure.
+1. Turn the **event emission toggle** to **On**. The event defaults to **Telemetry**.
+1. Optionally, change the emission type to **PlayStream** using the radio buttons.
+1. The change appears in the **Pending changes** sidebar until you save.
+
+To disable an event:
+
+1. Locate the event you want to disable.
+1. Turn the **event emission toggle** to **Off**.
+1. The change appears in the **Pending changes** sidebar until you save.
+
+> [!NOTE]
+> Some events have mandatory types that cannot be changed. These events show a disabled toggle and their required emission type.
+
+To view event data in Explorer, select the chart icon next to any event. This opens the Explorer Basic page in a new tab, filtered to the selected event.
+
+## Use bulk operations
+
+The command bar below the filters provides bulk enable and disable options organized by event type:
+
+**PlayStream:**
+
+- **Enable all** — Enables all events and sets them to PlayStream.
+- **Disable all** — Disables all events currently set to PlayStream.
+
+**Telemetry:**
+
+- **Enable all** — Enables all events and sets them to Telemetry.
+- **Disable all** — Disables all events currently set to Telemetry.
+
+Select **Discard Changes** on the far right of the command bar to revert all unsaved modifications.
+
+## Review and save configuration changes
+
+As you make changes, the **Pending changes** sidebar appears on the right side of the page. It displays all unsaved modifications grouped by product in collapsible sections. Each entry shows the event name, namespace, and the change from the previous type to the new type.
+
+To save your changes:
+
+1. Select **Save** in the page header.
+1. Review the confirmation dialog, which shows the total number of pending changes.
+1. Select **Save** to apply your changes.
+
+> [!NOTE]
+> Game Manager shows a confirmation dialog if you navigate away with unsaved changes.
+
+## Next steps
+
+After changing event types, verify that any automation rules still reference active PlayStream events and that your analytics reports reflect the updated configuration.
+
+Learn more about working with events in PlayFab:
+
+- [PlayStream Event Model reference](../../api-references/events/index.md)
+- [PlayStream events documentation](playstream-events.md)
+- [PlayStream actions and rules for automation](../acting-data/action-rules-overview.md)
+- [Telemetry events overview](telemetry-overview.md)
diff --git a/playfab-docs/data-analytics/ingest-data/playstream-events.md b/playfab-docs/data-analytics/ingest-data/playstream-events.md
index dad5103fc..8290f63f0 100644
--- a/playfab-docs/data-analytics/ingest-data/playstream-events.md
+++ b/playfab-docs/data-analytics/ingest-data/playstream-events.md
@@ -45,5 +45,5 @@ In the following table, you can find examples of these two types of events.
 
 |             | PlayFabGenerated Events | UserGenerated Events      |
 | ----------- | ----------- | ----------- |
-| Standard Schema | [player_logged_in](../../api-references/events/player-logged-in.md) <br> [entity_created](../../api-references/events/entity-created.md) | [client_focus_change](../../api-references/events/client-focus-change.md) <br> [client_session_start](../../api-references/events/client-session-start.md) |
+| Standard Schema | [player_logged_in](../../api-references/events/PlayerIdentity/player-logged-in.md) <br> [entity_created](../../api-references/events/PlayerIdentity/entity-created.md) | [client_focus_change](../../api-references/events/Session/client-focus-change.md) <br> [client_session_start](../../api-references/events/Session/client-session-start.md) |
 | Custom Schema | N/A | Free-style |
diff --git a/playfab-docs/data-analytics/ingest-data/sessions.md b/playfab-docs/data-analytics/ingest-data/sessions.md
index 75c7f1c25..19ed0308f 100644
--- a/playfab-docs/data-analytics/ingest-data/sessions.md
+++ b/playfab-docs/data-analytics/ingest-data/sessions.md
@@ -20,8 +20,8 @@ Session support is currently *only* available in Unity SDK. Support for our othe
 
 You'll need to have the **180829** version or newer. This SDK first introduces two new events that can be configured to be emitted from the client automatically:
 
-1. [client_session_start](../../api-references/events/client-session-start.md)
-2. [client_focus_change](../../api-references/events/client-focus-change.md)
+1. [client_session_start](../../api-references/events/Session/client-session-start.md)
+2. [client_focus_change](../../api-references/events/Session/client-focus-change.md)
 
 ## Logging and managing events
 
diff --git a/playfab-docs/data-analytics/ingest-data/telemetry-keys-qs.md b/playfab-docs/data-analytics/ingest-data/telemetry-keys-qs.md
index eb607c467..ac19e3e60 100644
--- a/playfab-docs/data-analytics/ingest-data/telemetry-keys-qs.md
+++ b/playfab-docs/data-analytics/ingest-data/telemetry-keys-qs.md
@@ -14,7 +14,7 @@ ms.localizationpriority: medium
 
 ## Creating Telemetry Keys in Game Manager
 
-- Sign in to [Game Manager](https://developer.playfab.com/en-US/login).
+- Sign in to [Game Manager](https://developer.playfab.com).
 - Go to **My Studios and Titles** page and select your game title to display the dashboard.
 - Select **Data** from the menu on the left.
 - Select the **Telemetry Keys** tab.
@@ -22,8 +22,8 @@ ms.localizationpriority: medium
 - Fill the **Key** field. 
 - Select **Create telemetry key**.
 
-Here is an example of how the newly created Telemetry Key should look like:
+Here's an example of how the newly created Telemetry Key should look like:
 
 ![New telemetry key](media/new-telemetry-key.png)
 
-Once the Telemetry Key has been created, you can use it from your game client when calling [WriteTelemetryEvents API](/rest/api/playfab/events/play-stream-events/write-telemetry-events) by including it via HTTP header X-TelemetryKey as called out in the Overview page. You can look at an example here: [Telemetry Keys Overview](telemetry-keys-overview.md) in the Section **Specifying Entities for Events**s
\ No newline at end of file
+Once the Telemetry Key has been created, you can use it from your game client when calling [WriteTelemetryEvents API](/rest/api/playfab/events/play-stream-events/write-telemetry-events) by including it via HTTP header X-TelemetryKey as called out in the Overview page. You can look at an example here: [Telemetry Keys Overview](telemetry-keys-overview.md) in the Section **Specifying Entities for Events**.
\ No newline at end of file
diff --git a/playfab-docs/data-analytics/ingest-data/toc.yml b/playfab-docs/data-analytics/ingest-data/toc.yml
index 0d9586bd7..a6e069b0c 100644
--- a/playfab-docs/data-analytics/ingest-data/toc.yml
+++ b/playfab-docs/data-analytics/ingest-data/toc.yml
@@ -41,3 +41,5 @@ items:
       href: ht-telemetry-keys-delete.md
     - name: Activate or Deactivate Telemetry Keys
       href: ht-activate-deactivate-telemetry-keys.md
+    - name: Enable or Disable Service Generated Events
+      href: opt-in-events.md
diff --git a/playfab-docs/data-analytics/learn-data/churn-prediction/churn-prediction-quickstart.md b/playfab-docs/data-analytics/learn-data/churn-prediction/churn-prediction-quickstart.md
index 231a1aae2..4970ec68c 100644
--- a/playfab-docs/data-analytics/learn-data/churn-prediction/churn-prediction-quickstart.md
+++ b/playfab-docs/data-analytics/learn-data/churn-prediction/churn-prediction-quickstart.md
@@ -14,7 +14,7 @@ ms.localizationpriority: medium
 
 ## Prerequisites
 
-1. Sign in to [PlayFab portal](https://playfab.com).
+1. Sign in to [PlayFab portal](https://developer.playfab.com).
 2. Navigate to your title.
 
 ## Create a Churn Prediction segment and apply mitigation strategy
diff --git a/playfab-docs/data-analytics/learn-data/data-explorer/getting-started-with-data-explorer-basic.md b/playfab-docs/data-analytics/learn-data/data-explorer/getting-started-with-data-explorer-basic.md
index 24f5dde9e..d42f33acc 100644
--- a/playfab-docs/data-analytics/learn-data/data-explorer/getting-started-with-data-explorer-basic.md
+++ b/playfab-docs/data-analytics/learn-data/data-explorer/getting-started-with-data-explorer-basic.md
@@ -58,7 +58,7 @@ The table shows the Event Name, Timestamp (UTC), Player ID, and Event Data (via
 #### What's the sum of order totals this week?
 ![Order totals sum this week](media/ExplorerBasic_Query_3.png)
 
-#### Are Playfab limits being exceeded?
+#### Are PlayFab limits being exceeded?
 ![Title limits exceeded this week](media/ExplorerBasic_Query_4.png)
 
 ### Multi Condition Queries
diff --git a/playfab-docs/data-analytics/learn-data/data-explorer/quickstart.md b/playfab-docs/data-analytics/learn-data/data-explorer/quickstart.md
index 0be0d56a3..083331cba 100644
--- a/playfab-docs/data-analytics/learn-data/data-explorer/quickstart.md
+++ b/playfab-docs/data-analytics/learn-data/data-explorer/quickstart.md
@@ -19,7 +19,7 @@ ms.localizationpriority: medium
 
 To query the data in basic mode:
 
-1. Log in to the [PlayFab Game Manager](https://developer.playfab.com/en-us/login).
+1. Log in to the [PlayFab Game Manager](https://developer.playfab.com).
 2. Select your Title.
 3. In the left navigation column, select **Data**.
 4. Select the **Data Explorer (basic)** tab at the top of the page. 
@@ -30,7 +30,7 @@ To learn how to author custom Basic queries, see the [Getting Started with Data
 
 To query the data in advanced mode
 
-1. Log in to the [PlayFab Game Manager](https://developer.playfab.com/en-us/login).
+1. Log in to the [PlayFab Game Manager](https://developer.playfab.com).
 2. Select your Title.
 3. In the left navigation column, select **Data**.
 4. Select the **Data Explorer (advanced)** tab at the top of the page. 
diff --git a/playfab-docs/data-analytics/learn-data/reports/daily-email-report.md b/playfab-docs/data-analytics/learn-data/reports/daily-email-report.md
index f4d693597..3a79abaab 100644
--- a/playfab-docs/data-analytics/learn-data/reports/daily-email-report.md
+++ b/playfab-docs/data-analytics/learn-data/reports/daily-email-report.md
@@ -25,7 +25,7 @@ Titles are subscribed to the email by default but you'll only receive the email
 
 To unsubscribe from this list follow these steps:
 
-- Sign in to [Game Manager](https://developer.playfab.com/en-US/login).
+- Sign in to [Game Manager](https://developer.playfab.com).
 - Go to **My Studios and Titles** page and select your game title to display the dashboard.
 - Select the **Settings** icon next to the Title name on the upper left side.
 - Select **Title Settings** tab.
diff --git a/playfab-docs/data-analytics/learn-data/reports/real-time-analytics-tutorial.md b/playfab-docs/data-analytics/learn-data/reports/real-time-analytics-tutorial.md
index ca9c09d99..9d6120363 100644
--- a/playfab-docs/data-analytics/learn-data/reports/real-time-analytics-tutorial.md
+++ b/playfab-docs/data-analytics/learn-data/reports/real-time-analytics-tutorial.md
@@ -19,7 +19,7 @@ This tutorial explains end-to-end steps on how to integrate **PlayFab** and **Fa
 ### Prerequisites
 
 * To successfully complete this tutorial, you need a Microsoft Fabric-enabled [capacity](/fabric/enterprise/licenses#capacity). For a limited time, you can [sign up for the Microsoft Fabric (Preview) trial](/fabric/get-started/fabric-trial).
-* A PlayFab developer account. Sign up at [playfab.com](https://developer.playfab.com/en-US/sign-up)
+* A PlayFab developer account. Sign up at [playfab.com](https://developer.playfab.com)
 * Microsoft PowerBI Desktop installed. See [Get started with Power BI Desktop](/power-bi/fundamentals/desktop-getting-started#install-and-run-power-bi-desktop)
 
 ## Create a Fabric workspace
diff --git a/playfab-docs/data-analytics/learn-data/trends/trends-overview.md b/playfab-docs/data-analytics/learn-data/trends/trends-overview.md
index 5d67ee5d1..e913c0737 100644
--- a/playfab-docs/data-analytics/learn-data/trends/trends-overview.md
+++ b/playfab-docs/data-analytics/learn-data/trends/trends-overview.md
@@ -14,29 +14,29 @@ ms.localizationpriority: medium
 
 The Trends feature is a collection of graphical representations of game analytics key performance analytics (KPIs) metrics that acts as your gateway to valuable insights and strategic decision-making. 
 
-Simply navigate to the Dashboard section of the Analyze Tab in Game Manager to view industry–standard metrics about your game. 
+Navigate to the Dashboard section of the Analyze Tab in Game Manager to view industry–standard metrics about your game. 
 
-Trends allows you to evaluate daily historical performance across six KPIs including daily & monthly active players, new players, screentime, retention, and revenue. You can effortlessly compare different time periods from as short as one week to a full 6 months, enabling you to measure the impact of your efforts and make data-driven decisions. 
+Trends allow you evaluate daily historical performance across six KPIs including daily & monthly active players, new players, screen time, retention, and revenue. You can effortlessly compare different time periods from as short as one week to a full six months, enabling you to measure the impact of your efforts and make data-driven decisions. 
 With the ability to break down KPIs by platform and region and segments as dimensions, you can identify top performers, focus on strategic markets, and uncover areas for improvement. 
 
 ## Trends metrics
 
 **Active Players**
-- **Daily Active Players (DAU)**: Number of unique players seen in the game per day based on the [player_logged_in](../../../api-references/events/player-logged-in.md) event. 
-- **Monthly Active Players (MAU) Rolling 30**: Number of unique players seen in the game during the span of the last 30 days based on the [player_logged_in event](../../../api-references/events/player-logged-in.md) event. 
+- **Daily Active Players (DAU)**: Number of unique players seen in the game per day based on the [player_logged_in](../../../api-references/events/PlayerIdentity/player-logged-in.md) event. 
+- **Monthly Active Players (MAU) Rolling 30**: Number of unique players seen in the game during the span of the last 30 days based on the [player_logged_in event](../../../api-references/events/PlayerIdentity/player-logged-in.md) event. 
 
 **New Players** 
-- **New Players**: The number of players that were seen in the game for the first time based on the [player_added_title](../../../api-references/events/player-added-title.md) event. 
+- **New Players**: The number of players that were seen in the game for the first time based on the [player_added_title](../../../api-references/events/PlayerIdentity/player-added-title.md) event. 
 
 **Screen Time**
-- **Average Duration**: Average length of time that a player has the game on screen and in focus per day. This is based on the [client_focus_change](../../../api-references/events/client-focus-change.md) event. 
-- **Average On-Screen** Intervals: Average number of times a player has the game on screen and in focus per day. This is based on the [client_focus_change](../../../api-references/events/client-focus-change.md) event. 
+- **Average Duration**: Average length of time that a player has the game on screen and in focus per day. This is based on the [client_focus_change](../../../api-references/events/Session/client-focus-change.md) event. 
+- **Average On-Screen** Intervals: Average number of times a player has the game on screen and in focus per day. This is based on the [client_focus_change](../../../api-references/events/Session/client-focus-change.md) event. 
 
 **New User Retention**
-- **Nth Day New User Retention (Classical Retention)**: Percentage of players seen specifically on the Nth Day after they first played the game based on the [player_added_title](../../../api-references/events/player-added-title.md) and [player_logged_in](../../../api-references/events/player-logged-in.md) events. 
+- **Nth Day New User Retention (Classical Retention)**: Percentage of players seen specifically on the Nth Day after they first played the game based on the [player_added_title](../../../api-references/events/PlayerIdentity/player-added-title.md) and [player_logged_in](../../../api-references/events/PlayerIdentity/player-logged-in.md) events. 
 
 **Transaction Revenue**  
-- **Revenue**: Total revenue (USD) per day generated from in-app purchases that use the PlayFab economy APIs. This is based on the [player_realmoney_purchase](../../../api-references/events/player-realmoney-purchase.md) event.
+- **Revenue**: Total revenue (USD) per day generated from in-app purchases that use the PlayFab economy APIs. This is based on the [player_realmoney_purchase](../../../api-references/events/Player/player-realmoney-purchase.md) event.
 
 ## See also
 
diff --git a/playfab-docs/data-analytics/legacy/connectivity/connecting-python-to-insights.md b/playfab-docs/data-analytics/legacy/connectivity/connecting-python-to-insights.md
index 45187ddff..18904a8d4 100644
--- a/playfab-docs/data-analytics/legacy/connectivity/connecting-python-to-insights.md
+++ b/playfab-docs/data-analytics/legacy/connectivity/connecting-python-to-insights.md
@@ -25,7 +25,7 @@ You need a PlayFab account or user for which the authentication provider is set
 
 To verify that the account, or user, is set to use the Microsoft authentication provider:
 
-* Visit the PlayFab [log in page](https://developer.playfab.com/en-us/login).
+* Visit the PlayFab [log in page](https://developer.playfab.com).
 * Select **Sign in with Microsoft** to access your PlayFab account.
 
 If you can sign in, then the account is set to use the Microsoft authentication provider.
diff --git a/playfab-docs/data-analytics/legacy/insights/best-practices.md b/playfab-docs/data-analytics/legacy/insights/best-practices.md
index d474eae28..21559ac22 100644
--- a/playfab-docs/data-analytics/legacy/insights/best-practices.md
+++ b/playfab-docs/data-analytics/legacy/insights/best-practices.md
@@ -15,7 +15,7 @@ ms.localizationpriority: medium
 Here we examine some best practices for using PlayFab Insights and address the most frequently asked questions.
 
 > [!NOTE]
-> PlayFab Insights Management was deprecated on December 11th, 2023. We recommend using [Azure Data Explorer (ADX) Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Insights**, continue to see this article for best practice details. For more information, see [Insights Deprecation Blog](https://developer.microsoft.com/en-us/games/articles/2023/09/playfab-insights-management-to-be-deprecated-starting-december-11/).
+> PlayFab Insights Management will be retired 3/31/2026. We recommend using [Data Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Insights**, continue to see this article for best practice details. For more information, see [Insights Retirement Blog](https://developer.microsoft.com/en-us/games/articles/2025/11/playfab-insights-management-getplayerinsegment-apis-retired-starting-march-31/).
 
 ## Best Practices
 
@@ -103,7 +103,7 @@ Here we examine some best practices for using PlayFab Insights and address the m
      | Events per entity | 8,000 per second | Exceeding this limit results in a `PerEntityEventRateLimitExceeded` error. An entity most often represents an individual player, but can also be a player group or title. | 
      | Max payload size  | 10,240 bytes (10 KB) | |
 
-     If you run into any of these limits, contact the Playfab Support team for assistance. In the upper right-hand corner of Game Manager select the question mark icon, then select **Contact Us**.
+     If you run into any of these limits, contact the PlayFab Support team for assistance. In the upper right-hand corner of Game Manager select the question mark icon, then select **Contact Us**.
 
 ### I get an error "Query execution has exceeded the allowed limits" when I try to run a query
 
diff --git a/playfab-docs/data-analytics/legacy/insights/export.md b/playfab-docs/data-analytics/legacy/insights/export.md
index 13c280946..2b6704458 100644
--- a/playfab-docs/data-analytics/legacy/insights/export.md
+++ b/playfab-docs/data-analytics/legacy/insights/export.md
@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 # Exporting Data
 
 > [!NOTE] 
-> PlayFab Insights Management was deprecated on December 11th, 2023. We recommend using [Azure Data Explorer (ADX) Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Event Export**, continue to see this article for implementation details. For more information, see [Insights Deprecation Blog](https://developer.microsoft.com/en-us/games/articles/2023/09/playfab-insights-management-to-be-deprecated-starting-december-11/).
+> PlayFab Insights Management will be retired 3/31/2026. We recommend using [Data Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Event Export**, continue to see this article for best practice details. For more information, see [Insights Retirement Blog](https://developer.microsoft.com/en-us/games/articles/2025/11/playfab-insights-management-getplayerinsegment-apis-retired-starting-march-31/). Further clarification on the impact to Event export: [Event Export Impact as part of Insights Management Retirement](https://developer.microsoft.com/en-us/games/articles/2026/02/event-export-impact-playfab-insights-management-retirement/)
 
 Event Export is the primary mechanism for exporting data from your Insights data cluster without querying. Event Export can be reached under the data section of PlayFab Game Manager. The number of distinct export commands you can run is tied to your performance level.
 
diff --git a/playfab-docs/data-analytics/legacy/insights/management-commands.md b/playfab-docs/data-analytics/legacy/insights/management-commands.md
index 40cdc39ed..fa06a1fea 100644
--- a/playfab-docs/data-analytics/legacy/insights/management-commands.md
+++ b/playfab-docs/data-analytics/legacy/insights/management-commands.md
@@ -17,7 +17,7 @@ Insights management commands allow users to express more control over or to gath
 2. Data Control - These commands allow users to create and drop custom tables, ingest local and cloud data, and purge data from their DB
 
 > [!NOTE]
-> PlayFab Insights Management was deprecated on December 11th, 2023. We recommend using [Azure Data Explorer (ADX) Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Insights**, continue to see this article for management command details. For more information, see [Insights Deprecation Blog](https://developer.microsoft.com/en-us/games/articles/2023/09/playfab-insights-management-to-be-deprecated-starting-december-11/).
+> PlayFab Insights Management will be retired 3/31/2026. We recommend using [Data Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Insights**, continue to see this article for best practice details. For more information, see [Insights Retirement Blog](https://developer.microsoft.com/en-us/games/articles/2025/11/playfab-insights-management-getplayerinsegment-apis-retired-starting-march-31/).
 
 Some commands aren't available in evaluation mode.
 
diff --git a/playfab-docs/data-analytics/legacy/insights/overview.md b/playfab-docs/data-analytics/legacy/insights/overview.md
index 22fe2f46f..46112737e 100644
--- a/playfab-docs/data-analytics/legacy/insights/overview.md
+++ b/playfab-docs/data-analytics/legacy/insights/overview.md
@@ -12,48 +12,48 @@ ms.localizationpriority: medium
 # What is PlayFab Insights?
 
 > [!NOTE] 
-> PlayFab Insights Management was deprecated on December 11th, 2023. We recommend using [Azure Data Explorer (ADX) Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Insights**, continue to see this article for feature details. For more information, see [Insights Deprecation Blog](https://developer.microsoft.com/en-us/games/articles/2023/09/playfab-insights-management-to-be-deprecated-starting-december-11/).
+> PlayFab Insights Management will be retired 3/31/2026. We recommend using [Data Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Insights**, continue to see this article for best practice details. For more information, see [Insights Retirement Blog](https://developer.microsoft.com/en-us/games/articles/2025/11/playfab-insights-management-getplayerinsegment-apis-retired-starting-march-31/).
 
-PlayFab Insights is a managed data environment, giving you instant access to your games data without the need for additional engineering. Unlike other hosted data solutions Insights requires no setup, no GDPR work, and no extra engineering. Simply use PlayFab services and your data is available. Automatically ingest and scale, connect external visualization tools, and query freely. 
+PlayFab Insights is a managed data environment, giving you instant access to your games data without the need for additional engineering. Unlike other hosted data solutions Insights requires no setup, no GDPR work, and no extra engineering. Use PlayFab services and your data is available. Automatically ingest and scale, connect external visualization tools, and query freely. 
 
-## Key Features
+## Key features
 Insights key features revolve around data cluster management, data retention, ingestion options, and connectivity to outside tools.
 
-### Automatic Ingestion
+### Automatic ingestion
 PlayFab services automatically fire Playstream events. Any events fired by PlayFab services or created through our SDK are automatically routed to your Insights cluster. There's no need to worry about defining schema or DDL from automatic events. However, the option for sending your own custom events is available. For more information about sending custom events, see the [Custom event overview](../../ingest-data/playstream-overview.md) of Generating PlayStream events. 
 
-### Change Your Performance Level To Meet Your Needs
+### Change your performance level to meet your needs
 ![Insights Slider](media/insights-slider.png)
 
 Match your cluster performance to your needs minute by minute. Slide your performance level up or down or alternatively schedule your cluster to have different performance levels automatically using scheduled tasks. See [Performance Level & Retention](performance-retention.md) for details.
 
-### Schedule Your Performance Level
+### Schedule your performance level
 ![Scheduled Scaling](media/insights-schedule.png)
 
 Use standard cron expressions to automatically scale your cluster up and down during known times. See [Scheduled Scaling](scheduled-scaling.md) for details.
 
-### Keep Your Data as Long as You Need
+### Keep your data as long as you need
 ![Storage and Retention](media/insights-retention.png)
 
 Never delete your data or clear your data out every 30 days, whatever is needed for your studio. See [Performance Level & Retention](performance-retention.md) for details.
 
-### Connect Outside Tools
+### Connect outside tools
 Connect Power BI or Grafana for visualization, automate data jobs with Python or Azure Data Factory, explore your data with Azure Data Explorer. See [Connectivity](../connectivity/index.md) for details.
 
-### Export Original or Cleaned Data
+### Export original or cleaned data
 Use the automated export service to export all your data to Azure Blob or AWS S3. See [Exporting Data](export.md) for details.
 
-### Bring Your Own Datasets
+### Bring your own datasets
 Ingest your own custom datasets with [Management Commands](management-commands.md). Merge your custom Playstream events, standard Playstream events, and custom uploaded data to create more robust datasets.
 
-### GDPR Compliant
-Standard reporting is tracked and GDPR compliant. Call the playfab GDPR delete request and we'll do the rest. Have custom data you need to delete? No problem, use the [Management Commands](management-commands.md) to maintain your custom data.
+### GDPR compliant
+Standard reporting is tracked and GDPR compliant. Call the PlayFab GDPR delete request and we'll do the rest. Have custom data you need to delete? No problem, use the [Management Commands](management-commands.md) to maintain your custom data.
 
-## Getting Started with PlayFab Insights
-PlayFab Insights is available to all studios right out of the box. The only thing needed to get started is some data. Implement any PlayFab service and you get playstream events automatically sent to your *Insights* or you [can send telemetry directly using PlayFab API calls](xref:titleid.playfabapi.com.events.playstreamevents). Once you have some data check out [Data Explorer](../../export-data/data-connection-quickstart.md).
+## Getting started with PlayFab Insights
+PlayFab Insights is available to all studios right out of the box. The only thing needed to get started is some data. Implement any PlayFab service and you get playstream events automatically sent to your *Insights* or you [can send telemetry directly using PlayFab API calls](xref:titleid.playfabapi.com.events.playstreamevents). After you have some data, check out [Data Explorer](../../export-data/data-connection-quickstart.md).
 
 ## What services are powered by Insights?
-PlayFab Insights powers various features and functionality across Game Manager. Adjusting the performance level affects the following across your title:
+PlayFab Insights powers various features and functionality across Game Manager. Adjusting the performance level affects the following areas across your title:
 * Data
   * Data Explorer (Preview)
   * Event Export
diff --git a/playfab-docs/data-analytics/legacy/insights/performance-retention.md b/playfab-docs/data-analytics/legacy/insights/performance-retention.md
index d932d2626..04c537c56 100644
--- a/playfab-docs/data-analytics/legacy/insights/performance-retention.md
+++ b/playfab-docs/data-analytics/legacy/insights/performance-retention.md
@@ -1,7 +1,7 @@
 ---
 title: Performance and retention
 author: joannaleecy
-description: Performance and retention for playfab insights
+description: Performance and retention for PlayFab insights
 ms.author: jenelleb
 ms.date: 02/28/2020
 ms.topic: article
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 # Insights Management: Performance Levels & Retention
 
 > [!NOTE]
-> PlayFab Insights Management was deprecated on December 11th, 2023. We recommend using [Azure Data Explorer (ADX) Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Performance Levels & Retention**, continue to see this article for implementation details. For more information, see [Insights Deprecation Blog](https://developer.microsoft.com/en-us/games/articles/2023/09/playfab-insights-management-to-be-deprecated-starting-december-11/).
+> PlayFab Insights Management will be retired 3/31/2026. We recommend using [Data Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Performance Levels & Retention**, continue to see this article for best practice details. For more information, see [Insights Retirement Blog](https://developer.microsoft.com/en-us/games/articles/2025/11/playfab-insights-management-getplayerinsegment-apis-retired-starting-march-31/).
 
 PlayFab Insights provides studios the ability to change the performance characteristics of their data system. Controls are located in **Management** under the data section in Game Manager.
 
@@ -31,7 +31,7 @@ The **Performance Level** slider is used to select a new performance level. The
 ### Is performance level access limited?
 Yes. Every title begins at Performance Level 1, a free tier of service that is included in all PlayFab offerings. Live titles can change their performance level at will, however, titles in Development Mode must either enable paid insights features or launch to access performance levels greater than 1.
 
-To enable paid Insights features while a title is in development mode:
+To enable paid Insights features while a title is in Development Mode:
 
 1. Sign in to [developer.playfab.com](https://developer.playfab.com)
 2. Select a title in Development Mode to enter the Title Overview page
diff --git a/playfab-docs/data-analytics/legacy/insights/pricing.md b/playfab-docs/data-analytics/legacy/insights/pricing.md
index a2e7a435b..d74b47b39 100644
--- a/playfab-docs/data-analytics/legacy/insights/pricing.md
+++ b/playfab-docs/data-analytics/legacy/insights/pricing.md
@@ -13,18 +13,18 @@ ms.localizationpriority: medium
 # Insights pricing
 
 > [!NOTE]
-> PlayFab Insights Management was deprecated on December 11th, 2023. We recommend using [Azure Data Explorer (ADX) Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Insights**, continue to see this article for pricing details. For more information, see [Insights Deprecation Blog](https://developer.microsoft.com/en-us/games/articles/2023/09/playfab-insights-management-to-be-deprecated-starting-december-11/).
+> PlayFab Insights Management will be retired 3/31/2026. We recommend using [Data Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Insights**, continue to see this article for best practice details. For more information, see [Insights Retirement Blog](https://developer.microsoft.com/en-us/games/articles/2025/11/playfab-insights-management-getplayerinsegment-apis-retired-starting-march-31/).
 
-The total combined usage of Insights features are billed in a virtual currency called "Insights Credits". Insight Credits are derived from conversion rates for usage of each Insight services.
+The total combined usage of Insights features is billed in a virtual currency called "Insights Credits." Insight Credits are derived from conversion rates for usage of each Insight services.
 
-The Standard and Premium pricing plans include a number of free monthly Insights credits. If usage exceeds the number of free credits, any additional credits are billed at the rate specified on your plan. The Pay-as-you-go pricing plan does not include free credits, so each credit is billed at the rate specified in the plan. For more information on the number of free credits and additional credit rates included in each plan, see [PlayFab pricing](http://playfab.com/pricing).
+The Standard and Premium pricing plans include a number of free monthly Insights credits. If usage exceeds the number of free credits, any extra credits are billed at the rate specified on your plan. The Pay-as-you-go pricing plan doesn't include free credits, so each credit is billed at the rate specified in the plan. For more information on the number of free credits and additional credit rates included in each plan, see [PlayFab pricing](http://playfab.com/pricing).
 
 ## Insights Performance
 Each title is set to a chosen performance level that is billed to the minute (Insights Credits Per Hour / 60). The cost in credits for each performance level is located at the bottom of the table on the Insights Management page:
 ![Insights Slider](media/performance-level2.png)
 
 > [!IMPORTANT] 
-> All MAU-based pricing plans will be converted to a usage-based pricing plan on 11/01/2020. As part of the transition, a small number of titles will be placed on a paid Insights Performance level to maintain their current functionality. However, if a title would like to reduce the performance level (and thus cost) while also accepting a decrease in performance, the performance level can be adjusted on the Insights Management page in Game Manager using the above table. 
+> All MAU-based pricing plans will be converted to a usage-based pricing plan on November 1, 2020. As part of the transition, a few titles will be placed on a paid Insights Performance level to maintain their current functionality. However, if a title would like to reduce the performance level (and thus cost) while also accepting a decrease in performance, the performance level can be adjusted on the Insights Management page in Game Manager using the above table. 
 
 
 ## Retention
@@ -32,12 +32,12 @@ Data retention is billed in Terabyte months. Every day the end of day storage si
 
 ## Pricing example
 
-Below is an example scenario illustrating how one month of Insights billing is calculated for a studio:
+The following is an example scenario illustrating how one month of Insights billing is calculated for a studio:
 
 In April, a studio used performance level 4 from 9AM to 5PM each weekday and scaled down to performance level 2 at nights and on weekends. April has 21 weekdays and 9 weekend days, which works out to: 
 * 21 days at performance level 4, for 8 hours
 * 21 days at performance level 2, for 16 hours
-* 9 days at performance level 2, for 24 hours
+* Nine days at performance level 2, for 24 hours
 
 The credit rate per hour for each of these levels is:
 * performance level 2 = 1 credits/hour
@@ -54,4 +54,4 @@ Starting the month with no stored data, the studio added 1 TB of data every othe
 Thus, the studio's total monthly cost for Insights performance and data retention is 1,974 credits.
 
 ## Row Write Overages   
-Each Insights Performance level has an allotted number of writes per second to the data cluster. For customers not in development mode, going beyond the number of row writes for your performance level triggers row write overages instead of event throttling. Row write overages are charged at 1 credit per 2.7 million (2,700,000) rows written. This pricing is designed to allow for specific ingestion scenarios where it may be more cost effective to have row write overages instead of raising the Insights performance level.  
+Each Insights Performance level has an allotted number of writes per second to the data cluster. For customers not in Development Mode, going beyond the number of row writes for your performance level triggers row write overages instead of event throttling. Row write overages are charged at one credit per 2.7 million (2,700,000) rows written. This pricing is designed to allow for specific ingestion scenarios where it may be more cost effective to have row write overages instead of raising the Insights performance level.  
diff --git a/playfab-docs/data-analytics/legacy/insights/scheduled-scaling.md b/playfab-docs/data-analytics/legacy/insights/scheduled-scaling.md
index 6fb59b57c..4c7ee839d 100644
--- a/playfab-docs/data-analytics/legacy/insights/scheduled-scaling.md
+++ b/playfab-docs/data-analytics/legacy/insights/scheduled-scaling.md
@@ -1,7 +1,7 @@
 ---
 title: Scheduled Scaling
 author: joannaleecy
-description: Scheduled Scaling for playfab insights
+description: Scheduled Scaling for PlayFab insights
 ms.author: jenelleb
 ms.date: 02/28/2020
 ms.topic: article
@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 # Insights Scheduled Scaling
 
 > [!NOTE]
-> PlayFab Insights Management was deprecated on December 11th, 2023. We recommend using [Azure Data Explorer (ADX) Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Scheduled Scaling**, continue to see this article for implementation details. For more information, see [Insights Deprecation Blog](https://developer.microsoft.com/en-us/games/articles/2023/09/playfab-insights-management-to-be-deprecated-starting-december-11/).
+> PlayFab Insights Management will be retired 3/31/2026. We recommend using [Data Connections](../../export-data/data-connection-adx.md) to manage your performance and cost going forward. If your title is still using **Scheduled Scaling**, continue to see this article for best practice details. For more information, see [Insights Retirement Blog](https://developer.microsoft.com/en-us/games/articles/2025/11/playfab-insights-management-getplayerinsegment-apis-retired-starting-march-31/).
 
 The Insights Performance Level can be set to scale up and down at specific times of the day. This allows a studio to match their analytics resources demand to their supply and optimize costs. Scheduled Tasks can be found under automation in Game Manager. It can also be reached by clicking the *Add Insights scaling scheduled task* button in Insights Management. 
 
diff --git a/playfab-docs/data-analytics/privacy-compliance/gdpr-exporting-player-data.md b/playfab-docs/data-analytics/privacy-compliance/gdpr-exporting-player-data.md
index 76fee5f1f..fd7ce46f4 100644
--- a/playfab-docs/data-analytics/privacy-compliance/gdpr-exporting-player-data.md
+++ b/playfab-docs/data-analytics/privacy-compliance/gdpr-exporting-player-data.md
@@ -41,7 +41,7 @@ This API immediately returns a `JobReceiptId`, which you should store in your re
 
 Upon completion of the export, an email containing the export download link will be sent to the notification email address configured for the title.
 
-The completion of the task will also trigger a [`player_data_exported` PlayStream event](../../api-references/events/player-data-exported.md). The event contains the `JobReceiptId` as a property, as well as the `ExportDownloadUrl` property, which provides access to the exported data. Using either [Automation Rules with Azure Functions](../../live-service-management/service-gateway/automation/cloudscript-af/quickstart.md#azure-functions-in-automation-rules) or [Webhooks](../acting-data/webhooks-overview.md), you can register to receive these events on an endpoint of your choosing and process as needed. 
+The completion of the task will also trigger a [`player_data_exported` PlayStream event](../../api-references/events/PlayerIdentity/player-data-exported.md). The event contains the `JobReceiptId` as a property, as well as the `ExportDownloadUrl` property, which provides access to the exported data. Using either [Automation Rules with Azure Functions](../../live-service-management/service-gateway/automation/cloudscript-af/quickstart.md#azure-functions-in-automation-rules) or [Webhooks](../acting-data/webhooks-overview.md), you can register to receive these events on an endpoint of your choosing and process as needed. 
 
 The following example is how to use the Admin API with the [C# SDK](../../sdks/c-sharp/index.md). If you would like to use a different SDK, select one from the list of [PlayFab SDKs](../../sdks/playfab-sdk-intro.md).
 
diff --git a/playfab-docs/demo-game/overview.md b/playfab-docs/demo-game/overview.md
index 566b46339..42b3d03c1 100644
--- a/playfab-docs/demo-game/overview.md
+++ b/playfab-docs/demo-game/overview.md
@@ -12,9 +12,9 @@ ms.localizationpriority: medium
 
 # Demo game: Winter Starfall
 
-Winter Starfall is a game developed by PlayFab to showcase our different features and provide a way to explore how they are implemented in a live game.
+Winter Starfall is a game developed by PlayFab to showcase our different features and provide a way to explore how they're implemented in a live game.
 
-The game is available to play at [WinterStarfall.com](https://winterstarfall.com/). If you already have a PlayFab developer account you can also access it through the developer portal on the My Studios and Titles page.
+The game is available to play at [WinterStarfall.com](https://winterstarfall.com/). If you already have a PlayFab developer account, you can also access it through the developer portal on the My Studios and Titles page.
 
 ![game manager homepage showing demo games](media/demo-games-overview.png)
 
@@ -27,16 +27,16 @@ The game is built as a web app and uses APIs from the PlayFab SDK along with Pla
 
 ## Additional demo features
 
-Winter Starfall comes with features that make it easier to see what is going on 'under the hood' with PlayFab. The game is available for anyone to play, but to get the full use of these features you'll need to sign up for a [free developer account](https://developer.playfab.com/en-us/sign-up).
+Winter Starfall comes with features that make it easier to see what is going on 'under the hood' with PlayFab. The game is available for anyone to play, but to get the full use of these features you need to sign up for a [free developer account](https://developer.playfab.com).
 
-Next to the profile icon in the upper right there is a PlayFab icon that will open the PlayFab activity sidebar when clicked.
+Next to the profile icon in the upper right there's a PlayFab icon that opens the PlayFab activity sidebar when selected.
 
 ![winter-starfall-profile](media/winter-starfall-activity.png)
 
-1. The activity sidebar shows a list of API calls that updates as you play the game. Each API call is tagged and color coded to indicate which PlayFab SDK it is related to.
+1. The activity sidebar shows a list of API calls that updates as you play the game. Each API call is tagged and color coded to indicate which PlayFab SDK it's related to.
 1. You can select one of the API calls in the list to view the full API request and response.
-1. Selecting **View title F8941** will open the title in Game Manager where you can see how the different features are configured. This is where you'll be prompted to sign in with a PlayFab developer account.
-1. **Clear** will remove all the current notifications from the activity bar.
+1. Selecting **View title F8941** opens the title in Game Manager where you can see how the different features are configured. This step is where you're prompted to sign in with a PlayFab developer account.
+1. **Clear** removes all the current notifications from the activity bar.
 
 <!---
 You'll also notice throughout the game these various callouts. Each of these indicates where a specific PlayFab feature is used to power a certain aspect of the game and hovering over will show more information and take you to the related pages in Game Manager.
@@ -45,7 +45,7 @@ You'll also notice throughout the game these various callouts. Each of these ind
 --->
 
 > [!NOTE]
-> You can play the demo game at any time, but to access Game Manager you'll need to sign up for a [free developer account](https://developer.playfab.com/en-us/sign-up).
+> You can play the demo game at any time, but to access Game Manager you need to sign up for a [free developer account](https://developer.playfab.com).
 
 ## Included PlayFab features
 
@@ -53,13 +53,13 @@ The following section breaks down in more detail the different PlayFab features
 
 ### Authentication
 
-The first thing that happens in any PlayFab game is logging in a player, which returns an authentication token that is required for all subsequent API calls. Winter Starfall supports multiple forms of recoverable login with email, Microsoft (via OpenID), Google, and Facebook. The [source code and scenarios tutorial](source-code-and-best-practices.md) gives an in depth walkthrough of the login flow and best practices for player authentication.
+The first thing that happens in any PlayFab game is logging in a player, which returns an authentication token that is required for all subsequent API calls. Winter Starfall supports multiple forms of recoverable sign-in with email, Microsoft (via OpenID), Google, and Facebook. The [source code and scenarios tutorial](source-code-and-best-practices.md) gives an in-depth walkthrough of the sign in flow and best practices for player authentication.
 
 [Learn more about PlayFab Authentication](../identity/player-identity/authentication/index.md)
 
 ### Economy
 
-As a fantasy RPG style game, Winter Starfall includes an economy system for the player to visit stores, purchase items, and earn currency through battles. PlayFab's newest economy service handles everything related to inventory and commerce in the game. The [source code and scenarios tutorial](source-code-and-best-practices.md) gives an in depth walkthrough of the purchase flow that occurs in the game.
+As a fantasy role-playing game (RPG), Winter Starfall includes an economy system for the player to visit stores, purchase items, and earn currency through battles. PlayFab's newest economy service handles everything related to inventory and commerce in the game. The [source code and scenarios tutorial](source-code-and-best-practices.md) gives an in depth walkthrough of the purchase flow that occurs in the game.
 
 [Learn more about Economy V2](../economy-monetization/economy-v2/overview.md)
 
@@ -67,11 +67,11 @@ As a fantasy RPG style game, Winter Starfall includes an economy system for the
 
 Players in PlayFab have associated data that is stored in the service by different features. Player data as a feature allows you to store player-related information in key/value pairs or objects and files that can be shared across multiple games and devices.
 
-In Winter Starfall, Player data is used to store the game state and information like which characters have joined the player's party. When the player moves through the story, their position is recorded in their player profile through a call to the [UpdateUserData](xref:titleid.playfabapi.com.client.playerdatamanagement.updateuserdata) API. This data is then accessed with GetUserData when they log in, to load the player into the right point in the story with all their past progress.
+In Winter Starfall, player data is used to store the game state and information like which characters joined the player's party. When the player moves through the story, their position is recorded in their player profile through a call to the [UpdateUserData](xref:titleid.playfabapi.com.client.playerdatamanagement.updateuserdata) API. This data is then accessed with `GetUserData` when they sign in, to load the player into the right point in the story with all their past progress.
 
 ![winter-starfall-player-data](media/winterstarfall-player-data.jpg)
 
-For example, these are the API request and response body from the call to `GetUserData` during the login flow. 
+For example, these examples are the API request and response body from the call to `GetUserData` during the login flow. 
 
 **GetUserData - Request**
 
@@ -116,7 +116,7 @@ For example, these are the API request and response body from the call to `GetUs
 
 ### Title data
 
-Title data is similar to Player data in that it stores key-value pairs, only the data pertains to the game title instead of a specific player. Winter Starfall uses title data in conjuction with the Economy system to calculate the price when selling an item by storing the value `multipliers` with a value of `sell, 0.5`. For more information on how the sale flow works, see the [source code and scenarios tutorial](source-code-and-best-practices.md).
+Title data is similar to Player data in that it stores key-value pairs, only the data pertains to the game title instead of a specific player. Winter Starfall uses title data with the Economy system to calculate the price when selling an item by storing the value `multipliers` with a value of `sell, 0.5`. For more information on how the sale flow works, see the [source code and scenarios tutorial](source-code-and-best-practices.md).
 
 ![winterstarfall title data overview in game manager](media/winterstarfall-title-data.jpg)
 
@@ -124,15 +124,15 @@ Title data is similar to Player data in that it stores key-value pairs, only the
 
 ### CloudScript with Azure Functions
 
-CloudScript is a very flexible feature that allows you to implement custom server-side fucntionality, which allows for nearly limitless solutions when paired with other PlayFab features.
+CloudScript is a flexible feature that allows you to implement custom server-side functionality, which allows for nearly limitless solutions when paired with other PlayFab features.
 
-The game uses this feature to solve for a number of scenarios:
+The game uses this feature to solve for many scenarios:
 
 - [CombatVictory](https://github.com/PlayFab/winter-starfall/blob/main/azure-functions/CombatVictory.cs) - After the player wins a battle, execute a series of actions to grant exp, items, and add party members.
 - [PlayerCreated](https://github.com/PlayFab/winter-starfall/blob/main/azure-functions/PlayerCreated.cs) - Equips a new player with starting items and stats.
 - [ProgressCheckpoint](https://github.com/PlayFab/winter-starfall/blob/main/azure-functions/ProgressCheckpoint.cs) - Performs actions to unlock items and characters after reaching key story points.
 - [ResetPlayer](https://github.com/PlayFab/winter-starfall/blob/main/azure-functions/ResetPlayer.cs) - Wipes user data, items, and statistics for a full reset.
-- [SellItem](https://github.com/PlayFab/winter-starfall/blob/main/azure-functions/SellItem.cs) - Enables selling items at a discount, which is not an inherent feature of the economy system. The purchase/sale flow is covered in more detail in the [source code and scenarios tutorial](source-code-and-best-practices.md).
+- [SellItem](https://github.com/PlayFab/winter-starfall/blob/main/azure-functions/SellItem.cs) - Enables selling items at a discount, which isn't an inherent feature of the economy system. The purchase/sale flow is covered in more detail in the [source code and scenarios tutorial](source-code-and-best-practices.md).
 
 [Learn more about CloudScript with Azure Functions](../live-service-management/service-gateway/automation/cloudscript-af/index.md)
 
@@ -152,20 +152,20 @@ In addition to title news, PlayFab offers other communication features like temp
 
 ## Demo limitations
 
-Because Winter Starfall is powered by real player data, some features are limited in scope in the Game Manager view. This section will give an overview of what the limited features would look like in Game Manager. To explore these pages in more detail, you can [download the source code](https://github.com/PlayFab/winter-starfall) and run a local instance of the game, or create your own new title from scratch.
+Because Winter Starfall is powered by real player data, some features are limited in scope in the Game Manager view. This section gives an overview of what the limited features would look like in Game Manager. To explore these pages in more detail, you can [download the source code](https://github.com/PlayFab/winter-starfall) and run a local instance of the game, or create your own new title from scratch.
 
 > [!NOTE]
 > For a full guide to the features in the developer portal, see the [Game Manager documentation](../live-service-management/gamemanager/index.md)
 
 ### Players
 
-The **Players** section of Game Manager is hidden in the Winter Starfall title in order to protect player information. Usually, you would be able to query the entire list of players in your game and select an individual account to update their data through Game Manager. From the player overview page you can view all information related to the player including inventory items, a record of all logins, player data, and more.
+The **Players** section of Game Manager is hidden in the Winter Starfall title in order to protect player information. Usually, you would be able to query the entire list of players in your game and select an individual account to update their data through Game Manager. From the player overview page, you can view all information related to the player including inventory items, a record of all logins, player data, and more.
 
 ![player overview](media/player-overview.png)
 
 ### Data & Analytics
 
-Some of the features under the **Analyze** section are also limited to protect title and player information. This includes the **Data** and **Audit History** sections. The **Data** section contains features like [Data Explorer](../data-analytics/learn-data/data-explorer/index.md) which allows you to query and view a PlayFab event records, which will show events (API calls) such as when a specific player logged in. 
+Some of the features under the **Analyze** section are also limited to protect title and player information. This limitation includes the **Data** and **Audit History** sections. The **Data** section contains features like [Data Explorer](../data-analytics/learn-data/data-explorer/index.md), which allows you to query and view a PlayFab event record, which shows events (API calls) such as when a specific player logged in. 
 
 ![data page](media/demo-game-data.png)
 
@@ -175,13 +175,13 @@ For a full view of what other features are part of the **Data** section, see the
 
 ### Other
 
-Under title settings, the **Secret keys** tab is hidden. See the [documention for secret key management](../live-service-management/gamemanager/secret-key-management.md).
+Under title settings, the **Secret keys** tab is hidden. See the [documentation for secret key management](../live-service-management/gamemanager/secret-key-management.md).
 
 ![Game Manager UI showing Secret Keys page](media/secret-keys.jpg)
 
 ## Next steps
 
-After trying the demo, we recommend starting with these topics to learn more about how PlayFab works:
+After trying the demo, we recommend starting with these articles to learn more about how PlayFab works:
 - Learn more about [Game Manager](../live-service-management/gamemanager/index.md)
 - Learn about the [Entity model](../live-service-management/game-configuration/entities/index.md)
 - Learn about [PlayFab Services SDK](../sdks/sdk-overview.md)
diff --git a/playfab-docs/docfx.json b/playfab-docs/docfx.json
index 34969a045..1e6b3daeb 100644
--- a/playfab-docs/docfx.json
+++ b/playfab-docs/docfx.json
@@ -33,7 +33,7 @@
         "overwrite": [],
         "externalReference": [],
         "globalMetadata": {
-            "uhfHeaderId": "MSDocsHeader-PlayFab",
+            "uhfHeaderId": "MSDocsHeader-Gaming",
             "breadcrumb_path": "/gaming/playfab/breadcrumb/toc.json",
             "feedback_system": "Standard",
             "feedback_product_url": "https://community.playfab.com/index.html",
diff --git a/playfab-docs/economy-monetization/economy-v2/catalog/bundles.md b/playfab-docs/economy-monetization/economy-v2/catalog/bundles.md
index 43fcdaecd..30e570c98 100644
--- a/playfab-docs/economy-monetization/economy-v2/catalog/bundles.md
+++ b/playfab-docs/economy-monetization/economy-v2/catalog/bundles.md
@@ -18,7 +18,7 @@ Bundles allow you to group multiple items together into a single item. You can c
 
 ## Creating a Bundle
 
-To create a bundle, you must first make sure you have published Catalog Items, Currency, or UGC that you want to be accessible/purchaseable in your game. You can follow the steps in the [Economy V2 Quickstart](../quickstart.md#step-3---publish-an-item-to-the-catalog)
+To create a bundle, you must first make sure you have published Catalog Items, Currency, or user-generated content (UGC) that you want to be accessible/purchaseable in your game. You can follow the steps in the [Economy V2 Quickstart](../quickstart.md#step-3---publish-an-item-to-the-catalog)
 
 ### [GameManager](#tab/creating-bundle-game-manager)
 
@@ -90,3 +90,16 @@ Response:
     ...
 }
 ```
+
+## Purchasing and Unpacking Bundles
+
+When a player purchases a bundle, the bundle is **automatically unpacked—the individual items referenced in the bundle are granted directly to the player's inventory. The bundle itself doesn't appear as an inventory item. For more details on how bundles interact with inventory, see [Bundles in Inventory](../inventory/index.md#bundles).
+
+Bundles are also the primary mechanism for linking real-money marketplace products to in-game items. Each bundle can be linked to one or more marketplace products using `AlternateIds`. For more information, see [Fraud Prevention Quickstart](../fraud-prevention/quickstart.md).
+
+## See also
+
+* [Inventory Overview](../inventory/index.md)
+* [Stores](stores.md)
+* [Marketplace Integrations](../marketplace/marketplace-integrations/overview.md)
+* [Fraud Prevention](../fraud-prevention/index.md)
diff --git a/playfab-docs/economy-monetization/economy-v2/catalog/catalog-overview.md b/playfab-docs/economy-monetization/economy-v2/catalog/catalog-overview.md
index 19ae49a5e..a31682edf 100644
--- a/playfab-docs/economy-monetization/economy-v2/catalog/catalog-overview.md
+++ b/playfab-docs/economy-monetization/economy-v2/catalog/catalog-overview.md
@@ -37,7 +37,7 @@ Tab | Description | Reference
 **Stores** | Stores allow you to override base catalog prices for items. | [PlayFab Economy V2 Stores](stores.md)
 **Subscriptions** |   Virtual subscriptions allow you to grant time based access to durable goods. | [PlayFab Economy V2 Subscriptions](subscriptions.md).
 
-Each of these is an Item Type that can be used within your Catalog. Bundles 
+Each of these is an Item Type that can be used within your Catalog.
 
 ### Catalog V2 item fields
 
diff --git a/playfab-docs/economy-monetization/economy-v2/catalog/catalog-views.md b/playfab-docs/economy-monetization/economy-v2/catalog/catalog-views.md
index 72ddf328b..3f5bec874 100644
--- a/playfab-docs/economy-monetization/economy-v2/catalog/catalog-views.md
+++ b/playfab-docs/economy-monetization/economy-v2/catalog/catalog-views.md
@@ -80,7 +80,7 @@ Catalog Views is a regularly updated storage blob of query results, accessible t
 ### Prerequisites
 
 1. Catalog Views is currently in Private Preview. Send an email to **PFEconomyPreviews@microsoft.com** with the subject **Access to Catalog Views Private Preview** along with your PlayFab Title ID to be able to start using the feature in your environment.
-2. Sign in to [PlayFab portal](https://playfab.com).
+2. Sign in to [PlayFab portal](https://developer.playfab.com).
 3. Navigate to your title.
 
 ### Create a New View
diff --git a/playfab-docs/economy-monetization/economy-v2/catalog/real-money-prices.md b/playfab-docs/economy-monetization/economy-v2/catalog/real-money-prices.md
new file mode 100644
index 000000000..73ef6e12c
--- /dev/null
+++ b/playfab-docs/economy-monetization/economy-v2/catalog/real-money-prices.md
@@ -0,0 +1,170 @@
+---
+title: Economy v2 Real Money Prices
+author: ernestoc
+description: Learn how to use RealMoneyPriceDetails to track real-money pricing for catalog items in PlayFab Economy v2.
+ms.author: ernestoc
+ms.date: 02/19/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, commerce, economy, pricing, real money, marketplace, revenue
+ms.localizationpriority: medium
+---
+
+# Real money prices
+
+[!INCLUDE [notice](../../../includes/_economy-release.md)]
+
+Real money prices allow you to associate real-world currency values with catalog items on a per-marketplace basis. The `RealMoneyPriceDetails` property on a catalog item contains separate price dictionaries for each supported marketplace. This data is used by PlayFab to track revenue from marketplace transactions.
+
+## Overview
+
+When players purchase items through external marketplaces (Apple App Store, Google Play, Steam, Microsoft Store, Nintendo eShop, PlayStation Store), the transaction involves real-world money. By setting `RealMoneyPriceDetails` on your catalog items, PlayFab can:
+
+- **Track revenue** from marketplace redemptions in the [marketplace_transaction_redeemed](../../../api-references/events/Inventory/marketplace-transaction-redeemed.md) event.
+
+## Format
+
+`RealMoneyPriceDetails` is an object with a separate price dictionary for each supported marketplace:
+
+| Property | Type | Description |
+| :--- | :--- | :--- |
+| `AppleAppStorePrices` | `Dictionary<string, int>` | The Apple App Store price amount per currency code. |
+| `GooglePlayPrices` | `Dictionary<string, int>` | The Google Play price amount per currency code. |
+| `MicrosoftStorePrices` | `Dictionary<string, int>` | The Microsoft Store price amount per currency code. |
+| `NintendoEShopPrices` | `Dictionary<string, int>` | The Nintendo eShop price amount per currency code. |
+| `PlayStationStorePrices` | `Dictionary<string, int>` | The PlayStation Store price amount per currency code. |
+| `SteamPrices` | `Dictionary<string, int>` | The Steam price amount per currency code. |
+
+Each dictionary maps a three-letter [ISO 4217](https://www.iso.org/iso-4217-currency-codes.html) currency code to a price in the **smallest currency unit** (for example, cents for USD).
+
+> [!NOTE]
+> Only **United States Dollar (USD)** is currently supported as a currency code.
+
+You only need to populate the marketplace properties that are relevant to your title. For example, if your game is only on Google Play and the Apple App Store, you only need to set `GooglePlayPrices` and `AppleAppStorePrices`.
+
+### Price examples
+
+| Real-world price | Dictionary value |
+| :--- | :--- |
+| $0.99 USD | `{"USD": 99}` |
+| $1.39 USD | `{"USD": 139}` |
+| $4.99 USD | `{"USD": 499}` |
+| $9.99 USD | `{"USD": 999}` |
+
+## Setting real money prices on a catalog item
+
+Real money prices are typically set on **bundles** that are linked to external marketplace products via `AlternateIds`. When a player redeems a marketplace purchase, PlayFab uses the `RealMoneyPriceDetails` value from the matching catalog bundle to record the revenue.
+
+### [API](#tab/setting-prices-api)
+
+You can set `RealMoneyPriceDetails` when creating or updating a catalog item using `CreateDraftItem` or `UpdateDraftItem`:
+
+```json
+{
+  "Item": {
+    "Type": "bundle",
+    "Title": {
+      "NEUTRAL": "Starter Pack"
+    },
+    "ItemReferences": [
+      {
+        "Id": "{{LaserSwordID}}",
+        "Amount": 1
+      },
+      {
+        "Id": "{{GoldCurrencyID}}",
+        "Amount": 500
+      }
+    ],
+    "RealMoneyPriceDetails": {
+      "GooglePlayPrices": {
+        "USD": 499
+      },
+      "AppleAppStorePrices": {
+        "USD": 499
+      },
+      "SteamPrices": {
+        "USD": 499
+      }
+    },
+    "AlternateIds": [
+      {
+        "Type": "GooglePlay",
+        "Value": "com.mygame.starterpack"
+      },
+      {
+        "Type": "AppleAppStore",
+        "Value": "com.mygame.starterpack"
+      },
+      {
+        "Type": "Steam",
+        "Value": "starterpack_001"
+      }
+    ]
+  },
+  "Publish": true
+}
+```
+
+You can also set different prices per marketplace if your pricing varies across stores:
+
+```json
+"RealMoneyPriceDetails": {
+  "GooglePlayPrices": {
+    "USD": 499
+  },
+  "AppleAppStorePrices": {
+    "USD": 529
+  },
+  "MicrosoftStorePrices": {
+    "USD": 499
+  }
+}
+```
+
+### [Game Manager](#tab/setting-prices-game-manager)
+
+1. Navigate to **Economy** > **Catalog (V2)**.
+2. Under the **Bundles** tab, select the bundle you want to edit or create a new one.
+3. In the **Prices** section, configure the real money price for each marketplace.
+4. In the **Marketplace Mapping** section, link the bundle to your external marketplace products.
+
+---
+
+## How real money prices appear in events
+
+When a marketplace transaction is redeemed, the price for the corresponding marketplace is included in the [marketplace_transaction_redeemed](../../../api-references/events/Inventory/marketplace-transaction-redeemed.md) event as `RealMoneyPrices`. For example, a Google Play redemption:
+
+```json
+{
+  "Marketplace": "GooglePlay",
+  "MarketplaceTransctionId": "GPA.1234-5678-9012-34567",
+  "MarketplaceAlternateId": "com.mygame.starterpack",
+  "Amount": 1,
+  "ItemId": "{{BundleID}}",
+  "ItemType": "bundle",
+  "RealMoneyPrices": {
+    "USD": 499
+  }
+}
+```
+
+This event data can then be used for:
+
+- Custom analytics queries via the Insights Explorer
+
+## Best practices
+
+- **Always set `RealMoneyPriceDetails` on marketplace bundles.** This ensures accurate revenue tracking and analytics.
+- **Use the smallest currency unit.** For USD, provide the price in cents (for example, `499` for $4.99).
+- **Only populate the marketplaces you use.** You don't need to set prices for every marketplace — only the ones your title is published on.
+- **Keep prices in sync with your marketplace listings.** When you update prices in an external marketplace, update the corresponding property in `RealMoneyPriceDetails` to maintain accurate reporting.
+- **Set per-marketplace prices when they differ.** If your game is priced differently across stores, use the per-marketplace properties to reflect the actual price on each platform.
+
+## See also
+
+- [Economy v2 Bundles](bundles.md)
+- [Stores](stores.md)
+- [Fraud prevention quickstart](../fraud-prevention/quickstart.md)
+- [Marketplace integrations](../marketplace/marketplace-integrations/overview.md)
+- [marketplace_transaction_redeemed event](../../../api-references/events/Inventory/marketplace-transaction-redeemed.md)
diff --git a/playfab-docs/economy-monetization/economy-v2/catalog/subscriptions.md b/playfab-docs/economy-monetization/economy-v2/catalog/subscriptions.md
index 32fbd8d08..3dc9ba524 100644
--- a/playfab-docs/economy-monetization/economy-v2/catalog/subscriptions.md
+++ b/playfab-docs/economy-monetization/economy-v2/catalog/subscriptions.md
@@ -15,11 +15,11 @@ ms.localizationpriority: medium
 Subscriptions allow you to grant time based access to durable goods. Items within a subscription are unpacked in a player's inventory after calling [GetInventoryItems](/rest/api/playfab/economy/inventory/get-inventory-items). 
 
 > [!NOTE]
->This article focuses on virtual subscriptions, or the subscriptions that live inside of your game. We have a new feature in **Private Preview** where you can link virtual subscriptions to real-world marketplaces using PlayFab's Inventory Redeem APIs. Here is where you can find more information about how to do this:
->- [IOS Subscription Redemption](../marketplace/marketplace-redemption/ios-subscription-redemption.md)
->- [Google Play Store Subscription Redemption](../marketplace/marketplace-redemption/google-subscription-redemption.md)
+> This article focuses on virtual subscriptions, or the subscriptions that live inside of your game. We have a feature in **Private Preview** where you can link virtual subscriptions to real-world marketplaces using PlayFab's Inventory Redeem APIs. Here is where you can find more information about how to do this:
+> - [iOS Subscription Redemption](../marketplace/marketplace-redemption/ios-subscription-redemption.md)
+> - [Google Play Store Subscription Redemption](../marketplace/marketplace-redemption/google-subscription-redemption.md)
 >
->To access this feature, send an email to **PFEconomyPreviews@microsoft.com** with the subject **PlayFab Mobile Subscriptions** along with your PlayFab Title ID and we will enable the feature in your environment.
+> To access this feature, send an email to **PFEconomyPreviews@microsoft.com** with the subject **PlayFab Mobile Subscriptions** along with your PlayFab Title ID and we will enable the feature in your environment.
 
 ## Creating a Subscription
 
diff --git a/playfab-docs/economy-monetization/economy-v2/catalog/toc.yml b/playfab-docs/economy-monetization/economy-v2/catalog/toc.yml
index 1dbf76b43..e220b8ae9 100644
--- a/playfab-docs/economy-monetization/economy-v2/catalog/toc.yml
+++ b/playfab-docs/economy-monetization/economy-v2/catalog/toc.yml
@@ -3,6 +3,8 @@ items:
   href: catalog-overview.md
 - name: Bundles
   href: bundles.md
+- name: Real money prices
+  href: real-money-prices.md
 - name: Stores
   href: stores.md
 - name: Subscriptions
diff --git a/playfab-docs/economy-monetization/economy-v2/faq.md b/playfab-docs/economy-monetization/economy-v2/faq.md
index 1dfc1985b..9b0e2b0ba 100644
--- a/playfab-docs/economy-monetization/economy-v2/faq.md
+++ b/playfab-docs/economy-monetization/economy-v2/faq.md
@@ -22,7 +22,7 @@ ms.localizationpriority: medium
 
 * Create a catalog of items - Easily create and manage a large number of virtual items for your in-game store.
 * Manage player inventories - Keep track of what items each player has in their inventory across all of the platforms your game runs on.
-* Create virtual currencies - Make different types of virtual money that players can use in your game. For example, you can have a "soft" currency that players can earn by playing the game, and a "hard" currency that players can buy with real money.
+* Create virtual currencies - Make different types of virtual money that players can use in your game. For example, you can have a "soft" currency that players earn by playing the game, and a "hard" currency that players can buy with real money.
 * Create stores - Make different stores where players can buy or sell items. You can set different prices for items in different stores, or offer special deals or discounts to players.
 * Let players create content - Use User Generated Content (UGC) to let players create their own items or content and share it with other players. UGC makes your game more fun and creative for players.
 
@@ -30,7 +30,7 @@ ms.localizationpriority: medium
 
 **A:** PlayFab Economy has many tools and options that help you follow best practices for creating a virtual economy. Here are some of the ways PlayFab Economy helps you.
 
-* Search for items: Use PlayFab Economy to search for items in your catalog. Search makes it easy to create special in-game views and find what you are looking for.
+* Search for items: Use PlayFab Economy to search for items in your catalog. Search makes it easy to create special in-game views and find what you're looking for.
 * Validate receipts: Use PlayFab Economy to check if players really bought something with real money from a platform store. Receipt Validation helps prevent fraud and cheating.
 * Create bundles: Use PlayFab Economy to group items together and sell them as a bundle. Bundles make it easier for players to buy multiple items at once, such as virtual currency packs of 100, 500, and so on.
 * Create virtual subscriptions: Use PlayFab Economy to let players subscribe to your game or service. Subscriptions mean players pay a regular fee (for example, every month) to get access to special features or content.
@@ -40,13 +40,13 @@ ms.localizationpriority: medium
 
 **Q: How do I migrate my title from V1 (Legacy) to V2?**
 
-**A:** If you have a live title with existing player data, we don’t recommend that you attempt to migrate users today. Although the API and Game Manager surface are similar, migration, especially with live player data, requires diligent engineering.
+**A:** If you have a live title with existing player data, don't attempt to migrate users today. Although the API and Game Manager surface are similar, migration, especially with live player data, requires diligent engineering.
 
-If your title isn’t live yet, the process is easier but there are differences in functionality between the two systems. Those differences are highlighted in this FAQ. To learn more about Economy V2, see [Economy overview](overview.md). If you're a premium customer, reach out to us via the support channel. We’d be happy to consult and help you plan if you have questions.
+If your title isn't live yet, the process is easier but there are differences in functionality between the two systems. Those differences are highlighted in this FAQ. To learn more about Economy V2, see [Economy overview](overview.md). If you're a premium customer, reach out to us via the support channel. We'd be happy to consult and help you plan if you have questions.
 
 **Q: What are the differences between V1 (Legacy) and V2?**
 
-**A:** V2 is complete rearchitecture from V1, and there are many important differences. At a high level, the Catalog has changed from being a single document to individual versioned items all of which are in their own document with their own metadata. Catalog (V2) allows increased scale for in-game catalogs and intelligent [Search](catalog/search.md) for creating in-game channels of content. V2 requires a different pattern of interaction with the catalog compared to V1. Inventory PlayFab [Inventory](inventory/index.md) has been rearchitected to better handle higher amounts of throughput, higher usage calling patterns, and allow for more stable (and idempotent) transactions. Inventory now natively supports [Collections](inventory/collections.md) and [Stacks](inventory/stacks.md). [Stores](catalog/stores.md) and sales are also handled differently in V2.
+**A:** V2 is a complete rearchitecture from V1, and there are many important differences. At a high level, the Catalog changed from being a single document to individual versioned items, all of which are in their own document with their own metadata. Catalog (V2) supports increased scale for in-game catalogs and intelligent [Search](catalog/search.md) for creating in-game channels of content. V2 requires a different pattern of interaction with the catalog compared to V1. Inventory PlayFab [Inventory](inventory/index.md) is rearchitected to better handle higher amounts of throughput, higher usage calling patterns, and allow for more stable (and idempotent) transactions. Inventory now natively supports [Collections](inventory/collections.md) and [Stacks](inventory/stacks.md). [Stores](catalog/stores.md) and sales are also handled differently in V2.
 
 **Q: Which version of Economy should I use?**
 
@@ -54,14 +54,14 @@ If your title isn’t live yet, the process is easier but there are differences
 
 **Q: Does Economy V2 support all of the features from Economy V1 (Legacy)?**
 
-**A:** No, Economy V2 doesn’t have full parity with all of the features PlayFab supports in V1 (Legacy). Some of these features never received the adoption we hoped for in Playfab. Others were lacking the depth and surface area needed to really help developers implement them in their games. Some we plan to deliver in future updates. Specifically today Economy V2 doesn't support PlayFab style Coupons, Limited Items, Recharge Item Rates, Drop Tables, or Store Support with Segments.
+**A:** No, Economy V2 doesn't have full parity with all of the features PlayFab supports in V1 (Legacy). Some of these features never received the adoption we hoped for in Playfab. Others were lacking the depth and surface area needed to really help developers implement them in their games. Some we plan to deliver in future updates. Specifically today Economy V2 doesn't support PlayFab style Coupons, Limited Items, Recharge Item Rates, Drop Tables, or Store Support with Segments. However, some V1 patterns can be replicated using V2 building blocks—for example, [fixed-contents containers can be implemented using bundles and virtual currency](tutorials/containers-with-fixed-contents.md), and item conversion (crafting) can be achieved using the [ExecuteInventoryOperations](/rest/api/playfab/economy/inventory/execute-inventory-operations) API.
 
 ## Marketplace and platform integrations
 
 **Q: Does PlayFab help with Platform Enforcement, such as virtual currency restrictions or sharing entitlements between platforms?**
 
-**A:** Our goal with Economy is to make enabling cross platform entitlements easy for titles to manage, and also make it easy when that sharing isn't allowed. Our features allow you to link a single virtual catalog item to multiple different platform entitlements to ease item management and enable 'Buy Once Play Anywhere scenarios.' You can also, instead, silo virtual currencies, and have multiple separate player inventories, to isolate purchases to comply with different platform obligations. Although the platform features help this way, we don't police or enforce platform policies, it's up to you to implement platform policies for your title.
+**A:** The goal of Economy is to make enabling cross platform entitlements easy for titles to manage, and also make it easy when that sharing isn't allowed. Use the features to link a single virtual catalog item to multiple different platform entitlements to ease item management and enable 'Buy Once Play Anywhere scenarios.' You can also, instead, silo virtual currencies, and have multiple separate player inventories, to isolate purchases to comply with different platform obligations. Although the platform features help this way, they don't police or enforce platform policies. You need to implement platform policies for your title.
 
 **Q: Does the platform help abstract away the storefronts of multiple platforms behind a single API?**
 
-**A:** Yes. We’ve set up Economy V2 Bundles to be linkable to items on multiple different platforms. You can use platforms to consolidate receipt validation and redemption scenarios. You can then use our APIs universally to populate your in-game store, regardless of what the platform is and with little platform specific code post-authorization.
+**A:** Yes. Set up Economy V2 Bundles to be linkable to items on multiple different platforms. Use platforms to consolidate receipt validation and redemption scenarios. Then use the APIs universally to populate your in-game store, regardless of what the platform is and with little platform specific code post-authorization.
diff --git a/playfab-docs/economy-monetization/economy-v2/fraud-prevention/index.md b/playfab-docs/economy-monetization/economy-v2/fraud-prevention/index.md
index fb3d42350..ccb6f4887 100644
--- a/playfab-docs/economy-monetization/economy-v2/fraud-prevention/index.md
+++ b/playfab-docs/economy-monetization/economy-v2/fraud-prevention/index.md
@@ -14,7 +14,7 @@ ms.localizationpriority: medium
 
 [!INCLUDE [notice](../../../includes/_economy-release.md)]
 
-The heart of any game economy is allowing players to purchase game items, currencies, and more with virtual currencies or Real Word (RW) money.
+The heart of any game economy is allowing players to purchase game items, currencies, and more with virtual currencies or real-world (RW) money.
 
 ## Fraud Vectors
 
diff --git a/playfab-docs/economy-monetization/economy-v2/fraud-prevention/quickstart.md b/playfab-docs/economy-monetization/economy-v2/fraud-prevention/quickstart.md
index dab61b133..c2d35cd43 100644
--- a/playfab-docs/economy-monetization/economy-v2/fraud-prevention/quickstart.md
+++ b/playfab-docs/economy-monetization/economy-v2/fraud-prevention/quickstart.md
@@ -32,11 +32,11 @@ To give those entries meaning, we need to mirror them in the PlayFab Catalog. Mi
 Each Bundle can be linked to one or more Partner Marketplace Products by adding an AlternateId to it. The AlternateId is the link between PlayFab and any external IAP Market. When your title calls Redeem for a given player entity, we pass this ID up to the IAP Market to check. The general flow is:
 
 1. Create 1 (or more) real world offers in the Microsoft Store
-1. Populate the Add-ons in PlayFab with IAP Market calling permissions and create corresponding Bundles in Playfab that link to the offers you created
+1. Populate the Add-ons in PlayFab with IAP Market calling permissions and create corresponding Bundles in PlayFab that link to the offers you created
 1. Call `RedeemMicrosoftStoreInventoryItems`
 
 > [!NOTE]
-> Unlike previous incarnations of Playfab, in the new system you just create one bundle offer, and then you add each market SKU that needs to reference into the AlternateId list. You don’t need to create a new Item for each IAP market.
+> Unlike previous incarnations of PlayFab, in the new system you just create one bundle offer, and then you add each market SKU that needs to reference into the AlternateId list. You don’t need to create a new Item for each IAP market.
 
 ### Step 1 - Setting up your marketplace integration
 
diff --git a/playfab-docs/economy-monetization/economy-v2/inventory/collections.md b/playfab-docs/economy-monetization/economy-v2/inventory/collections.md
index 8c06659b5..52bdff3e0 100644
--- a/playfab-docs/economy-monetization/economy-v2/inventory/collections.md
+++ b/playfab-docs/economy-monetization/economy-v2/inventory/collections.md
@@ -26,7 +26,7 @@ Using the `GetInventoryCollectionIds` API, you can get a list of `CollectionId`s
 
 An example `GetInventoryCollectionIds` request:
 
-```csharp
+```json
 {
   "Entity": {
     "Type": "title_player_account",
@@ -39,11 +39,11 @@ An example `GetInventoryCollectionIds` request:
 
 This request would return the following response:
 
-```csharp
+```json
 {
   "data": {
   "CollectionIds": [
-    "default".
+    "default",
     "main_character"
     ]
   }
@@ -74,7 +74,7 @@ For example, the following `AddInventoryItems` request uses the collectionId `ma
 }
 ```
 
-The above request would either create a brand new inventory collection of and add 5 of the item to it or add 5 to the existing `main_character` inventory collection if it already existed.
+The above request would either create a brand new inventory collection and add 10 of the item to it or add 10 to the existing `main_character` inventory collection if it already existed.
 
 ### DeleteInventoryCollection
 
diff --git a/playfab-docs/economy-monetization/economy-v2/inventory/etags.md b/playfab-docs/economy-monetization/economy-v2/inventory/etags.md
new file mode 100644
index 000000000..fb659e488
--- /dev/null
+++ b/playfab-docs/economy-monetization/economy-v2/inventory/etags.md
@@ -0,0 +1,92 @@
+---
+title: Inventory ETags
+author: wesjong
+description: Using ETags for optimistic concurrency control with PlayFab Inventory APIs.
+ms.author: wesjong
+ms.date: 02/20/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, commerce, economy, monetization, inventory, etags, concurrency
+ms.localizationpriority: medium
+---
+
+# Inventory ETags
+
+[!INCLUDE [notice](../../../includes/_economy-release.md)]
+
+ETags provide optimistic concurrency control for the PlayFab Inventory APIs. They allow you to detect and prevent conflicting writes when multiple sources are modifying a player's inventory simultaneously.
+
+## How Inventory ETags work
+
+Inventory read APIs such as `GetInventoryItems` return an `ETag` in the response body. This value represents the current version of the player's inventory collection. You can pass this value in subsequent write requests to ensure your changes don't conflict with other updates that might have occurred since you last read the inventory.
+
+### Example `GetInventoryItems` response with ETag
+
+```json
+{
+  "code": 200,
+  "status": "OK",
+  "data": {
+    "Items": [
+      {
+        "Id": "0b440353-bdbc-48d8-8873-f0988c1f9d8b",
+        "StackId": "default",
+        "Amount": 10,
+        "Type": "catalogItem"
+      }
+    ],
+    "ETag": "1/MQ=="
+  }
+}
+```
+
+## Supported HTTP Headers
+
+Inventory write APIs support ETags through the following HTTP headers:
+
+- **`X-PlayFab-Economy-If-Match`**—Pass a previously received `ETag` value. The request succeeds only if the inventory's current ETag matches. Use this check when you need to guarantee that no other write has occurred since you last read the inventory.
+- **`X-PlayFab-Economy-If-None-Match`**—Pass `*` as the value. The request succeeds only if the item doesn't already exist in the inventory. Useful for "create-only" scenarios.
+
+## Supported APIs
+
+The following Inventory write APIs support ETag headers:
+
+- [AddInventoryItems](/rest/api/playfab/economy/inventory/add-inventory-items)
+- [SubtractInventoryItems](/rest/api/playfab/economy/inventory/subtract-inventory-items)
+- [UpdateInventoryItems](/rest/api/playfab/economy/inventory/update-inventory-items)
+- [PurchaseInventoryItems](/rest/api/playfab/economy/inventory/purchase-inventory-items)
+- [DeleteInventoryItems](/rest/api/playfab/economy/inventory/delete-inventory-items)
+- [TransferInventoryItems](/rest/api/playfab/economy/inventory/transfer-inventory-items)
+- [ExecuteInventoryOperations](/rest/api/playfab/economy/inventory/execute-inventory-operations)
+
+## Usage Example
+
+A typical workflow using inventory ETags:
+
+1. Call `GetInventoryItems` and store the `ETag` from the response.
+2. Perform your inventory write (for example, `AddInventoryItems`) and include the `X-PlayFab-Economy-If-Match` header with the stored `ETag`.
+3. If the inventory has been modified by another request since you read it, the API returns a **412 Precondition Failed** error. In that case, re-read the inventory, get the latest `ETag`, and retry.
+
+```
+POST /Inventory/AddInventoryItems
+Content-Type: application/json
+X-EntityToken: <entity-token>
+X-PlayFab-Economy-If-Match: 1/MQ==
+
+{
+    "Entity": {
+        "Type": "title_player_account",
+        "Id": "ABCD12345678"
+    },
+    "Item": {
+        "Id": "0b440353-bdbc-48d8-8873-f0988c1f9d8b"
+    },
+    "Amount": 5
+}
+```
+
+## See also
+
+- [Inventory Overview](index.md)
+- [Catalog ETags](../catalog/etags.md)
+- [Idempotency](index.md#idempotency)
diff --git a/playfab-docs/economy-monetization/economy-v2/inventory/index.md b/playfab-docs/economy-monetization/economy-v2/inventory/index.md
index 3adef32fb..f7fe4684c 100644
--- a/playfab-docs/economy-monetization/economy-v2/inventory/index.md
+++ b/playfab-docs/economy-monetization/economy-v2/inventory/index.md
@@ -158,6 +158,17 @@ An example `PurchaseInventoryItems` request:
 }
 ```
 
+> [!NOTE]
+> The `PurchaseInventoryItems` API is used for purchases with virtual currencies. For real-money purchases through external marketplaces (Apple App Store, Google Play, Steam, Microsoft Store), use the corresponding Redeem APIs (such as `RedeemAppleAppStoreInventoryItems`, `RedeemGooglePlayInventoryItems`, `RedeemSteamInventoryItems`, or `RedeemMicrosoftStoreInventoryItems`). These APIs validate the purchase receipt with the marketplace and grant the items to the player's inventory. For more information, see [Marketplace Redemption](../marketplace/marketplace-redemption/overview.md).
+
+#### Bundles
+
+When a bundle is purchased (via `PurchaseInventoryItems` or a marketplace Redeem API), the bundle is **automatically unpacked** into the player's inventory. The individual items referenced in the bundle's `ItemReferences` are granted directly — the bundle itself does not appear as an item in the player's inventory.
+
+For example, purchasing a bundle containing 2x Laser Sword and 2x Laser Gun grants those items individually. The virtual currency cost defined in the bundle's `PriceOptions` is deducted from the player's inventory as part of the transaction.
+
+Bundles that are linked to marketplace products via `AlternateIds` follow the same unpacking behavior when redeemed. For more information on creating bundles, see [Bundles](../catalog/bundles.md).
+
 ### Transfer Inventory Items
 
 The `TransferInventoryItems` API can be used in three different ways.
@@ -262,7 +273,7 @@ More information about stacks can be found [here](stacks.md).
 
 You can use the `ExecuteInventoryOperations` API to batch multiple inventory operations in a single request. Operations will happen in request order specified and if an operation is unable to be performed, the whole set of operations is canceled.
 
-The `ExecuteInventoryOperations` takes in an `Operation` parameter that is a list of operations. There can be at most ten operations in the `Operation` list but operation types can repeat (for example, 10 Add operations are valid). There is also a limit to 250 items that can be modified/added in a single request. For example, adding a bundle with 50 items counts as 50 items modified. The valid operation types are:
+The `ExecuteInventoryOperations` takes in an `Operation` parameter that is a list of operations. There can be at most **50 operations** in the `Operation` list but operation types can repeat (for example, 10 Add operations are valid). There is also a limit to **300 items** that can be modified/added in a single request. For example, adding a bundle with 50 items counts as 50 items modified. The valid operation types are:
 
 * Add
 * Subtract
@@ -334,6 +345,10 @@ For example, the following `PurchaseItem` API request can be called multiple tim
 > [!NOTE]
 > Using the same `IdempotencyId` for different request types will cause a conflict and throw an error.
 
+### ETags and Concurrency Control
+
+Inventory write APIs support optimistic concurrency control through ETags and HTTP headers. For full details, see [Inventory ETags](etags.md).
+
 ### Display Properties
 
 Display Properties are custom item properties that can be added to items and item stacks in player inventories.
diff --git a/playfab-docs/economy-monetization/economy-v2/inventory/items-and-inventory-overview.md b/playfab-docs/economy-monetization/economy-v2/inventory/items-and-inventory-overview.md
index ff1f6daa1..e9e524601 100644
--- a/playfab-docs/economy-monetization/economy-v2/inventory/items-and-inventory-overview.md
+++ b/playfab-docs/economy-monetization/economy-v2/inventory/items-and-inventory-overview.md
@@ -1,40 +1,61 @@
 ---
 title: Items and Inventory Overview
 author: thomasgu
-description: Overall description of Items and Inventory in V2.
+description: Overview of Economy v2 Items and Inventory concepts and APIs.
 ms.author: thomg
 ms.date: 02/20/2025
 ms.topic: article
 ms.service: azure-playfab
-keywords: playfab, commerce, economy, items, catalogs
+keywords: playfab, commerce, economy, items, catalogs, inventory, v2
 ms.localizationpriority: medium
 ---
 
 # PlayFab Items and Inventory Overview
 
-Items and inventories are essential features for creating engaging and immersive games. They allow you to offer customization options, rewards, progression systems, and monetization opportunities for your players. 
+[!INCLUDE [notice](../../../includes/_economy-release.md)]
 
-PlayFab provides a flexible and powerful platform for creating and managing these virtual goods. You can use PlayFab to define different types of items, such as durables, consumables, bundles, containers, and more. You can also use PlayFab to track the ownership and usage of items by your players. Here are some of the key concepts you need to know about items and inventories in PlayFab:
+Items and inventories are essential features for creating engaging and immersive games. They allow you to offer customization options, rewards, progression systems, and monetization opportunities for your players.
 
-[!INCLUDE [notice](../../../includes/_economy-deprecation.md)]
+PlayFab Economy v2 provides a flexible and powerful platform for creating and managing virtual goods. You can define different types of items — such as durables, consumables, bundles, subscriptions, and virtual currencies — and track the ownership and usage of items across your players' inventories.
 
 ## Key concepts
 
-* **Catalog** - A catalog is a collection of all the items that are available in your game. Catalogs offer an easy way to manage your game's virtual items. 
-* **Catalog Items** – Catalog items are the individual items that you define in your catalog. They can represent any kind of virtual good that you want to offer in your game, such as weapons, outfits, power-ups, loot boxes, etc. You can customize the properties and behaviors of catalog items to suit your game design.
-* **Catalog Stores** - You can use store create multiple item listings for different purposes, such as seasonal events, promotions, or testing.
-* **Player Inventory Collections** -  Inventory is a record of the items that a player owns or has used in your game. It also contains information about the player's virtual currency balances and item history. All player accounts can have one or more inventories, which we call inventory collections. 
-* **Virtual Currency** - Virtual currency is a type of item that can be used as a medium of exchange in your game. You commonly use virtual currency to sell or buy other items from the catalog or a store. You can also use virtual currency to implement soft currency conversions from in-app purchases or to drive gameplay mechanics.
-
-For more information about these and other related concepts, please refer to the [Economy V2 Catalog Overview](../catalog/catalog-overview.md) 
+* **Catalog** - A catalog is a collection of all the items that are available in your game. Catalogs offer an easy way to manage your game's virtual items. For more information, see the [Catalog Overview](../catalog/catalog-overview.md).
+* **Catalog Items** – Individual items defined in your catalog. They can represent any kind of virtual good, such as weapons, outfits, power-ups, loot boxes, etc. You can customize properties and behaviors to suit your game design.
+* **Catalog Stores** - Stores allow you to create multiple item listings for different purposes, such as seasonal events, promotions, or testing. See [Stores](../catalog/stores.md).
+* **Bundles** - Bundles are catalog items that contain references to other items. When a player purchases a bundle, the referenced items are unpacked and added to their inventory.
+* **Subscriptions** - Subscriptions grant time-based access to durable goods. Items within a subscription are available in a player's inventory for the duration of the subscription. See [Subscriptions](../catalog/subscriptions.md).
+* **Player Inventory Collections** - Inventory is a record of the items that a player owns in your game. It contains information about item amounts, virtual currency balances, and custom properties. All player accounts can have one or more inventories called [Collections](collections.md).
+* **Stacks** - Stacks allow multiple distinct instances of the same item to exist within a single inventory, each with their own amount and custom properties. See [Stacks](stacks.md).
+* **Virtual Currency** - Virtual currency is a type of item used as a medium of exchange in your game. You can use virtual currency to buy items from the catalog or a store, implement soft currency from in-app purchases, or drive gameplay mechanics.
 
 ## Key APIs
 
-PlayFab provides a large interactive playing field for interaction with items and inventory, and the Item definition in the Catalog allows for quite a bit of customization. A rich set of APIs is available for interacting with items and inventories in your game. You can use these APIs to perform various actions, such as purchasing items, granting items, consuming items, updating inventory, and querying inventory. Most common interactions are through a few key APIs:
+A rich set of APIs is available for interacting with items and inventories in your game. You can use these APIs to perform actions such as purchasing items, granting items, updating inventory, transferring items between players, and querying transaction history.
+
+### Inventory Management
+
+* **[GetInventoryItems](/rest/api/playfab/economy/inventory/get-inventory-items)** - Retrieve the current inventory of an entity. Supports pagination with `ContinuationToken` and bulk loading via [TurboLoading](turboloading.md).
+* **[AddInventoryItems](/rest/api/playfab/economy/inventory/add-inventory-items)** - Add items directly to a player's inventory.
+* **[SubtractInventoryItems](/rest/api/playfab/economy/inventory/subtract-inventory-items)** - Reduce item amounts in a player's inventory.
+* **[UpdateInventoryItems](/rest/api/playfab/economy/inventory/update-inventory-items)** - Set item amounts or modify [Display Properties](index.md#display-properties) on inventory items.
+* **[DeleteInventoryItems](/rest/api/playfab/economy/inventory/delete-inventory-items)** - Remove entire stacks of items from a player's inventory.
+
+### Purchasing and Trading
+
+* **[PurchaseInventoryItems](/rest/api/playfab/economy/inventory/purchase-inventory-items)** - Buy catalog items or bundles using virtual currency. Deducts the currency from the player's inventory and grants the purchased item.
+* **[TransferInventoryItems](/rest/api/playfab/economy/inventory/transfer-inventory-items)** - Transfer items between players, between a player's inventory collections, or between stacks within the same inventory.
+
+### Batch Operations
+
+* **[ExecuteInventoryOperations](/rest/api/playfab/economy/inventory/execute-inventory-operations)** - Batch up to 10 inventory operations (Add, Subtract, Update, Purchase, Transfer, Delete) in a single atomic request. If any operation fails, the entire batch is rolled back.
+
+### History and Diagnostics
+
+* **[GetTransactionHistory](/rest/api/playfab/economy/inventory/get-transaction-history)** - Retrieve transaction events from a player's inventory. Supports filtering by timestamp and pagination for reviewing the full operation history. See [Transaction History](transaction-history.md).
+
+### Reliability
 
-* **PurchaseInventoryItems** - This API allows a player to buy catalog items or bundles with virtual currency. It deducts the currency from the player's inventory and adds an item instance to the player's inventory.
-* **GetInventoryItems** - Allows you to retrieve the current inventory of an Entity, and will return a list of item instances for the specified player.
-* **UpdateInventoryItems** - Used to make convenient changes to inventory items, especially to DisplayProperties for modifying custom attributes.
-* **GetTransactionHistory** - Will get the latest transaction events from the inventory, and allow you to page through to get the full transaction history.
+* **Idempotency** - All inventory APIs support an `IdempotencyId` parameter to safely retry requests without duplicate side effects. IDs are enforced for 14 days. See [Idempotency](index.md#idempotency).
 
-For more information on how to use these APIs and other related APIs, please refer to the [PlayFab Inventory API documentation](/rest/api/playfab/economy/inventory?view=playfab-rest) 
+For the full API reference and detailed examples for each operation, see the [Inventory API documentation](index.md) and the [PlayFab REST API reference](/rest/api/playfab/economy/inventory).
diff --git a/playfab-docs/economy-monetization/economy-v2/inventory/stacks.md b/playfab-docs/economy-monetization/economy-v2/inventory/stacks.md
index 35f1101fe..c4a53c535 100644
--- a/playfab-docs/economy-monetization/economy-v2/inventory/stacks.md
+++ b/playfab-docs/economy-monetization/economy-v2/inventory/stacks.md
@@ -120,7 +120,7 @@ When you make purchases with stacks, there are a few parameters that are relevan
 - For the `Item` object, you can define an optional `StackId` that represents the stack the receiving items will be placed in
 - There's a`DeleteEmptyStacks` boolean that can be set which deletes the stack if the subtracted amount results in the stack having an amount of 0.
 
-> TODO Add link
+> For more details on purchasing items, see [PurchaseInventoryItems](/rest/api/playfab/economy/inventory/purchase-inventory-items).
 
 An example `PurchaseInventoryItems` request with stacks:
 
diff --git a/playfab-docs/economy-monetization/economy-v2/inventory/toc.yml b/playfab-docs/economy-monetization/economy-v2/inventory/toc.yml
index 4e80f15e5..c270be990 100644
--- a/playfab-docs/economy-monetization/economy-v2/inventory/toc.yml
+++ b/playfab-docs/economy-monetization/economy-v2/inventory/toc.yml
@@ -11,5 +11,7 @@ items:
   href: stacks.md
 - name: Transaction History
   href: transaction-history.md
+- name: ETags
+  href: etags.md
 - name: TurboLoading
   href: turboloading.md
diff --git a/playfab-docs/economy-monetization/economy-v2/inventory/turboloading.md b/playfab-docs/economy-monetization/economy-v2/inventory/turboloading.md
index 524cde976..4154aad5e 100644
--- a/playfab-docs/economy-monetization/economy-v2/inventory/turboloading.md
+++ b/playfab-docs/economy-monetization/economy-v2/inventory/turboloading.md
@@ -44,14 +44,14 @@ You can enable compression for all API responses using the Cross-Platform PlayFa
 // Initialize PFHttpSettings struct
 PFHttpSettings* httpSettings = new PFHttpSettings;
 
-// Enable Repsonse Compression (and automatic decompression)
+// Enable Response Compression (and automatic decompression)
 httpSettings->requestResponseCompression = true;
 
 // Set PFHttpSettings
 HRESULT hr = PFSetHttpSettings(httpSettings); // Add your own error handling FAILED(hr) == true
 ```
 
-Additionally you can disable compression for all API reponses:
+Additionally you can disable compression for all API responses:
 ```C++
 // Disable Response Compression
 httpSettings->requestResponseCompression = false;
diff --git a/playfab-docs/economy-monetization/economy-v2/limits.md b/playfab-docs/economy-monetization/economy-v2/limits.md
index 51025a9be..89a8a1a49 100644
--- a/playfab-docs/economy-monetization/economy-v2/limits.md
+++ b/playfab-docs/economy-monetization/economy-v2/limits.md
@@ -62,15 +62,15 @@ The purpose of this guide is to detail the limits that are enforced when creatin
 > [!NOTE]
 >
 > - Inventory throttling will be calculated based on the target entity, individually for each API.
-> - For example, if a Player or a Title (game service, coudscript, etc.) calls an Inventory API to update the Player entity's inventory, the Limit (Player) throttling will be applied.
+> - For example, if a Player or a Title (game service, CloudScript, etc.) calls an Inventory API to update the Player entity's inventory, the Limit (Player) throttling will be applied.
 > - [Group entity](../../live-service-management/game-configuration/entities/index.md#group) inventories are also supported, and Group Entities share the same throttling rate as Player entities. See also [Groups](../../community/associations/groups/index.md).
 
 ### Read
 
 | **API** | **Limit (Player)** | **Limit (Title)** |
 |---------|--------------------|-------------------|
-| **GetInventoryItems** | 1.67 rps (100 in 60 seconds) | - |
-| **GetInventoryCollectionIds** | 1.67 rps (100 in 60 seconds) | - |
+| **GetInventoryItems** | 0.67 rps (40 in 60 seconds) | - |
+| **GetInventoryCollectionIds** | 0.08 rps (5 in 60 seconds) | - |
 
 ### Read Transaction History
 
@@ -82,25 +82,25 @@ The purpose of this guide is to detail the limits that are enforced when creatin
 
 | **API** | **Limit (Player)** | **Limit (Title)** |
 |---------|--------------------|-------------------|
-| **AddInventoryItems** | 0.66 rps (60 in 90 seconds) | - |
-| **SubtractInventoryItems** | 0.66 rps (60 in 90 seconds) | - |
-| **UpdateInventoryItems** | 0.66 rps (60 in 90 seconds) | - |
-| **PurchaseInventoryItems** | 0.66 rps (60 in 90 seconds) | - |
-| **TransferInventoryItems** | 0.66 rps (60 in 90 seconds) | - |
-| **DeleteInventoryItems** | 0.66 rps (60 in 90 seconds) | - |
-| **ExecuteInventoryOperations** | 0.66 rps (60 in 90 seconds) | - |
-| **DeleteInventoryCollection** | 0.16 rps (15 in 90 seconds) | - |
+| **AddInventoryItems** | 0.33 rps (20 in 60 seconds) | - |
+| **SubtractInventoryItems** | 0.33 rps (20 in 60 seconds) | - |
+| **UpdateInventoryItems** | 0.33 rps (20 in 60 seconds) | - |
+| **PurchaseInventoryItems** | 0.33 rps (20 in 60 seconds) | - |
+| **TransferInventoryItems** | 0.33 rps (20 in 60 seconds) | - |
+| **DeleteInventoryItems** | 0.33 rps (20 in 60 seconds) | - |
+| **ExecuteInventoryOperations** | 0.33 rps (20 in 60 seconds) | - |
+| **DeleteInventoryCollection** | 0.08 rps (5 in 60 seconds) | - |
 
 ### Redeem
 
 | **API** | **Limit (Player)** | **Limit (Title)** |
 |---------|--------------------|-------------------|
-| **RedeemAppleAppStoreInventoryItems** | 0.66 rps (60 in 90 seconds) | - |
-| **RedeemGooglePlayInventoryItems** | 0.66 rps (60 in 90 seconds) | - |
-| **RedeemMicrosoftStoreInventorItems** | 0.66 rps (60 in 90 seconds) | - |
-| **RedeemNintendoEShopInventoryItems** | 0.66 rps (60 in 90 seconds) | - |
-| **RedeemPlayStationStoreInventoryItems** | 0.66 rps (60 in 90 seconds) | - |
-| **RedeemSteamInventoryItems** | 0.66 rps (60 in 90 seconds) | - |
+| **RedeemAppleAppStoreInventoryItems** | 0.16 rps (10 in 60 seconds) | - |
+| **RedeemGooglePlayInventoryItems** | 0.16 rps (10 in 60 seconds) | - |
+| **RedeemMicrosoftStoreInventoryItems** | 0.16 rps (10 in 60 seconds) | - |
+| **RedeemNintendoEShopInventoryItems** | 0.16 rps (10 in 60 seconds) | - |
+| **RedeemPlayStationStoreInventoryItems** | 0.16 rps (10 in 60 seconds) | - |
+| **RedeemSteamInventoryItems** | 0.16 rps (10 in 60 seconds) | - |
 
 ## API Limits
 
@@ -166,7 +166,7 @@ Up to 20GB of catalog data are allowed per Catalog creator entity. This limit is
 
 ### Titles
 
-Tiles have a **512 character limit** per country code.
+Titles have a **512 character limit** per country code.
 
 ### Descriptions
 
diff --git a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/google.md b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/google.md
index 53e3012d6..1c9f2bc4e 100644
--- a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/google.md
+++ b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/google.md
@@ -108,7 +108,7 @@ It's time to move on to the [Google Play Console](https://play.google.com/consol
 
     ![Add app permissions](../../media/marketplace-integrations/google/add-app-permissions.png)
 
-6. From the list of apps, choose the one you want your account to be linked to. In this case, it's **Economy V2 Playfab Test App**. Once selected, press **Apply**.
+6. From the list of apps, choose the one you want your account to be linked to. In this case, it's **Economy V2 PlayFab Test App**. Once selected, press **Apply**.
 
     ![App selection](../../media/marketplace-integrations/google/app-selection.png)
 
diff --git a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/microsoft.md b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/microsoft.md
new file mode 100644
index 000000000..501a31ec9
--- /dev/null
+++ b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/microsoft.md
@@ -0,0 +1,177 @@
+---
+title: Marketplace integration - Microsoft Store
+author: mareg
+description: How to redeem Microsoft Store in-app purchases through PlayFab Economy v2
+ms.author: mareg
+ms.date: 02/23/2026
+ms.topic: tutorial
+ms.service: azure-playfab
+keywords: playfab, integration, marketplace, microsoft store, xbox, redeem, consumable, durable
+ms.localizationpriority: medium
+---
+
+# Marketplace integration: Microsoft Store
+
+This tutorial shows you how to redeem Microsoft Store in-app purchases (including Xbox) through PlayFab Economy v2 using the [RedeemMicrosoftStoreInventoryItems](/rest/api/playfab/economy/inventory/redeem-microsoft-store-inventory-items) API.
+
+By the end of this tutorial, you:
+
+- Created an add-on in Partner Center
+- Configured the required Partner Center and PlayFab settings
+- Linked your Microsoft Store product to a PlayFab catalog Bundle
+- Called the Redeem API and verified items in your player's inventory
+
+## Prerequisites
+
+1. A [Partner Center](https://partner.microsoft.com/) account with access to your app.
+2. An app already created in Partner Center.
+3. A Title already created in [Game Manager](https://developer.playfab.com/).
+4. The player calling the Redeem API must be authenticated to PlayFab using an Xbox Live identity (for example, via `LoginWithXbox`). Players authenticated with other identity types (such as CustomID or email) do not have the Xbox context required for this flow.
+
+## Supported product types
+
+The `RedeemMicrosoftStoreInventoryItems` API supports the following Microsoft Store product types:
+
+- **Developer-managed consumable** — Products that can be purchased, used, and purchased again (for example, in-game currency packs). The game service is responsible for tracking fulfillment.
+- **Durable** — Products that are purchased once and owned permanently (for example, DLC, expansion packs, season passes, or cosmetic items).
+
+> [!IMPORTANT]
+> **Store-managed consumables are not supported.** PlayFab Economy v2 cannot redeem Store-managed consumables. If your add-on is configured as a Store-managed consumable, the Redeem API returns an HTTP 200 response with empty results and no error, making the issue difficult to diagnose.
+
+## Step 1: Create your add-on in Partner Center
+
+1. Sign in to [Partner Center](https://partner.microsoft.com/) and navigate to your app.
+2. Under **Add-ons**, select **Create a new add-on**.
+3. Select the appropriate product type:
+   - **Developer-managed consumable** for items that can be repurchased (currency, consumable packs).
+   - **Durable** for one-time purchases (DLC, season passes, cosmetic unlocks).
+4. Complete the add-on configuration (pricing, descriptions, and so on) and submit it.
+
+> [!IMPORTANT]
+> When creating a Developer-managed consumable, Partner Center displays a warning that reads: *"Xbox requires consumables to be managed, so do not use this option and create a 'managed consumable' add-on instead. If you have any questions, contact your Microsoft representative."**
+>
+> This warning reflects general Xbox platform guidance and **does not apply to the PlayFab redemption flow**. Developer-managed consumables work correctly on Xbox when used with PlayFab's `RedeemMicrosoftStoreInventoryItems` API. You can safely proceed with this product type.
+
+5. After creating your add-on, note the **Store ID**—the alphanumeric string (for example, `9NBLGGH42CFD`) shown in Partner Center. Use this value for PlayFab, **not** the developer-defined Product ID, or the add-on name.
+
+For more information on product types, see [Choosing the right product type](/gaming/gdk/docs/store/commerce/getting-started/xstore-choosing-the-right-product-type).
+
+## Step 2: Configure Product Group, Dev Studio, and Business Partner ID
+
+This step configures the delegated Xbox Security Token Service (XSTS) token flow that PlayFab uses to query the Microsoft Store Collections API on behalf of the player.
+
+> [!WARNING]
+> The Product Group, Dev Studio, and Business Partner ID configuration is the most commonly missed step. Without it, the Redeem API call succeeds (HTTP 200) but the Collections API returns zero items—resulting in empty `Succeeded`, `Failed`, and `TransactionIds` arrays with no error message.
+
+1. In [Partner Center](https://partner.microsoft.com/), navigate to **Developer Settings** > **Xbox Live** > **Web Services** and generate a Business Partner Certificate if you have not already.
+2. Navigate to **Developer Settings** > **Xbox Live** > **Business Partner** and note the **Business Partner ID** that matches the web service your relying party is tied to.
+3. Create a **Dev Studio** (or use an existing one) and set its **Dev Studio ID** to match the **Business Partner ID** from step 2. If the Dev Studio already has a different ID, create a new Dev Studio rather than changing the existing value. Changing it can break existing services.
+4. Create a **Product Group** and assign it to the Dev Studio from step 3.
+5. Add your game product **and** all of your add-ons to the **Included in this product group** list. Items must be explicitly moved from the "available" side to the "included" side.
+6. Select **Save**.
+7. Navigate to your game's **Xbox Settings** page and confirm the linked **Business Partner** matches the one from step 2.
+8. **Republish** your game product and all add-ons to the Microsoft Store in your target sandbox or RETAIL environment.
+
+For the full configuration walkthrough, see [Configure products with delegated authentication (XSTS tokens)](/gaming/gdk/docs/store/commerce/service-to-service/xstore-authenticating-your-service#additional-configuration-required-to-view-and-manage-products-with-delegated-authentication-xsts-tokens).
+
+## Step 3: Enable the Xbox Network add-on in Game Manager
+
+The Xbox Network add-on links your Partner Center product to your PlayFab title and enables Xbox token validation for Microsoft Store redemption.
+
+1. Open [Game Manager](https://developer.playfab.com/) and select your **Title**.
+2. Select **Add-ons** from the left navigation menu.
+3. Locate and select the **Xbox Network** add-on (labeled **Distribute for Xbox**).
+4. Select the correct **Seller ID** from the dropdown. If you do not see the correct Seller ID, select **Sign in with a different partner center account**.
+5. Select your **Partner Center Product ID** from the dropdown and confirm the **Xbox Live Title ID** (decimal) matches what you see in Partner Center under **Xbox services** > **Xbox Settings**.
+6. Select **Install Xbox Network** to save the configuration.
+
+For more details, see [Xbox Live add-on configuration](/gaming/playfab/identity/player-identity/platform-specific-authentication/xbox-live-add-on).
+
+> [!NOTE]
+> Game Manager also has a separate **Microsoft Store** add-on page (also under **Add-ons**). While it does not require configuration, it contains useful guidance including confirmation of supported product types and details on the Dev Studio ID and Business Partner ID setup.
+
+## Step 4: Create a PlayFab Bundle with Marketplace Mapping
+
+To link your Microsoft Store product to your PlayFab catalog, create a **Bundle** with a **Marketplace Mapping** (AlternateId).
+
+1. In [Game Manager](https://developer.playfab.com/), navigate to **Economy** > **Catalog (V2)** > **Bundles**.
+2. Select **New bundle** (or edit an existing one).
+3. Under the **Marketplace Mapping** section, add a new mapping:
+   - Set the **Marketplace type** to `MicrosoftStore` (case-sensitive, must be exactly `MicrosoftStore`).
+   - Set the **value** to the exact **Store ID** from Partner Center (for example, `9NBLGGH42CFD`). Do not use the developer-defined Product ID or the add-on name.
+4. Add the items you want the player to receive when this Bundle is redeemed (for example, in-game currency, virtual items).
+5. **Publish** the Bundle. Unpublished (draft) Bundles are not matched during redemption.
+
+For more information on alternate IDs, see [Alternate IDs](/gaming/playfab/economy-monetization/economy-v2/catalog/content-types-tags-and-properties#alternate-ids).
+
+## Step 5: Acquire and provide the Xbox token
+
+When calling the [RedeemMicrosoftStoreInventoryItems](/rest/api/playfab/economy/inventory/redeem-microsoft-store-inventory-items) API, you must provide a valid Xbox token in the `XboxToken` parameter.
+
+
+- If you are using the **GDK C API**, use:
+
+  ```cpp
+  XUserGetTokenAndSignatureAsync  // with method "POST", URL "https://playfabapi.com/", and empty body ""
+  ```
+
+All three parameters (method, URL, and body) must be provided exactly as shown. An incorrectly obtained token causes the Collections API query to fail silently, returning empty results with no error.
+
+## Step 6: Test the integration
+
+Before considering your integration complete, verify the full end-to-end flow:
+
+1. Ensure your add-on is published to the sandbox or environment you are testing in.
+2. Sign in as a test player using an Xbox Live identity and make a test purchase of the add-on through the Microsoft Store. The player must have an unredeemed purchase on their account before the Redeem API has anything to detect.
+3. Call `RedeemMicrosoftStoreInventoryItems` with the player's `XboxToken`.
+4. Verify the response contains entries in the `Succeeded` array and that the corresponding items appear in the player's PlayFab inventory.
+
+> [!NOTE]
+> **Developer-managed consumable fulfillment:** After a Developer-managed consumable is redeemed, PlayFab automatically reports it as **fulfilled** (consumed) with the Microsoft Store on your behalf. The fulfillment step is necessary before the player can purchase the consumable again. If the consumable does not appear as fulfilled after a successful redemption, retry the `RedeemMicrosoftStoreInventoryItems` call. If the issue persists, escalate to the PlayFab team through your support channel. For details, see [Managing consumables and refunds](/gaming/gdk/docs/store/commerce/service-to-service/xstore-managing-consumables-and-refunds).
+
+## Troubleshooting
+
+If the `RedeemMicrosoftStoreInventoryItems` call returns successfully (HTTP 200) but the `Succeeded`, `Failed`, and `TransactionIds` arrays in the response are all empty, the Microsoft Store Collections API is not finding any matching items to redeem. A configuration issue typically causes this behavior. Check the following items:
+
+| Issue | Resolution |
+|---|---|
+| **Wrong product type** | Ensure the add-on is a **Developer-managed consumable** or **Durable**, not a Store-managed consumable. PlayFab does not support Store-managed consumables. |
+| **Incorrect Store ID in PlayFab** | Confirm the Marketplace Mapping value matches the **Store ID** (alphanumeric string like `9NBLGGH42CFD`), not the developer-defined Product ID or add-on name. |
+| **Bundle not published** | Publish the Bundle in your PlayFab catalog. Draft Bundles are not matched during redemption. |
+| **Missing Product Group configuration** | Confirm your game and add-ons are included in a Product Group tied to the correct Dev Studio and Business Partner ID. The Product Group configuration is the most commonly missed step. See [Step 2](#step-2-configure-product-group-dev-studio-and-business-partner-id). |
+| **Xbox Network add-on not configured** | Install and configure the Xbox Network add-on in Game Manager. See [Step 3](#step-3-enable-the-xbox-network-add-on-in-game-manager). |
+| **No unredeemed purchase** | The player must have an unredeemed purchase of the product before the API can detect and redeem it. Make a test purchase first. |
+| **Consumable not fulfilled** | PlayFab automatically fulfills Developer-managed consumables after redemption. If a consumable was redeemed once but does not redeem again, retry the `RedeemMicrosoftStoreInventoryItems` call. If the issue persists, escalate to the PlayFab team through your support channel. See [Managing consumables and refunds](/gaming/gdk/docs/store/commerce/service-to-service/xstore-managing-consumables-and-refunds). |
+| **Sandbox mismatch** | Ensure the add-on is published to the same sandbox you are testing in. The Xbox token carries sandbox context, so both must match. |
+| **Invalid Xbox token** | Verify the token is obtained with the correct parameters: method `POST`, URL `https://playfabapi.com/`, and an empty body string `""`. |
+| **Player not authenticated with Xbox identity** | The player must be signed in to PlayFab using an Xbox Live identity (for example, via `LoginWithXbox`). Other identity types do not have the Xbox context required for redemption. |
+
+If the API returns an HTTP error (such as 400), check the error response for the following codes:
+
+| Error code | Description |
+|---|---|
+| `InvalidCatalogItemConfiguration` | The Bundle or Marketplace Mapping is misconfigured in the PlayFab catalog. |
+| `InvalidXboxLiveToken` | The Xbox token is invalid, expired, or obtained with incorrect parameters. |
+| `AccountNotLinked` | The player's PlayFab account is not linked to an Xbox Live identity. |
+| `XboxInaccessible` | PlayFab cannot reach Xbox services. The error may be transient. |
+| `XboxXASSExchangeFailure` | The XSTS token exchange failed. Verify your Business Partner and relying party configuration. |
+
+> [!TIP]
+> If the call succeeds (HTTP 200) but returns empty results and all other configuration looks correct, check the Product Group configuration first. The Product Group step is the most commonly missed step.
+
+## Note on PC / Windows titles
+
+This tutorial covers the Xbox flow, which uses delegated XSTS tokens (passed via the `XboxToken` parameter). For **PC / Windows titles**, Microsoft recommends using User Store IDs with Microsoft Entra ID for service-to-service authentication instead. For more information, see [Requesting a User Store ID for service-to-service authentication](/gaming/gdk/docs/store/commerce/service-to-service/xstore-requesting-a-userstoreid) and [Authenticating your service — User Store IDs](/gaming/gdk/docs/store/commerce/service-to-service/xstore-authenticating-your-service#authenticating-through-microsoft-entra-id-and-user-store-ids).
+
+## See also
+
+- [RedeemMicrosoftStoreInventoryItems API reference](/rest/api/playfab/economy/inventory/redeem-microsoft-store-inventory-items)
+- [Fraud prevention quickstart](/gaming/playfab/economy-monetization/economy-v2/fraud-prevention/quickstart)
+- [Xbox Live add-on configuration](/gaming/playfab/identity/player-identity/platform-specific-authentication/xbox-live-add-on)
+- [Authenticating your service (XSTS tokens)](/gaming/gdk/docs/store/commerce/service-to-service/xstore-authenticating-your-service)
+- [Choosing the right product type](/gaming/gdk/docs/store/commerce/getting-started/xstore-choosing-the-right-product-type)
+- [Consumable-based ecosystems](/gaming/gdk/docs/store/commerce/fundamentals/xstore-consumable-based-ecosystems)
+- [Managing consumables and refunds](/gaming/gdk/docs/store/commerce/service-to-service/xstore-managing-consumables-and-refunds)
+- [Alternate IDs (Marketplace Mapping)](/gaming/playfab/economy-monetization/economy-v2/catalog/content-types-tags-and-properties#alternate-ids)
+- [How to successfully integrate an Apple app into Game Manager](apple.md)
+- [How to successfully integrate a Google app into Game Manager](google.md)
diff --git a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/overview.md b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/overview.md
index ace6dec1c..5aea5df3c 100644
--- a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/overview.md
+++ b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/overview.md
@@ -17,12 +17,12 @@ Marketplace integration with PlayFab allows you to connect your game to various
 ## Supported Marketplaces
 
 ### Steam
-Integrate your game with Steam to leverage its extensive user base and robust infrastructure for in-game purchases. Configure the necessary settings in the Game Manager to connect your PlayFab title with Steam.
+Integrate your game with Steam to use its extensive user base and robust infrastructure for in-game purchases. To connect your PlayFab title with Steam, configure the necessary settings in Game Manager.
 
 See our [Steam integration documentation](steam.md).
 
 ### Apple
-Connect your game to the Apple App Store to enable in-app purchases for iOS users. Follow the integration steps in the Game Manager to ensure a smooth connection between PlayFab and Apple's marketplace.
+To enable in-app purchases for iOS users, connect your game to the Apple App Store. To ensure a smooth connection between PlayFab and Apple's marketplace, follow the integration steps in Game Manager.
 
 See our [Apple App Store integration documentation](apple.md).
 
@@ -31,4 +31,9 @@ Integrate with Google Play to offer in-app purchases for Android users. Set up t
 
 See our [Google Play Store integration documentation](google.md).
 
+### Microsoft Store
+To enable in-app purchases for Xbox and Windows users, integrate with the Microsoft Store. To link your PlayFab title with the Microsoft Store marketplace, configure the Xbox Network add-on in Game Manager and set up your Product Group in Partner Center.
+
+See our [Microsoft Store integration documentation](microsoft.md).
+
 By integrating with these marketplaces, you can streamline the purchase process for your players and manage all transactions through PlayFab's unified platform.
\ No newline at end of file
diff --git a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/toc.yml b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/toc.yml
index 917f0196f..55603507d 100644
--- a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/toc.yml
+++ b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-integrations/toc.yml
@@ -5,5 +5,7 @@ items:
     href: google.md
   - name: Apple App Store
     href: apple.md
+  - name: Microsoft Store
+    href: microsoft.md
   - name: Steam
     href: steam.md
\ No newline at end of file
diff --git a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-redemption/microsoft.md b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-redemption/microsoft.md
new file mode 100644
index 000000000..5ad1cb5be
--- /dev/null
+++ b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-redemption/microsoft.md
@@ -0,0 +1,156 @@
+---
+title: Redemption with the Microsoft Store Marketplace
+author: mareg
+description: Set up PlayFab and the Microsoft Store to enable purchases and redemption on Xbox and Windows
+ms.author: mareg
+ms.date: 02/22/2026
+ms.topic: tutorial
+ms.service: azure-playfab
+keywords: playfab, integration, marketplace, microsoft store, xbox, purchase, redemption
+ms.localizationpriority: medium
+---
+
+# Set up PlayFab and the Microsoft Store to enable purchases
+
+This tutorial shows you how to:
+
+- Create a purchasable product in the Microsoft Store
+- Map it to a PlayFab bundle
+- Redeem purchased items into a player's inventory using the [RedeemMicrosoftStoreInventoryItems](/rest/api/playfab/economy/inventory/redeem-microsoft-store-inventory-items) API
+
+## Prerequisites
+
+1. A Title in PlayFab's [Game Manager](https://developer.playfab.com/).
+2. An existing [integration between the selected Title and the Microsoft Store](../marketplace-integrations/microsoft.md), including:
+    - The **Xbox Network** add-on installed and configured in Game Manager.
+    - The **Product Group**, **Dev Studio**, and **Business Partner ID** configured in Partner Center.
+3. A [Partner Center](https://partner.microsoft.com/) account with access to your app.
+4. An app already created in Partner Center.
+5. The player calling the Redeem API must be authenticated to PlayFab using an Xbox Live identity (for example, via `LoginWithXbox`). Players authenticated with other identity types (such as CustomID or email) do not have the Xbox context required for this flow.
+
+## Step 1: Create your add-on in Partner Center
+
+If you did not create an add-on in Partner Center as part of the [marketplace integration setup](../marketplace-integrations/microsoft.md#step-1-create-your-add-on-in-partner-center), follow these steps:
+
+1. Sign in to [Partner Center](https://partner.microsoft.com/) and navigate to your app.
+2. Under **Add-ons**, select **Create a new add-on**.
+3. Select the appropriate product type:
+   - **Developer-managed consumable** for items that can be repurchased (currency, consumable packs).
+   - **Durable** for one-time purchases (DLC, season passes, cosmetic unlocks).
+4. Complete the add-on configuration (pricing, descriptions, and so on) and submit it.
+5. After creating your add-on, note the **Store ID**—the alphanumeric string (for example, `9NBLGGH42CFD`) shown in Partner Center. Use this value for the marketplace mapping in PlayFab, **not** the developer-defined Product ID, or the add-on name.
+
+> [!IMPORTANT]
+> **Store-managed consumables are not supported.** Only Developer-managed consumables and Durables work with the `RedeemMicrosoftStoreInventoryItems` API. Partner Center may display a warning suggesting that Developer-managed consumables are not supported on Xbox. This warning does not apply when using the PlayFab redemption flow. For more information, see [Choosing the right product type](/gaming/gdk/docs/store/commerce/getting-started/xstore-choosing-the-right-product-type).
+
+6. Publish the add-on to the sandbox or environment you intend to test in.
+
+## Step 2: Create a Bundle in Game Manager
+
+> [!NOTE]
+> Before creating a bundle in **Game Manager**, create and publish the items you want to add to the bundle in your Catalog. If you need guidance on how to create an item, refer to [this step](../../tutorials/craftingGame/crafting-game-game-manager.md#step-4---create-your-first-item).
+
+To enable a marketplace mapping between **Game Manager** and the **Microsoft Store**, you need to create a **Bundle** in Game Manager. A bundle can contain multiple items with different quantities, and PlayFab adds them to the player's inventory once redeemed. Follow these steps:
+
+1. Go to [Game Manager](https://developer.playfab.com/) and navigate to your **Title**.
+2. From the left navigation menu, choose **Engage** > **Economy**.
+3. Select the **Bundles** tab.
+4. Select **New bundle**.
+5. Add any information you want to the **Bundle**, such as items and prices.
+6. Scroll down to the end of the page and select **Save and publish** if you want it to be redeemable by players right away. Select **Save as draft** if you want to publish it at a later date.
+
+### Add items to your Bundle
+
+A bundle by itself does not grant any items to a player. You must first link items to it. Once redeemed, the bundle grants those items to the specific player.
+
+To add items to your bundle:
+
+1. Go to the **Items** section in edit mode.
+2. Select **Add**. A window appears showing all your catalog items.
+3. Find your desired item and select **Add** next to it.
+4. Select the **Add** button at the bottom.
+
+## Step 3: Enable marketplace mapping
+
+To ensure that when a player purchases a product from the Microsoft Store it gets properly matched and assigned in Game Manager, you must configure the **Marketplace Mapping** on your Bundle.
+
+1. Navigate to your bundle in edit mode.
+2. Scroll down to the **Marketplace Mapping** section.
+3. From the **Marketplace** dropdown, select **MicrosoftStore** (case-sensitive, must be exactly `MicrosoftStore`).
+4. For your **Marketplace ID**, use the exact **Store ID** from Partner Center (for example, `9NBLGGH42CFD`). Do **not** use the developer-defined Product ID.
+5. Select the **+** at the right side of that row and **Save** your changes.
+
+> [!IMPORTANT]
+> The Bundle must be **published** (not left as a draft) for it to be matched during redemption. The redemption API does not detect unpublished catalog items.
+
+For more information on alternate IDs, see [Alternate IDs](/gaming/playfab/economy-monetization/economy-v2/catalog/content-types-tags-and-properties#alternate-ids).
+
+## Step 4: Authenticate your player
+
+Before making a redemption call, you must ensure that the player is properly authenticated. For Xbox and Microsoft Store scenarios, use [LoginWithXbox](/rest/api/playfab/client/authentication/login-with-xbox) to authenticate the player with PlayFab.
+
+After a successful call to `LoginWithXbox`, PlayFab returns an `EntityToken` that you must use in the headers of your redemption call with the `X-EntityToken` key.
+
+## Step 5: Acquire the Xbox token
+
+The `RedeemMicrosoftStoreInventoryItems` API requires a valid Xbox token in the `XboxToken` parameter. This token is separate from the `EntityToken` used for authentication.
+
+- If you are using the **GDK C API**, use:
+
+  ```cpp
+  XUserGetTokenAndSignatureAsync  // with method "POST", URL "https://playfabapi.com/", and empty body ""
+  ```
+
+All three parameters (method, URL, and body) must be provided exactly as shown. An incorrectly obtained token causes the Microsoft Store Collections API query to fail silently, returning no items.
+
+## Step 6: Make a purchase
+
+The player must purchase the add-on from the Microsoft Store before you can redeem it through PlayFab. This purchase can be made through the Xbox or Windows Store interface.
+
+> [!NOTE]
+> If you are testing in a sandbox environment, ensure the player account and the add-on are both published to the same sandbox. The player must have an **unredeemed purchase** on their account for the redemption API to find items to redeem.
+
+## Step 7: Redeem the purchase
+
+With your player authenticated, the Xbox token acquired, and a purchase completed, you are ready to call the [RedeemMicrosoftStoreInventoryItems](/rest/api/playfab/economy/inventory/redeem-microsoft-store-inventory-items) API.
+
+Include the `EntityToken` as the `X-EntityToken` header, and provide the Xbox token in the request body:
+
+```json
+{
+    "XboxToken": "{Your Xbox token from GetTokenAndSignatureAsync}"
+}
+```
+
+### How redemption works
+
+When the `RedeemMicrosoftStoreInventoryItems` call is made, PlayFab uses the Xbox token to query the Microsoft Store Collections API for any unredeemed purchases associated with the player's account. It then matches those purchases against the **Store IDs** configured in your PlayFab Bundle Marketplace Mappings and grants the corresponding items.
+
+A successful response includes a `200` status code alongside the [RedeemMicrosoftStoreInventoryItemsResponse](/rest/api/playfab/economy/inventory/redeem-microsoft-store-inventory-items), which contains:
+
+- **Succeeded**—A list of successfully redeemed items.
+- **Failed**—A list of items that failed to redeem.
+- **TransactionIds**—IDs for each redemption transaction.
+
+Each redemption action triggers a corresponding event in the player's transaction history, which can be retrieved from the **Transaction History (V2)** tab under the player's overview page in [Game Manager](https://developer.playfab.com/).
+
+Alongside the record in the player's transaction history, an `items_redeemed` **PlayStream** event is also triggered and logged. You can access these logs for your Title by going to the **Data** page under the **Analyze** section of the left navigation bar in [Game Manager](https://developer.playfab.com/).
+
+### Fulfillment for Developer-managed consumables
+
+If the redeemed product is a **Developer-managed consumable**, PlayFab automatically reports it as **fulfilled** (consumed) with the Microsoft Store on your behalf after a successful redemption. The fulfillment step is necessary before the player can repurchase the same consumable. If the consumable does not appear as fulfilled after a successful redemption, retry the `RedeemMicrosoftStoreInventoryItems` call. If the issue persists, escalate to the PlayFab team through your support channel. Durables do not require fulfillment because they are one-time purchases. For more information, see [Managing consumables and refunds](/gaming/gdk/docs/store/commerce/service-to-service/xstore-managing-consumables-and-refunds).
+
+## Troubleshooting
+
+If the redemption call returns `200` but all three arrays (`Succeeded`, `Failed`, `TransactionIds`) are empty, the Microsoft Store Collections API is not finding any matching items. This result typically indicates a configuration issue. See the [troubleshooting section](../marketplace-integrations/microsoft.md#troubleshooting) in the Microsoft Store integration guide for a full list of common causes and resolutions.
+
+If the API returns an HTTP error (such as 400), check the error response for codes like `InvalidCatalogItemConfiguration`, `InvalidXboxLiveToken`, or `AccountNotLinked`.
+
+## See also
+
+- [Microsoft Store marketplace integration](../marketplace-integrations/microsoft.md)
+- [RedeemMicrosoftStoreInventoryItems API reference](/rest/api/playfab/economy/inventory/redeem-microsoft-store-inventory-items)
+- [Fraud prevention quickstart](/gaming/playfab/economy-monetization/economy-v2/fraud-prevention/quickstart)
+- [Xbox Live add-on configuration](/gaming/playfab/identity/player-identity/platform-specific-authentication/xbox-live-add-on)
+- [How to successfully integrate an Apple app into Game Manager](../marketplace-integrations/apple.md)
+- [How to successfully integrate a Google app into Game Manager](../marketplace-integrations/google.md)
diff --git a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-redemption/overview.md b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-redemption/overview.md
index a6a050ca9..f7742ed2f 100644
--- a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-redemption/overview.md
+++ b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-redemption/overview.md
@@ -18,25 +18,29 @@ After a successful marketplace integration, the next step is to focus on redeemi
 
 ### Apple
 
-Redemption from the Apple marketplace involves verifying the purchase receipt with Apple's servers and updating the player's inventory or account accordingly. For more details see [Apple redemption documentation](apple.md)
+Redemption from the Apple marketplace involves verifying the purchase receipt with Apple's servers and updating the player's inventory or account accordingly. For more information, see [Apple redemption documentation](apple.md).
 
 ### Google
 
-Redemption from the Google marketplace involves verifying the purchase receipt with Google's servers and updating the player's inventory or account accordingly. For more details see [Google redemption documentation](google.md)
+Redemption from the Google marketplace involves verifying the purchase receipt with Google's servers and updating the player's inventory or account accordingly. For more information, see [Google redemption documentation](google.md).
+
+### Microsoft Store
+
+Redemption from the Microsoft Store involves using an Xbox token to query the Microsoft Store Collections API for unredeemed purchases and granting the corresponding items to the player's inventory. For more information, see [Microsoft Store redemption documentation](microsoft.md).
 
 ### Steam
 
-Redemption from the Steam marketplace involves verifying the purchase receipt with Steam's servers and updating the player's inventory accordingly. For more details see [Steam redemption documentation](steam.md)
+Redemption from the Steam marketplace involves verifying the purchase receipt with Steam's servers and updating the player's inventory accordingly. For more information, see [Steam redemption documentation](steam.md).
 
 ## Subscription Redemption
 
 ### Apple Subscriptions
 
-Subscription redemption from the Apple marketplace involves verifying the subscription receipt with Apple's servers and updating the player's account accordingly. For more details see [Apple subscription documentation](ios-subscription-redemption.md).
+Subscription redemption from the Apple marketplace involves verifying the subscription receipt with Apple's servers and updating the player's account accordingly. For more information, see [Apple subscription documentation](ios-subscription-redemption.md).
 
 ### Google Subscriptions
 
-Subscription redemption from the Google marketplace involves verifying the subscription receipt with Google's servers and updating the player's account accordingly. For more details see [Google subscription documentation](google-subscription-redemption.md).
+Subscription redemption from the Google marketplace involves verifying the subscription receipt with Google's servers and updating the player's account accordingly. For more information, see [Google subscription documentation](google-subscription-redemption.md).
 
 ## Conclusion
 
diff --git a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-redemption/toc.yml b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-redemption/toc.yml
index 94c081921..615836729 100644
--- a/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-redemption/toc.yml
+++ b/playfab-docs/economy-monetization/economy-v2/marketplace/marketplace-redemption/toc.yml
@@ -3,6 +3,8 @@ items:
     href: overview.md
   - name: Google redemption
     href: google.md
+  - name: Microsoft Store redemption
+    href: microsoft.md
   - name: Steam redemption
     href: steam.md
   - name: Google subscription redemption
diff --git a/playfab-docs/economy-monetization/economy-v2/overview.md b/playfab-docs/economy-monetization/economy-v2/overview.md
index c789d597f..a5acbbd0f 100644
--- a/playfab-docs/economy-monetization/economy-v2/overview.md
+++ b/playfab-docs/economy-monetization/economy-v2/overview.md
@@ -14,58 +14,79 @@ ms.localizationpriority: medium
 
 [!INCLUDE [notice](../../includes/_economy-release.md)]
 
-Economy v2 is a major change from the existing PlayFab Monetization suite of features. The goal of the change is to support titles with hundreds of millions of active players, large progression systems, and giant inventories. The architecture has been rebuilt on the modern Azure Stack from the ground up and it targets developers' needs related to the following features.
+Economy v2 is a major change from the existing PlayFab Monetization suite of features. The goal of the change is to support titles with hundreds of millions of active players, large progression systems, and giant inventories. The architecture is rebuilt on the modern Azure Stack from the ground up. It targets developers' needs related to the following features.
 
 * Idempotent transactions
 * Batch operations
 * Handling of high [concurrency](catalog/etags.md) rates, especially with inventory interactions
-* Large unified catalog (up to 20GB per entity) of in-game goods or user-generated content (UGC), supporting multiple entities
-* Individual Catalog Item documents instead of all items being stored in a single document
-* Large player inventories ([3,000+ items](limits.md))
+* Large unified catalog (up to 20 GB per entity) of in-game goods or user-generated content (UGC), supporting multiple entities
+* Individual Catalog Item documents instead of all items stored in a single document
+* Large player inventories ([thousands of items](limits.md))
 * Integration with PlayFab Entities
 
-Economy v2 is designed with the same flexibility and extensibility that you would expect from other PlayFab services. Although the architecture is new to PlayFab, it's battle-tested and it supports internal Microsoft titles, such as **Minecraft**, **Sea of Thieves**, and **Flight Simulator**.
+Economy v2 is designed with the same flexibility and extensibility that you expect from other PlayFab services. Although the architecture is new to PlayFab, it's battle-tested and supports internal Microsoft titles, such as **Minecraft**, **Sea of Thieves**, and **Flight Simulator**.
 
-Interested to find out why we made Economy V2 and how you can use the improvements in your title?
+Interested to find out why we made Economy v2 and how you can use the improvements in your title?
 >[!VIDEO https://www.youtube.com/embed/NcvFFgTZ6ek]
 
-#### PlayFab Economy v2
+## Which version of Economy should I use?
 
-Provides an introduction to the Azure PlayFab Economy v2 and discusses key improvements in V2.
+Use version 2. If you're on version 1, consider upgrading. Although Microsoft isn't deprecating v1 and will maintain and support it for all titles, it's in bugfix-only mode. The new Economy features are developed only for version 2. For more information on the differences between the two versions, see [FAQ](faq.md).
 
->[!VIDEO https://www.youtube.com/embed/NcvFFgTZ6ek]
+## New in Economy v2
 
-## Which version of Economy should I use?
+Economy v2 introduces several new capabilities that aren't available in v1:
 
-You should use version 2. If you're on version 1, you should look at upgrading. Although we're _not_ deprecating v1 and will maintain and support it for all titles, it's in bugfix-only mode. The new Economy features are being developed only for version 2. For more information on the differences between the two versions, see [FAQ](faq.md).
+* Updated interactions between the [inventory](inventory/index.md) and catalog allow you to support unique items, nonunique items, stacks of items, and multiple stacks of items.
+* You can upload and manage [metadata](catalog/content-types-tags-and-properties.md) and content, including images and files, alongside your catalog items.
+* You can create [deep links](catalog/deep-links.md) to game content by using the economy settings.
+* Customizable [catalog search](catalog/search.md) enables you to set up custom views with tags and content types.
+* A simple way to [localize](catalog/localization.md) item descriptions and titles.
+* APIs that support PlayerEntity-facing [Item Ratings and Reviews](catalog/ratings.md).
+* Support for custom workflow in [authoring with draft states](catalog/item-status.md) and [policy permissions sets for catalog admins and reviewers](settings.md). You can prepublish catalog items with a future start date.
+* [Bundle items](catalog/bundles.md) that you can link to multiple external marketplace items.
+* [Inventory Collections](inventory/collections.md) that allow a single player to have multiple inventories, such as per-character or per-platform.
+* [Inventory Stacks](inventory/stacks.md) that enable multiple distinct instances of the same item within one inventory, each with its own amount and properties.
+* [TurboLoading](inventory/turboloading.md) that loads an entire inventory (up to 10,000 items) in a single compressed API call for faster startup.
+* [User Generated Content (UGC)](ugc/overview.md) that empowers players to create, upload, and search for moderated content by using a built-in moderation pipeline.
+* [ExecuteInventoryOperations](/rest/api/playfab/economy/inventory/execute-inventory-operations) batches inventory operations atomically in a single request. If any operation fails, the entire batch is rolled back.
+* [ETags](catalog/etags.md) that provide optimistic concurrency control for catalog and inventory updates, preventing race conditions.
+* Built-in [fraud prevention and receipt validation](fraud-prevention/index.md) across Apple, Google, Steam, Nintendo, PlayStation Store, and Microsoft Store marketplaces.
+* [Targeted offers](player-segmented-monetization/targeted-offers.md) that enable segment-exclusive stores with dynamic pricing tailored to different player groups.
 
-## Changes in key features
+## Changes from v1
 
-Features of Economy that were too restrictive to be useful didn't make the cut to v2. To remediate this, we launched Azure Functions as an enhanced successor to CloudScript. We also provided a recipe-style documentation as a starting point for your own custom implementations. We then focused our efforts on what you told us was most important.
+Features of Economy that were too restrictive to be useful didn't make the cut to v2. To remediate this limitation, the product team launched Azure Functions as an enhanced successor to CloudScript. The team also provided recipe-style documentation as a starting point for your own custom implementations. The product team then focused efforts on what you told them was most important.
 
-The following v1 features aren't included in Economy v2:
+The following v1 features aren't included as native item types in Economy v2. Some features can be partially replicated by using v2 building blocks, while others require custom logic through [Azure Functions](/azure/azure-functions/functions-overview).
 
-* Trading
-* Converting items  
-* Limited items
-* Drop tables
-* Containers
-* Recharge rates
-* Store support for segments
+### Partially supported
 
-Economy v2 brings new useful features:
+You can achieve these v1 features by using existing v2 APIs and building blocks:
+
+* **Converting items**: You can achieve item conversion (crafting) by using the [ExecuteInventoryOperations](/rest/api/playfab/economy/inventory/execute-inventory-operations) API, which atomically subtracts input items and adds the result in a single request. For an example, see the [Crafting Game tutorial](tutorials/craftingGame/game-context.md).
+* **Containers (fixed contents)**: You can implement containers that always grant the same items by using [bundles and virtual currency](tutorials/containers-with-fixed-contents.md). A currency token represents the container, and purchasing a bundle priced at one token grants the contents.
+
+### Not supported
+
+These v1 features have no native v2 equivalent and require custom logic (for example, by using Azure Functions):
+
+* **Trading**: V1 provided atomic two-way item swaps between players. V2 doesn't have a native trading API. Implementing player-to-player trading requires custom orchestration with [Azure Functions](/azure/azure-functions/functions-overview).
+* **Limited items**: V1 supported catalog items with a finite global supply. V2 requires server-side logic to track and enforce a global quantity cap.
+* **Drop tables**: V1 had built-in weighted random loot tables. V2 requires custom random selection logic by using Azure Functions. For a complete implementation, see the [drop tables and randomized loot tutorial](tutorials/drop-tables-and-randomized-loot.md).
+* **Containers (randomized)**: V1 containers paired with drop tables granted random items on open. V2 requires custom logic to subtract the container and grant randomly selected items. See the [drop tables and randomized loot tutorial](tutorials/drop-tables-and-randomized-loot.md).
+* **Recharge rates**: V1 allowed items with usage counts that regenerated over time. V2 requires custom time-based logic to calculate and grant regenerated amounts.
+* **Store support for segments**: V1 allowed automatic linking between player segments and stores. V2 has both [Stores](catalog/stores.md) and [Segments](../../player-progression/player-data/player-segments.md) and supports [targeted offers](player-segmented-monetization/targeted-offers.md) with segment-exclusive stores, but you must manually set up the configuration rather than use automatic assignment.
 
-* Updated interactions between the [inventory](inventory/index.md) and catalog allow you to support unique items, non-unique items, stacks of items, and multiple stacks of items.
-* Catalog items have [metadata](catalog/content-types-tags-and-properties.md) and content, including images and files, can be uploaded and managed alongside your catalog.
-* [Deep links](catalog/deep-links.md) to game content can now be created using the economy settings.
-* Customizable [catalog search](catalog/search.md) allows you to set up custom views with tags and content types.
-* Simple way to [localize](catalog/localization.md) item descriptions and titles.
-* APIs that support PlayerEntity-facing [Item Ratings and Reviews](catalog/ratings.md).
-* Support for custom workflow in [authoring with draft states](catalog/item-status.md) and [policy permissions sets for catalog admins and reviewers](settings.md). You can prepublish catalog items with a future start date.
-* [Bundle items](catalog/bundles.md) that can be linked to multiple external marketplace items.
 
 ## See also
 
 * [Quickstart](quickstart.md)
 * [Settings](settings.md)
 * [Stores](catalog/stores.md)
+* [Inventory](inventory/index.md)
+* [Marketplace Integrations](marketplace/marketplace-integrations/overview.md)
+* [Fraud Prevention](fraud-prevention/index.md)
+* [TurboLoading](inventory/turboloading.md)
+* [Limits](limits.md)
+* [FAQ](faq.md)
diff --git a/playfab-docs/economy-monetization/economy-v2/quickstart.md b/playfab-docs/economy-monetization/economy-v2/quickstart.md
index 6750d7489..17e9a3c0a 100644
--- a/playfab-docs/economy-monetization/economy-v2/quickstart.md
+++ b/playfab-docs/economy-monetization/economy-v2/quickstart.md
@@ -197,7 +197,7 @@ Fill in the required metadata – there are only four required properties (_Crea
 Create a "Draft" Catalog Item by calling the [CreateDraftItem](/rest/api/playfab/economy/catalog/create-draft-item) endpoint:
 
 * The EntityToken (from GetEntityToken or other PlayFab `login` call) in the X-EntityToken header
-* The Playfab Title ID in the item's CreatorEntity.Id
+* The PlayFab Title ID in the item's CreatorEntity.Id
 
 ```bash
 curl \
@@ -355,7 +355,7 @@ Create a Draft Currency Catalog Item by calling the [CreateDraftItem](/rest/api/
 
 * An EntityToken with Catalog Permissions  
 * The Entity.Id as the item 'Creator'  
-* The Playfab Title ID
+* The PlayFab Title ID
 * The Item should be a Bundle of type 'Currency' and contain a Title and Description
 
 Call PublishItem with the ItemId returned from the CreateDraftItem.
diff --git a/playfab-docs/economy-monetization/economy-v2/settings.md b/playfab-docs/economy-monetization/economy-v2/settings.md
index 7dc331317..8498e374c 100644
--- a/playfab-docs/economy-monetization/economy-v2/settings.md
+++ b/playfab-docs/economy-monetization/economy-v2/settings.md
@@ -14,7 +14,7 @@ ms.localizationpriority: medium
 
 [!INCLUDE [notice](../../includes/_economy-release.md)]
 
-Economy v2 includes the following configuration that can be updated in Game Manager bg selecting **Economy** > **Catalog (V2)** then **⚙️ Settings**.
+Economy v2 includes the following configuration that can be updated in Game Manager by selecting **Economy** > **Catalog (V2)** then **⚙️ Settings**.
 
 These settings can also be set and accessed via APIs using the [UpdateCatalogConfig](/rest/api/playfab/economy/catalog/update-catalog-config) and [GetCatalogConfig](/rest/api/playfab/economy/catalog/get-catalog-config) calls respectively. Catalog Config APIs can only be called by [title entities](../../live-service-management/game-configuration/entities/index.md#title).
 
diff --git a/playfab-docs/economy-monetization/economy-v2/tutorials/containers-with-fixed-contents.md b/playfab-docs/economy-monetization/economy-v2/tutorials/containers-with-fixed-contents.md
new file mode 100644
index 000000000..d7c7a2262
--- /dev/null
+++ b/playfab-docs/economy-monetization/economy-v2/tutorials/containers-with-fixed-contents.md
@@ -0,0 +1,266 @@
+---
+title: Containers with fixed contents in Economy v2
+author: ernestoc
+description: How to implement fixed-contents containers in Economy v2 using bundles and virtual currency
+ms.author: ernestoc
+ms.date: 02/23/2026
+ms.topic: tutorial
+ms.service: azure-playfab
+keywords: playfab, commerce, economy, containers, bundles, virtual currency
+ms.localizationpriority: medium
+---
+
+# Containers with fixed contents in Economy v2
+
+[!INCLUDE [notice](../../../includes/_economy-release.md)]
+
+Economy v1 (Legacy) had a built-in **Containers** feature—special catalog items that, when opened, granted their contents to the player's inventory. Economy v2 doesn't include containers as a native item type, but you can achieve the same behavior for **fixed-contents containers** (containers that always grant the same items) by using a combination of virtual currency and bundles.
+
+## How it works
+
+The pattern uses three Economy v2 building blocks:
+
+1. **A virtual currency (or stackable item)** that represents the container itself—for example, "Treasure Chest Token."
+2. **A Bundle** priced at 1 of that currency, containing the items the container should grant.
+3. **A purchase call** where the player spends 1 token to buy the bundle, which automatically unpacks and grants the items.
+
+From the player's perspective, they receive a token (via gameplay rewards, store purchases, and so on), then "open" it to get the items inside—exactly how V1 containers worked.
+
+## Prerequisites
+
+- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A Title created in [Game Manager](https://developer.playfab.com/).
+- At least one published catalog item that you want the container to grant.
+
+## Step 1: Create a virtual currency for the container
+
+Create a virtual currency that represents the container. Each unit of this currency acts as one unopened container.
+
+### [Game Manager](#tab/create-currency-gm)
+
+1. Go to **Economy** > **Catalog (V2)** > **Currency**.
+2. Select **New currency**.
+3. Set the **Title** to a descriptive name, such as `Treasure Chest`.
+4. Set the **FriendlyId** to a short code, such as `tc`.
+5. Select **Save and publish**.
+
+### [REST API](#tab/create-currency-api)
+
+Call [CreateDraftItem](/rest/api/playfab/economy/catalog/create-draft-item):
+
+```json
+{
+  "Item": {
+    "CreatorEntity": {
+      "Id": "{{TitleID}}",
+      "Type": "title"
+    },
+    "Type": "currency",
+    "AlternateIds": [
+      {
+        "Type": "FriendlyId",
+        "Value": "tc"
+      }
+    ],
+    "Title": {
+      "NEUTRAL": "Treasure Chest"
+    },
+    "Description": {
+      "NEUTRAL": "A treasure chest that can be opened to reveal its contents."
+    },
+    "StartDate": "2023-07-27T00:00:00.000Z"
+  },
+  "Publish": true
+}
+```
+
+---
+
+## Step 2: Create a bundle priced at one container token
+
+Create a bundle that contains the items you want the container to grant. Price the bundle at exactly one unit of the container currency.
+
+### [Game Manager](#tab/create-bundle-gm)
+
+1. Go to **Economy** > **Catalog (V2)** > **Bundles**.
+2. Select **New bundle**.
+3. Set the **Title** to describe the container's contents, such as `Treasure Chest Contents`.
+4. Under **Items**, add the items and quantities you want the container to grant—for example, 1 **Legendary Sword** and 100 **Gold**.
+5. Under **Price**, set the price to **1** of your container currency (**Treasure Chest**).
+6. Select **Save and publish**.
+
+### [REST API](#tab/create-bundle-api)
+
+Call [CreateDraftItem](/rest/api/playfab/economy/catalog/create-draft-item):
+
+```json
+{
+  "Item": {
+    "Type": "bundle",
+    "Title": {
+      "NEUTRAL": "Treasure Chest Contents"
+    },
+    "StartDate": "2023-07-27T00:00:00.000Z",
+    "ItemReferences": [
+      {
+        "Id": "{{LegendarySwordID}}",
+        "Amount": 1
+      },
+      {
+        "Id": "{{GoldCurrencyID}}",
+        "Amount": 100
+      }
+    ],
+    "PriceOptions": {
+      "Prices": [
+        {
+          "Amounts": [
+            {
+              "ItemId": "{{TreasureChestCurrencyID}}",
+              "Amount": 1
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Publish": true
+}
+```
+
+---
+
+When a player purchases this bundle, the bundle is [automatically unpacked](../catalog/bundles.md#purchasing-and-unpacking-bundles)—the individual items go directly to the player's inventory.
+
+## Step 3: Grant container tokens to players
+
+Grant the container currency to players through any mechanism that fits your game design:
+
+- **Gameplay rewards**—Grant tokens after completing a level, quest, or achievement by using [AddInventoryItems](/rest/api/playfab/economy/inventory/add-inventory-items).
+- **Store purchases**—Sell the container token in a [Store](../catalog/stores.md) for another virtual currency or real money.
+- **Battle pass / seasonal rewards**—Include the token as a reward tier.
+
+Example using `AddInventoryItems` to grant three Treasure Chest tokens:
+
+```json
+{
+  "Entity": {
+    "Type": "title_player_account",
+    "Id": "{{PlayerID}}"
+  },
+  "Item": {
+    "Id": "{{TreasureChestCurrencyID}}"
+  },
+  "Amount": 3
+}
+```
+
+## Step 4: Open the container
+
+When the player wants to open a container, call [PurchaseInventoryItems](/rest/api/playfab/economy/inventory/purchase-inventory-items) to buy the bundle with one container token:
+
+```json
+{
+  "Entity": {
+    "Type": "title_player_account",
+    "Id": "{{PlayerID}}"
+  },
+  "Item": {
+    "Id": "{{TreasureChestContentsBundleID}}"
+  },
+  "Amount": 1,
+  "PriceAmounts": [
+    {
+      "ItemId": "{{TreasureChestCurrencyID}}",
+      "Amount": 1
+    }
+  ]
+}
+```
+
+After a successful call, the player's inventory is updated: One Treasure Chest token is deducted and the bundle's contents (one Legendary Sword + 100 Gold) are added.
+
+## Multiple container types
+
+Create multiple container types by repeating this pattern. For example:
+
+| Container | Currency (FriendlyId) | Bundle contents |
+|---|---|---|
+| Treasure Chest | `tc` | One Legendary Sword + 100 Gold |
+| Supply Crate | `sc` | Five Health Potions + 3 Mana Potions |
+| Premium Box | `pb` | One Rare Mount + 500 Gold + 50 Gems |
+
+Each container type has its own currency and bundle.
+
+## Using a Store for container purchases
+
+Use a [Store](../catalog/stores.md) to override the container bundle's price. By using a store, you can offer the same container at different prices in different contexts (for example, a discounted "open" cost during an event):
+
+```json
+{
+  "Item": {
+    "Type": "store",
+    "Title": {
+      "NEUTRAL": "Event Store"
+    },
+    "ItemReferences": [
+      {
+        "Id": "{{TreasureChestContentsBundleID}}",
+        "Amount": 1,
+        "PriceOptions": {
+          "Prices": [
+            {
+              "Amounts": [
+                {
+                  "ItemId": "{{TreasureChestCurrencyID}}",
+                  "Amount": 1
+                }
+              ]
+            }
+          ]
+        }
+      }
+    ]
+  },
+  "Publish": true
+}
+```
+
+Then pass the `StoreId` when purchasing:
+
+```json
+{
+  "Entity": {
+    "Type": "title_player_account",
+    "Id": "{{PlayerID}}"
+  },
+  "Item": {
+    "Id": "{{TreasureChestContentsBundleID}}"
+  },
+  "Amount": 1,
+  "PriceAmounts": [
+    {
+      "ItemId": "{{TreasureChestCurrencyID}}",
+      "Amount": 1
+    }
+  ],
+  "StoreId": "{{EventStoreID}}"
+}
+```
+
+## Limitations
+
+This pattern works for containers with **fixed, deterministic contents**. If you need **randomized loot** (where the contents vary each time a container is opened, similar to V1 containers paired with drop tables), see the [Drop tables and randomized loot](drop-tables-and-randomized-loot.md) tutorial. This tutorial uses [Azure Functions](/azure/azure-functions/functions-overview) to:
+
+1. Subtract the container token from the player's inventory.
+2. Run your weighted random selection logic.
+3. Grant the resulting items through the inventory APIs.
+
+## See also
+
+- [Economy v2 Bundles](../catalog/bundles.md)
+- [Economy v2 Stores](../catalog/stores.md)
+- [Virtual currencies](currencies.md)
+- [Economy v2 overview](../overview.md)
+- [PurchaseInventoryItems API reference](/rest/api/playfab/economy/inventory/purchase-inventory-items)
+- [AddInventoryItems API reference](/rest/api/playfab/economy/inventory/add-inventory-items)
diff --git a/playfab-docs/economy-monetization/economy-v2/tutorials/craftingGame/crafting-game-environment.md b/playfab-docs/economy-monetization/economy-v2/tutorials/craftingGame/crafting-game-environment.md
index 91dde9d3c..f9a4fc398 100644
--- a/playfab-docs/economy-monetization/economy-v2/tutorials/craftingGame/crafting-game-environment.md
+++ b/playfab-docs/economy-monetization/economy-v2/tutorials/craftingGame/crafting-game-environment.md
@@ -51,6 +51,6 @@ If you followed the steps so far, the package manager should now be open in VS.
 
 Once you have the appropriate source added to the package manager, you should now be able to search for the PlayFab SDK, called **PlayFabAllSDK**. This search should return some available packages, the one you're looking for shares the exact name mentioned previously, and looks like this:
 
-![Playfab SDK](../../media/crafting-game-images/pf-sdk.png)
+![PlayFab SDK](../../media/crafting-game-images/pf-sdk.png)
 
 Once installed you can start using all of the PlayFab API functions! We can now move on to the next step.
diff --git a/playfab-docs/economy-monetization/economy-v2/tutorials/currencies.md b/playfab-docs/economy-monetization/economy-v2/tutorials/currencies.md
index 1b9450187..52b78ef4c 100644
--- a/playfab-docs/economy-monetization/economy-v2/tutorials/currencies.md
+++ b/playfab-docs/economy-monetization/economy-v2/tutorials/currencies.md
@@ -18,7 +18,7 @@ Get started with PlayFab Economy by using the [PlayFab Services SDK](../../../sd
 
 ## Prerequisites
 
-* A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up)
+* A [PlayFab developer account](https://developer.playfab.com)
 * The PlayFab Beta SDK (You can find more information on the [Postman Quickstart](../../../sdks/postman/postman-quickstart.md#adding-playfab-collections))
 
 ## Get a title entity token
diff --git a/playfab-docs/economy-monetization/economy-v2/tutorials/drop-tables-and-randomized-loot.md b/playfab-docs/economy-monetization/economy-v2/tutorials/drop-tables-and-randomized-loot.md
new file mode 100644
index 000000000..40a460f55
--- /dev/null
+++ b/playfab-docs/economy-monetization/economy-v2/tutorials/drop-tables-and-randomized-loot.md
@@ -0,0 +1,387 @@
+---
+title: Drop tables and randomized loot in Economy v2
+author: ernestoc
+description: How to implement weighted random loot tables in Economy v2 using Azure Functions and ExecuteInventoryOperations
+ms.author: ernestoc
+ms.date: 02/23/2026
+ms.topic: tutorial
+ms.service: azure-playfab
+keywords: playfab, commerce, economy, drop tables, loot, random, gacha, azure functions
+ms.localizationpriority: medium
+---
+
+# Drop tables and randomized loot
+
+[!INCLUDE [notice](../../../includes/_economy-release.md)]
+
+Economy v1 (Legacy) had a built-in [Drop Tables](../../economy/tutorials/drop-tables.md) feature that let you define weighted random item distributions directly in Game Manager. Economy v2 doesn't include drop tables as a native feature, but you can implement the same behavior—and with more flexibility—using [Azure Functions](/azure/azure-functions/functions-overview) combined with the [ExecuteInventoryOperations](/rest/api/playfab/economy/inventory/execute-inventory-operations) API.
+
+This tutorial shows you how to build a complete randomized loot system that:
+
+- Defines loot tables with weighted item pools in [Title Data](../../../live-service-management/game-configuration/titledata/index.md).
+- Uses an Azure Function to roll random items from a loot table.
+- Atomically subtracts a container token and grants the randomly selected items in a single call.
+
+## How it works
+
+1. **Define loot tables in Title Data**: Store your drop table configurations (item IDs, weights, quantities) as JSON in Title Data so you can update them without redeploying code.
+2. **Represent containers as virtual currency**: Use the same [container token pattern](containers-with-fixed-contents.md) as fixed-contents containers: a virtual currency that acts as an unopened loot box.
+3. **Call an Azure Function to open the container**: The function reads the loot table, runs weighted random selection, then calls `ExecuteInventoryOperations` to atomically subtract 1 container token and add the randomly selected items.
+
+## Prerequisites
+
+- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A title created in [Game Manager](https://developer.playfab.com/).
+- Published catalog items that you can grant as loot rewards.
+- A virtual currency representing the container (see [Containers with fixed contents](containers-with-fixed-contents.md#step-1-create-a-virtual-currency-for-the-container) for setup instructions).
+- An [Azure Functions](../../../live-service-management/service-gateway/automation/cloudscript-af/quickstart.md) project connected to your PlayFab title.
+
+## Step 1: Define loot tables in Title Data
+
+Store your loot table definitions in [Title Data](../../../live-service-management/game-configuration/titledata/index.md) so designers can update drop rates without code changes.
+
+### Example loot table structure
+
+Create a Title Data key called `LootTables` with a JSON value:
+
+```json
+{
+  "TreasureChest": {
+    "Rolls": 1,
+    "Items": [
+      { "ItemId": "{{CommonSwordID}}", "Weight": 1000, "MinQuantity": 1, "MaxQuantity": 1 },
+      { "ItemId": "{{UncommonSwordID}}", "Weight": 100, "MinQuantity": 1, "MaxQuantity": 1 },
+      { "ItemId": "{{RareSwordID}}", "Weight": 10, "MinQuantity": 1, "MaxQuantity": 1 },
+      { "ItemId": "{{LegendarySwordID}}", "Weight": 1, "MinQuantity": 1, "MaxQuantity": 1 }
+    ]
+  },
+  "SupplyCrate": {
+    "Rolls": 3,
+    "Items": [
+      { "ItemId": "{{HealthPotionID}}", "Weight": 50, "MinQuantity": 1, "MaxQuantity": 5 },
+      { "ItemId": "{{ManaPotionID}}", "Weight": 50, "MinQuantity": 1, "MaxQuantity": 3 },
+      { "ItemId": "{{GoldCurrencyID}}", "Weight": 80, "MinQuantity": 10, "MaxQuantity": 100 },
+      { "ItemId": "{{RareGemID}}", "Weight": 5, "MinQuantity": 1, "MaxQuantity": 1 }
+    ]
+  }
+}
+```
+
+Each loot table includes the following properties:
+
+| Property | Description |
+|---|---|
+| **Rolls** | How many times to roll on the table when the container is opened. |
+| **Items** | The pool of possible rewards, each with a weight and quantity range. |
+| **Weight** | Relative probability. A higher weight means the item is more likely to drop. |
+| **MinQuantity / MaxQuantity** | Range of how many of that item to grant per roll. |
+
+### Setting Title Data
+
+#### [Game Manager](#tab/title-data-gm)
+
+1. Go to **Content** > **Title Data**.
+2. Create a key called `LootTables`.
+3. Paste your JSON loot table configuration as the value.
+4. Select **Save**.
+
+#### [API](#tab/title-data-api)
+
+Use [SetTitleData](/rest/api/playfab/server/title-wide-data-management/set-title-data):
+
+```json
+{
+  "Key": "LootTables",
+  "Value": "{\"TreasureChest\":{\"Rolls\":1,\"Items\":[...]}}"
+}
+```
+
+---
+
+## Step 2: Create the Azure Function
+
+Create an Azure Function that your game client calls when a player wants to open a container. The function:
+
+1. Verifies the player has at least one container token.
+2. Reads the loot table from Title Data.
+3. Runs weighted random selection.
+4. Calls `ExecuteInventoryOperations` to atomically subtract the token and grant the rewards.
+
+### Data models
+
+```csharp
+public class OpenContainerRequest
+{
+    public string LootTableId { get; set; }  // e.g., "TreasureChest"
+}
+
+public class LootTable
+{
+    public int Rolls { get; set; }
+    public List<LootTableEntry> Items { get; set; }
+}
+
+public class LootTableEntry
+{
+    public string ItemId { get; set; }
+    public int Weight { get; set; }
+    public int MinQuantity { get; set; }
+    public int MaxQuantity { get; set; }
+}
+```
+
+### Weighted random selection
+
+```csharp
+public static LootTableEntry RollOnTable(LootTable table, Random rng)
+{
+    int totalWeight = table.Items.Sum(e => e.Weight);
+    int roll = rng.Next(0, totalWeight);
+
+    int cumulative = 0;
+    foreach (var entry in table.Items)
+    {
+        cumulative += entry.Weight;
+        if (roll < cumulative)
+            return entry;
+    }
+
+    // Fallback (shouldn't reach here)
+    return table.Items.Last();
+}
+```
+
+### Full Azure Function
+
+```csharp
+[FunctionName("OpenLootContainer")]
+public static async Task<dynamic> Run(
+    [HttpTrigger(AuthorizationLevel.Function, "post", Route = null)] HttpRequest req,
+    ILogger log)
+{
+    // 1. Parse the PlayFab context and request
+    var context = JsonConvert.DeserializeObject<FunctionExecutionContext<dynamic>>(
+        await req.ReadAsStringAsync());
+    var args = context.FunctionArgument != null
+        ? JsonConvert.DeserializeObject<OpenContainerRequest>(
+            context.FunctionArgument.ToString())
+        : null;
+
+    if (args == null || string.IsNullOrEmpty(args.LootTableId))
+        return new { Error = "LootTableId is required." };
+
+    var playerEntity = context.CallerEntityProfile.Entity;
+    var settings = new PlayFabApiSettings
+    {
+        TitleId = context.TitleAuthenticationContext.Id,
+        DeveloperSecretKey = Environment.GetEnvironmentVariable("PLAYFAB_DEV_SECRET_KEY")
+    };
+    var authContext = new PlayFabAuthenticationContext
+    {
+        EntityToken = context.TitleAuthenticationContext.EntityToken
+    };
+
+    var serverApi = new PlayFabServerInstanceAPI(settings);
+    var economyApi = new PlayFabEconomyInstanceAPI(settings, authContext);
+
+    // 2. Read the loot table from Title Data
+    var titleDataResult = await serverApi.GetTitleDataAsync(new GetTitleDataRequest
+    {
+        Keys = new List<string> { "LootTables" }
+    });
+
+    if (!titleDataResult.Result.Data.ContainsKey("LootTables"))
+        return new { Error = "LootTables not found in Title Data." };
+
+    var allTables = JsonConvert.DeserializeObject<Dictionary<string, LootTable>>(
+        titleDataResult.Result.Data["LootTables"]);
+
+    if (!allTables.ContainsKey(args.LootTableId))
+        return new { Error = $"Loot table '{args.LootTableId}' not found." };
+
+    var lootTable = allTables[args.LootTableId];
+
+    // 3. Roll for rewards
+    var rng = new Random();
+    var rewards = new Dictionary<string, int>(); // ItemId -> total quantity
+
+    for (int i = 0; i < lootTable.Rolls; i++)
+    {
+        var entry = RollOnTable(lootTable, rng);
+        int quantity = rng.Next(entry.MinQuantity, entry.MaxQuantity + 1);
+
+        if (rewards.ContainsKey(entry.ItemId))
+            rewards[entry.ItemId] += quantity;
+        else
+            rewards[entry.ItemId] = quantity;
+    }
+
+    // 4. Build the atomic operation: subtract 1 container token + add rewards
+    var operations = new List<InventoryOperation>();
+
+    // Subtract the container token
+    // The container currency ID must match the LootTableId mapping
+    // Store this mapping in Title Data or use a naming convention
+    operations.Add(new InventoryOperation
+    {
+        Subtract = new SubtractInventoryItemsOperation
+        {
+            Item = new InventoryItemReference
+            {
+                Id = GetContainerCurrencyId(args.LootTableId) // Your mapping logic
+            },
+            Amount = 1
+        }
+    });
+
+    // Add each reward
+    foreach (var reward in rewards)
+    {
+        operations.Add(new InventoryOperation
+        {
+            Add = new AddInventoryItemsOperation
+            {
+                Item = new InventoryItemReference { Id = reward.Key },
+                Amount = reward.Value
+            }
+        });
+    }
+
+    // 5. Execute atomically
+    var executeResult = await economyApi.ExecuteInventoryOperationsAsync(
+        new ExecuteInventoryOperationsRequest
+        {
+            Entity = new EntityKey
+            {
+                Id = playerEntity.Id,
+                Type = playerEntity.Type
+            },
+            Operations = operations,
+            IdempotencyId = Guid.NewGuid().ToString()
+        });
+
+    if (executeResult.Error != null)
+    {
+        log.LogError($"Failed to execute operations: {executeResult.Error.ErrorMessage}");
+        return new { Error = executeResult.Error.ErrorMessage };
+    }
+
+    log.LogInformation($"Player {playerEntity.Id} opened {args.LootTableId}, received: " +
+        string.Join(", ", rewards.Select(r => $"{r.Value}x {r.Key}")));
+
+    return new { Rewards = rewards, TransactionIds = executeResult.Result.TransactionIds };
+}
+```
+
+> [!NOTE]
+> The `GetContainerCurrencyId` helper function maps a loot table name to its corresponding container currency ID. You can store this mapping in Title Data alongside the loot tables, or use a naming convention.
+
+## Step 3: Grant container tokens to players
+
+Grant container tokens to players through gameplay, store purchases, or rewards. Use the same approach described in [Containers with fixed contents](containers-with-fixed-contents.md#step-3-grant-container-tokens-to-players).
+
+## Step 4: Call the function from your game client
+
+When the player wants to open a container, call the Azure Function by using [ExecuteFunction](/rest/api/playfab/cloudscript/server-side-cloud-script/execute-function):
+
+```json
+{
+    "FunctionName": "OpenLootContainer",
+    "FunctionParameter": {
+        "LootTableId": "TreasureChest"
+    },
+    "GeneratePlayStreamEvent": true
+}
+```
+
+The response contains the randomly selected rewards:
+
+```json
+{
+    "FunctionResult": {
+        "Rewards": {
+            "{{UncommonSwordID}}": 1
+        },
+        "TransactionIds": ["txn-abc-123"]
+    }
+}
+```
+
+## Loot table design patterns
+
+### Rarity tiers
+
+The classic rarity system with exponentially decreasing weights:
+
+```json
+{
+  "Items": [
+    { "ItemId": "CommonItem",     "Weight": 1000, "MinQuantity": 1, "MaxQuantity": 1 },
+    { "ItemId": "UncommonItem",   "Weight": 100,  "MinQuantity": 1, "MaxQuantity": 1 },
+    { "ItemId": "RareItem",       "Weight": 10,   "MinQuantity": 1, "MaxQuantity": 1 },
+    { "ItemId": "LegendaryItem",  "Weight": 1,    "MinQuantity": 1, "MaxQuantity": 1 }
+  ]
+}
+```
+
+Drop probabilities:
+- Common: ~90.0%
+- Uncommon: ~9.0%
+- Rare: ~0.9%
+- Legendary: ~0.09%
+
+### Multi-roll with mixed rewards
+
+A supply crate that gives three random items from a mixed pool:
+
+```json
+{
+  "Rolls": 3,
+  "Items": [
+    { "ItemId": "{{HealthPotionID}}", "Weight": 40, "MinQuantity": 1, "MaxQuantity": 3 },
+    { "ItemId": "{{ManaPotionID}}",   "Weight": 40, "MinQuantity": 1, "MaxQuantity": 3 },
+    { "ItemId": "{{GoldCurrencyID}}", "Weight": 30, "MinQuantity": 10, "MaxQuantity": 50 },
+    { "ItemId": "{{RareGemID}}",      "Weight": 5,  "MinQuantity": 1, "MaxQuantity": 1 }
+  ]
+}
+```
+
+### Guaranteed + random (pity system)
+
+For a "guaranteed rare or better every 10 opens" pattern, track the player's open count in [Display Properties](../inventory/index.md#display-properties) or [Player Data](../../../player-progression/player-data/quickstart.md), and override the random selection in the Azure Function when the threshold is reached.
+
+### Nested drop tables
+
+A loot table can reference another loot table by ID. Your Azure Function resolves the reference recursively:
+
+```json
+{
+  "BossDropTable": {
+    "Rolls": 2,
+    "Items": [
+      { "ItemId": "TABLE:WeaponDropTable", "Weight": 50, "MinQuantity": 1, "MaxQuantity": 1 },
+      { "ItemId": "TABLE:ArmorDropTable",  "Weight": 30, "MinQuantity": 1, "MaxQuantity": 1 },
+      { "ItemId": "{{GoldCurrencyID}}",    "Weight": 80, "MinQuantity": 50, "MaxQuantity": 200 }
+    ]
+  }
+}
+```
+
+The function checks if an `ItemId` starts with `TABLE:` and, if so, rolls on the referenced table instead of granting the item directly.
+
+## Security considerations
+
+- **Always run loot logic server-side** in an Azure Function. Never trust the client to determine which items were rolled. This approach prevents manipulation.
+- **Use `IdempotencyId`** on the `ExecuteInventoryOperations` call to prevent duplicate grants if the function is retried. For more information, see [Idempotent transactions and retries](idempotent-transactions-and-retries.md).
+- **Validate container ownership** by checking the player's inventory before subtracting. The `Subtract` operation in `ExecuteInventoryOperations` fails if the player doesn't have enough tokens, which rolls back the entire batch.
+- **Log all rolls** for auditing. The function's return value and PlayStream events provide a trail of what each player received.
+
+## See also
+
+- [Containers with fixed contents](containers-with-fixed-contents.md)
+- [ExecuteInventoryOperations API reference](/rest/api/playfab/economy/inventory/execute-inventory-operations)
+- [Idempotent transactions and retries](idempotent-transactions-and-retries.md)
+- [Title Data](../../../live-service-management/game-configuration/titledata/index.md)
+- [Azure Functions quickstart](../../../live-service-management/service-gateway/automation/cloudscript-af/quickstart.md)
+- [Drop tables (Legacy Economy)](../../economy/tutorials/drop-tables.md)
+- [Economy v2 overview](../overview.md)
diff --git a/playfab-docs/economy-monetization/economy-v2/tutorials/etags-and-concurrency-control.md b/playfab-docs/economy-monetization/economy-v2/tutorials/etags-and-concurrency-control.md
new file mode 100644
index 000000000..d8caed017
--- /dev/null
+++ b/playfab-docs/economy-monetization/economy-v2/tutorials/etags-and-concurrency-control.md
@@ -0,0 +1,345 @@
+---
+title: ETags and concurrency control in Economy v2
+author: ernestoc
+description: How to use ETags for optimistic concurrency control in inventory operations to prevent conflicting writes
+ms.author: ernestoc
+ms.date: 02/23/2026
+ms.topic: tutorial
+ms.service: azure-playfab
+keywords: playfab, commerce, economy, etags, concurrency, optimistic, inventory
+ms.localizationpriority: medium
+---
+
+# ETags and concurrency control
+
+[!INCLUDE [notice](../../../includes/_economy-release.md)]
+
+When multiple sources (for example, game servers, Azure Functions, or concurrent player actions) modify a player's inventory simultaneously, writes can conflict and overwrite each other. Economy v2 provides **ETags** for optimistic concurrency control—ensuring a write only succeeds if the inventory didn't change since you last read it.
+
+To prevent duplicate transactions from network retries, see [Idempotent transactions and retry patterns](idempotent-transactions-and-retries.md).
+
+## Prerequisites
+
+- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A title created in [Game Manager](https://developer.playfab.com/).
+- At least one published catalog item.
+
+## How it works
+
+Inventory read APIs (such as `GetInventoryItems`) return an `ETag` representing the current version of the inventory. You can pass this value in subsequent write requests by using the `X-PlayFab-Economy-If-Match` HTTP header. If the inventory was modified since you read it, the write is rejected with a **412 Precondition Failed** error.
+
+## Supported HTTP headers
+
+Inventory APIs support ETags through the following HTTP headers:
+
+- **`X-PlayFab-Economy-If-Match`**—Pass a previously received `ETag` value. On **write** APIs, the request succeeds only if the inventory's current ETag matches (returns **412 Precondition Failed** otherwise). On **read** APIs (`GetInventoryItems`), the call returns **412 Precondition Failed** if the inventory version doesn't yet match the provided ETag—indicating the read data might not reflect your latest write. Your client should retry the read until it succeeds.
+- **`X-PlayFab-Economy-If-None-Match`**—On **write** APIs, pass `*` as the value. The request succeeds only if the item doesn't already exist in the inventory. This header is useful for "create-only" scenarios. On **read** APIs (`GetInventoryItems`), pass a previously received `ETag` value. If the inventory didn't change, the API returns **304 Not Modified** with an empty body. If it changed, the API returns the full response with a new `ETag`.
+
+## ETags on GetInventoryItems (read path)
+
+You can use ETags on the read path to avoid redownloading an inventory that didn't change. This behavior is useful for polling scenarios or periodic inventory refreshes where the inventory is unlikely to change between calls.
+
+### How it works
+
+1. Call `GetInventoryItems` normally. The response includes an `ETag` in the response body.
+2. On subsequent calls, pass the stored `ETag` in the `If-None-Match` HTTP header.
+3. If the inventory didn't change, the API returns **304 Not Modified**—no body, no bandwidth cost.
+4. If the inventory changed, the API returns the full inventory with a new `ETag`.
+
+### Example
+
+**First call (no ETag):**
+
+```
+POST /Inventory/GetInventoryItems
+Content-Type: application/json
+X-EntityToken: {{EntityToken}}
+```
+
+```json
+{
+    "Entity": {
+        "Type": "title_player_account",
+        "Id": "{{PlayerID}}"
+    }
+}
+```
+
+Response (200 OK):
+
+```json
+{
+    "Items": [
+        {
+            "Id": "{{HealthPotionID}}",
+            "StackId": "default",
+            "Amount": 10
+        }
+    ],
+    "ETag": "1/MQ=="
+}
+```
+
+**Subsequent call (with ETag, inventory unchanged):**
+
+```
+POST /Inventory/GetInventoryItems
+Content-Type: application/json
+X-EntityToken: {{EntityToken}}
+If-None-Match: 1/MQ==
+```
+
+```json
+{
+    "Entity": {
+        "Type": "title_player_account",
+        "Id": "{{PlayerID}}"
+    }
+}
+```
+
+Response: **304 Not Modified** (empty body). Your client keeps using the cached inventory.
+
+**Subsequent call (with ETag, inventory changed):**
+
+If the inventory changed since the last read, the API returns the full response with a new `ETag`:
+
+Response (200 OK):
+
+```json
+{
+    "Items": [
+        {
+            "Id": "{{HealthPotionID}}",
+            "StackId": "default",
+            "Amount": 7
+        }
+    ],
+    "ETag": "2/Mg=="
+}
+```
+
+Your client updates its cache and stores the new `ETag` for future calls.
+
+### When to use read-path ETags
+
+| Scenario | Benefit |
+|---|---|
+| Periodic inventory refresh (polling every N seconds) | Avoids redownloading unchanged data, reducing bandwidth and API response size. |
+| Game startup check | Quickly verify if the player's inventory changed since the last session without transferring the full inventory. |
+| Multi-screen UI | Different UI panels can check for changes independently without redundant full reads. |
+| Read-after-write consistency | Ensure a `GetInventoryItems` call returns data that includes a write you made. |
+
+### Read-after-write with X-PlayFab-Economy-If-Match
+
+Inventory writes are eventually consistent. A `GetInventoryItems` call immediately after a write might return stale data. To verify that your read reflects a specific write, pass the `ETag` from the write response in the `X-PlayFab-Economy-If-Match` header on the next `GetInventoryItems` call. If the inventory isn't yet at that version, the API returns **412 Precondition Failed**. Your client should retry until the call succeeds with a 200 response.
+
+**Step 1: Perform a write and capture the new ETag**
+
+```
+POST /Inventory/AddInventoryItems
+Content-Type: application/json
+X-EntityToken: {{EntityToken}}
+```
+
+```json
+{
+    "Entity": {
+        "Type": "title_player_account",
+        "Id": "{{PlayerID}}"
+    },
+    "Item": {
+        "Id": "{{HealthPotionID}}"
+    },
+    "Amount": 5
+}
+```
+
+Response (200 OK):
+
+```json
+{
+    "ETag": "3/Mw==",
+    "IdempotencyId": null,
+    "TransactionIds": ["txn-abc-123"]
+}
+```
+
+**Step 2: Read with the write's ETag**
+
+```
+POST /Inventory/GetInventoryItems
+Content-Type: application/json
+X-EntityToken: {{EntityToken}}
+X-PlayFab-Economy-If-Match: 3/Mw==
+```
+
+```json
+{
+    "Entity": {
+        "Type": "title_player_account",
+        "Id": "{{PlayerID}}"
+    }
+}
+```
+
+- If the inventory is at the requested version → **200 OK** with the full inventory including the write.
+- If the inventory isn't yet at the requested version → **412 Precondition Failed**. Retry after a short delay.
+
+**Step 3: Retry loop (pseudocode)**
+
+```
+writeResult = AddInventoryItems(playerId, "HealthPotion", 5)
+writeETag = writeResult.ETag
+
+MAX_RETRIES = 5
+DELAY_MS = 100
+
+for attempt in 1..MAX_RETRIES:
+    result = GetInventoryItems(
+        playerId,
+        headers: { "X-PlayFab-Economy-If-Match": writeETag }
+    )
+
+    if result.status == 200:
+        return result.Items  // Read reflects the write
+    else if result.status == 412:
+        sleep(DELAY_MS)      // Not yet consistent, retry
+        continue
+    else:
+        return error(result)
+
+// Fallback: read without the header to get whatever is available
+return GetInventoryItems(playerId)
+```
+
+This pattern is useful when your game UI needs to immediately display the result of a purchase or reward grant—without it, a fast read call might return the prewrite state.
+
+## Supported APIs
+
+### Write APIs (support `X-PlayFab-Economy-If-Match` and `X-PlayFab-Economy-If-None-Match`)
+
+- [AddInventoryItems](/rest/api/playfab/economy/inventory/add-inventory-items)
+- [SubtractInventoryItems](/rest/api/playfab/economy/inventory/subtract-inventory-items)
+- [UpdateInventoryItems](/rest/api/playfab/economy/inventory/update-inventory-items)
+- [PurchaseInventoryItems](/rest/api/playfab/economy/inventory/purchase-inventory-items)
+- [DeleteInventoryItems](/rest/api/playfab/economy/inventory/delete-inventory-items)
+- [TransferInventoryItems](/rest/api/playfab/economy/inventory/transfer-inventory-items)
+- [ExecuteInventoryOperations](/rest/api/playfab/economy/inventory/execute-inventory-operations)
+
+### Read APIs (support `X-PlayFab-Economy-If-None-Match` and `X-PlayFab-Economy-If-Match`)
+
+- [GetInventoryItems](/rest/api/playfab/economy/inventory/get-inventory-items)
+
+## Example: Read-modify-write with ETag
+
+In this scenario, your game server reads a player's inventory, makes a decision based on current state, then writes an update. You want to guarantee that no concurrent change invalidates your logic.
+
+**Step 1: Read the inventory and capture the ETag**
+
+```
+POST /Inventory/GetInventoryItems
+```
+
+```json
+{
+    "Entity": {
+        "Type": "title_player_account",
+        "Id": "{{PlayerID}}"
+    }
+}
+```
+
+Response:
+
+```json
+{
+    "Items": [
+        {
+            "Id": "{{HealthPotionID}}",
+            "StackId": "default",
+            "Amount": 10
+        }
+    ],
+    "ETag": "1/MQ=="
+}
+```
+
+**Step 2: Write with the ETag**
+
+```
+POST /Inventory/SubtractInventoryItems
+Content-Type: application/json
+X-EntityToken: {{EntityToken}}
+X-PlayFab-Economy-If-Match: 1/MQ==
+```
+
+```json
+{
+    "Entity": {
+        "Type": "title_player_account",
+        "Id": "{{PlayerID}}"
+    },
+    "Item": {
+        "Id": "{{HealthPotionID}}"
+    },
+    "Amount": 3
+}
+```
+
+If another operation modifies the inventory between step 1 and step 2, the ETag doesn't match and the request returns **412 Precondition Failed**.
+
+**Step 3: Handle the conflict**
+
+If you receive a 412, re-read the inventory to get the latest state and ETag, reevaluate your logic, and retry.
+
+## Retry loop pattern (pseudocode)
+
+```
+MAX_RETRIES = 3
+for attempt in 1..MAX_RETRIES:
+    inventory, etag = GetInventoryItems(playerId)
+    
+    // Make your decision based on current inventory state
+    if inventory["HealthPotion"].Amount < 3:
+        return error("Not enough potions")
+    
+    result = SubtractInventoryItems(
+        playerId, "HealthPotion", 3,
+        headers: { "X-PlayFab-Economy-If-Match": etag }
+    )
+    
+    if result.status == 200:
+        return success
+    else if result.status == 412:
+        continue  // Retry with fresh data
+    else:
+        return error(result)
+
+return error("Max retries exceeded")
+```
+
+## Common scenarios
+
+| Scenario | How ETags help |
+|---|---|
+| Server-side read-modify-write | To prevent stale-data writes, read inventory, validate state, and write with ETag. |
+| Concurrent Azure Functions | Multiple functions processing the same player's inventory don't silently overwrite each other. |
+| Admin tools | Game Manager or support tools modifying a player's inventory detect conflicts with in-game operations. |
+
+## ETags vs. IdempotencyId
+
+These two mechanisms serve different purposes and should be used independently. Using them together in the same request is **not recommended**, as their retry semantics conflict—an `IdempotencyId` expects identical retries, while an ETag-based flow requires re-reading state and issuing a new request on each attempt.
+
+| Mechanism | Purpose | When to use |
+|---|---|---|
+| **IdempotencyId** | Prevents duplicate transactions from retries. | Purchases, grants, transfers—any operation where a retry could double-charge or double-grant. See [Idempotent transactions](idempotent-transactions-and-retries.md). |
+| **ETags** | Prevents concurrent writes from conflicting. | Read-modify-write patterns where you need to guarantee consistency. |
+
+## See also
+
+- [Idempotent transactions and retry patterns](idempotent-transactions-and-retries.md)
+- [Inventory ETags reference](../inventory/etags.md)
+- [Catalog ETags reference](../catalog/etags.md)
+- [Inventory overview](../inventory/index.md)
+- [ExecuteInventoryOperations](/rest/api/playfab/economy/inventory/execute-inventory-operations)
diff --git a/playfab-docs/economy-monetization/economy-v2/tutorials/idempotent-transactions-and-retries.md b/playfab-docs/economy-monetization/economy-v2/tutorials/idempotent-transactions-and-retries.md
new file mode 100644
index 000000000..0dafe0232
--- /dev/null
+++ b/playfab-docs/economy-monetization/economy-v2/tutorials/idempotent-transactions-and-retries.md
@@ -0,0 +1,93 @@
+---
+title: Idempotent transactions and retry patterns in Economy v2
+author: ernestoc
+description: How to use IdempotencyId to safely retry inventory operations and prevent duplicate transactions
+ms.author: ernestoc
+ms.date: 02/23/2026
+ms.topic: tutorial
+ms.service: azure-playfab
+keywords: playfab, commerce, economy, idempotent, retry
+ms.localizationpriority: medium
+---
+
+# Idempotent transactions and retry patterns
+
+[!INCLUDE [notice](../../../includes/_economy-release.md)]
+
+Network failures, timeouts, and duplicate requests are inevitable in live games. Economy v2 provides **IdempotencyId** to prevent duplicate transactions. This feature ensures an operation is processed only once even if the same request is sent multiple times.
+
+For optimistic concurrency control (ensuring a write only succeeds if inventory didn't change since you last read it), see [ETags and concurrency control](etags-and-concurrency-control.md).
+
+## Prerequisites
+
+- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A title created in [Game Manager](https://developer.playfab.com/).
+- At least one published catalog item and one virtual currency.
+
+## How it works
+
+When you include an `IdempotencyId` in an inventory write request, PlayFab stores that ID for **14 days**. If another request arrives with the same `IdempotencyId`, PlayFab returns the result of the original request without processing the operation again.
+
+## Supported APIs
+
+`IdempotencyId` is supported on all inventory write APIs:
+
+- [AddInventoryItems](/rest/api/playfab/economy/inventory/add-inventory-items)
+- [SubtractInventoryItems](/rest/api/playfab/economy/inventory/subtract-inventory-items)
+- [PurchaseInventoryItems](/rest/api/playfab/economy/inventory/purchase-inventory-items)
+- [TransferInventoryItems](/rest/api/playfab/economy/inventory/transfer-inventory-items)
+- [DeleteInventoryItems](/rest/api/playfab/economy/inventory/delete-inventory-items)
+- [UpdateInventoryItems](/rest/api/playfab/economy/inventory/update-inventory-items)
+- [ExecuteInventoryOperations](/rest/api/playfab/economy/inventory/execute-inventory-operations)
+
+## Example: Safe purchase with retry
+
+In this scenario, a player buys a Laser Sword. The client generates a unique `IdempotencyId` (for example, a GUID) before sending the request:
+
+```json
+{
+    "Entity": {
+        "Type": "title_player_account",
+        "Id": "{{PlayerID}}"
+    },
+    "Item": {
+        "Id": "{{LaserSwordID}}"
+    },
+    "Amount": 1,
+    "PriceAmounts": [
+        {
+            "ItemId": "{{DiamondCurrencyID}}",
+            "Amount": 5
+        }
+    ],
+    "IdempotencyId": "b7e3f1a2-9c4d-4e8f-a1b2-3c4d5e6f7a8b"
+}
+```
+
+If the client doesn't receive a response (for example, network timeout), it can safely retry the exact same request with the same `IdempotencyId`. PlayFab recognizes the duplicate and returns the original result. The player is charged only once.
+
+## Best practices
+
+- **Generate a unique ID per logical operation**—Use a GUID or UUID. Don't reuse the same ID for different operations.
+- **Generate the ID client-side before the first attempt**—This practice ensures all retries use the same ID.
+- **Don't change the request body between retries**—Using the same `IdempotencyId` with a different request body causes a conflict error.
+- **IDs expire after 14 days**—After that, the same ID can be used again for a new operation.
+
+## Redeem APIs are automatically idempotent
+
+The marketplace redeem APIs (`RedeemAppleAppStoreInventoryItems`, `RedeemGooglePlayInventoryItems`, `RedeemMicrosoftStoreInventoryItems`, `RedeemSteamInventoryItems`) don't require an `IdempotencyId`. They're inherently idempotent. Each marketplace receipt or token can only be redeemed once. A second call with the same receipt returns success but grants nothing.
+
+## Common scenarios
+
+| Scenario | Recommended approach |
+|---|---|
+| Client-side purchase (player buys an item) | Generate a GUID before the first attempt, retry with the same ID on timeout. |
+| Server-side reward grant (quest completion) | Use a deterministic ID derived from the quest and player (for example, `questId-playerId`) to prevent double-grants. |
+| Marketplace redemption | No `IdempotencyId` needed—redeem APIs are automatically idempotent. |
+
+## See also
+
+- [ETags and concurrency control](etags-and-concurrency-control.md)
+- [Inventory overview](../inventory/index.md#idempotency)
+- [Fraud prevention](../fraud-prevention/index.md)
+- [ExecuteInventoryOperations](/rest/api/playfab/economy/inventory/execute-inventory-operations)
diff --git a/playfab-docs/economy-monetization/economy-v2/tutorials/real-money-price-tracking.md b/playfab-docs/economy-monetization/economy-v2/tutorials/real-money-price-tracking.md
new file mode 100644
index 000000000..35352aef0
--- /dev/null
+++ b/playfab-docs/economy-monetization/economy-v2/tutorials/real-money-price-tracking.md
@@ -0,0 +1,218 @@
+---
+title: Real money price tracking in Economy v2
+author: ernestoc
+description: How to set up real money prices on catalog bundles and track revenue from marketplace redemptions
+ms.author: ernestoc
+ms.date: 02/23/2026
+ms.topic: tutorial
+ms.service: azure-playfab
+keywords: playfab, commerce, economy, pricing, real money, revenue, marketplace, analytics
+ms.localizationpriority: medium
+---
+
+# Real money price tracking
+
+[!INCLUDE [notice](../../../includes/_economy-release.md)]
+
+When players purchase items through external marketplaces (Apple App Store, Google Play, Steam, Microsoft Store, Nintendo eShop, PlayStation Store), the transaction involves real-world money. By configuring `RealMoneyPriceDetails` on your catalog bundles, PlayFab records the revenue amount in the [marketplace_transaction_redeemed](../../../api-references/events/Inventory/marketplace-transaction-redeemed.md) event, enabling you to build revenue analytics and reporting.
+
+This tutorial walks you through the end-to-end flow: setting real money prices on a bundle, redeeming a purchase, and viewing the revenue data in events.
+
+## Prerequisites
+
+- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A title created in [Game Manager](https://developer.playfab.com/).
+- A marketplace integration already configured (for example, [Google](../marketplace/marketplace-integrations/google.md), [Apple](../marketplace/marketplace-integrations/apple.md), or [Microsoft Store](../marketplace/marketplace-integrations/microsoft.md)).
+- A published bundle with a [Marketplace Mapping](../catalog/bundles.md) linking it to a marketplace product.
+
+## Step 1: Set real money prices on your bundle
+
+Add `RealMoneyPriceDetails` to the bundle that is linked to your marketplace product. Specify prices in the **smallest currency unit** (for example, cents for USD) per marketplace.
+
+### [API](#tab/set-prices-api)
+
+Use [UpdateDraftItem](/rest/api/playfab/economy/catalog/update-draft-item) to add prices to an existing bundle, and then publish it:
+
+```json
+{
+  "Item": {
+    "Id": "{{StarterPackBundleID}}",
+    "Type": "bundle",
+    "Title": {
+      "NEUTRAL": "Starter Pack"
+    },
+    "ItemReferences": [
+      {
+        "Id": "{{LaserSwordID}}",
+        "Amount": 1
+      },
+      {
+        "Id": "{{GoldCurrencyID}}",
+        "Amount": 500
+      }
+    ],
+    "RealMoneyPriceDetails": {
+      "GooglePlayPrices": {
+        "USD": 499
+      },
+      "AppleAppStorePrices": {
+        "USD": 499
+      },
+      "MicrosoftStorePrices": {
+        "USD": 499
+      }
+    },
+    "AlternateIds": [
+      {
+        "Type": "GooglePlay",
+        "Value": "com.mygame.starterpack"
+      },
+      {
+        "Type": "AppleAppStore",
+        "Value": "com.mygame.starterpack"
+      },
+      {
+        "Type": "MicrosoftStore",
+        "Value": "9NBLGGH42CFD"
+      }
+    ]
+  },
+  "Publish": true
+}
+```
+
+### [Game Manager](#tab/set-prices-gm)
+
+1. Go to **Economy** > **Catalog (V2)** > **Bundles**.
+2. Select the bundle to edit.
+3. In the **Prices** section, set the real money price for each marketplace where the bundle appears.
+4. Make sure the **Marketplace Mapping** section has the correct AlternateIds for each marketplace.
+5. Select **Save and publish**.
+
+---
+
+### Price format reference
+
+Prices use the smallest currency unit. Only **USD** is currently supported.
+
+| Real-world price | Dictionary value |
+|---|---|
+| $0.99 | `{"USD": 99}` |
+| $1.39 | `{"USD": 139}` |
+| $4.99 | `{"USD": 499}` |
+| $9.99 | `{"USD": 999}` |
+| $19.99 | `{"USD": 1999}` |
+
+Set prices only for the marketplaces your title uses. The supported marketplace properties are:
+
+- `AppleAppStorePrices`
+- `GooglePlayPrices`
+- `MicrosoftStorePrices`
+- `NintendoEShopPrices`
+- `PlayStationStorePrices`
+- `SteamPrices`
+
+### Different prices per marketplace
+
+If you price your game differently across stores, set each marketplace property individually:
+
+```json
+"RealMoneyPriceDetails": {
+  "GooglePlayPrices": {
+    "USD": 499
+  },
+  "AppleAppStorePrices": {
+    "USD": 529
+  },
+  "SteamPrices": {
+    "USD": 449
+  }
+}
+```
+
+## Step 2: Player makes a purchase and redeems
+
+After a player purchases the item from the external marketplace, your game calls the appropriate redeem API:
+
+| Marketplace | Redeem API |
+|---|---|
+| Google Play | [RedeemGooglePlayInventoryItems](/rest/api/playfab/economy/inventory/redeem-google-play-inventory-items) |
+| Apple App Store | [RedeemAppleAppStoreInventoryItems](/rest/api/playfab/economy/inventory/redeem-apple-app-store-inventory-items) |
+| Microsoft Store | [RedeemMicrosoftStoreInventoryItems](/rest/api/playfab/economy/inventory/redeem-microsoft-store-inventory-items) |
+| Steam | [RedeemSteamInventoryItems](/rest/api/playfab/economy/inventory/redeem-steam-inventory-items) |
+| Nintendo eShop | [RedeemNintendoEShopInventoryItems](/rest/api/playfab/economy/inventory/redeem-nintendo-e-shop-inventory-items) |
+| PlayStation Store | [RedeemPlayStationStoreInventoryItems](/rest/api/playfab/economy/inventory/redeem-play-station-store-inventory-items) |
+
+When PlayFab processes the redemption, it:
+
+1. Matches the marketplace receipt to the bundle's `AlternateId`.
+2. Grants the bundle's contents to the player's inventory.
+3. Emits a `marketplace_transaction_redeemed` event that includes the `RealMoneyPrices` from the matching bundle.
+
+## Step 3: View revenue in events
+
+After a successful redemption, the `marketplace_transaction_redeemed` event is emitted and includes the real money price data. You can find this event in Game Manager or query it through the data pipeline.
+
+### View in Game Manager
+
+1. Go to **Data** > **Event History** (under the **Analyze** section).
+2. Search for the `marketplace_transaction_redeemed` event name.
+3. Select an event to view its details, including the `RealMoneyPrices` field.
+
+### Example event payload
+
+A Google Play redemption of the Starter Pack ($4.99 USD) produces an event like this:
+
+```json
+{
+  "EventName": "marketplace_transaction_redeemed",
+  "Marketplace": "GooglePlay",
+  "MarketplaceTransctionId": "GPA.1234-5678-9012-34567",
+  "MarketplaceAlternateId": "com.mygame.starterpack",
+  "Amount": 1,
+  "ItemId": "{{StarterPackBundleID}}",
+  "ItemType": "bundle",
+  "RealMoneyPrices": {
+    "USD": 499
+  }
+}
+```
+
+The same bundle redeemed from the Apple App Store (priced at $5.29 USD) produces:
+
+```json
+{
+  "RealMoneyPrices": {
+    "USD": 529
+  }
+}
+```
+
+PlayFab uses the price for the specific marketplace where the redemption occurred.
+
+### Query revenue data
+
+You can use the event data for custom analytics. For example, to calculate total revenue over a period, query for all `marketplace_transaction_redeemed` events and sum the `RealMoneyPrices.USD` values:
+
+```
+Total revenue = Sum of (RealMoneyPrices.USD × Amount) across all events
+```
+
+> [!NOTE]
+> `RealMoneyPrices` reflects what you configured in `RealMoneyPriceDetails`, not the actual amount charged by the marketplace. Keep your prices in sync with your marketplace listings for accurate reporting.
+
+## Best practices
+
+- **Always set `RealMoneyPriceDetails` on marketplace bundles.** Without it, the `RealMoneyPrices` field in redemption events is empty, and you lose revenue visibility.
+- **Use the smallest currency unit.** For USD, provide the price in cents (for example, `499` for $4.99).
+- **Only populate the marketplaces you use.** You don't need to set prices for every marketplace — only the ones your title is published on.
+- **Keep prices in sync with your marketplace listings.** When you update prices in an external marketplace, update the corresponding property in `RealMoneyPriceDetails` to maintain accurate reporting.
+- **Set per-marketplace prices when they differ.** If your game is priced differently across stores, use the per-marketplace properties to reflect the actual price on each platform.
+
+## See also
+
+- [Real money prices reference](../catalog/real-money-prices.md)
+- [Economy v2 Bundles](../catalog/bundles.md)
+- [Fraud prevention quickstart](../fraud-prevention/quickstart.md)
+- [Marketplace integrations](../marketplace/marketplace-integrations/overview.md)
+- [marketplace_transaction_redeemed event](../../../api-references/events/Inventory/marketplace-transaction-redeemed.md)
diff --git a/playfab-docs/economy-monetization/economy-v2/tutorials/toc.yml b/playfab-docs/economy-monetization/economy-v2/tutorials/toc.yml
index fc4db6c1b..0b5dee83c 100644
--- a/playfab-docs/economy-monetization/economy-v2/tutorials/toc.yml
+++ b/playfab-docs/economy-monetization/economy-v2/tutorials/toc.yml
@@ -7,3 +7,13 @@ items:
     href: craftingGame/toc.yml
   - name: Virtual currencies
     href: currencies.md
+  - name: Containers with fixed contents
+    href: containers-with-fixed-contents.md
+  - name: Drop tables and randomized loot
+    href: drop-tables-and-randomized-loot.md
+  - name: Idempotent transactions and retries
+    href: idempotent-transactions-and-retries.md
+  - name: ETags and concurrency control
+    href: etags-and-concurrency-control.md
+  - name: Real money price tracking
+    href: real-money-price-tracking.md
diff --git a/playfab-docs/economy-monetization/economy-v2/ugc/index.yml b/playfab-docs/economy-monetization/economy-v2/ugc/index.yml
index 830c6b87c..531c154c2 100644
--- a/playfab-docs/economy-monetization/economy-v2/ugc/index.yml
+++ b/playfab-docs/economy-monetization/economy-v2/ugc/index.yml
@@ -1,6 +1,6 @@
 ### YamlMime:Landing
 
-title: Azure PlayFab UGC documentation # < 60 chars
+title: PlayFab UGC documentation # < 60 chars
 summary: summary # < 160 chars
 
 metadata:
diff --git a/playfab-docs/economy-monetization/economy/index.yml b/playfab-docs/economy-monetization/economy/index.yml
index 89816056c..4b697db84 100644
--- a/playfab-docs/economy-monetization/economy/index.yml
+++ b/playfab-docs/economy-monetization/economy/index.yml
@@ -1,6 +1,6 @@
 ### YamlMime:Landing
 
-title: Azure PlayFab Economy documentation # < 60 chars
+title: PlayFab Economy documentation # < 60 chars
 summary: PlayFab Economy provides you with the necessary features to more deeply engage with your community and monetize your game. # < 160 chars
 
 metadata:
diff --git a/playfab-docs/economy-monetization/economy/items/quickstart.md b/playfab-docs/economy-monetization/economy/items/quickstart.md
index 0b3ea24b9..f88ef400b 100644
--- a/playfab-docs/economy-monetization/economy/items/quickstart.md
+++ b/playfab-docs/economy-monetization/economy/items/quickstart.md
@@ -105,6 +105,6 @@ To confirm the purchase in Game Manager:
 
 To confirm:
 
-* Open the **PlayStream** tab. You should see a [Player virtual currency item purchased](../../../api-references/events/player-vc-item-purchased.md) event.
+* Open the **PlayStream** tab. You should see a [Player virtual currency item purchased](../../../api-references/events/Player/player-vc-item-purchased.md) event.
 * Open the **Inventory** tab. The inventory should now contain an apple. You can also use features on the **Inventory** tab to revoke the item, or grant the player _more_ apples.
 * Open the **Virtual Currency** tab. The player should only have 95 gold left.
diff --git a/playfab-docs/economy-monetization/economy/stores/quickstart.md b/playfab-docs/economy-monetization/economy/stores/quickstart.md
index 6127c6aad..3c879b810 100644
--- a/playfab-docs/economy-monetization/economy/stores/quickstart.md
+++ b/playfab-docs/economy-monetization/economy/stores/quickstart.md
@@ -108,7 +108,7 @@ Open Game Manager, and confirm that the purchase was made at the store price of
 3. Check the following information for the player:
    * Open the **Inventory** tab. The inventory should now contain a **pear**.
    * Open the **Virtual Currency** tab. Check the virtual currency **Amount** to verify that the player only spent 2 GD.
-   * Open the **PlayStream** tab. You'll see events showing the purchase flow from the store. Events include a [Player virtual currency item purchased](../../../api-references/events/player-vc-item-purchased.md) event, and a [Player virtual currency balance changed](../../../api-references/events/player-virtual-currency-balance-changed.md) event showing that the virtual currency balance changed by two GD.
+   * Open the **PlayStream** tab. You'll see events showing the purchase flow from the store. Events include a [Player virtual currency item purchased](../../../api-references/events/Player/player-vc-item-purchased.md) event, and a [Player virtual currency balance changed](../../../api-references/events/Player/player-virtual-currency-balance-changed.md) event showing that the virtual currency balance changed by two GD.
 
 > [!TIP]
 > You can use the Game Manager to change the order of items in your store and adjust prices at any time.
diff --git a/playfab-docs/economy-monetization/index.yml b/playfab-docs/economy-monetization/index.yml
index 04d08668e..81d801050 100644
--- a/playfab-docs/economy-monetization/index.yml
+++ b/playfab-docs/economy-monetization/index.yml
@@ -1,6 +1,6 @@
 ### YamlMime:Landing
 
-title: Azure PlayFab Economy v2 documentation # < 60 chars
+title: PlayFab Economy v2 documentation # < 60 chars
 summary: PlayFab Economy v2 provides a platform to build and grow marketplaces, progression, and engagement that scale with your players. # < 160 chars
 
 metadata:
diff --git a/playfab-docs/get-started/concepts.md b/playfab-docs/get-started/concepts.md
index b61097719..5263ba022 100644
--- a/playfab-docs/get-started/concepts.md
+++ b/playfab-docs/get-started/concepts.md
@@ -18,7 +18,7 @@ PlayFab offers various fundamental components that serve as the building blocks
 
 PlayFab uses a hierarchical structure to manage resources and configurations across different scopes. 
 
-A PlayFab namespace is the highest level entity that stores all of your global information. In the [PlayFab developer portal](../live-service-management/gamemanager/index.md), the namespace is referred to as the "Studio." 
+A PlayFab namespace is the highest-level entity that stores all global information which spans multiple titles.
 
 A PlayFab title is an entity that represents the data and configurations scoped to a specific game including game settings, player account, player data, and other game-related data.
 
@@ -26,7 +26,7 @@ A namespace might contain many titles, but a title can only belong to one namesp
 
 All titles under the same namespace can share certain resources and configurations. This feature is useful for managing [player identities](../identity/identity-overview.md) and data across multiple titles within the same namespace. 
 
-Titles can also be used to store data and configuration specific to a game environment, a specific version of your game, or game-specific scoped. For example, you might want to have a title for your development environment, your testing environment, your certification environment, and your live environment to keep all your data and configurations cleanly separated. You might also want a separate title for special releases of your game such as play tests, open betas, or demos. 
+Titles can also be used to store data and configuration specific to a game environment or a version of your game.  
 The purpose of a title is to manage game-specific data and configurations. 
 
 Namespaces and titles are two specific types of entities with hierarchical relationships, and there are more [built-in entity types](../live-service-management/game-configuration/entities/available-built-in-entity-types.md) to represent other useful scopes such as players, groups, and servers. 
diff --git a/playfab-docs/get-started/foundation-onboarding.md b/playfab-docs/get-started/foundation-onboarding.md
new file mode 100644
index 000000000..3717b8d3a
--- /dev/null
+++ b/playfab-docs/get-started/foundation-onboarding.md
@@ -0,0 +1,78 @@
+---
+title: Foundation Mode Onboarding
+author: m-kdearnley
+description: Describes how to get started with Foundation Mode.
+ms.author: kdearnley
+ms.date: 02/13/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, pricing, free tier
+ms.localizationpriority: medium
+---
+
+# Onboarding to Foundation Mode
+
+This article shows you how to set up Foundation Mode for your game. You'll request access to the preview, create a title in Foundation Mode, and link your Partner Center account.
+
+## Prerequisites
+
+Before you begin, make sure you have:
+
+- A [PlayFab developer account](../identity/dev-identity/pfab-account.md)
+- A game that you're shipping or planning to ship on Xbox
+- A [Partner Center account](https://developer.microsoft.com/en-GB/games/publish) (or create one during this process)
+
+## Request access to the preview
+
+> [!IMPORTANT]
+> During the preview, Foundation Mode is available for **new titles only**. You can't migrate existing titles at this time. A migration path for existing titles is planned, targeting June 2026.
+
+During the preview period, you need to request access before you can create titles in Foundation Mode.
+
+1. Sign in to [Game Manager](https://developer.playfab.com/).
+1. Navigate to your studio settings and select the Preview Features tab. You must have admin privileges for this tab to be visible. Studio settings can be reached from the home screen, click on the three dots (...) menu on your studio. 
+
+   ![Screenshot of the Game Manager My Studios page showing the three-dots menu on a studio with the Studio settings option highlighted.](media/foundation-onboarding/studio-settings-menu.png)
+
+   ![Screenshot of the Studio Settings page with the Preview Features tab selected, showing Foundation Mode.](media/foundation-onboarding/preview-features-tab.png)
+
+1. Select  **Foundation Mode** and complete the request form.
+1. Wait for approval. You will receive an email when your studio is enabled for Foundation Mode.
+
+## Create a Partner Center account
+
+If you don't already have a Partner Center account, create one to use Foundation Mode.
+
+1. Go to the [Xbox developer onboarding hub](https://developer.microsoft.com/en-GB/games/publish).
+1. Follow the steps to create your developer account.
+1. Complete the account verification process.
+
+
+## Create a title in Foundation Mode
+
+If your studio is onboarded to the Foundation Mode Preview, you can create new titles in Foundation Mode.
+
+1. Sign in to [Game Manager](https://developer.playfab.com/).
+1. Select your studio.
+1. Select **New Title**.
+1. Enter a name and select the correct studio for your title.
+1. Link your new PlayFab Title to an existing Seller ID and Product ID in Partner Center. These fields automatically populate based on the Microsoft Entra ID used to sign in to PlayFab.
+1. Select **Create Title**.
+
+Your new title is now set up in Foundation Mode with access to all included features.
+
+## Support during preview
+
+If you encounter any issues, [file a support ticket](../pricing/support.md#support-ticket-submission).
+
+## Next steps
+
+Now that you are set up in Foundation Mode, start building your game:
+
+- [Set up player authentication](../identity/player-identity/authentication/index.md)
+- [Configure multiplayer services](../multiplayer/index.yml)
+- [Set up leaderboards](../community/leaderboards/index.md)
+
+## See also
+
+- [Foundation Mode overview](mode-overview.md)
diff --git a/playfab-docs/get-started/index.yml b/playfab-docs/get-started/index.yml
index f4bd6f9f4..4315f0c7b 100644
--- a/playfab-docs/get-started/index.yml
+++ b/playfab-docs/get-started/index.yml
@@ -1,11 +1,11 @@
 ### YamlMime:Landing
 
-title: Azure PlayFab fundamentals
-summary: From pre-production to post-launch, learn how PlayFab can help you build and operate your game.  # < 160 chars
+title: PlayFab fundamentals
+summary: From preproduction to post-launch, learn how PlayFab can help you build and operate your game.  # < 160 chars
 
 metadata:
-  title: Azure PlayFab fundamentals and getting started documentation
-  description: From pre-production to post-launch, learn how PlayFab can help you build and operate your game. # Required; article description that is displayed in search results. < 160 chars.
+  title: PlayFab fundamentals and getting started documentation
+  description: From preproduction to post-launch, learn how PlayFab can help you build and operate your game. # Required; article description that is displayed in search results. < 160 chars.
   ms.service: azure-playfab #Required; service per approved list. service slug assigned to your service by ACOM.
   ms.topic: landing-page
   author: m-kdearnley
@@ -22,7 +22,7 @@ landingContent:
     linkLists:
       - linkListType: overview
         links:
-          - text: What is Playfab?
+          - text: What is PlayFab?
             url: what-is-playfab.md
       - linkListType: concept
         links:
diff --git a/playfab-docs/get-started/media/foundation-onboarding/preview-features-tab.png b/playfab-docs/get-started/media/foundation-onboarding/preview-features-tab.png
new file mode 100644
index 000000000..9e7f030e4
Binary files /dev/null and b/playfab-docs/get-started/media/foundation-onboarding/preview-features-tab.png differ
diff --git a/playfab-docs/get-started/media/foundation-onboarding/studio-settings-menu.png b/playfab-docs/get-started/media/foundation-onboarding/studio-settings-menu.png
new file mode 100644
index 000000000..c2bc320bc
Binary files /dev/null and b/playfab-docs/get-started/media/foundation-onboarding/studio-settings-menu.png differ
diff --git a/playfab-docs/get-started/mode-overview.md b/playfab-docs/get-started/mode-overview.md
new file mode 100644
index 000000000..d9d696717
--- /dev/null
+++ b/playfab-docs/get-started/mode-overview.md
@@ -0,0 +1,121 @@
+---
+title: PlayFab Modes
+author: m-kdearnley
+description: Describes Foundation Mode, Development Mode.
+ms.author: kdearnley
+ms.date: 02/13/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, pricing, free tier
+ms.localizationpriority: medium
+---
+
+# Foundation Mode overview
+
+Foundation Mode is a PlayFab service tier that enables eligible Xbox ecosystem developers to use PlayFab game services at no extra cost. It includes core features for player identity, multiplayer, progression, economy, and community - everything you need to build and ship games everywhere.
+
+If you're a developer shipping games on Xbox, or if you're planning to ship on Xbox, Foundation Mode gives you access to essential backend services without the stress of budgeting or billing.
+
+For more information about PlayFab's full capabilities, see [What is PlayFab?]( ../get-started/what-is-playfab.md).
+
+## Eligibility
+
+Developers are eligible for Foundation Mode if they meet the following requirements:
+
+- Register a studio in PlayFab Game Manager.
+
+- Ship or plan to ship their game on Xbox.
+
+- Link their PlayFab account to their Partner Center studio and product.
+
+> [!IMPORTANT]
+> During the preview, Foundation Mode is available for **new PlayFab titles only**. You can create new titles in Foundation Mode, but existing titles can't be migrated at this time. A migration path for existing titles is planned for mid-2026.
+
+## What's included
+
+Foundation Mode includes the following PlayFab features:
+
+**Identity**
+
+| **Feature** | **Description** |
+|---|---|
+| [Player Identity]( ../identity/player-identity/login/index.md) | Authenticate players and link accounts to enable cross-play and cross-progression features |
+| [Server identity](/rest/api/playfab/authentication/authentication/authenticate-game-server-with-custom-id)  | Authenticate game servers for secure backend communication |
+| [Developer identity]( ../identity/dev-identity/pfab-account.md) | Manage developer accounts and studio access |
+
+**Live service management**
+
+| **Feature** | **Description** |
+|---|---|
+| [API access policy]( ../api-references/api-access-policy.md) | Control access to PlayFab APIs for your title |
+| [Title communications]( ../live-service-management/game-configuration/title-communications/overview.md) | Send targeted messages and notifications to players |
+| [Title data]( ../live-service-management/game-configuration/titledata/index.md) | Store and retrieve title-level configuration data |
+| [Add-ons]( ../live-service-management/service-gateway/add-ons/add-ons.md) | Discover and manage add-on integrations for your title |
+| [Functions]( ../live-service-management/service-gateway/automation/cloudscript-af/index.md) | Invoke custom server-side logic using Azure Functions. Function invocations are included; however, Azure compute costs (GB-s) are billed separately through your Azure subscription |
+
+**Game data stream**
+
+| **Feature** | **Description** |
+|---|---|
+| [Telemetry]( ../data-analytics/ingest-data/telemetry-overview.md) | Service-generated telemetry data (custom events excluded) |
+| [PlayStream]( ../data-analytics/ingest-data/playstream-events.md) | System-generated PlayStream events for monitoring player activity |
+| [Reports]( ../data-analytics/learn-data/reports/overview.md) | Built-in reports for player activity and title performance |
+
+**Multiplayer**
+
+
+| **Feature** | **Description** |
+|---|---|
+| [Lobby]( ../multiplayer/lobby/index.md) | Create and manage game lobbies for players |
+| [Matchmaking]( ../multiplayer/matchmaking/index.md) | Match players based on skill, latency, and custom rules |
+| [Party Networking]( ../multiplayer/networking/index.md) | Secure, low-latency networking for multiplayer games |
+| [Real-time messages]( ../multiplayer/lobby/lobby-and-matchmaking-real-time-notifications.md) | Real-time messages from Lobby and Matchmaking services |
+
+**Community**
+
+| **Feature** | **Description** |
+|---|---|
+| [Friends]( ../community/associations/friends/index.md) | Manage player friend lists and relationships |
+| [Groups]( ../community/associations/groups/index.md) | Create and manage player groups and guilds |
+| [Player bans]( ../player-progression/player-data/player-bans.md) | Enforce community standards with player bans |
+| [Leaderboards]( ../community/leaderboards/index.md) | Display player rankings and competition results |
+
+**Progression**
+
+| **Feature** | **Description** |
+|---|---|
+| [Player profile]( ../player-progression/player-data/index.md) | Store and retrieve player profile data |
+| [Statistics]( ../player-progression/statistics/index.md) | Track player statistics and achievements |
+| [Game saves]( ../player-progression/game-saves/overview.md) | Cloud save support for player progress |
+
+**Economy**
+
+| **Feature** | **Description** |
+|---|---|
+| [Catalog]( ../economy-monetization/economy-v2/catalog/catalog-overview.md) | Define and manage your game's virtual items |
+| [Inventory](../economy-monetization/economy-v2/inventory/index.md) | Track player-owned items and currencies |
+
+## Service limits
+
+Foundation Mode includes API rate limits to ensure fair resource allocation, but it doesn't include monthly caps on usage for Foundation Mode titles. Most rate limits apply on a per-API, per-player basis. This limit restricts the number of calls a single player can make to a specific API endpoint in a short time period (for example, 30 calls per 2 minutes). This limit means that any experience that works at a developer's desk should accurately reflect how the game operates at scale, regardless of how many players your live game has.
+
+You can view all limits for your title in Game Manager under **Settings** > **Limits**. 
+
+## Billing and pricing
+
+Foundation Mode simplifies access to core PlayFab services under the Xbox publishing framework. Titles onboarded through Foundation Mode don't need a payment instrument on file, and all included services listed earlier are provided at no extra cost. There are no per-operation charges for reads, writes, storage, or executions within the included feature set.
+
+Foundation Mode applies at the title level. As long as your title only uses the core services included under Foundation Mode, no extra charges apply.
+
+> [!IMPORTANT]
+> The API blocks features that aren't included in Foundation Mode. If your title calls an API for a feature that isn't part of Foundation Mode, the call returns a permissions error. This restriction means there's no risk of unexpected charges—you can't accidentally use a paid feature.
+
+> [!NOTE]
+> **Azure Functions compute costs:** While Foundation Mode includes PlayFab function *invocations*, you pay separately through your Azure subscription for the underlying Azure compute resources (measured in GB-s). For more information, see [Azure Functions pricing](https://azure.microsoft.com/pricing/details/functions/).
+
+> [!NOTE]
+> Foundation Mode doesn't replace existing PlayFab pricing plans. If your studio has other titles that use Pay-as-you-go, Standard, or Premium plans, those titles continue to be billed under their respective pricing models and require a payment instrument on file. Studios can have a mix of Foundation Mode titles and titles on existing plans within the same account.
+
+## See also
+
+- [Foundation Mode Onboarding](foundation-onboarding.md)
\ No newline at end of file
diff --git a/playfab-docs/get-started/toc.yml b/playfab-docs/get-started/toc.yml
index d6f948fbd..10f3a3a58 100644
--- a/playfab-docs/get-started/toc.yml
+++ b/playfab-docs/get-started/toc.yml
@@ -3,3 +3,8 @@ items:
     href: what-is-playfab.md
   - name: Concepts
     href: concepts.md
+  - name: Foundation Mode overview
+    href: mode-overview.md
+  - name: Foundation Mode onboarding
+    href: foundation-onboarding.md
+
diff --git a/playfab-docs/get-started/what-is-playfab.md b/playfab-docs/get-started/what-is-playfab.md
index 8ee3193d7..8ec6b1d4e 100644
--- a/playfab-docs/get-started/what-is-playfab.md
+++ b/playfab-docs/get-started/what-is-playfab.md
@@ -10,11 +10,11 @@ keywords: playfab, analytics, multiplayer, authentication, leaderboards, liveops
 ms.localizationpriority: medium
 ---
 
-# What is Azure PlayFab?
+# What is PlayFab?
 
-Azure PlayFab is a complete backend platform for games, featuring managed game services, real-time analytics, and live operations management capabilities. These features help you engage and retain players, monetize your experiences, collect and analyze game data, and build player experiences across gaming platforms and devices.
+PlayFab is a complete backend platform for games, featuring managed game services, real-time analytics, and live operations management capabilities. These features help you engage and retain players, monetize your experiences, collect and analyze game data, and build player experiences across gaming platforms and devices.
 
-PlayFab's cost-effective and highly-scalable solutions are backed by the world-class infrastructure and a global reach of Azure, allowing all game creators to build and launch their games with confidence. Whether you are a team of one or one thousand, PlayFab has solutions that scale for all sizes of game. PlayFab is the perfect complement to your game: choose which PlayFab features you want to use, extend PlayFab capabilities with cloud-based logic, or connect PlayFab with your own bespoke game services. 
+PlayFab's cost-effective and highly-scalable solutions are backed by the world-class infrastructure and a global reach of Azure, allowing all game creators to build and launch their games with confidence. Whether you're a team of one or one thousand, PlayFab has solutions that scale for all sizes of game. PlayFab is the perfect complement to your game: choose which PlayFab features you want to use, extend PlayFab capabilities with cloud-based logic, or connect PlayFab with your own bespoke game services. 
 
 By managing the essential backend components, PlayFab can help you and your team devote more time to innovating and perfecting the elements of your game that matter most. 
 
@@ -38,11 +38,11 @@ PlayFab provides the following services:
 
 ## Cross-network identity
 
-**Player authentication**: Start with frictionless authentication and let players link accounts to roam across Windows, Xbox, Steam, PlayStation&#8482;Network, Nintendo, Facebook, iOS, Android, and more.
+**Player authentication**: Start with frictionless authentication and let players link accounts to roam across Windows, Xbox, Steam, PlayStation™ Network, Nintendo, Facebook, iOS, Android, and more.
 
 ## Live service management
 
-**Game Manager web portal**: A shared space (with roles and access permissions) where studio members can build, configure and operate your game.
+**Game Manager web portal**: A shared space (with roles and access permissions) where studio members can build, configure, and operate your game.
 
 **Title data**: Manage your game configuration remotely.
 
@@ -90,7 +90,7 @@ PlayFab provides the following services:
 
 ## Community
 
-**Leaderboards**: Facilitate permanent or time-limited competitions amongst friends or strangers.
+**Leaderboards**: Facilitate permanent or time-limited competitions among friends or strangers.
 
 ### Chat
 
diff --git a/playfab-docs/identity/dev-identity/authentication/aad-authentication.md b/playfab-docs/identity/dev-identity/authentication/aad-authentication.md
index b3c48de48..7cacb2c89 100644
--- a/playfab-docs/identity/dev-identity/authentication/aad-authentication.md
+++ b/playfab-docs/identity/dev-identity/authentication/aad-authentication.md
@@ -20,7 +20,7 @@ PlayFab supports two methods for user authentication. The first is the original
 
 You can create a new PlayFab account using an existing or new Microsoft Account. The PlayFab authentication system is no longer available for new accounts.
 
-1. Navigate to [PlayFab's Signup page](https://developer.playfab.com/en-US/sign-up).
+1. Navigate to [PlayFab's Signup page](https://developer.playfab.com).
 2. Select **Sign up with Microsoft** and follow the signup flow.
 
     ![Sign up with Microsoft](media/aad-sign-up.png)
diff --git a/playfab-docs/identity/dev-identity/pfab-account.md b/playfab-docs/identity/dev-identity/pfab-account.md
index cbd2bd07c..6e8d2ee11 100644
--- a/playfab-docs/identity/dev-identity/pfab-account.md
+++ b/playfab-docs/identity/dev-identity/pfab-account.md
@@ -12,11 +12,11 @@ ms.localizationpriority: medium
 
 # Creating a PlayFab account
 
-Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com/en-us/sign-up). If you already have a PlayFab account, you can skip this step.
+Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com). If you already have a PlayFab account, you can skip this step.
 
 ![PlayFab - Create your account](media/playfab-create-new-account.png)
 
-Once you have a PlayFab account, navigate to the PlayFab home page, [https://playfab.com](https://playfab.com), and sign in.
+Once you have a PlayFab account, navigate to the PlayFab home page, [https://developer.playfab.com](https://developer.playfab.com), and sign in.
 
 Since PlayFab doesn't know the name of your game studio or the title of your game, when you create a studio, a placeholder title called **My Game** is created for you. You can edit your title's information in the **Create Title** screen at any time.
 
diff --git a/playfab-docs/identity/index.yml b/playfab-docs/identity/index.yml
index 871e72c9f..91de3995f 100644
--- a/playfab-docs/identity/index.yml
+++ b/playfab-docs/identity/index.yml
@@ -1,6 +1,6 @@
 ### YamlMime:Landing
 
-title: Azure PlayFab Identity documentation
+title: PlayFab Identity documentation
 summary: Overviews, quickstarts, and tutorials that provide guidance on player login and GameManager authentication.  # < 160 chars
 
 metadata:
@@ -52,6 +52,8 @@ landingContent:
             url: player-identity/platform-specific-authentication/google-sign-in-unity.md            
           - text: Setup Sign In with Apple for PlayFab
             url: player-identity/platform-specific-authentication/apple-open-id.md
+          - text: Setting up Xbox Live title association in PlayFab
+            url: player-identity/platform-specific-authentication/xbox-live-add-on.md
           - text: Running an HTTP server for testing
             url: player-identity/platform-specific-authentication/running-an-http-server-for-testing.md
 
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/anonymous-login.md b/playfab-docs/identity/player-identity/platform-specific-authentication/anonymous-login.md
index c37b96687..00c164c80 100644
--- a/playfab-docs/identity/player-identity/platform-specific-authentication/anonymous-login.md
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/anonymous-login.md
@@ -10,7 +10,7 @@ keywords: playfab, authentication, server, anonymous login, customid
 ms.localizationpriority: medium
 ---
 
-# Setting up Playfab Authentication using Anonymous Login
+# Setting up PlayFab Authentication using Anonymous Login
 
 This guide shows you how to implement PlayFab authentication using anonymous login APIs with server-side protection, focusing only on CustomID authentication using HTML5/JavaScript.
 
@@ -26,14 +26,14 @@ To enhance the security of anonymous login, PlayFab implemented a crucial securi
    - Disabling client-side player creation prevents unauthorized account creation directly from unauthorized clients.
    - Only existing players can log in through client-side APIs.
 
-2. **Enabled Server-Side Player Creation**:
+1. **Enabled server-side player creation**:
    - Player account creation is now handled through server-side APIs (`LoginWithCustomID`, `LoginWithAndroidDeviceID`, `LoginWithIOSDeviceID`, `LoginWithNintendoDeviceId`).
    - This ensures all account creation happens in a secure, controlled environment.
 
 ## Prerequisites
 
 - A unique identifier for the player (CustomID)
-- A registered [PlayFab](https://playfab.com/) title
+- A registered [PlayFab](https://developer.playfab.com/) title
 - Your PlayFab title's secret key
 - Familiarity with [sign-in basics and best practices](../login/login-basics-best-practices.md)
 - A server with a valid domain name to serve static HTML files
@@ -41,9 +41,9 @@ To enhance the security of anonymous login, PlayFab implemented a crucial securi
 > [!NOTE]
 > If you need help with setting up a server, see the [Running an HTTP server for testing](running-an-http-server-for-testing.md) tutorial. Throughout this guide, we'll assume your domain is `http://playfab.example`. 
 
-## Authentication Flow
+## Authentication flow
 
-1. **Server-side Account Creation**:
+1. **Server-side account creation**:
    - Use `Server/LoginWithCustomID` with the server API to create new players
    - Requires a title secret key
    - Reference: [Server API - Login With Custom ID](xref:titleid.playfabapi.com.server.authentication.loginwithcustomid)
@@ -52,9 +52,9 @@ To enhance the security of anonymous login, PlayFab implemented a crucial securi
    - Use `Client/LoginWithCustomID` with the client API to log in existing players
    - Reference: [Client API - Login With Custom ID](xref:titleid.playfabapi.com.client.authentication.loginwithcustomid)
 
-## Implementation Steps
+## Implementation steps
 
-### 1. Set Up Your Development Environment
+### 1. Set up your development environment
 
 1. Download the JavaScript SDK from the [JavaScript SDK documentation](https://learn.microsoft.com/gaming/playfab/sdks/javascript/)
 2. Install the required Node.js packages:
@@ -63,7 +63,7 @@ To enhance the security of anonymous login, PlayFab implemented a crucial securi
 npm install playfab-sdk
 ```
 
-### 2. Server-Side Implementation (Node.js)
+### 2. Server-side implementation (Node.js)
 
 > [!IMPORTANT]
 > Keep your title secret key secure and never expose it in client-side code. The secret key should only be used in secure server environments.
@@ -121,7 +121,7 @@ server.listen(port, () => {
 });
 ```
 
-### 3. Client-Side Implementation (HTML)
+### 3. Client-side implementation (HTML)
 
 ```html
 <!DOCTYPE html>
@@ -160,18 +160,18 @@ server.listen(port, () => {
 </html>
 ```
 
-## Configuring Player Creation Settings
+## Configuring player creation settings
 
-### For Existing Titles
+### For existing titles
 
 1. Navigate to the PlayFab developer portal and select your title
-2. Go to **Settings**
-3. Select the **API Features** tab
+1. Go to **Settings**.
+1. Select the **API Features** tab.
 4. Check the box to prevent new player accounts from being created via anonymous login APIs
 
 ![Disabling player creation using Client/LoginWithCustomId](media/tutorials/anonymous-html5/existing_title.png)  
 
-### For New Titles
+### For new titles
 
 > [!WARNING]
 > Enabling automatic player creation for anonymous login APIs can compromise security. Only enable this feature temporarily during development or testing. Always disable it before moving to production.
@@ -179,16 +179,16 @@ server.listen(port, () => {
 New titles have player creation via anonymous APIs disabled by default. To enable for testing, perform the following:
 
 1. Navigate to the PlayFab developer portal and select your title
-2. Go to **Settings**
-3. Select the **API Features** tab
+1. Go to **Settings**.
+1. Select the **API Features** tab.
 4. Uncheck the box to allow new player accounts from being created via anonymous login APIs
 
 ![Enabling player creation using Client/LoginWithCustomId](media/tutorials/anonymous-html5/new_title.png)   
 
 
-## Testing and Response Examples
+## Testing and response examples
 
-### Server Response Example
+### Server response example
 
 When successfully creating a user through the server API, you receive a response similar to:
 
@@ -204,7 +204,7 @@ When successfully creating a user through the server API, you receive a response
 }
 ```
 
-### Client Response Example
+### Client response example
 
 When attempting to create a new account from the client API (which is now disabled), you receive an error:
 
@@ -229,7 +229,7 @@ When successfully logging in an existing user through the client API:
     }
 }
 ```
-## Further Reading
+## Further reading
 
 - [PlayFab Authentication Overview](../authentication/index.md)
 - [Login Basics and Best Practices](../login/login-basics-best-practices.md)
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/apple-open-id.md b/playfab-docs/identity/player-identity/platform-specific-authentication/apple-open-id.md
index b8fc609f7..1a29fabe7 100644
--- a/playfab-docs/identity/player-identity/platform-specific-authentication/apple-open-id.md
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/apple-open-id.md
@@ -37,7 +37,7 @@ Save the identifier where you can access it easily. You'll use in the next set o
 
 To set up the Apple Add-on in PlayFab:
 
-1. Sign in to [Game Manager](https://developer.playfab.com/en-US/login).
+1. Sign in to [Game Manager](https://developer.playfab.com).
 2. Select your title from the My Studios and Titles page.
 3. In the **Add-ons** pane, select the **Apple** platform.
 4. To install the Apple add-on, select **Install Apple**.
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/battlenet-login.md b/playfab-docs/identity/player-identity/platform-specific-authentication/battlenet-login.md
index 5fbb39fdb..21f3d5241 100644
--- a/playfab-docs/identity/player-identity/platform-specific-authentication/battlenet-login.md
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/battlenet-login.md
@@ -19,7 +19,7 @@ This tutorial guides you through the process of setting up PlayFab authenticatio
 You need:
 
 - A [Battle.net account](https://developer.battle.net) for testing.
-- A Registered [PlayFab](https://playfab.com/) title.
+- A Registered [PlayFab](https://developer.playfab.com/) title.
 - A familiarity with [Login basics and Best Practices](../login/login-basics-best-practices.md).
 - A server with a valid domain name to act as a static HTML file. Consult the [Running an HTTP server for testing](running-an-http-server-for-testing.md) tutorial for information on how to set one up.
 
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/facebook-html5.md b/playfab-docs/identity/player-identity/platform-specific-authentication/facebook-html5.md
index 7da4b4a92..be29f3036 100644
--- a/playfab-docs/identity/player-identity/platform-specific-authentication/facebook-html5.md
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/facebook-html5.md
@@ -17,7 +17,7 @@ This tutorial is designed to guide you through PlayFab authentication using Face
 ## Requirements
 
 - A [Facebook account](https://www.facebook.com/) for testing.
-- A registered [PlayFab](https://playfab.com/) title.
+- A registered [PlayFab](https://developer.playfab.com/) title.
 - A familiarity with [sign-in basics and best practices](../login/login-basics-best-practices.md).
 - A minimal server, with a valid domain name to serve static HTML file.
 
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/facebook-unity.md b/playfab-docs/identity/player-identity/platform-specific-authentication/facebook-unity.md
index 541bb4115..85625bd3a 100644
--- a/playfab-docs/identity/player-identity/platform-specific-authentication/facebook-unity.md
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/facebook-unity.md
@@ -19,7 +19,7 @@ This tutorial guides you through an example of PlayFab authentication using Face
 - [Unity 5+](https://unity3d.com/) and a created project.
 - [Facebook account](https://www.facebook.com/) for testing.
 - [Facebook SDK](https://developers.facebook.com/docs/unity/) imported into the project.
-- Registered [PlayFab](https://playfab.com/) title.
+- Registered [PlayFab](https://developer.playfab.com/) title.
 - [PlayFab SDK](https://aka.ms/playfabunitysdkdownload) imported into the project with a configured title reference.
 - Familiarity with [Login basics and Best Practices](../login/login-basics-best-practices.md).
 
@@ -45,10 +45,10 @@ A new **Application** pop-up will open.
 ![Facebook new app ID](media/tutorials/facebook-new-app-id.png)  
 
 1. Navigate to the **Settings** tab.
-2. Then move to the **Basic** sub-tab.
+2. Then move to the **Basic** subtab.
 3. Locate your **Application ID**.
     - Copy it somewhere to a safe place that is easily accessed.
-We will use it later to set up the Facebook SDK.
+We'll use it later to set up the Facebook SDK.
 
 ![Facebook save app ID](media/tutorials/facebook-save-app-id.png)  
 
@@ -58,7 +58,7 @@ We will use it later to set up the Facebook SDK.
 2. Verify that it has an assigned **User Token**.
 
 > [!NOTE]
-> If you *do not* have an assigned user token, request one using the button to the right of your screen. Refer to this page whenever you need a fresh user token. If authorization fails during testing on a PC, token expiration may be the most likely reason. Refresh the page to get a new user token and test again.
+> If you *don't* have an assigned user token, request one using the button to the right of your screen. Refer to this page whenever you need a fresh user token. If authorization fails during testing on a PC, token expiration might be the most likely reason. Refresh the page to get a new user token and test again.
 
 ![Facebook Access Token Tool](media/tutorials/facebook-unity/access-token-tool.png)  
 
@@ -203,17 +203,17 @@ public class PlayfabFacebookAuthExample : MonoBehaviour
 
 ### Running the application on Android
 
-Before launching the application on Android, you are required to perform additional configuration steps:
+Before launching the application on Android, you're required to perform additional configuration steps:
 
 - First, you need to ensure you have the Android platform selected, and the unique **Package ID** set (as indicated in the example below.
 
 > [!NOTE]
-> Please make sure to create your own *unique* **Package ID**.
+> Make sure to create your own *unique* **Package ID**.
 
 ![Set Android package ID](media/tutorials/facebook-unity/set-android-package-id.png)  
 
 > [!TIP]
-> **Optional step**:  Install [Open SSL](https://wiki.openssl.org/index.php/Binaries) and add it to the **PATH** environment variable. If it is missing, Unity will produce a harmless error during the build. This error does *not* stop the build, or effect the execution.
+> **Optional step**:  Install [Open SSL](https://wiki.openssl.org/index.php/Binaries) and add it to the **PATH** environment variable. If it's missing, Unity will produce a harmless error during the build. This error doesn't* stop the build, or effect the execution.
 
 Next, in your **Facebook Application** console:
 
@@ -247,7 +247,7 @@ Before launching the Application on iOS, you have to perform additional configur
 
 - First, ensure that you have the **iOS** platform selected.
 - Then, set a unique **Bundle ID** as indicated in the example provided below.
-- Please make sure to create your own *unique* **Package ID**.
+- Make sure to create your own *unique* **Package ID**.
 
 ![Set iOS bundle ID](media/tutorials/facebook-unity/set-ios-bundle-id.png)
 
@@ -303,4 +303,4 @@ Open your PlayFab title in Game Manager.
 
 ![PlayStream Debugger Facebook authentication event](media/tutorials/facebook-unity/playfab-facebook-auth-event.png)
 
-At this point you have successfully integrated Facebook Authentication for PlayFab.
+At this point, you have successfully integrated Facebook Authentication for PlayFab.
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/google-html5.md b/playfab-docs/identity/player-identity/platform-specific-authentication/google-html5.md
index 873c47c8d..9024daf55 100644
--- a/playfab-docs/identity/player-identity/platform-specific-authentication/google-html5.md
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/google-html5.md
@@ -16,18 +16,18 @@ This tutorial guides you through the process of PlayFab authentication using Goo
 
 ## Requirements
 
-You will need:
+You'll need:
 
 - A [Google account](https://google.com/) for testing.
-- A Registered `[PlayFab](https://playfab.com/)` title.
+- A Registered `[PlayFab](https://developer.playfab.com/)` title.
 - Familiarity with [Login basics and Best Practices](../login/login-basics-best-practices.md).
 - At the minimum, a server with a valid domain name to act as a static HTML file. Consult the [Running an HTTP server for testing](running-an-http-server-for-testing.md) tutorial for information on how to set one up.
 
 ## Server and domain
 
-This guide requires a server with a valid domain to follow. If you do not have a registered domain and remote web server yet, please follow our [Running an HTTP server for testing](running-an-http-server-for-testing.md) tutorial for information on how to set one to run a local web server with a valid domain name.
+This guide requires a server with a valid domain to follow. If you don't have a registered domain and remote web server yet, follow our [Running an HTTP server for testing](running-an-http-server-for-testing.md) tutorial for information on how to set one to run a local web server with a valid domain name.
 
-Throughout this guide, we will assume your domain is `[http://playfab.example](http://playfab.example)`.
+Throughout this guide, we'll assume your domain is `[http://playfab.example](http://playfab.example)`.
 
 ## Registering a Google API project
 
@@ -44,7 +44,7 @@ Start by navigating to the [Google API Console](https://console.developers.googl
 ![Google API Manager new project](media/tutorials/google-html5/create-new-project.png)  
 
 > [!NOTE]
-> It is normal for **API Manager** to take 10-20 seconds to generate the project.
+> It's normal for **API Manager** to take 10-20 seconds to generate the project.
 
 
 
@@ -57,7 +57,7 @@ Once the Project is created:
 ![Google API Manager OAuth consent screen](media/tutorials/google-html5/oauth-consent-screen.png)  
 
 1. Fill out an App Name
-2. Make sure there are emails for **user suport email** and **Developer Contact Email**
+2. Make sure there are emails for **user support email** and **Developer Contact Email**
 3. Then select **SAVE AND CONTINUE**
 
 ![Google API Manager OAuth Consent Screen configuration](media/tutorials/google-html5/create-oauth-consent-screen-1.png)
@@ -82,7 +82,7 @@ On the **OAuth client** screen shown below, the Google API Manager reveals two i
 2. The **client secret**.
 
 > [!NOTE]
-> Be sure to copy and save these values in a safe place that is easily accessible, as they will be used in the authorization process shown later in this tutorial.
+> Be sure to copy and save these values in a safe place that is easily accessible, as they'll be used in the authorization process shown later in this tutorial.
 
 ![Google API Manager OAuth client ID and secret](media/tutorials/google-html5/oauth-client-credentials.png)  
 
@@ -102,14 +102,14 @@ Go to the PlayFab **Game Manager** page for your title.
 > [!NOTE]
 > As of July 2017, **Google API Manager** has a bad habit of *not* hooking the **Allowed JS** origin domain properly. If you receive the following error:  
 > **"idpiframe_initialization_failed", details: "Not a valid origin for the client: somedomain.com..."**  
-> Please remove the credentials and recreate them. *There is no need to delete the entire project - just the credentials.*
+> Remove the credentials and recreate them. *There's no need to delete the entire project - just the credentials.*
 
 ## Testing using an access token
 
 In this example, we show how to test the LoginWithGoogleAccount API using the classic access token approach. Use the HTML code provided below for your testing.
 
 > [!NOTE]
-> Please *make sure* to replace `YOUR_CLIENT_ID` and `YOUR_PLAYFAB_TITLE` with your own values.
+> Make sure* to replace `YOUR_CLIENT_ID` and `YOUR_PLAYFAB_TITLE` with your own values.
 
 > [!Note]
 > the **AccessToken** param is missing in the **LoginWithGoogleAccountRequest** object in the TypeScript typings files. If you are using TypeScript with the Node SDK, you can create a custom type
@@ -183,7 +183,7 @@ In this example, we show how to test the LoginWithGoogleAccount API using the cl
 
 <b>Testing using the (deprecated) Google Sign-in Platform library</b>
 > [!NOTE]
->  The sample below uses the Google Sign-In platform library. **According to the [Google Identity public documentation site](https://developers.google.com/identity/gsi/web/guides/migration), the Google Sign-In JavaScript platform library for Web will be deprecated March 31, 2023**. This sample will not work for newly created Google clients moving forward - please refer to the prior code sample, which uses the newer Google Identity Services library!
+>  The sample below uses the Google Sign-In platform library. **According to the [Google Identity public documentation site](https://developers.google.com/identity/gsi/web/guides/migration), the Google Sign-In JavaScript platform library for Web will be deprecated March 31, 2023**. This sample won't work for newly created Google clients moving forward - refer to the prior code sample, which uses the newer Google Identity Services library!
     
 ```html
 <!DOCTYPE html>
@@ -233,7 +233,7 @@ In this example, we show how to test the LoginWithGoogleAccount API using the cl
 </html>
 ```
 
-Remember to open this page using your web server, and make sure to access this page using the URL you specified, while configuring Google Project, (`[PlayFab](http://playfab.example)` in our case).
+Remember to open this page using your web server, and make sure to access this page using the URL you specified, while configuring Google Project, (`http://playfab.example` in our case).
 
 1. Once the page opens, select **G Signed In**, and follow the general Google authentication flow.
 2. When this is finished, the script will try to authenticate on the PlayFab side and output the result.
@@ -241,4 +241,4 @@ Remember to open this page using your web server, and make sure to access this p
 ![Google Auth Example](media/tutorials/google-html5/google-auth-example.png)  
 
 > [!NOTE]
-> If you *already have* a Google authentication session running, you will not have to select **G Signed In**. Everything will happen automatically.
+> If you *already have* a Google authentication session running, you won't have to select **G Signed In**. Everything will happen automatically.
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/index.md b/playfab-docs/identity/player-identity/platform-specific-authentication/index.md
index 1fdcb122a..d8763996c 100644
--- a/playfab-docs/identity/player-identity/platform-specific-authentication/index.md
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/index.md
@@ -16,7 +16,7 @@ PlayFab supports a wide variety of authentication providers. This allows your ti
 
 What this means is that your players can choose how they prefer to verify their identity and sign in using a method that's most natural to them.
 
-Select authentication providers based on what is most meaningful for the players on your target platforms and distribution methods. For example, if your title is released on Xbox, it will make sense to offer Xbox Live sign-in as a way to authenticate their identity.
+Select authentication providers based on what is most meaningful for the players on your target platforms and distribution methods. For example, if your title is released on Xbox, it makes sense to offer Xbox Live sign-in as a way to authenticate their identity.
 
 ### Apple
 
@@ -41,11 +41,11 @@ Select authentication providers based on what is most meaningful for the players
 - [Setting up PlayFab authentication using Kongregate and HTML5](kongregate-html5.md)
 - [Setting up PlayFab authentication using Kongregate and Unity](kongregate-unity.md)
 
-### PlayStation&#174;
+### PlayStation&#174;5 / PlayStation&#174;4
 
 - [Setting up PlayFab authentication using PlayStation (secure link)](https://dev.azure.com/PlayFabPrivate/PS5/_git/XPlatCppSdk-Private-PS5?path=%2FGuideToLoginWithPSN.md&_a=preview)
 
-If you're unable to access the above secure link, see [Request access](https://aka.ms/pf-partner-request-access).
+If you're unable to access the secure link, see [Request access](https://aka.ms/pf-partner-request-access).
 
 "PlayStation" is a registered trademark or trademark of Sony Interactive Entertainment Inc.
 
@@ -59,6 +59,7 @@ If you're unable to access the above secure link, see [Request access](https://a
 
 ### Windows and Xbox
 
+- [Setting up Xbox Live title association in PlayFab](xbox-live-add-on.md)
 - [Authenticate Xbox Live users using PlayFab's Xbox Live Helper Library (recommended)](../../../multiplayer/networking/party-xbox-live-guide.md#mapping-between-xbox-live-user-ids-and-playfab-entity-ids)
 - [Setting up PlayFab authentication using Universal Windows Platform](uwp.md)
 - [Integrating the Universal Windows Platform with PlayFab](uwp-integration.md)
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/kongregate-html5.md b/playfab-docs/identity/player-identity/platform-specific-authentication/kongregate-html5.md
index b87e45e9b..6b32dc530 100644
--- a/playfab-docs/identity/player-identity/platform-specific-authentication/kongregate-html5.md
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/kongregate-html5.md
@@ -40,11 +40,11 @@ To do this, we need to prepare an `index.html` file with the following content.
 Navigate to the [Kongregate website](https://www.kongregate.com/):
 
 1. Select the **Games** tab.
-2. Then select the **Upload your game** button.
+1. Select the **Upload your game** button.
 
 ![Kongregate Games tab](media/tutorials/kongregate-games-tab.png)  
 
-A page to set up for a new application will open.
+A page to set up for a new application opens.
 
 1. Enter the **Application Name** in the **Title** field.
 2. Then enter a **Game Description** in the field provided.
@@ -53,9 +53,9 @@ A page to set up for a new application will open.
 
 ![Kongregate upload your game](media/tutorials/kongregate-upload-your-game.png)  
 
-You will be moved to the **Application Upload** page.
+You'll be moved to the **Application Upload** page.
 
-As a *very* important first step, make sure to save the **URL** from your **Web Address Bar**. This will save you a lot of time trying to restore access to the application once you close the page.
+As an important first step, make sure to save the **URL** from your **Web Address Bar**. This saves you a lot of time trying to restore access to the application once you close the page.
 
 1. Once this is done, select the prepared **index.html** file as your **Game File**.
 2. Then set up the screen size.
@@ -78,14 +78,14 @@ As a *very* important first step, make sure to save the **URL** from your **Web
 In your PlayFab title Game Manager:
 
 1. Navigate to **Add-ons**.
-2. Then locate and select **Kongregate**, as shown in the example provided below.
+1. Find and select **Kongregate**.
 
 ![PlayFab select Kongregate Add-on](media/tutorials/playfab-select-kongregate-add-on.png)
 
-A new page will open, allowing you to set up **Kongregate** integration.
+A new page opens, allowing you to set up **Kongregate** integration.
 
 1. Enter the **API Key** you acquired in the previous section.
-2. Select the **Install Kongregate** button.
+1. Select **Install Kongregate**.
 
 ![PlayFab set up Kongregate integration](media/tutorials/playfab-set-up-kongregate-integration.png)
 
@@ -145,7 +145,7 @@ Use the example code shown below to populate the `index.html` for your game.
 
     // The function prepares and triggers PlayFab LoginWithKongregate API call
     function loginInUsingPlayFab() {
-      // Setting up playfab title ID
+      // Setting up PlayFab title ID
       PlayFab.settings.titleId = "159F";
 
       // forming request
@@ -184,7 +184,7 @@ Use the example code shown below to populate the `index.html` for your game.
 
 ## Testing
 
-Remember that URL we asked you to save in a safe and accessible place a little earlier?  Use it now to access your **Application Upload** page.
+Remember that URL we asked you to save in a safe and accessible place a little earlier? Use it now to access your **Application Upload** page.
 
 1. Select **index.html** as your **Game File**.
 2. Set up the screen size.
@@ -197,6 +197,6 @@ Once the preview loads, wait for the Application to obtain the **Kongregate User
 
 - When that has happened, select the **PlayFab Login With Kongregate** button.
 - After a brief pause, you should receive an **Authenticated via PlayFab** message.
-- At this point you have successfully logged in using PlayFab and Kongregate!
+- At this point, you have successfully logged in using PlayFab and Kongregate!
 
 ![Testing PlayFab Login with Kongregate](media/tutorials/kongregate-html5/testing-playfab-login-with-kongregate.png)
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/partner-center-configuration-page.png b/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/partner-center-configuration-page.png
new file mode 100644
index 000000000..d6dc11678
Binary files /dev/null and b/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/partner-center-configuration-page.png differ
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/partner-center-product-id.png b/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/partner-center-product-id.png
new file mode 100644
index 000000000..d86f54f60
Binary files /dev/null and b/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/partner-center-product-id.png differ
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/xbox-add-on-installation-validation.png b/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/xbox-add-on-installation-validation.png
new file mode 100644
index 000000000..9bb590e03
Binary files /dev/null and b/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/xbox-add-on-installation-validation.png differ
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/xbox-add-on-installation.png b/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/xbox-add-on-installation.png
new file mode 100644
index 000000000..e4679e959
Binary files /dev/null and b/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/xbox-add-on-installation.png differ
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/xbox-live-add-on-page.png b/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/xbox-live-add-on-page.png
new file mode 100644
index 000000000..602cb5192
Binary files /dev/null and b/playfab-docs/identity/player-identity/platform-specific-authentication/media/tutorials/xbox-add-on/xbox-live-add-on-page.png differ
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/toc.yml b/playfab-docs/identity/player-identity/platform-specific-authentication/toc.yml
index c5dc286b5..7e3d2e2dd 100644
--- a/playfab-docs/identity/player-identity/platform-specific-authentication/toc.yml
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/toc.yml
@@ -33,7 +33,9 @@
     href: uwp.md
   - name: Setup Sign In with Apple for PlayFab
     href: apple-open-id.md
+  - name: Setting up Xbox Live title association in PlayFab
+    href: xbox-live-add-on.md
   - name: Integrating the Universal Windows Platform with PlayFab
     href: uwp-integration.md
-  - name: Setting up Playfab Authentication using Anonymous Login
+  - name: Setting up PlayFab Authentication using Anonymous Login
     href: anonymous-login.md
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/twitch-html5.md b/playfab-docs/identity/player-identity/platform-specific-authentication/twitch-html5.md
index 949f82235..4f48d0203 100644
--- a/playfab-docs/identity/player-identity/platform-specific-authentication/twitch-html5.md
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/twitch-html5.md
@@ -19,7 +19,7 @@ This tutorial has been designed to guide you through the process of PlayFab auth
 Prior to beginning, you should have:
 
 - A [Twitch Account](https://www.twitch.tv/) for testing.
-- A Registered [PlayFab](https://playfab.com/) title.
+- A Registered [PlayFab](https://developer.playfab.com/) title.
 - Familiarity with [Login basics and Best Practices](../login/login-basics-best-practices.md).
 - At the minimum, a server with a valid domain name to serve static HTML files.
 
@@ -28,14 +28,14 @@ Prior to beginning, you should have:
 
 ## Server and domain
 
-This tutorial requires a web server, in order to follow the instructions. If you do not have a registered remote web server yet, please follow our [Running an HTTP server for testing](running-an-http-server-for-testing.md) tutorial, for information on how to run a local web server.
+This tutorial requires a web server, in order to follow the instructions. If you don't have a registered remote web server yet, follow our [Running an HTTP server for testing](running-an-http-server-for-testing.md) tutorial, for information on how to run a local web server.
 
 >[!NOTE]
-> Throughout this tutorial, we will assume your domain is `[http://localhost/](http://localhost/)`.
+> Throughout this tutorial, we'll assume your domain is `[http://localhost/](http://localhost/)`.
 
 ## Registering a Twitch application
 
-Start by navigating to the [Twitch website](https://www.twitch.tv/), and verifying that you are logged in.
+Start by navigating to the [Twitch website](https://www.twitch.tv/), and verifying that you're logged in.
 
 1. Navigate to the **Account** drop-down.
 2. Select **Settings** from the menu provided.
@@ -46,7 +46,7 @@ On the **Settings** page, select **Connections (1)**, as shown below.
 
 ![Twitch settings connections](media/tutorials/twitch-html5/twitch-settings-connections.png)  
 
-At the very bottom of the page, select the **Register your application (1)** button, as shown below.
+At the bottom of the page, select the **Register your application (1)** button, as shown below.
 
 ![Twitch open application registration page](media/tutorials/twitch-html5/twitch-open-application-registration.png)  
 
@@ -65,13 +65,13 @@ A page will open that lets you configure a new app.
 Once the application is registered, the page will be updated and reveal the Client ID for your application.
 
 > [!NOTE]
-> Keep this Client ID in a safe and easily accessible place, as you will be using it later to configure your PlayFab title.
+> Keep this Client ID in a safe and easily accessible place, as you'll be using it later to configure your PlayFab title.
 
 ![Twitch manage application](media/tutorials/twitch-html5/twitch-manage-application.png)  
 
 ## Configuring a PlayFab title
 
-Once you acquire your Twitch Client ID, you may enable and configure a Twitch Add-on for your PlayFab title.
+Once you acquire your Twitch Client ID, you can enable and configure a Twitch Add-on for your PlayFab title.
 
 1. On your **PlayFab Title** screen, go to the menu and select the **Add-ons** item.
 2. Then select the **Twitch** icon link.
@@ -169,7 +169,7 @@ Make sure to replace `TWITCH_CLIENT_ID_GOES_HERE` and `PLAYFAB_TITLE_ID_GOES_HER
 4. Follow any **Twitch** instructions in the pop-up window, and watch the output.
 
 > [!IMPORTANT]
-> If you *already have* a Twitch auth session going when reaching the page, it is possible for callbacks to fire in a different, unexpected order. This case is shown in the screenshot shown below. However, you should make sure that only **Logging in via PlayFab** follows after **Logged in with Twitch**. This indicates that the token was received or restored from the local storage, and we do not have to wait for the Twitch SDK to start signing in to PlayFab.
+> If you *already have* a Twitch auth session going when reaching the page, it's possible for callbacks to fire in a different, unexpected order. This case is shown in the screenshot shown below. However, you should make sure that only **Logging in via PlayFab** follows after **Logged in with Twitch**. This indicates that the token was received or restored from the local storage, and we don't have to wait for the Twitch SDK to start signing in to PlayFab.
 
 ![Twitch Auth Example](media/tutorials/twitch-html5/twitch-auth-example.png)  
 
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/uwp.md b/playfab-docs/identity/player-identity/platform-specific-authentication/uwp.md
index 74474c8b3..70d9c6045 100644
--- a/playfab-docs/identity/player-identity/platform-specific-authentication/uwp.md
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/uwp.md
@@ -15,16 +15,16 @@ ms.localizationpriority: medium
 This tutorial guides you through the procedure for PlayFab authentication using the Universal Windows Platform (UWP).
 
 > [!IMPORTANT]
-> This procedure serves as a very basic introduction on how you can obtain all entities, and commit authentication via Windows Hello and PlayFab. For a more sophisticated example of Windows Hello and PlayFab authentication, consider our `[UWPExample project](https://github.com/PlayFab/UWPExample)`.
+> This procedure serves as a basic introduction on how you can obtain all entities, and commit authentication via Windows Hello and PlayFab. For a more sophisticated example of Windows Hello and PlayFab authentication, consider our `[UWPExample project](https://github.com/PlayFab/UWPExample)`.
 
 ## Requirements
 
 - Follow the [MSDN "Get Set Up" Guide](/windows/apps/windows-app-sdk/set-up-your-development-environment) to prepare Windows and Visual Studio for UWP development.
-- Have a registered [PlayFab](https://playfab.com/) title.
+- Have a registered [PlayFab](https://developer.playfab.com/) title.
 - Be familiar with [Login basics and Best Practices](../login/login-basics-best-practices.md).
 
 > [!NOTE]
-> it is *very* important that you use the Windows 10 operating system, are logged in with a verified Microsoft account, and have configured an access interface such as PIN. If these requirements are *not* met, the app will fail without any useful explanation of why.
+> It is *very* important that you use the Windows 10 operating system, are logged in with a verified Microsoft account, and have configured an access interface such as PIN. If these requirements aren't* met, the app will fail without any useful explanation of why.
 
 ## Preparing a Visual Studio project
 
@@ -58,7 +58,7 @@ In the **NuGet Manager** window:
 
 ![Visual Studio Install PlayFab SDK](media/tutorials/uwp/vs-install-playfab-sdk.png)  
 
-Once finished, your basic project setup is complete. In the next section we will modify 2 classes that should be automatically generated on project creation:
+Once finished, your basic project setup is complete. In the next section we'll modify two classes that should be automatically generated on project creation:
 
 1. **App**
 2. **MainPage**
@@ -67,7 +67,7 @@ Once finished, your basic project setup is complete. In the next section we will
 
 ### App.xaml.cs  
 
-This class will just set up our PlayFab SDK by setting a proper title ID. Do not forget to replace the title ID with your own.
+This class will just set up our PlayFab SDK by setting a proper title ID. Don't forget to replace the title ID with your own.
 
 ```csharp
 using System;
@@ -171,7 +171,7 @@ namespace GettingStartedPlayfabUWP
 
 ### MainPage.xaml
 
-This file contains the layout for our main page. This is a *super trivial* layout with 2 buttons, and a text input combined in a vertically oriented grid.
+This file contains the layout for our main page. This is a *super trivial* layout with two buttons, and a text input combined in a vertically oriented grid.
 
 The buttons are bound to specific methods, and the textbox is accessible via its name `UsernameInput`.
 
@@ -197,7 +197,7 @@ The buttons are bound to specific methods, and the textbox is accessible via its
 
 ### MainPage.xaml.cs
 
-This is the functional class for the main page and it is the heart of the example. Please refer to the code comments, and review the different methods that are designed to walk you through PlayFab+Hello register and login.
+This is the functional class for the main page and it's the heart of the example. Refer to the code comments, and review the different methods that are designed to walk you through PlayFab+Hello register and login.
 
 The easiest approach to start learning the code is to review the methods that are triggered by the corresponding buttons:
 
@@ -458,7 +458,7 @@ To run the application:
 
 Follow the instruction that **Windows** offers for authentication.
 
-1. Once your identity is confirmed, you will see the confirmation message saying that the account was **Registered and signed in**.
+1. Once your identity is confirmed, you'll see the confirmation message saying that the account was **Registered and signed in**.
 2. With a **Session Ticket**.
 
 ![UWP example - register confirmation](media/tutorials/uwp/uwp-example-register-confirmation.png)  
@@ -469,7 +469,7 @@ Follow the instruction that **Windows** offers for authentication.
 
 Follow the instruction that Windows offers for authentication.
 
-1. Once your identity is confirmed, you will see the confirmation message saying that the account is **Signed in**.
+1. Once your identity is confirmed, you'll see the confirmation message saying that the account is **Signed in**.
 2. With a **Session Ticket**.
 
 ![UWP example - sign in confirmation](media/tutorials/uwp/uwp-example-sign-in-confirmation.png)  
diff --git a/playfab-docs/identity/player-identity/platform-specific-authentication/xbox-live-add-on.md b/playfab-docs/identity/player-identity/platform-specific-authentication/xbox-live-add-on.md
new file mode 100644
index 000000000..b5080f952
--- /dev/null
+++ b/playfab-docs/identity/player-identity/platform-specific-authentication/xbox-live-add-on.md
@@ -0,0 +1,64 @@
+---
+title: Xbox Live Title Association
+author: antnguyen
+description: Learn how to set up and configure scoped token validation by linking Partner Center product ID to PlayFab title ID.
+ms.author: antnguyen
+ms.date: 10/09/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, authentication, server, partner center, xbox, xbox live
+ms.localizationpriority: medium
+---
+
+# Setting up Xbox Live title association in PlayFab
+
+Learn how to configure scoped token validation by linking your Partner Center product ID to a PlayFab title ID. 
+
+## Overview
+
+In this tutorial, you'll learn how to configure token validation by specifying which Xbox Live title tokens that PlayFab APIs accept when they use Xbox Live token parameters—giving you more control over integration behavior and enabling scoped token acceptance. These APIs include `Client/loginwithxbox`, `Client/LinkXboxAccount`, `Client/UnlinkXboxAccount`, `Client/ConsumeXboxEntitlement`, `Client/GetFriendLeaderboard`, `Client/GetFriendLeaderboardAroundCurrentUser`, `Client/GetFriendLeaderboardAroundPlayer`, `Client/ConsumeMicrosoftStoreEntitlements`, `Server/loginwithxbox`, `Server/LinkXboxAccount`, `Server/UnlinkXboxAccount`, `Server/GetFriendLeaderboard`, `Server/GetFriendsList`, `Server/GetFriendLeaderboardForEntity`, `Lobby/GetFriendLobbies`, `Server/GetFriendLeaderboardAroundPlayer`, `Inventory/RedeemMicrosoftStoreInventoryItems`, and `Inventory/Redeem`. 
+
+## Requirements
+
+- A registered [PlayFab](https://developer.playfab.com/) title.
+- [Partner Center](https://partner.microsoft.com/) account with an Xbox Live enabled title.
+
+## Partner Center Product ID and Xbox Live Title ID
+
+Start by navigating to the product page for your Partner Center title. 
+
+1. In the Partner Center dashboard, navigate to [Apps and Games](https://partner.microsoft.com/dashboard/apps-and-games/overview).
+2. Locate and select the Xbox Live enabled Partner Center title you wish to associate with PlayFab.
+3. Find and copy the Product ID from the URL of your game.
+
+![Parter Center product ID](media/tutorials/xbox-add-on/partner-center-product-id.png)
+
+4. Next find and copy the Xbox Live Title ID. Navigate to **Xbox services > Xbox Settings** and copy the **Title ID (decimal)** value.
+
+![Parter Center title ID](media/tutorials/xbox-add-on/partner-center-configuration-page.png)
+
+## Install Xbox Live Add-on
+
+Go to [PlayFab Game Manager](https://developer.playfab.com/) page for your title.
+
+1. Navigate to **Add-ons** in the menu.
+2. Locate and select the **Xbox Live** Add-on icon/link.
+
+![Xbox live Add-on](media/tutorials/xbox-add-on/xbox-live-add-on-page.png)
+
+3. Use the **Seller ID** dropdown to select the correct Seller ID from Partner Center. If you don't see the correct Seller ID, select **Sign in with a different partner center account** and sign in with the correct user.
+
+4. Use the **Product ID** dropdown to find the Partner Center Product ID that will be linked to the PlayFab title. Confirm that the Xbox Live Title ID matches the expected Xbox Live Title ID from Partner Center.
+
+![PlayFab Parter Center product ID](media/tutorials/xbox-add-on/xbox-add-on-installation.png)
+
+5. Select **Install Xbox Network** to save the setting and restrict API calls to the selected Xbox Live Title ID. 
+
+![Install Xbox Add-On](media/tutorials/xbox-add-on/xbox-add-on-installation-validation.png)
+
+By following these steps, you can confidently configure scoped Xbox Live token validation within PlayFab, ensuring that only tokens from designated Partner Center title are accepted. This setup streamlines cross-platform authentication, reinforces title-specific security, and empowers developers to deliver seamless, trusted player experiences across Xbox-enabled services.
+
+## Further Reading
+
+- [PlayFab Authentication Overview](../authentication/index.md)
+- [Login Basics and Best Practices](../login/login-basics-best-practices.md)
\ No newline at end of file
diff --git a/playfab-docs/includes/_common-properties-eventsv1.md b/playfab-docs/includes/_common-properties-eventsv1.md
new file mode 100644
index 000000000..8b89af9c4
--- /dev/null
+++ b/playfab-docs/includes/_common-properties-eventsv1.md
@@ -0,0 +1,12 @@
+All V1 PlayStream events are formatted as JSON objects and share the following common properties:
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|EntityId|String|The identifier for the entity (title, player, etc) to which this event applies.|
+|EntityType|String|The type of entity (player, title, etc.) to which this event applies. If PlayFab is meant to take action on this entity, then the EntityType must be either 'player', 'character', or 'title'. It is required that any entity type that PlayFab does not currently parse should be prepended with a namespace (like 'com.mygame.guild') as PlayFab may begin to parse root entities at any time.|
+|EventId|String|PlayFab-assigned unique identifier for this event.|
+|EventName|String|The name of this event.|
+|EventNamespace|String|The assigned namespacing for this event. For example: 'com.myprogram.ads'|
+|Source|String|The name of the source of this PlayStream event; will be PlayFab if the event originated from us.|
+|SourceType|[SourceType](../api-references/events/data-types/sourcetype.md)|The type of source of this event (PlayFab partner, other backend, or from the PlayFab API).|
+|Timestamp|DateTime|The time (in UTC) associated with this event.|
\ No newline at end of file
diff --git a/playfab-docs/includes/_common-properties-eventsv2.md b/playfab-docs/includes/_common-properties-eventsv2.md
new file mode 100644
index 000000000..572862134
--- /dev/null
+++ b/playfab-docs/includes/_common-properties-eventsv2.md
@@ -0,0 +1,12 @@
+All V2 PlayStream events are formatted as JSON objects and most share the following common properties:
+
+|Name|Type|Description|
+| :--------------------|:-------------------|:----------------------|
+|SchemaVersion|String|PlayStream event format version, following a semantic versioning scheme.|
+|FullName|[Object](../api-references/events/data-types/fullnameobject.md)|Combination of the event name and event namespace to fully specify the event type.|
+|Id|String|PlayFab-assigned unique identifier for this event.|
+|Timestamp|DateTime|The time (in UTC) associated with this event.|
+|Entity|[Object](../api-references/events/data-types/entityobject.md)|Details about the entity to which this event applies including Entity Id and Entity type.|
+|Originator|[Object](../api-references/events/data-types/originatorobject.md)|Object describing the source and source type that initiated this event.| 
+|PayloadContentType|String|Specifies the content of the event payload. Default is "JSON".|
+|Origin Info|Object|Optional field containing info about events originating outside of PlayFab.|
\ No newline at end of file
diff --git a/playfab-docs/index.yml b/playfab-docs/index.yml
index ba4411f27..2bd5df06c 100644
--- a/playfab-docs/index.yml
+++ b/playfab-docs/index.yml
@@ -1,12 +1,12 @@
 ### YamlMime:Hub
 
 # root section (required)
-title: Azure PlayFab documentation
-summary: Learn how to build and manage engaging games using Microsoft Azure PlayFab services.
-# brand: playfab
+title: PlayFab documentation
+summary: Learn how to build and manage engaging games using Microsoft PlayFab services.
+# brand: PlayFab
 
 metadata:
-  title: Azure PlayFab documentation
+  title: PlayFab documentation
   description: PlayFab is a complete backend platform for live games. 
   services: service
   ms.service: azure-playfab
diff --git a/playfab-docs/live-service-management/game-configuration/entities/available-built-in-entity-types.md b/playfab-docs/live-service-management/game-configuration/entities/available-built-in-entity-types.md
index da010037f..ea220e468 100644
--- a/playfab-docs/live-service-management/game-configuration/entities/available-built-in-entity-types.md
+++ b/playfab-docs/live-service-management/game-configuration/entities/available-built-in-entity-types.md
@@ -53,7 +53,7 @@ Set the `ID` field to your game's **Title ID**. To retrieve the **Title ID**:
 
 ## master_player_account
 
-The `master_player_account` is a player entity that is shared by all titles within your studio.
+The `master_player_account` is a player entity that is shared by all titles associated to a given namespace.
 
 Set the `ID` field to the `LoginResult.PlayFabId` from the classic API. To retrieve the `LoginResult`, call one of the login methods in [Client Authentication](xref:titleid.playfabapi.com.client.authentication).
 
diff --git a/playfab-docs/live-service-management/game-configuration/entities/entity-files.md b/playfab-docs/live-service-management/game-configuration/entities/entity-files.md
index eaa91d877..6c66979f3 100644
--- a/playfab-docs/live-service-management/game-configuration/entities/entity-files.md
+++ b/playfab-docs/live-service-management/game-configuration/entities/entity-files.md
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 
 # Entity files
 
-Entity files allow you to read and write files attached to an entity, in any format. The example shown below demonstrates a full entity-file loop, from logging in, to loading a file, and uploading a new file.
+Entity files enable you to read and write files attached to an entity, in any format. The following example demonstrates a full entity-file loop, from signing in, to loading a file, and uploading a new file.
 
 ```csharp
 #if !DISABLE_PLAYFABENTITY_API && !DISABLE_PLAYFABCLIENT_API
@@ -82,8 +82,7 @@ public class EntityFileExample : MonoBehaviour
         var request = new PlayFab.ClientModels.LoginWithCustomIDRequest
         {
             CustomId = SystemInfo.deviceUniqueIdentifier,
-            CreateAccount = true,
-            LoginTitlePlayerAccountEntity = true
+            CreateAccount = true
         };
         PlayFabClientAPI.LoginWithCustomID(request, OnLogin, OnSharedFailure);
     }
@@ -142,7 +141,7 @@ public class EntityFileExample : MonoBehaviour
     {
         if (error.Error == PlayFabErrorCode.EntityFileOperationPending)
         {
-            // This is an error you should handle when calling InitiateFileUploads, but your resolution path may vary
+            // This is an error you should handle when calling InitiateFileUploads, but your resolution path might vary
             GlobalFileLock += 1; // Start AbortFileUploads
             var request = new PlayFab.DataModels.AbortFileUploadsRequest
             {
@@ -170,7 +169,7 @@ public class EntityFileExample : MonoBehaviour
         );
         GlobalFileLock -= 1; // Finish InitiateFileUploads
     }
-    void FinalizeUpload()
+    void FinalizeUpload(byte[] body) // body is unused in this example
     {
         GlobalFileLock += 1; // Start FinalizeFileUploads
         var request = new PlayFab.DataModels.FinalizeFileUploadsRequest
@@ -195,22 +194,22 @@ public class EntityFileExample : MonoBehaviour
 - `GlobalFileLock` is a simplistic way to avoid file collisions, specifically designed for this example.
   - Independent file actions won't cause any issues.
   - Each file action requires many steps and multiple API calls, so don't try to access the same file in multiple ways at the same time.
-  - If you're very careful, you won't need any locking mechanism.
-  - If you want to do something complicated, your locking mechanism may be much more complex.
-- `OnGUI` is a very old (but very dense) way to build a Unity GUI entirely within script.
+  - If you're careful, you don't need any locking mechanism.
+  - If you want to do something complicated, your locking mechanism might be much more complex.
+- `OnGUI` is an old, but very dense way, to build a Unity GUI entirely within script.
   - Your GUI will be much better, and game-specific.
 - All PlayFab features *first* require a login or authentication.
-- `LoadAllFiles()` will do exactly as it says. For the current logged-in entity, load all file saved to PlayFab.
-  - This requires multiple steps:
+- `LoadAllFiles()` does exactly as it says. For the current signed-in entity, it loads all files saved to PlayFab.
+  - This function requires multiple steps:
     - Asking PlayFab where the files are located,
     - And then downloading them separately.  
 - `UploadFile(string fileName)` saves the file to the service for the entity.
-  - For simplicity, this example saves one file at a time, but files can be uploaded atomically in sets as well.
-  - The steps for this are:
+  - For simplicity, this example saves one file at a time, but you can upload files atomically in sets as well.
+  - The steps for this operation are:
     - Initialize an atomic upload operation,
     - Upload all files,
     - Finalize an atomic upload operation.
-  - The entity won't consider the file upload complete, nor reflect any changes to other callers until the atomic upload operation has been finalized successfully.
+  - The entity doesn't consider the file upload complete, nor reflect any changes to other callers until the atomic upload operation is finalized successfully.
 
 ## Game Manager and entities
 
@@ -218,6 +217,6 @@ The Game Manager allows you to manipulate objects and files for players. The pla
 
 ![Game Manager - Entities - Player overview](media/tutorials/game-manager-entities-player-overview.png)  
 
-In addition, files and objects now have their own sections in the **Players** tab.
+Also, the **Players** tab now includes separate sections for files and objects.
 
 ![Game Manager - Entities - Player Files and Objects](media/tutorials/game-manager-entities-player-files.png)  
diff --git a/playfab-docs/live-service-management/game-configuration/entities/quickstart.md b/playfab-docs/live-service-management/game-configuration/entities/quickstart.md
index b90c77b17..2b7111e86 100644
--- a/playfab-docs/live-service-management/game-configuration/entities/quickstart.md
+++ b/playfab-docs/live-service-management/game-configuration/entities/quickstart.md
@@ -18,7 +18,7 @@ For information on migrating from the legacy account and data systems to PlayFab
 
 ## Requirements
 
-- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A [PlayFab developer account](https://developer.playfab.com).
 - An installed copy of the Unity Editor. For information on installing the Unity Editor, see [Installing Unity](https://docs.unity3d.com/Manual/GettingStartedInstallingUnity.html) in the Unity documentation. You can also install a version of the Unity using the Visual Studio feature installer.
   > [!NOTE]
   > The PlayFab Unity3D SDK supports Unity Editor version 5.3 and higher.
diff --git a/playfab-docs/live-service-management/game-configuration/experiments/pricing.md b/playfab-docs/live-service-management/game-configuration/experiments/pricing.md
index 3b9b9c0d4..3aca5b44e 100644
--- a/playfab-docs/live-service-management/game-configuration/experiments/pricing.md
+++ b/playfab-docs/live-service-management/game-configuration/experiments/pricing.md
@@ -12,14 +12,14 @@ ms.localizationpriority: medium
 
 # Billing for PlayFab Experiments
 
-This document describes how Experiments are metered and billed. In PlayFab's free Development mode, titles can use Experiments without a fee as long the aggregate number of player accounts is less than 100,000 (attempts to create additional player accounts will fail). For Live titles (on the pay-as-you-go model – Standard, Premium, or Enterprise), Experiments is billed under the [Insights credit system](../../../pricing/Meters/meters.md#insights) with no consumption limits. Insights credits are a virtual currency that allows all Insights services to be billed through a common value. Please note, Experiments service operation has no association with the performance characteristics control of Insights service.
+This document describes how Experiments are metered and billed. In PlayFab's free Development Mode, titles can use Experiments without a fee as long the aggregate number of player accounts is less than 1000 (attempts to create additional player accounts will fail). For Live titles (on the pay-as-you-go model – Standard, Premium, or Enterprise), Experiments is billed under the [Insights credit system](../../../pricing/Meters/meters.md#insights) with no consumption limits. Insights credits are a virtual currency that allows all Insights services to be billed through a common value. The Experiments service operation has no association with the performance characteristics control of Insights service.
 
 The [billing summary page](../../../pricing/billingDetails.md) page provides a daily snapshot of your month-to-date estimate charges with Experiments service’s Insights credit as breakdown. Admin or billing permissions are required to view the Billing Summary page. The comprising factors, which account for the accrued Insights credits based on the consumption of the Experiments service are below. 
 
 What factors contribute to the consumption billing for Experiments service under Insights meter?
 The metering starts only during the run of an experiment and stops when the experiment is completed or stopped. There are three key factors used to bill additional Insights credit utilization for Experiments service. 
 1.	Size of the target audience for treatment assignment. The participating audience of an experiment is either all the active players or is determined based on the selected Segment’s computation in a real-time manner. Also, the process of assignment and instrumentation of a treatment configuration is done by stamping variant IDs onto the player profile. So, the larger the target audience, the more resources are consumed, which results in higher Insights metering. 
-2.	Computation of metrics. This is measured in analysis computation job minutes for each scorecard. This is variable and the determining factors are the set of metrics (that is, each metric’s definition and complexity) and the number of relevant Entity events (with type ‘player’) associated with the involved metric set. So, the larger the associated event set (PlayStream or Telemetry) for a metric set, the higher the Insights metering. Please note, currently, we support a predefined metric set, so there are only two events—player_logged_in and player_realmoney_purchase—for which the scorecard computation happens, and the events’ variable size could add to the computation job minutes. 
+2.	Computation of metrics. This is measured in analysis computation job minutes for each scorecard. This is variable and the determining factors are the set of metrics (that is, each metric’s definition and complexity) and the number of relevant Entity events (with type ‘player’) associated with the involved metric set. So, the larger the associated event set (PlayStream or Telemetry) for a metric set, the higher the Insights metering. A predefined metric set is supported, so there are only two events—player_logged_in and player_realmoney_purchase—for which the scorecard computation happens, and the events’ variable size could add to the computation job minutes. 
 3.	Experiment duration. The longer the duration of an experiment, the higher the consumption of the Experiments service, which results in higher Insights metering. 
 
-Please note, the [Experiment APIs](/rest/api/playfab/experimentation/experimentation) and [PlayStream events](../../../api-references/events/index.md) are accounted for outside of the Insights credit system. The Experiment APIs along with the Overrides assignment usage are accrued under the [profile read/ writes meters](../../../pricing/Meters/meters.md#profile). Also, the Experiments’ PlayStream events are accrued under the [events meters](../../../pricing/Meters/meters.md#events). 
+Note: the [Experiment APIs](/rest/api/playfab/experimentation/experimentation) and [PlayStream events](../../../api-references/events/index.md) are accounted for outside of the Insights credit system. The Experiment APIs along with the Overrides assignment usage are accrued under the [profile read/ writes meters](../../../pricing/Meters/meters.md#profile). Also, the Experiments’ PlayStream events are accrued under the [events meters](../../../pricing/Meters/meters.md#events). 
diff --git a/playfab-docs/live-service-management/game-configuration/segmentation/advanced-segmentation.md b/playfab-docs/live-service-management/game-configuration/segmentation/advanced-segmentation.md
index 293c18aab..1a6f25367 100644
--- a/playfab-docs/live-service-management/game-configuration/segmentation/advanced-segmentation.md
+++ b/playfab-docs/live-service-management/game-configuration/segmentation/advanced-segmentation.md
@@ -28,7 +28,7 @@ You can create segments with Player Custom properties either via API or Game man
 
 ### Via Game Manager 
 
-- Sign in to [Game Manager](https://developer.playfab.com/en-US/login).
+- Sign in to [Game Manager](https://developer.playfab.com).
 - Go to the **Players** page.
 - Go to the **Segments** tab.
 - [Create or update a segment](segmentation-quickstart.md).
diff --git a/playfab-docs/live-service-management/game-configuration/segmentation/player-custom-properties-qs.md b/playfab-docs/live-service-management/game-configuration/segmentation/player-custom-properties-qs.md
index 9d56ad16e..229f3579b 100644
--- a/playfab-docs/live-service-management/game-configuration/segmentation/player-custom-properties-qs.md
+++ b/playfab-docs/live-service-management/game-configuration/segmentation/player-custom-properties-qs.md
@@ -19,7 +19,7 @@ To get started using Player Custom Properties, follow the guides here.
 
 ## Creating, modifying, deleting Player Custom Properties in Game Manager 
 
- Sign in to [Game Manager](https://developer.playfab.com/en-US/login).
+ Sign in to [Game Manager](https://developer.playfab.com).
 - Go to the **Players** page and select a player.
 - Select the **Player Data** tab. 
 - Select the **Custom** subtab.
@@ -60,7 +60,7 @@ To modify a custom property:
 > [!NOTE] 
 > V1 and V2 PlayStream events can be used to set or update custom properties.
 
-- Sign in to [Game Manager](https://developer.playfab.com/en-US/login).
+- Sign in to [Game Manager](https://developer.playfab.com).
 - Go to the **Automation** page and select the **Rules** tab.
 - Select the **New rule** button on the top right of the page.
 - Populate the **Name** and **Event** type text boxes. V1 events are prefixed with **com.playfab.** or **title.** whereas v2 events are prefixed with **playfab.** or **custom.**
diff --git a/playfab-docs/live-service-management/game-configuration/segmentation/segmentation-player-count.md b/playfab-docs/live-service-management/game-configuration/segmentation/segmentation-player-count.md
new file mode 100644
index 000000000..8bba3e2dd
--- /dev/null
+++ b/playfab-docs/live-service-management/game-configuration/segmentation/segmentation-player-count.md
@@ -0,0 +1,26 @@
+---
+title: Tutorial to Count Players of a Segment
+author: yegarci
+description: This is a tutorial document for customers to get the count of players in a segment
+ms.author: yegarci
+ms.date: 03/30/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, segments, segmentation, player count
+ms.localizationpriority: medium
+---
+
+# Count Players of a Segment (Preview)
+
+> [!NOTE]
+> The GetSegmentPlayerCount API is in preview. We anticipate ongoing changes to it as we continue gathering feedback and optimizing for customer use.
+
+This tutorial walks you through getting the player count of a given segment using the new GetSegmentPlayerCount APIs (currently in preview). These APIs, together with the ExportPlayersInSegment API and GetSegmentExport API, fully replace the functionality of the retired GetPlayersInSegment APIs. For getting started with the export APIs, follow this tutorial: [Tutorial to export players in a Segment - PlayFab | Microsoft Learn.](segmentation-export-players-in-a-segment.md)
+
+Send a POST request with the Segment ID as a payload to the GetSegmentPlayerCount API. The 'ProfilesInSegment' in the response is the player count for the segment.
+
+![Get Segment Player Count](../../../data-analytics/acting-data/media/get-segment-player-count.png)
+
+
+> [!Note]
+> The API requires the ‘X-SecretKey’ header with the value being a Title Secret key. The ‘Content-Type’ header should be set to ‘application/json’ 
\ No newline at end of file
diff --git a/playfab-docs/live-service-management/game-configuration/segmentation/toc.yml b/playfab-docs/live-service-management/game-configuration/segmentation/toc.yml
index 52c1cadaf..75f45f34d 100644
--- a/playfab-docs/live-service-management/game-configuration/segmentation/toc.yml
+++ b/playfab-docs/live-service-management/game-configuration/segmentation/toc.yml
@@ -21,4 +21,6 @@ items:
     - name: Export Players of a Segment
       href: segmentation-export-players-in-a-segment.md
     - name: Advanced Segmentation with Player Custom Properties (Preview)
-      href: advanced-segmentation.md
\ No newline at end of file
+      href: advanced-segmentation.md
+    - name: Count Players of a Segment (Preview)
+      href: segmentation-player-count.md
\ No newline at end of file
diff --git a/playfab-docs/live-service-management/game-configuration/title-communications/emails/using-a-rule-to-verify-a-contact-email-address.md b/playfab-docs/live-service-management/game-configuration/title-communications/emails/using-a-rule-to-verify-a-contact-email-address.md
index a1e8d7706..ea1692fc2 100644
--- a/playfab-docs/live-service-management/game-configuration/title-communications/emails/using-a-rule-to-verify-a-contact-email-address.md
+++ b/playfab-docs/live-service-management/game-configuration/title-communications/emails/using-a-rule-to-verify-a-contact-email-address.md
@@ -141,6 +141,8 @@ void FailureCallback(PlayFabError error)
 }
 ```
 
+After 'AddOrUpdateContactEmail' succeeds, the com.playfab.player_updated_contact_email event triggers the rule and PlayFab sends the verification email automatically. There is no separate step to send the email.
+
 ## Step 4 - Confirm that the contact email was added to the player's profile
 
 Next, confirm that the contact email was added to the player's profile. Log into the **Game Manager**, and visit the **Players Profile** page.
@@ -219,5 +221,4 @@ When the player selects that URL, three things happen:
 
 So that's it for this tutorial. You've seen how to set up your SMTP server, create an email template, and create a rule that sends an email to a player verifying their email address.
 
-If you have any questions or feedback on this tutorial, please let us know in our [community forums](https://community.playfab.com/).
- 
+If you have any questions or feedback on this tutorial, please let us know in our [community Discord](https://developer.microsoft.com/en-us/games/articles/2024/05/playfab-dev-forums-move-to-discord/).
\ No newline at end of file
diff --git a/playfab-docs/live-service-management/gamemanager/quickstart.md b/playfab-docs/live-service-management/gamemanager/quickstart.md
index 0084721ca..4a7b05bc3 100644
--- a/playfab-docs/live-service-management/gamemanager/quickstart.md
+++ b/playfab-docs/live-service-management/gamemanager/quickstart.md
@@ -19,7 +19,7 @@ Get started with PlayFab by using Game Manager to create your PlayFab account, c
 
 ## Create a PlayFab account
 
-On the [PlayFab sign up](https://developer.playfab.com/en-us/sign-up) screen, you can create a PlayFab specific account or use your Microsoft account to sign in.
+On the [PlayFab sign up](https://developer.playfab.com) screen, you can create a PlayFab specific account or use your Microsoft account to sign in.
 
 When you've signed in, PlayFab prompts you enter your contact information and studio information. If you haven't finalized the game studio name, you can change it later.
 
diff --git a/playfab-docs/live-service-management/gamemanager/reference.md b/playfab-docs/live-service-management/gamemanager/reference.md
index 60e1ecf70..afe986e05 100644
--- a/playfab-docs/live-service-management/gamemanager/reference.md
+++ b/playfab-docs/live-service-management/gamemanager/reference.md
@@ -12,9 +12,9 @@ ms.localizationpriority: medium
 
 # Game Manager reference
 
-This reference familiarizes you with the high-level aspects of the Game Manager. For more detailed information, you may select your specific topic of interest in the PlayFab documentation that follows.
+This reference familiarizes you with the high-level aspects of the Game Manager. For more detailed information, select your specific article of interest in the PlayFab documentation that follows.
 
-To get the most value from this topic, you should have created your PlayFab account, logged in, and viewed the Game Manager for your title, even if it's an empty title for now.
+To get the most value from this article, you should create your PlayFab account, logged in, and viewed the Game Manager for your title, even if it's an empty title for now.
 
 The sections provided below offer greater insight on each Game Manager area. Each time you perform an API call or task, view the results in the Game Manager in the appropriate area for that task.
 
@@ -29,24 +29,24 @@ Game Manager is split into four major sections:
 - Engage – Facilitate connections with players.
 - Analyze – Monitor and act on player behaviors.
 
-## Title Overview
+## Title overview
 
 An overview of the recent and less-recent performance of your title.
 
-**Overview** - shows your game's basic statistics and what you may have assigned as Key Performance Indicators (KPIs). In the upper-right, you will find time period toggle buttons, and there are also filters for the tables.
+**Overview** - shows your game's basic statistics and what you assigned as Key Performance Indicators (KPIs). In the upper-right, you'll find time period toggle buttons. There are also filters for the tables.
 
-- **4h**: This will load data generated within the last 4 hours.
-- **24h**: This will load data generated within the last 24 hours.
-- **3d**: This will load data generated within the last 3 days.
-- **7d**: This will load data generated within the last 7 days.
-- **mtd**: This will load data generated within the current month.
+- **4h**: This loads data generated within the last 4 hours.
+- **24h**: This loads data generated within the last 24 hours.
+- **3d**: This loads data generated within the last three days.
+- **7d**: This loads data generated within the last seven days.
+- **mtd**: This loads data generated within the current month.
 
 > [!NOTE]
 > In Game Manager, all times are displayed in local time.
 
 ![Game Manager - Dashboards](media/tutorials/game-manager-dashboard.png)
 
-The tables in the Overview tab allow you to monitor PlayStream events in real time. They include the following:
+The tables in the Overview tab allow you to monitor PlayStream events in real time. They include the following metrics:
 
 - **Unique Users**: The average number of unique players logging in per day.
 - **API Calls**: Indicates how many API calls were executed within the given time period.
@@ -70,7 +70,7 @@ In this section of the Game Manager, a sorted list is presented, and organized b
 
 ![Game Manager - Players Tab](media/tutorials/game-manager-players-tab.png)
 
-**Overview** - this detailed screen provides a wealth of insight into the players' activities. The sub-menu contains many links to other player-centric information, as shown below.
+**Overview** - this detailed screen provides a wealth of insight into the players' activities. The submenu contains many links to other player-centric information, as shown below.
 
 ![Game Manager - Player - Overview](media/tutorials/game-manager-player-overview.png)
 
@@ -92,9 +92,9 @@ Some specific tools your team can use to remedy defrauded players and identify p
 
 Multiplayer allows you to configure server hosting and matchmaking.  
 
-**Servers** - Whether you are looking to hosting multi-player matches or just need a secure environment that can reduce many common forms of hacking and abuse, the PlayFab Thunderhead servers work with many architectures and game types. These servers provide an excellent alternative when compared with the overhead of dedicated game servers.
+**Servers** - Whether you're looking to hosting multi-player matches or just need a secure environment that can reduce many common forms of hacking and abuse, the PlayFab Thunderhead servers work with many architectures and game types. These servers provide an excellent alternative when compared with the overhead of dedicated game servers.
 
-**Matchmaking** - Set up your matchmaking queues by configuring match sizes, servers and statistics.
+**Matchmaking** - Set up your matchmaking queues by configuring match sizes, servers, and statistics.
 
 ![Matchmaking](media/tutorials/game-manager-multiplayer-matchmaking.png)
 
@@ -129,7 +129,7 @@ To configure marketplace integrations for your title: Explore the **Add-ons** se
 
   ![Game Manager - Add-ons - Partner Add-ons](media/tutorials/game-manager-add-ons-partner-add-ons.png)
 
-Setup instructions for each add-on may vary. Additional billing information may also be required.
+Setup instructions for each add-on vary. More billing information might also be required.
 
 [Back to About the Game Manager](#about-game-manager)
 
@@ -149,7 +149,7 @@ As an example, the following image shows the primary catalogs for **Unicorn Batt
 
 **Items** - An item within the catalog. Items can be of several different types.
 
-**Stores**- A subset of catalog items that can be set to prices that are different than those specified by the catalog.
+**Stores**- A subset of catalog items that can be set to prices that are different than prices specified by the catalog.
 
 ![Game Manager - Economy - Catalogs - Edit Container](media/tutorials/game-manager-economy-catalogs-edit-container.png)
 
@@ -171,7 +171,7 @@ Additional Information:
 
 ### User Generated Content
 
-The User Generated Content tab displays all published content for your title. When enabled, all users can create, discover, and consume content.
+The **User Generated Content** (UGC) tab displays all published content for your title. When enabled, all users can create, discover, and consume content.
 
 ![UGC Landing Page](media/tutorials/game-manager-ugc.png)
 
@@ -196,15 +196,15 @@ Additional Information:
 
 ### Progression
 
-The Progression tab displays all the active stats and leaderboards for your title. [Playfab Statistics](../../player-progression/statistics/index.md) and [PlayFab Leaderboards](../../community/leaderboards/quickstart-leaderboards.md) can be defined and configured here. You can even link a leaderboard to a stat to have one call drive updates for both. 
+The Progression tab displays all the active stats and leaderboards for your title. [PlayFab Statistics](../../player-progression/statistics/index.md) and [PlayFab Leaderboards](../../community/leaderboards/quickstart-leaderboards.md) can be defined and configured here. You can even link a leaderboard to a stat to have one call drive updates for both. 
 
 - [Back to About the Game Manager](#about-game-manager)
 
 ### Content
 
-The Content section offers tools for engaging with your players.  The content can include news, remote configuration, and files.  
+The Content section offers tools for engaging with your players. The content can include news, remote configuration, and files.  
 
-**Title Data** - Here you can configure and store key properties which you can change after your game launches. Title data is accessible from all API sets by all users. Because of this, title data is an ideal place to store your custom title settings. Internal data is hidden from game clients and only available on your game servers.
+**Title Data** - Here you can configure and store key properties that you can change after your game launches. Title data is accessible from all API sets by all users. Because of this, title data is an ideal place to store your custom title settings. Internal data is hidden from game clients and only available on your game servers.
 
 ### Add or edit title data keys
 
@@ -222,11 +222,11 @@ The Content section offers tools for engaging with your players.  The content ca
 
 **Title News** - Create title news for your game title. As needed, add additional languages.
 
-**File Management** - Create, organize and upload files for your game client via the Content Delivery Network (CDN).
+**File Management** - Create, organize, and upload files for your game client via the Content Delivery Network (CDN).
 > [!NOTE]
 > There are varying time delays, depending on the type of file handling that is required. For detailed information, view the online Help for the File Management tab.
 
-**Email Templates** - Create, configure and manage email templates for game clients.
+**Email Templates** - Create, configure, and manage email templates for game clients.
 
 The following example shows the **Email Templates** tab for *Great Game*.
 
@@ -242,11 +242,11 @@ Analyze allows you to monitor and act on player behaviors.
 
 ### Dashboards
 
-Dashboards allow you to see Trends, run Reports and perform Diagnostics.
+Dashboards allow you to see Trends, run Reports, and perform Diagnostics.
 
 ### Data
 
-In the **Data** area you can do a number of things to track and analyze data from your players' activities. There are a number of graphing and reports capabilities that provide the ability to consolidate and visualize the data.
+In the **Data** area, you can do many things to track and analyze data from your players' activities. There are a number of graphing and reports capabilities that provide the ability to consolidate and visualize the data.
 
 **Trends** - Configure and view trends for a number of statistics for time periods ranging from 7 days to 26 months. The Trends graph shows classic retention - only new players that have returned - for the chosen time period. The 30-day retention report includes both new and returning players.
 **Event History** - Search and display a number of different Event History types, depending on the query you create. Use event name, date range, or event values.
@@ -254,7 +254,7 @@ In the **Data** area you can do a number of things to track and analyze data fro
 
 ![Game Manager - Reports](media/tutorials/game-manager-analytics-reports.png)
 
-For additional or custom reports, please open a feature request in our [community forums](https://community.playfab.com/spaces/24/index.html).
+For additional or custom reports, open a feature request in our [community forums](https://community.playfab.com/spaces/24/index.html).
 
 **Webhooks** - Webhooks allow you to have some or all of your PlayStream events forwarded to any web URL you want. The event data is sent via POST in the request body as JSON.
 
@@ -281,7 +281,7 @@ On the Audit History page, select any entry in the log to view the complete deta
 
 Access the title settings from the Settings menu.
 
-**General** - Provides basic information that you will use to configure your title such as player display names and the default language for your title.
+**General** - Provides basic information that you'll use to configure your title such as player display names and the default language for your title.
 
   ![Game Manager - Settings - General Tab](media/tutorials/game-manager-settings-general.png)
 
@@ -294,12 +294,12 @@ Choose your preferred options, and select the **Save** button.
 **Secret Keys** - Allows you to create and manage your PlayFab secret keys, the unique identifier for your game when making Admin and server API calls.
 
 > [!IMPORTANT]
-> This key should only be shared with trusted members of your development team, since it enables API calls that can affect game data and player accounts. Never share your PlayFab API secret key with anyone; doing so may jeopardize your title's security.
+> This key should only be shared with trusted members of your development team, since it enables API calls that can affect game data and player accounts. Never share your PlayFab API secret key with anyone; doing so might jeopardize your title's security.
 
 **Email Preferences** - Allows you to configure e-mail settings such as Subscription and Reply-To addresses.
 **Push Notifications** - Configure notifications to be sent to android or iOS devices.
 **Limits** - Set limits on certain PlayFab features, economic or otherwise in your game.
-**Client Profile Options** - Allows you to configure what a Client can or cannot access and configure on their own for the title.
+**Client Profile Options** - Allows you to configure what a Client can or can't access and configure on their own for the title.
 
 ## Other basic actions
 
@@ -316,7 +316,7 @@ Choose your preferred options, and select the **Save** button.
 
 ### View PlayFab news
 
-New notifications will be indicated in the little bell icon in the upper-right corner of your window.
+New notifications are indicated in the little bell icon in the upper-right corner of your window.
 
 1. Select icon to display **News**.
 2. View the news from the PlayFab team, ordered by the most recent, first. The news feeds include information on new features, API updates, and service outages.
@@ -325,18 +325,18 @@ New notifications will be indicated in the little bell icon in the upper-right c
 
 ### Create and edit studios and titles
 
-In this section you learn how to create and manage studios and game titles.
+In this section, you learn how to create and manage studios and game titles.
 
 **To add a new studio:**
 
-1. Click the PlayFab icon to display the **My Studios** and **Titles** pages.
-2. Click **NEW STUDIO** to create a new studio in the dialog that appears.
+1. Select the PlayFab icon to display the **My Studios** and **Titles** pages.
+2. Select **NEW STUDIO** to create a new studio in the dialog that appears.
 3. Enter a **Studio Name** and **Authentication provider**.
 4. Save your changes and return to the My Studios and Titles page.
 
 **To edit an existing studio:**
 
-1. Select the elipsis drop-down menu to the right side of your **Studio name**, then select **Studio settings**.
+1. Select the ellipsis drop-down menu to the right side of your **Studio name**, then select **Studio settings**.
 
   ![Game manager - Edit Studio](media/tutorials/game-manager-mystudiosandtitles-settings.png)
 2. Make your edits.
@@ -345,7 +345,7 @@ In this section you learn how to create and manage studios and game titles.
 **To add a new title:**
 
 1. Select the drop-down menu to the right side of your Studio's Name, and then select **New title** to display the Create Title page.
-2. Enter the details and click the **CREATE TITLE** button.
+2. Enter the details and select the **CREATE TITLE** button.
 
   ![Game manager - Create a new game](media/tutorials/game-manager-create-title.png)
 3. Save your changes and return to the My Studios and Titles page.
@@ -360,12 +360,12 @@ In this section you learn how to create and manage studios and game titles.
 
 ### About User Accounts
 
-You can create user accounts that are individual or Admin-level accounts. Admin accounts provide access to one or more sections on one or more titles of a given studio, and of course provide full ability to configure studio and title information.
+You can create user accounts that are individual or Admin-level accounts. Admin accounts provide access to one or more sections on one or more titles of a given studio, and provide full ability to configure studio and title information.
 
 ![Game manager - Studio Users](media/tutorials/game-manager-studio-users.png)
 
 1. Select the drop-down menu to the far right from your Studio name, and then select **Studio users**.
 2. Choose **ADD USER** to display the Add New User page. Check the box if you want to make the user an Admin.
-3. To remove accounts in the **Users** page, simply select **Remove**.
+3. To remove accounts in the **Users** page, select **Remove**.
 
-If you do not already have a PlayFab Admin account, an e-mail will be sent to the address you provided. Upon confirmation, the new account will have access to the Studio and title.
+If you don't already have a PlayFab Admin account, an e-mail is sent to the address you provided. Upon confirmation, the new account has access to the Studio and title.
diff --git a/playfab-docs/live-service-management/index.yml b/playfab-docs/live-service-management/index.yml
index c2ea92f22..02960eef0 100644
--- a/playfab-docs/live-service-management/index.yml
+++ b/playfab-docs/live-service-management/index.yml
@@ -1,6 +1,6 @@
 ### YamlMime:Landing
 
-title: Azure PlayFab Live service management documentation
+title: PlayFab Live service management documentation
 summary: Manage and optimize your game effectively with game configuration and title data, player segmentation for targeted configuration and AB testing, and title-wide communication tools. # < 160 chars
 
 metadata:
diff --git a/playfab-docs/live-service-management/service-gateway/automation/cloudscript-af/quickstart.md b/playfab-docs/live-service-management/service-gateway/automation/cloudscript-af/quickstart.md
index 336735799..0894206df 100644
--- a/playfab-docs/live-service-management/service-gateway/automation/cloudscript-af/quickstart.md
+++ b/playfab-docs/live-service-management/service-gateway/automation/cloudscript-af/quickstart.md
@@ -19,20 +19,20 @@ In this quickstart, you write a CloudScript using Azure Functions with Visual St
 There are a couple of steps needed to get started with PlayFab C# CloudScript.
 
 - Visit the Visual Studio Code [QuickStart: Create an Azure Functions project using Visual Studio Code](/azure/azure-functions/create-first-function-vs-code-csharp?pivots=programming-language-csharp) and return here once you're set up. The following prerequisites are covered in their quickstart guide:
-  - An [Azure account](https://azure.microsoft.com/free).  Signing up for an Azure Account is free
+  - An [Azure account](https://azure.microsoft.com/free). Signing up for an Azure Account is free
   - An [Azure Subscription](/azure/cost-management-billing/manage/create-subscription)
   - A Functions App resource configured in the Azure portal
     - To minimize latency of your CloudScript using Azure Functions place them in the *US-West*, *US-West 2*, or *US-West 3* Azure regions.
     - **Security Note:** From a security perspective, you should make sure to only use a given function secret with PlayFab and not use it for calling the same function from any other source.
     - **Security Note:** For queued functions, you should set up a distinct storage account for the queues used for the queue trigger.
-- A [PlayFab](https://playfab.com/) account.
+- A [PlayFab](https://developer.playfab.com/) account.
 
 > [!NOTE]
 > PlayFab Azure Functions can use the Azure Functions V2 runtime or greater, and .NET Core 2 or greater. We recommend that you use the latest version (currently Azure Functions V4 and .NET 6).
 
 ## Create an Azure Function
 
-1. Create a basic "HelloWorld" example function. You can see how to do this by following the [Create your first function using Visual Studio Code guide](/azure/azure-functions/functions-create-first-function-vs-code).  For a code example using PlayFab variables, see the section below [PlayFab Function Context, Variables and using the Server SDKs](#playfabfunctioncontext).
+1. Create a basic "HelloWorld" example function. You can see how to do this by following the [Create your first function using Visual Studio Code guide](/azure/azure-functions/functions-create-first-function-vs-code). For a code example using PlayFab variables, see the section [PlayFab Function Context, Variables, and using the Server SDKs](#playfabfunctioncontext).
 
     > [!IMPORTANT]
     > The "Create your first function using Visual Studio Code" guide instructs you to set the Authorization Level of your Azure Function to `Anonymous`. This is done to simplify testing.
@@ -46,7 +46,7 @@ There are a couple of steps needed to get started with PlayFab C# CloudScript.
     
 3. For **Name**, enter a human-friendly name for your function. For **Function URL**, enter the HTTP Trigger URL of the function. The URL can be found in the context menu of the Azure function resource as shown in "Run the function in Azure" section of [Quickstart: Create a function in Azure using Visual Studio Code](/azure/azure-functions/create-first-function-vs-code-csharp?pivots=programming-language-csharp#run-the-function-in-azure). If your Azure Function uses `Function` level authorization, the URL contains  the Authorization key.
 
-For more information about deploying Azure functions, see [Deploy Azure Functions from Visual Studio Code](https://code.visualstudio.com/tutorials/functions-extension/deploy-app).
+For more information about deploying Azure functions, see [Deploy Azure Functions by using Visual Studio Code](https://learn.microsoft.com/azure/azure-functions/functions-develop-vs-code).
 
 
 ## Using and Calling CloudScript using Azure Functions from your PlayFab Title
@@ -144,15 +144,15 @@ private void CallCSharpExecuteFunction()
 
 ```
 
-### PlayFab CloudScript Context, Variables and Server SDKs <a name="playfabfunctioncontext"></a>
+### PlayFab CloudScript Context, Variables, and Server SDKs <a name="playfabfunctioncontext"></a>
 
-One advantage of using CloudScript using Azure Functions is that the PlayStream Event and Player Profile context is automatically passed to the Azure Function. On invocation of the CloudScript, you receive the context according to the function's invocation scenario. For example, the context is different depending on whether it was triggered by a PlayStream Action or called directly from the client. This includes information such as the entity profile on whose behalf the CloudScripts was invoked, and potentially the PlayStream events used to invoke the CloudScript.
+One advantage of using CloudScript using Azure Functions is that the PlayStream Event and Player Profile context is automatically passed to the Azure Function. On invocation of the CloudScript, you receive the context according to the function's invocation scenario. For example, the context varies depending on whether it's triggered by a PlayStream Action or called directly from the client. This includes information such as the entity profile on whose behalf the CloudScripts was invoked, and potentially the PlayStream events used to invoke the CloudScript.
 
 1. You'll need to install the PlayFab SDK via Package Manager. To do this open Terminal or CMD Console in Visual Studio Code and type: `dotnet add package PlayFabAllSDK`
 2. You need to include the [CS2AFHelperClasses.cs](https://github.com/PlayFab/PlayFab-Samples/blob/master/Samples/CSharp/AzureFunctions/CS2AFHelperClasses.cs) file that contains the implementation of `PlayFab.Samples`
 3. Execution of a script can occur through several methods (APIs, Scheduled Tasks, PlayStream Event, Segment Entering and Exit method).  The context of the execution is important to implement your CloudScript. See the [Using CloudScript context models tutorial](CloudScript-af-context.md) for details on how to use the context of the script.
 
-You can use the HelloWorld example below as your first Azure Function. It invokes an entity API and returns a greeting to the authenticated player. Classic server APIs can be invoked in a similar fashion; however, one would need to specify the title secret key in order to make the call. The secret key can be stored in [application settings](/azure/azure-functions/functions-how-to-use-azure-function-app-settings?tabs=portal#settings) and retrieved using `Environment.GetEnvironmentVariable()` method.
+You can use the HelloWorld example as your first Azure Function. It invokes an entity API and returns a greeting to the authenticated player. Classic server APIs can be invoked in a similar fashion; however, one would need to specify the title secret key in order to make the call. The secret key can be stored in [application settings](/azure/azure-functions/functions-how-to-use-azure-function-app-settings?tabs=portal#settings) and retrieved using `Environment.GetEnvironmentVariable()` method.
 
 ```c#
 using PlayFab;
@@ -233,7 +233,7 @@ To call the HelloWorld Azure Function from a PlayFab SDK use `ExecuteFunction`.
 
 ## Azure Functions in Automation Rules
 
-Azure Functions can also be called by creating rules and scheduled tasks.  This works in the same way as our standard CloudScript.  To create a rule or scheduled task, go to **Automation** > **Rules**  or **Automation** > **Scheduled Tasks**. 
+Azure Functions can also be called by creating rules and scheduled tasks. This works in the same way as our standard CloudScript. To create a rule or scheduled task, go to **Automation** > **Rules**  or **Automation** > **Scheduled Tasks**. 
 
 - Select **New Rule**
 - Enter a name for your rule
@@ -241,7 +241,7 @@ Azure Functions can also be called by creating rules and scheduled tasks.  This
 - Add an action
 - From the action dropdown, select **Execute Azure Function**
 
-A list of available Azure Functions that you've registered will be available in the drop-down list.
+A list of available Azure Functions that you've registered are available in the drop-down list.
 
 ![Configure Rule for Azure Functions](media/azure_function_rules.png)
 
@@ -251,7 +251,7 @@ With Azure functions, you now have the option to debug your CloudScript locally
 
 ## Execution limits
 
-CloudScript calls to Azure Functions have timeout limits. If your webhook takes too long to execute, the request will time out in PlayFab. Make sure your code can execute fast enough to stay under the timeout limits.
+CloudScript calls to Azure Functions have timeout limits. If your webhook takes too long to execute, the request times out in PlayFab. Make sure your code can execute fast enough to stay under the timeout limits.
 
 | Source         | Action type   | Limit (seconds) |
 | -------------- | ------------- | --------------: |
diff --git a/playfab-docs/live-service-management/service-gateway/automation/cloudscript/making-webhook-calls-from-cloudscript.md b/playfab-docs/live-service-management/service-gateway/automation/cloudscript/making-webhook-calls-from-cloudscript.md
index 2b45c7de9..27c1c1e13 100644
--- a/playfab-docs/live-service-management/service-gateway/automation/cloudscript/making-webhook-calls-from-cloudscript.md
+++ b/playfab-docs/live-service-management/service-gateway/automation/cloudscript/making-webhook-calls-from-cloudscript.md
@@ -22,6 +22,9 @@ This allows titles to make calls to basic informational services, but it *also*
 
 This tutorial discusses making Webhook calls from CloudScript, for both *nonsecure* and *secure* scenarios.
 
+> [!NOTE]
+> You can refer to the 'PlayFab static IP prefixes and addresses' section of the API Features page in the Developer Portal if you need to allowlist IP addresses used for outbound CloudScript calls.
+
 As a REST call, the structure of a Webhook call from CloudScript is simple. The elements to be specified are:
 
 - The URL endpoint.
diff --git a/playfab-docs/media/Player Profile Search.png b/playfab-docs/media/Player Profile Search.png
index f6c168ee9..eb38611df 100644
Binary files a/playfab-docs/media/Player Profile Search.png and b/playfab-docs/media/Player Profile Search.png differ
diff --git a/playfab-docs/media/add-subscription-items.png b/playfab-docs/media/add-subscription-items.png
index 32e2115fb..d20e0c86f 100644
Binary files a/playfab-docs/media/add-subscription-items.png and b/playfab-docs/media/add-subscription-items.png differ
diff --git a/playfab-docs/media/create-subscription-button.png b/playfab-docs/media/create-subscription-button.png
index 66c7ea7f7..27aabfd8e 100644
Binary files a/playfab-docs/media/create-subscription-button.png and b/playfab-docs/media/create-subscription-button.png differ
diff --git a/playfab-docs/media/economy-menu-location.png b/playfab-docs/media/economy-menu-location.png
index 8463bb549..291dbe4a8 100644
Binary files a/playfab-docs/media/economy-menu-location.png and b/playfab-docs/media/economy-menu-location.png differ
diff --git a/playfab-docs/media/inventory-after-redemption.png b/playfab-docs/media/inventory-after-redemption.png
index f5d41f1ec..c306cdc4a 100644
Binary files a/playfab-docs/media/inventory-after-redemption.png and b/playfab-docs/media/inventory-after-redemption.png differ
diff --git a/playfab-docs/media/marketplace-mapping.png b/playfab-docs/media/marketplace-mapping.png
index 8c67134fb..ce58c9836 100644
Binary files a/playfab-docs/media/marketplace-mapping.png and b/playfab-docs/media/marketplace-mapping.png differ
diff --git a/playfab-docs/media/player-account-id.png b/playfab-docs/media/player-account-id.png
index 163089bfa..903cb19bb 100644
Binary files a/playfab-docs/media/player-account-id.png and b/playfab-docs/media/player-account-id.png differ
diff --git a/playfab-docs/media/save-options.png b/playfab-docs/media/save-options.png
index dc4153d8b..0c1e9ccb4 100644
Binary files a/playfab-docs/media/save-options.png and b/playfab-docs/media/save-options.png differ
diff --git a/playfab-docs/media/secret-key.png b/playfab-docs/media/secret-key.png
index 6414d2eda..5e946c2e7 100644
Binary files a/playfab-docs/media/secret-key.png and b/playfab-docs/media/secret-key.png differ
diff --git a/playfab-docs/media/subscription-options.png b/playfab-docs/media/subscription-options.png
index f159d3015..ecc98408c 100644
Binary files a/playfab-docs/media/subscription-options.png and b/playfab-docs/media/subscription-options.png differ
diff --git a/playfab-docs/media/subscriptions-tab.png b/playfab-docs/media/subscriptions-tab.png
index 2dd5f0b18..a3002009b 100644
Binary files a/playfab-docs/media/subscriptions-tab.png and b/playfab-docs/media/subscriptions-tab.png differ
diff --git a/playfab-docs/multiplayer/index.yml b/playfab-docs/multiplayer/index.yml
index b7a6b9826..c423a889c 100644
--- a/playfab-docs/multiplayer/index.yml
+++ b/playfab-docs/multiplayer/index.yml
@@ -1,6 +1,6 @@
 ### YamlMime:Landing
 
-title: Azure PlayFab Multiplayer documentation
+title: PlayFab Multiplayer documentation
 summary: PlayFab Multiplayer services support real-time multiplayer capabilities for matchmaking, grouping, networking, and server hosting. # < 160 chars
 
 metadata:
diff --git a/playfab-docs/multiplayer/lobby/create-a-lobby.md b/playfab-docs/multiplayer/lobby/create-a-lobby.md
index bb523de61..bf9cd0d9b 100644
--- a/playfab-docs/multiplayer/lobby/create-a-lobby.md
+++ b/playfab-docs/multiplayer/lobby/create-a-lobby.md
@@ -22,9 +22,9 @@ There are several ways a lobby can be created.
 * **By your game servers**: Your title's game servers can create lobbies and wait for players to join. These are server-owned lobbies.
 * **By matchmaking**: After a group of players form after matchmaking, a lobby is created as a holding place before the game starts. These are client-owned lobbies.
 
-From a technical perspective, all lobbies are fall into two main categories based on ownership&mdash;server-owned and client-owned. To learn more, see [Owner requirements and privileges](owner-requirements-and-privileges.md).
+From a technical perspective, all lobbies fall into two main categories based on ownership&mdash;server-owned and client-owned. To learn more, see [Owner requirements and privileges](owner-requirements-and-privileges.md).
 
-The general usage of PlayFab Lobby is to temporarily hold a group of players together. For commonly used applications of Lobby, see the [Azure PlayFab Lobby overview](index.md).
+The general usage of PlayFab Lobby is to temporarily hold a group of players together. For commonly used applications of Lobby, see the [PlayFab Lobby overview](index.md).
 
 ### Supported entity types
 
diff --git a/playfab-docs/multiplayer/lobby/find-lobbies.md b/playfab-docs/multiplayer/lobby/find-lobbies.md
index 46c1e7440..99c1de369 100644
--- a/playfab-docs/multiplayer/lobby/find-lobbies.md
+++ b/playfab-docs/multiplayer/lobby/find-lobbies.md
@@ -63,7 +63,7 @@ These OData operators can be used to compose query strings. The operators are ca
 | le         | less than or equal to    | number_key2 le 10                                     |
 | gt         | greater than             | number_key3 gt 100                                    |
 | ge         | greater than or equal to | number_key3 ge 100                                    |
-| ne         | ne                       | string_key1 ne 'CaptureTheFlag'                       |
+| ne         | not equal to             | string_key1 ne 'CaptureTheFlag'                       |
 | and        | and                      | string_key1 eq 'CaptureTheFlag' and number_key2 lt 10 |
 
 
@@ -92,7 +92,7 @@ OData style string that contains sorting for this query in either ascending ("as
 |-----------------------------|---------------------------------------------------|
 | number_key1 asc             | order by number search key ascending              |
 | lobby/memberCount desc      | order by number search key descending             |
-| distance(number_key1 = 5)   | sort on distance from the given number            |
+| distance{number_key1 = 5}   | sort on distance from the given number            |
 | *default*                   | order by creation time descending                 |
 
 
@@ -143,9 +143,9 @@ void FindGamesWithRuntimeQuery(
     filterString += " and ";
     filterString += PFLOBBY_SEARCH_KEY_COMPETITION_STYLE + std::string(" eq ") + "'" + COMPETITION_STYLE_RANKED + "'";
     filterString += " and ";
-    filterString += PFLOBBY_SEARCH_KEY_SKILL + std::string(" -ge ") + std::to_string(minimumSkill);
+    filterString += PFLOBBY_SEARCH_KEY_SKILL + std::string(" ge ") + std::to_string(minimumSkill);
     filterString += " and ";
-    filterString += PFLOBBY_SEARCH_KEY_SKILL + std::string(" -le ") + std::to_string(maximumSkill);
+    filterString += PFLOBBY_SEARCH_KEY_SKILL + std::string(" le ") + std::to_string(maximumSkill);
 
     // Create sort string based on player's sort preference.
     std::string sortString;
diff --git a/playfab-docs/multiplayer/lobby/index.md b/playfab-docs/multiplayer/lobby/index.md
index d7f2cbb4b..5892e9f89 100644
--- a/playfab-docs/multiplayer/lobby/index.md
+++ b/playfab-docs/multiplayer/lobby/index.md
@@ -1,7 +1,7 @@
 ---
-title: Azure PlayFab Lobby overview
+title: PlayFab Lobby overview
 author: joannaleecy
-description: Learn about Azure PlayFab Lobby.
+description: Learn about PlayFab Lobby.
 ms.author: jenelleb
 ms.date: 04/08/2025
 ms.topic: article
@@ -10,9 +10,9 @@ keywords: playfab, multiplayer, lobby, matchmaking
 ms.localizationpriority: medium
 ---
 
-# Azure PlayFab Lobby overview
+# PlayFab Lobby overview
  
-Azure PlayFab Lobby is a service to create a temporary grouping mechanism for players to play games together. It's frequently used together with matchmaking, allowing for pre-formed groups to join the same matchmaking ticket, or allowing matched players to convene and receive further notifications about the group such as join/leave events or server connection details. 
+PlayFab Lobby is a service to create a temporary grouping mechanism for players to play games together. It's frequently used together with matchmaking, allowing for pre-formed groups to join the same matchmaking ticket, or allowing matched players to convene and receive further notifications about the group such as join/leave events or server connection details. 
 
 ## Benefits
 
diff --git a/playfab-docs/multiplayer/lobby/join-lobbies.md b/playfab-docs/multiplayer/lobby/join-lobbies.md
index 9f5aba747..fdb06af0c 100644
--- a/playfab-docs/multiplayer/lobby/join-lobbies.md
+++ b/playfab-docs/multiplayer/lobby/join-lobbies.md
@@ -22,7 +22,8 @@ Players can discover connection strings and join lobbies in the following ways.
 1. By searching for available lobbies with [FindLobbies](find-lobbies.md) and joining an available lobby
 1. By sharing the lobby's connection string via any out-of-band, custom discovery mechanism
 
-> NOTE: Only players (i.e. title_player_account PlayFab entities) can join lobbies as members. Game servers (i.e. game_server PlayFab entities) cannot join lobbies as members. For more information on the how game servers interact with lobbies, see [Game Servers and Lobbies](lobby-server-overview.md).
+> [!NOTE]
+> Only players (i.e. title_player_account PlayFab entities) can join lobbies as members. Game servers (i.e. game_server PlayFab entities) cannot join lobbies as members. For more information on the how game servers interact with lobbies, see [Game Servers and Lobbies](lobby-server-overview.md).
 
 ## Connection strings and Lobby IDs
 
diff --git a/playfab-docs/multiplayer/lobby/lobby-and-matchmaking-client-sdk-errors.md b/playfab-docs/multiplayer/lobby/lobby-and-matchmaking-client-sdk-errors.md
index c9813f349..e43fc92a0 100644
--- a/playfab-docs/multiplayer/lobby/lobby-and-matchmaking-client-sdk-errors.md
+++ b/playfab-docs/multiplayer/lobby/lobby-and-matchmaking-client-sdk-errors.md
@@ -6,7 +6,7 @@ ms.author: scmunro
 ms.date: 11/12/2022
 ms.topic: article
 ms.service: azure-playfab
-keywords: playfab, multiplayer, networking, lobby, matchmaking, async, state change, notification
+keywords: playfab, multiplayer, networking, lobby, matchmaking, async, state change, message
 ---
 
 # Handling Lobby and Matchmaking SDK errors
@@ -55,7 +55,7 @@ than synchronous errors. A non-exhaustive list of some of the types of errors re
 
 - service throttling errors
 - invalid parameter errors that can't be validated synchronously on the client
-- errors interacting with the real-time notification service
+- errors interacting with the real-time message service
 - connectivity errors
 
 See the [Error codes and error messages](#error-codes-and-error-messages) section for guidance on getting human-readable 
diff --git a/playfab-docs/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications.md b/playfab-docs/multiplayer/lobby/lobby-and-matchmaking-real-time-messages.md
similarity index 52%
rename from playfab-docs/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications.md
rename to playfab-docs/multiplayer/lobby/lobby-and-matchmaking-real-time-messages.md
index 5ed1b9db7..582c48dcd 100644
--- a/playfab-docs/multiplayer/lobby/lobby-and-matchmaking-real-time-notifications.md
+++ b/playfab-docs/multiplayer/lobby/lobby-and-matchmaking-real-time-messages.md
@@ -1,43 +1,43 @@
 ---
 author: thboard
-title: Lobby and Matchmaking real-time Notifications
-description: Conceptual overview for Match and Lobby notifications
+title: Lobby and Matchmaking real-time messages
+description: Conceptual overview for Match and Lobby messages
 ms.author: thboard
 ms.topic: conceptual
 ms.service: azure-playfab
 ms.date: 03/14/2022
 ---
 
-# Lobby and Matchmaking real-time notifications
+# Lobby and Matchmaking real-time messages
 
 ## Overview
 
 The Matchmaking and Lobby features have built in support for real-time
-notifications. Notifying players of changes to Matchmaking or Lobby has never
-been easier, as the work to handle notifications is done for you in the [Azure PlayFab Lobby and Matchmaking SDK](lobby-matchmaking-sdks/lobby-matchmaking-sdks.md). New APIs will
-allow connected clients to subscribe for notifications of Lobby and Matchmaking
+messages. Sending messages to players about changes to Matchmaking or Lobby has never
+been easier, as the work to handle messages is done for you in the [PlayFab Lobby and Matchmaking SDK](lobby-matchmaking-sdks/lobby-matchmaking-sdks.md). New APIs will
+allow connected clients to subscribe for messages about Lobby and Matchmaking
 changes. With this addition, you'll no longer need to poll for changes to
 matches or lobbies. 
 
 The SDK has been designed to simplify your work. The SDK manages calls between 
 game clients or servers and PlayFab Lobby and Matchmaking services. It handles 
-the delivery of notifications from those services to connected clients in real 
-time. Real-time notifications have cross-platform support, and will work 
+the delivery of messages from those services to connected clients in real 
+time. Real-time messages have cross-platform support, and will work 
 anywhere PlayFab supplies a SDK. Matchmaking and Lobby can be used separately or
-together, and real-time notifications will work in either case. There's no
-support for real-time notifications without the SDK at this time.
-Real-time notifications aren't available as a solution for stand-alone or
+together, and real-time messages will work in either case. There's no
+support for real-time messages without the SDK at this time.
+Real-time messages aren't available as a solution for stand-alone or
 general use.
 
-## How do real-time notifications work 
+## How do real-time messages work 
 
-Each client maintains a single WebSocket to receive real-time notifications.
+Each client maintains a single WebSocket to receive real-time messages.
 When there are updates to Matchmaking or Lobby resources in the cloud, the
-SDK will forward notifications in real-time to all connected clients
+SDK will forward messages in real-time to all connected clients
 subscribed to those resources. 
 
-When a client connects to receive real-time notifications, they'll open a new
-WebSocket connection to receive notifications and listen for change events. When
+When a client connects to receive real-time messages, they'll open a new
+WebSocket connection to receive messages and listen for change events. When
 a client creates a lobby, joins a lobby, starts listening for invitations, or
 creates a Matchmaking ticket, the connected client will subscribe to a Lobby or
 Matchmaking resource to listen for changes. The client will be notified when
@@ -45,27 +45,27 @@ there's an update on the resource topic they’ve subscribed to. For example, if
 client has subscribed to a Lobby resource, they may be notified on change events
 like Player A or B has joined or left a Lobby. Matchmaking and Lobby
 documentation describe in more detail the operations that will power
-notifications. 
+messages. 
 
-The WebSocket connection that enables real-time notifications is also used for
+The WebSocket connection that enables real-time messages is also used for
 detecting client connectivity. This client connectivity status is used by the
 Lobby service to power lobby ownership management. 
 
 ## Shared connection support
 
-Matchmaking and Lobby notifications have support to share a single WebSocket
+Matchmaking and Lobby messages have support to share a single WebSocket
 connection, which may be useful if you’re creating a title with couch co-op.
 Today, up to eight local users may share the WebSocket connection, and local
 players can be added or removed to that shared connection. Multiple users
-sharing the same connection can subscribe to topics to get notifications for
+sharing the same connection can subscribe to topics to get messages for
 Matchmaking or Lobby events for those topics. 
 
 ## Using the SDK
 
 The SDK simplifies your work for cross-network and cross-platform play by
-handling real-time notifications for you. Notifications are sent to clients on
+handling real-time messages for you. Messages are sent to clients on
 receiving invites, joining and updating lobbies, finding matches, and more. The
-SDK enables cross-platform play and real-time notifications on any
-platform that PlayFab offers SDK support. Sending notifications to clients is
+SDK enables cross-platform play and real-time messages on any
+platform that PlayFab offers SDK support. Sending messages to clients is
 automatic, and the developer doesn't have to do any work to enable
-notifications. 
+messages. 
diff --git a/playfab-docs/multiplayer/lobby/lobby-and-matchmaking.md b/playfab-docs/multiplayer/lobby/lobby-and-matchmaking.md
index 3fe6b63b8..aa4d438ec 100644
--- a/playfab-docs/multiplayer/lobby/lobby-and-matchmaking.md
+++ b/playfab-docs/multiplayer/lobby/lobby-and-matchmaking.md
@@ -13,25 +13,25 @@ ms.localizationpriority: medium
 # Use Lobby and Matchmaking Together
  
 
-When designing multiplayer games, matchmaking and lobbies are often used together to help people form groups to play together. 
+When you design multiplayer games, matchmaking and lobbies are often used together to help people form groups to play together. 
 
-PlayFab Lobby and PlayFab Matchmaking helps you implement a wide variety of multiplayer scenarios.
+PlayFab Lobby and PlayFab Matchmaking help you implement a wide variety of multiplayer scenarios.
 
-This article describes the relationship between these two services and illustrates how they can be used together to implement a [game scenario](#example-scenario) specified below.
+This article describes the relationship between these two services and shows how they can be used together to implement the following [game scenario](#example-scenario).
 
 ## Understand the relationship between Lobby and Matchmaking
 
 Lobby and Matchmaking work seamlessly together to create cohesive multiplayer matchmaking experience for your title. 
 
 * Matchmaking gathers a set of players together looking to participate in a game session.
-* After matchmaking has identified a set of players, Lobby provides them a communication medium to coordinate joining a game session together.
+* After matchmaking identifies a set of players, Lobby provides them with a communication medium to coordinate joining a game session together.
     * Common scenarios for lobby include sharing game server connection information, sharing client IPs for peer-to-peer games, and sharing player configurations.
 
 ### Arranged lobbies
 
-Titles can use "Arranged Lobbies" to support easily creating lobbies for your players which have been grouped together via matchmaking.
+Titles can use "Arranged Lobbies" to support easily creating lobbies for your players that are grouped together via matchmaking.
 
-After the matchmaking ticket has successfully matched a group of players, the matchmaking ticket will contain a __lobbyArrangementString__. Each player can then pass the arrangement string to __PFMultiplayerJoinArrangedLobby__ to join the same lobby.
+After the matchmaking ticket successfully matches a group of players, the matchmaking ticket contains a __lobbyArrangementString__. Each player can then pass the arrangement string to __PFMultiplayerJoinArrangedLobby__ to join the same lobby.
 
 ## Example Scenario
 
@@ -43,24 +43,24 @@ A player wants to play with other people. The player starts a multiplayer game,
 * The initial set of players is populated via matchmaking.
 * The lobby owner is able to invite friends to join.
 * When the required number of players are met, all players in the lobby receive a message asking if they're ready to start the game. They have one minute to respond. The game starts after all the players confirmed that they're ready to start game. 
-* If players in the lobby did not confirm their ready-to-play status, the lobby owner can remove them as inactive players and use matchmaking to find new players to quickly replace them.
+* If players in the lobby didn't confirm their ready-to-play status, the lobby owner can remove them as inactive players and use matchmaking to find new players to quickly replace them.
 * When any player gets disconnected unexpectedly during the game, the title should find a new replacement for the dropped player through matchmaking using server backfill.
-* When the game ends, all players return to the lobby. Players are awarded team achievements equally. They have the option to either stay to start another game together or leave the lobby.
+* When the game ends, all players return to the lobby. Players are awarded team achievements equally. They can either stay to start another game together or leave the lobby.
 
 ### Implementation
 
-This section describes how to use Matchmaking and Lobby to implement the above [design specifications](#design-specifications).
+This section describes how to use Matchmaking and Lobby to implement the [design specifications](#design-specifications).
 
-* [Create a matchmade lobby](#create-a-matchmade-lobby)
+* [Create a match-made lobby](#create-a-match-made-lobby)
 * [Send invites to friends](#send-invites-to-friends)
 * [Allow people to find and join game](#allow-people-to-find-and-join-game)
-* [Notify players to start game](#notify-players-to-start-game)
+* [Get player confirmation to start game](#get-player-confirmation-to-start-game)
 * [Remove and replace inactive players](#remove-and-replace-inactive-players)
 * [Handle a finished game](#handle-a-finished-game)
 
-### Create a matchmade lobby
+### Create a match-made lobby
 
-Create a public lobby for a group of matchmade players.
+Create a public lobby for a group of match-made players.
 
 * Each player creates a matchmaking ticket with their specified matchmaking attributes.
     * To learn more, see [Specify ticket attributes](../matchmaking/ticket-attributes.md).
@@ -68,9 +68,9 @@ Create a public lobby for a group of matchmade players.
     * Tickets are matched based on rules.
     * Rules can be defined in the matchmaking queue configuration.
     * To learn more, see [Configure matchmaking queues](../matchmaking/config-queues.md).
-* After matchmaking, each player joins the matchmade lobby via the matchmaking ticket's __lobbyArrangementString__.
+* After matchmaking, each player joins the match-made lobby via the matchmaking ticket's __lobbyArrangementString__.
     * When joining the arranged lobby, specify that the lobby's __accessPolicy__ is __Public__ to make the lobby open.
-    * See [Arranged lobbies](#arranged-lobbies) for more information.
+    * For more information, see [Arranged lobbies](#arranged-lobbies).
 * The first player to join the arranged lobby becomes the owner for the lobby.
 * The lobby properties can be used to specify which game map a game session intends to use.
     * For more information, see [Lobby properties](lobby-properties.md).
@@ -88,15 +88,15 @@ Allow the lobby owner to select friends and send invites.
 
 ### Allow people to find and join game
 
-Setup the lobby's search properties to allow other players to find it
+Set up the lobby's search properties to allow other players to find it
 
 * Display all lobbies in your game UI. Your title should also provide a way to accept player's search terms.
 * Use __PFMultiplayerFindLobbies__ using the player's search parameters to return a list of lobbies that match the criteria.
 * After a player selects to join a game, use __PFMultiplayerJoinLobby__ to add the player to the game.
 
-### Notify players to start game 
+### Get player confirmation to start game 
 
-Inform all players in the lobby that game is ready to start
+Inform all players in the lobby that the game is ready to start
 
 * When the required number of players are in the lobby, display game UI to get players to confirm that they're ready to start play.
 * Allow the lobby owner to view these confirmation responses.
@@ -105,19 +105,19 @@ Inform all players in the lobby that game is ready to start
 
 Lobby owner has the ability to remove inactive or disconnected players and initiate matchmaking to fill up the remaining spots
 
-* If a player has discoonected or did not respond within the given set duration (one minute), use __PFLobbyForceRemoveMember__ to remove the player.
-* The lobby owner will use __CreateServerBackfillTicket__ to create a matchmaking ticket. Tickets created using this API are given priority during searching. This is to minimize gameplay disruption. To learn more, see [Using server backfill tickets](../matchmaking/backfill-tickets.md).
+* If a player disconnects or didn't respond within the given set duration (one minute), use __PFLobbyForceRemoveMember__ to remove the player.
+* The lobby owner uses __CreateServerBackfillTicket__ to create a matchmaking ticket. Tickets created using this API are given priority during searching. This approach minimizes gameplay disruption. To learn more, see [Using server backfill tickets](../matchmaking/backfill-tickets.md).
 * After joining the backfill lobby, the game's lobby owner can share the original lobby's connection string with the new backfill players and they can join the original lobby.
 * Extend the game start time when appropriate.
 
 ### Handle a finished game
 
-After the game has finished, all players return to the lobby screen to complete the game session.
+After the game finishes, all players return to the lobby screen to complete the game session.
 
-* Lobbies are transient so any data from the lobby which should be persisted should be retained by each player at this point.
+* Lobbies are transient so any data from the lobby that should be persisted must be retained by each player at this point.
     * For example, some game scenarios may benefit from processing data stored in the member properties and turning that data into player achievements.
-* Players who want to continue playing with the same group will stay in the lobby.
-* Players who want to stop playing with the same group will leave the lobby with __PFLobbyLeave__ and restart the process with a new matchmaking group.
+* Players who want to continue playing with the same group stay in the lobby.
+* Players who want to stop playing with the same group leave the lobby with __PFLobbyLeave__ and restart the process with a new matchmaking group.
 
 ## See also
 
diff --git a/playfab-docs/multiplayer/lobby/lobby-getting-started.md b/playfab-docs/multiplayer/lobby/lobby-getting-started.md
index e5f8bac2c..04e3dbfef 100644
--- a/playfab-docs/multiplayer/lobby/lobby-getting-started.md
+++ b/playfab-docs/multiplayer/lobby/lobby-getting-started.md
@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 # Lobby SDK Quickstart
  
 
-This article describes how to set up the development environment for Azure PlayFab Lobby and create your first lobby using the PlayFab Multiplayer C/C++ SDK.
+This article describes how to set up the development environment for PlayFab Lobby and create your first lobby using the PlayFab Multiplayer C/C++ SDK.
 
 > [!NOTE]
 > The PlayFab Multiplayer SDK also provides APIs for PlayFab Matchmaking.
@@ -24,7 +24,7 @@ This article describes how to set up the development environment for Azure PlayF
 
 ## Prerequisites
 
-You need a [PlayFab account](https://playfab.com) to use PlayFab Lobbies. For instructions to create an account, see [Quickstart: Game Manager](../../live-service-management/gamemanager/quickstart.md).
+You need a [PlayFab account](https://developer.playfab.com) to use PlayFab Lobbies. For instructions to create an account, see [Quickstart: Game Manager](../../live-service-management/gamemanager/quickstart.md).
 
 ## Download and set up the PlayFab Multiplayer SDK
 
diff --git a/playfab-docs/multiplayer/lobby/lobby-invites.md b/playfab-docs/multiplayer/lobby/lobby-invites.md
index 80fa45b20..b98f90312 100644
--- a/playfab-docs/multiplayer/lobby/lobby-invites.md
+++ b/playfab-docs/multiplayer/lobby/lobby-invites.md
@@ -15,7 +15,8 @@ ms.localizationpriority: medium
 
 This article provides an overview of Lobby invites and how to use them in the Lobby and Matchmaking SDK.
 
-> NOTE: Only players (i.e. title_player_account PlayFab entities) can send or receive invites. Game servers (i.e. game_server PlayFab entities) cannot. For more information on the how game servers interact with lobbies, see [Game Servers and Lobbies](lobby-server-overview.md).
+> [!NOTE]
+> Only players (i.e. title_player_account PlayFab entities) can send or receive invites. Game servers (i.e. game_server PlayFab entities) cannot. For more information on the how game servers interact with lobbies, see [Game Servers and Lobbies](lobby-server-overview.md).
 
 ## Invite types
 
@@ -27,6 +28,7 @@ There are two types of invites your game is likely to make use of.
 ### Joining a lobby by in-game invites
 
 * A member of a lobby may invite another player to that lobby directly via the lobby service.
+* The lobby owner can choose to restrict sending invites to only the owner via the lobby property  __RestrictInvitesToLobbyOwner__
 * This invite shares the lobby's connection string with the invited player.
 * The invited player receives the invitation via __PFLobbyInviteReceivedStateChange__ and can use the attached connection string to join the lobby.
 * These invites work cross-platform but only work in-game.
diff --git a/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-and-matchmaking-release-notes.md b/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-and-matchmaking-release-notes.md
index 27fead97f..6619b6c57 100644
--- a/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-and-matchmaking-release-notes.md
+++ b/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-and-matchmaking-release-notes.md
@@ -11,41 +11,89 @@ ms.localizationpriority: medium
 ---
 
 # PlayFab Multiplayer C++ SDK release notes
+## 1.9.0
+
+March 26, 2026
+
+### New features
+
+- Added [PFLobbyGetRestrictInvitesToLobbyOwner](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetrestrictinvitestolobbyowner.md) to retrieve the lobby’s current policy that indicates whether only the lobby owner can send invites to join the lobby.
+- Added the `restrictInvitesToLobbyOwner` field to [PFLobbyArrangedJoinConfiguration](../playfabmultiplayerreference-cpp/pflobby/structs/pflobbyarrangedjoinconfiguration.md), [PFLobbyCreateConfiguration](../playfabmultiplayerreference-cpp/pflobby/structs/pflobbycreateconfiguration.md), and [PFLobbyDataUpdate](../playfabmultiplayerreference-cpp/pflobby/structs/pflobbydataupdate.md) structs to control whether only the lobby owner or any member can send invites to join the lobby. If you're using default initializers for these structs, no code changes are necessary. If you're not using default initializers, be sure to initialize the new fields.
+
+### Bug fixes
+
+- Fixed an issue where the SDK didn't automatically generate a disconnected state change after a connection was lost and the SDK couldn't reestablish the connection.
+
+## 1.8.8
+
+March 23, 2026
+
+### Bug fixes
+
+- Fixed undefined reference to DeriveWorkQueue on Linux.
+- Improved Linux linker hardening for PlayFab Multiplayer.
+
+## 1.8.7
+
+February 26, 2026
+
+### Bug fixes
+
+- Fixed an issue where the library might crash after losing a WebSocket connection while paused in a debugger.
+
+## 1.8.6
+
+February 13, 2026
+
+### Bug fixes
+
+- Fixed an issue where, 24 hours after the first lobby or matchmaking attempt, if the library isn't cleaned up, it might fail to create subsequent lobbies, join subsequent lobbies, subscribe to lobby invitations, or create subsequent matchmaking tickets.
+- Fixed an issue where PlayFab Lobby service failures could cause the PlayFabMultiplayer library to be unable to create new lobbies until after it called [PFMultiplayerUninitialize()](../playfabmultiplayerreference-cpp/pfmultiplayer/functions/pfmultiplayeruninitialize.md) and the library was reinitialized with `PFMultiplayerInitialize`.
+- Fixed an issue on non-GDK platforms where the library kept internal process task queue memory allocated after the library was cleaned up by using [PFMultiplayerUninitialize()](../playfabmultiplayerreference-cpp/pfmultiplayer/functions/pfmultiplayeruninitialize.md).
+- Fixed an issue where several PubSub service errors were collapsed into one generic HTTP 4XX error message, [0x89236409](../playfabmultiplayerreference-cpp/pfmultiplayererrors.md). Now, the library provides different error codes for different service errors which makes it easier to diagnose and troubleshoot.
+
+## 1.8.5
+
+January 21, 2026
+
+### Bug fixes
+
+- Hid symbols in iOS platform to prevent symbol clashing. This version is an iOS only release.
 
 ## 1.8.4
 
-Nov 5, 2025
+November 5, 2025
 
 ### Bug fixes
 
-- Fixed an issue where exposed U symbols crashes at runtime on Android. All symbols except from the ones provided by us were hidden. This is an Android-only release.
+- Fixed an issue where exposed U symbols caused crashes at runtime on Android. All symbols except the ones provided by Microsoft are hidden. This is an Android-only release.
 
 ## 1.8.3
 
-Oct 10, 2025
+October 10, 2025
 
 ### Bug fixes
 
-- Fixed an issue where exposed `libHttpClient` symbols caused symbol clashes on Android. Added option that allows games that require a specific version of
-  `libHttpClient` to supply their own dynamic `libHttpClient` and use the `.dynLHC` package to avoid symbol conflicts. The `.hideLHC` from
-  v1.8.2 is replaced by `.dynLHC` drop. This is an Android-only release.
+- Fixed an issue where exposed `libHttpClient` symbols caused symbol clashes on Android. Added an option that allows games that require a specific version of
+  `libHttpClient` to supply their own dynamic `libHttpClient` and use the `.dynLHC` package to avoid symbol conflicts. The `.dynLHC` package replaces the `.hideLHC` package from
+  version 1.8.2. This is an Android-only release.
 
 ## 1.8.2
 
-Sep 5, 2025
+September 5, 2025
 
 ### Bug fixes
 
 - Fixed an issue where exposed `libHttpClient` symbols caused symbol clashes on Android. Added an option that allows games that require a specific version of
   `libHttpClient` to supply their own dynamic `libHttpClient` and use the `.hideLHC` package to avoid symbol conflicts. This is an Android-only release.
 
-### New Support
+### New support
 
-- Added support for 16 KB page sizes to satisfy the new [Android page size requirements](https://developer.android.com/guide/practices/page-sizes).
+- Added support for 16-KB page sizes to satisfy the new [Android page size requirements](https://developer.android.com/guide/practices/page-sizes).
 
 ## 1.8.1
 
-Aug 20, 2025
+August 20, 2025
 
 ### Bug fixes
 
@@ -55,10 +103,10 @@ Aug 20, 2025
 
 June 11, 2025
 
-### New Features
+### New features
 
-- Added new [PFMultiplayerConnectToLobby](../playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerconnecttolobby.md)
-- Added a `lobbyId` field to the [PFLobbyInviteReceivedStateChange](../playfabmultiplayerreference-cpp/pflobby/structs/pflobbyinvitereceivedstatechange.md) struct to support joining using just the lobby id.
+- Added new [PFMultiplayerConnectToLobby](../playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerconnecttolobby.md) function.
+- Added a `lobbyId` field to the [PFLobbyInviteReceivedStateChange](../playfabmultiplayerreference-cpp/pflobby/structs/pflobbyinvitereceivedstatechange.md) struct to support joining using just the lobby ID.
 
 ### Bug fixes
 - Fixed bug where PubSub connection failures could cause library to crash.
@@ -69,7 +117,7 @@ May 7, 2025
 
 ### Bug fixes
 
-- Fixed an issue where exposed symbols caused symbol clashes on the Android platform. This is an Android-only release.
+- Fixed an issue where exposed symbols caused symbol clashes on the Android platform. This version supports only Android.
 
 ## 1.7.15
 
@@ -87,8 +135,8 @@ April 28, 2025
 
 - Fixed an issue where the second local user failed to join the lobby created by the first user after a network reconnection.
 
-### Threading Changes
-- The SDK is replacing its custom networking threads with a thread pool implementation, which will enable more efficient CPU utilization.
+### Threading changes
+- The SDK replaces its custom networking threads with a thread pool implementation, which enables more efficient CPU utilization.
 
 ## 1.7.13
 
@@ -106,8 +154,8 @@ April 15, 2025
 
 ### Bug fixes
 - Fixed a crash that occurred when a network reconnection happened after an unexpected disconnection, following the creation and joining of a multi-user lobby.
-- Fixed an issue where calling [PFLobbyPostUpdate](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbypostupdate.md). on a non-existent lobby did not automatically generate a disconnected state change.
-- Fixed a crash and exposing `libc++_shared.so` when loading library on Android
+- Fixed an issue where calling [PFLobbyPostUpdate](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbypostupdate.md) on a non-existent lobby didn't automatically generate a disconnected state change.
+- Fixed a crash and exposure of `libc++_shared.so` when loading library on Android.
 - Included `libHttpClient` in the release package on Android. For usage details, see [PlayFab Multiplayer Android getting started](android-specific-requirements.md).
 - Fixed an issue with symbol exposure on the Apple platform.
 
@@ -127,7 +175,7 @@ March 6, 2025
 
 ### Bug fixes
 
-- Fixed an issue where the library could crash if the app suspended at the same time that a local user was being disconnected. This is a GDK-only release.
+- Fixed an issue where the library could crash if the app suspended at the same time that a local user was disconnecting. This fix is for a GDK-only release.
 
 ## 1.7.9
 
@@ -135,9 +183,9 @@ February 11, 2025
 
 ### Bug fixes
 
-- Fixed an issue where the library would incorrectly retry some operations associated with the real-time notification service when HTTP 401 was received.
-- Fixed a regression introduced in v1.7.8 that assigned the `PFMultiplayerServerDetails::region` value to `PFMultiplayerServerDetails::fqdn`.
-- Fixed an issue where the properties associated with a new member weren't immediately available until a subsequent `Updated` state change was provided. Now, as soon as a `MemberAdded` state change is provided to the game, [PFLobbyGetMemberConnectionStatus()](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetmemberconnectionstatus.md), [PFLobbyGetMemberPropertyKeys()](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetmemberpropertykeys.md), and [PFLobbyGetMemberProperty()](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetmemberproperty.md) provide the most up-to-date information associated with the member. In order to preserve compatibility for games that took a dependency on the previous behavior, the first `Updated` state change after the member is added will continue to provide this initial list of property keys as if they were new properties.
+- Fixed an issue where the library incorrectly retried some operations associated with the real-time message service when it received HTTP 401.
+- Fixed a regression introduced in version 1.7.8 that assigned the `PFMultiplayerServerDetails::region` value to `PFMultiplayerServerDetails::fqdn`.
+- Fixed an issue where the properties associated with a new member weren't immediately available until a subsequent `Updated` state change. Now, as soon as a `MemberAdded` state change is provided to the game, [PFLobbyGetMemberConnectionStatus()](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetmemberconnectionstatus.md), [PFLobbyGetMemberPropertyKeys()](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetmemberpropertykeys.md), and [PFLobbyGetMemberProperty()](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetmemberproperty.md) provide the most up-to-date information associated with the member. To preserve compatibility for games that took a dependency on the previous behavior, the first `Updated` state change after the member is added continues to provide this initial list of property keys as if they were new properties.
 - Fixed a couple of issues where the library could crash when [PFMultiplayerUninitialize()](../playfabmultiplayerreference-cpp/pfmultiplayer/functions/pfmultiplayeruninitialize.md) was called while cleaning up internal web request resources.
 - Fixed an issue for GDK Xbox where the library could crash during suspend while cleaning up internal state associated with the invite listener.
 - Fixed an issue for Android where the library could crash when when [PFMultiplayerUninitialize()](../playfabmultiplayerreference-cpp/pfmultiplayer/functions/pfmultiplayeruninitialize.md) was called while cleaning up JavaVM attached threads.
@@ -149,9 +197,9 @@ November 5, 2024
 
 ### Bug fixes
 
-- Fixed an issue where calling [PFMatchmakingTicketCancel](../playfabmultiplayerreference-cpp/pfmatchmaking/functions/pfmatchmakingticketcancel.md) for a backfill ticket created with [PFMultiplayerCreateServerBackfillTicket](../playfabmultiplayerreference-cpp/pfmatchmaking/functions/pfmultiplayercreateserverbackfillticket.md) would fail.
+- Fixed an issue where calling [PFMatchmakingTicketCancel](../playfabmultiplayerreference-cpp/pfmatchmaking/functions/pfmatchmakingticketcancel.md) for a backfill ticket created with [PFMultiplayerCreateServerBackfillTicket](../playfabmultiplayerreference-cpp/pfmatchmaking/functions/pfmultiplayercreateserverbackfillticket.md) failed.
 - Fixed an issue where the SDK treated all values in [PFMultiplayerServerDetails](../playfabmultiplayerreference-cpp/pfmatchmaking/structs/pfmultiplayerserverdetails.md) as mandatory.
-- Fixed an issue where the Sony (PlayStation&#174;4 and PlayStation&#174;5) versions of the SDK didn't correctly handle intermittent HTTP request failures from the Sony (PlayStation&#174;4 and PlayStation&#174;5) HTTP library. Additionally, improved error reporting to provide more detailed information in such cases.
+- Fixed an issue where the Sony (PlayStation®4 and PlayStation®5) versions of the SDK didn't correctly handle intermittent HTTP request failures from the Sony (PlayStation®4 and PlayStation®5) HTTP library. Additionally, improved error reporting now provides more detailed information for these cases.
 
 'PlayStation' is a registered trademark or trademark of Sony Interactive Entertainment Inc.
 
@@ -160,7 +208,7 @@ November 5, 2024
 October 25, 2024
 
 ### Bug fixes
-- Fixed an issue with exposed OpenSSL symbols on the macOS platform. This is a macOS-only release.
+- Fixed an issue with exposed OpenSSL symbols on the macOS platform. This release supports only macOS.
 
 ## 1.7.6
 
@@ -168,9 +216,9 @@ August 12, 2024
 
 ### Bug fixes
 
-- Fixed an issue for GDK Xbox where some events wouldn't be queued after suspending and resuming a title.
+- Fixed an issue for GDK Xbox where some events weren't queued after suspending and resuming a title.
 - Fixed a crash for GDK Xbox after suspending and resuming a title.
-- Updated [PFMultiplayerCreateServerBackfillTicket](../playfabmultiplayerreference-cpp/pfmatchmaking/functions/pfmultiplayercreateserverbackfillticket.md) to automatically handle failures where a match member is already a member of too many tickets. In this situation, the SDK automatically cancels existing tickets for members of the backfill ticket and retry ticket creation.
+- Updated [PFMultiplayerCreateServerBackfillTicket](../playfabmultiplayerreference-cpp/pfmatchmaking/functions/pfmultiplayercreateserverbackfillticket.md) to automatically handle failures when a match member is already a member of too many tickets. In this situation, the SDK automatically cancels existing tickets for members of the backfill ticket and retries ticket creation.
 
 ## 1.7.5
 
@@ -178,7 +226,7 @@ July 17, 2024
 
 ### Bug fixes
 
-- Fixed potential issue with PFMultiplayerUninitialize causing a crash when being used with custom memory hooks on Unix System.
+- Fixed potential issue with PFMultiplayerUninitialize causing a crash when used with custom memory hooks on Unix System.
 
 ## 1.7.4
 
@@ -186,7 +234,7 @@ June 17, 2024
 
 ### Bug fixes
 
-- Fixed an issue where messages received by WebSockets on PlayStation&#174;4 and, PlayStation&#174;5 wouldn't be parsed correctly by the SDK if they contained the `'\0'` character. Failure to parse these messages could lead to PubSub connectivity issues. This is a PlayStation&#174;4 and PlayStation&#174;5 only release.
+- Fixed an issue where the SDK didn't correctly parse messages received by WebSockets on PlayStation®4 and PlayStation®5 if the messages contained the `'\0'` character. Failure to parse these messages could lead to PubSub connectivity problems. This fix applies only to PlayStation®4 and PlayStation®5.
 
 'PlayStation' is a registered trademark or trademark of Sony Interactive Entertainment Inc.
 
@@ -196,7 +244,7 @@ April 23, 2024
 
 ### Bug fixes
 
-- Resolved duplicate class error when Party and Multiplayer are used in the same app. This is an Android only release.
+- Resolved duplicate class error when Party and Multiplayer are used in the same app. This fix applies only to Android.
 
 ## 1.7.2
 
@@ -204,17 +252,17 @@ March 7, 2024
 
 ### Bug fixes
 
-- Fixed an issue where the internal PubSub notification WebSocket was slow to detect and react to disconnections, which could lead to errors to create or join lobbies and matchmaking tickets.
-- Fixed an issue where failure of PubSub to establish connection with the SignalR service wouldn't trigger a failed state change and wouldn't allow subsequent Multiplayer API calls to subscribe to PubSub.
+- Fixed an issue where the internal PubSub notification WebSocket was slow to detect and react to disconnections. This problem could lead to errors when creating or joining lobbies and matchmaking tickets.
+- Fixed an issue where failure of PubSub to establish connection with the SignalR service didn't trigger a failed state change and didn't allow subsequent Multiplayer API calls to subscribe to PubSub.
 - Improved internal diagnostics.
 
 ## 1.7.1
 
 February 14, 2024
 
-### New Features
+### New features
 
-- Added new APIs to enable PlayFab GameServer entities to join and interact with client-owned lobbies:
+- Added new APIs that enable PlayFab GameServer entities to join and interact with client-owned lobbies:
   - [PFMultiplayerJoinLobbyAsServer](../playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerjoinlobbyasserver.md)
   - [PFLobbyServerPostUpdateAsServer](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbyserverpostupdateasserver.md)
   - [PFLobbyServerLeaveAsServer](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbyserverleaveasserver.md)
@@ -227,7 +275,7 @@ February 14, 2024
 
 November 15, 2023
 
-### New Features
+### New features
 
 - Added new [PFMatchmakingTicketGetCustomContext](../playfabmultiplayerreference-cpp/pfmatchmaking/functions/pfmatchmakingticketgetcustomcontext.md) and
 [PFMatchmakingTicketSetCustomContext](../playfabmultiplayerreference-cpp/pfmatchmaking/functions/pfmatchmakingticketsetcustomcontext.md)
@@ -243,7 +291,7 @@ August 16, 2023
 
 ### Bug fixes
 
-- Fixes a bug where the GDK DLL wasn't being codesigned. This is a GDK-only release.
+- Fixed a bug where the GDK DLL wasn't being code-signed. This fix is for a GDK-only release.
 
 ## 1.6.3
 
@@ -251,7 +299,7 @@ August 14, 2023
 
 ### Bug fixes
 
-- Fixed an issue where the library may crash while handling a change notification.
+- Fixed an issue where the library might crash while handling a change notification.
 - Added new [PFLobbyMemberCountRemainingSearchKey](../playfabmultiplayerreference-cpp/pflobby/constants/pflobbysearchkeys.md) constant to make it easier to search for and sort lobbies based on their remaining member counts.
 
 ## 1.6.2
@@ -260,16 +308,16 @@ July 14, 2023
 
 ### Bug fixes
 
-- Fixed an issue where matchmaking operations started by PFMultiplayerJoinMatchmakingTicketFromId timed out prematurely.
-- Fixed an issue where PFMatchmakingTicketGetTicketId could provide a null value if called shortly after starting a matchmaking operation. Now, an empty string is provided as expected.
-- Fixed an issue where the macOS library was identifying as iOS via web request headers. This identification is primarily used for diagnostics.
+- Fixed an issue where matchmaking operations started by `PFMultiplayerJoinMatchmakingTicketFromId` timed out prematurely.
+- Fixed an issue where `PFMatchmakingTicketGetTicketId` could return a null value if called shortly after starting a matchmaking operation. Now, it returns an empty string as expected.
+- Fixed an issue where the macOS library identified as iOS through web request headers. This identification is primarily used for diagnostics.
 - Improved internal diagnostics.
 
 ## 1.6.1
 
 June 14, 2023
 
-- On PlayStation&#174;4 and, PlayStation&#174;5, PlayFab Multiplayer cleans up all resources associated with it and reinitialize if the title enters and remains in background mode for more than 10 minutes.
+- On PlayStation&#174;4 and PlayStation&#174;5, PlayFab Multiplayer cleans up all resources associated with it and reinitializes if the title enters and remains in background mode for more than 10 minutes.
 
 'PlayStation' is a registered trademark or trademark of Sony Interactive Entertainment Inc.
 
@@ -277,9 +325,9 @@ June 14, 2023
 
 June 14, 2023
 
-### New Features
+### New features
 
-- Added a `membershipLock` field to the [PFLobbySearchResult](../playfabmultiplayerreference-cpp/pflobby/structs/pflobbysearchresult.md) struct to enable reading the lock state of the lobbies provided in search results from [PFMultiplayerFindLobbies()](../playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerfindlobbies.md).
+- Added a `membershipLock` field to the [PFLobbySearchResult](../playfabmultiplayerreference-cpp/pflobby/structs/pflobbysearchresult.md) struct so you can read the lock state of the lobbies provided in search results from [PFMultiplayerFindLobbies()](../playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerfindlobbies.md).
 
 ## 1.5.3
 
@@ -287,7 +335,7 @@ April 25, 2023
 
 ### Bug fixes
 
-- Fix a linker error specific to iOS and macOS where HttpClient.framework wouldn't be found during runtime.
+- Fixed a linker error specific to iOS and macOS where HttpClient.framework wasn't found during runtime.
 
 ## 1.5.2
 
@@ -295,7 +343,7 @@ April 4, 2023
 
 ### Bug fixes
 
-- Introduce the PFMultiplayerPal.h header, which provides support for non-MSVC compilers. This header defines SAL and HRESULTs for non-MSVC compiled platforms.
+- Introduced the `PFMultiplayerPal.h` header, which provides support for non-MSVC compilers. This header defines SAL and HRESULTs for non-MSVC compiled platforms.
 
 ## 1.5.1
 
@@ -309,7 +357,7 @@ March 20, 2023
 
 March 16, 2023
 
-### New Features
+### New features
 
 - Added new APIs and support for server-owned lobbies:
     - [PFMultiplayerCreateAndClaimServerLobby](../playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayercreateandclaimserverlobby.md)
@@ -317,13 +365,13 @@ March 16, 2023
     - [PFLobbyServerPostUpdate](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbyserverpostupdate.md)
     - [PFLobbyServerDeleteLobby](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbyserverdeletelobby.md)
 - Added new support for creating matchmaking server backfill tickets with [PFMultiplayerCreateServerBackfillTicket](../playfabmultiplayerreference-cpp/pfmatchmaking/functions/pfmultiplayercreateserverbackfillticket.md).
-- Added new [PFLobbyMembershipLockSearchKey](../playfabmultiplayerreference-cpp/pflobby/constants/pflobbysearchkeys.md) constant to make it easier to search for only locked or unlocked lobbies when calling PFMultiplayerFindLobbies().
+- Added new [PFLobbyMembershipLockSearchKey](../playfabmultiplayerreference-cpp/pflobby/constants/pflobbysearchkeys.md) constant to make it easier to search for only locked or unlocked lobbies when calling `PFMultiplayerFindLobbies()`.
 
 For more information on using server-owned lobbies, see [Game servers and lobbies](../lobby-server-overview.md).
 
 ### Bug fixes
 
-- Mitigation to reduce unexpected PubSub disconnections due to background thread contention
+- Added a fix that reduces unexpected PubSub disconnections due to background thread contention.
 
 ## 1.4.3
 
@@ -347,9 +395,9 @@ October 25, 2022
 
 ### Bug fixes
 
-- Fixed a bug where unnecessary, short-lived threads would spawn.
+- Fixed a bug where the library spawned unnecessary, short-lived threads.
 - On Windows, Xbox, and Android, fixed a bug where the library might attempt web requests before a previously recorded retry-after period expires.
-- Improve the error message if a web server can't be reached.
+- Improved the error message if a web server can't be reached.
 
 ## 1.4.0
 
@@ -357,7 +405,7 @@ October 11, 2022
 
 ### New features
 
-- PlayFab Multiplayer v1.4.0 brings support for Android.
+- PlayFab Multiplayer version 1.4.0 adds support for Android.
 
 ## 1.3.1
 
@@ -365,7 +413,7 @@ September 20, 2022
 
 ### Bug fixes
 
-- Fixed a bug that caused websocket resources to leak memory when [PFMultiplayerUninitialize](../playfabmultiplayerreference-cpp/pfmultiplayer/functions/pfmultiplayeruninitialize.md) was called or when the library internally handled app suspension on Xbox consoles.
+- Fixed a bug that caused WebSocket resources to leak memory when calling [PFMultiplayerUninitialize](../playfabmultiplayerreference-cpp/pfmultiplayer/functions/pfmultiplayeruninitialize.md) or when the library internally handled app suspension on Xbox consoles.
 
 ## 1.3.0
 
@@ -373,8 +421,8 @@ September 9, 2022
 
 ### New features
 
-- Implemented a new function, [PFLobbyGetMemberConnectionStatus](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetmemberconnectionstatus.md), which can be used to detect whether a user is connected to the PubSub notification service. When a user's connection status changes, you receive a [PFLobbyUpdatedStateChange](../playfabmultiplayerreference-cpp/pflobby/structs/pflobbyupdatedstatechange.md) with a [PFLobbyMemberUpdateSummary](../playfabmultiplayerreference-cpp/pflobby/structs/pflobbymemberupdatesummary.md) where the `connectionStatusUpdated` field is `true`.
-- Updated the protocol used to exchange messages with the PubSub notification service from JSON to MessagePack, decreasing the message sizes. This change has no impact on the API surface.
+- Added a new function, [PFLobbyGetMemberConnectionStatus](../playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetmemberconnectionstatus.md), which you can use to detect whether a user is connected to the PubSub notification service. When a user's connection status changes, you receive a [PFLobbyUpdatedStateChange](../playfabmultiplayerreference-cpp/pflobby/structs/pflobbyupdatedstatechange.md) with a [PFLobbyMemberUpdateSummary](../playfabmultiplayerreference-cpp/pflobby/structs/pflobbymemberupdatesummary.md) where the `connectionStatusUpdated` field is `true`.
+- Updated the protocol used to exchange messages with the PubSub notification service from JSON to MessagePack, which decreases the message sizes. This change has no effect on the API surface.
 
 ### Bug fixes
 
@@ -392,7 +440,7 @@ August 17, 2022
 ### Bug fixes
 
 - Improved the message reported by [PFMultiplayerGetErrorCode](../playfabmultiplayerreference-cpp/pfmultiplayer/functions/pfmultiplayergeterrormessage.md) for several error codes.
-- Fixed a bug where entities weren't unsubscribed from the notification service under some failure conditions.
+- Fixed a bug where the notification service didn't unsubscribe entities under some failure conditions.
 
 ## 1.1.5
 
@@ -400,9 +448,9 @@ July 13, 2022
 
 ### Bug fixes
 
-- Fixed incorrect constant string values for PFLobbyMemberCountSearchKey and PFLobbyAmMemberSearchKey in the PFLobby.h header
-- Fixed a bug, which could cause `PFMultiplayerUninitialize()` to block indefinitely if a websocket closes unexpectedly
-- Fixed a bug, which caused PubSub notifications to become unusable and Lobby/Matchmaking API operations to stall out indefinitely after an unexpected websocket disconnect
+- Fixed incorrect constant string values for `PFLobbyMemberCountSearchKey` and `PFLobbyAmMemberSearchKey` in the PFLobby.h header.
+- Fixed a bug that could cause `PFMultiplayerUninitialize()` to block indefinitely if a WebSocket closes unexpectedly.
+- Fixed a bug that caused PubSub notifications to become unusable and Lobby/Matchmaking API operations to stall out indefinitely after an unexpected WebSocket disconnect.
 
 ## 1.1.4
 
@@ -410,8 +458,8 @@ June 24, 2022
 
 ### Bug fixes
 
-- GDK: Fixed a bug where operations involving network communication would silently fail if performed too soon following suspend/resume.
-- Fixed a bug where the SDK crashes when resuming execution after being broken into the debugger for 10+ seconds.
+- GDK: Fixed a bug where operations involving network communication silently failed if the operations started too soon after suspend or resume.
+- Fixed a bug where the SDK crashes when resuming execution after being broken into the debugger for more than 10 seconds.
 
 ## 1.1.3
 
@@ -419,16 +467,16 @@ June 10, 2022
 
 ### New features
 
-- The SDK is now more responsive to unexpected disconnections (detected 2-3x faster than previously).
-- Unexpected Lobby disconnections will now result in automatic reconnect attempts - the disconnect is communicated to the client only after these reconnect attempts fail.
-- GDK/Win32: Web service failure responses (429, 503, etc.) will now result in automatic retries - a failure is communicated to the client only after these retries fail.
+- The SDK is now more responsive to unexpected disconnections (detects them 2-3 times faster than previously).
+- Unexpected Lobby disconnections now result in automatic reconnect attempts. The client learns about the disconnect only after these reconnect attempts fail.
+- GDK/Win32: Web service failure responses (429, 503, and similar responses) now trigger automatic retries. The client learns about the failure only after these retries fail.
 
 ### Bug fixes
 
 - Fixed a bug where matchmaking failed after 10 consecutive matches.
-- Fixed a bug where GetErrorMessage(...) functionality didn't provide error messages related to matchmaking.
-- Fixed a bug where two fields in the LobbySearchResult struct weren't correctly populated (maxMemberCount and currentMemberCount).
-- Fixed various bugs related to behavior/reliability following suspend/resume.
+- Fixed a bug where `GetErrorMessage(...)` didn't provide error messages related to matchmaking.
+- Fixed a bug where two fields in the `LobbySearchResult` struct weren't correctly populated (`maxMemberCount` and `currentMemberCount`).
+- Fixed various bugs related to behavior and reliability following suspend and resume.
 
 ## 1.1.1
 
@@ -444,7 +492,7 @@ March 4, 2022
 
 ### API changes
 
-- PFMultiplayerGetErrorMessage's API signature changed. Previously this function returned an `HRESULT` and used an output parameter to return the error message string. Now the function returns the string directly.
+- Changed `PFMultiplayerGetErrorMessage`'s API signature. Previously, this function returned an `HRESULT` and used an output parameter to return the error message string. Now, the function returns the string directly.
 
 ### New features
 
@@ -452,12 +500,12 @@ March 4, 2022
 
 ### Bug fixes
 
-- Fixed a bug where using initial member data passed to `PFMultiplayerJoinLobby` would be ignored if the player was rejoining a lobby.
+- Fixed a bug where the API ignored initial member data passed to `PFMultiplayerJoinLobby` if the player was rejoining a lobby.
 
 ## 1.0.0
 November 23, 2021
 
-PlayFab Multiplayer is now available in private preview. For an overview of Matchmaking and Lobby features, check out:
+PlayFab Multiplayer is now available in preview. For an overview of Matchmaking and Lobby features, check out:
 
 * [PlayFab Lobby Overview](../index.md)
 * [PlayFab Multiplayer Lobby Quickstart](../lobby-getting-started.md)
diff --git a/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-matchmaking-logging.md b/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-matchmaking-logging.md
index 73b8d1ac2..361af022f 100644
--- a/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-matchmaking-logging.md
+++ b/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-matchmaking-logging.md
@@ -1,7 +1,7 @@
 ---
-title: Diagnostic tracing/logging in Azure PlayFab Lobby and Matchmaking SDKs
+title: Diagnostic tracing/logging in PlayFab Lobby and Matchmaking SDKs
 author: vicodex
-description: Learn about tracing/logging in the SDKs for Azure PlayFab Lobby and Matchmaking.
+description: Learn about tracing/logging in the SDKs for PlayFab Lobby and Matchmaking.
 ms.author: victorku
 ms.date: 10/26/2022
 ms.topic: article
@@ -10,9 +10,9 @@ keywords: playfab, multiplayer, networking, party, sdk, sample
 ms.localizationpriority: medium
 ---
 
-# Tracing/logging instructions for Azure Playfab Lobby and Matchmaking SDKs
+# Tracing/logging instructions for PlayFab Lobby and Matchmaking SDKs
 
-This topic describes how to capture diagnostic traces generated by the Azure PlayFab Lobby and Matchmaking SDKs.
+This topic describes how to capture diagnostic traces generated by the PlayFab Lobby and Matchmaking SDKs.
 
 > [!NOTE]
 > Our SDKs undergo internal testing before every release to ensure the expected level of functionality and normally don't require logging to be enabled by default, particularly in the shipping version of your game.
diff --git a/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-matchmaking-sdks.md b/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-matchmaking-sdks.md
index 6522f75fc..2e2ffc15e 100644
--- a/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-matchmaking-sdks.md
+++ b/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/lobby-matchmaking-sdks.md
@@ -1,7 +1,7 @@
 ---
-title: Azure PlayFab Lobby and Matchmaking SDKs
+title: PlayFab Lobby and Matchmaking SDKs
 author: PushpadantK
-description: Learn about the SDKs for Azure PlayFab Lobby and Matchmaking.
+description: Learn about the SDKs for PlayFab Lobby and Matchmaking.
 ms.author: pkacha
 ms.date: 11/30/2021
 ms.topic: article
@@ -10,9 +10,9 @@ keywords: playfab, multiplayer, matchmaking, lobby, sdk, sample
 ms.localizationpriority: medium
 ---
 
-# Azure Playfab Lobby and Matchmaking SDKs
+# PlayFab Lobby and Matchmaking SDKs
 
-This article describes all the Azure PlayFab Lobby and Matchmaking SDKs that are currently available.
+This article describes all the PlayFab Lobby and Matchmaking SDKs that are currently available.
 
 If you don't find what you need, let us know by writing a post on our [forums](https://community.playfab.com/index.html).
 
diff --git a/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/multiplayer-unity-plugin-quickstart.md b/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/multiplayer-unity-plugin-quickstart.md
index 7ed4a4d36..f24e915e4 100644
--- a/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/multiplayer-unity-plugin-quickstart.md
+++ b/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/multiplayer-unity-plugin-quickstart.md
@@ -22,7 +22,7 @@ This quickstart helps you make your first API calls using the PlayFab Multiplaye
 
 ## Requirements
 
-- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A [PlayFab developer account](https://developer.playfab.com).
 - An installed copy of the Unity Editor. To install Unity for personal use via Unity Hub, or Unity+ for professional use, see [Download Unity](https://unity3d.com/get-unity/download). Check on Unity support in documentation of your specific platform if needed. The minimum supported Unity version is Unity 2017 LTS.
 - A Unity Project – this can be any of the following:
 
diff --git a/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/multiplayer-unity-sdk-getting-started.md b/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/multiplayer-unity-sdk-getting-started.md
index fb24b18cd..310576813 100644
--- a/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/multiplayer-unity-sdk-getting-started.md
+++ b/playfab-docs/multiplayer/lobby/lobby-matchmaking-sdks/multiplayer-unity-sdk-getting-started.md
@@ -1,7 +1,7 @@
 ---
-title: Azure PlayFab Multiplayer getting started for Unity
+title: PlayFab Multiplayer getting started for Unity
 author: victorku
-description: Quickstart for Azure PlayFab Multiplayer Unity plugin.
+description: Quickstart for PlayFab Multiplayer Unity plugin.
 ms.author: victorku
 ms.date: 11/23/2021
 ms.topic: article
diff --git a/playfab-docs/multiplayer/lobby/lobby-properties.md b/playfab-docs/multiplayer/lobby/lobby-properties.md
index a95c413a5..b1fb5f106 100644
--- a/playfab-docs/multiplayer/lobby/lobby-properties.md
+++ b/playfab-docs/multiplayer/lobby/lobby-properties.md
@@ -1,5 +1,5 @@
 ---
-title: Azure PlayFab Lobby custom properties
+title: PlayFab Lobby custom properties
 author: joannaleecy
 description: Learn about custom properties in Lobby.
 ms.author: jenelleb
@@ -15,33 +15,34 @@ ms.localizationpriority: medium
 
 This article describes custom properties stored on the lobby. Use this functionality to store metadata about the game sessions that your lobby's represent.
 
-## Pre-defined properties
+## Predefined properties
 
-Each lobby has a set of pre-defined properties commonly needed for most game scenarios.
+Each lobby has a set of predefined properties commonly needed for most game scenarios.
 
 | Property     | Definition        |
 |--------------|-------------------|
-| lobbyId      | This is the unique identifier for a lobby. It can be used to distinguish between multiple lobbies that a player may be a part of. |
-| connectionString  | The identifier used to join the lobby. It is provided by the Lobby service. When an invite is sent to other players, the __connectionString__ is sent as the invitation. |
+| lobbyId      | This is the unique identifier for a lobby. It can be used to distinguish between multiple lobbies that a player might be a part of. |
+| connectionString  | The identifier used to join the lobby. It's provided by the Lobby service. When an invite is sent to other players, the __connectionString__ is sent as the invitation. |
 | maxMemberCount   | The maximum number of players allowed in the lobby. This property can only be changed by owner. |
-| owner  | The entity that owns the lobby. Some lobbies may temporarily be ownerless in some circumstances. To learn more, see [Ownership changes](ownership-changes.md). |
-| ownerMigrationPolicy | Policy determines how a new owner will be chosen. To learn more, see [Ownership changes](ownership-changes.md). |
+| owner  | The entity that owns the lobby. Some lobbies might be temporarily ownerless in some circumstances. To learn more, see [Ownership changes](ownership-changes.md). |
+| ownerMigrationPolicy | Policy determines how a new owner is chosen. To learn more, see [Ownership changes](ownership-changes.md). |
 | accessPolicy | Policy indicates who can discover the lobby's connection string. This property can only be changed by the owner. |
-| membershipLock  | This value indicates whether new members may join the lobby or not. When __Locked__, new members may not join. When __Unlocked__ new members may join. This property can only be changed by the owner. |
+| membershipLock  | This value indicates whether new members can join the lobby or not. When __Locked__, new members can't join. When __Unlocked__ new members can join. This property can only be changed by the owner. |
+| RestrictInvitesToLobbyOwner  | A setting that controls whether only the lobby owner can send invites to join the lobby. When true, only the lobby owner can send invites. When false or not specified, any member can send invites. Defaults to false if not specified. Restricted to client owned lobbies.|
 
 ## Custom Properties
 
-There are 3 types of custom properties that titles can define. 
+There are three types of custom properties that titles can define. 
 
 1. Custom lobby properties
     * These properties apply to the whole lobby.
     * Only members of the lobby can see these properties.
     * Only the owner of the lobby can change these properties.
 2. Custom member properties
-    * There is a unique map of member properties for each member in the lobby
+    * There's a unique map of member properties for each member in the lobby
     * Only members of the lobby can see these properties.
     * All members of the lobby can see every other members' properties.
-    * Each member may modify their own member properties but cannot modify another member's properties.
+    * Each member may modify their own member properties but can't modify another member's properties.
     * Once a member leaves the lobby, their member properties are deleted from the lobby.
 3. Custom search properties.
     * These are special properties which can be used by all players in your title to search for lobbies matching a specific criteria.
diff --git a/playfab-docs/multiplayer/lobby/lobby-ttl.md b/playfab-docs/multiplayer/lobby/lobby-ttl.md
new file mode 100644
index 000000000..a885c3136
--- /dev/null
+++ b/playfab-docs/multiplayer/lobby/lobby-ttl.md
@@ -0,0 +1,119 @@
+---
+title: Lobby lifetime and expiration
+author: kkline
+description: Learn about the lifetime of lobbies, including how different lobby types and connection states affect lobby expiration.
+ms.author: kkline
+ms.date: 02/27/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, multiplayer, lobby, matchmaking, ttl, lifetime, expiration
+ms.localizationpriority: medium
+---
+
+# Lobby lifetime and expiration
+
+This article explains how lobbies expire and are deleted. Lobby lifetime depends on the lobby type, connection state, and member activity. Understanding these behaviors helps you design your game to avoid unexpected lobby loss and keep search results clean.
+
+## Overview
+
+PlayFab Lobbies are temporary groupings of players. Every lobby has a time to live (TTL) that determines when it will be automatically deleted if left idle. The TTL is reset whenever there's activity on the lobby, such as a member joining, leaving, or updating lobby data.
+
+The two most important factors that determine how long a lobby lives are:
+
+* **Lobby type**: Whether the lobby is client-owned or server-owned.
+* **Connection state**: Whether members (and servers) are connected through real-time notifications.
+
+## Default lobby lifetime
+
+When a lobby is created, it's assigned a default TTL of **1 hour**. Each time the lobby is updated&mdash;through member joins, data updates, or other operations&mdash;the TTL is refreshed back to its full duration.
+
+For lobbies that use real-time notifications (connections), the TTL is extended to **4 hours** when a member connects. This longer TTL accounts for the fact that connected lobbies are actively monitored through the connection system and don't need to expire as quickly.
+
+> [!NOTE]
+> The lobby TTL resets on every lobby operation. A lobby that is actively being used will not expire due to TTL alone.
+
+## How connections affect lobby lifetime
+
+Lobbies that use [real-time notifications](lobby-and-matchmaking-real-time-notifications.md) track member connections. The connection state of members directly impacts the lobby's lifetime and search visibility.
+
+### Connected lobbies
+
+When at least one member is connected to a client-owned lobby, the lobby remains searchable and has a maximum idle TTL of **4 hours**. As long as the lobby continues to receive updates or connection activity, the TTL continues to reset.
+
+### Disconnected lobbies
+
+When all members disconnect from a client-owned lobby, two things happen:
+
+1. **The lobby is hidden from search.** This prevents other players from discovering a lobby that may be abandoned.
+2. **The lobby TTL is reduced to 1 minute.** The lobby enters a brief grace period before deletion.
+
+If a member reconnects during this grace period, the lobby is restored to full visibility and its TTL is extended back to 4 hours.
+
+## Lifetime behavior by lobby type
+
+Client-owned and server-owned lobbies have different expiration behaviors.
+
+### Client-owned lobbies
+
+| Scenario | Behavior |
+|----------|----------|
+| Active with connected members | TTL is 4 hours, reset on each operation. Lobby is searchable. |
+| Active without connections | TTL is 1 hour, reset on each operation. Lobby is searchable. |
+| Owner disconnects | Owner migration is triggered per the __ownerMigrationPolicy__. No direct impact on TTL. |
+| All members disconnect | Lobby is hidden from search. TTL is reduced to 1 minute. |
+| Member reconnects after all disconnected | Lobby becomes searchable again. TTL is restored to 4 hours. |
+| Last member leaves | Lobby is deleted immediately. |
+
+For more information on what happens when an owner disconnects, see [Ownership changes](ownership-changes.md).
+
+### Server-owned lobbies
+
+| Scenario | Behavior |
+|----------|----------|
+| Active with connected server | TTL is 4 hours, reset on each operation. Lobby is searchable. |
+| Active without connections | TTL is 1 hour, reset on each operation. Lobby is searchable. |
+| Server-owner disconnects | Lobby is hidden from search. TTL is unaffected. |
+| Server-owner reconnects | Lobby becomes searchable again. |
+| All members disconnect | No action. The server is not a member, so member disconnections don't affect lobby lifetime. |
+| Server leaves | The server can be replaced by another server claiming ownership. |
+
+> [!IMPORTANT]
+> Server-owned lobbies are not deleted when all player members leave. Only the server owner can delete a server-owned lobby, or it will expire after the TTL runs out.
+
+## Extending lobby lifetime beyond the default TTL
+
+The 4-hour idle TTL is intended to be the maximum ordinary expected time a lobby would be left unattended. However, some scenarios&mdash;such as server-owned lobbies waiting for players to arrive&mdash;may require longer-lived lobbies.
+
+To keep a lobby alive beyond the default TTL, periodically update the lobby before the TTL expires. Any update operation resets the TTL. For example, a game server can update a lobby property at a regular interval to prevent the lobby from expiring.
+
+> [!NOTE]
+> Any lobby operation resets the TTL, including updating lobby properties, member properties, or search properties.
+
+## Search visibility and expiration
+
+Lobby expiration and search visibility are closely related but distinct concepts.
+
+* **Hidden from search** means the lobby won't appear in [FindLobbies](find-lobbies.md) results, but it still exists and can be joined using the connection string.
+* **Deleted** means the lobby no longer exists and can't be accessed.
+
+A lobby may be hidden from search but still alive during the grace period after all members disconnect. This design protects against temporary network disruptions&mdash;if members quickly reconnect, the lobby is restored without any data loss.
+
+## Summary
+
+| Factor | Value |
+|--------|-------|
+| Default TTL (no connections) | 1 hour |
+| Default TTL (with connections) | 4 hours |
+| TTL after all members disconnect (client-owned) | 1 minute before deletion |
+| Client-owned lobby, last member leaves | Deleted immediately |
+| Server-owned lobby, server disconnects | Hidden from search, TTL unaffected |
+| TTL reset trigger | Any lobby operation (join, update, leave) |
+
+## See also
+
+* [Create a lobby](create-a-lobby.md)
+* [Ownership changes](ownership-changes.md)
+* [Game servers and lobbies](lobby-server-overview.md)
+* [Lobby and matchmaking real-time notifications](lobby-and-matchmaking-real-time-notifications.md)
+* [Lobby properties](lobby-properties.md)
+* [Find lobbies](find-lobbies.md)
diff --git a/playfab-docs/multiplayer/lobby/owner-requirements-and-privileges.md b/playfab-docs/multiplayer/lobby/owner-requirements-and-privileges.md
index 301e80a53..751d8bfd5 100644
--- a/playfab-docs/multiplayer/lobby/owner-requirements-and-privileges.md
+++ b/playfab-docs/multiplayer/lobby/owner-requirements-and-privileges.md
@@ -44,6 +44,19 @@ The owner of a lobby has privileges that non-owning members of the lobby don't h
     * In server-owned lobbies, the owner can only assign another server as the new owner.
     * In client-owned lobbies, the owner can only assign another member as the new owner.
 
+## Client-owned lobby access from a game_server
+
+When using a client-owned lobby, you might have the need to securely put data into the lobby from a server. APIs have been added or modified to allow this scenario, so that you can use a 'game_server' entity to join and update the lobby for this purpose. 'ServerData' is similar to 'LobbyData' but it can only be added by a 'game_server' entity. This allows you store important information for other clients to read, such as server connection data, where you can trust the source of the data and even the client lobby owner can't modify it. 
+
+| REST API                                                                                      |  C++ SDK                                                                                                             | Description                         |
+|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|-------------------------------------|
+| [JoinLobbyAsServer](../../../../rest/api/playfab/multiplayer/lobby/join-lobby-as-server)      | [PFMultiplayerJoinLobbyAsServer](playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerjoinlobbyasserver)   | Join a client-owned lobby from a 'game_server'. A lobby owner cannot remove a connected 'game_server', and only one 'game_server' can be joined at a time |
+| [UpdateLobbyAsServer](../../../../rest/api/playfab/multiplayer/lobby/update-lobby-as-server)  | [PFLobbyServerPostUpdateAsServer](playfabmultiplayerreference-cpp/pflobby/functions/pflobbyserverpostupdateasserver) | Update a lobby's ServerData object from a connected 'game_server' |
+| [LeaveLobbyAsServer](../../../../rest/api/playfab/multiplayer/lobby/leave-lobby-as-server)    | [PFLobbyServerLeaveServer](playfabmultiplayerreference-cpp/pflobby/functions/pflobbyserverleaveasserver)             | Leave a client owned lobby from a 'game_server' gracefully, ServerData contents remain |
+| [GetLobby](../../../../rest/api/playfab/multiplayer/lobby/get-lobby)                          | Not necessary, happens on Join                                                                                       | Get a lobby when a 'game_server' is joined to it |
+| [FindLobbies](../../../../rest/api/playfab/multiplayer/lobby/find-lobbies)                    | [PFMultiplayerFindLobbies](playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerfindlobbies)               | Find lobbies that the 'game_server' is associated with |
+ 
+
 ## See also
 
 * [Lobby properties](lobby-properties.md)
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetrestrictinvitestolobbyowner.md b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetrestrictinvitestolobbyowner.md
new file mode 100644
index 000000000..c60bd9670
--- /dev/null
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/functions/pflobbygetrestrictinvitestolobbyowner.md
@@ -0,0 +1,53 @@
+---
+author: ScottMunroMS
+title: "PFLobbyGetRestrictInvitesToLobbyOwner"
+description: "Gets the lobby's current policy for whether only the lobby owner can send invites to join the lobby."
+ms.author: scmunro
+ms.topic: reference
+ms.service: azure-playfab
+ms.date: 03/24/2026
+---
+
+# PFLobbyGetRestrictInvitesToLobbyOwner  
+
+Gets the lobby's current policy for whether only the lobby owner can send invites to join the lobby.  
+
+## Syntax  
+  
+```cpp
+HRESULT PFLobbyGetRestrictInvitesToLobbyOwner(  
+    PFLobbyHandle lobby,  
+    bool* restrictInvitesToLobbyOwner  
+)  
+```  
+  
+### Parameters  
+  
+**`lobby`** &nbsp; PFLobbyHandle  
+  
+The handle of the lobby.  
+  
+**`restrictInvitesToLobbyOwner`** &nbsp; bool*  
+*output*  
+  
+The output value indicating whether the current policy only the lobby owner can send invites to join the lobby.  
+  
+  
+### Return value
+Type: HRESULT
+  
+```S_OK``` if the call succeeded or an error code otherwise. The human-readable form of the error code can be retrieved via [PFMultiplayerGetErrorMessage()](../../pfmultiplayer/functions/pfmultiplayergeterrormessage.md).
+  
+## Remarks  
+  
+When true, only the lobby owner can send invites. When false, any member can send invites. Can only be true for client-owned lobbies. <br /><br /> If this lobby object was created by calling [PFMultiplayerJoinLobby()](pfmultiplayerjoinlobby.md), this method returns an error until [PFMultiplayerStartProcessingLobbyStateChanges()](pfmultiplayerstartprocessinglobbystatechanges.md) provides a [PFLobbyUpdatedStateChange](../structs/pflobbyupdatedstatechange.md) with [PFLobbyUpdatedStateChange::restrictInvitesToLobbyOwnerUpdated](../structs/pflobbyupdatedstatechange.md) set to true. If joining the lobby succeeds, this field is guaranteed to be populated by the time PFMultiplayerStartProcessingLobbyStateChanges() provides a [PFLobbyJoinLobbyCompletedStateChange](../structs/pflobbyjoinlobbycompletedstatechange.md).   <br /><br /> If this lobby object was created by calling [PFMultiplayerClaimServerLobby()](pfmultiplayerclaimserverlobby.md), this method returns an error until [PFMultiplayerStartProcessingLobbyStateChanges()](pfmultiplayerstartprocessinglobbystatechanges.md) provides a [PFLobbyUpdatedStateChange](../structs/pflobbyupdatedstatechange.md) with [PFLobbyUpdatedStateChange::restrictInvitesToLobbyOwnerUpdated](../structs/pflobbyupdatedstatechange.md) set to true. If claiming the lobby succeeds, this field is guaranteed to be populated by the time PFMultiplayerStartProcessingLobbyStateChanges() provides a [PFLobbyClaimServerLobbyCompletedStateChange](../structs/pflobbyclaimserverlobbycompletedstatechange.md).
+  
+## Requirements  
+  
+**Header:** PFLobby.h
+  
+## See also  
+[PFLobby members](../pflobby_members.md)  
+
+  
+  
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerfindlobbies.md b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerfindlobbies.md
index 72f58d7ea..a12fbddd2 100644
--- a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerfindlobbies.md
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerfindlobbies.md
@@ -31,7 +31,7 @@ The handle of the PFMultiplayer API instance.
   
 **`searchingEntity`** &nbsp; [PFEntityKey*](../../pfmultiplayer/pfentitykey_clientsdk.md)  
   
-The playfab entity performing the search.  
+The PlayFab entity performing the search.  
   
 **`searchConfiguration`** &nbsp; [PFLobbySearchConfiguration*](../structs/pflobbysearchconfiguration.md)  
   
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md
index 44b6fd178..319f9759d 100644
--- a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md
@@ -5,7 +5,7 @@ description: "PFMultiplayer C/C++ API overview - PFLobby.h"
 ms.author: scmunro
 ms.topic: reference
 ms.service: azure-playfab
-ms.date: 06/10/2025
+ms.date: 03/24/2026
 ---
 
 # PFMultiplayer C/C++ API overview - PFLobby.h
@@ -31,6 +31,7 @@ ms.date: 06/10/2025
 | [PFLobbyGetMembershipLock](functions/pflobbygetmembershiplock.md) | Gets the lobby's current membership lock state. |  
 | [PFLobbyGetOwner](functions/pflobbygetowner.md) | Gets the current owner of the lobby. |  
 | [PFLobbyGetOwnerMigrationPolicy](functions/pflobbygetownermigrationpolicy.md) | Gets the owner migration policy of the lobby. |  
+| [PFLobbyGetRestrictInvitesToLobbyOwner](functions/pflobbygetrestrictinvitestolobbyowner.md) | Gets the lobby's current policy for whether only the lobby owner can send invites to join the lobby. |  
 | [PFLobbyGetSearchProperty](functions/pflobbygetsearchproperty.md) | Get the search property value from its key. |  
 | [PFLobbyGetSearchPropertyKeys](functions/pflobbygetsearchpropertykeys.md) | Get the list of search property keys. |  
 | [PFLobbyGetServer](functions/pflobbygetserver.md) | Gets the server entity joined to the lobby. |  
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbyarrangedjoinconfiguration.md b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbyarrangedjoinconfiguration.md
index 9488d56cd..35c76d26e 100644
--- a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbyarrangedjoinconfiguration.md
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbyarrangedjoinconfiguration.md
@@ -5,7 +5,7 @@ description: "The initial configuration data used when joining an arranged lobby
 ms.author: scmunro
 ms.topic: reference
 ms.service: azure-playfab
-ms.date: 03/15/2022
+ms.date: 03/24/2026
 ---
 
 # PFLobbyArrangedJoinConfiguration  
@@ -22,6 +22,7 @@ struct PFLobbyArrangedJoinConfiguration {
     uint32_t memberPropertyCount;  
     const char* const* memberPropertyKeys;  
     const char* const* memberPropertyValues;  
+    bool restrictInvitesToLobbyOwner;  
 }  
 ```
   
@@ -61,6 +62,12 @@ The values of the initial member properties for the joiner of the lobby.
   
 Per-member properties are only visible to members of the lobby.
   
+**`restrictInvitesToLobbyOwner`** &nbsp; bool  
+  
+The policy for whether only the lobby owner can send invites to join the lobby.
+  
+When true, only the lobby owner can send invites. When false, any member can send invites. Can only be true for client-owned lobbies.
+  
   
 ## Requirements  
   
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbycreateconfiguration.md b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbycreateconfiguration.md
index 86c086505..318b9a6f3 100644
--- a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbycreateconfiguration.md
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbycreateconfiguration.md
@@ -5,7 +5,7 @@ description: "The initial configuration data used when creating a lobby."
 ms.author: scmunro
 ms.topic: reference
 ms.service: azure-playfab
-ms.date: 02/25/2023
+ms.date: 03/24/2026
 ---
 
 # PFLobbyCreateConfiguration  
@@ -25,6 +25,7 @@ struct PFLobbyCreateConfiguration {
     uint32_t lobbyPropertyCount;  
     const char* const* lobbyPropertyKeys;  
     const char* const* lobbyPropertyValues;  
+    bool restrictInvitesToLobbyOwner;  
 }  
 ```
   
@@ -34,7 +35,7 @@ struct PFLobbyCreateConfiguration {
   
 The maximum number of members allowed in the new lobby.
   
-This value must be at least ```PFLobbyMaxMemberCountLowerLimit``` and no more than ```PFLobbyMaxMemberCountUpperLimit```. <br /><br /> If a client would violate this limit by calling [PFMultiplayerJoinLobby()](../functions/pfmultiplayerjoinlobby.md) or [PFLobbyAddMember](../functions/pflobbyaddmember.md), the operation will fail asynchronously.
+This value must be at least ```PFLobbyMaxMemberCountLowerLimit``` and no more than ```PFLobbyMaxMemberCountUpperLimit```. <br /><br /> If a client would violate this limit by calling [PFMultiplayerJoinLobby()](../functions/pfmultiplayerjoinlobby.md) or [PFLobbyAddMember](../functions/pflobbyaddmember.md), the operation fails asynchronously.
   
 **`ownerMigrationPolicy`** &nbsp; [PFLobbyOwnerMigrationPolicy](../enums/pflobbyownermigrationpolicy.md)  
   
@@ -55,14 +56,14 @@ The number of initial search properties for the new lobby.
   
 The keys of the initial search properties for the new lobby.
   
-Search properties are visible to non-members of the lobby as metadata which can be used to filter and sort lobby search results. <br /><br /> Search properties must be of the form string_keyN or number_keyN where "N" is a number between 1 and ```PFLobbyMaxSearchPropertyCount```. e.g. string_key1, number_key14, etc. <br /><br />
+Search properties are visible to non-members of the lobby as metadata, which can be used to filter and sort lobby search results. <br /><br /> Search properties must be of the form string_keyN or number_keyN where "N" is a number between 1 and ```PFLobbyMaxSearchPropertyCount```. e.g., string_key1, number_key14, etc. <br /><br />
   
 **`searchPropertyValues`** &nbsp; const char* const*  
 *array of size `searchPropertyCount`*  
   
 The values of the initial search properties for the new lobby.
   
-Search properties are visible to non-members of the lobby as metadata which can be used to filter and sort lobby search results.
+Search properties are visible to non-members of the lobby as metadata, which can be used to filter and sort lobby search results.
   
 **`lobbyPropertyCount`** &nbsp; uint32_t  
   
@@ -82,6 +83,12 @@ The values of the initial lobby properties for the new lobby.
   
 Lobby properties are only visible to members of the lobby.
   
+**`restrictInvitesToLobbyOwner`** &nbsp; bool  
+  
+The policy for whether only the lobby owner can send invites to join the lobby.
+  
+When true, only the lobby owner can send invites. When false, any member can send invites. Can only be true for client-owned lobbies.
+  
   
 ## Requirements  
   
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbydataupdate.md b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbydataupdate.md
index b31d928ff..ecbae3a83 100644
--- a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbydataupdate.md
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbydataupdate.md
@@ -5,7 +5,7 @@ description: "A request to make an update to the shared portion of the lobby."
 ms.author: scmunro
 ms.topic: reference
 ms.service: azure-playfab
-ms.date: 02/25/2023
+ms.date: 03/24/2026
 ---
 
 # PFLobbyDataUpdate  
@@ -26,6 +26,7 @@ struct PFLobbyDataUpdate {
     uint32_t lobbyPropertyCount;  
     const char* const* lobbyPropertyKeys;  
     const char* const* lobbyPropertyValues;  
+    const bool* restrictInvitesToLobbyOwner;  
 }  
 ```
   
@@ -46,7 +47,7 @@ This value can only be updated under one of the following conditions:
   
 An optional, updated capacity for the number of members in this lobby.
   
-This new value must be greater than than the number of members currently in the lobby and less than ```PFLobbyMaxMemberCountUpperLimit```. <br /><br /> This value can only be updated by the current lobby owner.
+This new value must be greater than the number of members currently in the lobby and less than ```PFLobbyMaxMemberCountUpperLimit```. <br /><br /> This value can only be updated by the current lobby owner.
   
 **`accessPolicy`** &nbsp; const [PFLobbyAccessPolicy](../enums/pflobbyaccesspolicy.md)*  
 *may be nullptr*  
@@ -66,34 +67,34 @@ This value can only be updated by the current lobby owner.
   
 The number of search properties to update.
   
-Only the current lobby owner can update the search properties. <br /><br /> There may only be ```PFLobbyMaxSearchPropertyCount``` concurrent search properties at any given time. Therefore, at most, twice that many unique properties can be specified in this update if half of those properties are being deleted.   <br /><br /> If the property limits are violated, the entire update operation will fail.
+Only the current lobby owner can update the search properties. <br /><br /> There may only be ```PFLobbyMaxSearchPropertyCount``` concurrent search properties at any given time. Therefore, at most, twice that many unique properties can be specified in this update if half of those properties are being deleted.   <br /><br /> If the property limits are violated, the entire update operation fails.
   
 **`searchPropertyKeys`** &nbsp; const char* const*  
 *array of size `searchPropertyCount`*  
   
 The keys of the search properties to update.
   
-Only the current lobby owner can update the lobby properties. <br /><br /> Search properties are visible to non-members of the lobby as metadata which can be used to filter and sort lobby search results.   <br /><br /> Only the properties specified in this list of keys will be updated. If the key doesn't exist yet, the property will be created. If the new property value is nullptr, the property will be deleted. Any existing properties omitted from this list will be left unmodified.   <br /><br /> Search properties must be of the form string_keyN or number_keyN where "N" is a number between 1 and ```PFLobbyMaxSearchPropertyCount```. e.g. string_key1, number_key14, etc. <br /><br />
+Only the current lobby owner can update the lobby properties. <br /><br /> Search properties are visible to non-members of the lobby as metadata, which can be used to filter and sort lobby search results.   <br /><br /> Only the properties specified in this list of keys will be updated. If the key doesn't exist yet, the property is created. If the new property value is nullptr, the property is deleted. Any existing properties omitted from this list will be left unmodified.   <br /><br /> Search properties must be of the form string_keyN or number_keyN where "N" is a number between 1 and ```PFLobbyMaxSearchPropertyCount```. e.g., string_key1, number_key14, etc. <br /><br />
   
 **`searchPropertyValues`** &nbsp; const char* const*  
 *array of size `searchPropertyCount`*  
   
 The values of the search properties to update.
   
-Only the current lobby owner can update the search properties. <br /><br /> Search properties are visible to non-members of the lobby as metadata which can be used to filter and sort lobby search results.   <br /><br /> To delete a value, provide nullptr as its new value.
+Only the current lobby owner can update the search properties. <br /><br /> Search properties are visible to non-members of the lobby as metadata, which can be used to filter and sort lobby search results.   <br /><br /> To delete a value, provide nullptr as its new value.
   
 **`lobbyPropertyCount`** &nbsp; uint32_t  
   
 The number of lobby properties to update.
   
-Only the current lobby owner can update the lobby properties. <br /><br /> There may only be ```PFLobbyMaxLobbyPropertyCount``` concurrent lobby properties at any given time. Therefore, at most, twice that many unique properties can be specified in this update if half of those properties are being deleted.   <br /><br /> If the property limits are violated, the entire update operation will fail.
+Only the current lobby owner can update the lobby properties. <br /><br /> There may only be ```PFLobbyMaxLobbyPropertyCount``` concurrent lobby properties at any given time. Therefore, at most, twice that many unique properties can be specified in this update if half of those properties are being deleted.   <br /><br /> If the property limits are violated, the entire update operation fails.
   
 **`lobbyPropertyKeys`** &nbsp; const char* const*  
 *array of size `lobbyPropertyCount`*  
   
 The keys of the lobby properties to update.
   
-Only the current lobby owner can update the lobby properties. <br /><br /> Lobby properties are only visible to members of the lobby.   <br /><br /> Only the properties specified in this list of keys will be updated. If the key doesn't exist yet, the property will be created. If the new property value is nullptr, the property will be deleted. Any existing properties omitted from this list will be left unmodified.
+Only the current lobby owner can update the lobby properties. <br /><br /> Lobby properties are only visible to members of the lobby.   <br /><br /> Only the properties specified in this list of keys will be updated. If the key doesn't exist yet, the property is created. If the new property value is nullptr, the property is deleted. Any existing properties omitted from this list will be left unmodified.
   
 **`lobbyPropertyValues`** &nbsp; const char* const*  
 *array of size `lobbyPropertyCount`*  
@@ -102,6 +103,13 @@ The values of the lobby properties to update.
   
 Only the current lobby owner can update the lobby properties. <br /><br /> Lobby properties are only visible to members of the lobby.   <br /><br /> To delete a value, provide nullptr as its new value.
   
+**`restrictInvitesToLobbyOwner`** &nbsp; const bool*  
+*may be nullptr*  
+  
+An optional update to the policy for whether only the lobby owner can send invites to join the lobby.
+  
+When true, only the lobby owner can send invites. When false, any member can send invites. Can only be true for client-owned lobbies.
+  
 ## Remarks  
   
 Most data in the shared portion of the lobby can only be updated by the owner. Check the documentation for each field for confirmation.
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbyupdatedstatechange.md b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbyupdatedstatechange.md
index 2c3e58549..b302618b3 100644
--- a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbyupdatedstatechange.md
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/structs/pflobbyupdatedstatechange.md
@@ -5,7 +5,7 @@ description: "Information specific to the *Updated* type of state change."
 ms.author: scmunro
 ms.topic: reference
 ms.service: azure-playfab
-ms.date: 02/14/2024
+ms.date: 03/24/2026
 ---
 
 # PFLobbyUpdatedStateChange  
@@ -31,6 +31,7 @@ struct PFLobbyUpdatedStateChange : PFLobbyStateChange {
     uint32_t updatedServerPropertyCount;  
     const char* const* updatedServerPropertyKeys;  
     bool serverConnectionStatusUpdated;  
+    bool restrictInvitesToLobbyOwnerUpdated;  
 }  
 ```
   
@@ -101,6 +102,10 @@ The keys of properties that updated for a client-owned lobby's joined server.
   
 A flag indicating whether the lobby server's connection status changed.
   
+**`restrictInvitesToLobbyOwnerUpdated`** &nbsp; bool  
+  
+A flag indicating if the lobby's policy for restricting invites to the lobby owner changed.
+  
 ## Remarks  
   
 This state change signifies that the lobby is updated and provides hints as to which values have changed. Multiple updates may be provided by a single call to [PFMultiplayerStartProcessingLobbyStateChanges()](../functions/pfmultiplayerstartprocessinglobbystatechanges.md). All state reflected by these updates become available simultaneously when PFMultiplayerStartProcessingLobbyStateChanges() is called, so the updates can be reconciled either individually or as a batch.
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md
index 0fba0672e..4e032f1ff 100644
--- a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md
@@ -36,8 +36,8 @@ ms.date: 11/15/2023
 | [PFMatchmakingMatchMember](structs/pfmatchmakingmatchmember.md) | A member of a match result. |  
 | [PFMatchmakingServerBackfillTicketConfiguration](structs/pfmatchmakingserverbackfillticketconfiguration.md) | Defines the configuration for a server backfill ticket. |  
 | [PFMatchmakingTicketConfiguration](structs/pfmatchmakingticketconfiguration.md) | Defines the configuration for a matchmaking ticket. |  
-| [PFMultiplayerPort](structs/pfmultiplayerport.md) | A port used by a Playfab Multiplayer Server. |  
-| [PFMultiplayerServerDetails](structs/pfmultiplayerserverdetails.md) | Details about a Playfab Multiplayer Server. |  
+| [PFMultiplayerPort](structs/pfmultiplayerport.md) | A port used by a PlayFab Multiplayer Server. |  
+| [PFMultiplayerServerDetails](structs/pfmultiplayerserverdetails.md) | Details about a PlayFab Multiplayer Server. |  
   
 ## State changes  
   
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/structs/pfmultiplayerport.md b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/structs/pfmultiplayerport.md
index dd5e35fc2..0d3b802e3 100644
--- a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/structs/pfmultiplayerport.md
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/structs/pfmultiplayerport.md
@@ -1,7 +1,7 @@
 ---
 author: ScottMunroMS
 title: "PFMultiplayerPort"
-description: "A port used by a Playfab Multiplayer Server."
+description: "A port used by a PlayFab Multiplayer Server."
 ms.author: scmunro
 ms.topic: reference
 ms.service: azure-playfab
@@ -10,7 +10,7 @@ ms.date: 08/16/2022
 
 # PFMultiplayerPort  
 
-A port used by a Playfab Multiplayer Server.  
+A port used by a PlayFab Multiplayer Server.  
 
 ## Syntax  
   
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/structs/pfmultiplayerserverdetails.md b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/structs/pfmultiplayerserverdetails.md
index 5fc72cf74..90bed0ce8 100644
--- a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/structs/pfmultiplayerserverdetails.md
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmatchmaking/structs/pfmultiplayerserverdetails.md
@@ -1,7 +1,7 @@
 ---
 author: ScottMunroMS
 title: "PFMultiplayerServerDetails"
-description: "Details about a Playfab Multiplayer Server."
+description: "Details about a PlayFab Multiplayer Server."
 ms.author: scmunro
 ms.topic: reference
 ms.service: azure-playfab
@@ -10,7 +10,7 @@ ms.date: 08/16/2022
 
 # PFMultiplayerServerDetails  
 
-Details about a Playfab Multiplayer Server.  
+Details about a PlayFab Multiplayer Server.  
 
 ## Syntax  
   
@@ -29,12 +29,12 @@ struct PFMultiplayerServerDetails {
 **`fqdn`** &nbsp; const char*  
 *is null-terminated*  
   
-The fully qualified domain name of the virtual machine that is hosting this multiplayer server.
+The fully qualified domain name of the virtual machine that's hosting this multiplayer server.
   
 **`ipv4Address`** &nbsp; const char*  
 *is null-terminated*  
   
-The IPv4 address of the virtual machine that is hosting this multiplayer server.
+The IPv4 address of the virtual machine that's hosting this multiplayer server.
   
 **`ports`** &nbsp; const [PFMultiplayerPort](pfmultiplayerport.md)*  
   
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmultiplayererrors.md b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmultiplayererrors.md
index 88accee13..224b754f5 100644
--- a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmultiplayererrors.md
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/pfmultiplayererrors.md
@@ -1,11 +1,11 @@
 ---
 author: ScottMunroMS
 title: "PlayFab Multiplayer C++ SDK Error Codes"
-description: "Error codes used by the PlayFab Multiplayer, Lobby and Matchmaking APIs"
+description: "Error codes used by the PlayFab Multiplayer, Lobby, and Matchmaking APIs"
 ms.author: scmunro
 ms.topic: reference
 ms.service: azure-playfab
-ms.date: 08/19/2022
+ms.date: 02/13/2026
 ---
 
 # PlayFab Multiplayer C++ SDK Error Codes
@@ -15,110 +15,166 @@ The following error codes are used by the PlayFab Multiplayer, Lobby and Matchma
 For additional guidance on handling these errors, check out [Handling Lobby and Matchmaking C++ SDK errors](../lobby-and-matchmaking-client-sdk-errors.md)
 
 ### Multiplayer
+
 | Hex | Dec | Description |
 | ------ | ------ | ------ |
-|	0x89236400	|	-1994169344	|	The PlayFabMultiplayer library must be initialized.	|
-|	0x89236401	|	-1994169343	|	Only one PlayFabMultiplayer instance can exist at a time.	|
-|	0x89236402	|	-1994169342	|	No PlayFab entity token was associated with the provided entity key. Use PFMultiplayerSetEntityToken to associate a PlayFab entity token with a PlayFab entity key before passing that entity key to the API.	|
-|	0x89236403	|	-1994169341	|	The provided multiplayer thread ID is invalid/unknown.	|
-|	0x89236404	|	-1994169340	|	The provided PlayFab entity key is malformed or otherwise invalid.	|
-|	0x89236405	|	-1994169339	|	The Microsoft Game Core XNetworking feature is unavailable	|
-|	0x89236406	|	-1994169338	|	The PlayFab Multiplayer library couldn't be initialized because the Game Core Network stack wasn't initialized. Use the Microsoft Game Core XNetworkingGetConnectivityHint API to determine when the network stack is initialized.	|
-|	0x89236408	|	-1994169336	|	The operation was canceled due to the title suspending.	|
-|	0x89236409	|	-1994169335	|	The PlayFab service returned an unexpected error with a 4XX status code.	|
-|	0x8923640A	|	-1994169334	|	The PlayFab service returned an unexpected error with a 5XX status code.	|
-|	0x8923640B	|	-1994169333	|	The Entity ID is invalid.	|
-|	0x8923640C	|	-1994169332	|	The Entity Type is invalid or unsupported.	|
-|	0x8923640D	|	-1994169331	|	A request rate limit was exceeded. The request wasn't automatically retried again because retries are disabled or the retry-after period was too long.	|
+| 0x89236400 | -1994169344 | The PlayFabMultiplayer library must be initialized. |
+| 0x89236401 | -1994169343 | Only one PlayFabMultiplayer instance can exist at a time. |
+| 0x89236402 | -1994169342 | No PlayFab entity token was associated with the provided entity key. Use PFMultiplayerSetEntityToken to associate a PlayFab entity token with a PlayFab entity key before passing that entity key to the API. |
+| 0x89236403 | -1994169341 | The provided multiplayer thread ID is invalid/unknown. |
+| 0x89236404 | -1994169340 | The provided PlayFab entity key is malformed or otherwise invalid. |
+| 0x89236405 | -1994169339 | The Microsoft Game Core XNetworking feature is unavailable. |
+| 0x89236406 | -1994169338 | The PlayFab Multiplayer library couldn't be initialized because the Game Core Network stack wasn't initialized. Use the Microsoft Game Core XNetworkingGetConnectivityHint API to determine when the network stack is initialized. |
+| 0x89236408 | -1994169336 | The operation was canceled due to the title suspending. |
+| 0x89236409 | -1994169335 | The PlayFab service returned an unexpected error with a 4XX status code. |
+| 0x8923640A | -1994169334 | The PlayFab service returned an unexpected error with a 5XX status code. |
+| 0x8923640B | -1994169333 | The Entity ID is invalid. |
+| 0x8923640C | -1994169332 | The Entity Type is invalid or unsupported. |
+| 0x8923640D | -1994169331 | A request rate limit was exceeded. The request wasn't automatically retried again because retries are disabled or the retry-after period was too long. |
 
 ### Lobby
+
 | Hex | Dec | Description |
 | ------ | ------ | ------ |
-|	0x89236200	|	-1994169856	|	Can't create local user; local user limit reached.	|
-|	0x89236202	|	-1994169854	|	A user with the provided entity ID already exists.	|
-|	0x89236203	|	-1994169853	|	Requested, provided, or configured Lobby owner migration policy is invalid.	|
-|	0x89236204	|	-1994169852	|	Requested, provided, or configured Lobby access policy is invalid.	|
-|	0x89236205	|	-1994169851	|	Requested object is still pending asynchronous creation.	|
-|	0x89236206	|	-1994169850	|	The provided max member count value is outside of the allowed range of values.	|
-|	0x89236207	|	-1994169849	|	Provided lobby property count exceeds maximum allowed.	|
-|	0x89236208	|	-1994169848	|	Encountered an unexpected error.	|
-|	0x89236209	|	-1994169847	|	Failed to parse json data.	|
-|	0x8923620B	|	-1994169845	|	A parameter or value provided to the PlayFab service was invalid.	|
-|	0x8923620C	|	-1994169844	|	An unexpected error code was returned by the PlayFab service.	|
-|	0x8923620D	|	-1994169843	|	The provided entity token has expired.	|
-|	0x8923620E	|	-1994169842	|	The user isn't authorized to execute the operation.	|
-|	0x89236212	|	-1994169838	|	An unknown error code was returned by the PlayFab service.	|
-|	0x89236213	|	-1994169837	|	The PlayFab entity token is malformed or otherwise invalid.	|
-|	0x89236214	|	-1994169836	|	The specified Lobby entity ID is invalid.	|
-|	0x89236215	|	-1994169835	|	The provided property bag contains duplicate property keys.	|
-|	0x89236216	|	-1994169834	|	A Lobby request rate limit was exceeded. The request wasn't automatically retried again because retries are disabled or the retry-after period was too long.	|
-|	0x89236217	|	-1994169833	|	The owner of the lobby isn't a member of the lobby.	|
-|	0x8923621A	|	-1994169830	|	The operation couldn't be completed because the entity provided wasn't locally authenticated. Log in the entity first and provide the library a token using SetEntityToken.	|
-|	0x8923621B	|	-1994169829	|	The provided Lobby state change type is invalid/unknown.	|
-|	0x8923621C	|	-1994169828	|	The provided Lobby state change result is invalid/unknown.	|
-|	0x8923621D	|	-1994169827	|	The provided Lobby disconnect reason is invalid/unknown.	|
-|	0x8923621E	|	-1994169826	|	The PlayFab service returned unexpected 'bad request' error.	|
-|	0x8923621F	|	-1994169825	|	The provided Lobby thread ID is invalid/unknown.	|
-|	0x89236220	|	-1994169824	|	The operation couldn't be completed because the entity provided wasn't a member of the lobby.	|
-|	0x89236221	|	-1994169823	|	The PlayFab service returned an invalid/malformed response.	|
-|	0x89236222	|	-1994169822	|	Either a lobby update or a member update must be provided.	|
-|	0x89236223	|	-1994169821	|	Updates can't be queued after disconnecting from the lobby.	|
-|	0x89236224	|	-1994169820	|	The provided lobby join request contained an invalid property deletion.	|
-|	0x89236225	|	-1994169819	|	The requested user was already a member of the lobby.	|
-|	0x89236226	|	-1994169818	|	The requested lobby doesn't exist.	|
-|	0x89236227	|	-1994169817	|	The requested lobby wasn't in a joinable state.	|
-|	0x89236228	|	-1994169816	|	The provided Lobby member removed reason is invalid/unknown.	|
-|	0x89236229	|	-1994169815	|	The operation couldn't be completed because the acting member wasn't the owner.	|
-|	0x8923622A	|	-1994169814	|	Lobby member can't self-promote to owner while owner is still connected using current owner migration policy.	|
-|	0x8923622B	|	-1994169813	|	The arrangement string version isn't supported.	|
-|	0x8923622C	|	-1994169812	|	An arrangement string for the specified entity key wasn't found in the packed arrangement string.	|
-|	0x8923622D	|	-1994169811	|	The arrangement string is an invalid format and couldn't be parsed.	|
-|	0x8923622E	|	-1994169810	|	Requested, provided, or configured Lobby invite listener status is invalid.	|
-|	0x8923622F	|	-1994169809	|	The invite listener is already set and must be stopped before resetting.	|
-|	0x89236230	|	-1994169808	|	The invite listener isn't set and so can't be stopped.	|
-|	0x89236231	|	-1994169807	|	Requested,  provided,  or configured Lobby membership lock is invalid.	|
-|	0x89236232	|	-1994169806	|	The member can't rejoin the lobby because they have been banned.	|
-|	0x89236233	|	-1994169805	|	The member can't join the lobby because they are already concurrently a member of the maximum number of allowed lobbies.	|
-|	0x89236234	|	-1994169804	|	The owner can't promote disconnected member to owner if owner migration policy is Automatic.	|
-|	0x89236235	|	-1994169803	|	The connection status is invalid.	|
+| 0x89236200 | -1994169856 | Can't create local user; local user limit reached. |
+| 0x89236202 | -1994169854 | A user with the provided entity ID already exists. |
+| 0x89236203 | -1994169853 | Requested, provided, or configured Lobby owner migration policy is invalid. |
+| 0x89236204 | -1994169852 | Requested, provided, or configured Lobby access policy is invalid. |
+| 0x89236205 | -1994169851 | Requested object is still pending asynchronous creation. |
+| 0x89236206 | -1994169850 | The provided max member count value is outside of the allowed range of values. |
+| 0x89236207 | -1994169849 | Provided lobby property count exceeds maximum allowed. |
+| 0x89236208 | -1994169848 | Encountered an unexpected error. |
+| 0x89236209 | -1994169847 | Failed to parse json data. |
+| 0x8923620B | -1994169845 | A parameter or value provided to the PlayFab service was invalid. |
+| 0x8923620C | -1994169844 | The PlayFab service returned an unexpected error. |
+| 0x8923620D | -1994169843 | The provided entity token has expired. |
+| 0x8923620E | -1994169842 | The user isn't authorized to execute the operation. |
+| 0x89236212 | -1994169838 | The PlayFab Service returned an unknown error. |
+| 0x89236213 | -1994169837 | The PlayFab entity token is malformed or otherwise invalid. |
+| 0x89236214 | -1994169836 | The specified Lobby entity ID is invalid. |
+| 0x89236215 | -1994169835 | The provided property bag contains duplicate property keys. |
+| 0x89236216 | -1994169834 | A Lobby request rate limit was exceeded. The request wasn't automatically retried again because retries are disabled or the retry-after period was too long. |
+| 0x89236217 | -1994169833 | The owner of the lobby isn't a member of the lobby. |
+| 0x8923621A | -1994169830 | The operation couldn't be completed because the entity provided wasn't locally authenticated. Log in the entity first, and provide the library a token using SetEntityToken. |
+| 0x8923621B | -1994169829 | The provided Lobby state change type is invalid/unknown. |
+| 0x8923621C | -1994169828 | The provided Lobby state change result is invalid/unknown. |
+| 0x8923621D | -1994169827 | The provided Lobby disconnect reason is invalid/unknown. |
+| 0x8923621E | -1994169826 | The PlayFab service returned unexpected 'bad request' error. |
+| 0x8923621F | -1994169825 | The provided Lobby thread ID is invalid/unknown. |
+| 0x89236220 | -1994169824 | The operation couldn't be completed because the entity provided wasn't a member of the lobby. |
+| 0x89236221 | -1994169823 | The PlayFab service returned an invalid/malformed response. |
+| 0x89236222 | -1994169822 | Either a lobby update or a member update must be provided. |
+| 0x89236223 | -1994169821 | Updates can't be queued after disconnecting from the lobby. |
+| 0x89236224 | -1994169820 | The provided lobby join request contained an invalid property deletion. |
+| 0x89236225 | -1994169819 | The requested user was already a member of the lobby. |
+| 0x89236226 | -1994169818 | The requested lobby doesn't exist. |
+| 0x89236227 | -1994169817 | The requested lobby wasn't in a joinable state. |
+| 0x89236228 | -1994169816 | The provided Lobby member removed reason is invalid/unknown. |
+| 0x89236229 | -1994169815 | The operation couldn't be completed because the acting member wasn't the owner. |
+| 0x8923622A | -1994169814 | Lobby member can't self-promote to owner while owner is still connected using current owner migration policy. |
+| 0x8923622B | -1994169813 | The arrangement string version isn't supported. |
+| 0x8923622C | -1994169812 | An arrangement string for the specified entity key wasn't found in the packed arrangement string. |
+| 0x8923622D | -1994169811 | The arrangement string is an invalid format and couldn't be parsed. |
+| 0x8923622E | -1994169810 | Requested, provided, or configured Lobby invite listener status is invalid. |
+| 0x8923622F | -1994169809 | The invite listener is already set and must be stopped before resetting. |
+| 0x89236230 | -1994169808 | The invite listener isn't set and so can't be stopped. |
+| 0x89236231 | -1994169807 | Requested, provided, or configured Lobby membership lock is invalid. |
+| 0x89236232 | -1994169806 | The member can't rejoin the lobby because they have been banned. |
+| 0x89236233 | -1994169805 | The member can't join the lobby because they are already concurrently a member of the maximum number of allowed lobbies. |
+| 0x89236234 | -1994169804 | The owner can't promote disconnected member to owner if owner migration policy is Automatic. |
+| 0x89236235 | -1994169803 | The connection status is invalid. |
+| 0x89236236 | -1994169802 | Operation can only be performed by the lobby's server-owner. |
+| 0x89236237 | -1994169801 | The specified calling server hasn't joined the lobby. The lobby has a different server joined. |
+| 0x89236238 | -1994169800 | The lobby doesn't have a joined server. |
+| 0x89236239 | -1994169799 | The lobby already has a joined server. |
+| 0x8923623A | -1994169798 | The server has already joined the lobby. |
+| 0x8923623B | -1994169797 | The server can't join a lobby which isn't client-owned. |
+| 0x8923623C | -1994169796 | The server can't join a lobby which doesn't use connections. |
+| 0x8923623D | -1994169795 | Operation can only be performed by the non-owning server associated with the lobby. |
+| 0x8923623E | -1994169794 | The connection status is invalid. |
 
 ### Matchmaking
+
+| Hex | Dec | Description |
+| ------ | ------ | ------ |
+| 0x89236300 | -1994169600 | The provided matchmaking ticket status is invalid/unknown. |
+| 0x89236301 | -1994169599 | The provided matchmaking ticket result is invalid/unknown. |
+| 0x89236302 | -1994169598 | The provided matchmaking ticket cancel reason is invalid/unknown. |
+| 0x89236303 | -1994169597 | The provided matchmaking state change type is invalid/unknown. |
+| 0x89236304 | -1994169596 | The ticket was canceled due to a cancelation request. |
+| 0x89236305 | -1994169595 | The ticket was canceled due to a service error. |
+| 0x89236306 | -1994169594 | The ticket was canceled because the timeout elapsed before a match could be found. |
+| 0x89236307 | -1994169593 | The ticket was canceled for an unknown reason. |
+| 0x89236308 | -1994169592 | Duplicate users aren't allowed in the ticket parameters. |
+| 0x89236309 | -1994169591 | At least one local user must be specified in the ticket parameters. |
+| 0x8923630A | -1994169590 | There were too many users in the ticket for the queue. |
+| 0x8923630B | -1994169589 | The ticket is already completed. |
+| 0x8923630C | -1994169588 | Encountered an unrecoverable failure when attempting to cancel the ticket. |
+| 0x8923630D | -1994169587 | One of the users is a member of too many tickets. |
+| 0x8923630F | -1994169585 | A matchmaking request rate limit was exceeded. The request wasn't automatically retried again because retries are disabled or the retry-after period was too long. |
+| 0x89236310 | -1994169584 | The timeout elapsed without the service completing the ticket. |
+| 0x89236311 | -1994169583 | The calling entity is invalid. |
+| 0x89236312 | -1994169582 | One of the users in the ticket has invalid attributes. |
+| 0x89236313 | -1994169581 | The queue wasn't found. |
+| 0x89236314 | -1994169580 | The match wasn't found. |
+| 0x89236315 | -1994169579 | The ticket wasn't found. |
+| 0x89236316 | -1994169578 | The user already joined the ticket. |
+| 0x89236317 | -1994169577 | The queue config is invalid. |
+| 0x89236318 | -1994169576 | One of the users in the ticket has an invalid entity profile. |
+| 0x89236319 | -1994169575 | Matchmaking isn't enabled for this title. |
+| 0x8923631A | -1994169574 | One of the users in the ticket has attributes that are too large. |
+| 0x8923631B | -1994169573 | One of the ticket attributes is invalid. |
+| 0x8923631C | -1994169572 | The user hasn't joined the ticket. |
+| 0x8923631D | -1994169571 | The number of queues has exceeded the limit for this title. |
+| 0x8923631E | -1994169570 | The API called doesn't match the type of ticket requested. |
+| 0x8923631F | -1994169569 | The request was malformed. |
+| 0x89236320 | -1994169568 | Match details can only be provided when the ticket is in the matched state. |
+| 0x89236321 | -1994169567 | The provided multiplayer protocol type is invalid. |
+| 0x89236322 | -1994169566 | The ticket was canceled by the service. |
+
+### PubSub
+
 | Hex | Dec | Description |
 | ------ | ------ | ------ |
-|	0x89236300	|	-1994169600	|	The provided matchmaking ticket status is invalid/unknown.	|
-|	0x89236301	|	-1994169599	|	The provided matchmaking ticket result is invalid/unknown.	|
-|	0x89236302	|	-1994169598	|	The provided matchmaking ticket cancel reason is invalid/unknown.	|
-|	0x89236303	|	-1994169597	|	The provided matchmaking state change type is invalid/unknown.	|
-|	0x89236304	|	-1994169596	|	The ticket was canceled due to a cancelation request.	|
-|	0x89236305	|	-1994169595	|	The ticket was canceled due to a service error.	|
-|	0x89236306	|	-1994169594	|	The ticket was canceled because the timeout elapsed before a match could be found.	|
-|	0x89236307	|	-1994169593	|	The ticket was canceled for an unknown reason.	|
-|	0x89236308	|	-1994169592	|	Duplicate users aren't allowed in the ticket parameters.	|
-|	0x89236309	|	-1994169591	|	At least one local user must be specified in the ticket parameters.	|
-|	0x8923630A	|	-1994169590	|	There were too many users in the ticket for the queue.	|
-|	0x8923630B	|	-1994169589	|	The ticket is already completed.	|
-|	0x8923630C	|	-1994169588	|	Encountered an unrecoverable failure when attempting to cancel the ticket.	|
-|	0x8923630D	|	-1994169587	|	One of the users is a member of too many tickets.	|
-|	0x8923630F	|	-1994169585	|	A matchmaking request rate limit was exceeded. The request wasn't automatically retried again because retries are disabled or the retry-after period was too long.	|
-|	0x89236310	|	-1994169584	|	The timeout elapsed without the service completing the ticket.	|
-|	0x89236311	|	-1994169583	|	The calling entity is invalid.	|
-|	0x89236312	|	-1994169582	|	One of the users in the ticket has invalid attributes.	|
-|	0x89236313	|	-1994169581	|	The queue wasn't found.	|
-|	0x89236314	|	-1994169580	|	The match wasn't found.	|
-|	0x89236315	|	-1994169579	|	The ticket wasn't found.	|
-|	0x89236316	|	-1994169578	|	The user already joined the ticket.	|
-|	0x89236317	|	-1994169577	|	The queue config is invalid.	|
-|	0x89236318	|	-1994169576	|	One of the users in the ticket has an invalid entity profile.	|
-|	0x89236319	|	-1994169575	|	Matchmaking isn't enabled for this title.	|
-|	0x8923631A	|	-1994169574	|	One of the users in the ticket has attributes that are too large.	|
-|	0x8923631B	|	-1994169573	|	One of the ticket attributes is invalid.	|
-|	0x8923631C	|	-1994169572	|	The user hasn't joined the ticket.	|
-|	0x8923631D	|	-1994169571	|	The number of queues has exceeded the limit for this title.	|
-|	0x8923631E	|	-1994169570	|	The API called doesn't match the type of ticket requested.	|
-|	0x8923631F	|	-1994169569	|	The request was malformed.	|
-|	0x89236320	|	-1994169568	|	Match details can only be provided when the ticket is in the matched state.	|
-|	0x89236321	|	-1994169567	|	The provided multiplayer protocol type is invalid.	|
-|	0x89236322	|	-1994169566	|	The ticket was canceled by the service.	|
+| 0x89236600 | -1994168832 | The PubSub library must be initialized. |
+| 0x89236601 | -1994168831 | Only one PubSubManager instance can exist at a time. |
+| 0x09236602 |  153314818 | The requested operation failed because the PubSub API is still in use. |
+| 0x89236603 | -1994168829 | The specified PubSub entity ID is invalid. |
+| 0x89236604 | -1994168828 | The requested operation failed because the PubSub entity is still in use. |
+| 0x89236605 | -1994168827 | Encountered an exception while parsing and adding the PubSub connection ID to a PlayFab message body. |
+| 0x89236606 | -1994168826 | Failed to parse json data. |
+| 0x89236607 | -1994168825 | The PubSub library is already unsubscribed from the provided PubSub subscription. |
+| 0x89236608 | -1994168824 | Failed to create a PubSub connection string. |
+| 0x89236609 | -1994168823 | The PubSub service encountered an error while creating or maintaining the connection. |
+| 0x8923660A | -1994168822 | Encountered an exception while parsing connection identifier. |
+| 0x8923660B | -1994168821 | The requested entity wasn't found. |
+| 0x8923660C | -1994168820 | The provided connection exists but is in an invalid/unknown state. |
+| 0x8923660D | -1994168819 | Encountered an unexpected exception when attempting to establish PubSub connection. |
+| 0x8923660E | -1994168818 | Encountered an unexpected exception when parsing a subscription event. |
+| 0x8923660F | -1994168817 | Encountered an unexpected exception when parsing a subscription notification payload. |
+| 0x89236610 | -1994168816 | Attempted to establish a PubSub subscription without any available PubSub connections. |
+| 0x89236611 | -1994168815 | The PubSub service declined the attempt to subscribe to the specified resource. |
+| 0x89236612 | -1994168814 | Failed to end the PubSub session while attempting to disconnect. |
+| 0x89236613 | -1994168813 | The Microsoft Game Core XNetworking feature is unavailable. |
+| 0x89236614 | -1994168812 | The PubSub library couldn't be initialized because the Game Core Network stack wasn't initialized. Use the Microsoft Game Core XNetworkingGetConnectivityHint API to determine when the network stack is initialized. |
+| 0x89236616 | -1994168810 | Unable to set up signalr websocket connection. |
+| 0x89236617 | -1994168809 | The PubSub library has hit its max websocket connections limit. |
+| 0x89236618 | -1994168808 | The PubSub connection has hit its max entity limit. |
+| 0x89236619 | -1994168807 | The PubSub service doesn't recognize the entity type. |
+| 0x8923661A | -1994168806 | The PubSub service doesn't recognize the request type. |
+| 0x8923661B | -1994168805 | The PubSub service was unavailable via SignalR. |
+| 0x8923661C | -1994168804 | The PubSub service returned an unexpected response. |
+| 0x8923661D | -1994168803 | The PubSub service is throttling the client over signalr due to exceeding the rate limit. |
+| 0x8923661E | -1994168802 | The PlayFab service returned an unexpected error with a 4XX status code. |
+| 0x8923661F | -1994168801 | The PlayFab service returned an unexpected error with a 5XX status code. |
+| 0x89236620 | -1994168800 | The PubSub service failed to deliver a subscription confirmation within a reasonable timeout. |
+| 0x89236621 | -1994168799 | The PubSub service failed due to lack of authentication credentials to a specific resource. |
+| 0x89236622 | -1994168798 | Failed to access PubSub services; check credentials. |
+| 0x89236623 | -1994168797 | The provided PlayFab title does not have PubSub services enabled. |
+| 0x89236624 | -1994168796 | The PubSub service is throttling the client due to exceeding the rate limit. |
+| 0x89236625 | -1994168795 | The PubSub service could not complete the request because a connection for the specified entity was not found. |
+| 0x89236626 | -1994168794 | PlayFab services rejected our PubSub connection handle as invalid. |
+| 0x89236627 | -1994168793 | The entity has exceeded their limit of concurrent PubSub subscriptions. |
 
 ## Global HRESULT error codes
 
diff --git a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/toc.yml b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/toc.yml
index 2fed0cdc4..9f353f17a 100644
--- a/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/toc.yml
+++ b/playfab-docs/multiplayer/lobby/playfabmultiplayerreference-cpp/toc.yml
@@ -52,6 +52,8 @@
     href: pflobby/functions/pflobbygetowner.md
   - name: PFLobbyGetOwnerMigrationPolicy
     href: pflobby/functions/pflobbygetownermigrationpolicy.md
+  - name: PFLobbyGetRestrictInvitesToLobbyOwner
+    href: pflobby/functions/pflobbygetrestrictinvitestolobbyowner.md
   - name: PFLobbyGetSearchProperty
     href: pflobby/functions/pflobbygetsearchproperty.md
   - name: PFLobbyGetSearchPropertyKeys
diff --git a/playfab-docs/multiplayer/lobby/toc.yml b/playfab-docs/multiplayer/lobby/toc.yml
index 48bfa6670..3e14e2b0d 100644
--- a/playfab-docs/multiplayer/lobby/toc.yml
+++ b/playfab-docs/multiplayer/lobby/toc.yml
@@ -21,6 +21,8 @@ items:
     href: owner-requirements-and-privileges.md
   - name: Lobby ownership changes
     href: ownership-changes.md
+  - name: Lobby lifetime and expiration
+    href: lobby-ttl.md
   - name: Use lobby and matchmaking together
     href: lobby-and-matchmaking.md
   - name: Game servers and Lobbies
@@ -29,8 +31,8 @@ items:
     href: lobby-and-matchmaking-client-sdk-async.md
   - name: Handling C++ SDK errors
     href: lobby-and-matchmaking-client-sdk-errors.md
-- name: Lobby and Matchmaking real-time notifications
-  href: lobby-and-matchmaking-real-time-notifications.md
+- name: Lobby and Matchmaking real-time messages
+  href: lobby-and-matchmaking-real-time-messages.md
 - name: Reference
   items:
   - name: C++ SDK reference
diff --git a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerPort.md b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerPort.md
index a5e64037c..f5dfe9cdd 100644
--- a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerPort.md
+++ b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerPort.md
@@ -10,7 +10,7 @@ ms.date: 08/18/2022
 
 # Class MultiplayerPort
 
-A port used by a Playfab Multiplayer Server.
+A port used by a PlayFab Multiplayer Server.
 
 ```csharp
 public class MultiplayerPort
@@ -20,7 +20,7 @@ public class MultiplayerPort
 
 | name | description |
 | --- | --- |
-| [MultiplayerPort](MultiplayerPort/MultiplayerPort.md)(…) | A port used by a Playfab Multiplayer Server. |
+| [MultiplayerPort](MultiplayerPort/MultiplayerPort.md)(…) | A port used by a PlayFab Multiplayer Server. |
 | [Name](MultiplayerPort/Name.md) { get; set; } | The name of the port as specified in the PlayFab Game Manager server settings. |
 | [Num](MultiplayerPort/Num.md) { get; set; } | The number for the port. |
 | [Protocol](MultiplayerPort/Protocol.md) { get; set; } | The protocol for the port. |
diff --git a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerPort/MultiplayerPort.md b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerPort/MultiplayerPort.md
index 35ac2a1ad..82ce29cb9 100644
--- a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerPort/MultiplayerPort.md
+++ b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerPort/MultiplayerPort.md
@@ -10,7 +10,7 @@ ms.date: 08/18/2022
 
 # MultiplayerPort constructor
 
-A port used by a Playfab Multiplayer Server.
+A port used by a PlayFab Multiplayer Server.
 
 ```csharp
 public MultiplayerPort(string name, uint num, MultiplayerProtocolType protocolType)
diff --git a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerServerDetails.md b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerServerDetails.md
index d1f0e45dd..a4c011004 100644
--- a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerServerDetails.md
+++ b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerServerDetails.md
@@ -10,7 +10,7 @@ ms.date: 08/18/2022
 
 # Class MultiplayerServerDetails
 
-Details about a Playfab Multiplayer Server.
+Details about a PlayFab Multiplayer Server.
 
 ```csharp
 public class MultiplayerServerDetails
@@ -20,9 +20,9 @@ public class MultiplayerServerDetails
 
 | name | description |
 | --- | --- |
-| [MultiplayerServerDetails](MultiplayerServerDetails/MultiplayerServerDetails.md)(…) | Details about a Playfab Multiplayer Server. |
-| [Fqdn](MultiplayerServerDetails/Fqdn.md) { get; set; } | The fully qualified domain name of the virtual machine that is hosting this multiplayer server. |
-| [Ipv4Address](MultiplayerServerDetails/Ipv4Address.md) { get; set; } | The IPv4 address of the virtual machine that is hosting this multiplayer server. |
+| [MultiplayerServerDetails](MultiplayerServerDetails/MultiplayerServerDetails.md)(…) | Details about a PlayFab Multiplayer Server. |
+| [FQDN](MultiplayerServerDetails/Fqdn.md) { get; set; } | The fully qualified domain name of the virtual machine that's hosting this multiplayer server. |
+| [Ipv4Address](MultiplayerServerDetails/Ipv4Address.md) { get; set; } | The IPv4 address of the virtual machine that's hosting this multiplayer server. |
 | [Ports](MultiplayerServerDetails/Ports.md) { get; set; } | The ports the multiplayer server uses. |
 | [Region](MultiplayerServerDetails/Region.md) { get; set; } | The server's region. |
 
diff --git a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerServerDetails/MultiplayerServerDetails.md b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerServerDetails/MultiplayerServerDetails.md
index da7eb5f70..b87c27700 100644
--- a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerServerDetails/MultiplayerServerDetails.md
+++ b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/MultiplayerServerDetails/MultiplayerServerDetails.md
@@ -10,7 +10,7 @@ ms.date: 08/18/2022
 
 # MultiplayerServerDetails constructor
 
-Details about a Playfab Multiplayer Server.
+Details about a PlayFab Multiplayer Server.
 
 ```csharp
 public MultiplayerServerDetails(string fqdn, string ipv4Address, IList<MultiplayerPort> ports, 
@@ -19,8 +19,8 @@ public MultiplayerServerDetails(string fqdn, string ipv4Address, IList<Multiplay
 
 | parameter | description |
 | --- | --- |
-| fqdn | The fully qualified domain name of the virtual machine that is hosting this multiplayer server. |
-| ipv4Address | The IPv4 address of the virtual machine that is hosting this multiplayer server. |
+| FQDN | The fully qualified domain name of the virtual machine that's hosting this multiplayer server. |
+| ipv4Address | The IPv4 address of the virtual machine that's hosting this multiplayer server. |
 | ports | The ports the multiplayer server uses. |
 | region | The server's region. |
 
diff --git a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFabMultiplayerSDK.md b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFabMultiplayerSDK.md
index 60271aac6..bcb88efbd 100644
--- a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFabMultiplayerSDK.md
+++ b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/PlayFabMultiplayerSDK.md
@@ -42,9 +42,9 @@ ms.date: 11/23/2021
 | class [MatchmakingTicketMatchMember](PlayFab.Multiplayer/MatchmakingTicketMatchMember.md) | A member of a match result. |
 | enum [MatchmakingTicketStatus](PlayFab.Multiplayer/MatchmakingTicketStatus.md) | The possible states for a matchmaking ticket. |
 | struct [MatchUser](./PlayFab.Multiplayer/MatchUser.md) | A member of a match result. |
-| class [MultiplayerPort](./PlayFab.Multiplayer/MultiplayerPort.md) | A port used by a Playfab Multiplayer Server. |
+| class [MultiplayerPort](./PlayFab.Multiplayer/MultiplayerPort.md) | A port used by a PlayFab Multiplayer Server. |
 | enum [MultiplayerProtocolType](PlayFab.Multiplayer/MultiplayerProtocolType.md) | The access policy for the lobby |
-| class [MultiplayerServerDetails](./PlayFab.Multiplayer/MultiplayerServerDetails.md) | Details about a Playfab Multiplayer Server. |
+| class [MultiplayerServerDetails](./PlayFab.Multiplayer/MultiplayerServerDetails.md) | Details about a PlayFab Multiplayer Server. |
 | class [PFEntityKey](./PlayFab.Multiplayer/PFEntityKey.md) | PFEntityKey data model. Combined entity type and ID structure which uniquely identifies a single entity. |
 | class [PlayFabMultiplayer](./PlayFab.Multiplayer/PlayFabMultiplayer.md) |  |
 | class [PlayFabMultiplayerErrorArgs](PlayFab.Multiplayer/PlayFabMultiplayerErrorArgs.md) | An event argument class representing a PFMultiplayer error. |
diff --git a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/index.md b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/index.md
index 0c0940b98..b04792c74 100644
--- a/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/index.md
+++ b/playfab-docs/multiplayer/lobby/unity-multiplayer-api-reference/index.md
@@ -28,8 +28,8 @@ ms.date: 11/23/2021
 | [MatchmakingMatchDetails](PlayFab.Multiplayer/MatchmakingMatchDetails.md) |  |
 | [MatchmakingTicket](PlayFab.Multiplayer/MatchmakingTicket.md) |  |
 | [MatchmakingTicketMatchMember](PlayFab.Multiplayer/MatchmakingTicketMatchMember.md) |  |
-| [MultiplayerPort](./PlayFab.Multiplayer/MultiplayerPort.md) | A port used by a Playfab Multiplayer Server. |
-| [MultiplayerServerDetails](./PlayFab.Multiplayer/MultiplayerServerDetails.md) | Details about a Playfab Multiplayer Server. |
+| [MultiplayerPort](./PlayFab.Multiplayer/MultiplayerPort.md) | A port used by a PlayFab Multiplayer Server. |
+| [MultiplayerServerDetails](./PlayFab.Multiplayer/MultiplayerServerDetails.md) | Details about a PlayFab Multiplayer Server. |
 | [PFEntityKey](./PlayFab.Multiplayer/PFEntityKey.md) | PFEntityKey data model. Combined entity type and ID structure which uniquely identifies a single entity. |
 | [PlayFabMultiplayer](./PlayFab.Multiplayer/PlayFabMultiplayer.md) |  |
 | [PlayFabMultiplayerServer](PlayFab.Multiplayer/PlayFabMultiplayer.PlayFabMultiplayerServer.md) |  |
diff --git a/playfab-docs/multiplayer/matchmaking/backfill-tickets.md b/playfab-docs/multiplayer/matchmaking/backfill-tickets.md
index f5530ef56..0e8b78533 100644
--- a/playfab-docs/multiplayer/matchmaking/backfill-tickets.md
+++ b/playfab-docs/multiplayer/matchmaking/backfill-tickets.md
@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 # Using server backfill tickets - REST API
 
 > [!NOTE]
-> We highly recommend you consider using the Multiplayer SDKs as it includes real-time notification support that reduces the need for polling, improving the matchmaking experience and reducing delays. [Using Server Backfill Tickets - Multiplayer SDK](backfill-tickets-multiplayer-sdk.md)
+> We highly recommend you consider using the Multiplayer SDKs as it includes real-time message support that reduces the need for polling, improving the matchmaking experience and reducing delays. [Using Server Backfill Tickets - Multiplayer SDK](backfill-tickets-multiplayer-sdk.md)
 
 Games hosted on a server sometimes find they need to search for extra
 players. Most often this occurs when one or more players disconnect while the
diff --git a/playfab-docs/multiplayer/matchmaking/config-queues.md b/playfab-docs/multiplayer/matchmaking/config-queues.md
index 3dc88c658..0984cd710 100644
--- a/playfab-docs/multiplayer/matchmaking/config-queues.md
+++ b/playfab-docs/multiplayer/matchmaking/config-queues.md
@@ -14,94 +14,94 @@ ms.localizationpriority: medium
 
 ## Overview
 
-Match configuration centers around queues, which represent a place where tickets wait to be matched with each other. Each queue has some general configuration about what is required for a match. In addition, it can contain a set of rules which provide further restrictions on how tickets are matched together.
+Match configuration centers around queues, which represent a place where tickets wait to be matched with each other. Each queue has some general configuration about what is required for a match. In addition, it can contain a set of rules that provide further restrictions on how tickets are matched together.
 
 ## Queue configuration
 
-At the queue level, the configuration describes basic requirements regarding how tickets are matched inside a queue, as well as how you obtain statistics information about the queue.
+At the queue level, the configuration describes basic requirements regarding how tickets are matched inside a queue and how you obtain statistics information about the queue.
 
 ### Queue name
 
-The name for a specific queue. It is between 1 and 64 characters long (inclusive) and is case-sensitive. It is alpha-numeric, plus underscores and hyphens, and starts with a letter or number. Generally a queue name represents a way to play a game, such as "4v4CaptureTheFlag" or "UnrankedRace". When creating a matchmaking ticket, the queue name must be specified to identify which queue it should enter.
+The name for a specific queue. It is between 1 and 64 characters long (inclusive) and is case-sensitive. It's alpha-numeric, plus underscores and hyphens, and starts with a letter or number. Generally a queue name represents a way to play a game, such as "4v4CaptureTheFlag" or "UnrankedRace". When you create a matchmaking ticket, you must specify the queue name to identify which queue it should enter.
 
 ### Match size
 
-The range of players allowed in a match. The minimum match size must be greater than or equal to 2, and the maximum match size must be less than or equal to 100 (this limit is 32, if using teams).
+The range of players allowed in a match. The minimum match size must be greater than or equal to two. The maximum match size must be less than or equal to 100. When using teams, this limit is 32.
 
-In addition, even if a ticket alone already meets the minimum requirements for a match, it won't return a match found until it matches at least one other ticket. If a ticket already meets the maximum requirement for a match, however, it will be rejected.
+In addition, even if a ticket alone already meets the minimum requirements for a match, it doesn't return a match found until it matches at least one other ticket. If a ticket already meets the maximum requirement for a match, however, it is rejected.
 
 ### Statistics available to players
 
-This determines which queue statistics are exposed to players through the [GetQueueStatistics API](xref:titleid.playfabapi.com.multiplayer.matchmaking.getqueuestatistics). Servers always have access to all statistics. See the [Displaying queue statistics in your title](display-statistics.md) tutorial for more information.
+This feature determines which queue statistics are exposed to players through the [GetQueueStatistics API](xref:titleid.playfabapi.com.multiplayer.matchmaking.getqueuestatistics). Servers always have access to all statistics. For more information, see [Displaying queue statistics in your title](display-statistics.md).
 
-There are two options you can control within this:
+There are two options you can control within this configuration:
 
-1. **Show the number of players matching** - Whether the number of players waiting for a match is exposed to players. Titles may use this to hide the relative popularity of the mode, or to keep player counts hidden for business reasons.
+1. **Show the number of players matching** - Whether the number of players waiting for a match is exposed to players. Titles may use this option to hide the relative popularity of the mode, or to keep player counts hidden for business reasons.
 2. **Show the time to match statistics** - Whether the time to match statistics (average and percentiles) are exposed to players.
 
 ### Teams
 
-A queue can include team configuration to have the match service assign players to teams. Additional team-specific rules can be used to control how team assignment is done. Furthermore, the match service will ensure that players matching together in the same ticket are not assigned to different teams.
+A queue can include team configuration to have the match service assign players to teams. More team-specific rules can be used to control how team assignment is done. Furthermore, the match service ensures that players matching together in the same ticket aren't assigned to different teams.
 
-You can have 2 or more teams defined in a queue.
+You can have two or more teams defined in a queue.
 
-+ **Team name** - The name used for this team. Team names are between 1 and 64 characters long (inclusive) and are case-sensitive. They are alphanumeric, plus underscores and hyphens, and start with a letter or number. In addition they must be unique within a queue.
-+ **Team size** - Minimum and maximum number of players that can be on the team. Matchmaking will try to form teams with as many players as possible up to the maximum.
++ **Team name** - The name used for this team. Team names are between 1 and 64 characters long (inclusive) and are case-sensitive. They're alphanumeric, plus underscores and hyphens, and start with a letter or number. In addition, they must be unique within a queue.
++ **Team size** - Minimum and maximum number of players that can be on the team. Matchmaking tries to form teams with as many players as possible up to the maximum.
 
-Besides defining the teams and their sizes, additional rules can be enabled to help with how to handle teams in matchmaking. See [below](#team-rule-types) for information on team-specific rules.
+Besides defining the teams and their sizes, other rules can be enabled to help with how to handle teams in matchmaking. For information on team-specific rules, see [Team rule types](#team-rule-types).
 
 ## Rule configuration
 
 Rules may be optionally defined for a queue. When configured, they help the matchmaking algorithm determine which tickets should match together. Each rule applies to a single attribute in the player metadata. You can have a maximum of 20 rules defined for a single queue.
 
-There are many types of rules. Each contains some common configurable elements, as well as elements that are specific to that particular type of rule. In addition, many rules allow an expansion, in which the rules become less restrictive over time.
+There are many types of rules. Each contains some common configurable elements and elements that are specific to that particular type of rule. In addition, many rules allow an expansion, in which the rules become less restrictive over time.
 
 ### Common rule elements
 
-The elements below are often used by all rules.
+The following elements are often used by all rules.
 
 + **Rule Name** - The name must be between 1 and 255 characters long (inclusive), is alpha-numeric plus underscores and hyphens, and must start with a letter or number. Rule names must be unique within a queue.
-+ **Weight** - A way to modify the importance of a rule. Rules in general provide both a restriction as well as a way to sort the remaining tickets that are eligible. The weight is a multiplier, modifying how important the rule is for sorting purposes.
++ **Weight** - A way to modify the importance of a rule. Rules in general provide both a restriction and a way to sort the remaining tickets that are eligible. The weight is a multiplier, modifying how important the rule is for sorting purposes. For more information, see [Understanding rule weight in matchmaking](rule-weights.md).
 + **Attribute Source** - Rules often act upon information that is provided to them. This field describes two options for the source of this information:
 
   1. **User** - Attributes are submitted alongside players in the create or join ticket request.
-  2. **Player Entity** - Attributes are retrieved from the player's associated Player Entity. These can be set via the [SetObjects API](xref:titleid.playfabapi.com.data.object.setobjects)
+  2. **Player Entity** - Attributes are retrieved from the player's associated Player Entity. You can set these attributes via the [SetObjects API](xref:titleid.playfabapi.com.data.object.setobjects). DO NOT use this source when using external entity types. 
 + **Attribute Path** - The path to reach the attribute. When using a User Attribute Source, it is simply the name of the attribute. When using a Player
   Entity Attribute Source, it is a [JSONPath](https://github.com/json-path/JsonPath) that retrieves a particular item from the entity, such as `$.playerSkill.Mean`.
 + **Behavior when attribute is not specified** - If a rule requires an attribute, but none is specified, the rule may be configured with one of two behaviors:
 
   1. It may supply a default value for the attribute.
-  2. It may use this as a signal to indicate the ticket meets any restriction supplied by the rule. This may be useful if for instance, some players express a preference, and another player is willing to match anyone. The player with no preference can neglect to supply an attribute, and match with any other players.
+  2. It may use this signal as a way to indicate the ticket meets any restriction supplied by the rule. This behavior may be useful if, for instance, some players express a preference, and another player is willing to match anyone. The player with no preference can neglect to supply an attribute, and match with any other players.
 
 ### Standard rule types
 
-Each of the rule types is listed below, along with its purpose, some common uses, and any specific configuration the rule may require.
+Each of the following rule types is listed along with its purpose, some common uses, and any specific configuration the rule may require.
 
 | Rule type       | Description | Common Uses | Rule-specific fields |
 |-----------------|-------------|-------------|----------------------|
 | String Equality | Ensures that a string attribute is the same across all tickets in a match. |  Requires build versions or other specific items to match | none |
 | Difference | Ensures that the absolute difference for a number attribute between any two tickets in a match is less than a configured maximum difference. |  Groups players by skill, experience, or other numeric comparisons |  Merge function - Select how multiple player values are merged into one value representing the ticket. Choices are min, max, and average. Defaults to average. |
-| Set Intersection | Ensures that for a given attribute that is a list of strings, all tickets in a match share at least as many values as is configured. | DLC or map selection | Min intersection size - Minimum number of shared items for a match. |
+| Set Intersection | Ensures that for a given attribute that is a list of strings, all tickets in a match share at least as many values as is configured. | Downloadable content (DLC) or map selection | Min intersection size - Minimum number of shared items for a match. |
 | Match Total | Ensures that the sum of a number attribute across all players in a match is within a configured range. | Role selection, emulating host/server matchmaking, adjusting player count restrictions over time | Min/Max total - Sum of attribute must be within these inclusive bounds. |
 | Region Selection | Ensures that the latency to a common data center for all users of the match is less than a configured max value. | Required for multiplayer server integration | Max Latency - Only datacenters within this max latency are eligible for a match. |
 
 ### Team rule types
 
-Team rules can only be set if teams are present in the queue configuration. They provide additional ways to require balance between the teams. The following team rules are available:
+Team rules can only be set if teams are present in the queue configuration. They provide more ways to require balance between the teams. The following team rules are available:
 
 | Rule type       | Description | Common Uses | Rule-specific fields |
 |-----------------|-------------|-------------|----------------------|
-| Team Difference | Ensures that teams included in a match are within a configured difference for a specific attribute (such as skills). This is very similar to a standard Difference Rule, except that the values compared are each team's average value. | Balancing skills across teams | none |
-| Team Size Balance | Ensures the difference in player count between the largest and smallest team does not exceed a threshold. For instance, this rule could be used to create a queue where 3v3 and 4v4 matches are allowed, but a 3v4 is not. | Player count balance across teams | Allowed Team Size Difference - How uneven the teams can be, as measured by the difference in the number of players assigned to each one. |
-| Team Ticket Size Similarity | Ensures that all teams either have a large party, or do not have a large party. A large party is defined as at least half of the maximum team's size. | Prevents parties (pre-made teams) from matching with a group of solo players. | none |
+| Team Difference | Ensures that teams included in a match are within a configured difference for a specific attribute (such as skills). This is similar to a standard Difference Rule, except that the values compared are each team's average value. | Balancing skills across teams | none |
+| Team Size Balance | Ensures the difference in player count between the largest and smallest team doesn't exceed a threshold. For instance, this rule could be used to create a queue where 3v3 and 4v4 matches are allowed, but a 3v4 isn't. | Player count balance across teams | Allowed Team Size Difference - How uneven the teams can be, as measured by the difference in the number of players assigned to each one. |
+| Team Ticket Size Similarity | Ensures that all teams either have a large party, or don't have a large party. A large party is defined as at least half of the maximum team's size. | Prevents parties (premade teams) from matching with a group of solo players. | none |
 
 ### Expansions and becoming optional
 
-Rules may become optional or less restrictive over time, allowing tickets that have waited for some time to search wider for a potential match. There are two methods for controlling this behavior:
+Rules may become optional or less restrictive over time, allowing tickets that wait for some time to search wider for a potential match. There are two methods for controlling this behavior:
 
-1. **Seconds until optional** - Simply indicates a length of time that the rule is active. The rule no longer restricts matches among tickets that have waited this time.
+1. **Seconds until optional** - Simply indicates a length of time that the rule is active. The rule no longer restricts matches among tickets that wait this time.
 
-2. **Expansion process** - Rules gradually adjust their configured thresholds over time. For instance, a Difference Rule may require matches within a particular maximum difference. As a ticket waits, the rule may expand the maximum difference, permitting expansion to a larger and larger range for the ticket, and allowing it to be matched even if perfect opponents are unavailable.
+2. **Expansion process** - Rules gradually adjust their configured thresholds over time. For instance, a Difference Rule may require matches within a particular maximum difference. As a ticket waits, the rule may expand the maximum difference. This expansion permits a larger and larger range for the ticket. It allows the ticket to be matched even if perfect opponents are unavailable.
 
 Expansions can be either **linear** or **custom**. In a linear expansion, a value grows over time, using a fixed change after each time interval. The items customized in a linear expansion are:
 
@@ -112,9 +112,9 @@ Expansions can be either **linear** or **custom**. In a linear expansion, a valu
 In a custom expansion, the rule can use an arbitrary value each time the rule changes its restrictions. The following fields are used:
 
 + **Seconds between expansions** - How long in between each instance of the rule changing its restrictions
-+ **One or more custom fields** that modifies a rule during the expansion. Each field is semicolon delimited to represent a different value which is used in each expansion's interval. The word "null" may be used in place of a value to indicate the rule is not active during this interval.
++ **One or more custom fields** that modifies a rule during the expansion. Each field is semicolon delimited to represent a different value that is used in each expansion's interval. The word "null" may be used in place of a value to indicate the rule isn't active during this interval.
 
-The exact field modified depends on the rule. The following chart describes which rules have which kinds of expansions, and what fields are modified by the expansion.
+The exact field modified depends on the rule. The following chart describes which rules have which kinds of expansions, and what fields the expansion modifies.
 
 | Rule type        | Linear Expansion Allowed? | Custom expansion allowed? | Attribute modified during expansion |
 |------------------|-------------|-------------|----------------------|
@@ -127,4 +127,4 @@ The exact field modified depends on the rule. The following chart describes whic
 | Team Size Balance| yes | yes | Allowed difference in number of players per team |
 | Team Ticket Size Similarity | no | no | n/a |
 
-For more details on configuration use cases and examples, see [Matchmaking scenario and configuration examples](config-examples.md).
+For more information on configuration use cases and examples, see [Matchmaking scenario and configuration examples](config-examples.md).
diff --git a/playfab-docs/multiplayer/matchmaking/index.md b/playfab-docs/multiplayer/matchmaking/index.md
index 06a433b02..29b4e3ae1 100644
--- a/playfab-docs/multiplayer/matchmaking/index.md
+++ b/playfab-docs/multiplayer/matchmaking/index.md
@@ -90,6 +90,6 @@ For more information on specific flows from either your game client or service,
 + [Matchmaking API Reference](xref:titleid.playfabapi.com.multiplayer.matchmaking)
 <!-- + [Matchmaking Admin API Reference](xref:titleid.playfabapi.com.multiplayer.matchmakingadmin) -->
 + [PlayStream Events](../../api-references/events/index.md)
-    + [matchmaking_match_found](../../api-references/events/matchmaking-match-found.md)
-    + [matchmaking_ticket_completed](../../api-references/events/matchmaking-ticket-completed.md)
+    + [matchmaking_match_found](../../api-references/events/Matchmaking/match-found.md)
+    + [matchmaking_ticket_completed](../../api-references/events/Matchmaking/ticket-completed.md)
 
diff --git a/playfab-docs/multiplayer/matchmaking/matchmaking-partition.md b/playfab-docs/multiplayer/matchmaking/matchmaking-partition.md
new file mode 100644
index 000000000..55fffe864
--- /dev/null
+++ b/playfab-docs/multiplayer/matchmaking/matchmaking-partition.md
@@ -0,0 +1,48 @@
+---
+title: Matchmaking scaling
+author: keithrkline
+description: Describes how matchmaking scales under load
+ms.author: kkline
+ms.date: 02/25/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, multiplayer, matchmaking, partition, scaling, performance
+ms.localizationpriority: medium
+---
+
+# How matchmaking scales under load
+
+## Overview
+
+When a queue receives a high volume of tickets, the service automatically scales its processing to maintain low match latency. As load increases, tickets are grouped using your queue's configured rules so that similar tickets—tickets more likely to be compatible—are evaluated together. As load decreases, these groups consolidate, giving the service a larger pool of tickets to choose from and improving match quality.
+
+This scaling is transparent to players, but the rules you configure on a queue influence how effectively the service can distribute work. Understanding this process can help you design queue configurations that scale efficiently.
+
+## What makes a rule scale well
+
+When the service needs to distribute tickets across its processing capacity, it looks for rule attributes that naturally divide tickets into roughly equal groups. Rules with a wide range of distinct values work best—they give the service more options for balancing load evenly.
+
+If no rule provides a good distribution, the service falls back to a general-purpose distribution that balances load without relying on rule attributes. For example, this happens when most tickets share identical attribute values.
+
+### Rules that partition well
+
++ **String equality rules with diverse values**—Rules like `GameMode` or `Region` that have multiple distinct values across your player population create natural partition boundaries. The service can cleanly divide tickets into groups that share the same value.
++ **Required rules**—Rules that remain enforced throughout matching (without an expansion) are preferred for partitioning because they represent hard constraints. Splitting on these rules ensures that partition boundaries align with your strongest match requirements.
++ **Higher-weighted rules**—Rules with a greater [weight](rule-weights.md) are prioritized for partitioning. This approach means the rules you consider most important for match quality are also the ones most likely to guide how tickets are distributed.
++ **Difference rules with a spread of values**—Numeric rules like skill rating work well when player values are distributed across a range, allowing the service to split tickets into groups with similar values.
+
+### Rules that are less effective for partitioning
+
++ **Rules where most tickets share the same value**—If nearly all players submit the same attribute value for a rule, the service can't use that rule to create a meaningful split.
++ **Rules with heavy wildcard usage**—When a large proportion of tickets uses a wildcard (match-any) value for a rule, that rule becomes less useful for dividing tickets into distinct groups.
++ **Rules with expansions**—Rules that become optional over time are deprioritized for partitioning because they represent softer constraints that may not hold during a ticket's lifetime.
+
+## Design considerations
+
+When designing matchmaking queues for games that may experience high ticket volumes, keep the following considerations in mind:
+
++ **Distribute attribute values**—Rules with diverse attribute values across your player population produce better partition splits. If most players share the same value for a rule, it doesn't help balance load across partitions.
++ **Weight important rules higher**—The [weight](rule-weights.md) of a rule affects both match sorting priority and partition splitting priority. Assigning higher weights to the rules most important for match quality ensures those rules also guide how tickets are distributed.
++ **Avoid unnecessary wildcards**—When a large proportion of tickets uses wildcard values for a rule, that rule becomes less useful for partitioning. Consider whether wildcard behavior is necessary for your game design.
++ **Retries during partition changes are normal**—When the partition layout changes due to a split or merge, some tickets may be briefly canceled with a retry signal. The matchmaking SDK handles this automatically, so players experience only a momentary delay.
+
diff --git a/playfab-docs/multiplayer/matchmaking/quickstart-client-sdk.md b/playfab-docs/multiplayer/matchmaking/quickstart-client-sdk.md
index 30d22c207..a0e702ed1 100644
--- a/playfab-docs/multiplayer/matchmaking/quickstart-client-sdk.md
+++ b/playfab-docs/multiplayer/matchmaking/quickstart-client-sdk.md
@@ -27,7 +27,7 @@ The matchmaking service handles finding a match among tickets in a queue. When a
 
 ## Prerequisites
 
-You need a [PlayFab account](https://playfab.com) to use PlayFab Matchmaking. For instructions to create an account, see [Quickstart: Game Manager](../../live-service-management/gamemanager/quickstart.md).
+You need a [PlayFab account](https://developer.playfab.com) to use PlayFab Matchmaking. For instructions to create an account, see [Quickstart: Game Manager](../../live-service-management/gamemanager/quickstart.md).
 
 ## Configure a matchmaking queue in Game Manager
 
diff --git a/playfab-docs/multiplayer/matchmaking/quickstart.md b/playfab-docs/multiplayer/matchmaking/quickstart.md
index ae89ba399..dad405ab4 100644
--- a/playfab-docs/multiplayer/matchmaking/quickstart.md
+++ b/playfab-docs/multiplayer/matchmaking/quickstart.md
@@ -1,7 +1,7 @@
 ---
 title: Matchmaking quickstart
 author: keithrkline
-description: Quickstart which demonstrates a matchmaking flow in Unity
+description: Quickstart that demonstrates a matchmaking flow in Unity
 ms.author: kkline
 ms.date: 03/15/2019
 ms.topic: article
@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 # Matchmaking REST API quickstart 
 
 > [!NOTE]
-> We highly recommend you consider using the Multiplayer SDKs as it includes real-time notification support that reduces the need for polling. This will improve the matchmaking experience and reduce delays. [Quickstart - Client SDK](quickstart-client-sdk.md)
+> We highly recommend you consider using the Multiplayer SDKs as it includes real-time message support that reduces the need for polling. This will improve the matchmaking experience and reduce delays. [Quickstart - Client SDK](quickstart-client-sdk.md)
 
 This quickstart guide walks you through the entire process for integrating the matchmaking feature. All code examples within this quickstart are for Unity - however, the concepts and flow apply (in general) to other platforms as well.
 
@@ -22,11 +22,11 @@ user](#multiple-user-ticket-matchmaking) matchmaking section.
 
 This tutorial illustrates how to submit a ticket to a specific queue in order to find a game. A queue likely maps to a game mode or multiple game modes (ex.: a capture the flag mode and a king of the hill mode in the same queue).
 
-The matchmaking service handles finding a match amongst tickets in a queue. When a match is found, your title must handle connecting the players together for gameplay.
+The matchmaking service handles finding a match among tickets in a queue. When a match is found, your title must handle connecting the players together for gameplay.
 
 ## Configure a matchmaking queue in Game Manager
 
-The quickstart assumes that you have configured your queue(s) in Game Manager. For details on how to set one up, see [Configuring matchmaking queues](config-queues.md).
+The quickstart assumes that you have configured your queues in Game Manager. For details on how to set one up, see [Configuring matchmaking queues](config-queues.md).
 
 ## Single user ticket matchmaking
 
@@ -79,7 +79,7 @@ PlayFabMultiplayerAPI.CreateMatchmakingTicket(
 
 ### Check the status of the matchmaking ticket
 
-You must poll the service by `TicketId` to access the `Status` of the ticket in matchmaking. In order to do so, have your title call [GetMatchmakingTicket](xref:titleid.playfabapi.com.multiplayer.matchmaking.getmatchmakingticket). You can poll up to 10 times per minute. For instance, poll for the ticket status every 6 seconds. Polling can increase delays when retrieving the status of your ticket. It is for this reason we highly recommend you consider using the Multiplayer SDK method described here [Quickstart - Client SDK](quickstart-client-sdk.md). This avoids the need to poll by using the real-time notification functionality. 
+You must poll the service by `TicketId` to access the `Status` of the ticket in matchmaking. In order to do so, have your title call [GetMatchmakingTicket](xref:titleid.playfabapi.com.multiplayer.matchmaking.getmatchmakingticket). You can poll up to 10 times per minute. For instance, poll for the ticket status every 6 seconds. Polling can increase delays when retrieving the status of your ticket. It is for this reason we highly recommend you consider using the Multiplayer SDK method described here [Quickstart - Client SDK](quickstart-client-sdk.md). This avoids the need to poll by using the real-time message functionality. 
 
 When the status of
 the ticket changes to `Matched`, your client can stop polling the ticket. From that point on, the ticket will include the `MatchId`.
@@ -172,13 +172,13 @@ The rest of the process is the same as that of [single user ticket matchmaking](
 
 ### Connecting your players together
 
-Once your players have matched, you will want to have them join each other - either through a server, or by peer-to-peer connections.
+Once your players have matched, you'll want to have them join each other - either through a server, or by peer-to-peer connections.
 
-If you are using a dedicated server, you can rely on the Match ID to uniquely identify the group of players they should be in. If you are using PlayFab's multiplayer servers, `GetMatch` will provide a server and port for your players to connect to.
+If you're using a dedicated server, you can rely on the Match ID to uniquely identify the group of players they should be in. If you're using PlayFab's multiplayer servers, `GetMatch` provides a server and port for your players to connect to.
 
-Please refer to [Integrating with PlayFab Multiplayer Servers](multiplayer-servers.md) for more information.
+For more information, see [Integrating with PlayFab Multiplayer Servers](multiplayer-servers.md).
 
-As of this release, peer-to-peer connection is currently not officially supported by matchmaking. If peer-to-peer is required, consider using [Playfab Party](../networking/index.md), or an [interim workaround](peer-to-peer.md).
+As of this release, peer-to-peer connection is currently not officially supported by matchmaking. If peer-to-peer is required, consider using [PlayFab Party](../networking/index.md), or an [interim workaround](peer-to-peer.md).
 Contact us for more support on this.
 
 ## Conclusion
diff --git a/playfab-docs/multiplayer/matchmaking/rule-weights.md b/playfab-docs/multiplayer/matchmaking/rule-weights.md
new file mode 100644
index 000000000..0d327f8e4
--- /dev/null
+++ b/playfab-docs/multiplayer/matchmaking/rule-weights.md
@@ -0,0 +1,237 @@
+---
+title: Understanding rule weight in matchmaking
+author: keithrkline
+description: Explains how the Weight property on matchmaking rules affects match quality and ticket sorting
+ms.author: kkline
+ms.date: 02/24/2026
+ms.topic: conceptual
+ms.service: azure-playfab
+keywords: playfab, multiplayer, matchmaking, weight, rules, configuration
+ms.localizationpriority: medium
+---
+
+# Understanding rule weight in matchmaking
+
+## Overview
+
+When you configure a matchmaking queue, you can assign each rule a **Weight** value. Weight is a numeric multiplier that controls how much influence a particular rule has when the matchmaking system ranks and sorts eligible tickets. It doesn't change whether a ticket passes or fails a rule—it only affects **how important that rule is relative to others** when determining which tickets are the best candidates for a match.
+
+Understanding weight is essential for tuning match quality. By adjusting weights across your rules, you can prioritize what matters most for your game—whether that's skill balance, geographic proximity, or shared content.
+
+## How weight works
+
+Every rule that supports weight computes a **distance** value for each pair of tickets being evaluated. This distance represents how similar or different two tickets are according to that rule:
+
+- A distance of **0** means the tickets are a perfect match for that rule.
+- A distance closer to **1** means the tickets are at the edge of what the rule allows.
+- A distance of **infinite** (hard rejection) means the tickets can't match according to that rule, regardless of weight.
+
+The matchmaking system calculates a **total distance** across all weighted rules using the following formula:
+
+```
+totalDistance = Σ (rule.Weight × rule.Distance)
+```
+
+Tickets with a lower total distance are considered better candidates and are tried first when building a match. Weight acts as a scalar multiplier on each rule's contribution to this total.
+
+> [!IMPORTANT]
+> Weight does **not** override hard restrictions. If a rule determines that two tickets are incompatible, the tickets are excluded entirely. For example, this happens with a Difference Rule where the values exceed the maximum allowed difference. Weight only influences the **priority order** among tickets that are already eligible.
+
+## How each rule computes distance
+
+Before you look at weight examples, it helps to understand how each weighted rule computes its distance value. The distance is always a number between 0 and 1, where lower values indicate a closer match.
+
+| Rule type | Distance formula | Distance = 0 | Distance = 1 |
+|-----------|-----------------|---------------|--------------|
+| Difference | `absoluteDifference / maxDifference` | Player values are identical | Players differ by the full allowed amount |
+| String Equality | 0 if strings match; 1 if the rule is optional and strings differ | Strings are identical | Rule is optional and strings differ |
+| Set Intersection | `1 / (1 + sharedItemCount)` | N/A (minimum is 0.5 with one shared item) | No shared items (`1 / (1 + 0) = 1`) |
+| Match Total | `(maxTotal - (groupTotal + ticketValue)) / maxTotal` | Group is at the target capacity | Group is far from the target total |
+| Region Selection | `1 / (1 + Σ qualityTerms)` | Many low-latency common regions | Few or poor common regions |
+
+## Which rules support weight
+
+Weight applies to the **standard rule types** that participate in distance-based sorting. The following rules support the Weight property:
+
+| Rule type | Supports Weight |
+|-----------|:-:|
+| String Equality | ✔ |
+| Difference | ✔ |
+| Set Intersection | ✔ |
+| Match Total | ✔ |
+| Region Selection | ✔ |
+
+The following **team rule types** do **not** support weight. These rules act as validators—they either pass or fail a match and don't participate in distance-based sorting:
+
+| Rule type | Supports Weight | Behavior |
+|-----------|:-:|-------------|
+| Team Difference | ✘ | Validates that team averages are within an allowed difference |
+| Team Size Balance | ✘ | Validates that team player counts are balanced |
+| Team Ticket Size Similarity | ✘ | Validates that teams have similar party compositions |
+
+## Valid weight values
+
+Weight must be a number **greater than 0** and **up to 1000** (inclusive). A weight of 0 isn't permitted. If no weight is specified, the default value is **1**.
+
+## Examples
+
+The following examples use a queue with a **Difference Rule** for skill and a **Set Intersection Rule** for preferred game maps. Three players—Alice, Bob, and Charlie—are in the queue. The matchmaking system needs to decide which of the two candidates (Bob or Charlie) is the better match for Alice.
+
+### Queue configuration
+
+```json
+"Rules": [
+    {
+        "Type": "DifferenceRule",
+        "Name": "SkillRule",
+        "Attribute": { "Path": "skill", "Source": "User" },
+        "MaxDifference": 10,
+        "MergeFunction": "Average",
+        "Weight": 1
+    },
+    {
+        "Type": "SetIntersectionRule",
+        "Name": "MapRule",
+        "Attribute": { "Path": "preferredMaps", "Source": "User" },
+        "MinIntersectionSize": 1,
+        "Weight": 1
+    }
+]
+```
+
+### Player attributes
+
+| Player | Skill | Preferred Maps |
+|--------|-------|----------------|
+| Alice | 20 | "Dustbowl", "Summit", "Lakeside" |
+| Bob | 24 | "Dustbowl," "Summit" |
+| Charlie | 17 | "Lakeside" |
+
+### Step 1: Compute per-rule distances
+
+**SkillRule** (Difference Rule) uses the formula `absoluteDifference / maxDifference`:
+
+- Alice vs Bob: `|20 - 24| / 10 = 4 / 10 = 0.4`
+- Alice vs Charlie: `|20 - 17| / 10 = 3 / 10 = 0.3`
+
+**MapRule** (Set Intersection Rule) uses the formula `1 / (1 + sharedItemCount)`:
+
+- Alice vs Bob: They share "Dustbowl" and "Summit" (two items) → `1 / (1 + 2) = 0.33`
+- Alice vs Charlie: They share "Lakeside" (one item) → `1 / (1 + 1) = 0.5`
+
+### Example 1: Equal weights
+
+With both rules at Weight = 1, the total distance is:
+
+```
+Bob:     totalDistance = (1 × 0.4)  + (1 × 0.33) = 0.73
+Charlie: totalDistance = (1 × 0.3)  + (1 × 0.5)  = 0.80
+```
+
+**Result:** Bob (0.73) is a better match than Charlie (0.80). Even though Charlie is closer in skill, Bob shares more maps with Alice, and both rules contribute equally. Bob is tried first.
+
+### Example 2: Prioritizing skill (Weight = 10 on SkillRule)
+
+If your game is competitive and skill balance matters most, increase the SkillRule weight:
+
+```json
+{
+    "Type": "DifferenceRule",
+    "Name": "SkillRule",
+    ...
+    "Weight": 10
+},
+{
+    "Type": "SetIntersectionRule",
+    "Name": "MapRule",
+    ...
+    "Weight": 1
+}
+```
+
+Now the total distances change:
+
+```
+Bob:     totalDistance = (10 × 0.4)  + (1 × 0.33) = 4.33
+Charlie: totalDistance = (10 × 0.3)  + (1 × 0.5)  = 3.50
+```
+
+**Result:** Charlie (3.50) is now the better match. The higher weight on skill means Charlie's closer skill level (three difference vs 4) outweighs the fact that Bob shares more maps. Skill dominates the sort order.
+
+### Example 3: Prioritizing shared maps (Weight = 10 on MapRule)
+
+If your game is casual and players care most about playing on their favorite maps, increase the MapRule weight instead:
+
+```json
+{
+    "Type": "DifferenceRule",
+    "Name": "SkillRule",
+    ...
+    "Weight": 1
+},
+{
+    "Type": "SetIntersectionRule",
+    "Name": "MapRule",
+    ...
+    "Weight": 10
+}
+```
+
+Now the total distances become:
+
+```
+Bob:     totalDistance = (1 × 0.4)  + (10 × 0.33) = 3.70
+Charlie: totalDistance = (1 × 0.3)  + (10 × 0.5)  = 5.30
+```
+
+**Result:** Bob (3.70) is preferred. Sharing two maps with Alice gives Bob a significant advantage, and the small skill gap with Charlie barely matters. Map preference dominates the sort order.
+
+### Example 4: When players can't match (hard rejection)
+
+Now add a fourth player, **Dave**, whose skill is far from Alice's and who shares no preferred maps:
+
+| Player | Skill | Preferred Maps |
+|--------|-------|----------------|
+| Alice | 20 | "Dustbowl," "Summit," "Lakeside" |
+| Dave | 35 | "Fortress" |
+
+**SkillRule:** `|20 - 35| / 10 = 15 / 10 = 1.5`—but the difference of 15 exceeds `MaxDifference` (10), so the rule returns **infinite distance** (hard rejection).
+
+**MapRule:** Alice and Dave share 0 maps, and `MinIntersectionSize` is 1, so this rule also returns **infinite distance**.
+
+```
+Dave: totalDistance = infinite  (skill difference 15 > MaxDifference 10 → hard rejection)
+```
+
+No matter how the weights are configured, Dave can't match with Alice. Even if only one rule returns infinite distance, the entire total distance becomes infinite and the ticket is excluded from the candidate list. Weight can't override a hard rejection—it can only influence priority among tickets that are already eligible. To allow players like Dave to eventually match, use [rule expansions](config-queues.md#expansions-and-becoming-optional) to relax the restrictions over time.
+
+### Summary of the examples
+
+The table below shows how weight changes which candidate is preferred, using the same player attributes and the same rules—only the weights differ.
+
+| Weight configuration | Bob's total distance | Charlie's total distance | Dave's total distance | Best match for Alice |
+|---|:-:|:-:|:-:|---|
+| Skill = 1, Maps = 1 (equal) | 0.73 | 0.80 | ∞ (rejected) | Bob |
+| Skill = 10, Maps = 1 (skill priority) | 4.33 | 3.50 | ∞ (rejected) | Charlie |
+| Skill = 1, Maps = 10 (map priority) | 3.70 | 5.30 | ∞ (rejected) | Bob |
+
+The underlying distances never change—only the relative importance assigned to each rule changes. Dave is always rejected because the player's attributes exceed the hard limits, regardless of weight. This approach is the power of weight tuning.
+
+## Weight and rule expansions
+
+When a rule becomes optional (through [Seconds until optional](config-queues.md#expansions-and-becoming-optional) or expansion), it no longer hard-rejects tickets. However, tickets that would be rejected still receive a nonzero distance value. Weight continues to scale this distance, which means optional rules still influence the sort order—they push "violating" tickets lower in priority rather than excluding them entirely.
+
+This behavior is useful for ensuring that even when rules relax over time, the best matches are still preferred.
+
+## Best practices
+
+- **Start with equal weights** and adjust based on match quality feedback from your players.
+- **Use higher weights** on the rules that are most important to your game's experience (such as skill for competitive titles, or shared content for casual games).
+- **Remember that weight only affects sorting**—it can't make an impossible match happen. Use [expansions](config-queues.md#expansions-and-becoming-optional) to relax hard restrictions over time.
+- **Avoid extreme weight ratios** (such as 1000:1) unless you intentionally want one rule to completely overshadow all others.
+
+## See also
+
+- [Configuring matchmaking queues](config-queues.md)
+- [Matchmaking scenario and configuration examples](config-examples.md)
+- [Specifying attributes with your tickets](ticket-attributes.md)
diff --git a/playfab-docs/multiplayer/matchmaking/toc.yml b/playfab-docs/multiplayer/matchmaking/toc.yml
index 36af65398..7c7697aa2 100644
--- a/playfab-docs/multiplayer/matchmaking/toc.yml
+++ b/playfab-docs/multiplayer/matchmaking/toc.yml
@@ -19,6 +19,10 @@ items:
     href: config-examples.md
   - name: Specifying attributes with your tickets
     href: ticket-attributes.md
+  - name: Understanding rule weight in matchmaking
+    href: rule-weights.md
+  - name: How matchmaking scales under load
+    href: matchmaking-partition.md
   - name: Using server backfill tickets - Multiplayer SDK
     href: backfill-tickets-multiplayer-sdk.md
   - name: Using server backfill tickets - REST API
@@ -31,8 +35,8 @@ items:
     href: ../lobby/lobby-and-matchmaking-client-sdk-async.md
   - name: Handling Client SDK errors
     href: ../lobby/lobby-and-matchmaking-client-sdk-errors.md
-- name: Lobby and Matchmaking real-time notifications
-  href: ../lobby/lobby-and-matchmaking-real-time-notifications.md
+- name: Lobby and Matchmaking real-time messages
+  href: ../lobby/lobby-and-matchmaking-real-time-messages.md
 - name: Reference
   items:
   - name: Client SDK reference
diff --git a/playfab-docs/multiplayer/mpintro.md b/playfab-docs/multiplayer/mpintro.md
index 8e2f76397..1a4357895 100644
--- a/playfab-docs/multiplayer/mpintro.md
+++ b/playfab-docs/multiplayer/mpintro.md
@@ -23,7 +23,7 @@ Multiplayer is a great addition to many titles, and PlayFab provides several ser
 
 While titles can use all of these services in combination, they can be used independently as well, and this is quite common. For example titles might use PlayFab matchmaking but allocate servers from an alternative multiplayer server hosting solution. Or games might use PlayFab multiplayer servers for hosting, but use their own matchmaking system to bring players together.
 
-Increasingly games are building *cross-network* experiences with players engaging each other from different identity domains (e.g. Xbox Live players interacting with Steam players interacting with custom identity systems). PlayFab's services were designed to support cross-progression and cross-network play.
+Increasingly games are building *cross-network* experiences with players engaging each other from different identity domains (for example, Xbox Live players interacting with Steam players interacting with custom identity systems). PlayFab's services were designed to support cross-progression and cross-network play.
 
 ## Example multiplayer scenarios
 
@@ -45,7 +45,7 @@ Players often want to control who they play with, preferentially selecting frien
 
 Players can also be members of multiple Lobbies at the same time. This allows you to create flexible player groupings such as allowing three friends to remain grouped as they matchmake with others over several matches. 
 
-With built-in [real-time notifications](lobby/lobby-and-matchmaking-real-time-notifications.md), members of a Lobby can receive real-time messages when changes occur such as members joining or leaving, or data being written to the Lobby. The same real-time notification mechanism can be used for cross-platform invites, allowing players to listen for an invite whether or not they are a member of a Lobby. Platforms may provide built-in invitation and presence systems that launch toasts and have other beneficial experiences (join in progress from the player profile card) that you should consider integrating if applicable.
+With built-in [real-time messages](lobby/lobby-and-matchmaking-real-time-messages.md), members of a Lobby can receive real-time messages when changes occur such as members joining or leaving, or data being written to the Lobby. The same real-time message mechanism can be used for cross-platform invites, allowing players to listen for an invite whether or not they are a member of a Lobby. Platforms may provide built-in invitation and presence systems that launch toasts and have other beneficial experiences (join in progress from the player profile card) that you should consider integrating if applicable.
 
 While you can use Lobby for signaling and other limited data-sharing, PlayFab Party is best suited for real-time data transfer and chat. PlayFab Lobby can be used to share PlayFab Party network descriptors or PlayFab multiplayer server session details to the group's data storage. This sharing of session information can allow players to join a friend's session unsolicited. If you are using non-PlayFab services for real-time networking or game hosting, those systems typically have identifying information that you can similarly signal between players using Lobby.
 
@@ -72,11 +72,11 @@ Party utilizes Azure Cognitive Services to transcribe player voice chat and synt
 
 ### Game hosting
 
-Real-time multiplayer games typically select a specific player device to host game state (aka "peer to peer") or use a dedicated multiplayer server. If hosting a game on a player device, PlayFab Party is an ideal low-latency device-to-device networking system to synchronize this game state across the session's participants.
+Real-time multiplayer games typically select a specific player device to host game state (also known as "peer to peer") or use a dedicated multiplayer server. If hosting a game on a player device, PlayFab Party is an ideal low-latency device-to-device networking system to synchronize this game state across the session's participants.
 
 It is difficult to scale peer to peer games when the device count grows. While PlayFab Party provides network encryption and uses relays to protect player IP addresses, having a device operate as host still opens avenues for cheating.
 
-PlayFab Multiplayer Servers provides simple and efficient scaling of multiplayer across Azure's global cloud. Using a small server, for example loading 10 sessions of 10 players each on a F2v2 Linux virtual machine, can efficiently and dramatically simplify your multiplayer design and improve it's reliability compared to a P2P implementation. Sophisticated multiplayer computation can be achieved by setting a server's build configuration to allocate more Azure resources to a session, perhaps using 8 or more cores for a 200 player experience.
+PlayFab Multiplayer Servers provides simple and efficient scaling of multiplayer across Azure's global cloud. Using a small server, for example loading 10 sessions of 10 players each on a F2v2 Linux virtual machine, can efficiently and dramatically simplify your multiplayer design and improve its reliability compared to a P2P implementation. Sophisticated multiplayer computation can be achieved by setting a server's build configuration to allocate more Azure resources to a session, perhaps using 8 or more cores for a 200 player experience.
 
 - [Learn more about Party](./networking/index.md)
 - [Learn more about Multiplayer Servers](./servers/index.md)
diff --git a/playfab-docs/multiplayer/networking/android-specific-requirements.md b/playfab-docs/multiplayer/networking/android-specific-requirements.md
index 254c4c103..54ba96004 100644
--- a/playfab-docs/multiplayer/networking/android-specific-requirements.md
+++ b/playfab-docs/multiplayer/networking/android-specific-requirements.md
@@ -18,7 +18,7 @@ This document lists the basic prerequisites and requirements necessary to integr
 
 Before you start this tutorial, please ensure that the following prerequisites have been met:
 
-1. You created a [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+1. You created a [PlayFab developer account](https://developer.playfab.com).
 
 1. You created a PlayFab Title and your title has been allow-listed for PlayFab Party.
 
diff --git a/playfab-docs/multiplayer/networking/apple-specific-requirements.md b/playfab-docs/multiplayer/networking/apple-specific-requirements.md
index 59ef04935..45bbd4b57 100644
--- a/playfab-docs/multiplayer/networking/apple-specific-requirements.md
+++ b/playfab-docs/multiplayer/networking/apple-specific-requirements.md
@@ -17,7 +17,7 @@ This document lists the basic prerequisites and requirements necessary to integr
 ## Prerequisites
 Before you start this tutorial, ensure that the following prerequisites have been met:
 
-1. You've created a [PlayFab developer account](https://developer.playfab.com/en-us/sign-up)
+1. You've created a [PlayFab developer account](https://developer.playfab.com)
 2. You've created a PlayFab Title and your title has been allow-listed for PlayFab Party
 3. You have Xcode version 10.2.1 or higher installed
 4. You have access to the [PlayFab Party platforms repository](https://github.com/PlayFab/PlayFabParty)
diff --git a/playfab-docs/multiplayer/networking/concepts-port-usage.md b/playfab-docs/multiplayer/networking/concepts-port-usage.md
index e99ce9d1e..d0cb5a237 100644
--- a/playfab-docs/multiplayer/networking/concepts-port-usage.md
+++ b/playfab-docs/multiplayer/networking/concepts-port-usage.md
@@ -12,11 +12,11 @@ keywords: playfab, multiplayer, networking
 
 # PlayFab Party port usage, firewall, and packet size requirements
 
-This topic provides details about Azure PlayFab Party port usage, firewall, and packet size requirements that are needed to enable chat and data communication.
+This topic provides details about PlayFab Party port usage, firewall, and packet size requirements that are needed to enable chat and data communication.
 
 ## Communication Patterns
 
-Azure PlayFab Party uses two communication patterns:
+PlayFab Party uses two communication patterns:
 
  1. HTTPS communication, which is initiated from the API caller to multiple cloud web services, including *playfabapi.com*.
 
@@ -28,7 +28,7 @@ For web service request issues, other necessary PlayFab and platform operations
 
 ## HTTPS Domain Names
 
-Microsoft Azure PlayFab Party performs UDP and HTTPS connections to multiple cloud services. To ensure correct functionality, environments that filter HTTPS traffic based on domain name need to ensure the following names or name patterns are accessible:
+Microsoft PlayFab Party performs UDP and HTTPS connections to multiple cloud services. To ensure correct functionality, environments that filter HTTPS traffic based on domain name need to ensure the following names or name patterns are accessible:
 
 HTTPS connectivity:
 * *\*.playfabapi.com*
@@ -39,7 +39,7 @@ This list of domain names can change without notice. Check this list regularly a
 
 ## MTU and packet sizes
 
-Azure PlayFab Party automatically performs fragmentation and reassembly to fit large application messages within environmental packet size limits. Some network environments can still cause communication failures despite this functionality.
+PlayFab Party automatically performs fragmentation and reassembly to fit large application messages within environmental packet size limits. Some network environments can still cause communication failures despite this functionality.
 
 PlayFab Party currently expects environments to support a Maximum Transmission Unit (MTU) size of at least 1,419 bytes to avoid poor performance or potential connectivity failures. This MTU size is supported in typical environments. Virtual Private Networks (VPNs), IPv4/IPv6 tunneling, or explicit administrative configuration might reduce the MTU size in one or both directions of the network path between the Party client, service, or other clients.
 
@@ -59,11 +59,11 @@ PlayFab Party communication always requires outbound-initiated packets and their
 
 ## Remote IP addresses and UDP ports
 
-Microsoft Azure PlayFab Party provides dynamically scaled services across multiple regions to offer the best latency to users. This means there's no permanent remote destination hostname, IP address, or port that can be referenced by network administrators interested in strict communication constraints.
+Microsoft PlayFab Party provides dynamically scaled services across multiple regions to offer the best latency to users. This means there's no permanent remote destination hostname, IP address, or port that can be referenced by network administrators interested in strict communication constraints.
 
 Microsoft provides weekly updates of an IP address range list for Azure that is [available for download](https://www.microsoft.com/download/details.aspx?id=56519). This list can be useful if a continually synchronized policy is feasible to restrict local network traffic. In most cases, the ongoing maintenance of this list is a challenge and prone to subtle connectivity failures. Also, for direct peer-to-peer connections within a Party network the remote client IP addresses also have to be known and enabled for connectivity. For these reasons we recommend firewalls not restrict remote IP address connectivity.
 
-The supported remote port range that may be in use by Azure PlayFab Party can be any ports other than the Internet Assigned Numbers Authority (IANA) reserved range of 0-1023. Currently transparent cloud relays will only be assigned port numbers from 30000-65535, but Microsoft reserves the right to change this behavior in the future. As a best practice, the port range of 1024-65535 should be used. This is particularly important for titles that are using direct peer-to-peer connections for a Party network, since NAT implementations typically assign ports from this range. Blocking remote ports other than the full recommended range may also prevent direct communication.
+The supported remote port range that may be in use by PlayFab Party can be any ports other than the Internet Assigned Numbers Authority (IANA) reserved range of 0-1023. Currently transparent cloud relays will only be assigned port numbers from 30000-65535, but Microsoft reserves the right to change this behavior in the future. As a best practice, the port range of 1024-65535 should be used. This is particularly important for titles that are using direct peer-to-peer connections for a Party network, since NAT implementations typically assign ports from this range. Blocking remote ports other than the full recommended range may also prevent direct communication.
 
 To enable UDP connectivity, environments that filter UDP traffic based on domain name need to ensure the following names or name patterns are accessible:
 
diff --git a/playfab-docs/multiplayer/networking/index.md b/playfab-docs/multiplayer/networking/index.md
index 89341d2a8..a5bc6da10 100644
--- a/playfab-docs/multiplayer/networking/index.md
+++ b/playfab-docs/multiplayer/networking/index.md
@@ -1,7 +1,7 @@
 ---
-title: Azure PlayFab Party overview
+title: PlayFab Party overview
 author: joannaleecy
-description: Learn about Azure PlayFab Party real-time chat and data communication libraries for your game.
+description: Learn about PlayFab Party real-time chat and data communication libraries for your game.
 ms.author: jenelleb
 ms.date: 10/13/2020
 ms.topic: article
@@ -10,9 +10,9 @@ keywords: playfab, multiplayer, networking, party
 ms.localizationpriority: medium
 ---
 
-# Azure PlayFab Party overview
+# PlayFab Party overview
 
-Azure PlayFab Party is a low-latency chat and data communication solution for cross-platform and cross-device multiplayer games. The voice and text features in Party can be used as a standalone chat solution.
+PlayFab Party is a low-latency chat and data communication solution for cross-platform and cross-device multiplayer games. The voice and text features in Party can be used as a standalone chat solution.
 
 For multiplayer games that use a server-client authoritative architecture to curtail competitive cheating concerns or support devices with limited resources, consider multiplayer servers like [PlayFab multiplayer servers](../servers/index.md) to host custom, dedicated game logic in a dynamically scaling cloud environment and use Party for chat communication.
 
diff --git a/playfab-docs/multiplayer/networking/media/enable-party.png b/playfab-docs/multiplayer/networking/media/enable-party.png
index 8c640ca22..127f3d917 100644
Binary files a/playfab-docs/multiplayer/networking/media/enable-party.png and b/playfab-docs/multiplayer/networking/media/enable-party.png differ
diff --git a/playfab-docs/multiplayer/networking/party-features.md b/playfab-docs/multiplayer/networking/party-features.md
index bca265d83..d9d8ba585 100644
--- a/playfab-docs/multiplayer/networking/party-features.md
+++ b/playfab-docs/multiplayer/networking/party-features.md
@@ -1,7 +1,7 @@
 ---
-title: Azure PlayFab Party features
+title: PlayFab Party features
 author: joannaleecy
-description: Learn about the features of Azure PlayFab Party.
+description: Learn about the features of PlayFab Party.
 ms.author: jenelleb
 ms.date: 10/13/2020
 ms.topic: article
@@ -10,9 +10,9 @@ keywords: playfab, multiplayer, networking, party
 ms.localizationpriority: medium
 ---
 
-# Azure PlayFab Party features
+# PlayFab Party features
 
-This topic provides details about Azure PlayFab Party features and how you can use them in your game.
+This topic provides details about PlayFab Party features and how you can use them in your game.
 
 For a high-level summary of Party features, see the [Party overview](index.md). If you're ready to start developing, see the [Party Quickstart](quickstart.md).
 
diff --git a/playfab-docs/multiplayer/networking/party-logging.md b/playfab-docs/multiplayer/networking/party-logging.md
index b63e9cee4..ce6accc10 100644
--- a/playfab-docs/multiplayer/networking/party-logging.md
+++ b/playfab-docs/multiplayer/networking/party-logging.md
@@ -1,7 +1,7 @@
 ---
-title: Diagnostic tracing/logging in Azure PlayFab Party SDKs
+title: Diagnostic tracing/logging in PlayFab Party SDKs
 author: vicodex
-description: Learn about tracing/logging in the SDKs for Azure PlayFab Party.
+description: Learn about tracing/logging in the SDKs for PlayFab Party.
 ms.author: victorku
 ms.date: 10/26/2022
 ms.topic: article
@@ -10,16 +10,16 @@ keywords: playfab, multiplayer, networking, party, sdk, sample
 ms.localizationpriority: medium
 ---
 
-# Tracing/logging instructions for Azure Playfab Party SDKs
+# Tracing/logging instructions for PlayFab Party SDKs
 
-This topic describes how to capture diagnostic traces generated by the Azure PlayFab Party SDKs.
+This article describes how to capture diagnostic traces generated by the PlayFab Party SDKs.
 
 > [!NOTE]
 > Our SDKs undergo internal testing before every release to ensure the expected level of functionality and normally don't require logging to be enabled by default, particularly in the shipping version of your game.
 >
-> However, sometimes it may be needed to capture and share produced logs with Microsoft for troubleshooting and diagnostic purposes.
+> However, sometimes it might be needed to capture and share produced logs with Microsoft for troubleshooting and diagnostic purposes.
 
-The type of logs and the way logging should be configured/captured depends on a platform. Our middleware SDKs (Unity and Unreal) use Party C++ SDKs as an underlying dependency component, and a process of configuring/capturing logs for them is the same or very similar to the process for a corresponding C++ SDK. All necessary instructions and pointers are listed in the table below:
+The type of logs and the way logging should be configured/captured depends on a platform. Our middleware SDKs (Unity and Unreal) use Party C++ SDKs as an underlying dependency component, and a process of configuring/capturing logs for them is the same or similar to the process for a corresponding C++ SDK. All necessary instructions and pointers are listed in the table below:
 
 ## Per platform logging instructions
 
@@ -27,7 +27,7 @@ The type of logs and the way logging should be configured/captured depends on a
 |------------|------------|------------|
 | Android | Plain text | See [`Logging` section of this `README.md` file](https://github.com/PlayFab/PlayFabParty#logging) and `Android` in a table under that section. |
 | iOS | Plain text | See [`Logging` section of this `README.md` file](https://github.com/PlayFab/PlayFabParty#logging) and `iOS` in a table under that section. |
-| MacOS | Plain text | See [`Logging` section of this `README.md` file](https://github.com/PlayFab/PlayFabParty#logging) and `macOS` in a table under that section. |
+| macOS | Plain text | See [`Logging` section of this `README.md` file](https://github.com/PlayFab/PlayFabParty#logging) and `macOS` in a table under that section. |
 | Linux | Plain text | See [`Logging` section of this `README.md` file](https://github.com/PlayFab/PlayFabParty#logging) and `Linux` in a table under that section. |
 | Switch | Plain text | See `Logging` section of `README.md` file included in a NuGet package for this SDK. |
 | PlayStation 4 | Plain text | See `Logging` section of `README.md` file included in a NuGet package for this SDK. |
diff --git a/playfab-docs/multiplayer/networking/party-playstream-events.md b/playfab-docs/multiplayer/networking/party-playstream-events.md
index 37784903e..84d425694 100644
--- a/playfab-docs/multiplayer/networking/party-playstream-events.md
+++ b/playfab-docs/multiplayer/networking/party-playstream-events.md
@@ -1,6 +1,6 @@
 ---
 title: PlayFab Party PlayStream Events
-description: Microsoft Azure PlayFab PlayStream events generated by the Party real-time chat and data communication API.
+description: Microsoft PlayFab PlayStream events generated by the Party real-time chat and data communication API.
 author: joannaleecy
 ms.author: jenelleb
 ms.date: 08/16/2019
diff --git a/playfab-docs/multiplayer/networking/party-samples.md b/playfab-docs/multiplayer/networking/party-samples.md
index e66836897..a38fb82fc 100644
--- a/playfab-docs/multiplayer/networking/party-samples.md
+++ b/playfab-docs/multiplayer/networking/party-samples.md
@@ -1,7 +1,7 @@
 ---
 title: Party samples
 author: joannaleecy
-description: Learn about the samples for Azure PlayFab Party.
+description: Learn about the samples for PlayFab Party.
 ms.author: jenelleb
 ms.date: 10/13/2020
 ms.topic: article
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 
 # Party samples
 
-This topic lists all the Azure PlayFab Party samples that are currently available. 
+This topic lists all the PlayFab Party samples that are currently available. 
 
 If there's a specific sample that you'd like to have, let us know by writing a post on our [forums](https://community.playfab.com/index.html).
 
diff --git a/playfab-docs/multiplayer/networking/party-sdks.md b/playfab-docs/multiplayer/networking/party-sdks.md
index b645d853c..7f75e62c5 100644
--- a/playfab-docs/multiplayer/networking/party-sdks.md
+++ b/playfab-docs/multiplayer/networking/party-sdks.md
@@ -1,7 +1,7 @@
 ---
-title: Azure PlayFab Party SDKs
+title: PlayFab Party SDKs
 author: joannaleecy
-description: Learn about the SDKs for Azure PlayFab Party.
+description: Learn about the SDKs for PlayFab Party.
 ms.author: jenelleb
 ms.date: 02/22/2021
 ms.topic: article
@@ -10,9 +10,9 @@ keywords: playfab, multiplayer, networking, party, sdk, sample
 ms.localizationpriority: medium
 ---
 
-# Azure Playfab Party SDKs
+# PlayFab Party SDKs
 
-This topic describes all the Azure PlayFab Party SDKs that are currently available.
+This topic describes all the PlayFab Party SDKs that are currently available.
 
 If you don't find what you need, let us know by writing a post on our [forums](https://community.playfab.com/index.html).
 
diff --git a/playfab-docs/multiplayer/networking/party-tutorial-requestpartyservice.md b/playfab-docs/multiplayer/networking/party-tutorial-requestpartyservice.md
index 1cec37a60..5498e1f6d 100644
--- a/playfab-docs/multiplayer/networking/party-tutorial-requestpartyservice.md
+++ b/playfab-docs/multiplayer/networking/party-tutorial-requestpartyservice.md
@@ -22,7 +22,7 @@ This tutorial describes the steps to request parties from your own services rath
 
 You need a PlayFab account and have enabled the Party feature. 
 
-1. Create or sign in to your [PlayFab account](https://playfab.com). 
+1. Create or sign in to your [PlayFab account](https://developer.playfab.com). 
 2. [Enable Party feature via Game Manager](enable-party.md) from your PlayFab account.
 3. Download and set up Party SDK. For download links, see [Party SDKs](party-sdks.md).
 
diff --git a/playfab-docs/multiplayer/networking/party-unity-plugin-quickstart.md b/playfab-docs/multiplayer/networking/party-unity-plugin-quickstart.md
index 4eb5b90e0..02a47a7b9 100644
--- a/playfab-docs/multiplayer/networking/party-unity-plugin-quickstart.md
+++ b/playfab-docs/multiplayer/networking/party-unity-plugin-quickstart.md
@@ -20,7 +20,7 @@ This quickstart helps you install the Party SDK for Unity and make your first AP
 
 ## Requirements
 
-- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A [PlayFab developer account](https://developer.playfab.com).
 - An installed copy of the Unity Editor. To install Unity for personal use via Unity Hub, or Unity+ for professional use, see [Download Unity](https://unity3d.com/get-unity/download). Check on Unity support in documentation of your specific platform if needed. The minimum supported Unity version is Unity 2017 LTS.
 - A Unity Project, which can be any of the following options:
 
diff --git a/playfab-docs/multiplayer/networking/party-unreal-engine-oss-overview.md b/playfab-docs/multiplayer/networking/party-unreal-engine-oss-overview.md
index 31fb0880f..1cbab8d83 100644
--- a/playfab-docs/multiplayer/networking/party-unreal-engine-oss-overview.md
+++ b/playfab-docs/multiplayer/networking/party-unreal-engine-oss-overview.md
@@ -52,10 +52,11 @@ PlayFab OSS works alongside the PlayFab SDK marketplace plugin, which provides o
 | 5.3          | Supported*  | Supported*  | Supported*  | Supported*  | Supported*  | Supported*  |
 | 5.4          | Supported*  | Supported*  | Supported*  | Supported*  | Supported*  | Supported*  |
 | 5.5          | Supported*  | Supported*  | Supported*  | Supported*  | Supported*  | Supported*  |
-| 5.6          | Supported   | Supported   | Supported   | Supported   | Supported   | Supported   |
+| 5.6          | Supported*  | Supported*  | Supported*  | Supported*  | Supported*  | Supported*  |
+| 5.7          | Supported   | Supported   | Supported   | Supported   | Supported   | Supported   |
 
-*For users on previous versions of Unreal Engine (UE4.27, 5.0, 5.1, 5.2, 5.3, and 5.4) who wish to use PlayFab Online Subsystem, here are two options:
-- Upgrade your local Unreal Engine version to 5.6.
+*For users on previous versions of Unreal Engine (UE4.27, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 and 5.6) who wish to use PlayFab Online Subsystem, here are two options:
+- Upgrade your local Unreal Engine version to 5.7.
 - Pull the latest release and backport it to your game.
 For UE4, 4.27 is the recommended version since crossplay between different platforms doesn't work on 4.26, but it does on 4.27. If you're on an earlier version of Unreal Engine 4, the OSS can be backported with minimal work. See [Using older versions of Unreal Engine 4](party-unreal-engine-using-older-versions.md) for more details.
 
@@ -81,7 +82,7 @@ The supported Nintendo Switch SDK versions can be found at [Switch SDK Updates P
 - UE5.0: \Engine\Platforms\Switch\Source\Programs\UnrealBuildTool\SwitchPlatformSDK.cs
 - UE5.1, UE5.2 and UE5.3: \Engine\Platforms\Switch\Source\Programs\UnrealBuildTool\SwitchPlatformSDK.Versions.cs
 - UE5.4: \Engine\Platforms\Switch\Config\Switch_SDK.json
-- UE5.5 and UE5.6: \Engine\Platforms\Nintendo\Config\Nintendo_SDK.json
+- UE5.5, UE5.6 and UE5.7: \Engine\Platforms\Nintendo\Config\Nintendo_SDK.json
 
 ## Which version of the PS5™ and PS4™ SDKs are supported?
 
@@ -89,7 +90,7 @@ The supported Sony PlayStation SDK versions can be found at [PS4 SDK Compatibili
 - UE4: \Engine\Platforms\[PS4|PS5]\Source\Programs\UnrealBuildTool\UEBuild[PS4|PS5].cs
 - UE5.0: \Engine\Platforms\[PS4|PS5]\Source\Programs\UnrealBuildTool\[PS4|PS5]PlatformSDK.cs
 - UE5.1, UE5.2 and UE5.3: \Engine\Platforms\[PS4|PS5]\Source\Programs\UnrealBuildTool\[PS4|PS5]PlatformSDK.Versions.cs
-- UE5.4, UE5.5 and UE5.6: \Engine\Platforms\[PS4|PS5]\Config\[PS4|PS5]_SDK.json
+- UE5.4, UE5.5, UE5.6 and UE5.7: \Engine\Platforms\[PS4|PS5]\Config\[PS4|PS5]_SDK.json
 
 >[!NOTE]
 > In order to access Unreal’s documentation and UDN forum links above, you must be a registered Unreal Developer and tented for the specific platform.
diff --git a/playfab-docs/multiplayer/networking/party-unreal-engine-oss-quickstart.md b/playfab-docs/multiplayer/networking/party-unreal-engine-oss-quickstart.md
index 4f491b96b..2793b06dd 100644
--- a/playfab-docs/multiplayer/networking/party-unreal-engine-oss-quickstart.md
+++ b/playfab-docs/multiplayer/networking/party-unreal-engine-oss-quickstart.md
@@ -11,7 +11,7 @@ keywords: playfab, multiplayer, networking, unreal, unreal engine, unreal engine
 
 # QuickStart: PlayFab Online Subsystem
 
-This article helps you set up and use Azure PlayFab Multiplayer features like Lobby, Matchmaking, and Party for games built with Unreal Engine 4 or Unreal Engine 5. For the full list of supported platforms and versions in Unreal Engine 4 or Unreal Engine 5, see [Supported platforms](party-unreal-engine-oss-overview.md).
+This article helps you set up and use PlayFab Multiplayer features like Lobby, Matchmaking, and Party for games built with Unreal Engine 4 or Unreal Engine 5. For the full list of supported platforms and versions in Unreal Engine 4 or Unreal Engine 5, see [Supported platforms](party-unreal-engine-oss-overview.md).
 
 After following the relevant steps that are outlined in this page for your target platforms, you'll be ready to start using the PlayFab Online Subsystem (PF OSS). Authentication, networking, VOIP, grouping into lobbies, and matchmaking is handled on your behalf with no other changes required.
 
@@ -232,7 +232,7 @@ Ways to help you troubleshoot issues.
 
 Users might face issues when trying to create an Unreal Engine Installed Build with the OnlineSubsystemPlayFab on GDK build flavors. We provide the following guidance to successfully overcome this issue until there's a more complete solution.
 
-**If you're using Unreal Engine 5.4, 5.5 or 5.6:**
+**If you're using Unreal Engine 5.4, 5.5, 5.6 or 5.7:**
 
 * You might encounter the following runtime error: `Runtime dependency Party.dll is configured to be staged from C:\Program Files (x86)\Microsoft GDK\<version>\Party.dll and Engine\Plugins\Online\OnlineSubsystemPlayFab\Platforms\GDK\Redist\Party.dll`
 * Navigate to Engine\Platforms\GDK\Plugins\Online\OnlineSubsystemGDK\
diff --git a/playfab-docs/multiplayer/networking/quickstart.md b/playfab-docs/multiplayer/networking/quickstart.md
index e328f79b1..b9c65034f 100644
--- a/playfab-docs/multiplayer/networking/quickstart.md
+++ b/playfab-docs/multiplayer/networking/quickstart.md
@@ -26,7 +26,7 @@ For a deeper understanding, consult the linked reference and conceptual document
 
 You need a PlayFab account, and you *must enable* the Party feature to start using Party. 
 
-1. Create or sign in to your [PlayFab account](https://playfab.com). For instructions, see [Quickstart: Game Manager](../../live-service-management/gamemanager/quickstart.md).
+1. Create or sign in to your [PlayFab account](https://developer.playfab.com). For instructions, see [Quickstart: Game Manager](../../live-service-management/gamemanager/quickstart.md).
 1. [Enable Party feature via Game Manager](enable-party.md) from your PlayFab account.
 
 ## Platform Prerequisites
@@ -293,7 +293,7 @@ At this point, you have a party network descriptor and are ready to share it wit
 ### Use PlayFab Lobby to share the Party network descriptor
 
 PlayFab Lobby can be used to temporarily group players as they move into and out of matches and can be used to synchronize the network descriptor so that players can join the same network. 
-PlayFab Lobby is highly customizable to support a wide variety of gameplay needs on all supported platforms and across platforms. Refer to the [Multiplayer SDK Quickstart](../lobby/lobby-getting-started.md) for more detail about using PlayFab Lobby with real-time notifications.
+PlayFab Lobby is highly customizable to support a wide variety of gameplay needs on all supported platforms and across platforms. Refer to the [Multiplayer SDK Quickstart](../lobby/lobby-getting-started.md) for more detail about using PlayFab Lobby with real-time messages.
 
 For details about using PlayFab Lobby together with PlayFab Party, refer to [Create a lobby with PlayFab Multiplayer SDK](party-lobby-integration.md).
 
diff --git a/playfab-docs/multiplayer/networking/reference/partyerrors.md b/playfab-docs/multiplayer/networking/reference/partyerrors.md
index 55351e44a..400a2a3cd 100644
--- a/playfab-docs/multiplayer/networking/reference/partyerrors.md
+++ b/playfab-docs/multiplayer/networking/reference/partyerrors.md
@@ -5,7 +5,7 @@ description: Error codes used by PlayFab Party APIs
 ms.author: scmunro
 ms.topic: reference
 ms.service: azure-playfab
-ms.date: 08/11/2022
+ms.date: 01/25/2026
 ---
 
 # PlayFab Party Error Codes
@@ -153,8 +153,6 @@ The following error codes are used by the PlayFab Party APIs:
 | 0x1058 | 4184 | The provided target chat control list contained at least one duplicate chat control. |
 | 0x1059 | 4185 | The provided target endpoint list contained at least one duplicate endpoint. |
 | 0x105A | 4186 | A platform error resulted in failure to determine the preferred UI language. |
-| 0x105B | 4187 | XAudio 2.7 debug version not installed on system (install the DirectX SDK Developer Runtime). |
-| 0x105C | 4188 | XAudio 2.7 not installed on system (install the DirectX End-user Runtimes (June 2010)). |
 | 0x105E | 4190 | Authentication was attempted for a user that is already authenticated. |
 | 0x1062 | 4194 | The text-to-speech synthesis request was rejected by the service for being too large. |
 | 0x1063 | 4195 | The text-to-speech synthesis request was throttled. |
@@ -264,6 +262,7 @@ The following error codes are used by the PlayFab Party APIs:
 | 0x112C | 4396 | The region quality measurement minimum required successful responses value is invalid. |
 | 0x112D | 4397 | The region quality measurement ideal number of successful responses value is invalid. |
 | 0x1136 | 4406 | The network is being destroyed because it is idle. |
+| 0x113C | 4412 | The user default platform audio device monitor is uninitialized; it may have failed or be unsupported on this platform. |
 
 ## Platform-specific errors
 | Hex | Dec | Description |
@@ -293,7 +292,6 @@ The following error codes are used by the PlayFab Party APIs:
 | 0x301C | 12316 | A user matching the ID wasn't found in the Microsoft gaming runtime. |
 | 0x301D | 12317 | There isn't a default user for the Microsoft gaming runtime. |
 | 0x301E | 12318 | The Microsoft gaming runtime failed to resolve a required user privilege. |
-| 0x301F | 12319 | The Microsoft gaming XNetworking feature is unavailable. |
 | 0x3020 | 12320 | The network stack must be initialized before calling PartyManager::Initialize(); use the Microsoft Game Core XNetworkingGetConnectivityHint API to determine when the network stack is initialized. |
 | 0x3021 | 12321 | Callers must pass a port value of 0 when the PartyLocalUdpSocketBindAddressOptions::ExcludeGameCorePreferredUdpMultiplayerPort option is set. |
 | 0x3022 | 12322 | It's invalid to pass PartyLocalUdpSocketBindAddressOptions::ExcludeGameCorePreferredUdpMultiplayerPort in all versions of PlayFab Party except for the Microsoft Game Core version. |
diff --git a/playfab-docs/multiplayer/networking/release-notes.md b/playfab-docs/multiplayer/networking/release-notes.md
index bb4ea91ce..5a5fd99d7 100644
--- a/playfab-docs/multiplayer/networking/release-notes.md
+++ b/playfab-docs/multiplayer/networking/release-notes.md
@@ -13,19 +13,64 @@ ms.localizationpriority: medium
 # PlayFab Party Release Notes
 
 > [!NOTE]
-> Support for the XDK and Windows 7 platforms ended on August 1, 2023. No new PlayFab Party library updates will be released for those platforms. The PlayFab Party networking and voice services will continue to operate with no impact to any titles currently using Windows 7 or XDK versions of the PlayFab Party library.
-> 
->For more information, please see our [forum post](https://community.playfab.com/articles/141546/playfab-party-ending-support-for-the-xdk-and-windo.html).
+> Support for the XDK and Windows 7 platforms ended on August 1, 2023. No new PlayFab Party library updates will be released for those platforms. The PlayFab Party networking and voice services continue to operate with no impact to any titles currently using Windows 7 or XDK versions of the PlayFab Party library.
 
 > [!NOTE]
-> Support for 32-bit Android platforms (arm7 and x86) ended on October 19th, 2023. No new PlayFab Party library updates will be released for those platforms. The PlayFab Party networking and voice services will continue to operate with no impact to any titles currently using the PlayFab Party library on 32-bit Android platforms.
+> Support for 32-bit Android platforms (arm7 and x86) ended on October 19, 2023. No new PlayFab Party library updates will be released for those platforms. The PlayFab Party networking and voice services will continue to operate with no impact to any titles currently using the PlayFab Party library on 32-bit Android platforms.
+
+## 1.10.18
+
+March 26, 2026
+
+-  Improved Linux linker hardening for PlayFab Party.
+
+## 1.10.17
+
+February 23, 2026
+
+- Android: Fix Bluetooth microphones not working.
+- Linux: Remove SafeStack.
+- Apple: Hide OpenSSL symbols from Party.
+- Nintendo Switch 2: Resolved TCP connection error when IP changes.
+
+## 1.10.16
+
+February 2, 2026
+
+- GDK: Added support for environments that use in-proc GRTS.
+- GDK: Added support for [`PartyAudioDeviceSelectionType::SystemDefault`](reference/enums/partyaudiodeviceselectiontype.md).
+
+### Bug fixes
+
+- Fixed possible crash in multinetwork transition scenarios. 
+
+## 1.10.15
+
+December 17, 2025
+
+- Nintendo Switch 2: Added 10-second timeout for web requests.
+
+## 1.10.14
+
+December 9, 2025
+
+- Changed the [`PartyNetwork::CreateEndpoint`](reference/classes/PartyNetwork/methods/partynetwork_createendpoint.md) PartyStatusChangeResult behavior to return `PartyServiceError` for transient errors that occur before the token expires, and to return `UserNotAuthorized` only when the token has expired.
+- Android: Added support for 16-KB page sizes to satisfy the new [Android page size requirements](https://developer.android.com/guide/practices/page-sizes).
+
+
+## 1.10.13
+
+October 14, 2025
+
+- Fixed an issue that caused the microphone to not function properly on iOS 26.
+- Apple: Added support for Arm64.xcframework on iOS.
 
 ## 1.10.12
 
 October 6, 2025
 
-- Changed the [`PartyNetwork::CreateEndpoint`](reference/classes/PartyNetwork/methods/partynetwork_createendpoint.md) PartyStatusChangeResult behavior to return `PartyServiceError` for transient errors that occur before the token expires, and to return `UserNotAuthorized` only when the token has actually expired.
-- Android: Added support for 16 KB page sizes to satisfy the new [Android page size requirements](https://developer.android.com/guide/practices/page-sizes).
+- Changed the [`PartyNetwork::CreateEndpoint`](reference/classes/PartyNetwork/methods/partynetwork_createendpoint.md) PartyStatusChangeResult behavior to return `PartyServiceError` for transient errors that occur before the token expires, and to return `UserNotAuthorized` only when the token has expired.
+- Android: Added support for 16-KB page sizes to satisfy the new [Android page size requirements](https://developer.android.com/guide/practices/page-sizes).
 - Apple: Added support for Arm64 simulator builds on iOS.
 
 ### Bug fixes
@@ -45,34 +90,34 @@ March 11, 2025
 
 January 24, 2025
 
-- PlayStation&#174;4 and, PlayStation&#174;5: Resolved a crash related to profanity masking on PlayStation platforms.
+- PlayStation&#174;4 and PlayStation&#174;5: Resolved a crash related to profanity masking on PlayStation platforms.
 
 ## 1.10.6
 
 December 10, 2024
 
-- PlayStation&#174;4 and, PlayStation&#174;5: Resolved build warnings and errors for integration with C++14 and above.
+- PlayStation&#174;4 and PlayStation&#174;5: Resolved build warnings and errors for integration with C++14 and later versions.
 
 ## 1.10.5
 
 November 18, 2024
 
-- Fixed an issue where voice chat would sometimes not work for users remaining in a Party network after other users rejoined and left multiple times.
+- Fixed an issue where voice chat sometimes didn't work for users who stayed in a Party network after other users rejoined and left multiple times.
 - Fixed an issue where [PartyLocalEndpoint::GetEndpointStatistics](reference/classes/PartyLocalEndpoint/methods/partylocalendpoint_getendpointstatistics.md) would report incorrect values for [PartyEndpointStatistic::CurrentlyQueuedSendMessages](reference/enums/partyendpointstatistic.md) and [PartyEndpointStatistic::CurrentlyQueuedSendMessageBytes](reference/enums/partyendpointstatistic.md) when used with direct peer connections.
-- Fixed broken symlinks for the framework on the macOS.
-- Improved handling log exceptions for non Windows platforms during collection of SDK logs.
+- Fixed broken symlinks for the framework on macOS.
+- Improved handling of log exceptions for non-Windows platforms during collection of SDK logs.
 
 ## 1.10.4
 
 November 12, 2024
 
-- PlayStation&#174;4 and, PlayStation&#174;5: Resolved crashes related to mutex operations and endpoint state changes during creation and destruction.
+- PlayStation&#174;4 and PlayStation&#174;5: Resolved crashes related to mutex operations and endpoint state changes during creation and destruction.
 
 ## 1.10.3
 
 October 14, 2024
 
-- Added support for up to 128 devices per network. For more details, see [Scalable networks](party-features.md#scalable-networks-up-to-128-devices-per-network).
+- Added support for up to 128 devices per network. For more information, see [Scalable networks](party-features.md#scalable-networks-up-to-128-devices-per-network).
 - Increased `c_maxNetworkConfigurationMaxDeviceCount` from 32 to 128.
 - Updated internal diagnostics.
 - Updated build settings for security hardening.
@@ -84,27 +129,27 @@ September 18, 2024
 
 ### Bug fixes
 
-- Fixed an issue where the library may crash when establishing direct peer connections in networks with three or more devices.
+- Fixed an issue where the library might crash when it establishes direct peer connections in networks with three or more devices.
 
 ## 1.10.0
 
 August 5, 2024
 
-- Added support for game_server entities, so servers can connect to Party networks via the SDK and be securely identified by game clients. After authenticating a `game_server` entity via AuthenticateGameServerWithCustomId, it can be added as a local user via [PartyManager::CreateLocalUserWithEntityType](reference/classes/PartyManager/methods/partymanager_createlocaluserwithentitytype.md).
+- Added support for `game_server` entities, so servers can connect to Party networks via the SDK and be securely identified by game clients. After authenticating a `game_server` entity via `AuthenticateGameServerWithCustomId`, it can be added as a local user via [PartyManager::CreateLocalUserWithEntityType](reference/classes/PartyManager/methods/partymanager_createlocaluserwithentitytype.md).
 - Added methods for determining the entity type associated with each entity in the library. For more information, see [PartyLocalUser::GetEntityType](reference/classes/PartyLocalUser/methods/partylocaluser_getentitytype.md), [PartyEndpoint::GetEntityType](reference/classes/PartyEndpoint/methods/partyendpoint_getentitytype.md), and [PartyChatControl::GetEntityType](reference/classes/PartyChatControl/methods/partychatcontrol_getentitytype.md).
 - Added a direct peer connectivity option that enables direct peer connections between `title_player` and `game_server` entities while disallowing direct peer connections between `title_player` entities and other `title_player` entities. For more information, see [PartyDirectPeerConnectivityOptions::OnlyServers](reference/enums/partydirectpeerconnectivityoptions.md).
 - Added methods to retrieve a convenient list of endpoints based on filters. For more information, see [PartyNetwork::GetEndpointsByUserType](reference/classes/PartyNetwork/methods/partynetwork_getendpointsbyusertype.md).
-- Memory allocations by third party libraries used in PlayFab Party on PlayStation&#174;4 and, PlayStation&#174;5 that were using default allocators have been updated to use Party's memory callbacks. Titles using [PartyManager::SetMemoryCallbacks](reference/classes/PartyManager/methods/partymanager_setmemorycallbacks.md) to configure title-specific memory allocation functions allocations will now see and have control over these allocations.
+- Updated memory allocations by third party libraries used in PlayFab Party on PlayStation&#174;4 and, PlayStation&#174;5 that were using default allocators have been updated to use Party's memory callbacks. Titles using [PartyManager::SetMemoryCallbacks](reference/classes/PartyManager/methods/partymanager_setmemorycallbacks.md) to configure title-specific memory allocation functions allocations will now see and have control over these allocations.
 
 ### Bug fixes
 
-- Fixed an issue where the library may crash on Windows or Xbox while the process is terminating.
+- Fixed an issue where the library might crash on Windows or Xbox while the process is terminating.
 - Addressed spurious direct peer connection failures after a previous connection attempt failed in certain cases for non Windows platforms.
-- Fixed an issue where the DestroyNetwork event was not fired during repeated Party network creation and destroying.
+- Fixed an issue where the DestroyNetwork event wasn't fired during repeated Party network creation and destroying.
 
 ### Known issues
 
-- The library may occasionally crash when establishing direct peer connections in networks with three or more devices.
+- The library might occasionally crash when establishing direct peer connections in networks with three or more devices.
 
 ## 1.9.5
 
@@ -147,13 +192,13 @@ February 5, 2024
 
 November 13, 2023
 
-- Fixed a bug where a crash may occur when a client tries to leave a network on Nintendo Switch.
+- Fixed a bug where a crash might occur when a client tries to leave a network on Nintendo Switch.
 
 ## 1.8.10
 
 October 19, 2023
 
-This release updates the minimum SDK versioning and target SDK versioning for PlayFab Party Apple and Android platforms.
+This release updates the minimum SDK version and target SDK version for PlayFab Party Apple and Android platforms.
 
 For Apple platforms, we follow [Apple's Xcode guidelines](https://developer.apple.com/support/xcode/) with the release of Xcode 15.
 - iOS
@@ -171,7 +216,7 @@ For Android platforms, we follow [Google's target API guidelines](https://develo
     - The Compile SDK Version has been increased from Android API 28 to Android API 34.
     - Support for 32-bit Android platforms (arm7 and x86) ended on October 19, 2023. No new PlayFab Party library updates will be released for those platforms. The PlayFab Party networking and voice services will continue to operate with no impact to any titles currently using the PlayFab Party library on 32-bit Android platforms.
 
-If you experience any issues with integrating these packages, [please file a PlayFab Support Ticket](../../pricing/Support.md).
+If you experience any issues with integrating these packages, [please file a PlayFab Support Ticket](../../pricing/support.md).
 
 ## 1.8.9
 
@@ -180,7 +225,7 @@ October 20, 2023
 - Implemented shared properties for endpoints. Shared properties may be set when creating an endpoint via
 [`PartyNetwork::CreateEndpoint`](reference/classes/PartyNetwork/methods/partynetwork_createendpoint.md). A shared
 property may be retrieved using [`PartyEndpoint::GetSharedProperty`](reference/classes/PartyEndpoint/methods/partyendpoint_getsharedproperty.md).
-- Improved audio packet queueing to reduce perceived chat audio latency in some scenarios.
+- Improved audio packet queuing to reduce perceived chat audio latency in some scenarios.
 - Upgraded internal version of the Opus codec.
 - Fixed a low frequency crash.
 - Improved internal diagnostics.
@@ -196,7 +241,7 @@ June 28, 2023
 
 ### Bug fixes
 
-- Fixed a bug where [`PartyLocalChatControl::SetAudioRenderVolume`](reference/classes/PartyLocalChatControl/methods/partylocalchatcontrol_setaudiorendervolume.md) would not properly work for Nintendo Switch, PlayStation&#174;4 and, PlayStation&#174;5.
+- Fixed a bug where [`PartyLocalChatControl::SetAudioRenderVolume`](reference/classes/PartyLocalChatControl/methods/partylocalchatcontrol_setaudiorendervolume.md) wouldn't properly work for Nintendo Switch, PlayStation&#174;4 and, PlayStation&#174;5.
 
 “PlayStation” is a registered trademark or trademark of Sony Interactive Entertainment Inc.
 
@@ -221,7 +266,7 @@ May 8, 2023
 - iOS, Android: Added support for enabling noise suppression on audio captured from a local chat control. For more information, see [`PartyLocalChatControl::SetVoiceAudioOptions`](reference/classes/PartyLocalChatControl/methods/partylocalchatcontrol_setvoiceaudiooptions.md).
 
 ### Bug fixes
-- Fixed a bug where the library may leak memory due to internal diagnostic tracking when the user's entity token expires.
+- Fixed a bug where the library could leak memory due to internal diagnostic tracking when the user's entity token expires.
 
 ## 1.7.23
 
@@ -234,8 +279,8 @@ April 1, 2023
 March 30, 2023
 
 ### Bug fixes
-- Fixed a bug where Party could crash if it was not cleaned up before the host process started exiting.
-- Changed behavior for peer-to-peer connection to fallback to a relayed connection if the link is disconnected unexpectedly. The previous behavior would disconnect both the devices from the network.
+- Fixed a bug where Party could crash if it wasn't cleaned up before the host process started exiting.
+- Changed behavior for peer-to-peer connection to fall back to a relayed connection if the link is disconnected unexpectedly. The previous behavior would disconnect both the devices from the network.
 
 ## 1.7.20
 
@@ -243,7 +288,7 @@ February 8, 2023
 
 ### Bug fixes
 
-- Fixed a bug where audio from 44.1 kHz microphones may sound distorted. 
+- Fixed a bug where audio from 44.1-kHz microphones may sound distorted. 
 - Improved diagnostic error messages for network errors reported by [PartyManager::GetErrorMessage()](reference/classes/PartyManager/methods/partymanager_geterrormessage.md).
 
 ## 1.7.19
@@ -260,8 +305,8 @@ October 7, 2022
 
 ### Bug fixes
 
-- Fixed a bug where a crash may occur when a chat control is connect to a network on iOS. 
-- Fixed a bug where a crash may occur when enabling iOS log.
+- Fixed a bug where a crash might occur when a chat control is connected to a network on iOS. 
+- Fixed a bug where a crash might occur when enabling iOS log.
 
 ## 1.7.16
 
@@ -272,7 +317,7 @@ September 27, 2022
 - Added .bundle for Unity plug-in loading and native macOS development.
 
 ### Bug fixes
-- Fixed a bug where a crash may occur when enabling macOS log.
+- Fixed a bug where a crash might occur when enabling macOS log.
 
 ## 1.7.14
 
@@ -280,7 +325,7 @@ August 12, 2022
 
 ### New SDKs for Linux and macOS
 
-- Added native support for PlayFab Party on Linux and macOS, enabling game developers to create cross-platform or multiplatform real-time multiplayer experiences on even more platforms. For links to these and other SDK releases,see [Azure Playfab Party SDKs](party-sdks.md).
+- Added native support for PlayFab Party on Linux and macOS, enabling game developers to create cross-platform or multiplatform real-time multiplayer experiences on even more platforms. For links to these and other SDK releases, see [PlayFab Party SDKs](party-sdks.md).
 
 August 11, 2022
 
@@ -323,8 +368,8 @@ February 8, 2022
 September 30, 2021
 ### Bug fixes
 
-- Fixed an issue where some 16kHz microphones weren't working.
-- Fixed an issue where microphone permission changes were not handled on Windows.
+- Fixed an issue where some 16 kHz microphones weren't working.
+- Fixed an issue where microphone permission changes weren't handled on Windows.
 - Fixed a memory leak in some `PartyManager::CreateNewNetwork()` failure conditions.
 - Fixed an occasional crash in `PartyLocalEndpoint::GetEndpointStatistics()`.
 
@@ -344,13 +389,13 @@ June 29, 2021
 
 ### Bug fixes
 
-- Fixed a bug where a crash may occur when a chat control is connected to a network while that same chat control is disconnecting from another network.
+- Fixed a bug where a crash might occur when a chat control connects to a network while that same chat control is disconnecting from another network.
 
 ## 1.6.0
 April 12, 2021
 ### New thread control and text moderation features
 
-- The library's work can now be run manually on game-controlled threads. For more information, see [`PartyManager::SetWorkMode`](reference/classes/PartyManager/methods/partymanager_setworkmode.md).
+- The library's work can now run manually on game-controlled threads. For more information, see [`PartyManager::SetWorkMode`](reference/classes/PartyManager/methods/partymanager_setworkmode.md).
 - Offensive text chat can now optionally be filtered. For more information, see [Using text moderation](../../community/voice-communications/concepts-text-moderation.md).
 
 ### Explicit enum numbering in the header
@@ -361,26 +406,27 @@ April 12, 2021
 March 26, 2021
 ### Bug fixes
 
-- Fixed a bug where audio is cutting out on iOS devices using Bluetooth headsets.
+- Fixed a bug where audio cuts out on iOS devices using Bluetooth headsets.
 - Fixed a bug where an incorrect error code is generated when the app doesn't have permission to activate a microphone on Windows platforms.
-- Fixed a bug where an unhealthy device is never refreshed unless something else forces a refresh.
-- Fixed a bug where a crash may occur when dereferencing a send channel's user data after the source endpoint associated with that channel has become invalid.
+- Fixed a bug where an unhealthy device isn't refreshed unless something else forces a refresh.
+- Fixed a bug where a crash might occur when dereferencing a send channel's user data after the source endpoint associated with that channel becomes invalid.
 - Fixed a bug where clients experience silent failures if a remote chat control doesn't have a language code.
 
 ## 1.5.10
 
 ### Bug fixes
 
-- Fixed a bug where the library may fail to initialize on some Windows devices due to a mismatch between the processor affinity of the process and the library's default thread affinity.
-- Fixed a bug where the library may not provide errors when an operation fails due to an internal web request failure.
-- Fixed a bug where a crash may occur when direct peer connectivity is enabled and the library attempts to establish direct peer connectivity to another device.
-- Fixed a bug that may result in crackling or distorted audio.
+- Fixed a bug where the library might fail to initialize on some Windows devices due to a mismatch between the processor affinity of the process and the library's default thread affinity.
+- Fixed a bug where the library might not provide errors when an operation fails due to an internal web request failure.
+- Fixed a bug where a crash might occur when direct peer connectivity is enabled and the library attempts to establish direct peer connectivity to another device.
+- Fixed a bug that might result in crackling or distorted audio.
 
 ## 1.5.1
 September 05, 2020
+
 ### Bug fix
 
-- Fixed a bug where the library may fail to activate the microphone on iOS.
+- Fixed a bug where the library fails to activate the microphone on iOS.
 
 ## 1.5.0
 
@@ -408,7 +454,7 @@ April 30, 2020
 - The transcription stack has been updated to use TLS1.2 on Windows 7, Android, and iOS. Upgrade if you make use of any of these platforms as TLS1.1 support will be deprecated by [Azure Speech Services](https://azure.microsoft.com/updates/azuretls12/) beginning in September 2020. All other platforms already support TLS1.2 and no upgrade is necessary.
 
 ### Bug fixes
-- Fixed a bug where the `languageCode` field in the `PartyCreateChatControlCompletedStateChange` struct was not being populated.
+- Fixed a bug where the `languageCode` field in the `PartyCreateChatControlCompletedStateChange` struct wasn't being populated.
 - Fixed a bug that was artificially inflating the latency measurements reported by `PartyManager::GetRegions()`.
 - Fixed a bug that allowed `PartyManager::SetMemoryCallbacks()` to be called at unsafe times.
 - Fixed a bug where calling `PartyManager::DestroyLocalUser()` with a `PartyLocalUser` in a `PartyNetwork` would generate a `PartyLocalUserRemovedStateChange` with an incorrect value in the removedReason field, `PartyLocalUserRemovedReason::RemoveLocalUser`, instead of the correct value, `PartyLocalUserRemovedReason::DestroyLocalUser`.
@@ -421,12 +467,12 @@ April 30, 2020
 - Typos in the header documentation have been fixed.
 - A more descriptive error code and error message are now provided when an invalid region is passed to `PartyManager::CreateNewNetwork()`.
 - The documentation for the lifetimes of `PartyString` values has been clarified for the structures and interfaces in Party.h.
-- The documentation for `PartyManager::Cleanup()` was clarified to explain it is not a thread-safe call.
+- The documentation for `PartyManager::Cleanup()` was clarified to explain it isn't a thread-safe call.
 - A more descriptive error code and error message are provided when `PartyManager::ConnectToNetwork()` asynchronously fails with internet connectivity errors.
 
 ## 1.3.0
 
-### Chat API Changes
+### Chat API changes
 
 * The real-time audio manipulation functions, which can be used to modify outgoing or incoming voice chat audio, are implemented for Windows and Xbox. For more information, see [Using real-time audio manipulation to apply custom voice effects](../../community/voice-communications/concepts-realtime-audio-manipulation.md).
 * The chat permission options have more options for optionally configuring text-to-speech and microphone audio permissions independently. For more information, see [`PartyChatPermissionOptions`](reference/enums/partychatpermissionoptions.md).
@@ -436,24 +482,24 @@ April 30, 2020
 
 ## 1.2.2
 
-### iOS Changes
+### iOS changes
 
 - Adds support for the volume control API.
 
 ## 1.2.0
 
-### Android Changes
+### Android changes
 
 - Adds support for the volume control API.
-- Removes audio focus handling from the library.  Host applications are now expected to implement their own focus handling logic.
+- Removes audio focus handling from the library. Host applications are now expected to implement their own focus handling logic.
 
 ## 1.0.2
 
-- Fixed crash in background telemetry
+- Fixed crash in background telemetry.
 
 ## 1.0.1
 
-### Party API Changes
+### Party API changes
 
 #### PartyManager::SetMemoryCallbacks Changes
 
@@ -465,27 +511,27 @@ The `PartyStateChangeResult` value `TitleCreateNetworkThrottled` has been remove
 
 ## 0.7.0-prerelease
 
-### Windows Packaging Changes
+### Windows packaging changes
 
 This release of Party introduces a new NuGet package, [Microsoft.PlayFab.PlayFabParty.Cpp.Windows](https://www.nuget.org/packages/Microsoft.PlayFab.PlayFabParty.Cpp.Windows), which replaces and deprecates the NuGet packages specific to Windows 10 and Windows 7 (Microsoft.PlayFab.PlayFabParty.Cpp.Win10 and Microsoft.PlayFab.PlayFabParty.Cpp.Win7, respectively). The new unified Windows NuGet package contains two new DLLs, PartyWin.dll (supports Windows 8.1 and up) and PartyWin7.dll (only for use on Windows 7). With the new Windows unified NuGet package, the correct Party DLL is loaded based on runtime detection of the OS version, so both PartyWin.dll and PartyWin7.dll should be included in the game distribution package.
 
-### Android Changes
+### Android changes
 
 The Android flavor now uses a shared object for Party (libparty.so) instead of a static library (libparty.a).
 
 This release also contains Android-specific bug fixes for audio device selection.
 
-### iOS Changes
+### iOS changes
 
 The iOS flavor of Party now has the framework package included for dynamically loading libparty instead of the statically built libparty.a.
 
-### API Changes
+### API changes
 
 #### UpdateEntityToken API
 
 This release of Party makes a change related to the handling of PlayFab entity tokens. In the previous version, the game provided Party with a user's entity token in the `PartyManager::CreateLocalUser()` API. Thereafter, Party internally refreshed the entity token and kept it up to date.
 
-In this version, the internal token refreshing behavior has been removed and replaced by a new API, `PartyLocalUser::UpdateEntityToken()`. The caller is now responsible for monitoring the expiration of the entity token provided to `PartyManager::CreateLocalUser()` and `PartyLocalUser::UpdateEntityToken()`. When the token is nearing or past the expiration time, a new token should be obtained by performing a PlayFab login operation and provided to the Party library by calling `PartyLocalUser::UpdateEntityToken()`. It is recommended to acquire a new token when the previously supplied token is halfway through its validity period. On platforms that may enter a low power state or pause application execution for a long time, the token may be prevented from being refreshed before it expires. The token should be checked for expiration once execution resumes.
+In this version, the internal token refreshing behavior has been removed and replaced by a new API, `PartyLocalUser::UpdateEntityToken()`. The caller is now responsible for monitoring the expiration of the entity token provided to `PartyManager::CreateLocalUser()` and `PartyLocalUser::UpdateEntityToken()`. When the token is nearing or past the expiration time, a new token should be obtained by performing a PlayFab login operation and provided to the Party library by calling `PartyLocalUser::UpdateEntityToken()`. It's recommended to acquire a new token when the previously supplied token is halfway through its validity period. On platforms that enter a low power state or pause application execution for a long time, the token might be prevented from being refreshed before it expires. The token should be checked for expiration once execution resumes.
 
 The rough flow is as follows:
 
@@ -497,14 +543,14 @@ The rough flow is as follows:
 1. [New] Call `PartyLocalUser::UpdateEntityToken()` to pass in the new token to Party
 
 Additional notes:
-- The act of acquiring an entity token does not invalidate any previously obtained entity tokens. They remain valid until they expire.
+- The act of acquiring an entity token doesn't invalidate any previously obtained entity tokens. They remain valid until they expire.
 - The internal refreshing functionality was removed because most games are expected to make their own PlayFab calls. Having both the game and the Party library fetch entity tokens causes unnecessary service load to manage two sets of tokens.
 
 #### Chat API Changes
 
 The `PartyVoiceChatTranscriptionReceivedStateChange` now includes a `languageCode` field, which indicates the language of the transcription.
 
-The `PartyChatTextReceivedStateChange` now includes a `languageCode` field, which may indicate the language of the chat text. The `languageCode` field will be populated when chat text translation has been enabled via `PartyLocalChatControl::SetTextChatOptions()`.
+The `PartyChatTextReceivedStateChange` now includes a `languageCode` field, which indicates the language of the chat text. The `languageCode` field will be populated when chat text translation has been enabled via `PartyLocalChatControl::SetTextChatOptions()`.
 
 ## 0.6.0-prerelease
 
@@ -519,12 +565,12 @@ For more information, see the following links:
 
 ## 0.5.0-prerelease
 
-### API Changes
+### API changes
 
 #### Accessible Chat
 * Added support for text-to-speech narration. (see `PartyLocalChatControl::SetTextToSpeechProfile()`)
 * Added more options for controlling when speech-to-text occurs. (see `PartyLocalChatControl::SetTranscriptionOptions()`)
-* Added text-to-text translation to the API, although it is not yet supported. (see `PartyLocalChatControl::SetTextChatOptions()`)
+* Added text-to-text translation to the API, although it isn't yet supported. (see `PartyLocalChatControl::SetTextChatOptions()`)
 * Reduced text-to-speech bandwidth and memory usage.
 
 #### Network access control
@@ -533,13 +579,13 @@ For more information, see the following links:
 
 ## 0.4.6-prerelease
 
-### API Changes
+### API changes
 
 Added new public API `PartyLocalUser::UpdateEntityToken()`.
 
 
 ## 0.2.0-prerelease
 
-### API Changes
+### API changes
 
 * `PartyManager::Initialize` now requires a valid PlayFab Title ID to be passed in.
diff --git a/playfab-docs/multiplayer/networking/unreal-release-notes.md b/playfab-docs/multiplayer/networking/unreal-release-notes.md
index 04d16dc12..8e13b6146 100644
--- a/playfab-docs/multiplayer/networking/unreal-release-notes.md
+++ b/playfab-docs/multiplayer/networking/unreal-release-notes.md
@@ -14,20 +14,31 @@ ms.localizationpriority: medium
 
 Refer to [QuickStart: PlayFab Online Subsystem (OSS)](party-unreal-engine-oss-quickstart.md) for download and install instructions.
 
-## 2.3.7
-**Release 2.3.7 is ready to use with Unreal Engine 5.6.**
+## 2.3.8
+**Release 2.3.8 is ready to use with Unreal Engine 5.7.**
+
+UE5.7 Upgrade Fixes:
+
+* Removed the unused `SEARCH_PRESENCE` key from the lobby search key mapping and related query filter logic, simplifying lobby search parameter handling.
+* Removed dead code related to session search on Win64, as the new join logic no longer relies on this path.
+
+Bug fixes:
 
-**Library Updates:**
+* Added a new `CleanupFailedJoinSession` method to `FOnlineSessionPlayFab` to ensure proper cleanup of PlayFab and Party sessions, removal of local session references, and delegate notification when a native session join fails. This method is now called in all relevant failure paths.
 
-Multiplayer SDK C++ library (Windows/GDK) : From 1.7.9 to 1.8.0.
+* Changed logic to cache the desired session (`CachedDesiredSession`) instead of searching for it on every join, simplifying and improving the reliability of native session joins.
 
-Party SDK C++ library (Windows/GDK) : From 1.10.5 to 1.10.12.
+## 2.3.7
+**Release 2.3.7 is ready to use with Unreal Engine 5.6.**
+
+Library Updates:
 
-**UE5.6 Upgrade Fixes:**
+- Multiplayer SDK C++ library (Windows/GDK) : From 1.7.9 to 1.8.0.
+- Party SDK C++ library (Windows/GDK) : From 1.10.5 to 1.10.12.
 
-### Plugin Configuration Updates
+UE5.6 Upgrade Fixes:
 
-* Updated `OnlineSubsystemPlayFab.uplugin` to use `PlatformAllowList` instead of `WhitelistPlatforms`, and renamed `OnlineSubsystemSwitch` to `OnlineSubsystemNintendo` for consistency. Also incremented the plugin version. [[1]](diffhunk://#diff-5e89106b2fe67da11c76d335b2c0f6c597035a66aa80dc7021dfc24cb8ef24cfL4-R5) [[2]](diffhunk://#diff-5e89106b2fe67da11c76d335b2c0f6c597035a66aa80dc7021dfc24cb8ef24cfL27-R27) [[3]](diffhunk://#diff-5e89106b2fe67da11c76d335b2c0f6c597035a66aa80dc7021dfc24cb8ef24cfL57-R87)
+* Updated `OnlineSubsystemPlayFab.uplugin` to use `PlatformAllowList` instead of `WhitelistPlatforms`, and renamed `OnlineSubsystemSwitch` to `OnlineSubsystemNintendo` for consistency. Also incremented the plugin version.
 * On UE 5.6 and later the `DriverClassName` parameter requires the "/Script/" prefix. For example, use `"/Script/OnlineSubsystemPlayFab.PlayFabNetDriver"` instead of `"OnlineSubsystemPlayFab.PlayFabNetDriver"`.
 Example usage:
   ```
@@ -119,8 +130,8 @@ Known issue:
 - To invite a Steam or PlayStation player, the host must be on the same platform.
 
 ## 2.0.0
-- UE4 engine OSS PlayFab is updated to use Multiplayer features offered by Azure PlayFab such as Lobby, Matchmaking along with PlayFab Party.
-This update replaces the Xbox provided MPSD with Azure PlayFab Lobby and XBL Smart match with Azure Matchmaking service.
+- UE4 engine OSS PlayFab is updated to use Multiplayer features offered by PlayFab such as Lobby, Matchmaking along with PlayFab Party.
+This update replaces the Xbox provided MPSD with PlayFab Lobby and XBL Smart match with Azure Matchmaking service.
 - XDK is no longer supported for this version of the OSS.
 
 ## 1.0.7
diff --git a/playfab-docs/multiplayer/networking/xblreference/partyxblerrors.md b/playfab-docs/multiplayer/networking/xblreference/partyxblerrors.md
index 02212f651..958f9c251 100644
--- a/playfab-docs/multiplayer/networking/xblreference/partyxblerrors.md
+++ b/playfab-docs/multiplayer/networking/xblreference/partyxblerrors.md
@@ -5,13 +5,13 @@ description: List of error codes used by the PlayFab Party's Xbox Live Helper Li
 ms.author: scmunro
 ms.topic: reference
 ms.service: azure-playfab
-ms.date: 08/11/2022
+ms.date: 01/25/2026
 ---
 
 # PlayFab Party Xbox Live Helper Library Error Codes
 The following error codes are used by the PlayFab Party Xbox Live Helper Library:
 
-## Xbox Live Helper Library Errors
+## Xbox Live Helper Library errors
 | Hex | Dec | Description |
 | --- | --- | ----------- |
 | 0x5000 | 20480 | Only one instance of PartyXblManager can exist at a time. |
@@ -30,4 +30,4 @@ The following error codes are used by the PlayFab Party Xbox Live Helper Library
 | 0x500F | 20495 | The specified correlation ID didn't match any outstanding requests. |
 | 0x5014 | 20500 | Setting profiling callbacks after PartyXblManager initialization is forbidden. |
 | 0x5015 | 20501 | The request failed because the Xbox Live token was invalid. |
-| 0x5016 | 20502 | The request failed because the Xbox Live token was expired. |
\ No newline at end of file
+| 0x5016 | 20502 | The request failed because the Xbox Live token was expired. |
diff --git a/playfab-docs/multiplayer/real-time-notifications/client-methods/receive-message.md b/playfab-docs/multiplayer/real-time-messages/client-methods/receive-message.md
similarity index 55%
rename from playfab-docs/multiplayer/real-time-notifications/client-methods/receive-message.md
rename to playfab-docs/multiplayer/real-time-messages/client-methods/receive-message.md
index 27418133e..738f6a191 100644
--- a/playfab-docs/multiplayer/real-time-notifications/client-methods/receive-message.md
+++ b/playfab-docs/multiplayer/real-time-messages/client-methods/receive-message.md
@@ -11,15 +11,13 @@ ms.date: 03/10/2022
 # ReceiveMessage
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
-
-Receives messages from [real-time notifications
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
+
+Receives messages from [real-time messages
 subscriptions](../subscribing-to-resources.md).
 
 ```text
@@ -40,5 +38,5 @@ ReceiveMessage(Message message)
 - Type [Message](../types/message.md)
 - Client method
   [ReceiveSubscriptionChangeMessage](receive-subscription-change-message.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/client-methods/receive-subscription-change-message.md b/playfab-docs/multiplayer/real-time-messages/client-methods/receive-subscription-change-message.md
similarity index 53%
rename from playfab-docs/multiplayer/real-time-notifications/client-methods/receive-subscription-change-message.md
rename to playfab-docs/multiplayer/real-time-messages/client-methods/receive-subscription-change-message.md
index eb6964268..46ccc3282 100644
--- a/playfab-docs/multiplayer/real-time-notifications/client-methods/receive-subscription-change-message.md
+++ b/playfab-docs/multiplayer/real-time-messages/client-methods/receive-subscription-change-message.md
@@ -11,23 +11,21 @@ ms.date: 03/10/2022
 # ReceiveSubscriptionChangeMessage
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 Receives [SubscriptionChangeMessages](../types/subscription-change-message.md),
-so the client will know when its [subscription](../subscribing-to-resources.md)
+so the client knows when its [subscription](../subscribing-to-resources.md)
 status changes. This message indicates that a request to subscribe or
-unsubscribe has finished processing. It is possible that the service will fail
-to perform a subscription update in a way where the client will never receive
-this message. Because of this, clients should implement a timer so they can
-retry the subscription call if no
-[SubscriptionChangeMessage](../types/subscription-change-message.md) is received
-by this method after 5 seconds. This timer-based retry can be performed a few
+unsubscribe finished processing. It's possible that the service fails
+to perform a subscription update in a way where the client never receives
+this message. For this reason, clients should implement a timer so they can
+retry the subscription call if this method doesn't receive a
+[SubscriptionChangeMessage](../types/subscription-change-message.md)
+after 5 seconds. This timer-based retry can be performed a few
 times with exponential backoff for subsequent attempts.
 
 ```text
@@ -47,5 +45,5 @@ ReceiveSubscriptionChangeMessage(SubscriptionChangeMessage subscriptionChangeMes
 
 - Type [SubscriptionChangeMessage](../types/subscription-change-message.md)
 - Client method [ReceiveMessage](receive-message.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-messages/overview.md b/playfab-docs/multiplayer/real-time-messages/overview.md
new file mode 100644
index 000000000..482bf71df
--- /dev/null
+++ b/playfab-docs/multiplayer/real-time-messages/overview.md
@@ -0,0 +1,39 @@
+---
+author: WarrenAlpert
+title: Real-time messages for Lobby and Matchmaking APIs
+description: Real-time messages for Lobby and Matchmaking APIs
+ms.author: waralp
+ms.topic: reference
+ms.service: azure-playfab
+ms.date: 03/10/2022
+---
+
+# Real-time messages for Lobby and Matchmaking APIs
+
+> [!NOTE]
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
+
+The [Lobby and Matchmaking
+services](../lobby/lobby-and-matchmaking.md) offer a real-time
+messages feature, which enables individual game clients to subscribe to
+receive messages from these services. Game clients subscribe for
+messages over a persistent [SignalR WebSocket
+connection](/aspnet/core/signalr/introduction). To learn more about
+the scenario as a whole, see the [conceptual documentation for Lobby and
+Matchmaking real-time
+messages](../lobby/lobby-and-matchmaking-real-time-messages.md).
+
+To use this feature, game clients will first need to [implement a SignalR client
+that connects to the SignalR Hub](signalr-hub.md) for real-time messages.
+Once connected, the clients can [subscribe to
+resources](subscribing-to-resources.md) they would like to receive messages
+for.
+
+## See also
+
+- [Real-time messages SignalR Hub](signalr-hub.md)
+- [Subscribing to resources](subscribing-to-resources.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/server-methods/add-entity-to-session.md b/playfab-docs/multiplayer/real-time-messages/server-methods/add-entity-to-session.md
similarity index 64%
rename from playfab-docs/multiplayer/real-time-notifications/server-methods/add-entity-to-session.md
rename to playfab-docs/multiplayer/real-time-messages/server-methods/add-entity-to-session.md
index b95b5aa11..de9473100 100644
--- a/playfab-docs/multiplayer/real-time-notifications/server-methods/add-entity-to-session.md
+++ b/playfab-docs/multiplayer/real-time-messages/server-methods/add-entity-to-session.md
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # AddEntityToSession
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 For scenarios where multiple entities are signed in to the same device. Add an
 additional entity to the session, other than the entity that started the
@@ -44,5 +42,5 @@ SharedSessionResponse AddEntityToSession(SharedSessionRequest request)
 ## See also
 
 - Server method [RemoveEntityFromSession](remove-entity-from-session.md).
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/server-methods/end-session.md b/playfab-docs/multiplayer/real-time-messages/server-methods/end-session.md
similarity index 56%
rename from playfab-docs/multiplayer/real-time-notifications/server-methods/end-session.md
rename to playfab-docs/multiplayer/real-time-messages/server-methods/end-session.md
index 3ac55a3af..3ca07251d 100644
--- a/playfab-docs/multiplayer/real-time-notifications/server-methods/end-session.md
+++ b/playfab-docs/multiplayer/real-time-messages/server-methods/end-session.md
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # EndSession
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 End the session.
 
@@ -41,5 +39,5 @@ EndSessionResponse EndSession(EndSessionRequest request)
 ## See also
 
 - Server method [StartOrRecoverSession](start-or-recover-session.md).
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/server-methods/remove-entity-from-session.md b/playfab-docs/multiplayer/real-time-messages/server-methods/remove-entity-from-session.md
similarity index 61%
rename from playfab-docs/multiplayer/real-time-notifications/server-methods/remove-entity-from-session.md
rename to playfab-docs/multiplayer/real-time-messages/server-methods/remove-entity-from-session.md
index de7d93133..c9194ec74 100644
--- a/playfab-docs/multiplayer/real-time-notifications/server-methods/remove-entity-from-session.md
+++ b/playfab-docs/multiplayer/real-time-messages/server-methods/remove-entity-from-session.md
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # RemoveEntityFromSession
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 Remove an additional entity that was added to the session with
 [AddEntityToSession](add-entity-to-session.md).
@@ -42,5 +40,5 @@ SharedSessionResponse RemoveEntityFromSession(SharedSessionRequest request)
 ## See also
 
 - Server method [AddEntityToSession](add-entity-to-session.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/server-methods/start-or-recover-session.md b/playfab-docs/multiplayer/real-time-messages/server-methods/start-or-recover-session.md
similarity index 64%
rename from playfab-docs/multiplayer/real-time-notifications/server-methods/start-or-recover-session.md
rename to playfab-docs/multiplayer/real-time-messages/server-methods/start-or-recover-session.md
index 3cd904dd3..368dc03c2 100644
--- a/playfab-docs/multiplayer/real-time-notifications/server-methods/start-or-recover-session.md
+++ b/playfab-docs/multiplayer/real-time-messages/server-methods/start-or-recover-session.md
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # StartOrRecoverSession
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 Starts a session.
 
@@ -45,5 +43,5 @@ StartOrRecoverSessionResponse StartOrRecoverSession(StartOrRecoverSessionRequest
 ## See also
 
 - Server method [EndSession](end-session.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/signalr-hub.md b/playfab-docs/multiplayer/real-time-messages/signalr-hub.md
similarity index 73%
rename from playfab-docs/multiplayer/real-time-notifications/signalr-hub.md
rename to playfab-docs/multiplayer/real-time-messages/signalr-hub.md
index 693dd6bc0..a252a0307 100644
--- a/playfab-docs/multiplayer/real-time-notifications/signalr-hub.md
+++ b/playfab-docs/multiplayer/real-time-messages/signalr-hub.md
@@ -1,25 +1,23 @@
 ---
 author: WarrenAlpert
-title: Real-time notifications SignalR Hub
-description: Real-time notifications SignalR Hub
+title: Real-time messages SignalR Hub
+description: Real-time messages SignalR Hub
 ms.author: waralp
 ms.topic: reference
 ms.service: azure-playfab
 ms.date: 03/10/2022
 ---
 
-# Real-time notifications SignalR Hub
+# Real-time messages SignalR Hub
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
-
-The real-time notifications feature for [Lobby and Matchmaking
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
+
+The real-time messages feature for [Lobby and Matchmaking
 services](../lobby/lobby-and-matchmaking.md) works through a
 [SignalR service](/aspnet/core/signalr), which exposes
 a [SignalR Hub](/aspnet/core/signalr/introduction#hubs). This
@@ -28,7 +26,7 @@ they subscribed to](subscribing-to-resources.md).
 
 ## Connecting to the SignalR Hub
 
-The first step in receiving real-time notifications is to create a [SignalR
+The first step in receiving real-time messages is to create a [SignalR
 client](/aspnet/core/signalr/client-features). The
 client can create a connection to the SignalR Hub by [instantiating a
 HubConnection](/aspnet/core/signalr/dotnet-client#connect-to-a-hub)
@@ -43,9 +41,25 @@ documentation](https://github.com/dotnet/aspnetcore/blob/main/src/SignalR/docs/s
 > when connecting to the SignalR Hub is strongly recommended, and will be
 > enforced as the only supported encoding in the future.
 
+> [!IMPORTANT]
+> The client **must** set `KeepAliveInterval` to **5 seconds** when building the
+> `HubConnection`. The backend service will time out and close connections that
+> do not receive a keep-alive ping within **10 seconds**. The default SignalR
+> `KeepAliveInterval` of 15 seconds is too slow and will cause disconnections.
+>
+> ```csharp
+> var connection = new HubConnectionBuilder()
+>     .WithUrl(hubUrl, options => { /* auth headers */ })
+>     .WithKeepAliveInterval(TimeSpan.FromSeconds(5))
+>     .Build();
+> ```
+>
+> For more details on SignalR client configuration, see the
+> [SignalR configuration documentation](/aspnet/core/signalr/configuration#configure-client-options).
+
 > [!NOTE]
 > 1. SignalR client implementations expect the URL to omit the `/negotiate`
->    portion of this path (ex: HubConnection should created to a URL that ends
+>    portion of this path (for example, HubConnection should be created to a URL that ends
 >    in `...playfabapi.com/pubsub`).
 > 1. The auth headers required to call this API can be passed to the SignalR
 >    client via `HttpConnectionOptions` as [seen on this
@@ -81,7 +95,7 @@ resources](subscribing-to-resources.md) and receiving messages.
 
 | Name |  Description  |
 | --- | --- |
-| [ReceiveMessage](client-methods/receive-message.md) | Receive a notification message. |
+| [ReceiveMessage](client-methods/receive-message.md) | Receive a message. |
 | [ReceiveSubscriptionChangeMessage](client-methods/receive-subscription-change-message.md) | Receive a SubscriptionChangeMessage to track current subscriptions. |
 
 ### Server methods
@@ -102,4 +116,4 @@ resources](subscribing-to-resources.md) and receiving messages.
 ## See also
 
 - [Subscribing to resources](subscribing-to-resources.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](overview.md)
+- [Real-time messages for Lobby and Matchmaking APIs](overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/subscribing-to-resources.md b/playfab-docs/multiplayer/real-time-messages/subscribing-to-resources.md
similarity index 65%
rename from playfab-docs/multiplayer/real-time-notifications/subscribing-to-resources.md
rename to playfab-docs/multiplayer/real-time-messages/subscribing-to-resources.md
index 835fda1ad..a7706e1cd 100644
--- a/playfab-docs/multiplayer/real-time-notifications/subscribing-to-resources.md
+++ b/playfab-docs/multiplayer/real-time-messages/subscribing-to-resources.md
@@ -1,7 +1,7 @@
 ---
 author: WarrenAlpert
-title: Subscribing to resources for real-time notifications
-description: Subscribing to resources for real-time notifications
+title: Subscribing to resources for real-time messages
+description: Subscribing to resources for real-time messages
 ms.author: waralp
 ms.topic: reference
 ms.service: azure-playfab
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # Subscribing to resources
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 After the client [connects to the SignalR
 Hub](signalr-hub.md#connecting-to-the-signalr-hub), and calls
@@ -28,7 +26,7 @@ provide the `Connection Handle` that they received when starting the session.
 For more information about starting and managing a session, see the [SignalR
 Hub](signalr-hub.md) overview.
 
-To manage resource subscriptions with the services that publish notifications,
+To manage resource subscriptions with the services that publish messages,
 see:
 
 | Service | Subscription API | Unsubscription API |
@@ -38,5 +36,5 @@ see:
 
 ## See also
 
-- [Real-time notifications SignalR Hub](signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](overview.md)
+- [Real-time messages SignalR Hub](signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/toc.yml b/playfab-docs/multiplayer/real-time-messages/toc.yml
similarity index 100%
rename from playfab-docs/multiplayer/real-time-notifications/toc.yml
rename to playfab-docs/multiplayer/real-time-messages/toc.yml
diff --git a/playfab-docs/multiplayer/real-time-messages/types/end-session-request.md b/playfab-docs/multiplayer/real-time-messages/types/end-session-request.md
new file mode 100644
index 000000000..2586213be
--- /dev/null
+++ b/playfab-docs/multiplayer/real-time-messages/types/end-session-request.md
@@ -0,0 +1,40 @@
+---
+author: WarrenAlpert
+title: EndSessionRequest real-time messages type
+description: EndSessionRequest real-time messages type
+ms.author: waralp
+ms.topic: reference
+ms.service: azure-playfab
+ms.date: 03/10/2022
+---
+
+# EndSessionRequest
+
+> [!NOTE]
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
+
+```json
+{
+    "traceParent": "00-84678fd69ae13e41fce1333289bcf482-22d157fb94ea4827-01"
+}
+```
+
+## Members
+
+**`traceParent`** &nbsp; string
+
+A valid [W3C TraceContext TraceParent
+Header](https://www.w3.org/TR/trace-context/#traceparent-header).
+
+Example: `00-84678fd69ae13e41fce1333289bcf482-22d157fb94ea4827-01`
+
+## See also
+
+- Type [EndSessionResponse](end-session-response.md)
+- Server method [EndSession](../server-methods/end-session.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/types/end-session-response.md b/playfab-docs/multiplayer/real-time-messages/types/end-session-response.md
similarity index 54%
rename from playfab-docs/multiplayer/real-time-notifications/types/end-session-response.md
rename to playfab-docs/multiplayer/real-time-messages/types/end-session-response.md
index 757eee824..240482430 100644
--- a/playfab-docs/multiplayer/real-time-notifications/types/end-session-response.md
+++ b/playfab-docs/multiplayer/real-time-messages/types/end-session-response.md
@@ -1,7 +1,7 @@
 ---
 author: WarrenAlpert
-title: EndSessionResponse real-time notifications type
-description: EndSessionResponse real-time notifications type
+title: EndSessionResponse real-time messages type
+description: EndSessionResponse real-time messages type
 ms.author: waralp
 ms.topic: reference
 ms.service: azure-playfab
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # EndSessionResponse
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 ```json
 {
@@ -47,5 +45,5 @@ Example: `4bf92f3577b34da6a3ce929d0e0e4736`
 
 - Type [EndSessionRequest](end-session-request.md)
 - Server method [EndSession](../server-methods/end-session.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/types/message.md b/playfab-docs/multiplayer/real-time-messages/types/message.md
similarity index 73%
rename from playfab-docs/multiplayer/real-time-notifications/types/message.md
rename to playfab-docs/multiplayer/real-time-messages/types/message.md
index ffd49bba3..ade62d771 100644
--- a/playfab-docs/multiplayer/real-time-notifications/types/message.md
+++ b/playfab-docs/multiplayer/real-time-messages/types/message.md
@@ -1,7 +1,7 @@
 ---
 author: WarrenAlpert
-title: Message real-time notifications type
-description: Message real-time notifications type
+title: Message real-time messages type
+description: Message real-time messages type
 ms.author: waralp
 ms.topic: reference
 ms.service: azure-playfab
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # Message
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 ```json
 {
@@ -56,5 +54,5 @@ Example: `4bf92f3577b34da6a3ce929d0e0e4736`
 ## See also
 
 - Client method [ReceiveMessage](../client-methods/receive-message.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/types/response-status.md b/playfab-docs/multiplayer/real-time-messages/types/response-status.md
similarity index 74%
rename from playfab-docs/multiplayer/real-time-notifications/types/response-status.md
rename to playfab-docs/multiplayer/real-time-messages/types/response-status.md
index 542ea9266..d1bb66fe0 100644
--- a/playfab-docs/multiplayer/real-time-notifications/types/response-status.md
+++ b/playfab-docs/multiplayer/real-time-messages/types/response-status.md
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # Response Status
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 Possible values for the **status** member of [SignalR server
 method](../signalr-hub.md#server-methods) responses.
@@ -39,5 +37,5 @@ method](../signalr-hub.md#server-methods) responses.
 - Type [EndSessionResponse](end-session-response.md)
 - Type [SharedSessionResponse](shared-session-response.md)
 - Type [StartOrRecoverSessionResponse](start-or-recover-session-response.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/types/shared-session-request.md b/playfab-docs/multiplayer/real-time-messages/types/shared-session-request.md
similarity index 65%
rename from playfab-docs/multiplayer/real-time-notifications/types/shared-session-request.md
rename to playfab-docs/multiplayer/real-time-messages/types/shared-session-request.md
index fb3009018..750a13069 100644
--- a/playfab-docs/multiplayer/real-time-notifications/types/shared-session-request.md
+++ b/playfab-docs/multiplayer/real-time-messages/types/shared-session-request.md
@@ -1,7 +1,7 @@
 ---
 author: WarrenAlpert
-title: SharedSessionRequest real-time notifications type
-description: SharedSessionRequest real-time notifications type
+title: SharedSessionRequest real-time messages type
+description: SharedSessionRequest real-time messages type
 ms.author: waralp
 ms.topic: reference
 ms.service: azure-playfab
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # SharedSessionRequest
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 ```json
 {
@@ -58,5 +56,5 @@ Example: `00-84678fd69ae13e41fce1333289bcf482-22d157fb94ea4827-01`
 - Server method [AddEntityToSession](../server-methods/add-entity-to-session.md)
 - Server method
   [RemoveEntityFromSession](../server-methods/remove-entity-from-session.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/types/shared-session-response.md b/playfab-docs/multiplayer/real-time-messages/types/shared-session-response.md
similarity index 61%
rename from playfab-docs/multiplayer/real-time-notifications/types/shared-session-response.md
rename to playfab-docs/multiplayer/real-time-messages/types/shared-session-response.md
index 6d379f8d3..207431d4f 100644
--- a/playfab-docs/multiplayer/real-time-notifications/types/shared-session-response.md
+++ b/playfab-docs/multiplayer/real-time-messages/types/shared-session-response.md
@@ -1,7 +1,7 @@
 ---
 author: WarrenAlpert
-title: SharedSessionResponse real-time notifications type
-description: SharedSessionResponse real-time notifications type
+title: SharedSessionResponse real-time messages type
+description: SharedSessionResponse real-time messages type
 ms.author: waralp
 ms.topic: reference
 ms.service: azure-playfab
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # SharedSessionResponse
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 ```json
 {
@@ -56,5 +54,5 @@ Example: `4bf92f3577b34da6a3ce929d0e0e4736`
 - Server method [AddEntityToSession](../server-methods/add-entity-to-session.md)
 - Server method
   [RemoveEntityFromSession](../server-methods/remove-entity-from-session.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/types/start-or-recover-session-request.md b/playfab-docs/multiplayer/real-time-messages/types/start-or-recover-session-request.md
similarity index 61%
rename from playfab-docs/multiplayer/real-time-notifications/types/start-or-recover-session-request.md
rename to playfab-docs/multiplayer/real-time-messages/types/start-or-recover-session-request.md
index a5a050ce0..081b30e46 100644
--- a/playfab-docs/multiplayer/real-time-notifications/types/start-or-recover-session-request.md
+++ b/playfab-docs/multiplayer/real-time-messages/types/start-or-recover-session-request.md
@@ -1,7 +1,7 @@
 ---
 author: WarrenAlpert
-title: StartOrRecoverSessionRequest real-time notifications type
-description: StartOrRecoverSessionRequest real-time notifications type
+title: StartOrRecoverSessionRequest real-time messages type
+description: StartOrRecoverSessionRequest real-time messages type
 ms.author: waralp
 ms.topic: reference
 ms.service: azure-playfab
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # StartOrRecoverSessionRequest
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 ```json
 {
@@ -48,5 +46,5 @@ Example: `00-84678fd69ae13e41fce1333289bcf482-22d157fb94ea4827-01`
 - Type [StartOrRecoverSessionResponse](start-or-recover-session-response.md)
 - Server method
   [StartOrRecoverSession](../server-methods/start-or-recover-session.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/types/start-or-recover-session-response.md b/playfab-docs/multiplayer/real-time-messages/types/start-or-recover-session-response.md
similarity index 73%
rename from playfab-docs/multiplayer/real-time-notifications/types/start-or-recover-session-response.md
rename to playfab-docs/multiplayer/real-time-messages/types/start-or-recover-session-response.md
index 02594bbb3..bd9f91996 100644
--- a/playfab-docs/multiplayer/real-time-notifications/types/start-or-recover-session-response.md
+++ b/playfab-docs/multiplayer/real-time-messages/types/start-or-recover-session-response.md
@@ -1,7 +1,7 @@
 ---
 author: WarrenAlpert
-title: StartOrRecoverSessionResponse real-time notifications type
-description: StartOrRecoverSessionResponse real-time notifications type
+title: StartOrRecoverSessionResponse real-time messages type
+description: StartOrRecoverSessionResponse real-time messages type
 ms.author: waralp
 ms.topic: reference
 ms.service: azure-playfab
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # StartOrRecoverSessionResponse
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 ```json
 {
@@ -51,7 +49,7 @@ A list of topic strings, matching the topic strings returned when [subscribing
 to resources](../subscribing-to-resources.md). This list only contains values if
 a session was recovered from an old `Connection Handle` and subscriptions were
 found to recover. It's possible that some subscriptions that are expected here
-will not be recovered. If there are any missing subscriptions  the client should
+will not be recovered. If there are any missing subscriptions, the client should
 resubscribe to those resources.
 
 Example: `["Opaque~Topic~String~6183258", "Another~Opaque~Topic~String~843156"]`
@@ -75,5 +73,5 @@ Example: `4bf92f3577b34da6a3ce929d0e0e4736`
 - Type [StartOrRecoverSessionRequest](start-or-recover-session-request.md)
 - Server method
   [StartOrRecoverSession](../server-methods/start-or-recover-session.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/types/subscription-change-message.md b/playfab-docs/multiplayer/real-time-messages/types/subscription-change-message.md
similarity index 80%
rename from playfab-docs/multiplayer/real-time-notifications/types/subscription-change-message.md
rename to playfab-docs/multiplayer/real-time-messages/types/subscription-change-message.md
index 03df9b300..dee4dad28 100644
--- a/playfab-docs/multiplayer/real-time-notifications/types/subscription-change-message.md
+++ b/playfab-docs/multiplayer/real-time-messages/types/subscription-change-message.md
@@ -1,7 +1,7 @@
 ---
 author: WarrenAlpert
-title: SubscriptionChangeMessage real-time notifications type
-description: SubscriptionChangeMessage real-time notifications type
+title: SubscriptionChangeMessage real-time messages type
+description: SubscriptionChangeMessage real-time messages type
 ms.author: waralp
 ms.topic: reference
 ms.service: azure-playfab
@@ -11,13 +11,11 @@ ms.date: 03/10/2022
 # SubscriptionChangeMessage
 
 > [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
+> The REST and SignalR APIs documented here are more complex than the client
+> SDKs. Consider using the
+> [Lobby C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
+> or [Matchmaking C++ SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md)
+> instead, unless those SDKs don't meet your needs.
 
 ```json
 {
@@ -92,5 +90,5 @@ Example: `4bf92f3577b34da6a3ce929d0e0e4736`
 
 - Client method
   [ReceiveSubscriptionChangeMessage](../client-methods/receive-subscription-change-message.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
+- [Real-time messages SignalR Hub](../signalr-hub.md)
+- [Real-time messages for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/overview.md b/playfab-docs/multiplayer/real-time-notifications/overview.md
deleted file mode 100644
index a29e0c945..000000000
--- a/playfab-docs/multiplayer/real-time-notifications/overview.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-author: WarrenAlpert
-title: Real-time notifications for Lobby and Matchmaking APIs
-description: Real-time notifications for Lobby and Matchmaking APIs
-ms.author: waralp
-ms.topic: reference
-ms.service: azure-playfab
-ms.date: 03/10/2022
----
-
-# Real-time notifications for Lobby and Matchmaking APIs
-
-> [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
-
-The [Lobby and Matchmaking
-services](../lobby/lobby-and-matchmaking.md) offer a real-time
-notifications feature, which enables individual game clients to subscribe to
-receive notifications from these services. Game clients subscribe for
-notifications over a persistent [SignalR WebSocket
-connection](/aspnet/core/signalr/introduction). To learn more about
-the scenario as a whole, see the [conceptual documentation for Lobby and
-Matchmaking real-time
-notifications](../lobby/lobby-and-matchmaking-real-time-notifications.md).
-
-To use this feature, game clients will first need to [implement a SignalR client
-that connects to the SignalR Hub](signalr-hub.md) for real-time notifications.
-Once connected, the clients can [subscribe to
-resources](subscribing-to-resources.md) they would like to receive notifications
-for.
-
-## See also
-
-- [Real-time notifications SignalR Hub](signalr-hub.md)
-- [Subscribing to resources](subscribing-to-resources.md)
diff --git a/playfab-docs/multiplayer/real-time-notifications/types/end-session-request.md b/playfab-docs/multiplayer/real-time-notifications/types/end-session-request.md
deleted file mode 100644
index d1b272d74..000000000
--- a/playfab-docs/multiplayer/real-time-notifications/types/end-session-request.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-author: WarrenAlpert
-title: EndSessionRequest real-time notifications type
-description: EndSessionRequest real-time notifications type
-ms.author: waralp
-ms.topic: reference
-ms.service: azure-playfab
-ms.date: 03/10/2022
----
-
-# EndSessionRequest
-
-> [!NOTE]
-> Using Lobby, Matchmaking, and real-time notifications directly with REST and
-> SignalR APIs is significantly more complex than using client SDKs such as the
-> [Lobby C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pflobby/pflobby_members.md)
-> and [Matchmaking C++
-> SDK](../../lobby/playfabmultiplayerreference-cpp/pfmatchmaking/pfmatchmaking_members.md),
-> and should only be done if the SDKs don't meet your needs.
-
-```json
-{
-    "traceParent": "00-84678fd69ae13e41fce1333289bcf482-22d157fb94ea4827-01"
-}
-```
-
-## Members
-
-**`traceParent`** &nbsp; string
-
-A valid [W3C TraceContext TraceParent
-Header](https://www.w3.org/TR/trace-context/#traceparent-header).
-
-Example: `00-84678fd69ae13e41fce1333289bcf482-22d157fb94ea4827-01`
-
-## See also
-
-- Type [EndSessionResponse](end-session-response.md)
-- Server method [EndSession](../server-methods/end-session.md)
-- [Real-time notifications SignalR Hub](../signalr-hub.md)
-- [Real-time notifications for Lobby and Matchmaking APIs](../overview.md)
diff --git a/playfab-docs/multiplayer/servers/author-a-game-server-build.md b/playfab-docs/multiplayer/servers/author-a-game-server-build.md
index 6829664b9..bdf1a26ef 100644
--- a/playfab-docs/multiplayer/servers/author-a-game-server-build.md
+++ b/playfab-docs/multiplayer/servers/author-a-game-server-build.md
@@ -36,10 +36,10 @@ This new build now helps manage game servers that are created using PlayFab Mult
 
 When using Windows game servers, you have to use the managed Windows container image. So the PlayFab Multiplayer Game Server Build can be uploaded as a zipped file combined with other dependencies (DLL files) during the [Deploy a build](deploying-playfab-multiplayer-server-builds.md) process. To help you determine what needs to be included in the zipped file, see [Determining required DLLs](determining-required-dlls.md).
 
-When using Linux game servers, you need to [Create your custom Linux container image](deploying-linux-based-builds.md) and the PlayFab Multiplayer Game Server Build can be included as part of the image. Once your custom image is uploaded, you would be able to [Deploy a build](deploying-playfab-multiplayer-server-builds.md).
+When using Linux game servers, you need to [Create and deploy Linux Builds](deploying-linux-based-builds.md) and the PlayFab Multiplayer Game Server Build can be included as part of the image. Once your custom image is uploaded, you would be able to [Deploy a build](deploying-playfab-multiplayer-server-builds.md).
 
 ## See also
 
 * [Determine DLL files to be included in the asset package for Windows servers](determining-required-dlls.md)
 * [Local debugging and integration for Windows servers](locally-debugging-game-servers-and-integration-with-playfab.md)
-* [Create Linux servers](deploying-linux-based-builds.md)
+* [Create and deploy Linux Builds](deploying-linux-based-builds.md)
diff --git a/playfab-docs/multiplayer/servers/build-definition.md b/playfab-docs/multiplayer/servers/build-definition.md
index f2821f042..b26f0fe3a 100644
--- a/playfab-docs/multiplayer/servers/build-definition.md
+++ b/playfab-docs/multiplayer/servers/build-definition.md
@@ -12,11 +12,11 @@ ms.localizationpriority: medium
 
 # Build definition and configuration
 
-This topic describes the parameters you need to specify when deploying/creating a Virtual Machine (VM)/game server build.
+This article describes the parameters you need to specify when deploying/creating a Virtual Machine (VM)/game server build.
 
 A build is created by specifying its *build definition* and *build configuration*. 
 
-Build definition **cannot be modified** after it is created. This requires you to select what Virtual Machines (VMs) you want, upload your PlayFab Multiplayer Game Server Build, assets, certificates, and more.
+Build definition **cannot be modified** after it's created. This requires you to select what Virtual Machines (VMs) you want, upload your PlayFab Multiplayer Game Server Build, assets, certificates, and more.
 
 Build configuration determines how your game scales across Azure. This **can be modified at any time** in a build's life.
 
@@ -34,10 +34,10 @@ For sample values you can use to deploy a simple server, see [Walk-through of de
 | Virtual machine (VM) selection | A drop-down list of global distributed Azure VMs with different technical specifications | Select the VMs based on what you need&mdash;number of cores, RAM, storage, region. For details, see [Multiplayer Servers details and price sheet](https://playfab.com/mps-detailed-pricing/).  |
 | Servers per machine | Number of game servers hosted on each VM. The number of cores in the VM is split by the number of servers. | |
 | Virtual machine OS | Select Windows or Linux platform. | |
-| Container | The container that will host your game server. | For Windows, you can simply select the managed Windows Server Core containers. For Linux-based VMs, see [Deploying Linux-based builds](deploying-linux-based-builds.md).|
-| Assets | Files you want uploaded on the servers. You can upload multiple assets but one of the assets **must** contain your [PlayFab Multiplayer Game Server Build](#). <br>All assets combined should be less than 10GB in size and must be in *zip*, *tar.gz* or *tar* file type. <br>Each asset has a mount path associated with it. This specifies where it is mounted in the container file system.| Asset filenames can only contain alphanumeric characters, underscores, hyphens, and periods. You can use C:\Assets as the typical mount path. What this means that PlayFab will unzip your assets and mount it **in the container file-system** (not the VM) as a folder in the **C**  drive under Assets. |
+| Container | The container that will host your game server. | For Windows, you can simply select the managed Windows Server Core containers. For Linux-based VMs, see [Create and deploy Linux Builds](deploying-linux-based-builds.md).|
+| Assets | Files you want uploaded on the servers. You can upload multiple assets but one of the assets **must** contain your [PlayFab Multiplayer Game Server Build](#). <br>All assets combined should be less than 10 GB in size and must be in *zip*, *tar.gz, or *tar* file type. <br>Each asset has a mount path associated with it. This specifies where it's mounted in the container file system.| Asset filenames can only contain alphanumeric characters, underscores, hyphens, and periods. You can use C:\Assets as the typical mount path. What this means that PlayFab will unzip your assets and mount it **in the container file-system** (not the VM) as a folder in the **C**  drive under Assets. |
 | Start command | The command to run when the game server starts, make sure to include any arguments that you need. |    |
-| Network | Define the port name, number, and protocol (TCP or UDP) to be used for incoming network traffic. Outgoing (or solicited) network flows do not need to be configured. For more networking information, see [Connecting clients to game servers](connecting-clients-to-game-servers.md).| |
+| Network | Define the port name, number, and protocol (TCP or UDP) to be used for incoming network traffic. Outgoing (or solicited) network flows don't need to be configured. For more networking information, see [Connecting clients to game servers](connecting-clients-to-game-servers.md).| |
 | Certificate (optional) | Upload certificates for the game server. This is a .pfx (Windows) or .pem (Linux) file containing the certificate to be installed within the container. Certificate names can only contain letters and numbers. No spaces or special characters such as dashes and underscores. | Typically, the certificate for service-to-service authentication is installed through this configuration. |
 | Metadata (optional)   | A set of property-values that can be retrieved using GSDK | |
 
@@ -55,7 +55,7 @@ Build configuration is determined by the following list of parameters. When sele
 
 This is the fastest way to view what's required when deploying/creating a VM build.
 
-* Log into your developer account on [PlayFab.com](https://playfab.com)
+* Log into your developer account on [PlayFab.com](https://developer.playfab.com)
 * Go to **My Studios and Titles** page and select your game title to display the dashboard
 * Go to **Multiplayer** > **Servers** page, select **New Build** at the top right to create a new build
 
diff --git a/playfab-docs/multiplayer/servers/deploy-using-game-manager.md b/playfab-docs/multiplayer/servers/deploy-using-game-manager.md
index 9b4d6ce4b..161edbafa 100644
--- a/playfab-docs/multiplayer/servers/deploy-using-game-manager.md
+++ b/playfab-docs/multiplayer/servers/deploy-using-game-manager.md
@@ -36,7 +36,7 @@ For details about the values you can use for each parameter, see [Build definiti
 1. Next we have the server details portion where you'll need to select an OS type either **Windows** or **Linux**. Then you'll select your server type, either process or container based on the OS you choose.
 
 > [!Note]
-> For Linux platform, you need to create your own container image. For more instructions, see [Create and deploy Linux container images](deploying-linux-based-builds.md). If you've already uploaded a container image, it will appear in the __Image__ dropdown. To use it, select the image.
+> For Linux platform, you need to create your own container image. For more instructions, see [Create and deploy Linux Builds](deploying-linux-based-builds.md). If you've already uploaded a container image, it will appear in the __Image__ dropdown. To use it, select the image.
 
 Once you've selected your OS type, you can then choose the server type. Based on the OS/Server type you'll have the following features you can enable.
 
diff --git a/playfab-docs/multiplayer/servers/deploy-using-powershell-api.md b/playfab-docs/multiplayer/servers/deploy-using-powershell-api.md
index 0a314595d..d8ce0d5cd 100644
--- a/playfab-docs/multiplayer/servers/deploy-using-powershell-api.md
+++ b/playfab-docs/multiplayer/servers/deploy-using-powershell-api.md
@@ -24,7 +24,7 @@ If this is your first time deploying a build, we recommend deploying a build usi
 ## Get your title ID and developer secret key
 
 * Get your PlayFab title ID
-    * Log into your developer account on [PlayFab.com](https://playfab.com)
+    * Log into your developer account on [PlayFab.com](https://developer.playfab.com)
     * In Game Manager, go to **My Studios and Titles** page. Look for your game title and get the PlayFab game title ID
 
 * Get the developer secret key for the title
@@ -84,7 +84,7 @@ If you receive an error that says `Title must have a valid payment instrument as
 
 Uploading an asset is mandatory when you're deploying a build for Windows servers. This is because your assets customize the managed Windows container image.
 
-However, it's optional when deploying a build for Linux servers since you're able to customize the Linux container image. To learn more, see [Create Linux container images](deploying-linux-based-builds.md).
+However, it's optional when deploying a build for Linux servers since you're able to customize the Linux container image. To learn more, see [Create and deploy Linux Builds](deploying-linux-based-builds.md).
 
 Run this command to upload an asset.
 
@@ -101,7 +101,7 @@ For more details, see [New-PfAsset reference documentation](https://github.com/P
 ## Create a build
 
 * When creating a build for Windows servers, you need to have uploaded an asset. If not, see [Upload an asset](#upload-an-asset).
-* When creating a build for Linux servers, you need to have uploaded your custom Linux container image to your PlayFab container registry. To learn more, see [Deploying Linux servers](deploying-linux-based-builds.md).
+* When creating a build for Linux servers, you need to have uploaded your custom Linux container image to your PlayFab container registry. To learn more, see [Create and deploy Linux Builds](deploying-linux-based-builds.md).
 
 > [!IMPORTANT] 
 > Make sure you use the correct values for __$vmSize__ and __$regions__ if you plan to take advantage of resources offered for [free evaluation](billing-for-thunderhead.md).
diff --git a/playfab-docs/multiplayer/servers/deploying-linux-based-builds.md b/playfab-docs/multiplayer/servers/deploying-linux-based-builds.md
index 2e0aaeb36..249f54abe 100644
--- a/playfab-docs/multiplayer/servers/deploying-linux-based-builds.md
+++ b/playfab-docs/multiplayer/servers/deploying-linux-based-builds.md
@@ -1,20 +1,24 @@
 ---
-title: Create and deploy Linux container images
+title: Create and deploy Linux Builds
 author: joannaleecy
-description: Create and deploy Linux container images.
+description: Create and deploy Linux Builds.
 ms.author: jenelleb
-ms.date: 04/01/2021
+ms.date: 03/19/2026
 ms.topic: article
 ms.service: azure-playfab
 keywords: playfab, multiplayer servers, thunderhead, linux
 ms.localizationpriority: medium
 ---
 
-# Create and deploy Linux container images
+# Create and deploy Linux Builds
 
-This article outlines specific steps to help you create and deploy Linux container images.
+This article contains details on how to create Linux Builds on PlayFab Multiplayer Servers, both using containers and using processes.
 
-As described in [Create VMs](deploying-playfab-multiplayer-server-builds.md), you configure VMs to be automatically spun up as game servers globally according to your budget and demand when using our service. In order to do so, you don't explicitly create VMs but define parameters that determine how they get created on your behalf. This process is called deploying or creating a build.
+## Create and deploy Linux container images
+
+This section outlines specific steps to help you create and deploy Linux container images.
+
+As described in [Create virtual machines (VMs)](deploying-playfab-multiplayer-server-builds.md), you configure VMs to be automatically spun up as game servers globally according to your budget and demand when using our service. In order to do so, you don't explicitly create VMs but define parameters that determine how they get created on your behalf. This process is called deploying or creating a build.
 
 PlayFab Multiplayer Servers can deploy both Linux-based and Windows-based game servers. The way builds are deployed for Linux containers are similar to Windows containers with a few important differences. To learn more, see [Windows and Linux container image differences](#windows-and-linux-container-image-differences). If you want to use PowerShell/API to manage Linux containers, see [Manage Linux container images using APIs](#manage-linux-container-images-using-apis).
 
@@ -30,8 +34,8 @@ This step is needed only if you want to use Windows development device to create
 
 [Windows Subsystem for Linux (WSL)](/windows/wsl/) enables you to use your development device in the familiar Windows environment to author and manage Linux container images. Using WSL means that you wouldn't need an overhead of a traditional Linux virtual machine or dual-boot setup.
 
-1. [Install WSL 2](/windows/wsl/). Make sure that you've restarted your machine and are using WSL 2. You also need to have successfully installed the Linux kernel update package.
-2. [Install a Linux distribution that uses WSL](/windows/wsl/install#step-6---install-your-linux-distribution-of-choice). Although our VMs use Ubuntu, you can select any distribution you want for your container image. Consider using [Ubuntu 20.04 LTS](https://www.microsoft.com/store/apps/9n6svws3rx71) or later versions.
+1. [Install WSL 2](/windows/wsl/). Make sure that you restart your machine and are using WSL 2. You also need to install the Linux kernel update package.
+2. [Install a Linux distribution that uses WSL](/windows/wsl/install#step-6---install-your-linux-distribution-of-choice). Although our VMs use Ubuntu, you can select any distribution you want for your container image. Consider using [Ubuntu 20.04 Long-Term Support (LTS)](https://www.microsoft.com/store/apps/9n6svws3rx71) or later versions.
 3. [Install Docker Desktop for Windows with WSL 2](/windows/wsl/tutorials/wsl-containers). For direct download link, go to [Docker Desktop for Windows (external)](https://hub.docker.com/editions/community/docker-ce-desktop-windows/).
 
 **Verify WSL 2 set up**
@@ -51,7 +55,7 @@ This step is needed only if you want to use Windows development device to create
 
 The Azure container registry account is associated with your PlayFab account. Only you have access to the containers uploaded there. This Azure container registry is free of charge.
 
-* In Game Manager, select your game title, then __Multiplayer__ > __Servers__. Next, select __New build__  on the right to open the build creation page.
+* In Game Manager, select your game title, then __Multiplayer__ > __Servers__. Select __New build__ to open the build creation page.
 * Select __Linux__ as the virtual machine operating system. 
 * Take note of the sign-in credentials&mdash;name, password, and customer5555555.azurecr.io, as this information is needed later
 
@@ -65,7 +69,7 @@ These steps help you create and push your custom Linux container image.
 
 #### Integrate your game server application with GSDK
 
-Similar to using Windows servers, you have to integrate your game server code with the PlayFab Multiplayer Server SDK (GSDK). This can be part of your container image.
+Similar to using Windows servers, you have to integrate your game server code with the PlayFab Multiplayer Server SDK (GSDK). The GSDK integration can be part of your container image.
 
 For instructions, see [Author a game server build](author-a-game-server-build.md) and [Integrating your title with PlayFab Game Server SDK (GSDK)](integrating-game-servers-with-gsdk.md).
 
@@ -87,7 +91,7 @@ A Dockerfile is a text file with no extension and contains all commands needed t
 
 #### Build and upload Linux container image
 
-1. Open your Linux terminal, making sure that you have installed Docker.
+1. Open your Linux terminal with Docker installed.
 2. Run the following Docker commands using the sign-in credentials obtained from the earlier step. Then follow the instructions on screen to enter your username and password.
 
 ```docker
@@ -101,11 +105,11 @@ password: HRDFOdIebJkvBAS+usa55555555
 ```
 3. Build the container image
 
-Run the command below to build the container image using the Dockerfile in the folder/directory you are in. Note that there's a "." at the end of __docker build__ command.
+Run the following command to build the container image using the Dockerfile in your current directory. There's a "." at the end of the __docker build__ command.
 
-The __-t__ flag specifies the name:tag information for your new container image. They'll be used if the build succeeds. If there are build errors, you have to fix them before moving on to the next step.
+The __-t__ flag specifies the name:tag information for your new container image. The name and tag are used if the build succeeds. If there are build errors, you have to fix them before moving on to the next step.
 
-In the example below, the repository name is __customer5555555.azurecr.io/pvp_gameserver__ and tag is __v1__. For more information, see [docker build command reference (external link)](https://docs.docker.com/engine/reference/commandline/build/) and [Building Dockerfile (external link)](https://docs.docker.com/engine/reference/builder/).
+In the following example, the repository name is __customer5555555.azurecr.io/pvp_gameserver__ and tag is __v1__. For more information, see [docker build command reference (external link)](https://docs.docker.com/engine/reference/commandline/build/) and [Building Dockerfile (external link)](https://docs.docker.com/engine/reference/builder/).
 
 When using WSL, the Windows C: drive is mounted at /mnt/c.
 * Then run __cd /mnt/c/path/to/your/Dockerfile__ to switch to the path where your Dockerfile is.
@@ -120,7 +124,7 @@ docker build -t customer5555555.azurecr.io/pvp_gameserver:v1 .
 
 4. Upload the container image
 
-Run the below commands to push the image to your Azure PlayFab Container registry. Select a meaningful and helpful name:tag combination for your uploaded container image. Then use [docker push](https://docs.docker.com/engine/reference/commandline/push/) or another container registry client, to upload your container to the Azure PlayFab operated registry.
+Run the commands to push the image to your PlayFab Container registry. Select a meaningful and helpful name:tag combination for your uploaded container image. To upload your container to the PlayFab operated registry, use [docker push](https://docs.docker.com/engine/reference/commandline/push/) or another container registry client.
 
 ```docker
 docker tag hello-world customer5555555.azurecr.io/pvp_gameserver:v1
@@ -140,12 +144,12 @@ For many developers, using Windows managed container is the preferred simple and
 > [!Note]
 > You are able to fully customize your game servers whether you are using Windows or Linux container images. When using Windows servers, you customize the managed container image by uploading assets. 
 
-The table below lists some differences when creating and using them.
+The following table lists some differences when creating and using them.
 
 | Developer options| Windows                 | Linux         |
 |------------------|-------------------------|---------------|
 | Development device OS | Windows OS | [Windows Subsystem for Linux (WSL)](#set-up-your-windows-development-device) or Linux OS (using dual-OS or VMs)|
-| Container image | Straightforward deployment using our managed container image. You can still customize the container by uploading additional files as assets. | Additional work is needed because you have to create your own custom container image that gives you complete control. |
+| Container image | Straightforward deployment using our managed container image. You can still customize the container by uploading extra files as assets. | More work is needed because you have to create your own custom container image that gives you complete control. |
 
 ## Manage Linux container images using APIs
 
@@ -154,14 +158,77 @@ You can use APIs to manage Linux container images. For the rest of build lifecyc
 * [GetContainerRegistryCredentials](/rest/api/playfab/multiplayer/multiplayer-server/get-container-registry-credentials): Retrieve a container registry address, user name, and password
 * [ListContainerImages](/rest/api/playfab/multiplayer/multiplayer-server/list-container-images) and [ListContainerImageTags](/rest/api/playfab/multiplayer/multiplayer-server/list-container-image-tags): Ensure your new image and tag are listed (sometimes it might take a couple of minutes for image to be fully registered in the system)
 * [CreateBuildWithCustomContainer](/rest/api/playfab/multiplayer/multiplayer-server/create-build-with-custom-container): Create a build with a custom container. Specify the tagged image you uploaded earlier. Ensure the following properties are set on the request:
-  * **ContainerImageReference** - The image name and tag that was uploaded earlier (and is visible in ListContainerImages and ListContainerImageTags above).
+  * **ContainerImageReference** - The image name and tag that was uploaded earlier. These values are visible in ListContainerImages and ListContainerImageTags.
   * **ContainerFlavor** - "CustomLinux"
-  * **ContainerRunCommand** (Optional) - In case your container doesn't have a default command that it runs, this can be used to provide the command to run, along with any arguments.
+  * **ContainerRunCommand** (Optional) - If your container doesn't have a default command, use this property to provide the command to run, along with any arguments.
+
+## Packaging assets for Linux process-based servers
+
+When using Linux in **process mode** (instead of container mode), you upload your game server as an asset archive rather than a container image. This section covers important packaging requirements.
+
+### Supported archive formats
+
+Assets should be uploaded as `.tar.gz`, or `.tar` files, so Unix file permissions (such as the execute bit) can be preserved during extraction.
+
+> [!WARNING]
+> **`.zip` files do not preserve Unix file permissions on Linux.** If you upload your Linux game server executable in a `.zip` archive, it loses its execute permission and fails to start with a "Permission denied" error. To work around this issue, either use `.tar.gz` instead, or set your start command to a shell script that runs `chmod +x` on your executable before launching it.
+
+### Tar.gz and tar archive structure requirements
+
+When extracting `.tar` or `.tar.gz` archives, PlayFab Multiplayer Servers strips the first directory level from the archive (equivalent to `tar --strip-components=1`). Your archive **must** contain a single top-level wrapper directory with all your game files inside it.
+
+**Proper structure** — files inside a top-level directory:
+
+```
+MyGameServer/
+├── MyGame.x86_64
+├── MyGame_Data/
+│   └── ...
+├── UnityPlayer.so
+└── start_server.sh
+```
+
+Create the archive with:
+
+```bash
+tar czf MyGameServer.tar.gz MyGameServer/
+```
+
+> [!CAUTION]
+> If your files are at the root of the archive without a wrapper directory, they are **silently skipped** during extraction. Your game server fails with "No such file or directory" errors because the executable is never written to disk.
+
+### Setting the start command
+
+For process-based servers, the start command should be **relative to the root asset folder after extraction** (that is, relative to where files end up after the top-level directory is stripped).
+
+For example, if your archive contains `MyGameServer/MyGame.x86_64`, after extraction the file is at the root of the asset folder. Set your start command to:
+
+```
+MyGame.x86_64
+```
+
+If your executable is inside a subfolder (for example, `MyGameServer/bin/MyGame.x86_64`), set the start command to:
+
+```
+bin/MyGame.x86_64
+```
+
+## Manage Linux process-based builds using APIs
+
+You can use APIs to manage Linux process-based builds. For the rest of build lifecycle (viewing usage, updating regions and standingBy configurations, deletion), manage them using Game Manager.
+
+* [CreateBuildWithProcessBasedServer](/rest/api/playfab/multiplayer/multiplayer-server/create-build-with-process-based-server): Create a build with the game server running as a process. Ensure the following properties are set on the request:
+  * **OsPlatform** - "Linux"
+  * **GameAssetReferences** - The list of game assets (uploaded as `.tar.gz` or `.tar` files). Each asset requires a **FileName** matching the uploaded asset name.
+  * **StartMultiplayerServerCommand** - The command to run when the game server starts. The path should be relative to the root asset folder after extraction (for example, `MyGame.x86_64 -server`).
+  * **Ports** - The ports to map for the build.
+  * **MultiplayerServerCountPerVm** - The number of game server instances to host on a single VM.
+  * **RegionConfigurations** - The regions to deploy to, with standby and maximum server counts.
 
 ## See also
 
 * [Intro to docker containers](/training/modules/intro-to-docker-containers/)
 * [Create your first server](create-your-first-server.md)
 * [Resources and samples](server-samples-resources.md)
-* [PlayFab Multiplayer Server SDKs](server-sdks.md)
+* [PlayFab Multiplayer Server Software Development Kits (SDKs)](server-sdks.md)
 * [API Reference](xref:titleid.playfabapi.com.multiplayer.multiplayerserver)
diff --git a/playfab-docs/multiplayer/servers/directly-debugging-game-servers.md b/playfab-docs/multiplayer/servers/directly-debugging-game-servers.md
index 528bba36e..d941ff529 100644
--- a/playfab-docs/multiplayer/servers/directly-debugging-game-servers.md
+++ b/playfab-docs/multiplayer/servers/directly-debugging-game-servers.md
@@ -52,7 +52,7 @@ This information is listed on __docker ps__:
 For more information, see [Docker networking](https://docs.docker.com/network/).
 
 > [!NOTE]
-> In both Windows and Linux, Docker containers are part of the "playfab" Docker network. You can do docker inspect network playfab to see information about the network.
+> In both Windows and Linux, Docker containers are part of the "playfab" Docker network. Use `docker inspect network playfab` to view information about the PlayFab network.
 
 #### How can I see runtime details for a container?
 
diff --git a/playfab-docs/multiplayer/servers/enable-playfab-multiplayer-servers.md b/playfab-docs/multiplayer/servers/enable-playfab-multiplayer-servers.md
index 01974a897..c8d555a79 100644
--- a/playfab-docs/multiplayer/servers/enable-playfab-multiplayer-servers.md
+++ b/playfab-docs/multiplayer/servers/enable-playfab-multiplayer-servers.md
@@ -12,16 +12,16 @@ ms.localizationpriority: medium
 
 # Enable PlayFab Multiplayer Server feature
 
-PlayFab Multiplayer Server is not automatically enabled when you sign up for a PlayFab account. In order to use and view the servers, you need to enable the feature from Game Manager or use API/PowerShell.
+PlayFab Multiplayer Server isn't automatically enabled when you sign up for a PlayFab account. In order to use and view the servers, you need to enable the feature from Game Manager or use API/PowerShell.
 
-You have to enable the feature using Game Manager if you do not yet have a payment method on the account.
+You have to enable the feature using Game Manager if you don't yet have a payment method on the account.
 
-Certain servers have limited free usage and capacity limits. They can be used during evaluation and development. If you are enrolled in paid pricing plans, you may request for additional server cores. To learn more, see [Managing Server cores quota](quota-changes.md).
+Certain servers have limited free usage and capacity limits. They can be used during evaluation and development. If you're enrolled in paid pricing plans, you may request for additional server cores. To learn more, see [Managing Server cores quota](quota-changes.md).
 
 ## Enable using Game Manager
 
-1. Log into your developer account on [PlayFab.com](https://playfab.com)
-2. Go to **My Studios and Titles** page and select your game title to display the dashboard. If you have not created one, you have to create a new title.
+1. Log into your developer account on [PlayFab.com](https://developer.playfab.com)
+2. Go to **My Studios and Titles** page and select your game title to display the dashboard. If you haven't created one, you have to create a new title.
 3. Go to **Multiplayer** > **Servers** page
 4. Select **Enable**
 
diff --git a/playfab-docs/multiplayer/servers/media/279a76f6cfe1f6d23263f57318128cde.png b/playfab-docs/multiplayer/servers/media/279a76f6cfe1f6d23263f57318128cde.png
index 81d1ab24a..6235a4e8a 100644
Binary files a/playfab-docs/multiplayer/servers/media/279a76f6cfe1f6d23263f57318128cde.png and b/playfab-docs/multiplayer/servers/media/279a76f6cfe1f6d23263f57318128cde.png differ
diff --git a/playfab-docs/multiplayer/servers/media/2b450620e7f7af30133262d510ecd90d.png b/playfab-docs/multiplayer/servers/media/2b450620e7f7af30133262d510ecd90d.png
index 1a6ffa608..dc023cc9e 100644
Binary files a/playfab-docs/multiplayer/servers/media/2b450620e7f7af30133262d510ecd90d.png and b/playfab-docs/multiplayer/servers/media/2b450620e7f7af30133262d510ecd90d.png differ
diff --git a/playfab-docs/multiplayer/servers/media/LinuxContainer.PNG b/playfab-docs/multiplayer/servers/media/LinuxContainer.PNG
index a39aefa3a..eb22e9eec 100644
Binary files a/playfab-docs/multiplayer/servers/media/LinuxContainer.PNG and b/playfab-docs/multiplayer/servers/media/LinuxContainer.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/LinuxProcess.PNG b/playfab-docs/multiplayer/servers/media/LinuxProcess.PNG
index 9ad7e9258..e7f579cca 100644
Binary files a/playfab-docs/multiplayer/servers/media/LinuxProcess.PNG and b/playfab-docs/multiplayer/servers/media/LinuxProcess.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/MPSBuildAssets.PNG b/playfab-docs/multiplayer/servers/media/MPSBuildAssets.PNG
index 6b6b7d698..f337e165b 100644
Binary files a/playfab-docs/multiplayer/servers/media/MPSBuildAssets.PNG and b/playfab-docs/multiplayer/servers/media/MPSBuildAssets.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/WindowsContainer.PNG b/playfab-docs/multiplayer/servers/media/WindowsContainer.PNG
index 26c1c8314..ae5a51066 100644
Binary files a/playfab-docs/multiplayer/servers/media/WindowsContainer.PNG and b/playfab-docs/multiplayer/servers/media/WindowsContainer.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/WindowsProcess.PNG b/playfab-docs/multiplayer/servers/media/WindowsProcess.PNG
index 0344e0b91..b6ec3d3fb 100644
Binary files a/playfab-docs/multiplayer/servers/media/WindowsProcess.PNG and b/playfab-docs/multiplayer/servers/media/WindowsProcess.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/a64d39fac095bd4aee45b5b9ac410ade.png b/playfab-docs/multiplayer/servers/media/a64d39fac095bd4aee45b5b9ac410ade.png
index b3a7a6db7..83b23e512 100644
Binary files a/playfab-docs/multiplayer/servers/media/a64d39fac095bd4aee45b5b9ac410ade.png and b/playfab-docs/multiplayer/servers/media/a64d39fac095bd4aee45b5b9ac410ade.png differ
diff --git a/playfab-docs/multiplayer/servers/media/copy-host-id.PNG b/playfab-docs/multiplayer/servers/media/copy-host-id.PNG
index 4cc2e1ce2..757c53abf 100644
Binary files a/playfab-docs/multiplayer/servers/media/copy-host-id.PNG and b/playfab-docs/multiplayer/servers/media/copy-host-id.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/assetDetails.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/assetDetails.PNG
index 36afd1ac4..709fe89c0 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/assetDetails.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/assetDetails.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/buildDetails.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/buildDetails.PNG
index 18436eec0..08b5b11cb 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/buildDetails.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/buildDetails.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/buildDetailsPage.png b/playfab-docs/multiplayer/servers/media/create-your-first-server/buildDetailsPage.png
index 3504d8cbd..a32ec79c1 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/buildDetailsPage.png and b/playfab-docs/multiplayer/servers/media/create-your-first-server/buildDetailsPage.png differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/networkDetails.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/networkDetails.PNG
index 75cec6247..8f7a470a9 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/networkDetails.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/networkDetails.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/regionDetails.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/regionDetails.PNG
index 21b3596ea..4774c699f 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/regionDetails.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/regionDetails.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/server-deployed.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/server-deployed.PNG
index e597806fc..315318e8e 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/server-deployed.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/server-deployed.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings-2.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings-2.PNG
index 6deb468da..80f40a90e 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings-2.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings-2.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings-process.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings-process.PNG
index 2b7e622c0..413c507b4 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings-process.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings-process.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings.PNG
index fc86d8f98..ddbe2ac8c 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/server-network-settings.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/server-new-build-container-linux.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/server-new-build-container-linux.PNG
index d5b1a1dda..81237db28 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/server-new-build-container-linux.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/server-new-build-container-linux.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/serverDetails.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/serverDetails.PNG
index eeeeb35cb..f9d80c772 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/serverDetails.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/serverDetails.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-api-settings-option.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-api-settings-option.PNG
index 66166e5c2..077e1f48a 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-api-settings-option.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-api-settings-option.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-api-settings.png b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-api-settings.png
index 84a1a5566..a10bd58c5 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-api-settings.png and b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-api-settings.png differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-build-info.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-build-info.PNG
index 044043c9a..81704b879 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-build-info.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-build-info.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-network-tcp.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-network-tcp.PNG
index 5902b49f8..dac66323d 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-network-tcp.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-network-tcp.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-os1.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-os1.PNG
index 317b81500..f229a987c 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-os1.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-os1.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-os3.PNG b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-os3.PNG
index 06e13560d..6aec0178b 100644
Binary files a/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-os3.PNG and b/playfab-docs/multiplayer/servers/media/create-your-first-server/windowsrunner-os3.PNG differ
diff --git a/playfab-docs/multiplayer/servers/media/d7bbed8dedd7e1774fc19e6afb5ac414.png b/playfab-docs/multiplayer/servers/media/d7bbed8dedd7e1774fc19e6afb5ac414.png
index 3209cfaac..40ac937ba 100644
Binary files a/playfab-docs/multiplayer/servers/media/d7bbed8dedd7e1774fc19e6afb5ac414.png and b/playfab-docs/multiplayer/servers/media/d7bbed8dedd7e1774fc19e6afb5ac414.png differ
diff --git a/playfab-docs/multiplayer/servers/media/dd7c75987e0c8574fad2855c7959d727.png b/playfab-docs/multiplayer/servers/media/dd7c75987e0c8574fad2855c7959d727.png
index 588bb8e13..69f64711b 100644
Binary files a/playfab-docs/multiplayer/servers/media/dd7c75987e0c8574fad2855c7959d727.png and b/playfab-docs/multiplayer/servers/media/dd7c75987e0c8574fad2855c7959d727.png differ
diff --git a/playfab-docs/multiplayer/servers/media/ospatchupdate_ux.png b/playfab-docs/multiplayer/servers/media/ospatchupdate_ux.png
index 280c6b615..c0a9a72af 100644
Binary files a/playfab-docs/multiplayer/servers/media/ospatchupdate_ux.png and b/playfab-docs/multiplayer/servers/media/ospatchupdate_ux.png differ
diff --git a/playfab-docs/multiplayer/servers/media/quota-change-properties.png b/playfab-docs/multiplayer/servers/media/quota-change-properties.png
index e3ad1ac6d..0ef65fcc3 100644
Binary files a/playfab-docs/multiplayer/servers/media/quota-change-properties.png and b/playfab-docs/multiplayer/servers/media/quota-change-properties.png differ
diff --git a/playfab-docs/multiplayer/servers/media/tutorials/game-manager-linux.png b/playfab-docs/multiplayer/servers/media/tutorials/game-manager-linux.png
index ef4663667..52bd8752c 100644
Binary files a/playfab-docs/multiplayer/servers/media/tutorials/game-manager-linux.png and b/playfab-docs/multiplayer/servers/media/tutorials/game-manager-linux.png differ
diff --git a/playfab-docs/multiplayer/servers/media/tutorials/game-manager-settings-api-features-allow-client-to-start-games.png b/playfab-docs/multiplayer/servers/media/tutorials/game-manager-settings-api-features-allow-client-to-start-games.png
index 02e5473ae..62d1a07c1 100644
Binary files a/playfab-docs/multiplayer/servers/media/tutorials/game-manager-settings-api-features-allow-client-to-start-games.png and b/playfab-docs/multiplayer/servers/media/tutorials/game-manager-settings-api-features-allow-client-to-start-games.png differ
diff --git a/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build-navAUG2019.png b/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build-navAUG2019.png
index 8ee0def4b..d5eff586d 100644
Binary files a/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build-navAUG2019.png and b/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build-navAUG2019.png differ
diff --git a/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build-quickstart.png b/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build-quickstart.png
index b8b6eeaee..d5eff586d 100644
Binary files a/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build-quickstart.png and b/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build-quickstart.png differ
diff --git a/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build.png b/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build.png
index 644efb3ec..d5eff586d 100644
Binary files a/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build.png and b/playfab-docs/multiplayer/servers/media/tutorials/game-manager-thunderhead-new-build.png differ
diff --git a/playfab-docs/multiplayer/servers/media/tutorials/new-build-button.png b/playfab-docs/multiplayer/servers/media/tutorials/new-build-button.png
index 560135fba..a6c6f7675 100644
Binary files a/playfab-docs/multiplayer/servers/media/tutorials/new-build-button.png and b/playfab-docs/multiplayer/servers/media/tutorials/new-build-button.png differ
diff --git a/playfab-docs/multiplayer/servers/os-patch-updates.md b/playfab-docs/multiplayer/servers/os-patch-updates.md
index c2674de8d..3e0cef67e 100644
--- a/playfab-docs/multiplayer/servers/os-patch-updates.md
+++ b/playfab-docs/multiplayer/servers/os-patch-updates.md
@@ -12,11 +12,11 @@ ms.localizationpriority: medium
 
 # OS patch updates for Windows
 
-Playfab Multiplayers Servers managed Windows containers undergo a methodical OS patch update process to ensure game servers are operating with the latest security updates.  Each month, Azure Compute certifies a Windows OS image that is integrated into Multiplayer Servers for developers to choose from the "Windows Server Core Preview" toggle during the build creation process.  Developers are encouraged to test their non-production game servers built with the "Windows Server Core Preview" option.  
+PlayFab Multiplayers Servers managed Windows containers undergo a methodical OS patch update process to ensure game servers are operating with the latest security updates. Each month, Azure Compute certifies a Windows OS image that is integrated into Multiplayer Servers for developers to choose from the "Windows Server Core Preview" toggle during the build creation process. Developers are encouraged to test their non-production game servers built with the "Windows Server Core Preview" option.  
 
 ![Multiplayer - OS Patch Update UX](media/ospatchupdate_ux.png)
 
-After 30 days, Multiplayer Servers will migrate the Windows Server Core Preview to the Windows Server Core image option - signaling a PlayFab approved OS image for production readiness.  This process will repeat every 30 days, cycling an OS preview image to its mainline OS core image.  If a game server built with OS core version that doesn’t match PlayFab’s OS core version, PlayFab will auto-update your game build server with the latest mainline OS core image.  This process is applied automatically with no build changes required by the developer.   
+After 30 days, Multiplayer Servers will migrate the Windows Server Core Preview to the Windows Server Core image option - signaling a PlayFab approved OS image for production readiness. This process repeats every 30 days, cycling an OS preview image to its mainline OS core image. If a game server built with OS core version that doesn’t match PlayFab’s OS core version, PlayFab will auto-update your game build server with the latest mainline OS core image. This process is applied automatically with no build changes required by the developer.   
 
 ## Patch update cycle
 
@@ -27,24 +27,24 @@ The following image illustrates the OS patch level update cycle.
 
 | Stage  | Stakeholder  | Description   |
 |---|---|---|
-| 1 | Customer |  Continuous integration & test process deploys production game builds with OS core and tests game builds with OS preview |
+| 1 | Customer |  Continuous integration and test process deploys production game builds with OS core and tests game builds with OS preview |
 | 2 | Azure |  MPS validates new published Windows OS patch |
 | 3 | MPS |  PlayFab replaces MPS OS preview with Windows OS patch |
 | 4 | MPS |  PlayFab replaces MPS OS core with MPS OS preview 30-days prior |
 | 5 | MPS |  PlayFab auto-updates game builds with OS Core |
 
-## Best Practices
+## Best practices
 
 1. Developers are encouraged to create and test their non-production game server builds with the OS preview image option.
-1. Developers with a mature build and continuous integration & deployment process should take into consideration that OS image updates cycle every 30 days
+1. Developers with a mature build and continuous integration and deployment process should take into consideration that OS image updates cycle every 30 days
 
 ## Constraints
 
 1. The patch update process occurs monthly
-1. Developers cannot opt out of the monthly OS patch level updates
-1. The patch update process is only applicable to Windows managed containers and does not apply to custom containers or Linux.
+1. Developers can't opt out of the monthly OS patch level updates
+1. The patch update process is only applicable to Windows managed containers and doesn't apply to custom containers or Linux.
 
 > [!NOTE]
 >
-> - Game server builds are immutable once created.  Therefore, developers cannot toggle between OS image preview and OS image core.
-> - A game server operating in production will be auto-updated to the latest OS core image version if the version that the build was made is older than the latest.  This will be applied automatically for any new multiplayer server allocation request only.
+> - Game server builds are immutable once created. Therefore, developers can't toggle between OS image preview and OS image core.
+> - A game server operating in production will be auto-updated to the latest OS core image version if the version that the build was made is older than the latest. This will be applied automatically for any new multiplayer server allocation request only.
diff --git a/playfab-docs/multiplayer/servers/quickstart-for-multiplayer-servers-api-powershell.md b/playfab-docs/multiplayer/servers/quickstart-for-multiplayer-servers-api-powershell.md
index d8f7fada1..cd2e391f8 100644
--- a/playfab-docs/multiplayer/servers/quickstart-for-multiplayer-servers-api-powershell.md
+++ b/playfab-docs/multiplayer/servers/quickstart-for-multiplayer-servers-api-powershell.md
@@ -27,7 +27,7 @@ Make sure you have completed the following steps.
 ## 1. Get your title ID and developer secret key
 
 * Get your PlayFab title ID
-    * Log into your developer account on [PlayFab.com](https://playfab.com)
+    * Log into your developer account on [PlayFab.com](https://developer.playfab.com)
     * In Game Manager, go to **My Studios and Titles** page. Look for your game title and get the PlayFab game title ID
 
 * Get the developer secret key for the title
diff --git a/playfab-docs/multiplayer/servers/quickstart-for-multiplayer-servers-game-manager.md b/playfab-docs/multiplayer/servers/quickstart-for-multiplayer-servers-game-manager.md
index 245ac30b1..44601ca14 100644
--- a/playfab-docs/multiplayer/servers/quickstart-for-multiplayer-servers-game-manager.md
+++ b/playfab-docs/multiplayer/servers/quickstart-for-multiplayer-servers-game-manager.md
@@ -28,7 +28,7 @@ Make sure you've completed the following steps.
 
 ## Steps
 
-1. Log into your developer account on [PlayFab.com](https://playfab.com)
+1. Log into your developer account on [PlayFab.com](https://developer.playfab.com)
 2. Go to **My Studios and Titles** page and select your game title to display the dashboard
 3. Go to **Multiplayer** > **Servers** page, select **New Build** at the top right to create a new build
 4. Use "My build" as the Build Name
diff --git a/playfab-docs/multiplayer/servers/server-samples-resources.md b/playfab-docs/multiplayer/servers/server-samples-resources.md
index 654322cde..e74a1b196 100644
--- a/playfab-docs/multiplayer/servers/server-samples-resources.md
+++ b/playfab-docs/multiplayer/servers/server-samples-resources.md
@@ -1,7 +1,7 @@
 ---
 title: Multiplayer Servers samples and resources
 author: joannaleecy
-description: Samples and resources for Azure PlayFab Multiplayer Game Servers.
+description: Samples and resources for PlayFab Multiplayer Game Servers.
 ms.author: jenelleb
 ms.date: 04/01/2021
 ms.topic: article
diff --git a/playfab-docs/multiplayer/servers/server-sdks.md b/playfab-docs/multiplayer/servers/server-sdks.md
index 4ff381a1b..499eeec78 100644
--- a/playfab-docs/multiplayer/servers/server-sdks.md
+++ b/playfab-docs/multiplayer/servers/server-sdks.md
@@ -1,7 +1,7 @@
 ---
-title: Azure PlayFab Multiplayer Game Server SDKs
+title: PlayFab Multiplayer Game Server SDKs
 author: joannaleecy
-description: Learn about the SDKs for Azure PlayFab Multiplayer Game Servers.
+description: Learn about the SDKs for PlayFab Multiplayer Game Servers.
 ms.author: jenelleb
 ms.date: 01/21/2021
 ms.topic: article
@@ -10,9 +10,9 @@ keywords: playfab, multiplayer, networking, party, sdk, sample
 ms.localizationpriority: medium
 ---
 
-# Azure Playfab Multiplayer Game Server SDKs
+# PlayFab Multiplayer Game Server SDKs
 
-This topic lists the different flavors of Azure PlayFab Multiplayer Game Server SDKs (GSDKs) we have today.
+This topic lists the different flavors of PlayFab Multiplayer Game Server SDKs (GSDKs) we have today.
 
 ## Download links
 
diff --git a/playfab-docs/multiplayer/servers/server-terms.md b/playfab-docs/multiplayer/servers/server-terms.md
index 656c86097..ed5a38b2a 100644
--- a/playfab-docs/multiplayer/servers/server-terms.md
+++ b/playfab-docs/multiplayer/servers/server-terms.md
@@ -1,7 +1,7 @@
 ---
-title: Playfab Multiplayer Server terms
+title: PlayFab Multiplayer Server terms
 author: joannaleecy
-description: Playfab Multiplayer Server terms.
+description: PlayFab Multiplayer Server terms.
 ms.author: jenelleb
 ms.date: 03/10/2021
 ms.topic: article
@@ -12,18 +12,18 @@ ms.localizationpriority: medium
 
 # Terminology
 
-This topic explains the terms used for PlayFab Multiplayer Server. We understand that it can be confusing since the word server is used in multiple places.
+This article explains the terms used for PlayFab Multiplayer Server. We understand that it can be confusing since the word server is used in multiple places.
 
-The internal structure of the PlayFab Multiplayer Server and general relationship of the various components is also lightly covered here. For details, see [Basics of a PlayFab game server](basics-of-a-playFab-game-server.md).
+The article also briefly covers the internal structure of the PlayFab Multiplayer Server and the general relationship of the various components. For more information, see [Basics of a PlayFab game server](basics-of-a-playFab-game-server.md).
 
 ## PlayFab Multiplayer Servers
 
-PlayFab Multiplayer Servers can also be known as PlayFab virtual machines (VMs) and Servers. 
+PlayFab Multiplayer Servers are also known as PlayFab virtual machines (VMs) and Servers. 
 
-They are Azure VMs with PlayFab managed service functionalities. Added functionalities optimize them for use as multiplayer game servers.
+They're Azure VMs with PlayFab managed service functionalities. The added functionalities optimize them for use as multiplayer game servers.
 
 Each PlayFab VM:
-* Has a component known as *PlayFab VM agent*. PlayFab VM agent provides information about your game server's current state, health status, players that are currently connected, and other telemtry.
+* Has a component known as *PlayFab VM agent*. PlayFab VM agent provides information about your game server's current state, health status, players that are currently connected, and other telemetry.
 * Can have multiple containers (game servers) running on them. Containers are a way to wrap up an application into its own isolated package. To learn more, see [What is a container?](https://azure.microsoft.com/overview/what-is-a-container/)
 
 ### Game server containers
@@ -32,24 +32,24 @@ Game servers run as containerized applications. This means that your game server
 
 Each container:
 * Functions as a game server
-* Has a PlayFab Multiplayer Game Server Build.  It is your usual game server build that is integrated with the PlayFab Game Server SDK (GSDK). Specifically, the code for the game server executable must include the GSDK and implement specific methods using APIs in the GSDK. This enables your game server to be connected to the PlayFab VM agent.
+* Has a PlayFab Multiplayer Game Server Build. It is your usual game server build that is integrated with the PlayFab Game Server SDK (GSDK). Specifically, the code for the game server executable must include the GSDK and implement specific methods using APIs in the GSDK. This integration enables your game server to connect to the PlayFab VM agent.
 
-Image below illustrates the various components of a PlayFab Multiplayer Server.
+The following image illustrates the various components of a PlayFab Multiplayer Server.
 ![PlayFab Multiplayer Server components](media/tutorials/multiplayer-server-hosting-service-diagram.png)
 
 ## Definition of key terms
 
-* **Game server executable**: This is a game server application that runs in containers of PlayFab VMs. It may be a simple network repeater, a fully authoritative game server running physics and AI, or anything in between. All game server executables needs to be integrated with PlayFab Game Server SDK (GSDK). This allows your game server to be able to interact with the PlayFab Multiplayer platform service.
+* **Game server executable**: This term refers to a game server application that runs in containers on PlayFab VMs. It might be a simple network repeater, a fully authoritative game server running physics and AI, or anything in between. All game server executables need to be integrated with PlayFab Game Server SDK (GSDK). By using this SDK, your game server can interact with the PlayFab Multiplayer platform service.
 
-* **Game server build**: This is the full set of content that is uploaded onto the game server. It includes the game server executable packaged with all the assets and certificates needed. It can be uploaded as individual certificates, zip files, and/or a container image. If you don't need a custom container image, you can use PlayFab managed Windows containers.
+* **Game server build**: This term refers to the full set of content that you upload onto the game server. It includes the game server executable packaged with all the assets and certificates needed. You can upload it as individual certificates, zip files, and/or a container image. If you don't need a custom container image, you can use PlayFab managed Windows containers.
 
-* **PlayFab Multiplayer Game Server Build**: This is the only type of game server build that can be used in PlayFab Multiplayer Servers. It is your usual game server build (as defined above) that is integrated with the PlayFab Game Server SDK (GSDK). Specifically, the code for the game server executable must include the GSDK and implement specific methods using APIs in the GSDK.
+* **PlayFab Multiplayer Game Server Build**: This term refers to the only type of game server build that you can use in PlayFab Multiplayer Servers. It's your usual game server build (as defined above) that you integrate with the PlayFab Game Server SDK (GSDK). Specifically, the code for the game server executable must include the GSDK and implement specific methods by using APIs in the GSDK.
 
-* **Game server**: This is your game server executable running in a container. There may be multiple containers (servers) running on a single virtual machine.
+* **Game server**: This term refers to your game server executable running in a container. A single virtual machine can run multiple containers (servers).
 
 * **PlayFab VM agent**: This agent is built into PlayFab VMs and facilitates key server interactions with the *PlayFab Multiplayer platform service*. The GSDK in the game server executable connects your game server to the PlayFab agent.
 
-* **PlayFab Multiplayer platform service**: Managed service that runs in the background for PlayFab Multiplayer Servers. It communicates information through PlayFab VM agent about your game server's current state, health status, players that are currently connected, and other telemtry.
+* **PlayFab Multiplayer platform service**: This managed service runs in the background for PlayFab Multiplayer Servers. It communicates information through the PlayFab VM agent about your game server's current state, health status, players that are currently connected, and other telemetry.
 
 ## Next steps
 
diff --git a/playfab-docs/multiplayer/servers/toc.yml b/playfab-docs/multiplayer/servers/toc.yml
index e492edf73..089c091a5 100644
--- a/playfab-docs/multiplayer/servers/toc.yml
+++ b/playfab-docs/multiplayer/servers/toc.yml
@@ -36,7 +36,7 @@
     href: deploy-using-game-manager.md
   - name: Deploy builds using PowerShell/API
     href: deploy-using-powershell-api.md
-  - name: Create Linux container images
+  - name: Create and deploy Linux Builds
     href: deploying-linux-based-builds.md
   - name: Server build lifecycle
     href: multiplayer-build-lifecycle.md
diff --git a/playfab-docs/multiplayer/servers/using-playfab-servers-to-host-games.md b/playfab-docs/multiplayer/servers/using-playfab-servers-to-host-games.md
index 425f0e571..dd23556de 100644
--- a/playfab-docs/multiplayer/servers/using-playfab-servers-to-host-games.md
+++ b/playfab-docs/multiplayer/servers/using-playfab-servers-to-host-games.md
@@ -20,7 +20,7 @@ As part of configuration process, you would upload a game server build that woul
 
 ## What you need
 
-* Developer account on [PlayFab.com](https://playfab.com)
+* Developer account on [PlayFab.com](https://developer.playfab.com)
 * [Enable PlayFab Multiplayer Servers feature](enable-playfab-multiplayer-servers.md)
 * Your server-client game source code
 
diff --git a/playfab-docs/multiplayer/servers/vmstartupscript.md b/playfab-docs/multiplayer/servers/vmstartupscript.md
index 5a7a2fa88..edd2a1d0f 100644
--- a/playfab-docs/multiplayer/servers/vmstartupscript.md
+++ b/playfab-docs/multiplayer/servers/vmstartupscript.md
@@ -17,7 +17,7 @@ ms.localizationpriority: medium
 > [!Important]
 > This feature is in preview. You're welcome to start using it today and give us your feedback. Instructions on how to connect with us is provided at the end of the article. Note that technical support is limited during preview.
 
-VmStartupScript allows you to run a custom script on virtual machines (VMs) that are used in Azure PlayFab Multiplayer Servers (MPS). MPS is optimized for game servers hosting, making it easy for your title to scale dynamically according to demand. To improve the ease of customizing a large number of servers quickly during VM initialization, the custom script can run on every underlying VM that hosts your game servers. It can be used to accomplish tasks such as installing custom software, modifying security settings, using a custom service to log game server output and metrics, and more.
+VmStartupScript allows you to run a custom script on virtual machines (VMs) that are used in PlayFab Multiplayer Servers (MPS). MPS is optimized for game servers hosting, making it easy for your title to scale dynamically according to demand. To improve the ease of customizing a large number of servers quickly during VM initialization, the custom script can run on every underlying VM that hosts your game servers. It can be used to accomplish tasks such as installing custom software, modifying security settings, using a custom service to log game server output and metrics, and more.
 
 > [!Note]
 > This is an advanced feature that should be used with extreme caution. The running script executes in the Virtual Machine (VM) level with admin (root) privileges. If not used properly, it can potentially disrupt the regular flow of the running game servers, or even prevent them from running at all. The end user is responsible for the content of the script.
diff --git a/playfab-docs/multiplayer/servers/windows-runner-sample.md b/playfab-docs/multiplayer/servers/windows-runner-sample.md
index 58374f669..b00478fc6 100644
--- a/playfab-docs/multiplayer/servers/windows-runner-sample.md
+++ b/playfab-docs/multiplayer/servers/windows-runner-sample.md
@@ -20,14 +20,14 @@ This tutorial lists the steps to get the sample set up ready for use with the Pl
 1. [Configure API feature option](#configure-api-feature-option)
 2. Create a PlayFab Multiplayer Game Server Build: [Server set up](#server-set-up)
 3. [Create servers by deploying a build](#create-servers-by-deploying-a-build)
-4. Request multiplayer servers: [Client set up](#client-set-up). This is needed so you can start a client that connects to the servers
+4. Request multiplayer servers: [Client set up](#client-set-up). This request is needed so you can start a client that connects to the servers
 
 ## Configure API feature option
 
  > [!Note]
 > This step is needed only for running this sample. You do not need to allow clients to start games unless your title requires this set up. 
 
-* Log into your developer account on [PlayFab.com](https://playfab.com) to use the Game Manager portal
+* Log into your developer account on [PlayFab.com](https://developer.playfab.com) to use the Game Manager portal
 * Select your game title
 * Select the settings icon > __API features__ as shown in the image below.
 
@@ -44,16 +44,16 @@ Describes how to get the PlayFab Multiplayer Game Server Build.
 * [PlayFab Game Server SDK](https://github.com/PlayFab/gsdk) of the PlayFab Multiplayer Server Build for the Windows Runner sample. 
 * If you prefer to build this on your own:
     * Get the [Windows Runner C# sample](https://github.com/PlayFab/MpsSamples/tree/master/WindowsRunnerCSharp) using standard Git methods or downloading this as a zip file.
-    * Open the project using Visual Studio 2017 or later. This should automatically trigger dependencies like the latest [PlayFab Game Server SDK (GSDK) nuget package](https://www.nuget.org/packages/com.playfab.csharpgsdk) to be downloaded.
-    * Compile and build the WindowsRunnerCSharp.csproj in release x64 configuration. You would get a game server build that is integrated with the GSDK, making this a valid PlayFab Multiplayer Game Server Build.
-    * Go to the bin folder and zip up all the x64 release binaries. There should be no internal folder structure, the zip file should be a simple flat collection of files, as shown in the image below.
+    * Open the project using Visual Studio 2017 or later. This should automatically trigger dependencies like the latest [PlayFab Game Server SDK (GSDK) NuGet package](https://www.nuget.org/packages/com.playfab.csharpgsdk) to be downloaded.
+    * Compile and build the WindowsRunnerCSharp.csproj in release x64 configuration. You would get a game server build that is integrated with the GSDK, making it a valid PlayFab Multiplayer Game Server Build.
+    * Go to the bin folder and zip up all the x64 release binaries. There should be no internal folder structure. The zip file should be a flat collection of files, as shown in the image below.
 
     ![GSDK Sample Output](media/tutorials/gsdk-sample-output.png)
 
 > [!Tip]
-> To cross-check, you can compare your build output with the compiled version provided in the link above.
+> To cross-check, you can compare your build output with the compiled version provided in the link.
 
-When you have the zip file, you are ready to start [deploying a build](#create-servers-by-deploying-a-build).
+When you have the zip file, you're ready to start [deploying a build](#create-servers-by-deploying-a-build).
 
 ## Create servers by deploying a build
 
@@ -62,7 +62,7 @@ You can deploy a build using one of the following methods.
 * [Use Game Manager to deploy and configure servers](quickstart-for-multiplayer-servers-game-manager.md)
 * [Use PowerShell to deploy and configure servers](quickstart-for-multiplayer-servers-api-powershell.md)
 
-For some settings, it may be easier to configure using the web interface&mdash;Game Manager.
+For some settings, it might be easier to configure using the web interface&mdash;Game Manager.
 
 Next, [set up and run the client](#client-set-up) to connect to the deployed servers.
 
@@ -85,7 +85,7 @@ Describes how to get the Windows Runner client application to connect to the gam
         * Copy the __titleId__ and __buildId__ and paste it somewhere convenient
 
 * Get the [Windows Runner C# sample](https://github.com/PlayFab/MpsSamples/tree/master/WindowsRunnerCSharp) using standard Git methods or downloading this as a zip file. Skip if you have done this earlier.
-* Open the project using Visual Studio 2017 or later. This should automatically trigger dependencies like the latest [Game Server SDK nuget package](https://www.nuget.org/packages/com.playfab.csharpgsdk) to be downloaded.
+* Open the project using Visual Studio 2017 or later. This should automatically trigger dependencies like the latest [Game Server SDK NuGet package](https://www.nuget.org/packages/com.playfab.csharpgsdk) to be downloaded.
 * Compile and build the __WindowsRunnerCSharpClient.csproj__ in release x64 configuration
 * Open Command Prompt and navigate to the output folder of this project
 * Run the WindowsRunnerCSharpClient using this command line, replacing \<TitleId> and \<BuildID> with the values above: __dotnet WindowsRunnerCSharpClient.dll --titleId \<TitleId> --buildId \<BuildId>__
diff --git a/playfab-docs/player-progression/game-saves/conflicts.md b/playfab-docs/player-progression/game-saves/conflicts.md
index 327424dcc..977c7c91a 100644
--- a/playfab-docs/player-progression/game-saves/conflicts.md
+++ b/playfab-docs/player-progression/game-saves/conflicts.md
@@ -3,32 +3,208 @@ title: Game Saves conflicts
 author: jasonsandlin
 description: Game Saves conflicts
 ms.author: jasonsa
-ms.date: 07/01/2025
+ms.date: 01/06/2026
 ms.topic: article
 ms.service: azure-playfab
 keywords: playfab, game saves
 ms.localizationpriority: medium
 ---
 
-## Game Saves conflicts
+# Game Save conflicts and atomic units
 
-Save conflicts occur when the same game data has been modified on multiple devices, and the system needs to determine which version to keep.
+## Overview
 
-### When Conflicts Happen
-Conflicts only occur during the sync operation (`PFGameSaveFilesAddUserWithUiAsync`) when **both** conditions are true:
-1. **Local changes exist**: Files have been modified locally since the last sync
-2. **Cloud changes exist**: Another device has uploaded newer data since the last sync
+Save conflicts happen when you modify the same game data on multiple devices. The system needs to decide which version to keep. To design your save data structure, you need to understand how the system detects and resolves conflicts.
+
+## When conflicts happen
+
+Conflicts happen during the sync operation (`PFGameSaveFilesAddUserWithUiAsync`) only when all of the following conditions are true:
+
+1. **Local changes exist**: You modified files locally since the last sync.
+2. **Cloud changes exist**: Another device uploaded newer data since the last sync.
+3. **Same atomic unit**: Both changes are in the same root-level folder.
+
+### Conflict detection matrix
+
+| Local device changes | Cloud has changes in same atomic unit | Result |
+|---------------------|--------------------------------------|--------|
+| Modified files | Yes | **CONFLICT** |
+| Deleted files | Yes | **CONFLICT** |
+| No changes | Yes | Download proceeds |
+| Modified files | No | Upload proceeds |
+| Deleted files | No | Delete proceeds |
+
+## What is an atomic unit?
+
+Some file sync systems treat conflicts on a file-by-file basis. If the same file needs to be uploaded and downloaded, there's a conflict. In Game Saves, each root-level subfolder is treated as an *atomic unit*.
+
+> **Each root-level subfolder is one atomic unit.**
+
+If any files or subfolders inside a root-level subfolder need to be downloaded and any files or folders in that same root subfolder need to be uploaded, then the entire atomic unit is in conflict.
+
+This approach allows you to:
+- **Maintain data integrity**: Interdependent files stay consistent together
+- **Provide isolation**: Independent data in separate folders sync without conflicts
+- **Minimize conflicts**: Changes to different atomic units on different devices merge automatically
+
+### Example save structure
+
+```
+SaveRoot/
+├── save.dat              ← Atomic unit: root
+├── player.dat            ← Atomic unit: root
+├── Save1/
+│   ├── stats.json        ← Atomic unit: Save1
+│   └── inventory.json    ← Atomic unit: Save1
+├── Save2/
+│   ├── stats.json        ← Atomic unit: Save2
+│   └── inventory.json    ← Atomic unit: Save2
+└── WorldState/
+    ├── map.dat           ← Atomic unit: WorldState
+    └── npcs/
+        └── positions.dat ← Atomic unit: WorldState
+```
+
+### Conflict scenarios
+
+| Device A changes | Device B changes | Conflict? | Why |
+|-----------------|------------------|-----------|-----|
+| `Save1/stats.json` | `Save1/inventory.json` | **YES** | Same atomic unit: Save1 |
+| `Save1/stats.json` | `Save2/stats.json` | No | Different units: Save1 vs Save2 |
+| `WorldState/map.dat` | `WorldState/npcs/positions.dat` | **YES** | Same atomic unit: WorldState |
+| `save.dat` | `Save1/stats.json` | No | Different units: root vs Save1 |
+| `player.dat` | `save.dat` | **YES** | Same atomic unit: root |
+
+## Root-level files: special case
+
+**All files at the save root share one atomic unit.**
+
+The system groups all files you place directly in the save root (not in any subfolder) together as a single atomic unit. If you modify one root-level file locally and another device modifies a different root-level file, this difference triggers a conflict.
+
+| Device A (local) | Device B (cloud) | Same Atomic Unit? | Result |
+|-----------------|------------------|-------------------|--------|
+| Modifies `rootfile1.txt` | Modifies `rootfile2.txt` | ✅ YES | **CONFLICT** |
+| Modifies `rootfile1.txt` | Modifies `save1/config.ini` | ❌ NO | No conflict, both sync |
+| Deletes `save.dat` | Modifies `progress.dat` | ✅ YES | **CONFLICT** |
+
+## User choice options
 
-### Conflict Resolution Approach
-Some file sync systems treat conflicts on a file-by-file basis – if the same file needs to be uploaded and also needs to be downloaded, then there's a conflict. In Game Saves, each root level subfolder is instead treated as an atomic unit. If there are any files or subfolders inside a root level subfolder that need to be downloaded and any files or folders in that same root subfolder that need to be uploaded, then the entire atomic unit is in conflict. This approach allows you to organize save data so that interdependent data integrity is maintained, while providing isolation between root subfolders for independent data that can be safely merged with changes to other atomic units. By using top level subfolders to structure your game save layout, you can minimize the likelihood of creating a conflict when changes to different atomic units happen on different devices. A slot-based game save system where each slot is a root level subfolder is a very simple example of how these atomic units can be used.
-### User Choice Options
 When conflicts occur, players choose between:
-- **Use Local Data**: Keep the device's current save data (overwrites cloud data on next upload)
-- **Use Cloud Data**: Download and use the cloud save data (overwrites local data)
 
-A conflict resolution decision applies to all atomic units that are in conflict at the time of sync. If the player chooses cloud, all the conflicting atomic units will be downloaded, and conversely, choosing local leads to all being uploaded.
+- **Use Local Data (Keep Local)**: Keep the device's current save data.
+- **Use Cloud Data (Keep Cloud)**: Download and use the cloud save data.
+
+### Critical: resolution is all or nothing
+
+> ⚠️ **Important**: While atomic units determine *when* a conflict is detected, the user's conflict resolution choice applies to the **entire save**, not per atomic unit.
+
+### Example: Mixed conflict scenario
+
+```
+SaveRoot/
+├── SlotA/ ← Local: modified, Cloud: modified  → CONFLICT
+├── SlotB/ ← Local: modified, Cloud: unchanged → Local-only change
+├── SlotC/ ← Local: unchanged, Cloud: modified → Cloud-only change
+└── SlotD/ ← Local: modified, Cloud: unchanged → Local-only change
+```
+
+**User sees conflict prompt** (due to SlotA).
+
+| User choice | SlotA | SlotB | SlotC | SlotD |
+|-------------|-------|-------|----------|--------------|
+| **Keep Local** | ✅ Local kept | ✅ Local uploaded | ❌ Cloud change **LOST** | ✅ Local uploaded |
+| **Keep Cloud** | ✅ Cloud downloaded | ❌ Local change **overwritten** | ✅ Cloud downloaded | ❌ Local change **overwritten** |
+
+### Why this matters
+
+1. **Keep Local loses cloud-only changes**: If you choose "Keep Local" because of a conflict in SlotA, you don't receive the cloud update to SlotC that another device made.
+
+2. **Keep Cloud loses local-only changes**: If you choose "Keep Cloud", the cloud state overwrites your local changes to SlotB and SlotD.
+
+3. **Rollback available**: Both choices preserve the discarded branch for future rollback capability.
+
+### Design summary
+
+| Aspect | Granularity |
+|--------|-------------|
+| Conflict **detection** | Per atomic unit (root subfolder) |
+| Conflict **resolution** | Entire save (all-or-nothing) |
+
+This all-or-nothing approach simplifies the player experience. While per-atomic-unit resolution technically maintains data consistency (since atomic units define consistency boundaries), it creates user experience challenges:
+
+- Players need to understand the concept of atomic units and folder boundaries.
+- Mixed results (some folders from local, others from cloud) can leave players confused about the final state.
+- Prompting for each conflicting atomic unit separately makes conflict resolution overwhelming.
+
+By presenting a single **Keep Local** vs **Keep Cloud** choice, players make one clear decision without needing to understand the underlying save structure.
+
+## When conflicts don't occur
+
+### Delete on both sides
+
+If both devices delete the same file (or files in the same atomic unit), **no conflict occurs**. The system recognizes that both devices agree the file should be removed.
+
+### Changes in different atomic units
+
+If Device A modifies files in `SlotA/` and Device B modifies files in `SlotB/`, no conflict occurs. Sync automatically merges both changes.
+
+## Best practices
+
+### 1. Design folder structure carefully
+
+Use subfolders for independent save units:
+
+```
+SaveRoot/
+├── Slot1/           ← Each slot is independent
+│   └── save.dat
+├── Slot2/
+│   └── save.dat
+```
+
+A slot-based game save system where each slot is a root-level subfolder is a simple example of how you can use atomic units effectively.
+
+Other examples include:
+- **Shared reference data**: Store data that any save slot might use, such as unlocked content or achievements, in its own subfolder so it syncs independently from individual save slots.
+- **Large asset collections**: If your game stores large sets of files that update independently, such as downloaded content packs or user-created levels, consider splitting them into multiple root subfolders so updates to one collection don't conflict with updates to another.
+
+### 2. Avoid root-level files for frequently modified data
+
+All root-level files share one atomic unit. Avoid placing frequently modified files at the root if you want to sync them independently.
+
+**Instead of:**
+```
+SaveRoot/
+├── autosave.dat     ← All root files = 1 atomic unit
+└── save1.dat
+└── save2.dat
+```
+
+**Consider:**
+```
+SaveRoot/
+├── AutoSave/
+│   └── autosave.dat     ← Independent unit
+└── Save1/
+    └── gamesave.dat ← Independent unit
+```
+
+### 3. Group related data together
+
+Use the same folder for files that must stay consistent together.
+
+```
+SaveRoot/
+├── Save1/
+│   ├── stats.json       ← These files are interdependent
+│   ├── inventory.json   ← and should conflict together
+│   └── quests.json
+```
+
+### 4. Minimize conflicts
+
+Upload frequently to reduce the chance of conflicts. The more often you sync, the less likely two devices have divergent changes.
+
+### 5. Monitor conflict rates
 
-### Best Practices
-- **Design folder structure carefully**: Group related save files into logical folders
-- **Minimize conflicts**: Upload frequently to reduce the chance of conflicts
-- **Clear conflict UI**: Help players understand what data they might lose with each choice
+Use [PlayStream events](playstream-events.md) to track how often conflicts occur and how players resolve them. A rising conflict rate or a strong skew toward "keep local" versus "keep remote" can signal UX or save-cadence problems worth investigating.
diff --git a/playfab-docs/player-progression/game-saves/linking.md b/playfab-docs/player-progression/game-saves/linking.md
new file mode 100644
index 000000000..e9e35ef25
--- /dev/null
+++ b/playfab-docs/player-progression/game-saves/linking.md
@@ -0,0 +1,395 @@
+---
+title: Account linking strategies for PlayFab Game Saves
+author: amccalib
+description: Requirements and strategies for linking player accounts across platforms when using PlayFab Game Saves.
+ms.author: andmcc
+ms.date: 12/05/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, game saves, account linking, cross-progression, identity linking
+ms.localizationpriority: medium
+---
+
+# Account linking strategies for PlayFab Game Saves
+
+## Primary linking identity
+
+The first requirement for any cross-progression strategy is to determine which player identity will span across gaming platforms. The player needs to be able to sign in with this identity on any device on which the game is available. For a first-party title, this is often the Microsoft account (MSA)/Xbox account. For many third parties, this is likely a publisher identity exposed through an OpenID Connect implementation. The two requirements for this player identity are:
+
+1. Available to players on every platform on which they could play the game
+2. Supported by an existing PlayFab Login call, such as `LoginWithXbox` or `LoginWithOpenIdConnect`
+
+Beyond those two requirements, it's useful if the identity supports some sort of device-based caching and silent sign-in on subsequent game launches. This isn't a hard requirement but can reduce workflow complexity and/or player friction.
+
+## Platform-native identity
+
+A platform-native identity is the account system provided by the platform on which the player is running the game. Examples include:
+- Steam: Steam account and auth ticket (`ISteamUser::GetAuthTicketForWebApi`)
+- Xbox on PC/Console: MSA/Xbox `XUserHandle` and XSTS token
+- PlayStation: PSN Online ID / account
+- Nintendo: Nintendo Service Account / device ID
+
+These identities are typically used to create and reuse a `PFLocalUserHandle` for the active player on a given device (for example, `PFLocalUserCreateHandleWithSteamUser` or wrapping an `XUserHandle`). They can also be used to authenticate via provider-specific PlayFab Login APIs (for example, `LoginWithSteam`, `LoginWithXbox`) when appropriate.
+
+In cross-progression scenarios, platform-native identities are linked to the primary linking identity, so that progress and entitlements follow the player across platforms. The recommended workflows in this document use the platform-native identity as the local user context and the primary linking identity as the cross-platform anchor.
+
+## Linking strategy options
+
+This document explores two related strategies:
+
+1. All players are **required** to link their platform-native identity with your primary linking identity before playing.
+2. Linking between the platform-native and primary linking identities is **optional** but heavily encouraged before playing.
+
+The first strategy is easier to implement and avoids difficult decisions for players involving potential lost progress down the road. It does increase initial friction getting started with the game and can lead to negative sentiment in cases where players don't see sufficient value in the upfront linking requirement. It's especially unsuitable for many free-to-play and mobile games that depend on extremely low barriers to bring in as many players as possible.
+
+The second strategy improves the up-front player experience in exchange for potential conflicts and hard decisions in the future, in addition to increased coding complexity for developers. Players can get started without any additional sign-in requirements. They can even start completely offline if the game supports it. That flexibility can create a problem down the road when they do decide to link. It's possible that the identity they link to may have preexisting progress on another platform. If that's the case, establishing the link could involve either abandoned progress or a messy merge the game will need to handle. Even if games do choose this strategy, they're encouraged to promote linking as early as possible, describe the benefits of linking, and warn of the potential risks of not linking.
+
+Ultimately, the choice between these strategies must be driven from a business perspective. One isn't clearly superior to the other. There's clear market evidence that transitioning from option 2 to option 1 after launch creates player dissatisfaction. This indicates the importance of getting this choice right early and designing around it from the start.
+
+## Desired state
+
+Regardless of strategy, the ultimate goal is to get every player into the same state. Their primary linking identity should be linked with the platform-native identity on every device on which they play. In that state, progress is consistently tied to the primary linking identity and platform-native identities can also be used as an effective proxy identity for the primary identity on all platforms.
+
+On some platforms, it's possible that the primary linking identity **is** the platform-native identity (first-party games running on an Xbox). In those cases, it becomes trivial to attain the desired state. This document doesn't explore those in any depth, as existing sign-in and linking guidance is adequate.
+
+## LocalUser versus login
+
+It's important to differentiate between two related but separate concepts that exist within the PlayFab SDK.
+
+A LocalUserCreate call constructs a local user object and returns a PFLocalUserHandle without performing any authentication. It identifies and caches the user by a platform-specific or persisted local ID (for example, wrapping an XUserHandle) so you can reuse the same local context across operations and game instances. This operation is purely local: it doesn't make network requests, obtain an entity token, or create a PlayFab account.
+
+In contrast, a Login call authenticates the local user with PlayFab and establishes an authenticated entity, including tokens and IDs. The Login call performs network requests (such as /Client/LoginWithXbox) and respects flags like createAccount, and once successful, the result is cached so subsequent calls can reuse the authenticated state.
+
+In short, creating a local user sets up local identity and handle management required for PlayFab Game Saves, while signing in is the step that contacts PlayFab to authenticate and enable APIs that require an entity.
+
+## Strategy 1 - required primary identity linking
+
+For the purposes of illustrating this strategy, we're going to discuss an Xbox first-party game shipping on Steam. The game uses Xbox/MSA as its primary linking identity. It requires all players to sign in to their Xbox/MSA prior to any gameplay. It still uses a LocalUserHandle based on the Steam identity, but blocks actual sign-in until the player has created and linked an Xbox identity. On subsequent launches, it can go straight through using the Steam identity, as it's been verified as linked.
+
+### High-level summary
+
+- Player must sign in with the cross-platform identity (Xbox/MSA) before playing.
+- Create a local player from the platform account (Steam) but hold online play until Xbox/MSA sign-in is complete.
+- After Xbox/MSA sign-in, link the platform account to the cross-platform account.
+- Refresh the local platform profile so it's connected to the cross-platform account.
+- Future launches are seamless: the player can go straight to play because the link is established.
+
+### Detailed walkthrough
+
+**Create a Steam local user handle**
+- Call `PFLocalUserCreateHandleWithSteamUser(serviceConfigHandle, customContext, outLocalUserHandle)`.
+- Result: `PFLocalUserHandle`; no authentication yet.
+
+**Attempt to go online**
+- Call `PFLocalUserLoginAsync(localUserHandle, /*createAccount*/ false, async)`.
+- On completion, if `PFLocalUserLoginGetResult` fails with `E_PF_ACCOUNT_NOT_FOUND`, trigger Xbox sign-in to bootstrap the account.
+- If `PFLocalUserLoginGetResult` succeeds, we already have an account in the desired state and it's online. Workflow complete.
+
+> [!NOTE]
+> If your title requires the cross-platform identity to remain linked to the current user (for example, the game requires Xbox sign-in and expects the entity's Xbox link to match the currently signed-in Xbox account), a successful platform login alone isn't sufficient. Call `PFAccountManagementClientGetAccountInfoAsync` after login to verify the cross-platform link matches the current user. If it doesn't, the entity may be tied to a stale cross-platform identity—follow the **Sign in via Xbox** and **Link Steam** steps below to realign.
+
+**Sign in via Xbox**
+- Build `PFAuthenticationLoginWithXUserRequest`:
+  - Set `createAccount=true` to create the PlayFab account if needed.
+  - Provide the `XUserHandle` from your signed-in Xbox user on the PC.
+- Call `PFAuthenticationLoginWithXUserAsync(serviceConfigHandle, request, async)`.
+- Complete with `PFAuthenticationLoginWithXUserGetResultSize(...)` and `PFAuthenticationLoginWithXUserGetResult(...)` to obtain `PFEntityHandle`.
+- Note: Use `PFAuthenticationLoginWithXbox` if the LoginWithXUser variant isn't available. This requires you to extract the XSTS token from the `XUserHandle` yourself.
+
+**Link Steam to the authenticated (Xbox-backed) PlayFab account**
+- Build a client link request with the current Steam auth ticket (from `ISteamUser::GetAuthTicketForWebApi` or equivalent in your integration; confirm exact function name in your code).
+- Call `PFAccountManagementClientLinkSteamAccountAsync(entityHandle, linkRequest, async)`.
+- Note: "LinkSteamAccount" is under Account Management, not Authentication.
+- After success, the player's Steam identity is linked to the Xbox-backed PlayFab account.
+
+**Associate Steam local user with an entity (post-link)**
+- Call `PFLocalUserLoginAsync(steamLocalUserHandle, /*createAccount*/ false, async)` again.
+- `PFLocalUserLoginGetResult` now succeeds; the resulting `PFEntityHandle` is bound to the Steam local user.
+
+**Normal operation going forward**
+- Game Save and other online APIs use the authenticated `PFEntityHandle`.
+- Subsequent game launches can go straight to playing because all the linking is in place.
+
+Notes
+- `PFLocalUserCreateHandleWithSteamUser` doesn't sign in on its own but attempting to call `PFGameSaveFilesAddUserWithUiAsync` results in a sign-in attempt. Ensure you've gone through the account linking flow prior to that call.
+
+### Link-conflict handling
+
+Two distinct conflicts can arise when linking Steam to the Xbox-backed entity. Each requires a different remedy:
+
+| Error | Meaning | Remedy |
+|---|---|---|
+| `E_PF_LINKED_ACCOUNT_ALREADY_CLAIMED` | The current Steam account is linked to a **different** PlayFab entity. | Call `PFAccountManagementClientLinkSteamAccountAsync` again with `forceLink=true` (after consent). This moves the Steam link to the current entity. |
+| `E_PF_ACCOUNT_ALREADY_LINKED` | The current entity already has a **different** Steam account linked. | Call `PFAccountManagementClientUnlinkSteamAccountAsync` to remove the old Steam link first, then call `PFAccountManagementClientLinkSteamAccountAsync` for the new Steam account. `forceLink` doesn't resolve this error. |
+
+**Recommended flow:**
+
+- After Xbox sign-in, call `PFAccountManagementClientGetAccountInfoAsync(xboxEntity, getInfoRequest, async)` to fetch account info and inspect linked identities.
+- If the entity already has a **different Steam account** linked:
+  - Warn the player that proceeding removes the old Steam association from this entity. Obtain consent.
+  - Call `PFAccountManagementClientUnlinkSteamAccountAsync(xboxEntity, unlinkRequest, async)` to remove the existing Steam link.
+  - Then call `PFAccountManagementClientLinkSteamAccountAsync` with the current Steam ticket.
+- If the link call returns `E_PF_LINKED_ACCOUNT_ALREADY_CLAIMED` (the Steam account belongs to another entity):
+  - Warn the player that this Steam account is associated with a different PlayFab account and linking it here removes that association.
+  - Retry with `forceLink=true` after consent.
+
+This preserves player agency and avoids unintentionally overriding links while still providing a clear path to reconcile identities.
+
+### Sample C++ flow (Steam-first gate, Xbox bootstrap, link Steam, sign in with Steam again):
+
+> [!IMPORTANT]
+> This sample uses `static XAsyncBlock` variables to simplify lifetime management. Production code should allocate async blocks dynamically (for example, as part of the context struct) to support concurrent or reentrant calls.
+
+```cpp
+// Assumes: serviceConfigHandle, taskQueue, and a signed-in XUserHandle (xUserHandle) are available
+//
+// NOTE: RETURN_IF_FAILED is used here for brevity. Because XAsyncBlock callbacks return void,
+// production code should replace it with proper error handling (for example, log and return).
+
+// Single context block used by multiple nested callbacks
+struct Strategy1AsyncCtx
+{
+    PFServiceConfigHandle serviceConfig{};
+    XTaskQueueHandle queue{};
+    PFLocalUserHandle steamUser{};
+    XUserHandle xUserHandle{};
+    PFEntityHandle xboxEntity{};
+};
+
+// 1) Create Steam local user
+PFLocalUserHandle steamUser{};
+RETURN_IF_FAILED(PFLocalUserCreateHandleWithSteamUser(serviceConfigHandle, /*customContext*/ nullptr, &steamUser));
+
+// 2) Attempt Steam login with createAccount=false
+XAsyncBlock steamLoginAsync{};
+steamLoginAsync.queue = taskQueue;
+// Provide context for nested callbacks
+// NOTE: Caller is responsible for deleting s1ctx in the terminal callback.
+Strategy1AsyncCtx* s1ctx = new Strategy1AsyncCtx{ serviceConfigHandle, taskQueue, steamUser, xUserHandle };
+steamLoginAsync.context = s1ctx;
+steamLoginAsync.callback = [](XAsyncBlock* async)
+{
+    auto* ctx = static_cast<Strategy1AsyncCtx*>(async->context);
+    // Try to get result-size; failure means login failed
+    size_t bufferSize{};
+    HRESULT hrSize = PFLocalUserLoginGetResultSize(async, &bufferSize);
+    if (FAILED(hrSize))
+    {
+        if (hrSize == E_PF_ACCOUNT_NOT_FOUND)
+        {
+            // 3) Bootstrap via Xbox (provider API), then link Steam
+            PFAuthenticationLoginWithXUserRequest xreq{};
+            xreq.createAccount = true;
+            xreq.user = ctx->xUserHandle; // supply your signed-in XUserHandle
+
+            static XAsyncBlock xboxLoginAsync{}; // ensure lifetime until callback
+            xboxLoginAsync.queue = async->queue;
+            xboxLoginAsync.context = ctx;
+            xboxLoginAsync.callback = [](XAsyncBlock* xAsync)
+            {
+                auto* ctx = static_cast<Strategy1AsyncCtx*>(xAsync->context);
+                // Obtain Xbox login result
+                PFEntityHandle xboxEntity{};
+                size_t xSize{};
+                RETURN_IF_FAILED(PFAuthenticationLoginWithXUserGetResultSize(xAsync, &xSize));
+                std::vector<uint8_t> xbuf(xSize);
+                PFAuthenticationLoginResult const* xres{};
+                RETURN_IF_FAILED(PFAuthenticationLoginWithXUserGetResult(xAsync, &xboxEntity, xbuf.size(), xbuf.data(), &xres, nullptr));
+                ctx->xboxEntity = xboxEntity;
+
+                // Detect existing Steam linkage before linking
+                // Build a minimal GetAccountInfo request
+                // Then call PFAccountManagementClientGetAccountInfoAsync(xboxEntity, &getInfoReq, &getInfoAsync)
+                // and inspect the linked accounts section of the result.
+                //
+                // If the entity already has a DIFFERENT Steam account linked:
+                //   Call PFAccountManagementClientUnlinkSteamAccountAsync(xboxEntity, &unlinkReq, &unlinkAsync)
+                //   to remove the old Steam link, then proceed to link the current Steam account below.
+                //   forceLink does NOT resolve this case (E_PF_ACCOUNT_ALREADY_LINKED error).
+                //
+                // If a DIFFERENT entity has this Steam account claimed:
+                //   The link call below will fail with E_PF_LINKED_ACCOUNT_ALREADY_CLAIMED.
+                //   Retry with forceLink=true after obtaining player consent.
+
+                // Link Steam to Xbox-backed account
+                PFAccountManagementClientLinkSteamAccountRequest linkReq{};
+                linkReq.steamTicket = GetCurrentSteamTicket(); // your helper wrapping ISteamUser::GetAuthTicketForWebApi
+                bool isServiceSpecific = true;
+                linkReq.ticketIsServiceSpecific = &isServiceSpecific;
+                // To resolve E_PF_LINKED_ACCOUNT_ALREADY_CLAIMED after consent:
+                // bool forceLink = true;
+                // linkReq.forceLink = &forceLink;
+
+                static XAsyncBlock linkAsync{};
+                linkAsync.queue = xAsync->queue;
+                linkAsync.context = ctx;
+                linkAsync.callback = [](XAsyncBlock* linkXAsync)
+                {
+                    auto* ctx = static_cast<Strategy1AsyncCtx*>(linkXAsync->context);
+                    RETURN_IF_FAILED(XAsyncGetStatus(linkXAsync, false));
+
+                    // 4) Re-login Steam local user to bind entity handle
+                    static XAsyncBlock steamReloginAsync{};
+                    steamReloginAsync.queue = linkXAsync->queue;
+                    steamReloginAsync.context = ctx;
+                    steamReloginAsync.callback = [](XAsyncBlock* reloginAsync)
+                    {
+                        auto* ctx = static_cast<Strategy1AsyncCtx*>(reloginAsync->context);
+                        PFEntityHandle entity{};
+                        RETURN_IF_FAILED(PFLocalUserLoginGetResult(reloginAsync, &entity, 0, nullptr, nullptr, nullptr));
+                        // Now the Steam local user has an associated entity
+                    };
+
+                    RETURN_IF_FAILED(PFLocalUserLoginAsync(ctx->steamUser, /*createAccount*/ false, &steamReloginAsync));
+                };
+
+                RETURN_IF_FAILED(PFAccountManagementClientLinkSteamAccountAsync(ctx->xboxEntity, &linkReq, &linkAsync));
+            };
+
+            // NOTE: On platforms that don't support LoginWithXUser, replace this with PFAuthenticationLoginWithXboxAsync
+            RETURN_IF_FAILED(PFAuthenticationLoginWithXUserAsync(ctx->serviceConfig, &xreq, &xboxLoginAsync));
+        }
+        // Other failures: handle/log as needed
+        return;
+    }
+
+    // Steam login succeeded: get entity
+    PFEntityHandle entity{};
+    RETURN_IF_FAILED(PFLocalUserLoginGetResult(async, &entity, 0, nullptr, nullptr, nullptr));
+    // Use entity as needed; PFServices/GameSave APIs, etc.
+};
+
+RETURN_IF_FAILED(PFLocalUserLoginAsync(steamUser, /*createAccount*/ false, &steamLoginAsync));
+```
+
+Implementation notes:
+- Use `E_PF_ACCOUNT_NOT_FOUND` to decide the Xbox bootstrap path; handle other errors separately.
+- Keep using the Steam `PFLocalUserHandle`; provider-specific Xbox sign-in returns an `entityHandle` used only to link Steam.
+- After linking, sign in with Steam again to bind the entity to the LocalUser.
+- Ensure you fetch a fresh Steam ticket for linking.
+- Close handles when no longer needed (`PFLocalUserCloseHandle`, `PFEntityCloseHandle`).
+
+## Strategy 2 - optional primary identity linking
+
+For this scenario, the game runs on Steam and uses Xbox/MSA as the primary linking identity. Players can begin playing without immediately signing in to Xbox/MSA. The game encourages linking early with clear benefits and warnings, but initial gameplay isn't blocked.
+
+### High-level summary
+- Create a local player using the platform account (Steam) and try to play online without creating a new account.
+- If online works, continue; if not, offer a choice:
+  - Sign in with the cross-platform identity (Xbox/MSA) to create a unified account, or
+  - Create a platform-only account now and start playing immediately.
+- Encourage early linking to Xbox/MSA by explaining benefits and risks.
+- When the player chooses to link:
+  - If linking succeeds directly, continue playing with a unified account.
+  - If the Xbox/MSA account already has progress elsewhere, pause and ask which progress to keep (reconciliation):
+    - Keep Xbox/MSA progress and attach the current platform account.
+    - Keep current platform progress and defer linking.
+- After linking, refresh the local platform profile so it's connected to the unified account.
+- Future launches are seamless: the player can go straight to play (assuming linking wasn't deferred).
+
+### Detailed walkthrough
+
+**Create a Steam local user handle**
+- Call `PFLocalUserCreateHandleWithSteamUser(serviceConfigHandle, customContext, outLocalUserHandle)`.
+- Result: `PFLocalUserHandle`; no authentication yet.
+
+**Attempt to go online (silent Steam path)**
+- Call `PFLocalUserLoginAsync(localUserHandle, /*createAccount*/ false, async)`.
+- On completion:
+  - If `PFLocalUserLoginGetResult` succeeds, use the resulting `PFEntityHandle` and proceed online.
+    - Check if the Steam-backed account is already linked to Xbox/MSA. Call `PFAccountManagementClientGetAccountInfoAsync(entityHandle, getInfoRequest, async)` and inspect linked identities. If not linked, prompt the player to link Xbox using the flow below (non-blocking), so future cross-progression works seamlessly.
+  - If `PFLocalUserLoginGetResult` fails with `E_PF_ACCOUNT_NOT_FOUND`, the player remains offline until an account is created. Offer two choices:
+    - Create an Xbox-backed PlayFab account now: sign in with Xbox/MSA (for example, `PFAuthenticationLoginWithXUserAsync`).
+    - Sign in with Steam now and start playing: call `PFLocalUserLoginAsync(localUserHandle, /*createAccount*/ true, async)` to create a Steam-backed PlayFab account bound to the local handle; on success, use the resulting `PFEntityHandle` to proceed online immediately.
+  - For other errors, handle gracefully (retry/backoff).
+
+**Prompt to link Xbox (non-blocking)**
+- Present benefits of linking (cross-progression, entitlement portability).
+- Offer Xbox/MSA sign-in.
+
+**Sign in via Xbox (bootstrap or late-link with reconciliation detection)**
+- If the player is initiating Xbox linking later (they already have a Steam-backed `PFEntityHandle` from the current session):
+  - Don't create a new Xbox-backed account.
+  - Attempt to link the Xbox identity directly to the current Steam-backed account by calling the appropriate link API (for example, `PFAccountManagementClientLinkXboxAccountAsync(currentSteamEntity, linkRequest, async)`).
+  - If the link succeeds, the Xbox/MSA identity is now linked; continue normal operation.
+  - If the link fails with a preexisting link/conflict error (Xbox identity already linked elsewhere), enter Account Reconciliation mode. Immediately perform Xbox/MSA sign-in with `createAccount=false` (for example, `PFAuthenticationLoginWithXUserAsync`) to obtain the Xbox-backed `PFEntityHandle`, then fetch profile metadata for context before prompting the player. After consent, proceed to linking decisions.
+- If the player has no existing account for Xbox (bootstrap path):
+  - First attempt Xbox/MSA sign-in with `createAccount=false` using `PFAuthenticationLoginWithXUserAsync` (or `PFAuthenticationLoginWithXboxAsync` where `LoginWithXUser` isn't available).
+    - If sign-in succeeds: the Xbox/MSA account already has a PlayFab account and likely existing progress. Enter Account Reconciliation mode to choose which progress to keep.
+    - If sign-in fails with `E_PF_ACCOUNT_NOT_FOUND`: proceed to create the PlayFab account by signing in again with `createAccount=true`.
+  - Complete with `PFAuthenticationLoginWithXUserGetResultSize(...)` and `PFAuthenticationLoginWithXUserGetResult(...)` to obtain `PFEntityHandle`.
+
+**Link Steam to the authenticated (Xbox-backed) PlayFab account**
+- Applicable when you just created a fresh Xbox-backed PlayFab account (no existing Steam links).
+- If you entered Account Reconciliation earlier, linking decisions and any required `forceLink` actions are handled there; skip this step.
+- Build a client link request with the current Steam auth ticket (from `ISteamUser::GetAuthTicketForWebApi` or your integration).
+- Call `PFAccountManagementClientLinkSteamAccountAsync(entityHandle, linkRequest, async)` with `forceLink=false` (default). This is expected to succeed for a fresh account.
+- If the link fails, treat it as an error condition (unexpected conflict or auth failure). Surface an error to the player and consider prompting them to sign in again before retrying.
+- After success, the player's Steam identity is linked to the Xbox-backed PlayFab account.
+
+**Associate Steam local user with an entity (post-link)**
+- Call `PFLocalUserLoginAsync(steamLocalUserHandle, /*createAccount*/ false, async)` again.
+- `PFLocalUserLoginGetResult` now succeeds; the resulting `PFEntityHandle` is bound to the Steam local user.
+
+**Normal operation going forward**
+- Game Save and other online APIs use the authenticated `PFEntityHandle`.
+- Subsequent game launches will be able to go straight to playing because all the linking is in place.
+
+Notes
+- Don't block initial gameplay with the Xbox/MSA sign-in; prompt early but allow players to defer.
+- `PFLocalUserCreateHandleWithSteamUser` doesn't sign in on its own. Ensure linking flows are completed before calling APIs that trigger sign-in like `PFGameSaveFilesAddUserWithUiAsync`.
+
+### Account reconciliation (existing progress on Xbox/MSA)
+
+When a player signs in with an Xbox/MSA account that already has progress (for example, from console or another platform), you must avoid blindly creating a new account or overriding existing links. Use a cautious, two-phase approach to detect and reconcile.
+
+> [!TIP]
+> **Player-facing wording:** In developer docs we use "reconciliation." For player UI, prefer clearer terms like "Game Profile Selection", "Choose Progress", or "Keep Existing Progress" to reduce confusion and emphasize that the player is selecting one profile to continue with (not merging).
+
+#### Detection phase
+- Reconciliation can be entered via two paths:
+  1) Existing Xbox/MSA account detected: attempt Xbox/MSA sign-in with `createAccount=false`.
+     - If sign-in succeeds, the Xbox/MSA identity already has a PlayFab account and likely existing progress—enter reconciliation.
+     - If sign-in fails with `E_PF_ACCOUNT_NOT_FOUND`, proceed with bootstrap (`createAccount=true`). There's no need to enter reconciliation.
+  2) Late-link conflict detected: when linking Xbox/MSA to the current Steam-backed account, the link fails with a preexisting-link/conflict error (Xbox identity already linked with a different Steam identity).
+     - Immediately perform Xbox/MSA sign-in with `createAccount=false` (for example, `PFAuthenticationLoginWithXUserAsync`) to obtain the Xbox-backed `PFEntityHandle`.
+     - Fetch profile metadata (for example, recent progression, save slots, timestamps) to present context.
+     - Enter reconciliation to decide which progress to keep.
+
+#### Reconciliation phase
+- Recommend the straightforward option: keep Xbox/MSA (primary linking identity) progress and abandon local Steam progress. This preserves the cross-platform anchor and avoids complex merges.
+- Players effectively have three choices (games may choose to only offer 1-2 of these):
+  1) Keep Xbox/MSA progress (recommended): proceed to link the current Steam account to the existing Xbox-backed PlayFab account.
+  2) Keep current Steam progress and cancel linking: continue with the Steam-backed account for now; don't link or override Xbox/MSA data. Offer linking again next time.
+  3) Keep current Steam progress and abandon Xbox progress: switch to the Steam-backed account and intentionally drop Xbox/MSA progress. This path requires explicit game design consideration and shouldn't be attempted lightly, especially if other platform-native identities are already attached to the Xbox account. For this document, we don't cover implementation details for this scenario.
+- Prior to committing:
+  - Call `PFAccountManagementClientGetAccountInfoAsync` for the Xbox entity to inspect existing provider links and verify whether a Steam link already exists.
+  - If the entity has a **different Steam account** linked, warn the player that this existing Steam association is removed from the entity before the new one can be added. This requires calling `PFAccountManagementClientUnlinkSteamAccountAsync` before linking the current Steam account. `forceLink` doesn't resolve this scenario.
+  - If the **current Steam account** is linked to a **different entity**, calling `PFAccountManagementClientLinkSteamAccountAsync` returns `E_PF_LINKED_ACCOUNT_ALREADY_CLAIMED`. Warn that linking moves the Steam identity away from the other entity, then retry with `forceLink=true` after consent.
+
+#### Commit actions (based on player choice)
+- Player chooses Xbox/MSA progress:
+  - Ensure Xbox sign-in entity is obtained (perform `PFAuthenticationLoginWithXUserAsync` with `createAccount=false` if not already done during detection).
+  - If the Xbox entity already has a different Steam account linked, call `PFAccountManagementClientUnlinkSteamAccountAsync` to remove it first.
+  - Link current Steam to Xbox-backed account. If the call returns `E_PF_LINKED_ACCOUNT_ALREADY_CLAIMED` (Steam is on another entity), retry with `forceLink=true` after consent.
+  - Sign in with the Steam local user again (`PFLocalUserLoginAsync(..., /*createAccount*/ false, ...)`) to bind the entity.
+- Player chooses Steam progress:
+  - If no PlayFab account exists for Steam yet, create/bind via `PFLocalUserLoginAsync(..., /*createAccount*/ true, ...)`.
+  - Defer Xbox link; allow gameplay immediately. Offer linking again next time.
+
+#### Notes
+- Always fetch and display enough context to inform the player's decision.
+- Record telemetry for reconciliation outcomes to improve prompts and defaults over time.
+
+### Strategy 2 flow diagram
+
+The following diagram shows the complete decision tree. Every path converges on a single terminal node where the player reaches a playable state.
+
+![Strategy 2 flow diagram showing the complete decision tree from Steam local user creation through sign-in, account linking, and reconciliation paths.](media/strategy2-flow.svg)
+
+## See also
+
+- [PlayFab Game Saves overview](overview.md)
+- [Game Saves quickstart](quickstart.md)
+- [Game Saves conflicts](conflicts.md)
+- [Token expiration and relogin](../../sdks/c/relogin.md)
\ No newline at end of file
diff --git a/playfab-docs/player-progression/game-saves/media/mermaid-learn.json b/playfab-docs/player-progression/game-saves/media/mermaid-learn.json
new file mode 100644
index 000000000..3cda37894
--- /dev/null
+++ b/playfab-docs/player-progression/game-saves/media/mermaid-learn.json
@@ -0,0 +1,17 @@
+{
+  "theme": "base",
+  "themeVariables": {
+    "primaryColor": "#e8f0fe",
+    "primaryTextColor": "#1a1a1a",
+    "primaryBorderColor": "#4a86c8",
+    "lineColor": "#5a6a7a",
+    "secondaryColor": "#f0f4f0",
+    "tertiaryColor": "#fff8e8",
+    "edgeLabelBackground": "#f0f4f8",
+    "fontFamily": "Segoe UI, sans-serif",
+    "fontSize": "14px"
+  },
+  "flowchart": {
+    "padding": 16
+  }
+}
diff --git a/playfab-docs/player-progression/game-saves/media/strategy2-flow.mmd b/playfab-docs/player-progression/game-saves/media/strategy2-flow.mmd
new file mode 100644
index 000000000..8a5442274
--- /dev/null
+++ b/playfab-docs/player-progression/game-saves/media/strategy2-flow.mmd
@@ -0,0 +1,44 @@
+flowchart TD
+    A["Create Steam local user
+    PFLocalUserCreateHandleWithSteamUser"] --> B["Try Steam sign-in
+    createAccount=false"]
+
+    B -->|"&nbsp;&nbsp;Success&nbsp;&nbsp;"| C["Check linked identities
+    GetAccountInfo"]
+    B -->|"&nbsp;&nbsp;E_PF_ACCOUNT_NOT_FOUND&nbsp;&nbsp;"| D{Player choice}
+
+    C -->|"&nbsp;&nbsp;Xbox/MSA linked&nbsp;&nbsp;"| PLAY[Play online]
+    C -->|"&nbsp;&nbsp;Not linked&nbsp;&nbsp;"| E["Prompt to link Xbox/MSA
+    non-blocking"]
+    E -->|"&nbsp;&nbsp;Player agrees&nbsp;&nbsp;"| LATE[BeginLateLink]
+    E -->|"&nbsp;&nbsp;Player defers&nbsp;&nbsp;"| PLAY
+
+    D -->|"&nbsp;&nbsp;Xbox bootstrap&nbsp;&nbsp;"| F["Try Xbox sign-in
+    createAccount=false"]
+    D -->|"&nbsp;&nbsp;Steam-only&nbsp;&nbsp;"| G["Steam sign-in
+    createAccount=true"] --> PLAY
+
+    F -->|"&nbsp;&nbsp;E_PF_ACCOUNT_NOT_FOUND&nbsp;&nbsp;"| H["Create Xbox account
+    createAccount=true"]
+    F -->|"&nbsp;&nbsp;Existing account&nbsp;&nbsp;"| LATE
+
+    H --> I[Link Steam to Xbox account] --> J[Rebind Steam local user] --> PLAY
+
+    LATE --> K[Try link Xbox to Steam account]
+    K -->|"&nbsp;&nbsp;Success&nbsp;&nbsp;"| PLAY
+    K -->|"&nbsp;&nbsp;Conflict&nbsp;&nbsp;"| L[Xbox sign-in to get entity]
+    L --> M["RunReconciliation
+    fetch account info + show UI"]
+
+    M -->|"&nbsp;&nbsp;Keep Xbox progress&nbsp;&nbsp;"| N0{Xbox entity has
+    different Steam?}
+    N0 -->|"&nbsp;&nbsp;Yes&nbsp;&nbsp;"| N1["Unlink old Steam
+    UnlinkSteamAccount"]
+    N1 --> N2["Link current Steam
+    to Xbox account"]
+    N0 -->|"&nbsp;&nbsp;No&nbsp;&nbsp;"| N2
+    N2 -->|"&nbsp;&nbsp;LinkedAccountAlreadyClaimed&nbsp;&nbsp;"| N3["Retry with
+    forceLink=true"]
+    N3 --> O
+    N2 -->|"&nbsp;&nbsp;Success&nbsp;&nbsp;"| O[Rebind Steam local user] --> PLAY
+    M -->|"&nbsp;&nbsp;Keep Steam progress&nbsp;&nbsp;"| P[Defer Xbox link] --> PLAY
\ No newline at end of file
diff --git a/playfab-docs/player-progression/game-saves/media/strategy2-flow.svg b/playfab-docs/player-progression/game-saves/media/strategy2-flow.svg
new file mode 100644
index 000000000..a36ea3a77
--- /dev/null
+++ b/playfab-docs/player-progression/game-saves/media/strategy2-flow.svg
@@ -0,0 +1 @@
+<svg id="my-svg" width="100%" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" class="flowchart" style="max-width: 1423.78px; background-color: transparent;" viewBox="0 0 1423.77734375 1967.859375" role="graphics-document document" aria-roledescription="flowchart-v2"><style>#my-svg{font-family:Segoe UI,sans-serif;font-size:14px;fill:#1a1a1a;}@keyframes edge-animation-frame{from{stroke-dashoffset:0;}}@keyframes dash{to{stroke-dashoffset:0;}}#my-svg .edge-animation-slow{stroke-dasharray:9,5!important;stroke-dashoffset:900;animation:dash 50s linear infinite;stroke-linecap:round;}#my-svg .edge-animation-fast{stroke-dasharray:9,5!important;stroke-dashoffset:900;animation:dash 20s linear infinite;stroke-linecap:round;}#my-svg .error-icon{fill:#fff8e8;}#my-svg .error-text{fill:#000717;stroke:#000717;}#my-svg .edge-thickness-normal{stroke-width:1px;}#my-svg .edge-thickness-thick{stroke-width:3.5px;}#my-svg .edge-pattern-solid{stroke-dasharray:0;}#my-svg .edge-thickness-invisible{stroke-width:0;fill:none;}#my-svg .edge-pattern-dashed{stroke-dasharray:3;}#my-svg .edge-pattern-dotted{stroke-dasharray:2;}#my-svg .marker{fill:#5a6a7a;stroke:#5a6a7a;}#my-svg .marker.cross{stroke:#5a6a7a;}#my-svg svg{font-family:Segoe UI,sans-serif;font-size:14px;}#my-svg p{margin:0;}#my-svg .label{font-family:Segoe UI,sans-serif;color:#1a1a1a;}#my-svg .cluster-label text{fill:#000717;}#my-svg .cluster-label span{color:#000717;}#my-svg .cluster-label span p{background-color:transparent;}#my-svg .label text,#my-svg span{fill:#1a1a1a;color:#1a1a1a;}#my-svg .node rect,#my-svg .node circle,#my-svg .node ellipse,#my-svg .node polygon,#my-svg .node path{fill:#e8f0fe;stroke:#4a86c8;stroke-width:1px;}#my-svg .rough-node .label text,#my-svg .node .label text,#my-svg .image-shape .label,#my-svg .icon-shape .label{text-anchor:middle;}#my-svg .node .katex path{fill:#000;stroke:#000;stroke-width:1px;}#my-svg .rough-node .label,#my-svg .node .label,#my-svg .image-shape .label,#my-svg .icon-shape .label{text-align:center;}#my-svg .node.clickable{cursor:pointer;}#my-svg .root .anchor path{fill:#5a6a7a!important;stroke-width:0;stroke:#5a6a7a;}#my-svg .arrowheadPath{fill:#0b0b0b;}#my-svg .edgePath .path{stroke:#5a6a7a;stroke-width:2.0px;}#my-svg .flowchart-link{stroke:#5a6a7a;fill:none;}#my-svg .edgeLabel{background-color:#f0f4f8;text-align:center;}#my-svg .edgeLabel p{background-color:#f0f4f8;}#my-svg .edgeLabel rect{opacity:0.5;background-color:#f0f4f8;fill:#f0f4f8;}#my-svg .labelBkg{background-color:rgba(240, 244, 248, 0.5);}#my-svg .cluster rect{fill:#fff8e8;stroke:hsl(41.7391304348, 60%, 85.4901960784%);stroke-width:1px;}#my-svg .cluster text{fill:#000717;}#my-svg .cluster span{color:#000717;}#my-svg div.mermaidTooltip{position:absolute;text-align:center;max-width:200px;padding:2px;font-family:Segoe UI,sans-serif;font-size:12px;background:#fff8e8;border:1px solid hsl(41.7391304348, 60%, 85.4901960784%);border-radius:2px;pointer-events:none;z-index:100;}#my-svg .flowchartTitleText{text-anchor:middle;font-size:18px;fill:#1a1a1a;}#my-svg rect.text{fill:none;stroke-width:0;}#my-svg .icon-shape,#my-svg .image-shape{background-color:#f0f4f8;text-align:center;}#my-svg .icon-shape p,#my-svg .image-shape p{background-color:#f0f4f8;padding:2px;}#my-svg .icon-shape rect,#my-svg .image-shape rect{opacity:0.5;background-color:#f0f4f8;fill:#f0f4f8;}#my-svg .label-icon{display:inline-block;height:1em;overflow:visible;vertical-align:-0.125em;}#my-svg .node .label-icon path{fill:currentColor;stroke:revert;stroke-width:revert;}#my-svg :root{--mermaid-font-family:"trebuchet ms",verdana,arial,sans-serif;}</style><g><marker id="my-svg_flowchart-v2-pointEnd" class="marker flowchart-v2" viewBox="0 0 10 10" refX="5" refY="5" markerUnits="userSpaceOnUse" markerWidth="8" markerHeight="8" orient="auto"><path d="M 0 0 L 10 5 L 0 10 z" class="arrowMarkerPath" style="stroke-width: 1; stroke-dasharray: 1, 0;"/></marker><marker id="my-svg_flowchart-v2-pointStart" class="marker flowchart-v2" viewBox="0 0 10 10" refX="4.5" refY="5" markerUnits="userSpaceOnUse" markerWidth="8" markerHeight="8" orient="auto"><path d="M 0 5 L 10 10 L 10 0 z" class="arrowMarkerPath" style="stroke-width: 1; stroke-dasharray: 1, 0;"/></marker><marker id="my-svg_flowchart-v2-circleEnd" class="marker flowchart-v2" viewBox="0 0 10 10" refX="11" refY="5" markerUnits="userSpaceOnUse" markerWidth="11" markerHeight="11" orient="auto"><circle cx="5" cy="5" r="5" class="arrowMarkerPath" style="stroke-width: 1; stroke-dasharray: 1, 0;"/></marker><marker id="my-svg_flowchart-v2-circleStart" class="marker flowchart-v2" viewBox="0 0 10 10" refX="-1" refY="5" markerUnits="userSpaceOnUse" markerWidth="11" markerHeight="11" orient="auto"><circle cx="5" cy="5" r="5" class="arrowMarkerPath" style="stroke-width: 1; stroke-dasharray: 1, 0;"/></marker><marker id="my-svg_flowchart-v2-crossEnd" class="marker cross flowchart-v2" viewBox="0 0 11 11" refX="12" refY="5.2" markerUnits="userSpaceOnUse" markerWidth="11" markerHeight="11" orient="auto"><path d="M 1,1 l 9,9 M 10,1 l -9,9" class="arrowMarkerPath" style="stroke-width: 2; stroke-dasharray: 1, 0;"/></marker><marker id="my-svg_flowchart-v2-crossStart" class="marker cross flowchart-v2" viewBox="0 0 11 11" refX="-1" refY="5.2" markerUnits="userSpaceOnUse" markerWidth="11" markerHeight="11" orient="auto"><path d="M 1,1 l 9,9 M 10,1 l -9,9" class="arrowMarkerPath" style="stroke-width: 2; stroke-dasharray: 1, 0;"/></marker><g class="root"><g class="clusters"/><g class="edgePaths"><path d="M690.313,82L690.313,86.167C690.313,90.333,690.313,98.667,690.313,106.333C690.313,114,690.313,121,690.313,124.5L690.313,128" id="L_A_B_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_A_B_0" data-points="W3sieCI6NjkwLjMxMjUsInkiOjgyfSx7IngiOjY5MC4zMTI1LCJ5IjoxMDd9LHsieCI6NjkwLjMxMjUsInkiOjEzMn1d" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M595.141,181.582L519.605,191.569C444.069,201.555,292.997,221.527,217.462,241.759C141.926,261.99,141.926,282.479,141.926,292.724L141.926,302.969" id="L_B_C_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_B_C_0" data-points="W3sieCI6NTk1LjE0MDYyNSwieSI6MTgxLjU4MjI5MDM4MzAxMjY2fSx7IngiOjE0MS45MjU3ODEyNSwieSI6MjQxLjV9LHsieCI6MTQxLjkyNTc4MTI1LCJ5IjozMDYuOTY4NzV9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M785.484,182.601L854.176,192.417C922.867,202.234,1060.25,221.867,1128.941,236.933C1197.633,252,1197.633,262.5,1197.633,267.75L1197.633,273" id="L_B_D_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_B_D_0" data-points="W3sieCI6Nzg1LjQ4NDM3NSwieSI6MTgyLjYwMDc5NzY5NjIyODY1fSx7IngiOjExOTcuNjMyODEyNSwieSI6MjQxLjV9LHsieCI6MTE5Ny42MzI4MTI1LCJ5IjoyNzd9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M115.596,380.969L107.831,391.88C100.067,402.792,84.537,424.615,76.773,447.609C69.008,470.604,69.008,494.771,69.008,518.938C69.008,543.104,69.008,567.271,69.008,589.688C69.008,612.104,69.008,632.771,69.008,651.688C69.008,670.604,69.008,687.771,69.008,704.938C69.008,722.104,69.008,739.271,69.008,758.188C69.008,777.104,69.008,797.771,69.008,818.438C69.008,839.104,69.008,859.771,69.008,880.438C69.008,901.104,69.008,921.771,69.008,944.188C69.008,966.604,69.008,990.771,69.008,1014.938C69.008,1039.104,69.008,1063.271,69.008,1095.848C69.008,1128.424,69.008,1169.411,69.008,1210.398C69.008,1251.385,69.008,1292.372,69.008,1324.949C69.008,1357.526,69.008,1381.693,69.008,1405.859C69.008,1430.026,69.008,1454.193,69.008,1478.359C69.008,1502.526,69.008,1526.693,69.008,1550.859C69.008,1575.026,69.008,1599.193,69.008,1623.359C69.008,1647.526,69.008,1671.693,69.008,1694.109C69.008,1716.526,69.008,1737.193,69.008,1757.859C69.008,1778.526,69.008,1799.193,69.008,1819.859C69.008,1840.526,69.008,1861.193,145.971,1878.986C222.935,1896.779,376.861,1911.699,453.825,1919.159L530.788,1926.619" id="L_C_PLAY_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_C_PLAY_0" data-points="W3sieCI6MTE1LjU5NjE0NTY5MDM3ODE3LCJ5IjozODAuOTY4NzV9LHsieCI6NjkuMDA3ODEyNSwieSI6NDQ2LjQzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6NTE4LjkzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6NTkxLjQzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6NjUzLjQzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6NzA0LjkzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6NzU2LjQzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6ODE4LjQzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6ODgwLjQzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6OTQyLjQzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6MTAxNC45Mzc1fSx7IngiOjY5LjAwNzgxMjUsInkiOjEwODcuNDM3NX0seyJ4Ijo2OS4wMDc4MTI1LCJ5IjoxMjEwLjM5ODQzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6MTMzMy4zNTkzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6MTQwNS44NTkzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6MTQ3OC4zNTkzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6MTU1MC44NTkzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6MTYyMy4zNTkzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6MTY5NS44NTkzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6MTc1Ny44NTkzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6MTgxOS44NTkzNzV9LHsieCI6NjkuMDA3ODEyNSwieSI6MTg4MS44NTkzNzV9LHsieCI6NTM0Ljc2OTUzMTI1LCJ5IjoxOTI3LjAwNDU1NjkyMzExMzh9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M168.255,380.969L176.02,391.88C183.785,402.792,199.314,424.615,207.079,440.776C214.844,456.938,214.844,467.438,214.844,472.688L214.844,477.938" id="L_C_E_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_C_E_0" data-points="W3sieCI6MTY4LjI1NTQxNjgwOTYyMTgzLCJ5IjozODAuOTY4NzV9LHsieCI6MjE0Ljg0Mzc1LCJ5Ijo0NDYuNDM3NX0seyJ4IjoyMTQuODQzNzUsInkiOjQ4MS45Mzc1fV0=" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M195.15,555.938L192,561.854C188.851,567.771,182.552,579.604,242.983,594.086C303.414,608.568,430.575,625.699,494.155,634.265L557.735,642.83" id="L_E_LATE_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_E_LATE_0" data-points="W3sieCI6MTk1LjE0OTYyMjg0NDgyNzU4LCJ5Ijo1NTUuOTM3NX0seyJ4IjoxNzYuMjUzOTA2MjUsInkiOjU5MS40Mzc1fSx7IngiOjU2MS42OTkyMTg3NSwieSI6NjQzLjM2NDEzMTM1NzM3MDl9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M232.363,555.938L235.164,561.854C237.966,567.771,243.569,579.604,246.37,595.854C249.172,612.104,249.172,632.771,249.172,651.688C249.172,670.604,249.172,687.771,249.172,704.938C249.172,722.104,249.172,739.271,249.172,758.188C249.172,777.104,249.172,797.771,249.172,818.438C249.172,839.104,249.172,859.771,249.172,880.438C249.172,901.104,249.172,921.771,249.172,944.188C249.172,966.604,249.172,990.771,249.172,1014.938C249.172,1039.104,249.172,1063.271,249.172,1095.848C249.172,1128.424,249.172,1169.411,249.172,1210.398C249.172,1251.385,249.172,1292.372,249.172,1324.949C249.172,1357.526,249.172,1381.693,249.172,1405.859C249.172,1430.026,249.172,1454.193,249.172,1478.359C249.172,1502.526,249.172,1526.693,249.172,1550.859C249.172,1575.026,249.172,1599.193,249.172,1623.359C249.172,1647.526,249.172,1671.693,249.172,1694.109C249.172,1716.526,249.172,1737.193,249.172,1757.859C249.172,1778.526,249.172,1799.193,249.172,1819.859C249.172,1840.526,249.172,1861.193,296.112,1878.41C343.052,1895.628,436.932,1909.396,483.872,1916.28L530.812,1923.164" id="L_E_PLAY_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_E_PLAY_0" data-points="W3sieCI6MjMyLjM2MjkzMTAzNDQ4Mjc2LCJ5Ijo1NTUuOTM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5Ijo1OTEuNDM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5Ijo2NTMuNDM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5Ijo3MDQuOTM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5Ijo3NTYuNDM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5Ijo4MTguNDM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5Ijo4ODAuNDM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5Ijo5NDIuNDM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5IjoxMDE0LjkzNzV9LHsieCI6MjQ5LjE3MTg3NSwieSI6MTA4Ny40Mzc1fSx7IngiOjI0OS4xNzE4NzUsInkiOjEyMTAuMzk4NDM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5IjoxMzMzLjM1OTM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5IjoxNDA1Ljg1OTM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5IjoxNDc4LjM1OTM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5IjoxNTUwLjg1OTM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5IjoxNjIzLjM1OTM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5IjoxNjk1Ljg1OTM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5IjoxNzU3Ljg1OTM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5IjoxODE5Ljg1OTM3NX0seyJ4IjoyNDkuMTcxODc1LCJ5IjoxODgxLjg1OTM3NX0seyJ4Ijo1MzQuNzY5NTMxMjUsInkiOjE5MjMuNzQ0MTkzMTgwODA2OX1d" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M1167.108,380.412L1157.89,391.416C1148.673,402.421,1130.239,424.429,1121.022,440.683C1111.805,456.938,1111.805,467.438,1111.805,472.688L1111.805,477.938" id="L_D_F_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_D_F_0" data-points="W3sieCI6MTE2Ny4xMDc1OTkzNDM0MTU2LCJ5IjozODAuNDEyMjg2ODQzNDE1NX0seyJ4IjoxMTExLjgwNDY4NzUsInkiOjQ0Ni40Mzc1fSx7IngiOjExMTEuODA0Njg3NSwieSI6NDgxLjkzNzV9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M1234.384,374.187L1249.029,386.229C1263.674,398.27,1292.964,422.354,1307.609,446.479C1322.254,470.604,1322.254,494.771,1322.254,518.938C1322.254,543.104,1322.254,567.271,1322.254,589.688C1322.254,612.104,1322.254,632.771,1322.254,651.688C1322.254,670.604,1322.254,687.771,1322.254,704.938C1322.254,722.104,1322.254,739.271,1322.254,758.188C1322.254,777.104,1322.254,797.771,1322.254,818.438C1322.254,839.104,1322.254,859.771,1322.254,880.438C1322.254,901.104,1322.254,921.771,1322.254,944.188C1322.254,966.604,1322.254,990.771,1322.254,1014.938C1322.254,1039.104,1322.254,1063.271,1322.254,1095.848C1322.254,1128.424,1322.254,1169.411,1322.254,1210.398C1322.254,1251.385,1322.254,1292.372,1322.254,1324.949C1322.254,1357.526,1322.254,1381.693,1322.254,1405.859C1322.254,1430.026,1322.254,1454.193,1322.254,1478.359C1322.254,1502.526,1322.254,1526.693,1322.254,1550.859C1322.254,1575.026,1322.254,1599.193,1322.254,1623.359C1322.254,1647.526,1322.254,1671.693,1322.254,1694.109C1322.254,1716.526,1322.254,1737.193,1322.254,1751.026C1322.254,1764.859,1322.254,1771.859,1322.254,1775.359L1322.254,1778.859" id="L_D_G_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_D_G_0" data-points="W3sieCI6MTIzNC4zODM1NDgzOTQ5LCJ5IjozNzQuMTg2NzY0MTA1MTAwMn0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5Ijo0NDYuNDM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5Ijo1MTguOTM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5Ijo1OTEuNDM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5Ijo2NTMuNDM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5Ijo3MDQuOTM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5Ijo3NTYuNDM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5Ijo4MTguNDM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5Ijo4ODAuNDM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5Ijo5NDIuNDM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5IjoxMDE0LjkzNzV9LHsieCI6MTMyMi4yNTM5MDYyNSwieSI6MTA4Ny40Mzc1fSx7IngiOjEzMjIuMjUzOTA2MjUsInkiOjEyMTAuMzk4NDM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5IjoxMzMzLjM1OTM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5IjoxNDA1Ljg1OTM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5IjoxNDc4LjM1OTM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5IjoxNTUwLjg1OTM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5IjoxNjIzLjM1OTM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5IjoxNjk1Ljg1OTM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5IjoxNzU3Ljg1OTM3NX0seyJ4IjoxMzIyLjI1MzkwNjI1LCJ5IjoxNzgyLjg1OTM3NX1d" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M1322.254,1856.859L1322.254,1861.026C1322.254,1865.193,1322.254,1873.526,1213.526,1885.449C1104.797,1897.372,887.341,1912.885,778.613,1920.641L669.884,1928.398" id="L_G_PLAY_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_G_PLAY_0" data-points="W3sieCI6MTMyMi4yNTM5MDYyNSwieSI6MTg1Ni44NTkzNzV9LHsieCI6MTMyMi4yNTM5MDYyNSwieSI6MTg4MS44NTkzNzV9LHsieCI6NjY1Ljg5NDUzMTI1LCJ5IjoxOTI4LjY4MjMxOTM5NzU1fV0=" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M1092.007,555.938L1088.841,561.854C1085.675,567.771,1079.343,579.604,1076.178,595.854C1073.012,612.104,1073.012,632.771,1073.012,651.688C1073.012,670.604,1073.012,687.771,1073.012,704.938C1073.012,722.104,1073.012,739.271,1073.012,758.188C1073.012,777.104,1073.012,797.771,1073.012,818.438C1073.012,839.104,1073.012,859.771,1073.012,880.438C1073.012,901.104,1073.012,921.771,1073.012,944.188C1073.012,966.604,1073.012,990.771,1073.012,1014.938C1073.012,1039.104,1073.012,1063.271,1073.012,1095.848C1073.012,1128.424,1073.012,1169.411,1073.012,1210.398C1073.012,1251.385,1073.012,1292.372,1073.012,1324.949C1073.012,1357.526,1073.012,1381.693,1073.012,1405.859C1073.012,1430.026,1073.012,1454.193,1073.012,1471.526C1073.012,1488.859,1073.012,1499.359,1073.012,1504.609L1073.012,1509.859" id="L_F_H_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_F_H_0" data-points="W3sieCI6MTA5Mi4wMDY4OTY1NTE3MjQxLCJ5Ijo1NTUuOTM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5Ijo1OTEuNDM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5Ijo2NTMuNDM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5Ijo3MDQuOTM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5Ijo3NTYuNDM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5Ijo4MTguNDM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5Ijo4ODAuNDM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5Ijo5NDIuNDM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5IjoxMDE0LjkzNzV9LHsieCI6MTA3My4wMTE3MTg3NSwieSI6MTA4Ny40Mzc1fSx7IngiOjEwNzMuMDExNzE4NzUsInkiOjEyMTAuMzk4NDM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5IjoxMzMzLjM1OTM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5IjoxNDA1Ljg1OTM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5IjoxNDc4LjM1OTM3NX0seyJ4IjoxMDczLjAxMTcxODc1LCJ5IjoxNTEzLjg1OTM3NX1d" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M1155.607,555.938L1162.611,561.854C1169.615,567.771,1183.624,579.604,1110.227,594.404C1036.829,609.204,876.026,626.97,795.624,635.854L715.222,644.737" id="L_F_LATE_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_F_LATE_0" data-points="W3sieCI6MTE1NS42MDY2MjcxNTUxNzI0LCJ5Ijo1NTUuOTM3NX0seyJ4IjoxMTk3LjYzMjgxMjUsInkiOjU5MS40Mzc1fSx7IngiOjcxMS4yNDYwOTM3NSwieSI6NjQ1LjE3NjEyNzQyNTA0NzJ9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M1073.012,1587.859L1073.012,1593.776C1073.012,1599.693,1073.012,1611.526,1073.012,1624.443C1073.012,1637.359,1073.012,1651.359,1073.012,1658.359L1073.012,1665.359" id="L_H_I_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_H_I_0" data-points="W3sieCI6MTA3My4wMTE3MTg3NSwieSI6MTU4Ny44NTkzNzV9LHsieCI6MTA3My4wMTE3MTg3NSwieSI6MTYyMy4zNTkzNzV9LHsieCI6MTA3My4wMTE3MTg3NSwieSI6MTY2OS4zNTkzNzV9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M1073.012,1722.359L1073.012,1728.276C1073.012,1734.193,1073.012,1746.026,1073.012,1757.193C1073.012,1768.359,1073.012,1778.859,1073.012,1784.109L1073.012,1789.359" id="L_I_J_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_I_J_0" data-points="W3sieCI6MTA3My4wMTE3MTg3NSwieSI6MTcyMi4zNTkzNzV9LHsieCI6MTA3My4wMTE3MTg3NSwieSI6MTc1Ny44NTkzNzV9LHsieCI6MTA3My4wMTE3MTg3NSwieSI6MTc5My4zNTkzNzV9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M1073.012,1846.359L1073.012,1852.276C1073.012,1858.193,1073.012,1870.026,1005.822,1883.263C938.631,1896.501,804.251,1911.142,737.061,1918.462L669.871,1925.783" id="L_J_PLAY_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_J_PLAY_0" data-points="W3sieCI6MTA3My4wMTE3MTg3NSwieSI6MTg0Ni4zNTkzNzV9LHsieCI6MTA3My4wMTE3MTg3NSwieSI6MTg4MS44NTkzNzV9LHsieCI6NjY1Ljg5NDUzMTI1LCJ5IjoxOTI2LjIxNjEyNTkwNDkxMzd9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M636.473,679.938L636.473,684.104C636.473,688.271,636.473,696.604,636.473,704.271C636.473,711.938,636.473,718.938,636.473,722.438L636.473,725.938" id="L_LATE_K_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_LATE_K_0" data-points="W3sieCI6NjM2LjQ3MjY1NjI1LCJ5Ijo2NzkuOTM3NX0seyJ4Ijo2MzYuNDcyNjU2MjUsInkiOjcwNC45Mzc1fSx7IngiOjYzNi40NzI2NTYyNSwieSI6NzI5LjkzNzV9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M519.907,782.938L493.882,788.854C467.856,794.771,415.805,806.604,389.779,822.854C363.754,839.104,363.754,859.771,363.754,880.438C363.754,901.104,363.754,921.771,363.754,944.188C363.754,966.604,363.754,990.771,363.754,1014.938C363.754,1039.104,363.754,1063.271,363.754,1095.848C363.754,1128.424,363.754,1169.411,363.754,1210.398C363.754,1251.385,363.754,1292.372,363.754,1324.949C363.754,1357.526,363.754,1381.693,363.754,1405.859C363.754,1430.026,363.754,1454.193,363.754,1478.359C363.754,1502.526,363.754,1526.693,363.754,1550.859C363.754,1575.026,363.754,1599.193,363.754,1623.359C363.754,1647.526,363.754,1671.693,363.754,1694.109C363.754,1716.526,363.754,1737.193,363.754,1757.859C363.754,1778.526,363.754,1799.193,363.754,1819.859C363.754,1840.526,363.754,1861.193,391.605,1877.589C419.456,1893.985,475.159,1906.111,503.01,1912.174L530.861,1918.236" id="L_K_PLAY_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_K_PLAY_0" data-points="W3sieCI6NTE5LjkwNzM4NDA3MjU4MDYsInkiOjc4Mi45Mzc1fSx7IngiOjM2My43NTM5MDYyNSwieSI6ODE4LjQzNzV9LHsieCI6MzYzLjc1MzkwNjI1LCJ5Ijo4ODAuNDM3NX0seyJ4IjozNjMuNzUzOTA2MjUsInkiOjk0Mi40Mzc1fSx7IngiOjM2My43NTM5MDYyNSwieSI6MTAxNC45Mzc1fSx7IngiOjM2My43NTM5MDYyNSwieSI6MTA4Ny40Mzc1fSx7IngiOjM2My43NTM5MDYyNSwieSI6MTIxMC4zOTg0Mzc1fSx7IngiOjM2My43NTM5MDYyNSwieSI6MTMzMy4zNTkzNzV9LHsieCI6MzYzLjc1MzkwNjI1LCJ5IjoxNDA1Ljg1OTM3NX0seyJ4IjozNjMuNzUzOTA2MjUsInkiOjE0NzguMzU5Mzc1fSx7IngiOjM2My43NTM5MDYyNSwieSI6MTU1MC44NTkzNzV9LHsieCI6MzYzLjc1MzkwNjI1LCJ5IjoxNjIzLjM1OTM3NX0seyJ4IjozNjMuNzUzOTA2MjUsInkiOjE2OTUuODU5Mzc1fSx7IngiOjM2My43NTM5MDYyNSwieSI6MTc1Ny44NTkzNzV9LHsieCI6MzYzLjc1MzkwNjI1LCJ5IjoxODE5Ljg1OTM3NX0seyJ4IjozNjMuNzUzOTA2MjUsInkiOjE4ODEuODU5Mzc1fSx7IngiOjUzNC43Njk1MzEyNSwieSI6MTkxOS4wODcyNjYxNTY0NjI2fV0=" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M671.205,782.938L678.96,788.854C686.715,794.771,702.225,806.604,709.98,817.771C717.734,828.938,717.734,839.438,717.734,844.688L717.734,849.938" id="L_K_L_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_K_L_0" data-points="W3sieCI6NjcxLjIwNTQ4NzY1MTIwOTYsInkiOjc4Mi45Mzc1fSx7IngiOjcxNy43MzQzNzUsInkiOjgxOC40Mzc1fSx7IngiOjcxNy43MzQzNzUsInkiOjg1My45Mzc1fV0=" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M717.734,906.938L717.734,912.854C717.734,918.771,717.734,930.604,717.734,941.771C717.734,952.938,717.734,963.438,717.734,968.688L717.734,973.938" id="L_L_M_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_L_M_0" data-points="W3sieCI6NzE3LjczNDM3NSwieSI6OTA2LjkzNzV9LHsieCI6NzE3LjczNDM3NSwieSI6OTQyLjQzNzV9LHsieCI6NzE3LjczNDM3NSwieSI6OTc3LjkzNzV9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M657.819,1051.938L648.238,1057.854C638.656,1063.771,619.494,1075.604,609.913,1086.771C600.332,1097.938,600.332,1108.438,600.332,1113.688L600.332,1118.938" id="L_M_N0_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_M_N0_0" data-points="W3sieCI6NjU3LjgxODY5NjEyMDY4OTcsInkiOjEwNTEuOTM3NX0seyJ4Ijo2MDAuMzMyMDMxMjUsInkiOjEwODcuNDM3NX0seyJ4Ijo2MDAuMzMyMDMxMjUsInkiOjExMjIuOTM3NX1d" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M567.457,1264.984L560.594,1276.38C553.73,1287.776,540.004,1310.568,533.141,1327.214C526.277,1343.859,526.277,1354.359,526.277,1359.609L526.277,1364.859" id="L_N0_N1_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_N0_N1_0" data-points="W3sieCI6NTY3LjQ1NzAxMjM1MjI4ODEsInkiOjEyNjQuOTg0MzU2MTAyMjg4fSx7IngiOjUyNi4yNzczNDM3NSwieSI6MTMzMy4zNTkzNzV9LHsieCI6NTI2LjI3NzM0Mzc1LCJ5IjoxMzY4Ljg1OTM3NX1d" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M526.277,1442.859L526.277,1448.776C526.277,1454.693,526.277,1466.526,531.845,1477.893C537.412,1489.26,548.546,1500.161,554.113,1505.611L559.68,1511.061" id="L_N1_N2_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_N1_N2_0" data-points="W3sieCI6NTI2LjI3NzM0Mzc1LCJ5IjoxNDQyLjg1OTM3NX0seyJ4Ijo1MjYuMjc3MzQzNzUsInkiOjE0NzguMzU5Mzc1fSx7IngiOjU2Mi41Mzg2MDQ1MjU4NjIxLCJ5IjoxNTEzLjg1OTM3NX1d" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M633.207,1264.984L640.07,1276.38C646.934,1287.776,660.66,1310.568,667.523,1334.047C674.387,1357.526,674.387,1381.693,674.387,1405.859C674.387,1430.026,674.387,1454.193,668.82,1471.726C663.252,1489.26,652.118,1500.161,646.551,1505.611L640.984,1511.061" id="L_N0_N2_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_N0_N2_0" data-points="W3sieCI6NjMzLjIwNzA1MDE0NzcxMTksInkiOjEyNjQuOTg0MzU2MTAyMjg4fSx7IngiOjY3NC4zODY3MTg3NSwieSI6MTMzMy4zNTkzNzV9LHsieCI6Njc0LjM4NjcxODc1LCJ5IjoxNDA1Ljg1OTM3NX0seyJ4Ijo2NzQuMzg2NzE4NzUsInkiOjE0NzguMzU5Mzc1fSx7IngiOjYzOC4xMjU0NTc5NzQxMzc5LCJ5IjoxNTEzLjg1OTM3NX1d" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M552.132,1587.859L544.425,1593.776C536.717,1599.693,521.302,1611.526,513.594,1622.693C505.887,1633.859,505.887,1644.359,505.887,1649.609L505.887,1654.859" id="L_N2_N3_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_N2_N3_0" data-points="W3sieCI6NTUyLjEzMjM1NDUyNTg2MjEsInkiOjE1ODcuODU5Mzc1fSx7IngiOjUwNS44ODY3MTg3NSwieSI6MTYyMy4zNTkzNzV9LHsieCI6NTA1Ljg4NjcxODc1LCJ5IjoxNjU4Ljg1OTM3NX1d" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M505.887,1732.859L505.887,1737.026C505.887,1741.193,505.887,1749.526,514.342,1759.244C522.798,1768.961,539.709,1780.063,548.165,1785.613L556.62,1791.164" id="L_N3_O_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_N3_O_0" data-points="W3sieCI6NTA1Ljg4NjcxODc1LCJ5IjoxNzMyLjg1OTM3NX0seyJ4Ijo1MDUuODg2NzE4NzUsInkiOjE3NTcuODU5Mzc1fSx7IngiOjU1OS45NjQyNzY3MTM3MDk2LCJ5IjoxNzkzLjM1OTM3NX1d" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M648.693,1587.859L656.427,1593.776C664.16,1599.693,679.627,1611.526,687.36,1629.526C695.094,1647.526,695.094,1671.693,695.094,1694.109C695.094,1716.526,695.094,1737.193,686.608,1753.078C678.123,1768.963,661.153,1780.066,652.667,1785.618L644.182,1791.169" id="L_N2_O_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_N2_O_0" data-points="W3sieCI6NjQ4LjY5MzE4NDI2NzI0MTMsInkiOjE1ODcuODU5Mzc1fSx7IngiOjY5NS4wOTM3NSwieSI6MTYyMy4zNTkzNzV9LHsieCI6Njk1LjA5Mzc1LCJ5IjoxNjk1Ljg1OTM3NX0seyJ4Ijo2OTUuMDkzNzUsInkiOjE3NTcuODU5Mzc1fSx7IngiOjY0MC44MzUwMjM5NDE1MzIyLCJ5IjoxNzkzLjM1OTM3NX1d" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M600.332,1846.359L600.332,1852.276C600.332,1858.193,600.332,1870.026,600.332,1879.443C600.332,1888.859,600.332,1895.859,600.332,1899.359L600.332,1902.859" id="L_O_PLAY_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_O_PLAY_0" data-points="W3sieCI6NjAwLjMzMjAzMTI1LCJ5IjoxODQ2LjM1OTM3NX0seyJ4Ijo2MDAuMzMyMDMxMjUsInkiOjE4ODEuODU5Mzc1fSx7IngiOjYwMC4zMzIwMzEyNSwieSI6MTkwNi44NTkzNzV9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M779.217,1051.938L789.049,1057.854C798.88,1063.771,818.544,1075.604,828.375,1102.014C838.207,1128.424,838.207,1169.411,838.207,1210.398C838.207,1251.385,838.207,1292.372,838.207,1324.949C838.207,1357.526,838.207,1381.693,838.207,1405.859C838.207,1430.026,838.207,1454.193,838.207,1478.359C838.207,1502.526,838.207,1526.693,838.207,1550.859C838.207,1575.026,838.207,1599.193,838.207,1623.359C838.207,1647.526,838.207,1671.693,838.207,1694.109C838.207,1716.526,838.207,1737.193,838.207,1752.776C838.207,1768.359,838.207,1778.859,838.207,1784.109L838.207,1789.359" id="L_M_P_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_M_P_0" data-points="W3sieCI6Nzc5LjIxNjk3MTk4Mjc1ODcsInkiOjEwNTEuOTM3NX0seyJ4Ijo4MzguMjA3MDMxMjUsInkiOjEwODcuNDM3NX0seyJ4Ijo4MzguMjA3MDMxMjUsInkiOjEyMTAuMzk4NDM3NX0seyJ4Ijo4MzguMjA3MDMxMjUsInkiOjEzMzMuMzU5Mzc1fSx7IngiOjgzOC4yMDcwMzEyNSwieSI6MTQwNS44NTkzNzV9LHsieCI6ODM4LjIwNzAzMTI1LCJ5IjoxNDc4LjM1OTM3NX0seyJ4Ijo4MzguMjA3MDMxMjUsInkiOjE1NTAuODU5Mzc1fSx7IngiOjgzOC4yMDcwMzEyNSwieSI6MTYyMy4zNTkzNzV9LHsieCI6ODM4LjIwNzAzMTI1LCJ5IjoxNjk1Ljg1OTM3NX0seyJ4Ijo4MzguMjA3MDMxMjUsInkiOjE3NTcuODU5Mzc1fSx7IngiOjgzOC4yMDcwMzEyNSwieSI6MTc5My4zNTkzNzV9XQ==" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/><path d="M838.207,1846.359L838.207,1852.276C838.207,1858.193,838.207,1870.026,810.14,1882.019C782.073,1894.012,725.938,1906.166,697.871,1912.242L669.804,1918.319" id="L_P_PLAY_0" class="edge-thickness-normal edge-pattern-solid edge-thickness-normal edge-pattern-solid flowchart-link" style=";" data-edge="true" data-et="edge" data-id="L_P_PLAY_0" data-points="W3sieCI6ODM4LjIwNzAzMTI1LCJ5IjoxODQ2LjM1OTM3NX0seyJ4Ijo4MzguMjA3MDMxMjUsInkiOjE4ODEuODU5Mzc1fSx7IngiOjY2NS44OTQ1MzEyNSwieSI6MTkxOS4xNjUwNzY1MjM5MDk2fV0=" marker-end="url(#my-svg_flowchart-v2-pointEnd)"/></g><g class="edgeLabels"><g class="edgeLabel"><g class="label" data-id="L_A_B_0" transform="translate(0, 0)"><foreignObject width="0" height="0"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(141.92578125, 241.5)"><g class="label" data-id="L_B_C_0" transform="translate(-31.421875, -10.5)"><foreignObject width="62.84375" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Success  </p></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(1197.6328125, 241.5)"><g class="label" data-id="L_B_D_0" transform="translate(-99.3515625, -10.5)"><foreignObject width="198.703125" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  E_PF_ACCOUNT_NOT_FOUND  </p></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(69.0078125, 1087.4375)"><g class="label" data-id="L_C_PLAY_0" transform="translate(-61.0078125, -10.5)"><foreignObject width="122.015625" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Xbox/MSA linked  </p></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(214.84375, 446.4375)"><g class="label" data-id="L_C_E_0" transform="translate(-39.9140625, -10.5)"><foreignObject width="79.828125" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Not linked  </p></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(349.04876, 614.71617)"><g class="label" data-id="L_E_LATE_0" transform="translate(-48.65625, -10.5)"><foreignObject width="97.3125" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Player agrees  </p></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(249.171875, 1210.3984375)"><g class="label" data-id="L_E_PLAY_0" transform="translate(-47.2890625, -10.5)"><foreignObject width="94.578125" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Player defers  </p></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(1111.8046875, 446.4375)"><g class="label" data-id="L_D_F_0" transform="translate(-55.2890625, -10.5)"><foreignObject width="110.578125" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Xbox bootstrap  </p></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(1322.25390625, 1014.9375)"><g class="label" data-id="L_D_G_0" transform="translate(-42.734375, -10.5)"><foreignObject width="85.46875" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Steam-only  </p></span></div></foreignObject></g></g><g class="edgeLabel"><g class="label" data-id="L_G_PLAY_0" transform="translate(0, 0)"><foreignObject width="0" height="0"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(1073.01171875, 942.4375)"><g class="label" data-id="L_F_H_0" transform="translate(-99.3515625, -10.5)"><foreignObject width="198.703125" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  E_PF_ACCOUNT_NOT_FOUND  </p></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(981.77968, 615.28612)"><g class="label" data-id="L_F_LATE_0" transform="translate(-57.5859375, -10.5)"><foreignObject width="115.171875" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Existing account  </p></span></div></foreignObject></g></g><g class="edgeLabel"><g class="label" data-id="L_H_I_0" transform="translate(0, 0)"><foreignObject width="0" height="0"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"></span></div></foreignObject></g></g><g class="edgeLabel"><g class="label" data-id="L_I_J_0" transform="translate(0, 0)"><foreignObject width="0" height="0"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"></span></div></foreignObject></g></g><g class="edgeLabel"><g class="label" data-id="L_J_PLAY_0" transform="translate(0, 0)"><foreignObject width="0" height="0"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"></span></div></foreignObject></g></g><g class="edgeLabel"><g class="label" data-id="L_LATE_K_0" transform="translate(0, 0)"><foreignObject width="0" height="0"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(363.75390625, 1405.859375)"><g class="label" data-id="L_K_PLAY_0" transform="translate(-31.421875, -10.5)"><foreignObject width="62.84375" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Success  </p></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(717.734375, 818.4375)"><g class="label" data-id="L_K_L_0" transform="translate(-31.2578125, -10.5)"><foreignObject width="62.515625" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Conflict  </p></span></div></foreignObject></g></g><g class="edgeLabel"><g class="label" data-id="L_L_M_0" transform="translate(0, 0)"><foreignObject width="0" height="0"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(600.33203125, 1087.4375)"><g class="label" data-id="L_M_N0_0" transform="translate(-69.28125, -10.5)"><foreignObject width="138.5625" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Keep Xbox progress  </p></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(526.27734375, 1333.359375)"><g class="label" data-id="L_N0_N1_0" transform="translate(-17.5546875, -10.5)"><foreignObject width="35.109375" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Yes  </p></span></div></foreignObject></g></g><g class="edgeLabel"><g class="label" data-id="L_N1_N2_0" transform="translate(0, 0)"><foreignObject width="0" height="0"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(674.38671875, 1405.859375)"><g class="label" data-id="L_N0_N2_0" transform="translate(-17.0078125, -10.5)"><foreignObject width="34.015625" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  No  </p></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(505.88671875, 1623.359375)"><g class="label" data-id="L_N2_N3_0" transform="translate(-101.7421875, -10.5)"><foreignObject width="203.484375" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table; white-space: break-spaces; line-height: 1.5; max-width: 200px; text-align: center; width: 200px;"><span class="edgeLabel"><p>  LinkedAccountAlreadyClaimed  </p></span></div></foreignObject></g></g><g class="edgeLabel"><g class="label" data-id="L_N3_O_0" transform="translate(0, 0)"><foreignObject width="0" height="0"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(695.09375, 1695.859375)"><g class="label" data-id="L_N2_O_0" transform="translate(-31.421875, -10.5)"><foreignObject width="62.84375" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Success  </p></span></div></foreignObject></g></g><g class="edgeLabel"><g class="label" data-id="L_O_PLAY_0" transform="translate(0, 0)"><foreignObject width="0" height="0"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"></span></div></foreignObject></g></g><g class="edgeLabel" transform="translate(838.20703125, 1478.359375)"><g class="label" data-id="L_M_P_0" transform="translate(-72.8359375, -10.5)"><foreignObject width="145.671875" height="21"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"><p>  Keep Steam progress  </p></span></div></foreignObject></g></g><g class="edgeLabel"><g class="label" data-id="L_P_PLAY_0" transform="translate(0, 0)"><foreignObject width="0" height="0"><div xmlns="http://www.w3.org/1999/xhtml" class="labelBkg" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="edgeLabel"></span></div></foreignObject></g></g></g><g class="nodes"><g class="node default" id="flowchart-A-0" transform="translate(690.3125, 45)"><rect class="basic label-container" style="" x="-158.65625" y="-37" width="317.3125" height="74"/><g class="label" style="" transform="translate(-126.65625, -21)"><rect/><foreignObject width="253.3125" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table; white-space: break-spaces; line-height: 1.5; max-width: 200px; text-align: center; width: 200px;"><span class="nodeLabel"><p>Create Steam local user<br />PFLocalUserCreateHandleWithSteamUser</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-B-1" transform="translate(690.3125, 169)"><rect class="basic label-container" style="" x="-95.171875" y="-37" width="190.34375" height="74"/><g class="label" style="" transform="translate(-63.171875, -21)"><rect/><foreignObject width="126.34375" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Try Steam sign-in<br />createAccount=false</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-C-3" transform="translate(141.92578125, 343.96875)"><rect class="basic label-container" style="" x="-101.328125" y="-37" width="202.65625" height="74"/><g class="label" style="" transform="translate(-69.328125, -21)"><rect/><foreignObject width="138.65625" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Check linked identities<br />GetAccountInfo</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-D-5" transform="translate(1197.6328125, 343.96875)"><polygon points="66.96875,0 133.9375,-66.96875 66.96875,-133.9375 0,-66.96875" class="label-container" transform="translate(-66.46875, 66.96875)"/><g class="label" style="" transform="translate(-40.46875, -10.5)"><rect/><foreignObject width="80.9375" height="21"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Player choice</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-PLAY-7" transform="translate(600.33203125, 1933.359375)"><rect class="basic label-container" style="" x="-65.5625" y="-26.5" width="131.125" height="53"/><g class="label" style="" transform="translate(-33.5625, -10.5)"><rect/><foreignObject width="67.125" height="21"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Play online</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-E-9" transform="translate(214.84375, 518.9375)"><rect class="basic label-container" style="" x="-110.8359375" y="-37" width="221.671875" height="74"/><g class="label" style="" transform="translate(-78.8359375, -21)"><rect/><foreignObject width="157.671875" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Prompt to link Xbox/MSA<br />non-blocking</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-LATE-11" transform="translate(636.47265625, 653.4375)"><rect class="basic label-container" style="" x="-74.7734375" y="-26.5" width="149.546875" height="53"/><g class="label" style="" transform="translate(-42.7734375, -10.5)"><rect/><foreignObject width="85.546875" height="21"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>BeginLateLink</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-F-15" transform="translate(1111.8046875, 518.9375)"><rect class="basic label-container" style="" x="-95.171875" y="-37" width="190.34375" height="74"/><g class="label" style="" transform="translate(-63.171875, -21)"><rect/><foreignObject width="126.34375" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Try Xbox sign-in<br />createAccount=false</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-G-17" transform="translate(1322.25390625, 1819.859375)"><rect class="basic label-container" style="" x="-93.5234375" y="-37" width="187.046875" height="74"/><g class="label" style="" transform="translate(-61.5234375, -21)"><rect/><foreignObject width="123.046875" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Steam sign-in<br />createAccount=true</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-H-20" transform="translate(1073.01171875, 1550.859375)"><rect class="basic label-container" style="" x="-95.84375" y="-37" width="191.6875" height="74"/><g class="label" style="" transform="translate(-63.84375, -21)"><rect/><foreignObject width="127.6875" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Create Xbox account<br />createAccount=true</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-I-24" transform="translate(1073.01171875, 1695.859375)"><rect class="basic label-container" style="" x="-117.6796875" y="-26.5" width="235.359375" height="53"/><g class="label" style="" transform="translate(-85.6796875, -10.5)"><rect/><foreignObject width="171.359375" height="21"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Link Steam to Xbox account</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-J-25" transform="translate(1073.01171875, 1819.859375)"><rect class="basic label-container" style="" x="-105.71875" y="-26.5" width="211.4375" height="53"/><g class="label" style="" transform="translate(-73.71875, -10.5)"><rect/><foreignObject width="147.4375" height="21"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Rebind Steam local user</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-K-28" transform="translate(636.47265625, 756.4375)"><rect class="basic label-container" style="" x="-126.875" y="-26.5" width="253.75" height="53"/><g class="label" style="" transform="translate(-94.875, -10.5)"><rect/><foreignObject width="189.75" height="21"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Try link Xbox to Steam account</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-L-32" transform="translate(717.734375, 880.4375)"><rect class="basic label-container" style="" x="-110.515625" y="-26.5" width="221.03125" height="53"/><g class="label" style="" transform="translate(-78.515625, -10.5)"><rect/><foreignObject width="157.03125" height="21"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Xbox sign-in to get entity</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-M-34" transform="translate(717.734375, 1014.9375)"><rect class="basic label-container" style="" x="-120.9375" y="-37" width="241.875" height="74"/><g class="label" style="" transform="translate(-88.9375, -21)"><rect/><foreignObject width="177.875" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>RunReconciliation<br />fetch account info + show UI</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-N0-36" transform="translate(600.33203125, 1210.3984375)"><polygon points="87.4609375,0 174.921875,-87.4609375 87.4609375,-174.921875 0,-87.4609375" class="label-container" transform="translate(-86.9609375, 87.4609375)"/><g class="label" style="" transform="translate(-50.4609375, -21)"><rect/><foreignObject width="100.921875" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Xbox entity has<br />different Steam?</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-N1-38" transform="translate(526.27734375, 1405.859375)"><rect class="basic label-container" style="" x="-96.1015625" y="-37" width="192.203125" height="74"/><g class="label" style="" transform="translate(-64.1015625, -21)"><rect/><foreignObject width="128.203125" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Unlink old Steam<br />UnlinkSteamAccount</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-N2-40" transform="translate(600.33203125, 1550.859375)"><rect class="basic label-container" style="" x="-89.4453125" y="-37" width="178.890625" height="74"/><g class="label" style="" transform="translate(-57.4453125, -21)"><rect/><foreignObject width="114.890625" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Link current Steam<br />to Xbox account</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-N3-44" transform="translate(505.88671875, 1695.859375)"><rect class="basic label-container" style="" x="-77.2734375" y="-37" width="154.546875" height="74"/><g class="label" style="" transform="translate(-45.2734375, -21)"><rect/><foreignObject width="90.546875" height="42"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Retry with<br />forceLink=true</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-O-46" transform="translate(600.33203125, 1819.859375)"><rect class="basic label-container" style="" x="-105.71875" y="-26.5" width="211.4375" height="53"/><g class="label" style="" transform="translate(-73.71875, -10.5)"><rect/><foreignObject width="147.4375" height="21"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Rebind Steam local user</p></span></div></foreignObject></g></g><g class="node default" id="flowchart-P-51" transform="translate(838.20703125, 1819.859375)"><rect class="basic label-container" style="" x="-79.0859375" y="-26.5" width="158.171875" height="53"/><g class="label" style="" transform="translate(-47.0859375, -10.5)"><rect/><foreignObject width="94.171875" height="21"><div xmlns="http://www.w3.org/1999/xhtml" style="display: table-cell; white-space: nowrap; line-height: 1.5; max-width: 200px; text-align: center;"><span class="nodeLabel"><p>Defer Xbox link</p></span></div></foreignObject></g></g></g></g></g></svg>
\ No newline at end of file
diff --git a/playfab-docs/player-progression/game-saves/offline.md b/playfab-docs/player-progression/game-saves/offline.md
index c40c7417c..65a66f187 100644
--- a/playfab-docs/player-progression/game-saves/offline.md
+++ b/playfab-docs/player-progression/game-saves/offline.md
@@ -28,7 +28,7 @@ When network is unavailable or the user chooses to play offline, the system ente
 
 ### Handling Network Failures During Initial Sync
 
-When `PFGameSaveFilesAddUserWithUiAsync()` is called without network connectivity, it triggers a `PFGameSaveFilesUiSyncFailedCallback`. Users can respond with two options:
+When `PFGameSaveFilesAddUserWithUiAsync()` is called without network connectivity, it triggers a `PFGameSaveFilesUiSyncFailedCallback`. The `XAsyncBlock` callback doesn't fire while the system waits for the user's response—the async operation is paused until the user selects a terminal action.
 
 ```cpp
 // Handle sync failure callback
@@ -48,8 +48,9 @@ void MyPFGameSaveFilesUiSyncFailedCallback(PFLocalUserHandle localUserHandle, PF
 ```
 
 **User Response Options:**
-- **Try Again**: Attempts the network call again (loops back to failure callback if still offline)
-- **Use Offline**: `PFGameSaveFilesAddUserWithUiAsync` async callback reports `S_OK` but puts system into offline mode (can be detected with `PFGameSaveFilesIsConnectedToCloud()`)
+- **Try Again (`Retry`)**: Retries the network call. If the retry also fails, this callback fires again and the user must respond again. The `XAsyncBlock` callback remains deferred through each retry loop.
+- **Use Offline (`UseOffline`)**: The `XAsyncBlock` callback fires with `S_OK`, but the system enters offline mode (detectable with `PFGameSaveFilesIsConnectedToCloud()`).
+- **Cancel**: The `XAsyncBlock` callback fires with `E_PF_GAMESAVE_USER_CANCELLED`.
 
 ### API Behavior in Offline Mode
 
@@ -89,8 +90,12 @@ Use this API before attempting cloud operations to provide appropriate user feed
 
 ### Upload Behavior in Connected Mode
 
-Even in connected mode, uploads can fail due to network issues. When this happens:
-- Failure UI callback is triggered
-- User can choose to retry or cancel
-- If cancelled, async completion returns `E_PF_GAMESAVE_USER_CANCELLED`
-- The game can call upload again later when network is restored
+Even in connected mode, uploads can fail due to network issues or rate limits. When this happens, the `XAsyncBlock` callback doesn't fire immediately—the async operation pauses while the system waits for the user's response through the [UI callback state machine](./ui-callbacks.md#how-the-state-machine-works):
+
+1. The `PFGameSaveFilesUiSyncFailedCallback` fires with the error details.
+2. The `XAsyncBlock` callback doesn't fire yet—the operation is paused while the system waits for a response.
+3. If the user selects `Retry`, the upload retries. If it fails again, the callback fires again and the user must respond again.
+4. If the user selects `Cancel`, the `XAsyncBlock` callback fires with `E_PF_GAMESAVE_USER_CANCELLED`.
+5. If a retry succeeds, the `XAsyncBlock` callback fires with `S_OK`.
+
+The game can call `PFGameSaveFilesUploadWithUiAsync()` again later when network is restored.
diff --git a/playfab-docs/player-progression/game-saves/overview.md b/playfab-docs/player-progression/game-saves/overview.md
index 1e95846ae..38f34fe66 100644
--- a/playfab-docs/player-progression/game-saves/overview.md
+++ b/playfab-docs/player-progression/game-saves/overview.md
@@ -14,7 +14,7 @@ ms.localizationpriority: medium
 
 ## What is Game Saves
 
-Game Saves allows players to continue their game, with their progress intact, as they switch across platforms, devices, and stores. Game Saves handles file synchronization and conflict resolution, helps players maintain a single-point-of-progression, and fully supports offline play.
+By using Game Saves, players can continue their game with their progress intact when they switch across platforms, devices, and stores. Game Saves handles file synchronization and conflict resolution. It helps players maintain a single point of progression and fully supports offline play.
 
 ### Benefits
 
@@ -22,16 +22,17 @@ Game Saves allows players to continue their game, with their progress intact, as
 - Eliminates the complexity of implementing cross-platform synchronization.
 - Supports online and offline play with control of transitions between those states.
 - Minimizes the chance of version conflicts.
-- Helps players seamlessly transition between devices and platforms to maintain a consistent point-of-progression.
+- Helps players seamlessly transition between devices and platforms to maintain a consistent point of progression.
 - Provides contextual cues to assist players in making informed conflict resolution and single point of progression decisions, when needed.
 - Recovers players from bad state with support for version rollback.
+- Emits [PlayStream events](playstream-events.md) for tracking save activity, conflicts, and rollbacks across your player base.
 - Works with background uploader and title-callable UI, where available.
 
 ### Gaming platforms currently supported
 
 - Xbox (One, Series S/X, PC, cloud)
 - Steam (PC, Steam Deck)
-- Windows (other stores / launchers)
+- Windows (other stores and launchers)
 
 ### Languages and game engines currently supported
 
@@ -53,16 +54,16 @@ Use this sample to:
 
 ### Authentication requirements
 
-- **Identity linking**: Titles must use a shared or linked user identity for game saves to seamlessly transition between platforms. PlayFab supports account linking between two authenticated providers.
+- **Identity linking**: To ensure game saves seamlessly transition between platforms, titles must use a shared or linked user identity. PlayFab supports account linking between two authenticated providers.
 
 ### Platform-specific considerations
 
-- **Non-Xbox/Windows platforms**: On platforms other than Windows and Xbox (such as Steam Deck), the UI must be provided by the game. Game Saves will trigger UI callbacks that the game can respond to.
+- **Non-Xbox/Windows platforms**: On platforms other than Windows and Xbox (such as Steam Deck), the game must provide the UI. Game Saves triggers UI callbacks that the game can respond to.
 
-- **Upload handling on non-Xbox/Windows platforms**: On platforms other than Windows and Xbox (such as Steam Deck), Game Saves upload will happen in the same process as the game. This means the game must warn the user not to exit before upload finishes, or the game save will not reach the cloud.
+- **Upload handling on non-Xbox/Windows platforms**: On platforms other than Windows and Xbox (such as Steam Deck), Game Saves upload happens in the same process as the game. This condition means the game must warn the user not to exit before upload finishes, or the game save doesn't reach the cloud.
 
 ### Multi-platform deployment
 
-- **Cross-storefront compatibility**: Games that plan to ship on multiple storefronts should consider how title updates out of lockstep will affect shared cloud game save data.
+- **Cross-storefront compatibility**: Games that plan to ship on multiple storefronts should consider how title updates that don't occur in lockstep affect shared cloud game save data.
 
-- **Robust save implementation**: While not required, for maximum reliability, games should implement a double-buffering approach alternating between two local on disk save files to ensure there's always a known good fallback if a write operation fails. This best practice is independent of cloud saves and helps prevent save corruption during abnormal game termination.
+- **Robust save implementation**: While not required, for maximum reliability, games should implement a double-buffering approach that alternates between two local on-disk save files to ensure there's always a known good fallback if a write operation fails. This best practice is independent of cloud saves and helps prevent save corruption during abnormal game termination.
diff --git a/playfab-docs/player-progression/game-saves/playstream-events.md b/playfab-docs/player-progression/game-saves/playstream-events.md
new file mode 100644
index 000000000..9fcc2f23a
--- /dev/null
+++ b/playfab-docs/player-progression/game-saves/playstream-events.md
@@ -0,0 +1,106 @@
+---
+title: Game Saves PlayStream events
+author: amccalib
+description: PlayStream events emitted by Game Saves, including save finalization, conflict resolution, and known-good rollback telemetry.
+ms.author: andmcc
+ms.date: 03/06/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, game saves, playstream, telemetry, events, conflicts, rollback
+ms.localizationpriority: medium
+---
+
+# Game Saves PlayStream events
+
+PlayFab Game Saves emits PlayStream events that you can use to track how players save, sync, and manage their game data. Use these events to monitor save activity, detect conflicts, and understand cross-device usage patterns across your player base.
+
+All Game Saves events are emitted against `title_player_account` entities in the `playfab.gamesave` namespace.
+
+## Events
+
+### `gamesave_version_finalized`
+
+Emitted each time a game save version is finalized. All files are uploaded and the version is complete. This event is the primary signal for tracking save activity.
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `Version` | `long` | The version number of the finalized game save |
+| `FinalizedAt` | `DateTime` | Timestamp when the version was finalized |
+| `TotalSizeBytes` | `long` | Total size of the finalized version, including all files |
+| `TotalFileCount` | `int` | Total number of files in the finalized version |
+| `NewFileCount` | `int` | Number of new files added in this version |
+| `NewFilesSizeBytes` | `long` | Size of the new files added in this version |
+| `PlayerIdentityProvider` | `string` | The identity provider the player used (for example, Steam, Xbox Live) |
+| `DeviceType` | `string` | The type of device the save was uploaded from |
+| `IsGeneratedByRollback` | `bool` | `true` if this version was created by rolling back to a previous version |
+| `Conflict` | `Conflict` | Present when this version was finalized as part of a conflict resolution. `null` otherwise. See [Conflict resolution](#scenario-conflict-resolution) |
+
+**Conflict** (nested object, present only during conflict resolution):
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `IsWinner` | `bool` | Whether the player's local changes won the conflict. The event always corresponds to a new manifest created from the client's local data. `true` means that manifest became the canonical version; `false` means the manifest was preserved as a rollback point while the existing cloud version remained canonical |
+| `ConflictingVersion` | `long` | The version number of the existing cloud version that was in conflict |
+
+### `gamesave_version_marked_known_good`
+
+Emitted when a game save version is explicitly marked as "known good." A known-good version serves as a trusted restore point. The version the system rolls back to if a player or the title needs to recover from a bad save state.
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `Version` | `long` | The version that was marked as known good |
+| `MarkedAt` | `DateTime` | Timestamp when the version was marked |
+
+---
+
+## Scenarios
+
+### Scenario: Standard cross-device usage
+
+A typical cross-device flow looks like a player saving on one device and resuming on another. In PlayStream, this pattern appears as a sequence of `gamesave_version_finalized` events with incrementing `Version` numbers.
+
+**What you see:**
+
+- A `gamesave_version_finalized` event each time the player saves, with `DeviceType` and `PlayerIdentityProvider` indicating which device and identity provider were used.
+- `NewFileCount` and `NewFilesSizeBytes` show how much data changed compared to the previous version. A version where `NewFileCount` is 0 means the player finalized a version with no new file content (for example, a metadata-only update).
+- `Conflict` is `null` and `IsGeneratedByRollback` is `false` for normal saves.
+
+**What to watch for:**
+
+- **Save frequency per player**: Track the rate of finalization events to understand player engagement and saving behavior.
+- **Save sizes over time**: Monitor `TotalSizeBytes` and `NewFilesSizeBytes` to catch unexpected growth in save data that could affect storage costs or sync times.
+- **Device distribution**: Aggregate `DeviceType` to understand which platforms your players save from most frequently.
+
+### Scenario: Conflict resolution
+
+Conflicts occur when two devices finalize a game save version against the same base version. For example, a player might play offline on their console and PC at the same time, and both devices try to sync when they come back online.
+
+**What you see:**
+
+- During conflict resolution, the client always uploads its local files to a new manifest and finalizes the manifest. This process produces a single `gamesave_version_finalized` event with a non-null `Conflict` object. The existing cloud version (already finalized in a prior event) doesn't produce a new event.
+- `Conflict.IsWinner` tells you whether the player's local changes won the conflict:
+  - `true`—the player chose **keep local**. The new manifest becomes the canonical version, and the prior cloud version is superseded.
+  - `false`—the player chose **keep remote**. The new manifest is preserved as a rollback point (containing the rejected local data), while the existing cloud version remains canonical.
+- `Conflict.ConflictingVersion` points to the existing cloud version that was in conflict.
+
+**What to watch for:**
+
+- **Conflict rate**—Filter for `gamesave_version_finalized` events where `Conflict` is present. A rising conflict rate might indicate that players frequently switch devices without syncing, or that your title's save cadence causes unnecessary version collisions.
+- **Local vs. remote preference**—Compare the ratio of `IsWinner = true` (kept local) vs. `IsWinner = false` (kept remote) to understand how players resolve conflicts. A strong skew toward one side might indicate a UX issue with the conflict prompt.
+- **Cross-device conflict patterns**—Use `DeviceType` and `PlayerIdentityProvider` on conflict events to understand which platform combinations are most prone to conflicts.
+
+### Scenario: Known good and rollback
+
+The "known good" mechanism lets you mark a specific version as a trusted restore point. If a player's save becomes corrupted or they need to recover, the system can roll back to the most recent known-good version and create a new version from it.
+
+**What you see:**
+
+- A `gamesave_version_marked_known_good` event when you designate a version as the restore point, with the `Version` number and `MarkedAt` timestamp.
+- If a rollback occurs, the system emits a new `gamesave_version_finalized` event with `IsGeneratedByRollback = true`. This new version's content is based on the known-good version, but it gets a new, incremented version number.
+- The rollback-generated version might also have `Conflict` data if the rollback was triggered as part of a conflict resolution.
+
+**What to watch for:**
+
+- **Rollback frequency**—Track `gamesave_version_finalized` events where `IsGeneratedByRollback = true`. Frequent rollbacks for a title might indicate save corruption issues or problems with the title's save logic.
+- **Known-good freshness**—Compare the `Version` in `gamesave_version_marked_known_good` against the latest finalized `Version` for the same player. A large gap means the player would lose significant progress if a rollback is needed.
+- **Rollback + conflict correlation**—If rollback-generated versions frequently appear alongside conflict data, that pattern might suggest that your conflict resolution strategy is triggering rollbacks as a side effect.
diff --git a/playfab-docs/player-progression/game-saves/quickstart.md b/playfab-docs/player-progression/game-saves/quickstart.md
index a2c3dfcca..48a8cb97e 100644
--- a/playfab-docs/player-progression/game-saves/quickstart.md
+++ b/playfab-docs/player-progression/game-saves/quickstart.md
@@ -278,6 +278,12 @@ if (FAILED(hr))
 // Success! Save data is now safely stored in the cloud
 ```
 
+### When can I write to the save folder again?
+
+During upload, the system reads and compresses your local save files before uploading them. Once the sync state transitions to `Uploading` (reported via `PFGameSaveFilesUiProgressCallback`), the system has finished reading your files and it's safe to write to the save folder again. You don't need to wait for the full upload to complete before resuming saves.
+
+If you aren't using the progress callback, wait for the `XAsyncBlock` to complete before writing new save data.
+
 ### Best Practices
 1. **Handle failures gracefully**: Network issues shouldn't crash your game
 2. **Use appropriate options**: 
@@ -292,47 +298,24 @@ if (FAILED(hr))
 
 ## Step 4: Handle UI Callbacks (Optional)
 
-Game Saves provides built-in UI for Xbox and Windows platforms, but you can customize the user experience by implementing your own UI callbacks.
-
-### Platform Requirements
-- **Xbox/Windows**: Built-in UI is provided; custom callbacks are optional
-- **Other platforms** (Steam Deck, etc.): Custom UI callbacks are **required**
-
-### Types of UI Callbacks
-- **Progress**: Show upload/download progress to users
-- **Conflicts**: Handle situations where local and cloud saves differ
-- **Active Device Contention**: Warn when user tries to sync on multiple devices
-- **Sync Failures**: Handle network or other sync errors
-- **Out of Storage**: Notify users when local storage is too full to sync
+Game Saves provides built-in UI for Xbox and Windows platforms. On other platforms (such as Steam Deck), your game must provide its own UI by handling callbacks.
 
-### When Callbacks Trigger
-UI callbacks only occur during two operations:
-- `PFGameSaveFilesAddUserWithUiAsync` (download from cloud)
-- `PFGameSaveFilesUploadWithUiAsync` (upload to cloud)
-
-### Implementation
+UI callbacks fire during `PFGameSaveFilesAddUserWithUiAsync` and `PFGameSaveFilesUploadWithUiAsync`. Each callback pauses the async operation until your game responds—the `XAsyncBlock` callback doesn't fire until all UI callbacks are resolved.
 
 ```cpp
 // Set up custom UI callbacks (call this before AddUser or Upload operations)
 // See sample for detailed examples of these callbacks.
-hr = PFGameSaveFilesSetUiCallbacks( 
-    MyPFGameSaveFilesUiProgressCallback, nullptr,
-    MyPFGameSaveFilesUiSyncFailedCallback, nullptr,
-    MyPFGameSaveFilesUiActiveDeviceContentionCallback, nullptr,
-    MyPFGameSaveFilesUiConflictCallback, nullptr,
-    MyPFGameSaveFilesUiOutOfStorageCallback, nullptr);
+PFGameSaveUICallbacks callbacks{};
+callbacks.progressCallback = MyProgressCallback;
+callbacks.syncFailedCallback = MySyncFailedCallback;
+callbacks.activeDeviceContentionCallback = MyActiveDeviceContentionCallback;
+callbacks.conflictCallback = MyConflictCallback;
+callbacks.outOfStorageCallback = MyOutOfStorageCallback;
+
+HRESULT hr = PFGameSaveFilesSetUiCallbacks(&callbacks);
 ```
 
-### Response APIs
-Each callback has a corresponding response API:
-- `PFGameSaveFilesSetUiProgressResponse()` - Respond to progress callback, letting users cancel
-- `PFGameSaveFilesSetUiConflictResponse()` - Respond to conflict callbacks
-- `PFGameSaveFilesSetUiActiveDeviceContentionResponse()` - Respond to device contention
-- `PFGameSaveFilesSetUiSyncFailedResponse()` - Respond to sync failures  
-- `PFGameSaveFilesSetUiOutOfStorageResponse()` - Respond to local storage full issues
-
-> [!IMPORTANT]
-> The Game Saves system waits for your response before continuing. Always call the appropriate response API when handling callbacks (except progress callbacks which don't need a response).
+For the full list of callback types, response APIs, user actions, and details on how the state machine works, see [Game Saves UI callbacks](./ui-callbacks.md).
 
 ## Understanding Save Conflicts
 
diff --git a/playfab-docs/player-progression/game-saves/rollback.md b/playfab-docs/player-progression/game-saves/rollback.md
new file mode 100644
index 000000000..301cf9a1c
--- /dev/null
+++ b/playfab-docs/player-progression/game-saves/rollback.md
@@ -0,0 +1,112 @@
+---
+title: Game Saves rollback
+author: andmcc
+description: How to use rollback to recover a player's game save to a previous version.
+ms.author: andmcc
+ms.date: 03/24/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, game saves, rollback, version recovery
+ms.localizationpriority: medium
+---
+
+# Game Saves rollback
+
+Rollback lets you restore a player's game save to an earlier state. Use it when a player's save becomes corrupted, when a title update introduces a bug that damages save data, or when a player wants to reverse a conflict resolution decision.
+
+## How rollback works
+
+Game Saves tracks finalized versions of a player's save data. When you trigger a rollback, the service creates a **new version** whose contents are identical to the earlier state you're restoring. Rollback preserves the original version history. It doesn't delete or overwrite previous versions. Other devices that sync after the rollback see it as a normal update.
+
+There are two types of rollback. You trigger each by passing an option flag to `PFGameSaveFilesAddUserWithUiAsync`:
+
+| Option | Description |
+|--------|-------------|
+| `PFGameSaveFilesAddUserOptions::RollbackToLastKnownGood` | Restores the most recently verified prior cloud save. This save was previously loaded and later replaced by a newer upload. |
+| `PFGameSaveFilesAddUserOptions::RollbackToLastConflict` | Restores the save state that lost the most recent conflict resolution. |
+
+Both options fall back to default behavior (sync the current latest version) if no eligible restore point exists.
+
+## When to use each rollback type
+
+### Rollback to last known good
+
+Use `RollbackToLastKnownGood` when you suspect the latest upload is bad. Common triggers include:
+
+- Load failure or failed integrity check after downloading a save.
+- A crash during or immediately after a save operation.
+- A player report of corrupted or regressed state.
+
+The service automatically tracks which versions are "known good." You don't need to mark them explicitly. A version becomes known good when you successfully load it and a newer upload later replaces it.
+
+### Rollback to last conflict
+
+Use `RollbackToLastConflict` when a player chose the wrong side during conflict resolution. As described in [Game Saves conflicts](conflicts.md), both resolution choices preserve the discarded branch. This rollback option restores that preserved branch.
+
+## Calling the API
+
+Trigger rollback by passing the appropriate option to `PFGameSaveFilesAddUserWithUiAsync`. You can only call this function once per user, so to roll back for a user that's already added, first call `PFGameSaveFilesUninitializeAsync` and wait for it to complete.
+
+```cpp
+// Rollback to last known good version
+XAsyncBlock async{};
+async.queue = queue;
+async.callback = [](XAsyncBlock* async)
+{
+    HRESULT hr = PFGameSaveFilesAddUserWithUiResult(async);
+    if (SUCCEEDED(hr))
+    {
+        // Save data is now restored to the last known good version.
+        // Read files from the game save folder as usual.
+    }
+};
+
+HRESULT hr = PFGameSaveFilesAddUserWithUiAsync(
+    localUserHandle,
+    PFGameSaveFilesAddUserOptions::RollbackToLastKnownGood,
+    &async
+);
+```
+
+To roll back to the last conflict loser instead, replace the option flag:
+
+```cpp
+HRESULT hr = PFGameSaveFilesAddUserWithUiAsync(
+    localUserHandle,
+    PFGameSaveFilesAddUserOptions::RollbackToLastConflict,
+    &async
+);
+```
+
+### Fallback behavior
+
+If no eligible restore point exists for the requested rollback type, the call behaves as if you passed `PFGameSaveFilesAddUserOptions::None`. The current latest version syncs normally. Check the synced files after the call completes to confirm whether a rollback occurred.
+
+## Title configuration
+
+You can restrict client-initiated rollback through two configuration flags. When you enable either flag, only support tools and Game Manager can perform that type of rollback.
+
+| Flag | Effect |
+|------|--------|
+| `DisableClientRollbackToLastKnownGood` | Prevents game clients from rolling back to the last known good version. |
+| `DisableClientRollbackToLastConflictLoser` | Prevents game clients from reversing the most recent conflict resolution decision. |
+
+Set these flags in Game Manager under **Progression > Game Saves**.
+
+## Error handling
+
+| HRESULT | Meaning |
+|---------|---------|
+| `E_PF_GAME_SAVE_MANIFEST_NOT_ELIGIBLE_FOR_ROLLBACK` | No eligible restore point exists for the requested rollback type. |
+| `E_PF_GAME_SAVE_NOT_FINALIZED_MANIFEST_NOT_ELIGIBLE_AS_KNOWN_GOOD` | The target version isn't eligible as a known good restore point. |
+| `E_PF_GAME_SAVE_SERVICE_NOT_ENABLED_FOR_TITLE` | Game Saves isn't enabled for this title. Complete onboarding first. |
+| `E_PF_GAME_SAVE_SERVICE_ONBOARDING_PENDING` | Title onboarding is still in progress. |
+
+## Considerations
+
+- **Rollback creates a new version.** It doesn't erase history. The player's version sequence continues forward.
+- **The service tracks known good automatically.** It determines which versions qualify based on successful load-then-replace cycles. Your game doesn't need to mark versions explicitly.
+- **One rollback per add-user call.** Because you can only call `PFGameSaveFilesAddUserWithUiAsync` once per user, triggering a second rollback requires calling `PFGameSaveFilesUninitializeAsync` first.
+- **UI callbacks still fire.** Rollback goes through the same sync flow as a normal add-user call. Register your [UI callbacks](ui-callbacks.md) before calling the API.
+- **Restrict rollback if needed.** If your game handles recovery server-side or through support tooling, disable client rollback with the title configuration flags to prevent players from accidentally reverting progress.
+- **Rollback works on all platforms.** This API has no platform-specific guards.
diff --git a/playfab-docs/player-progression/game-saves/toc.yml b/playfab-docs/player-progression/game-saves/toc.yml
index 5b9f621b4..07f94eb08 100644
--- a/playfab-docs/player-progression/game-saves/toc.yml
+++ b/playfab-docs/player-progression/game-saves/toc.yml
@@ -6,14 +6,22 @@ items:
   href: onboarding.md
 - name: Quickstart
   href: quickstart.md
+- name: Account Linking
+  href: linking.md
 - name: October 2025 GDK Implementation
   href: october-2025-gdk-changes.md
 - name: Steam Deck Implementation
   href: steam-deck-implementation.md
 - name: Conflicts
   href: conflicts.md
+- name: Rollback
+  href: rollback.md
+- name: UI Callbacks
+  href: ui-callbacks.md
 - name: Offline Mode
   href: offline.md
+- name: PlayStream Events
+  href: playstream-events.md
 - name: Active Device Changes
   href: activedevicechanges.md
 - name: Limits
diff --git a/playfab-docs/player-progression/game-saves/ui-callbacks.md b/playfab-docs/player-progression/game-saves/ui-callbacks.md
new file mode 100644
index 000000000..0579cba8a
--- /dev/null
+++ b/playfab-docs/player-progression/game-saves/ui-callbacks.md
@@ -0,0 +1,175 @@
+---
+title: Game Saves UI callbacks
+author: amccalib
+description: How Game Saves UI callbacks work, including the state machine model, callback types, and response APIs.
+ms.author: andmcc
+ms.date: 03/06/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, game saves, ui callbacks, sync failed, conflict, progress
+ms.localizationpriority: medium
+---
+
+# Game Saves UI callbacks
+
+Game Saves provides a set of UI callbacks that let your game respond to events during sync operations. On Xbox and Windows, the platform provides built-in UI for these events. On other platforms (such as Steam Deck), your game must implement its own UI by handling these callbacks.
+
+Setting callbacks on Xbox and Windows overrides the platform-provided UI with your implementation. This is useful if your game needs a consistent player experience across all platforms—register the same callbacks everywhere and the built-in UI won't appear.
+
+## How the state machine works
+
+Game Saves uses an internal state machine to coordinate UI callbacks with the async operation lifecycle. When a UI callback fires, the async operation pauses—the `XAsyncBlock` callback doesn't fire until the callback is resolved. The state machine doesn't progress until the game calls the corresponding response API or the async operation is canceled.
+
+This means:
+
+- Each callback type has a corresponding response API. Call the response API to tell the system what to do next.
+- Response APIs can be called inside or outside the callback function.
+- If a response action is `Retry`, the operation retries and may trigger the same callback again.
+- The `XAsyncBlock` callback only fires once the operation reaches a terminal state—success, cancellation, or an offline fallback.
+
+For example, if an upload fails due to rate limits:
+
+1. `PFGameSaveFilesUiSyncFailedCallback` fires with the error.
+2. The `XAsyncBlock` callback doesn't fire yet—the state machine waits for a response.
+3. If the user selects `Retry` and the retry also fails, the sync failed callback fires again.
+4. If the user selects `Cancel`, the `XAsyncBlock` callback fires with `E_PF_GAMESAVE_USER_CANCELLED`.
+5. If a retry succeeds, the `XAsyncBlock` callback fires with `S_OK`.
+
+## When callbacks trigger
+
+UI callbacks only fire during two async operations:
+
+| Operation | Callbacks that can trigger |
+|-----------|--------------------------|
+| `PFGameSaveFilesAddUserWithUiAsync` | Progress, Sync Failed, Active Device Contention, Conflict, Out of Storage |
+| `PFGameSaveFilesUploadWithUiAsync` | Progress, Sync Failed |
+
+## Registering callbacks
+
+Register all callbacks before calling `PFGameSaveFilesAddUserWithUiAsync` or `PFGameSaveFilesUploadWithUiAsync`:
+
+```cpp
+PFGameSaveUICallbacks callbacks{};
+callbacks.progressCallback = MyProgressCallback;
+callbacks.progressContext = nullptr;
+callbacks.syncFailedCallback = MySyncFailedCallback;
+callbacks.syncFailedContext = nullptr;
+callbacks.activeDeviceContentionCallback = MyActiveDeviceContentionCallback;
+callbacks.activeDeviceContentionContext = nullptr;
+callbacks.conflictCallback = MyConflictCallback;
+callbacks.conflictContext = nullptr;
+callbacks.outOfStorageCallback = MyOutOfStorageCallback;
+callbacks.outOfStorageContext = nullptr;
+
+HRESULT hr = PFGameSaveFilesSetUiCallbacks(&callbacks);
+```
+
+## Callback reference
+
+### Progress
+
+Reports upload or download progress. Use `PFGameSaveFilesUiProgressGetProgress` inside the callback to retrieve the current `PFGameSaveFilesSyncState`, bytes completed, and bytes total.
+
+**Callback**: `PFGameSaveFilesUiProgressCallback`
+
+**Response API**: `PFGameSaveFilesSetUiProgressResponse`
+
+| Action | Effect |
+|--------|--------|
+| `Cancel` | Cancels the operation. The `XAsyncBlock` callback fires with `E_PF_GAMESAVE_USER_CANCELLED`. |
+
+> [!NOTE]
+> The progress callback doesn't require a response to continue—the operation keeps progressing on its own. Only call the response API if the user wants to cancel.
+
+#### Sync states
+
+The `PFGameSaveFilesSyncState` enum indicates which phase the operation is in:
+
+| State | Description | Safe to write to save folder? |
+|-------|-------------|-------------------------------|
+| `NotStarted` | Operation hasn't begun | Yes |
+| `PreparingForDownload` | Preparing to download from cloud | Yes |
+| `Downloading` | Downloading from cloud | No |
+| `PreparingForUpload` | Reading and compressing local files | No |
+| `Uploading` | Upload to cloud in progress (local files captured) | Yes |
+| `SyncComplete` | Operation finished | Yes |
+
+### Sync failed
+
+Fires when a sync operation fails, for example due to network issues or rate limits.
+
+**Callback**: `PFGameSaveFilesUiSyncFailedCallback`
+
+**Parameters**: Receives `PFGameSaveFilesSyncState` (the phase that failed) and `HRESULT` (the error code).
+
+**Response API**: `PFGameSaveFilesSetUiSyncFailedResponse`
+
+| Action | Effect |
+|--------|--------|
+| `Cancel` | Cancels the operation. The `XAsyncBlock` callback fires with `E_PF_GAMESAVE_USER_CANCELLED`. |
+| `Retry` | Retries the failed operation. If the retry fails, this callback fires again. |
+| `UseOffline` | Only valid during `PFGameSaveFilesAddUserWithUiAsync`. The `XAsyncBlock` callback fires with `S_OK`, but the system enters offline mode. Use `PFGameSaveFilesIsConnectedToCloud()` to detect this state. |
+
+For more details on offline mode behavior, see [Game Saves offline mode](./offline.md).
+
+### Active device contention
+
+Fires during `PFGameSaveFilesAddUserWithUiAsync` when another device is already the active device for this user. The callback receives `PFGameSaveDescriptor` structs for both the local and remote save data, which include device names, timestamps, and save sizes that you can display to help the user decide.
+
+**Callback**: `PFGameSaveFilesUiActiveDeviceContentionCallback`
+
+**Response API**: `PFGameSaveFilesSetUiActiveDeviceContentionResponse`
+
+| Action | Effect |
+|--------|--------|
+| `Cancel` | Cancels the operation. The `XAsyncBlock` callback fires with `E_PF_GAMESAVE_USER_CANCELLED`. |
+| `Retry` | Retries—useful if the user expects the other device to release soon. If the other device is still active, this callback fires again. |
+| `SyncLastSavedData` | Makes the local device active and syncs. The remote device can no longer upload and receives an active device changed notification. |
+
+For more details on active device behavior, see [Game Saves active device changes](./activedevicechanges.md).
+
+### Conflict
+
+Fires during `PFGameSaveFilesAddUserWithUiAsync` when local and cloud save data have diverged. The callback receives `PFGameSaveDescriptor` structs for both the local and remote save data.
+
+**Callback**: `PFGameSaveFilesUiConflictCallback`
+
+**Response API**: `PFGameSaveFilesSetUiConflictResponse`
+
+| Action | Effect |
+|--------|--------|
+| `Cancel` | Cancels the operation. The `XAsyncBlock` callback fires with `E_PF_GAMESAVE_USER_CANCELLED`. |
+| `TakeLocal` | Keeps local save data and uploads it to the cloud. |
+| `TakeRemote` | Discards local changes and downloads the cloud save data. |
+
+> [!IMPORTANT]
+> Conflict resolution applies to the entire save, not individual files or folders. For details on how conflicts are detected at the atomic unit level and resolved globally, see [Game Saves conflicts](./conflicts.md).
+
+### Out of storage
+
+Fires during `PFGameSaveFilesAddUserWithUiAsync` when the local device doesn't have enough disk space to download save data from the cloud. The callback receives `requiredBytes` indicating how much space is needed.
+
+**Callback**: `PFGameSaveFilesUiOutOfStorageCallback`
+
+**Response API**: `PFGameSaveFilesSetUiOutOfStorageResponse`
+
+| Action | Effect |
+|--------|--------|
+| `Cancel` | Cancels the operation. The `XAsyncBlock` callback fires with `E_PF_GAMESAVE_USER_CANCELLED`. |
+| `Retry` | Retries after the user frees local storage space. If there still isn't enough space, this callback fires again. |
+
+## Platform requirements
+
+| Platform | UI callbacks |
+|----------|-------------|
+| **Xbox and Windows** | Optional. Set callbacks to override the built-in UI. |
+| **Other platforms** (Steam Deck, etc.) | **Required**. No built-in UI is available; your game must handle all callbacks. |
+
+For Steam Deck implementation details, see [Steam Deck implementation guide](./steam-deck-implementation.md).
+
+## Related content
+
+- [Game Saves quickstart](./quickstart.md)
+- [Game Saves offline mode](./offline.md)
+- [Game Saves conflicts](./conflicts.md)
+- [Game Saves active device changes](./activedevicechanges.md)
diff --git a/playfab-docs/player-progression/index.yml b/playfab-docs/player-progression/index.yml
index 5034e95fb..ec0692dd9 100644
--- a/playfab-docs/player-progression/index.yml
+++ b/playfab-docs/player-progression/index.yml
@@ -1,6 +1,6 @@
 ### YamlMime:Landing
 
-title: Azure PlayFab Player progression documentation
+title: PlayFab Player progression documentation
 summary: PlayFab Player Progression services enable reliable storage and sharing of player progression data across all gaming devices. # < 160 chars
 
 metadata:
diff --git a/playfab-docs/player-progression/player-data/getting-player-profiles.md b/playfab-docs/player-progression/player-data/getting-player-profiles.md
index 49ec4081b..70b505348 100644
--- a/playfab-docs/player-progression/player-data/getting-player-profiles.md
+++ b/playfab-docs/player-progression/player-data/getting-player-profiles.md
@@ -24,7 +24,7 @@ In this tutorial you learn how to:
 
 ## Requirements
 
-* A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+* A [PlayFab developer account](https://developer.playfab.com).
 * An installed copy of the Unity Editor. To install Unity for personal use via Unity Hub, or Unity+ for professional use, see [Download Unity](https://unity3d.com/get-unity/download).
   > [!NOTE]
   > The PlayFab Unity3D SDK supports Unity Editor version 5.3 (released December 2015) and higher.
@@ -130,7 +130,7 @@ By default, the **ALLOW CLIENT ACCESS TO PROFILE PROPERTIES:** had only **Displa
 
 To configure additional constraints for the title:
 
-* In [Game Manager](https://developer.playfab.com/en-US/login), select your title.
+* In [Game Manager](https://developer.playfab.com), select your title.
 * Select the gear icon in the upper left-hand corner, then select **Title settings**.
 * Select the **Client Profile Options** tab.
 * To enable both **Created** and **LastLogin** in the [ProfileConstraints](xref:titleid.playfabapi.com.server.accountmanagement.getplayerprofile#playerprofileviewconstraints), check **Creation date** and **Last login time**, then select **SAVE CLIENT PROFILE OPTIONS**.
diff --git a/playfab-docs/player-progression/player-data/quickstart.md b/playfab-docs/player-progression/player-data/quickstart.md
index 06a24687f..79f21d806 100644
--- a/playfab-docs/player-progression/player-data/quickstart.md
+++ b/playfab-docs/player-progression/player-data/quickstart.md
@@ -21,7 +21,7 @@ Player data is information that applies to an individual player or player group
 
 ## Requirements
 
-- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A [PlayFab developer account](https://developer.playfab.com).
 - An installed copy of the Unity Editor. To install Unity for personal use via Unity Hub, or Unity+ for professional use, see [Download Unity](https://unity3d.com/get-unity/download).
   > [!NOTE]
   > The PlayFab Unity3D SDK supports Unity Editor version 5.3 (released December 2015) and higher.
diff --git a/playfab-docs/player-progression/player-data/using-player-publisher-data.md b/playfab-docs/player-progression/player-data/using-player-publisher-data.md
index cd1b0abc1..f256faa24 100644
--- a/playfab-docs/player-progression/player-data/using-player-publisher-data.md
+++ b/playfab-docs/player-progression/player-data/using-player-publisher-data.md
@@ -16,7 +16,7 @@ Rewards usually involve *other* systems outside of player data, so this example
 
 ## Requirements
 
-- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A [PlayFab developer account](https://developer.playfab.com).
 - A player must sign into *both* titles using the same credentials. One approach is to use **Recoverable Credentials**, as described in our [Login Basics and Best Practices](../../identity/player-identity/login/login-basics-best-practices.md) tutorial. To add a **Recoverable** login to an anonymous account, see our [Account Linking](../../identity/player-identity/login/quickstart.md) tutorial.
 - This example requires a working knowledge of [CloudScript](../../live-service-management/service-gateway/automation/cloudscript/writing-custom-cloudscript.md):
   - Our example demonstrates basic data security to avoid player cheating. One could likewise use the server API on a custom game server, if the title makes use of them.
diff --git a/playfab-docs/player-progression/statistics/community-statistics.md b/playfab-docs/player-progression/statistics/community-statistics.md
index a5e5fa97c..5b4671419 100644
--- a/playfab-docs/player-progression/statistics/community-statistics.md
+++ b/playfab-docs/player-progression/statistics/community-statistics.md
@@ -12,13 +12,20 @@ ms.localizationpriority: medium
 
 # Community statistics
 
-Community statistics are a powerful tool to increase engagement and foster player investment in your game. By aggregating statistics at the game title level, developers can create shared goals and challenges that encourage collaboration among players. It transforms individual player actions into contributions toward community-wide objectives, driving sustained engagement as players work together to achieve collective milestones. Players feel their individual contributions matter to the larger community, strengthening their connection to both the game and fellow players.
+Community statistics are a powerful tool to increase engagement and foster player investment in your game. By aggregating statistics at the game title level, developers can create shared goals and challenges that encourage collaboration among players. This approach transforms individual player actions into contributions toward community-wide objectives, driving sustained engagement as players work together to achieve collective milestones. Players feel their individual contributions matter to the larger community, strengthening their connection to both the game and fellow players.
 
-For example, imagine implementing a global boss battle where the entire player base must collectively score 10 million eliminations within a week to unlock a special in-game event. As players see the community progress bar advancing with each of their contributions, they're motivated to help reach the goal. This creates a powerful feedback loop of investment and participation, especially when paired with real-time progress updates and milestone rewards along the way.
+For example, imagine implementing a global boss battle where the entire player base must collectively score 10 million eliminations within a week to unlock a special in-game event. As players see the community progress bar advancing with each of their contributions, they're motivated to help reach the goal. This behavior creates a powerful feedback loop of investment and participation, especially when paired with real-time progress updates and milestone rewards along the way.
 
-With PlayFab, you can easily manage community statistics by defining two statistics: one at the player level (aggregation source) and another at the game title level (aggregation destination). Updates made to player statistics are automatically aggregated to the title-level statistic. To retrieve the current community score, you read the statistics for the title entity.
+With PlayFab, you can easily manage community statistics by defining two statistics: one at the player level (aggregation source) and another at the title or group level (aggregation destination). Updates made to player statistics automatically aggregate to the destination statistic. To retrieve the current community score, you read the statistics for the destination entity.
 
-## Creating the source statistic definition 
+PlayFab supports two types of community statistics:
+
+- **Title-level**: Aggregates all player updates into a single title-wide statistic. Ideal for global goals shared across the entire player base.
+- **Group-level**: Aggregates player updates into a group entity statistic. Ideal for clan challenges, guild goals, or team-based objectives where subsets of players work toward a shared target.
+
+## Title-level community statistics
+
+### Creating the source statistic definition 
 
 First, create a statistic definition for players, which acts as the aggregation source:
 
@@ -48,7 +55,7 @@ CreateStatisticDefinitionRequest statDefinitionRequest = new CreateStatisticDefi
 PlayFabResult<PlayFab.LeaderboardsModels.EmptyResponse> createStatDefResult = await statsAPI.CreateStatisticDefinitionAsync(statDefinitionRequest);
 ```
 
-## Creating the destination statistic definition 
+### Creating the destination statistic definition 
 
 Next, create a statistic definition for the title, which acts as the aggregation destination. Specify the player statistic definition as the aggregation source for the title statistic definition:
 
@@ -73,13 +80,13 @@ CreateStatisticDefinitionRequest statDefinitionRequest = new CreateStatisticDefi
 
 PlayFabResult<PlayFab.LeaderboardsModels.EmptyResponse> createStatDefResult = await statsAPI.CreateStatisticDefinitionAsync(statDefinitionRequest);
 ```
-> **_NOTE:_** `EntityType` is set to `title` and `AggregationSources` is set to reference the statistic defined at the player level.
+> **_NOTE:_** Set `EntityType` to `title` and `AggregationSources` to reference the statistic defined at the player level.
 
-Once the community statistic is created, any updates made at the player level start getting aggregated at the title level. Only *new* updates are aggregated. If the source statistic has existed for a while, those historical values aren't backfilled at the title level.
+After you create the community statistic, any updates made at the player level start aggregating at the title level. The system aggregates only new updates. If the source statistic exists for a while, the system doesn't backfill those historical values at the title level.
 
-## Reading Community Statistics
+### Reading title community statistics
 
-To retrieve the current scores for the statistic at the title level, read the statistics for the Title entity:
+To get the current scores for the statistic at the title level, read the statistics for the title entity:
 
 ```C#
 // Use the PlayFabAuthenticationContext to call the API
@@ -98,12 +105,107 @@ GetStatisticsRequest request = new GetStatisticsRequest()
 PlayFabResult<GetStatisticsResponse> result = await statsAPI.GetStatisticsAsync(request); 
 ```
 
+## Group-level community statistics
+
+Group-level community statistics let you aggregate player actions within a specific group, such as a clan or guild. This aggregation is useful for scenarios like a clan challenge where members collectively work toward a shared goal.
+
+### Creating the destination statistic definition
+
+Create a statistic definition with `EntityType` set to `group`. Specify the player statistic definition as the aggregation source:
+
+```C#
+// Use the PlayFabAuthenticationContext to call the API
+PlayFabProgressionInstanceAPI statsAPI = new PlayFabProgressionInstanceAPI(context);
+CreateStatisticDefinitionRequest statDefinitionRequest = new CreateStatisticDefinitionRequest()
+{
+    Name = "groupCommunityStat",
+    AuthenticationContext = context,
+    EntityType = "group",
+    Columns = new List<StatisticColumn>()
+    {
+        new StatisticColumn()
+        {
+            Name = "Eliminations",
+            AggregationMethod = StatisticAggregationMethod.Sum,
+        },
+    },
+    AggregationSources = new string[] { "sourceStat" }
+};
+
+PlayFabResult<PlayFab.LeaderboardsModels.EmptyResponse> createStatDefResult = await statsAPI.CreateStatisticDefinitionAsync(statDefinitionRequest);
+```
+
+> [!NOTE]
+> The source statistic definition (player-level) is the same as the one used for title-level community statistics. You can reuse an existing source statistic definition.
+
+### Updating the source statistic
+
+When updating a player's source statistic for group-level aggregation, specify the target group entity in the `AggregationTargetEntityKeys` property of the `StatisticUpdate` object. This property tells PlayFab which group entity to aggregate the update to.
+
+```C#
+// Use the PlayFabAuthenticationContext to call the API
+PlayFabProgressionInstanceAPI statsAPI = new PlayFabProgressionInstanceAPI(context);
+
+UpdateStatisticsRequest request = new UpdateStatisticsRequest()
+{
+    AuthenticationContext = context,
+    Entity = new PlayFab.LeaderboardsModels.EntityKey()
+    {
+        Id = "<player entity id>",
+        Type = "title_player_account"
+    },
+    Statistics = new List<StatisticUpdate>()
+    {
+        new StatisticUpdate()
+        {
+            Name = "sourceStat",
+            Scores = new List<string> { "5" },
+            AggregationTargetEntityKeys = new List<PlayFab.LeaderboardsModels.EntityKey>()
+            {
+                new PlayFab.LeaderboardsModels.EntityKey()
+                {
+                    Id = "<group entity id>",
+                    Type = "group"
+                }
+            }
+        }
+    }
+};
+
+PlayFabResult<UpdateStatisticsResponse> result = await statsAPI.UpdateStatisticsAsync(request);
+```
+
+> [!IMPORTANT]
+> For title-level community statistics, `AggregationTargetEntityKeys` isn't required because the title is the default aggregation target. For group-level community statistics, you must specify the group entity key. Currently, you can specify only one entity key in `AggregationTargetEntityKeys`.
+
+### Reading group community statistics
+
+To get the current scores for the group community statistic, read the statistics for the group entity:
+
+```C#
+// Use the PlayFabAuthenticationContext to call the API
+PlayFabProgressionInstanceAPI statsAPI = new PlayFabProgressionInstanceAPI(context);
+
+GetStatisticsRequest request = new GetStatisticsRequest()
+{
+    AuthenticationContext = context,
+    Entity = new PlayFab.LeaderboardsModels.EntityKey()
+    {
+        Id = "<group entity id>",
+        Type = "group"
+    },
+};
+
+PlayFabResult<GetStatisticsResponse> result = await statsAPI.GetStatisticsAsync(request);
+```
+
 ## Restrictions
 
-* Currently, only one aggregation source can be specified for the community statistic.
-* Version configuration can't be specified for the community statistic. The version configuration specified for the source statistic applies to the community statistic as well.
-* The `EntityType` for the community statistic *must* be `title`.
-* `Last` aggregation can't be used for any of the columns.
+* You can specify only one aggregation source for the community statistic.
+* You can't specify version configuration for the community statistic. The version configuration you specify for the source statistic also applies to the community statistic.
+* The `EntityType` for the community statistic must be `title` or `group`.
+* You can't use `Last` aggregation for any of the columns.
+* You can specify only one entity key in `AggregationTargetEntityKeys` when updating the source statistic.
 
 ## See also
 
diff --git a/playfab-docs/player-progression/statistics/index.md b/playfab-docs/player-progression/statistics/index.md
index e7058074a..c2efbd05f 100644
--- a/playfab-docs/player-progression/statistics/index.md
+++ b/playfab-docs/player-progression/statistics/index.md
@@ -1,7 +1,7 @@
 ---
-title: Azure PlayFab Statistics overview
+title: PlayFab Statistics overview
 author: braulioal
-description: Learn about Azure PlayFab Statistics.
+description: Learn about PlayFab Statistics.
 ms.author: braulioal
 ms.date: 09/01/2024
 ms.topic: article
@@ -10,9 +10,9 @@ keywords: playfab, multiplayer, leaderboard, stats
 ms.localizationpriority: medium
 ---
 
-# Azure PlayFab Statistics overview
+# PlayFab Statistics overview
 
-Azure Playfab Statistics is a cross-platform service that enables the numerical representation of player activity within a title.
+PlayFab Statistics is a cross-platform service that enables the numerical representation of player activity within a title.
 
 ![PlayFab Stats Architecture](media/stats-relationship.png)
 
diff --git a/playfab-docs/player-progression/statistics/quickstart-statistics.md b/playfab-docs/player-progression/statistics/quickstart-statistics.md
index 3189dfbd5..2122ab6f4 100644
--- a/playfab-docs/player-progression/statistics/quickstart-statistics.md
+++ b/playfab-docs/player-progression/statistics/quickstart-statistics.md
@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 # Quickstart statistics
 
 In this guide, we're going to see how to set up the development environment for the Statistics service. We're also going
-to learn how to create a quick leaderboard from our website [Game Manager](https://developer.playfab.com/en-US/login).
+to learn how to create a quick leaderboard from our website [Game Manager](https://developer.playfab.com).
 
 ## Prerequisites
 
@@ -59,7 +59,7 @@ PlayFabSettings.staticSettings.DeveloperSecretKey = ""; // Change this to your t
 
 ## Creating a title and getting the secret key
 
-- Log in to https://playfab.com/
+- Log in to https://developer.playfab.com/
 - Create a title
     - Find the Title ID in the API Features section under settings.   
 - Generate secret key:
diff --git a/playfab-docs/player-progression/statistics/quota-statistics.md b/playfab-docs/player-progression/statistics/quota-statistics.md
index 7e34dabaf..fc75a393a 100644
--- a/playfab-docs/player-progression/statistics/quota-statistics.md
+++ b/playfab-docs/player-progression/statistics/quota-statistics.md
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 # Quota limits statistics
 
 The Statistic service is designed to align with PlayFab's pricing models, offering two distinct modes: 
-development and live. The development mode allows titles to test each feature and begin development. 
+development and live. The Development Mode allows titles to test each feature and begin development. 
 The live mode, on the other hand, is optimized for handling larger traffic loads typical of a live game.
 
 The following tables outline the limits for each of these modes:
diff --git a/playfab-docs/player-progression/statistics/statistics-with-playstream-and-telemetry.md b/playfab-docs/player-progression/statistics/statistics-with-playstream-and-telemetry.md
index e24d20018..4d014c181 100644
--- a/playfab-docs/player-progression/statistics/statistics-with-playstream-and-telemetry.md
+++ b/playfab-docs/player-progression/statistics/statistics-with-playstream-and-telemetry.md
@@ -34,7 +34,7 @@ Once you have enabled the event, you are now free to connect your events to what
 
 ## See Also
 
-- [`playfab.statistic.statistic_updated`](../../api-references/events/statistic-updated.md)
+- [`playfab.statistic.statistic_updated`](../../api-references/events/Statistics/statistic-updated.md)
 - [PlayStream Overview](../../data-analytics/ingest-data/playstream-overview.md)
 - [Leaderboards With PlayStream and Telemetry](../../community/leaderboards/leaderboards-with-playstream-and-telemetry.md)
 - [Telemetry Overview](../../data-analytics/ingest-data/telemetry-overview.md)
diff --git a/playfab-docs/pricing/Meters/meters.md b/playfab-docs/pricing/Meters/meters.md
index 9487c24c7..a484457dd 100644
--- a/playfab-docs/pricing/Meters/meters.md
+++ b/playfab-docs/pricing/Meters/meters.md
@@ -114,15 +114,15 @@ You can also use this [Party pricing calculator](https://playfab.com/party-calcu
 
 ### Matchmaking and Lobby
 
-PlayFab Matchmaking and Lobby are highly-customizable, proven solutions for building and orchestrating player groupings during a game session. Players can receive real-time notifications so they can quickly react when there are relevant updates in the Matchmaking or Lobby service. 
+PlayFab Matchmaking and Lobby are highly-customizable, proven solutions for building and orchestrating player groupings during a game session. Players can receive real-time messages so they can quickly react when there are relevant updates in the Matchmaking or Lobby service. 
 
 * **MatchmakingRequests**: One Matchmaking Request is metered for each call to a [Matchmaking API](/rest/api/playfab/multiplayer/matchmaking) endpoint. 
 * **LobbyRequests**: One Lobby Request is metered for each call to a [Lobby API](/rest/api/playfab/multiplayer/lobby) endpoint.
-* **Messages**: Metered by the number of message recipients. [Lobby and Matchmaking real-time notifications](../../multiplayer/lobby/lobby-and-matchmaking-real-time-notifications.md) are dispatched to subscribed clients upon important events such as receiving invites, joining and updating lobbies, or finding matches. 
+* **Messages**: Metered by the number of message recipients. [Lobby and Matchmaking real-time messages](../../multiplayer/lobby/lobby-and-matchmaking-real-time-messages.md) are dispatched to subscribed clients upon important events such as receiving invites, joining and updating lobbies, or finding matches. 
 
 ### Leaderboard
 
-Azure Playfab Leaderboards is a cross-platform service that allows to create a sorted list of players with the purpose
+PlayFab Leaderboards is a cross-platform service that allows to create a sorted list of players with the purpose
 of ranking them by scores.
 
 * **[Leaderboard Reads](leaderboard-meters.md)**: Metered by API calls that read from Leaderboards.
@@ -131,7 +131,7 @@ of ranking them by scores.
 
 ### Statistics
 
-Azure Playfab Statistics is a cross-platform service that allows to track the activity of players within the game.
+PlayFab Statistics is a cross-platform service that allows to track the activity of players within the game.
 
 * **[Statistics Reads](statistics-meters.md)**: Metered by API calls that read from Statistics. 
 * **[Statistics Writes](statistics-meters.md)**: Metered by API calls that write to Statistics. 
diff --git a/playfab-docs/pricing/Meters/profile-reads.md b/playfab-docs/pricing/Meters/profile-reads.md
index a0ddb336b..c1c804464 100644
--- a/playfab-docs/pricing/Meters/profile-reads.md
+++ b/playfab-docs/pricing/Meters/profile-reads.md
@@ -10,11 +10,11 @@ keywords: playfab, pricing
 ms.localizationpriority: medium
 ---
 
-# Profile Reads
+# Profile reads
 
 Profile includes any data stored related to the player profile, entity profile, character profile, groups, and inventory. Profile data is information that applies to an individual player, group of players, or items, and is stored as Key/Value Pairs (KVPs) by PlayFab. 
 
-The following APIs cause the Profile read meter to increment.
+The following APIs increment the profile read meter.
 
 ## Admin APIs
 
@@ -22,7 +22,7 @@ The following APIs cause the Profile read meter to increment.
     Checks the global count for the limited edition item.
 
 - [GetAllSegments](/rest/api/playfab/admin/play-stream/get-all-segments?view=playfab-rest&preserve-view=true)
-    Retrieves an array of player segment definitions. Results from this can be used in subsequent API calls such as GetPlayersInSegment which requires a Segment ID. While segment names can change the ID for that segment will not change.
+    Retrieves an array of player segment definitions. Results from this can be used in subsequent API calls such as GetPlayersInSegment which requires a Segment ID. While segment names can change the ID for that segment won't change.
 
 - [ExportMasterPlayerData](/rest/api/playfab/admin/account-management/export-master-player-data?view=playfab-rest&preserve-view=true)
     Exports all associated data of a master player account.
@@ -31,16 +31,16 @@ The following APIs cause the Profile read meter to increment.
     Retrieves the specified version of the title's catalog of virtual goods, including all defined properties.
 
 - [GetContentList](/rest/api/playfab/admin/content/get-content-list?view=playfab-rest&preserve-view=true)
-    List all contents of the title and get statistics such as size.
+    Lists all contents of the title and gets statistics such as size.
 
 - [GetDataReport](/rest/api/playfab/admin/player-data-management/get-data-report?view=playfab-rest&preserve-view=true)
     Retrieves a download URL for the requested report.
 
 - [GetPlayerSegments](/rest/api/playfab/admin/play-stream/get-player-segments?view=playfab-rest&preserve-view=true)
-    List all segments that a player currently belongs to at this moment in time.
+    Lists all segments that a player currently belongs to at this moment in time.
     
 - [GetPlayerTags](/rest/api/playfab/admin/play-stream/get-player-tags?view=playfab-rest&preserve-view=true)
-    Get all tags with a given Namespace (optional) from a player profile.
+    Gets all tags with a given Namespace (optional) from a player profile.
 
 - [GetPolicy](/rest/api/playfab/admin/authentication/get-policy?view=playfab-rest&preserve-view=true)
     Gets the requested policy.
@@ -55,7 +55,7 @@ The following APIs cause the Profile read meter to increment.
     Retrieves the set of items defined for the specified store, including all prices defined.
 
 - [GetTitleData](/rest/api/playfab/admin/title-wide-data-management/get-title-data?view=playfab-rest&preserve-view=true)
-    Retrieves the key-value store of custom title settings which can be read by the client.
+    Retrieves the key-value store of custom title settings that can be read by the client.
 
 - [GetUserAccountInfo](Retrieves the relevant details for a specified user, based upon a match against a supplied unique identifier)
     Retrieves the relevant details for a specified user, based upon a match against a supplied unique identifier.
@@ -64,34 +64,34 @@ The following APIs cause the Profile read meter to increment.
     Gets all bans for a user.
 
 - [GetUserData](/rest/api/playfab/admin/player-data-management/get-user-data?view=playfab-rest&preserve-view=true)
-    Retrieves the title-specific custom data for the user which is readable and writable by the client.
+    Retrieves the title-specific custom data for the user that's readable and writable by the client.
 
 - [GetUserInternalData](/rest/api/playfab/admin/player-data-management/get-user-internal-data?view=playfab-rest&preserve-view=true)
-    Retrieves the title-specific custom data for the user which cannot be accessed by the client.
+    Retrieves the title-specific custom data for the user, which can't be accessed by the client.
 
 - [GetUserInventory](/rest/api/playfab/admin/player-item-management/get-user-inventory?view=playfab-rest&preserve-view=true)
     Retrieves the specified user's current inventory of virtual goods
 
 - [GetUserPublisherData](/rest/api/playfab/admin/player-data-management/get-user-publisher-data?view=playfab-rest&preserve-view=true)
-    Retrieves the publisher-specific custom data for the user which is readable and writable by the client.
+    Retrieves the publisher-specific custom data for the user that's readable and writable by the client.
 
 - [GetUserPublisherInternalData](/rest/api/playfab/admin/player-data-management/get-user-publisher-internal-data?view=playfab-rest&preserve-view=true)
-    Retrieves the publisher-specific custom data for the user which cannot be accessed by the client.
+    Retrieves the publisher-specific custom data for the user that can't be accessed by the client.
 
 - [GetUserPublisherReadOnlyData](/rest/api/playfab/admin/player-data-management/get-user-publisher-read-only-data?view=playfab-rest&preserve-view=true)
-    Retrieves the publisher-specific custom data for the user which can only be read by the client.
+    Retrieves the publisher-specific custom data for the user that can only be read by the client.
 
 - [GetUserReadOnlyData](/rest/api/playfab/admin/player-data-management/get-user-read-only-data?view=playfab-rest&preserve-view=true)
-    Retrieves the title-specific custom data for the user which can only be read by the client.
+    Retrieves the title-specific custom data for the user that can only be read by the client.
 
 - [ListVirtualCurrencyTypes](/rest/api/playfab/admin/title-wide-data-management/list-virtual-currency-types?view=playfab-rest&preserve-view=true)
-    Retuns the list of all defined virtual currencies for the title
+    Returns the list of all defined virtual currencies for the title
 
 - [GetPlayerIdFromAuthToken](/rest/api/playfab/admin/account-management/get-player-id-from-auth-token?view=playfab-rest&preserve-view=true)
     Gets a player's ID from an auth token.
 
 - [GetPlayersInSegment](/rest/api/playfab/admin/play-stream/get-players-in-segment?view=playfab-rest&preserve-view=true)
-    Allows for paging through all players in a given segment. This API creates a snapshot of all player profiles that match the segment definition at the time of its creation and lives through the Total Seconds to Live, refreshing its life span on each subsequent use of the Continuation Token. Profiles that change during the course of paging will not be reflected in the results. AB Test segments are currently not supported by this operation.
+    Allows for paging through all players in a given segment. This API creates a snapshot of all player profiles that match the segment definition at the time of its creation and lives through the Total Seconds to Live, refreshing its life span on each subsequent use of the Continuation Token. Profiles that change during paging won't be reflected in the results. AB Test segments are currently not supported by this operation.
     
 - [GetExperiments](/rest/api/playfab/experimentation/experimentation/get-experiments?view=playfab-rest&preserve-view=true)
     Gets the details of all experiments for a title.
@@ -105,13 +105,13 @@ The following APIs cause the Profile read meter to increment.
 ## Client APIs
 
 - [GetAllUsersCharacters](/rest/api/playfab/client/characters/get-all-users-characters?view=playfab-rest&preserve-view=true)
-    Lists all of the characters that belong to a specific user. CharacterIds are not globally unique; characterId must be evaluated with the parent PlayFabId to guarantee uniqueness.
+    Lists all of the characters that belong to a specific user. CharacterIds aren't globally unique; characterId must be evaluated with the parent PlayFabId to guarantee uniqueness.
 
 - [GetCatalogItems](/rest/api/playfab/client/title-wide-data-management/get-catalog-items?view=playfab-rest&preserve-view=true)
     Retrieves the specified version of the title's catalog of virtual goods, including all defined properties.
 
 - [GetCharacterData](/rest/api/playfab/client/character-data/get-character-data?view=playfab-rest&preserve-view=true)
-    Retrieves the title-specific custom data for the character which is readable and writable by the client.
+    Retrieves the title-specific custom data for the character that's readable and writable by the client.
 
 - [GetCharacterInventory](/rest/api/playfab/client/player-item-management/get-character-inventory?view=playfab-rest&preserve-view=true)
     Retrieves the specified character's current inventory of virtual goods.
@@ -120,7 +120,7 @@ The following APIs cause the Profile read meter to increment.
     Retrieves a list of ranked characters for the given statistic, starting from the indicated point in the leaderboard.
 
 - [GetCharacterReadOnlyData](/rest/api/playfab/client/character-data/get-character-read-only-data?view=playfab-rest&preserve-view=true)
-    Retrieves the title-specific custom data for the character which can only be read by the client.
+    Retrieves the title-specific custom data for the character that can only be read by the client.
 
 - [GetCharacterStatistics](/rest/api/playfab/client/characters/get-character-statistics?view=playfab-rest&preserve-view=true)
     Retrieves the details of all title-specific statistics for the user.
@@ -132,7 +132,7 @@ The following APIs cause the Profile read meter to increment.
     Retrieves a list of ranked friends of the current player for the given statistic, centered on the requested PlayFab user. If PlayFabId is empty or null will return currently logged in user.
 
 - [GetFriendsList](/rest/api/playfab/client/friend-list-management/get-friends-list?view=playfab-rest&preserve-view=true)
-    Retrieves the current friend list for the local user, constrained to users who have PlayFab accounts. Friends from linked accounts (Facebook, Steam) are also included. You may optionally exclude some linked services' friends.
+    Retrieves the current friend list for the local user, constrained to users who have PlayFab accounts. Friends from linked accounts (Facebook, Steam) are also included. You can optionally exclude some linked services' friends.
 
 - [GetLeaderboard](/rest/api/playfab/client/player-data-management/get-leaderboard?view=playfab-rest&preserve-view=true)
     Retrieves a list of ranked users for the given statistic, starting from the indicated point in the leaderboard.
@@ -147,13 +147,13 @@ The following APIs cause the Profile read meter to increment.
     Retrieves a list of all of the user's characters for the given statistic.
 
 - [GetPaymentToken](/rest/api/playfab/client/player-item-management/get-payment-token?view=playfab-rest&preserve-view=true)
-    For payments flows where the provider requires playfab (the fulfiller) to initiate the transaction, but the client completes the rest of the flow. In the Xsolla case, the token returned here will be passed to Xsolla by the client to create a cart. Poll GetPurchase using the returned OrderId once you've completed the payment.
+    For payment flows where the provider requires PlayFab (the fulfiller) to initiate the transaction, but the client completes the rest of the flow. In the Xsolla case, the token returned here will be passed to Xsolla by the client to create a cart. Poll GetPurchase using the returned OrderId once you've completed the payment.
 
 - [GetPlayerProfile](/rest/api/playfab/client/account-management/get-player-profile?view=playfab-rest&preserve-view=true)
     Retrieves the player's profile.
 
 - [GetPlayerSegments](/rest/api/playfab/client/play-stream/get-player-segments?view=playfab-rest&preserve-view=true)
-    List all segments that a player currently belongs to at this moment in time.
+    Lists all segments that a player currently belongs to at this moment in time.
 
 - [GetPlayerStatistics](/rest/api/playfab/client/player-data-management/get-player-statistics?view=playfab-rest&preserve-view=true)
     Retrieves the indicated statistics (current version and values for all statistics, if none are specified), for the local player.
@@ -162,10 +162,10 @@ The following APIs cause the Profile read meter to increment.
     Retrieves the information on the available versions of the specified statistic.
 
 - [GetPlayerTags](/rest/api/playfab/client/play-stream/get-player-tags?view=playfab-rest&preserve-view=true)
-    Get all tags with a given Namespace (optional) from a player profile.
+    Gets all tags with a given Namespace (optional) from a player profile.
 
 - [GetPlayerTrades](/rest/api/playfab/client/trading/get-player-trades?view=playfab-rest&preserve-view=true)
-    Gets all trades the player has either opened or accepted, optionally filtered by trade status.
+    Gets all trades the player either opens or accepts, optionally filtered by trade status.
 
 - [GetPlayFabIDsFromFacebookIDs](/rest/api/playfab/client/account-management/get-playfab-ids-from-facebook-ids?view=playfab-rest&preserve-view=true)
     Retrieves the unique PlayFab identifiers for the given set of Facebook identifiers.
@@ -180,16 +180,16 @@ The following APIs cause the Profile read meter to increment.
     Retrieves the unique PlayFab identifiers for the given set of generic service identifiers. A generic identifier is the service name plus the service-specific ID for the player, as specified by the title when the generic identifier was added to the player account.
 
 - [GetPlayFabIDsFromGoogleIDs](/rest/api/playfab/client/account-management/get-playfab-ids-from-google-ids?view=playfab-rest&preserve-view=true)
-    Retrieves the unique PlayFab identifiers for the given set of Google identifiers. The Google identifiers are the IDs for the user accounts, available as "id" in the Google+ People API calls.
+    Retrieves the unique PlayFab identifiers for the given set of Google identifiers. The Google identifiers are the IDs for the user accounts, available as `id` in the Google+ People API calls.
 
 - [GetPlayFabIDsFromKongregateIDs](/rest/api/playfab/client/account-management/get-playfab-ids-from-kongregate-ids?view=playfab-rest&preserve-view=true)
-    Retrieves the unique PlayFab identifiers for the given set of Kongregate identifiers. The Kongregate identifiers are the IDs for the user accounts, available as "user_id" from the Kongregate API methods(ex: http://developers.kongregate.com/docs/client/getUserId).
+    Retrieves the unique PlayFab identifiers for the given set of Kongregate identifiers. The Kongregate identifiers are the IDs for the user accounts, available as `user_id` from the Kongregate API methods(for example, https://docs.kongregate.com/docs/concepts-handling-guests).
 
 - [GetPlayFabIDsFromNintendoSwitchDeviceIds](/rest/api/playfab/client/account-management/get-playfab-ids-from-nintendo-switch-device-ids?view=playfab-rest&preserve-view=true)
     Retrieves the unique PlayFab identifiers for the given set of Nintendo Switch identifiers.
 
 - [GetPlayFabIDsFromPSNAccountIDs](/rest/api/playfab/client/account-management/get-playfab-ids-from-psn-account-ids?view=playfab-rest&preserve-view=true)
-    Retrieves the unique PlayFab identifiers for the given set of PlayStation&#8482;Network identifiers.
+    Retrieves the unique PlayFab identifiers for the given set of PlayStation™ Network identifiers.
 
 - [GetPlayFabIDsFromSteamIDs](/rest/api/playfab/client/account-management/get-playfab-ids-from-steam-ids?view=playfab-rest&preserve-view=true)
     Retrieves the unique PlayFab identifiers for the given set of Steam identifiers. The Steam identifiers are the profile IDs for the user accounts, available as SteamId in the Steamworks Community API calls.
@@ -207,7 +207,7 @@ The following APIs cause the Profile read meter to increment.
     Retrieves a purchase along with its current PlayFab status. Returns inventory items from the purchase that are still active.
 
 - [GetSharedGroupData](/rest/api/playfab/client/shared-group-data/get-shared-group-data?view=playfab-rest&preserve-view=true)
-    Retrieves data stored in a shared group object, as well as the list of members in the group. Non-members of the group may use this to retrieve group data, including membership, but they will not receive data for keys marked as private. Shared Groups are designed for sharing data between a very small number of players, see [Using Shared Group Data](../../community/associations/groups/using-shared-group-data.md).
+    Retrieves data stored in a shared group object, and the list of members in the group. Non-members of the group use this to retrieve group data, including membership, but they won't receive data for keys marked as private. Shared Groups are designed for sharing data between a small number of players. For more information, see [Using Shared Group Data](../../community/associations/groups/using-shared-group-data.md).
 
 - [GetStoreItems](/rest/api/playfab/client/title-wide-data-management/get-store-items?view=playfab-rest&preserve-view=true)
     Retrieves the set of items defined for the specified store, including all prices defined.
@@ -219,51 +219,51 @@ The following APIs cause the Profile read meter to increment.
     Retrieves the user's PlayFab account details.
 
 - [LoginWithAndroidDeviceID](/rest/api/playfab/client/authentication/login-with-android-device-id?view=playfab-rest&preserve-view=true)
-    Signs the user in using the Android device identifier, returning a session identifier that can subsequently be used for API calls which require an authenticated user.
+    Signs the user in using the Android device identifier, returning a session identifier that can later be used for API calls that require an authenticated user.
 
 - [LoginWithCustomID](/rest/api/playfab/client/authentication/loginwithcustomid?view=playfab-rest&preserve-view=true)
-    Signs the user in using a custom unique identifier generated by the title, returning a session identifier that can subsequently be used for API calls which require an authenticated user
+    Signs the user in using a custom unique identifier generated by the title, returning a session identifier that can later be used for API calls that require an authenticated user
 
 - [LoginWithEmailAddress](/rest/api/playfab/client/authentication/login-with-email-address?view=playfab-rest&preserve-view=true)
-    Signs the user into the PlayFab account, returning a session identifier that can subsequently be used for API calls which require an authenticated user. Unlike most other login API calls, LoginWithEmailAddress does not permit the creation of new accounts via the CreateAccountFlag. Email addresses may be used to create accounts via RegisterPlayFabUser.
+    Signs the user into the PlayFab account, returning a session identifier that can later be used for API calls that require an authenticated user. Unlike most other login API calls, LoginWithEmailAddress doesn't permit the creation of new accounts via the CreateAccountFlag. Email addresses can be used to create accounts via RegisterPlayFabUser.
 
 - [LoginWithFacebook](/rest/api/playfab/client/authentication/login-with-facebook?view=playfab-rest&preserve-view=true)
-    Signs the user in using a Facebook access token, returning a session identifier that can subsequently be used for API calls which require an authenticated user.
+    Signs the user in using a Facebook access token, returning a session identifier that can later be used for API calls that require an authenticated user.
 
 - [LoginWithFacebookInstantGamesId](/rest/api/playfab/client/authentication/login-with-facebook-instant-games-id?view=playfab-rest&preserve-view=true)
-    Signs the user in using a Facebook Instant Games ID, returning a session identifier that can subsequently be used for API calls which require an authenticated user. Requires Facebook Instant Games to be configured.
+    Signs the user in using a Facebook Instant Games ID, returning a session identifier that can then be used for API calls that require an authenticated user. Requires Facebook Instant Games to be configured.
 
 - [LoginWithGameCenter](/rest/api/playfab/client/authentication/loginwithgamecenter?view=playfab-rest&preserve-view=true)
-    Signs the user in using an iOS Game Center player identifier, returning a session identifier that can subsequently be used for API calls which require an authenticated user.
+    Signs the user in using an iOS Game Center player identifier, returning a session identifier that can later be used for API calls that require an authenticated user.
 
 - [LoginWithGoogleAccount](/rest/api/playfab/client/authentication/login-with-game-center?view=playfab-rest&preserve-view=true)
-    Signs the user in using an iOS Game Center player identifier, returning a session identifier that can subsequently be used for API calls which require an authenticated user.
+    Signs the user in using an iOS Game Center player identifier, returning a session identifier that can later be used for API calls that require an authenticated user.
 
 - [LoginWithIOSDeviceID](/rest/api/playfab/client/authentication/login-with-google-account?view=playfab-rest&preserve-view=true)
-    Signs the user in using their Google account credentials.
+    Signs the user in by using their Google account credentials.
 
 - [LoginWithKongregate](/rest/api/playfab/client/authentication/login-with-kongregate?view=playfab-rest&preserve-view=true)
-    Signs the user in using a Kongregate player account.
+    Signs the user in by using a Kongregate player account.
 
 - [LoginWithNintendoSwitchDeviceId](/rest/api/playfab/client/authentication/login-with-nintendo-switch-device-id?view=playfab-rest&preserve-view=true)
-    Signs the user in using a Nintendo Switch Device ID, returning a session identifier that can subsequently be used for API calls which require an authenticated user.
+    Signs the user in using a Nintendo Switch Device ID, returning a session identifier that can then be used for API calls that require an authenticated user.
 
 - [LoginWithOpenIdConnect](/rest/api/playfab/client/authentication/login-with-openid-connect?view=playfab-rest&preserve-view=true)
-    Logs in a user with an Open ID Connect JWT created by an existing relationship between a title and an Open ID Connect provider.
+    Logs in a user by using an Open ID Connect JWT created by an existing relationship between a title and an Open ID Connect provider.
 
 - [LoginWithPlayFab](/rest/api/playfab/client/authentication/login-with-playfab?view=playfab-rest&preserve-view=true)
-    which require an authenticated user. Unlike most other login API calls, LoginWithPlayFab does not permit the creation of new accounts via the CreateAccountFlag. Username/Password credentials may be used to create accounts via RegisterPlayFabUser, or added to existing accounts using AddUsernamePassword.
+    which require an authenticated user. Unlike most other login API calls, `LoginWithPlayFab` doesn't permit the creation of new accounts via the `CreateAccountFlag`. Username/Password credentials can be used to create accounts via `RegisterPlayFabUser`, or added to existing accounts using `AddUsernamePassword`.
 
-- [LoginWithPSN](/rest/api/playfab/client/authentication/login-with-psn?view=playfab-rest&preserve-view=true)    Signs the user into the PlayFab account, returning a session identifier that can subsequently be used for API calls which require an authenticated user. Unlike most other login API calls, LoginWithPlayFab does not permit the creation of new accounts via the CreateAccountFlag. Username/Password credentials may be used to create accounts via RegisterPlayFabUser, or added to existing accounts using AddUsernamePassword.
+- [LoginWithPSN](/rest/api/playfab/client/authentication/login-with-psn?view=playfab-rest&preserve-view=true)    Signs the user into the PlayFab account, returning a session identifier that can then be used for API calls that require an authenticated user. Unlike most other login API calls, `LoginWithPlayFab` doesn't permit the creation of new accounts via the `CreateAccountFlag`. Username/Password credentials are used to create accounts via `RegisterPlayFabUser`, or added to existing accounts using `AddUsernamePassword`.
 
 - [LoginWithSteam](/rest/api/playfab/client/authentication/login-with-steam?view=playfab-rest&preserve-view=true)
-    Signs the user in using a Steam authentication ticket, returning a session identifier that can subsequently be used for API calls which require an authenticated user.
+    Signs the user in using a Steam authentication ticket, returning a session identifier that can later be used for API calls that require an authenticated user.
 
 - [LoginWithTwitch](/rest/api/playfab/client/authentication/login-with-twitch?view=playfab-rest&preserve-view=true)
-    Signs the user in using a Twitch access token.
+    Signs the user in by using a Twitch access token.
 
 - [LoginWithXbox](/rest/api/playfab/client/authentication/loginwithxbox?view=playfab-rest&preserve-view=true)
-    Signs the user in using a Xbox Live Token, returning a session identifier that can subsequently be used for API calls which require an authenticated user.
+    Signs the user in using an Xbox Live Token, returning a session identifier that can later be used for API calls that require an authenticated user.
 
 - [GetPlayerCombinedInfo](/rest/api/playfab/client/account-management/get-player-combined-info?view=playfab-rest&preserve-view=true)
     Retrieves all of the user's different kinds of info.
@@ -281,7 +281,7 @@ The following APIs cause the Profile read meter to increment.
     Gets information about a group and its roles.
 
 - [IsMember](/rest/api/playfab/groups/groups/is-member?view=playfab-rest&preserve-view=true)
-    Checks to see if an entity is a member of a group or role within the group.
+    Checks if an entity is a member of a group or role within the group.
 
 - [ListGroupApplications](/rest/api/playfab/groups/groups/list-group-applications?view=playfab-rest&preserve-view=true)
     Lists all outstanding requests to join a group.
@@ -318,22 +318,22 @@ The following APIs cause the Profile read meter to increment.
 ## Server APIs
 
 - [EvaluateRandomResultTable](/rest/api/playfab/server/player-item-management/evaluate-random-result-table?view=playfab-rest&preserve-view=true)
-    Returns the result of an evaluation of a Random Result Table - the ItemId from the game Catalog which would have been added to the player inventory, if the Random Result Table were added via a Bundle or a call to UnlockContainer.
+    Returns the result of an evaluation of a Random Result Table - the `ItemId` from the game Catalog that would have been added to the player inventory, if the Random Result Table were added via a Bundle or a call to UnlockContainer.
 
 - [GetAllSegments](/rest/api/playfab/server/play-stream/get-all-segments?view=playfab-rest&preserve-view=true)
-    Retrieves an array of player segment definitions. Results from this can be used in subsequent API calls such as GetPlayersInSegment which requires a Segment ID. While segment names can change the ID for that segment will not change.
+    Retrieves an array of player segment definitions. Results from this can be used in subsequent API calls such as GetPlayersInSegment which requires a Segment ID. While segment names can change the ID for that segment won't change.
 
 - [GetAllUsersCharacters](/rest/api/playfab/server/characters/get-all-users-characters?view=playfab-rest&preserve-view=true)
-    Lists all of the characters that belong to a specific user. CharacterIds are not globally unique; characterId must be evaluated with the parent PlayFabId to guarantee uniqueness.
+    Lists all of the characters that belong to a specific user. CharacterIds aren't globally unique; characterId must be evaluated with the parent PlayFabId to guarantee uniqueness.
 
 - [GetCatalogItems](/rest/api/playfab/server/title-wide-data-management/get-catalog-items?view=playfab-rest&preserve-view=true)
     Retrieves the specified version of the title's catalog of virtual goods, including all defined properties.
 
 - [GetCharacterData](/rest/api/playfab/server/character-data/get-character-data?view=playfab-rest&preserve-view=true)
-    Retrieves the title-specific custom data for the user which is readable and writable by the client.
+    Retrieves the title-specific custom data for the user that's readable and writable by the client.
 
 - [GetCharacterInternalData](/rest/api/playfab/server/character-data/get-character-internal-data?view=playfab-rest&preserve-view=true)
-    Retrieves the title-specific custom data for the user's character which cannot be accessed by the client.
+    Retrieves the title-specific custom data for the user's character that can't be accessed by the client.
 
 - [GetCharacterInventory](/rest/api/playfab/server/player-item-management/get-character-inventory?view=playfab-rest&preserve-view=true)
     Retrieves the specified character's current inventory of virtual goods.
@@ -347,7 +347,7 @@ The following APIs cause the Profile read meter to increment.
     Retrieves a list of ranked friends of the given player for the given statistic, starting from the indicated point in the leaderboard.
 
 - [GetFriendsList](/rest/api/playfab/server/friend-list-management/get-friends-list?view=playfab-rest&preserve-view=true)
-    Retrieves the current friends for the user with PlayFabId, constrained to users who have PlayFab accounts. Friends from linked accounts (Facebook, Steam) are also included. You may optionally exclude some linked services' friends.
+    Retrieves the current friends for the user with `PlayFabId`, constrained to users who have PlayFab accounts. Friends from linked accounts (Facebook, Steam) are also included. You might optionally exclude some linked services' friends.
 
 - [GetLeaderboard](/rest/api/playfab/server/player-data-management/get-leaderboard?view=playfab-rest&preserve-view=true)
     Retrieves a list of ranked users for the given statistic, starting from the indicated point in the leaderboard.
@@ -362,16 +362,16 @@ The following APIs cause the Profile read meter to increment.
     Retrieves a list of all of the user's characters for the given statistic.
 
 - [GetPlayerCombinedInfo](/rest/api/playfab/server/player-data-management/get-player-combined-info?view=playfab-rest&preserve-view=true)
-    Returns whatever info is requested in the response for the user. Note that PII (like email address, facebook id) may be returned. All parameters default to false.
+    Returns whatever info is requested in the response for the user. Note that personal date, like email address, facebook ID, might be returned. All parameters default to false.
 
 - [GetPlayerProfile](/rest/api/playfab/server/account-management/get-player-profile?view=playfab-rest&preserve-view=true)
     Retrieves the player's profile.
 
 - [GetPlayerSegments](/rest/api/playfab/server/play-stream/get-player-segments?view=playfab-rest&preserve-view=true)
-    List all segments that a player currently belongs to at this moment in time.
+    Lists all segments that a player currently belongs to at this moment in time.
 
 - [GetPlayersInSegment](/rest/api/playfab/server/play-stream/get-players-in-segment?view=playfab-rest&preserve-view=true)
-    Allows for paging through all players in a given segment. This API creates a snapshot of all player profiles that match the segment definition at the time of its creation and lives through the Total Seconds to Live, refreshing its life span on each subsequent use of the Continuation Token. Profiles that change during the course of paging will not be reflected in the results. AB Test segments are currently not supported by this operation.
+    Allows for paging through all players in a given segment. This API creates a snapshot of all player profiles that match the segment definition at the time of its creation and lives through the Total Seconds to Live, refreshing its life span on each subsequent use of the Continuation Token. Profiles that change during paging aren't reflected in the results. AB Test segments are currently not supported by this operation.
 
 - [GetPlayerStatistics](/rest/api/playfab/server/player-data-management/get-player-statistics?view=playfab-rest&preserve-view=true)
     Retrieves the current version and values for the indicated statistics, for the local player.
@@ -380,7 +380,7 @@ The following APIs cause the Profile read meter to increment.
     Retrieves the information on the available versions of the specified statistic.
 
 - [GetPlayerTags](/rest/api/playfab/server/play-stream/get-player-tags?view=playfab-rest&preserve-view=true)
-    Get all tags with a given Namespace (optional) from a player profile.
+    Gets all tags with a given Namespace (optional) from a player profile.
 
 - [GetPlayFabIDsFromFacebookIDs](/rest/api/playfab/server/account-management/getplayfabidsfromfacebookids?view=playfab-rest&preserve-view=true)
     Retrieves the unique PlayFab identifiers for the given set of Facebook identifiers.
@@ -413,7 +413,7 @@ The following APIs cause the Profile read meter to increment.
     Retrieves the associated PlayFab account identifiers for the given set of server custom identifiers.
 
 - [GetSharedGroupData](/rest/api/playfab/server/shared-group-data/get-shared-group-data?view=playfab-rest&preserve-view=true)
-    Retrieves data stored in a shared group object, as well as the list of members in the group. The server can access all public and private group data. Shared Groups are designed for sharing data between a very small number of players,  see [Using Shared Group Data](../../community/associations/groups/using-shared-group-data.md).
+    Retrieves data stored in a shared group object, and the list of members in the group. The server can access all public and private group data. Shared Groups are designed for sharing data between a small number of players.  For more information, see [Using Shared Group Data](../../community/associations/groups/using-shared-group-data.md).
 
 - [GetStoreItems](/rest/api/playfab/server/title-wide-data-management/get-store-items?view=playfab-rest&preserve-view=true)
     Retrieves the set of items defined for the specified store, including all prices defined, for the specified player.
@@ -431,30 +431,30 @@ The following APIs cause the Profile read meter to increment.
     Gets all bans for a user.
 
 - [GetUserData](/rest/api/playfab/server/player-data-management/get-user-data?view=playfab-rest&preserve-view=true)
-    Retrieves the title-specific custom data for the user which is readable and writable by the client.
+    Retrieves the title-specific custom data for the user that is readable and writable by the client.
 
 - [GetUserInternalData](/rest/api/playfab/server/player-data-management/get-user-internal-data?view=playfab-rest&preserve-view=true)
-    Retrieves the title-specific custom data for the user which cannot be accessed by the client.
+    Retrieves the title-specific custom data for the user that can't be accessed by the client.
 
 - [GetUserInventory](/rest/api/playfab/server/player-item-management/get-user-inventory?view=playfab-rest&preserve-view=true)
     Retrieves the specified user's current inventory of virtual goods.
 
 - [GetUserPublisherData](/rest/api/playfab/server/player-data-management/get-user-publisher-data?view=playfab-rest&preserve-view=true)
-    Retrieves the publisher-specific custom data for the user which is readable and writable by the client.
+    Retrieves the publisher-specific custom data for the user that is readable and writable by the client.
 
 - [GetUserPublisherInternalData](/rest/api/playfab/server/player-data-management/getuserpublisherinternaldata?view=playfab-rest&preserve-view=true)
-    Retrieves the publisher-specific custom data for the user which cannot be accessed by the client.
+    Retrieves the publisher-specific custom data for the user that can't be accessed by the client.
 
 - [GetUserPublisherReadOnlyData](/rest/api/playfab/server/player-data-management/get-user-publisher-internal-data?view=playfab-rest&preserve-view=true)
 
 - [GetUserReadOnlyData](/rest/api/playfab/server/player-data-management/update-user-read-only-data?view=playfab-rest&preserve-view=true)
-    Updates the title-specific custom data for the user which can only be read by the client.
+    Updates the title-specific custom data for the user that can only be read by the client.
 
 - [LoginWithServerCustomId](/rest/api/playfab/server/authentication/login-with-server-custom-id?view=playfab-rest&preserve-view=true)
-    Securely login a game client from an external server backend using a custom identifier for that player. Server Custom ID and Client Custom ID are mutually exclusive and cannot be used to retrieve the same player account.
+    Securely login a game client from an external server backend using a custom identifier for that player. Server Custom ID and Client Custom ID are mutually exclusive and can't be used to retrieve the same player account.
 
 - [LoginWithXbox](/rest/api/playfab/server/authentication/login-with-xbox?view=playfab-rest&preserve-view=true)
-    Signs the user in using a Xbox Live Token from an external server backend, returning a session identifier that can subsequently be used for API calls which require an authenticated user.
+    Signs the user in using an Xbox Live Token from an external server backend, returning a session identifier that can later be used for API calls that require an authenticated user.
 
 - [LoginWithXboxId](/rest/api/playfab/server/authentication/login-with-xbox-id?view=playfab-rest&preserve-view=true)
-    Signs the user in using an Xbox ID and Sandbox ID, returning a session identifier that can subsequently be used for API calls which require an authenticated user.
+    Signs the user in using an Xbox ID and Sandbox ID, returning a session identifier that can later be used for API calls that require an authenticated user.
diff --git a/playfab-docs/pricing/Meters/profile-writes.md b/playfab-docs/pricing/Meters/profile-writes.md
index aa0fae355..0ffc81b93 100644
--- a/playfab-docs/pricing/Meters/profile-writes.md
+++ b/playfab-docs/pricing/Meters/profile-writes.md
@@ -175,7 +175,7 @@ The following APIs cause the Profile writes meter to increment.
     Adds users to the set of those able to update both the shared data, as well as the set of users in the group. Only users in the group (and the server) can add new members. Shared Groups are designed for sharing data between a very small number of players, see [Using Shared Group Data](../../community/associations/groups/using-shared-group-data.md).
 
 - [AddUsernamePassword](/rest/api/playfab/client/account-management/addusernamepassword?)
-    Adds playfab username/password auth to an existing account created via an anonymous auth method, e.g. automatic device ID login.
+    Adds PlayFab username/password auth to an existing account created via an anonymous auth method, e.g. automatic device ID login.
 
 - [AndroidDevicePushNotificationRegistration](/rest/api/playfab/client/platform-specific-methods/androiddevicepushnotificationregistration?)
     Registers the Android device to receive push notifications
@@ -247,7 +247,7 @@ The following APIs cause the Profile writes meter to increment.
     Registers the iOS device to receive push notifications
 
 - [RegisterPlayFabUser](/rest/api/playfab/client/authentication/registerplayfabuser?)
-    Registers a new Playfab user account, returning a session identifier that can subsequently be used for API calls which require an authenticated user. You must supply either a username or an email address.
+    Registers a new PlayFab user account, returning a session identifier that can subsequently be used for API calls which require an authenticated user. You must supply either a username or an email address.
 
 - [RemoveContactEmail](/rest/api/playfab/client/account-management/removecontactemail?)
     Removes a contact email from the player's profile.
diff --git a/playfab-docs/pricing/account-upgrades.md b/playfab-docs/pricing/account-upgrades.md
index 3bd95dd57..7ac2d665a 100644
--- a/playfab-docs/pricing/account-upgrades.md
+++ b/playfab-docs/pricing/account-upgrades.md
@@ -1,5 +1,5 @@
 ---
-title: Account Upgrades
+title: Account upgrades
 author: nathankong-microsoft
 description: Describes how to upgrade an account in the new Game Manager experience.
 ms.author: jenelleb
@@ -10,16 +10,16 @@ keywords: playfab, pricing, upgrade, upgrades, launch, live
 ms.localizationpriority: medium
 ---
 
-# Account Upgrades
+# Account yupgrades
 Customers can upgrade their account plan using the self-serve plans experience found in Game Manager.
 
-## Account Plans 
+## Account plans 
 A PlayFab account has five plan options:
-1. **FREE TO START :** This plan has no cost to the customer. Studios that belong to free accounts may only contain titles that are in [development-mode.md](development-mode.md). Once a title reaches its development mode limits, it must be launched by upgrading to a paid plan. To learn how to launch a title, see Title Launches.Once a title reaches its development mode limits, it must be launched by upgrading to a paid plan. To learn how to launch a title, see Title Launches.
-2. **PAY-AS-YOU-GO :** This paid plan has no monthly base rate. Accounts are only charged for their monthly consumption for live titles. 
-3. **STANDARD :** This paid plan has a monthly base rate and private support options ([PaidTechnicalSupport.md](Support.md)). This plan comes with included meter usage amounts that live titles associated with the account may access. Once the included meter amounts have been used, the account will be charged for additional consumption.
-4. **PREMIUM :** This paid plan has a monthly base rate and private support options ([PaidTechnicalSupport.md](Support.md)). This plan comes with more included meter usage than the Standard plan. Once the included meter amounts have been used, the account will be charged for additional consumption.
-5. **ENTERPRISE :** An Enterprise account has a monthly base rate and private support channels that offer 24/7 assistance. This plan comes with more included meter usage than the Premium plan. Once the included meter amounts have been used, the account will be charged for additional consumption. An account can upgrade to an Enterprise plan through contacting the [https://playfab.com/contact/](https://playfab.com/contact/) .
+1. **FREE TO START:** This plan has no cost to the customer. Once a title reaches its Development Mode limits, it must be launched by upgrading to a paid plan. To learn how to launch a title, see Title Launches.
+2. **PAY-AS-YOU-GO:** This paid plan has no monthly base rate. Accounts are only charged for their monthly consumption for live titles. 
+3. **STANDARD:** This paid plan has a monthly base rate and private support options ([PaidTechnicalSupport.md](Support.md)). This plan comes with included meter usage amounts that live titles may access. Once the included meter amounts have been used, the account will be charged for additional consumption.
+4. **PREMIUM:** This paid plan has a monthly base rate and private support options ([PaidTechnicalSupport.md](Support.md)). This plan comes with more included meter usage than the Standard plan. Once the included meter amounts have been used, the account will be charged for additional consumption.
+5. **ENTERPRISE:** An Enterprise account has a monthly base rate and private support channels that offer 24/7 assistance. This plan comes with more included meter usage than the Premium plan. Once the included meter amounts have been used, the account will be charged for additional consumption. 
 
 The base rate's included consumption is cumulative across titles linked to an account.
 
@@ -27,15 +27,15 @@ The base rate's included consumption is cumulative across titles linked to an ac
 > All PlayFab account plans adhere to the [https://playfab.com/terms/](https://playfab.com/terms/).
 
 
-## Understanding the Account-Studio-Title Relationship
+## Understanding the account-studio-title relationship
 An account is linked to one Studio and a Studio may be linked to many titles. Upgrades are executed at the account level and launches are executed at the Title level.
 ![Image: Account-Studio-Title Relationship](pricingV2-media/AccountStudioTitleRelationship.png)
 
 
-## Changing Plans
+## Changing plans
 You can change your account's plan via Game Manager using the **Plan Recommendation** and **Plan Selection** pages. Plan changes are scheduled for the beginning of the next billing period.
 
-### Upgrading from Free to Start
+### Upgrading from free-to-start
 You can upgrade your account plan at any time on the **My Studios and Titles** page. Use the following steps to upgrade your account from Free to Start. Upgrading an account will upgrade all studios owned by the account.
 
 1. Log in to [http://developer.playfab.com/](http://developer.playfab.com/).
@@ -52,7 +52,7 @@ You can upgrade your account plan at any time on the **My Studios and Titles** p
 
 After an account is upgraded, the provided payment instrument is charged a monthly base rate per account in addition to usage charges for launched titles.
 
-### Upgrading and Downgrading
+### Upgrading and downgrading
 You can upgrade or downgrade your account plan at any time on the Studio Settings page of any studio owned by the account. Use the following steps to change your account's plan. Changing the account plan will change all studios owned by the account.
 
 1. Log in to [http://developer.playfab.com/](http://developer.playfab.com/).
@@ -67,11 +67,11 @@ You can upgrade or downgrade your account plan at any time on the Studio Setting
 
 6. Once you upgrade your account, on the **Studio Settings** page under the Studio Plan section, you will see your current plan as well as the scheduled plan.
 
-### Upgrading to Enterprise
+### Upgrading to enterprise
 
 Any account is eligible to upgrade to an Enterprise account plan. The PlayFab team must be contacted to upgrade to an Enterprise account plan. [https://playfab.com/contact/](https://playfab.com/contact/)
 
-### Cancel All Charges and Delete Your Studio 
+### Cancel all charges and delete Your sFtudio 
 
 Before proceeding with deletion, consider the following recommended (but optional) actions to ensure a smooth transition and avoid any unintended loss: 
 
diff --git a/playfab-docs/pricing/billingDetails.md b/playfab-docs/pricing/billingDetails.md
index 7b87dc633..3f3ae7cc0 100644
--- a/playfab-docs/pricing/billingDetails.md
+++ b/playfab-docs/pricing/billingDetails.md
@@ -14,12 +14,12 @@ ms.localizationpriority: medium
 
 Admin or billing permissions are required to view the **Billing Summary** page.
 
-The billing details page provides a daily snapshot of your month-to-date estimate charges. Use the information on this page to estimate what your bill will look like at the end of the month and view past months to understand trends and comparisons. The billing details page helps you determine what the biggest consumers of your metered resources are and gives you information that you can use to reduce your charges in subsequent months.
+The billing details page provides a daily snapshot of your month-to-date estimate charges. Use the information on this page to estimate what your bill looks like at the end of the month and view past months to understand trends and comparisons. The billing details page helps you determine what the biggest consumers of your metered resources are and gives you information that you can use to reduce your charges in subsequent months.
 
 > [!NOTE]
 > The values reported on the billing summary page are an **estimate** of usage and associated costs for an account. The amount shown might not depict the final invoice amount charged to an account.
 
-To view the billing details page for your studio navigate to the My Studios and Titles page. Click the ellipsis on the right side of your studio, and then selecting the Billing summary option in the drop-down.
+To view the billing details page for your studio, navigate to the My Studios and Titles page. Click the ellipsis on the right side of your studio, and then selecting the Billing summary option in the drop-down.
 
 ## Billing Summary Overview
 
@@ -30,9 +30,9 @@ To view the billing details page for your studio navigate to the My Studios and
 2. **Selected Month**
    * This is the month that the listed consumption and charges cover. Use the Month Filter (8) to change the selected month.
 3. **Month-To-Date (MTD) Estimated Charge**
-   * This is the daily snapshot of estimated total charges that your studio has accrued during the selected calendar month.
+   * This is the daily snapshot of estimated total charges that your studio accrues during the selected calendar month.
 4. **The Fine Print**
-    * Only use the **Billing Summary** page as an estimate for your month-to-date charges. Some meters have a 48+ hour delay and the **Billing Summary** page does not include all chargeable items (For example, Add-ons). On the first of the current month, you can view the final estimate for the previous month's charges (excluding taxes and delayed meter charges), and on the second of the current month, you can view the first estimate for the current month's usage and costs.
+    * Only use the **Billing Summary** page as an estimate for your month-to-date charges. Some meters have a 48+ hour delay and the **Billing Summary** page doesn't include all chargeable items (For example, Add-ons). On the first of the current month, you can view the final estimate for the previous month's charges (excluding taxes and delayed meter charges), and on the second of the current month, you can view the first estimate for the current month's usage and costs.
 5. **.csv Download**
    * You can download the **Billing Summary** view to .csv for further analysis. The "Download Summary" provides the same granularity as the **Billing Summary** page. The "Download daily" provides the daily breakdown of usage.
    > [!NOTE]
@@ -40,19 +40,19 @@ To view the billing details page for your studio navigate to the My Studios and
 6. **Contact Information**
    * This is the contact information we use to send you an invoice. This can be changed by navigating to the **Billing Information** page.
 7. **Title Filter**
-   * Use the **Title** filter to understand consumption and apportioned cost by title. Namespace events are counted in the "All" calculation, but aren't currently available to drill down (as they aren't tied to a title). Development mode titles are not charged to the account and do not display cost data.
+   * Use the **Title** filter to understand consumption and apportioned cost by title. Namespace events are counted in the "All" calculation, but aren't currently available to drill down (as they aren't tied to a title). Development Mode titles aren't charged to the account and don't display cost data.
 8. **Month Filter**
    * Use this filter to choose the month to display. All billing summary data from the time the account was updated to usage-based pricing is visible through the billing summary page.
 9. **Meter Category**
    * The **Pay as you Go** section buckets the full set of meters into logical categories. You can find the full set of meters in [meter documentation](Meters/meters.md).
 10. **Meter**
-    * This is a billable meter that at least one of your titles is consuming. You only see meters that you are using. For a full list of meters, see [meter documentation](Meters/meters.md).
+    * This is a billable meter that at least one of your titles is consuming. You only see meters that you're using. For a full list of meters, see [meter documentation](Meters/meters.md).
 11. **Usage**
-    * This column provides estimated, rounded usage (for readability purposes) for each tier/SKU, as well as the aggregated amount. To see the exact usage, download the .csv (5).
+    * This column provides estimated, rounded usage (for readability purposes) for each tier/SKU, and the aggregated amount. To see the exact usage, download the .csv (5).
 12. **Rate**
-    * This column provides the rounded rates (for readability purposes) for each tier/SKU. To see the exact rates, please download the .csv (5).
+    * This column provides the rounded rates (for readability purposes) for each tier/SKU. To see the exact rates, download the .csv (5).
 13. **Cost**
-    * This column provides the estimated cost for each tier/SKU, as well as the aggregated amount.
+    * This column provides the estimated cost for each tier/SKU, and the aggregated amount.
 14. **Description**
     * Each meter provides a brief description in the billing summary page. You can find a  more detailed explanation of the meters in [meter documentation](Meters/meters.md).
 
@@ -62,18 +62,18 @@ To view the billing details page for your studio navigate to the My Studios and
 
 The base rate charge includes:
 
-1. **Meter usage** amounts that are specified at [PlayFab pricing](https://www.playfab.com/pricing). Once meter usage across live titles associated to an account has surpassed the included amounts (above), an account's live title usage will be charged based on the meter rates found at [PlayFab pricing](https://www.playfab.com/pricing) (also listed under the "Rate" column on the Billing Summary page). These costs are referred to as "Pay-As-You-Go" charges.
+1. **Meter usage** amounts that are specified at [PlayFab pricing](https://www.playfab.com/pricing). Once meter usage across live titles associated to an account surpasses the included amounts (above), an account's live title usage is charged based on the meter rates found at [PlayFab pricing](https://www.playfab.com/pricing) (also listed under the "Rate" column on the Billing Summary page). These costs are referred to as "Pay-As-You-Go" charges.
 
     > [!NOTE]
-    > Titles in [Development Mode](development-mode.md) are not counted against included base rate usage.
+    > Titles in [Development Mode](development-mode.md) aren't counted against included base rate usage.
 
 2. **[Technical support](Support.md)** that is determined by the [account level](account-upgrades.md).
 
 ## Additional Section Definitions
 
-**Pay-As-You-Go Charges:** Pay-As-You-Go charges are the cost of individual meter usage per title in an account that exceed usage amounts that are part of the plan. The per-meter prices can be found at [PlayFab pricing](https://www.playfab.com/pricing) or under the "Rate" column on the billing summary page.
+**Pay-As-You-Go Charges:** Pay-As-You-Go charges are the cost of individual meter usage per title in an account that exceeds usage amounts that are part of the plan. The per-meter prices can be found at [PlayFab pricing](https://www.playfab.com/pricing) or under the "Rate" column on the billing summary page.
 
-**Additional Charges:** Additional charges include any charges not directly tied to the meter-usage pricing plan. For example, charges for MPS and Add-Ons may appear in the additional charges section.
+**Additional Charges:** Additional charges include any charges not directly tied to the meter-usage pricing plan. For example, charges for Multiplayer Servers (MPS) and Add-ons may appear in the additional charges section.
 
 ## Learn More
 
diff --git a/playfab-docs/pricing/consumption-best-practices.md b/playfab-docs/pricing/consumption-best-practices.md
index 5719a451a..0bb20ecb1 100644
--- a/playfab-docs/pricing/consumption-best-practices.md
+++ b/playfab-docs/pricing/consumption-best-practices.md
@@ -1,5 +1,5 @@
 ---
-title: PlayFab Consumption Best Practices
+title: PlayFab consumption best practices
 author: joannaleecy
 description: Describes best practices for managing your costs in PlayFab.
 ms.author: jenelleb
@@ -10,11 +10,11 @@ keywords: playfab, pricing
 ms.localizationpriority: medium
 ---
 
-# PlayFab Consumption: Best Practices
+# PlayFab consumption: best practices
 
 With PlayFab's consumption-based pricing model, you only pay for the actual service usage of your titles. But this raises an obvious question: how do you best optimize those titles to save money, while still implementing all the features you need? In this document, we dive into those details, and talk about best practices that will help you to plan ahead.
 
-Before you move your titles from Development Mode to Live, you can review the meter information in the Billing Summary tab of the Game Manager. A good starting practice is to periodically confirm the meters by using a separate title to check meter usage for real-world-player activity. You can have multiple titles in Development Mode, so that you can create titles on the fly as you reach development stages where you want to checkpoint that usage, and then delete those titles after you're done.
+Before you move your titles from Development Mode to Live, you can review the meter information in the Billing Summary tab of the Game Manager.
 
 There are six consumption meters: Events, Profile, Content and Configuration, CloudScript, Insights, and Multiplayer Services. The best way to begin optimizing a title is to look at each of the meters that it uses and see how it accumulates over time. This allows you to quickly derive some obvious improvements. For more information about meters, see [Pricing Meters](Meters/meters.md).
 
@@ -42,7 +42,7 @@ For more information about the specific API calls that result in "spin" on these
 
 We'll start with User Data and Statistics, since their usage patterns are similar, and then we'll talk about player inventory management.
 
-### Data and Statistics
+### Data and statistics
 
 When evaluating your usage of User Data, the same approximation logic as for events applies–each 1 KB increases the meter count by 1–though keep in mind that each "element" of a call should be thought of as distinct for purposes of this calculation. Each key value pair in a call to update User Data is counted separately. For reads, this 1 KB calculation applies to the total data returned, regardless of the number of key value pairs. This means that writing 10 keys of 100 bytes each is 10 "ticks" of the profile write meter, since each key value pair write is a minimum of 1 KB, while a read of those 10 keys is 1 "tick", since it's a total of 1 KB. For more specific details on the usages, see [Pricing meters](Meters/meters.md).
 
@@ -54,7 +54,7 @@ If you're coming from PC or console development–especially single player games
 
 How do you determine the optimal frequency of reads and writes? Two of the most common concerns of developers who want to update data and statistics more frequently are protecting against cheating, and having timely information stored server-side either for player-to-player interactions or to prevent data loss if the game exits unexpectedly.
 
-### Cheat Protection
+### Cheat protection
 
 While it might seem like you need to constantly update your backend data to ensure essential security, frequent updates are rarely necessary if your game doesn't require fully server-authoritative control of the session. To start, the fundamental question is how much security that you actually need.
 
@@ -72,7 +72,7 @@ For games with more real-time requirements, such as needing to update the server
 
 This is the model used by real-time multiplayer games. It's also a valid technique for single-player titles that require server-authoritative checks, though if that frequency is only a few times a minute per player, Azure Functions CloudScript could be the better option. The total CloudScript cost is easy to compute. It's the total gigabyte-seconds that you consume, with a minimum of 128 MB and 100 ms per execution, plus the normal calculations for any other service API calls the script uses. For example, if you have a total memory footprint, between your script code and variable usage in the script, of 250 MB, you would need to run that script for 4 seconds (across multiple users, most likely) to get to 1 GB/s. And within that script code, if you read or write Entity Objects, Title Data, User Data, etc., you'll need to calculate the spin that each of those calls has on the profile meters. Since hosted game server costs are dependent on how many servers you're running, and that in turns depends upon how many players can be hosted on a server at a time, it's not necessarily trivial to determine where the break-even point is between the two. But if you find that you need to call your scripts at a high frequency, and need to read and write data from the service each time, it's very likely that a game server solution is the better way to go.
 
-### Data Timeliness
+### Data timeliness
 
 One common theme we've heard among developers with high profile write rates is that they're concerned about the player losing progress. If the player exits the game before it can save and the local state can't be used the next time the game is played, or that state needs to travel between devices, you want to have the PlayFab-stored state information for the player be as up-to-date as possible.
 
@@ -93,7 +93,7 @@ For competition, [Leaderboards](../community/leaderboards/index.md) are an ideal
 
 For games that use cross-player data directly in the session, the most common optimization is to read only the information about the few specific players with whom the local player is interacting. For real-time action games, this is usually done on the server hosting the session. For others–such as games where players can attack each others' bases–the most common approaches are to either read all that data onto the local device or to send the local player only the subset of the other player's data that the local player should know. Games that do the former use server-side logic to evaluate the final results the client sends. Games that do the latter update the data iteratively over the course of the session with more data, when the local player should have access to it. But even then, they also use server-side logic to evaluate the final results. Again, the tipping point in deciding whether this should be done through script or on a hosted server is down to frequency. If it's more than a few times a minute, you're better off using a hosted server for the portion of the session that requires that data.
 
-## Economy and Inventory
+## Economy and inventory
 
 Inventory, and economy in general, requires a different approach. There's no avoiding the fact that if a player is giving up something of real (money) or perceived (virtual currency or consumable containers) value, they have an implicit expectation that the transaction will be honored. For any game with in-app purchases, an increment to the profile meter for a purchase made by the player with real-world currency is a trivial cost. In many types of games, inventory updates are infrequent enough to pose little concern for greatly increasing your overall usage. But for those with more frequent inventory updates–even if you don't have in-game monetization–there are optimization tricks to help reduce your costs.
 
@@ -103,7 +103,7 @@ When it comes to games that have higher rates of update to inventory, we're back
 
 By their nature, certain game genres, such as collectible card games, do need to update the player inventory at a somewhat higher rate. But even here, there are still opportunities to aggregate inventory changes and reduce the total usage on the profile meters. For example, in games that use [drop tables](../economy-monetization/economy/tutorials/drop-tables.md), the design frequently employs a container that has one or more "pulls" from each of several different drop tables. Typically, if these pulls are only an occasional action the incremental cost is small enough to not cause concern. But if players can collect many of those containers, and open multiples in a short period of time, you could provide an "open N" or even "open all" option. In that case, you use [PlayFab CloudScript using Azure Functions](../live-service-management/service-gateway/automation/cloudscript-af/index.md) or your custom game server to either query [Player Item Management - Get Random Result Tables](xref:titleid.playfabapi.com.server.playeritemmanagement.getrandomresulttables) for the set of drop tables or call [Player Item Management - Evaluate Random Result Table](xref:titleid.playfabapi.com.server.playeritemmanagement.evaluaterandomresulttable) without generating the inventory items. You could then update the player inventory far more efficiently by only adding instances where needed, and then updating the count of item stacks for the rest.
 
-## Content and Configuration
+## Content and configuration
 
 Where the Profile is primarily about the player, Content and Configuration is primarily about the title. A number of title-level components, such as Push Notifications, email services, and Title News are all included in this meter. In addition though, this is the meter used to track on Entity File usage. Similarly, requests for the URLs for uploading and downloading CDN files are tracked on this meter, though it's important to clarify that CDN costs are separate, and are billed based on the total gigabytes downloaded as described in [Content Delivery Network (CDN)](../data-analytics/legacy/content-delivery-network/index.md). The calculation of the Content and Configuration read and storage meters are similar to the Profile meters in that they're based on the size of the data, though obviously the units are significantly larger than 1 KB. For the Content and Configuration write meter, it's solely based on the total number of write operations, with each incrementing the meter by 1.
 
@@ -129,7 +129,7 @@ For information about Insights and how to use it, see [What is PlayFab Insights]
 
 For information about Insight best practices, see [Best Practices & FAQ](../data-analytics/legacy/insights/best-practices.md).
 
-## Multiplayer Services
+## Multiplayer services
 
 This one is the simplest of all, since the pricing is completely unchanged. In short, hosted [Multiplayer Servers](../multiplayer/servers/index.md) and the [Party service](../multiplayer/networking/index.md) have always been charged on a usage basis.
 
@@ -137,9 +137,7 @@ For hosted game servers specifically, you can minimize your costs by optimizing
 
 If low ping times are important on those servers, you can choose which regions to run the servers. For most games, the largest concentrations of players are limited to certain key regions, but if you have a widely dispersed player population—particularly when you're in the long tail of your game—you'll need to weigh the cost of running servers in every region near your players versus the impact of longer ping times on the subset of players in areas with few players. One thing that can help with that is to make sure you're using our [QOS service](../multiplayer/servers/using-qos-beacons-to-measure-player-latency-to-azure.md) to choose which regions to put players in, and then determine what your cut-off is for the minimum number of players you need playing in a region for it to be viable.
 
-To help get you through development without running up costs, we provide a significant number of free server hours in our hosting service, and our Party service is free for all Development Mode titles. It's also worth calling out that our Party service is also free for all use with Xbox Live signed-in players, and for titles in our Standard, Premium, and Enterprise tiers, we provide a generous allowance of connectivity, voice, and Cognitive Services (voice transcription and translation) at no additional cost, to help with 21st Century Communications and Video Accessibility Act (CVAA) compliance.
-
-## Managing your Live Game
+## Managing your live game
 
 That covers the fundamentals of the meters, but what should you be thinking about once your title is live? Managing your community of players primarily involves analytics ([Insights](#insights), in the section above) and updates to Content and Configuration. In addition, most games need to engage with players outside their normal interactions
 with the game itself. From re-engagement campaigns (to entice players to come back), to community rewards for meta-game activity, and even to thanking players for their own community work outside the game, a common practice these days is to use [LiveOps](https://playfab.com/liveops/) techniques to keep players highly engaged.
diff --git a/playfab-docs/pricing/development-mode.md b/playfab-docs/pricing/development-mode.md
index 6aaaee5c5..8f27395ce 100644
--- a/playfab-docs/pricing/development-mode.md
+++ b/playfab-docs/pricing/development-mode.md
@@ -1,7 +1,7 @@
 ---
-title: Development mode
+title: Development Mode
 author: joannaleecy
-description: Describes the features and limits of Development mode titles.
+description: Describes the features and limits of Development Mode titles.
 ms.author: jenelleb
 ms.date: 09/09/2020
 ms.topic: article
@@ -10,38 +10,41 @@ keywords: playfab, pricing, dev mode, development mode, title, meter, meters
 ms.localizationpriority: medium
 ---
 
-# Titles in Development mode
+# Titles in Development Mode
 
 > [!IMPORTANT]
-> When you're ready to scale up, it's important to make sure you switch your title from "Development mode" to "Live." To make this change, use the **Launch** button on the Game Overview page or the PlayFab main dashboard. This change ensures that the title isn't limited to 100,000 unique users.
+> When you're ready to scale up, it's important to make sure you switch your title from "Development Mode" to "Live." To make this change, use the **Launch** button on the Game Overview page or the PlayFab main dashboard. This change ensures that the title isn't limited to 100 unique users.
 
-All PlayFab titles are in one of two possible states - development mode and live. Development mode is, as the name suggests, meant for titles currently in development. This mode provides developers with the flexibility to connect a title to PlayFab without running up the bill.
+> [!NOTE] 
+> Development Mode is being replaced by Foundation Mode as of March 11, 2026. To access PlayFab services with no monthly bill for the duration of your development cycle, we recommend [creating new titles in Foundation Mode](../get-started/foundation-onboarding.md). All titles that ship to an Xbox storefront will also get Foundation Mode services included as part of their platform agreement. 
 
-A game in development mode can have up to 100,000 unique users. These titles can be [launched](title-launches.md) through Game Manager and is then considered live. Launching a title removes all development mode limitations and allows the title to expand outside of test markets.
+Developers can evaluate PlayFab services risk free using Development Mode, with no monthly bills up to the first 1000 unique users. Once a title in Development Mode hits this limit, no additional users can be created until a title is moved to a live mode. 
 
-By default, every title created starts in development mode. The **My Studios and Titles** main page indicate which state a title is in through a mark on the bottom, left corner of the title block. This indicator can also be viewed at the top of the left nav within a title. Titles in development mode are labeled **Development**. Live titles are blank.
+Titles can be [launched](title-launches.md) through Game Manager and is then considered live. Launching a title removes all Development Mode limitations. 
 
-**My Studios view of development mode title tag**
+By default, every title created starts in Development Mode. The **My Studios and Titles** main page indicate which state a title is in through a mark on the bottom, left corner of the title block. This indicator can also be viewed at the top of the left nav within a title. Titles in Development Mode are labeled **Development**. Live titles are blank.
 
-![My Studios view of development mode title tag](pricingV2-media/development-mode-title-tag.png "My Studios view of development mode title tag")
+**My Studios view of Development Mode title tag**
 
-**Title page view of development mode title tag**
+![My Studios view of Development Mode title tag](pricingV2-media/development-mode-title-tag.png "My Studios view of Development Mode title tag")
 
-![Title page view of development mode title tag](pricingV2-media/dev-mode-title-tag-titlePage.PNG "Title page view of development mode title tag")
+**Title page view of Development Mode title tag**
+
+![Title page view of Development Mode title tag](pricingV2-media/dev-mode-title-tag-titlePage.PNG "Title page view of Development Mode title tag")
 
 **Live title with blank tag**
 
 ![Live title with blank tag](pricingV2-media/live-mode-title.PNG "Live title with blank tag")
 
 > [!NOTE]
-> As long as your title is in development mode, consumption isn't counted towards any of your billable meters.
+> As long as your title is in Development Mode, consumption isn't counted towards any of your billable meters.
 
 The example below shows how meter consumption is reflected in the billing for a fictional customer called Fun Studios:
 
 | Title | Title mode | Meter Consumption |
 | --- | --- | --- |
 | Fun Game | Live | 1 million PlayStream events |
-| Fun Game 2: The Return of Fun | Development mode | 100,000 PlayStream events
+| Fun Game 2: The Return of Fun | Development Mode | 100,000 PlayStream events
 
 When Fun Studios visits their Billing Summary page, they only see the consumption for their Live title, Fun Game, count against their Standard Plan included resources.
 
@@ -53,19 +56,19 @@ When Fun Studios visits their Billing Summary page, they only see the consumptio
 
 ## Limits
 
-There are some studio and title limits associated with development mode:
+There are some studio and title limits associated with Development Mode:
 
 ### Studio limits
 
 | Limit | Amount |
 | --- | --- |
-| Titles in Development mode | 10 Titles |
+| Titles in Development Mode | 10 Titles |
 
 ### Title limits
 
 | Limit | Amount |
 | --- | --- |
-| Unique users | 100,000 users created |
+| Unique users | 1000 users created |
 | PlayStream events | 1 million events |
 | Telemetry events | 1 million events |
 | Profile reads | 5 million reads |
@@ -85,7 +88,7 @@ There are some studio and title limits associated with development mode:
 | Insights credits | Insights Performance Level 1 |
 
 **Definition of unique users:**
-Unique users are the total number of players ever created in your development mode title, which is distinct from monthly active users or daily active users.
+Unique users are the total number of players ever created in your Development Mode title, which is distinct from monthly active users or daily active users.
 
 > [!NOTE]
 > You can learn more about title limits at [PlayFab Pricing](https://www.playfab.com/pricing).
diff --git a/playfab-docs/pricing/pricing-overview.md b/playfab-docs/pricing/pricing-overview.md
index 052b22994..01196940a 100644
--- a/playfab-docs/pricing/pricing-overview.md
+++ b/playfab-docs/pricing/pricing-overview.md
@@ -15,7 +15,7 @@ ms.localizationpriority: medium
 
 1. **[Billing Summary](billingDetails.md):** View past and present estimated costs.
 
-2. **[Development Mode](development-mode.md):** Understand technical limits applied to titles in development mode.
+2. **[Development Mode](development-mode.md):** Understand technical limits applied to titles in Development Mode.
 
 3. **[Pricing Meters](Meters/meters.md):** Learn about meter pricing and related APIs.
 
diff --git a/playfab-docs/pricing/pricingV2-media/billingSummaryLink.PNG b/playfab-docs/pricing/pricingV2-media/billingSummaryLink.PNG
index 441812761..cf8651ada 100644
Binary files a/playfab-docs/pricing/pricingV2-media/billingSummaryLink.PNG and b/playfab-docs/pricing/pricingV2-media/billingSummaryLink.PNG differ
diff --git a/playfab-docs/pricing/pricingV2-media/dev-mode-title-tag-titlePage.PNG b/playfab-docs/pricing/pricingV2-media/dev-mode-title-tag-titlePage.PNG
index 154d03cb8..93436fddc 100644
Binary files a/playfab-docs/pricing/pricingV2-media/dev-mode-title-tag-titlePage.PNG and b/playfab-docs/pricing/pricingV2-media/dev-mode-title-tag-titlePage.PNG differ
diff --git a/playfab-docs/pricing/pricingV2-media/development-mode-title-tag.png b/playfab-docs/pricing/pricingV2-media/development-mode-title-tag.png
index c3dec5895..c4123674d 100644
Binary files a/playfab-docs/pricing/pricingV2-media/development-mode-title-tag.png and b/playfab-docs/pricing/pricingV2-media/development-mode-title-tag.png differ
diff --git a/playfab-docs/pricing/pricingV2-media/dropDownBillSumm.PNG b/playfab-docs/pricing/pricingV2-media/dropDownBillSumm.PNG
index e1b9c2409..5111ef6aa 100644
Binary files a/playfab-docs/pricing/pricingV2-media/dropDownBillSumm.PNG and b/playfab-docs/pricing/pricingV2-media/dropDownBillSumm.PNG differ
diff --git a/playfab-docs/pricing/pricingV2-media/launch-menu.PNG b/playfab-docs/pricing/pricingV2-media/launch-menu.PNG
index fa080dc10..d488cce47 100644
Binary files a/playfab-docs/pricing/pricingV2-media/launch-menu.PNG and b/playfab-docs/pricing/pricingV2-media/launch-menu.PNG differ
diff --git a/playfab-docs/pricing/pricingV2-media/live-mode-title.PNG b/playfab-docs/pricing/pricingV2-media/live-mode-title.PNG
index 21f2f4594..66a9a679e 100644
Binary files a/playfab-docs/pricing/pricingV2-media/live-mode-title.PNG and b/playfab-docs/pricing/pricingV2-media/live-mode-title.PNG differ
diff --git a/playfab-docs/pricing/pricingV2-media/myStudiosNotated.png b/playfab-docs/pricing/pricingV2-media/myStudiosNotated.png
index f91733ec9..d9ac4fdea 100644
Binary files a/playfab-docs/pricing/pricingV2-media/myStudiosNotated.png and b/playfab-docs/pricing/pricingV2-media/myStudiosNotated.png differ
diff --git a/playfab-docs/pricing/support.md b/playfab-docs/pricing/support.md
index a0e42048a..4f233e313 100644
--- a/playfab-docs/pricing/support.md
+++ b/playfab-docs/pricing/support.md
@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 # Accessing PlayFab Technical Support
 
 PlayFab offers a range of support options designed to meet the needs of developers across various stages of development and account tiers. Whether you're just getting started or actively managing a live title, you can access support through public documentation, community discord, or direct technical assistance. 
-Support availability is based on your account plan, with higher tiers offering expanded access and faster response times. Customers may upgrade their plans to unlock additional support features.
+Support availability is based on your account plan, with higher tiers offering expanded access and faster response times. Customers can upgrade their plans to unlock additional support features.
 
 ## Support Offerings Overview
 
@@ -21,8 +21,8 @@ Support availability is based on your account plan, with higher tiers offering e
 |:---------------------------------- |:-----------------------------------|:-----------------------------------| 
 | **Documentation**        | Public API reference, tutorials, samples, and feature guides. | Open to all |
 | **Discord Community**         | Community-based support and discussion forums via Discord. | Open to all |
-| **Account Help**            | Direct support for non-technical administrative issues | Open to all PlayFab Developers Accounts |
-| **Support Tickets**          | Direct support for technical issues and service implemetation questions. |Standard Plans and above|
+| **Account Help**            | Direct support for nontechnical administrative issues | Open to all PlayFab Developers Accounts |
+| **Support Tickets**          | Direct support for technical issues and service implementation questions. |Standard Plans and above|
 | **Emergency Escalations**          | Fastest incident response for service-impacting emergencies. |Premium Plans only |
 
 ## Support Offerings
@@ -45,46 +45,48 @@ Support availability is based on your account plan, with higher tiers offering e
 
 ### ACCOUNT HELP
 
-**Purpose:** Use PlayFab Account Help to submit non-technical inquiries related to account access, billing, plan management, sales, or other administrative support.
+**Purpose:** Use PlayFab Account Help to submit nontechnical inquiries related to account access, billing, plan management, sales, or other administrative support.
 
 **Minimum Required Account Plan:** PlayFab account is needed. Available to all PlayFab developers, including free-tier accounts.
 
 **How to access:** PlayFab Developers can access the **Account Help** page in Game Manager. 
-1. Log in to [PlayFab.com](https://playfab.com).
+1. Log in to [PlayFab.com](https://developer.playfab.com).
 2. Navigate to the **Studio-level** "..." section (ellipsis menu).
 3. Select Account Help.
 4. Complete the request form by selecting appropriate Problem Type and Sub-Type fields with description of the problem.
-5. Submit the ticket. Expect a response within 3 business days.
+5. Submit the ticket. Expect a response within three business days.
 
 > [!NOTE]
 > To streamline support access for effective issue resolution, PlayFab has updated its support experience across both PlayFab.com and Game Manager. This includes the deprecation of the “Contact Us” form on PlayFab.com, introduction of the Account Help support for all PlayFab developers.
-> For login-related issues, please use the self-service account recovery flow provided through Microsoft Entra ID. 
+> For login-related issues, use the self-service account recovery flow provided through Microsoft Entra ID. 
 
 ### SUPPORT TICKET SUBMISSION
 
-**Purpose:** Use support tickets to understand how to use a particular PlayFab feature, or to request help with a technical problem, or to report a bug. Customers with paid accounts may submit support tickets directly to the PlayFab team through the "Contact Us" Page in Game Manager. Customers will receive a response within 1 business day.
+**Purpose:** Use support tickets to understand how to use a particular PlayFab feature, or to request help with a technical problem, or to report a bug. Customers with paid accounts can submit support tickets directly to the PlayFab team through the "Contact Us" Page in Game Manager. Customers will receive a response within one business day.
 
 **Minimum Required Account Plan:** Standard Account Plan
 
 **How to access:** Qualified accounts can access the **Contact Us** page in Game Manager:
 
-1. Log in to [PlayFab.com](https://playfab.com).
+1. Log in to [PlayFab.com](https://developer.playfab.com).
 2. Navigate to the **Title Overview** page of the title needing support.
 3. To access the help menu, select the **?** in the top right navigation bar.
 4. Select **Contact Us** and fill out the support form.
 
+If you recently requested an upgrade, support ticket submission becomes available when the plan change takes effect. Plan changes are scheduled for the beginning of the next billing period. To confirm your current plan and effective date, see [Account upgrades](account-upgrades.md).
+
 ### EMERGENCY ESCALATIONS
 
 **Purpose:** Provides 24/7 access to PlayFab's on-call engineering team in the event of critical service-impacting issues. This provides fastest incident response time to customers during emergencies. 
 
 > [!NOTE]
-> Emergency escalations should be used sparingly and only in the case of high-impact service errors or outtages.
+> Emergency escalations should be used sparingly and only in the case of high-impact service errors or outages.
 
 **Minimum Required Account Plan:** Premium Account Plan
 
 **How to access:** Qualified accounts can use the emergency escalation option via the **Contact Us** page in Game Manager:
 
-1. Log in to [PlayFab.com](https://playfab.com).
+1. Log in to [PlayFab.com](https://developer.playfab.com).
 2. Navigate to the **Title Overview** page of the title needing support.
 3. Select the **?** in the top right navigation bar to access the drop-down menu.
 4. Select **Contact Us** to access the form.
diff --git a/playfab-docs/pricing/title-launches.md b/playfab-docs/pricing/title-launches.md
index ed8d87a37..43ad44195 100644
--- a/playfab-docs/pricing/title-launches.md
+++ b/playfab-docs/pricing/title-launches.md
@@ -18,34 +18,31 @@ Customers can upgrade their account plan and launch titles using the self-servic
 
 A PlayFab title has two possible modes.
 
-1. **Development mode:** A title in development mode doesn't incur costs when you're using the core services. Use this mode to experiment with most of PlayFab offerings. A title in development mode is subjected to specific total player accounts and meter usage limits as determined by PlayFab. For more information about the included limits, see [development-mode.md](development-mode.md).
-
-    > [!NOTE]
-    > [Multiplayer server hosting](../multiplayer/servers/billing-for-thunderhead.md), [Party](./Meters/meters.md#party), and [Insights](../data-analytics/legacy/insights/pricing.md) aren't part of the core services. But they do have limited free usage available in Development mode.
+1. **Development mMde:** A title in Development Mode doesn't incur costs when you're using the core services. Use this mode to experiment with most of PlayFab offerings. A title in Development Mode is subjected to specific total player accounts and meter usage limits as determined by PlayFab. For more information about the included limits, see [development-mode.md](development-mode.md).
 
 1. **Live:** A live title uses metering to measure your usage. You're charged according to the paid service account plan and rate. Any meter usage over what is included in the account plan's base rate results in charges per meter consumed. For more information, see [Meters/meters.md](Meters/meters.md).
 
     > [!NOTE]
-    > Your title could still be in development when your PlayFab title is Live. In the same way, you could have actual players in the game when the PlayFab title is in Development mode. A title in Development mode will continue to have the total player accounts limit as determined by PlayFab. Moving to Live removes that limit. To convert a title from Development mode to Live, go to the title in PlayFab portal and select the **Launch** button. For instructions, see below.
+    > Ensure you move your PlayFab title out of Development Mode before releasing your game. A title in Development Mode will continue to have the total player accounts limit as determined by PlayFab. Moving to Live removes that limit. To convert a title from Development Mode to Live, go to the title in PlayFab portal and select the **Launch** button. For instructions, see below.
 
 ## Launching a title
 
 > [!WARNING]
-> Launching a title is a permanent action. The title cannot return to Development mode after the launch is completed.
+> Launching a title is a permanent action. The title cannot return to Development Mode after the launch is completed.
 
-To be able to move a title from Development mode to Live, a title must be in a Studio with a paid account plan.
+To be able to move a title from Development Mode to Live, a title must be in a Studio with a paid account plan.
 
 ### Launching a title with a Free to Start plan
 
-Titles may only be changed to Live in Studios owned by paid accounts. Follow the steps in the section below to upgrade your free account to a paid account first. After the upgrade, you'll see the launch option to switch your title from Development mode to Live.
+Titles may only be changed to Live in Studios owned by paid accounts. Follow the steps in the section below to upgrade your free account to a paid account first. After the upgrade, you'll see the launch option to switch your title from Development Mode to Live.
 
 ### Launching a title within a Paid Account Plan
 
 To launch a title within a paid account plan:
 
-1. Sign in to [https://playfab.com/](https://playfab.com/)
+1. Sign in to [https://developer.playfab.com/](https://developer.playfab.com/)
 
-2. Navigate to the **My Studios** page and identify the **Development mode** title to be launched.
+2. Navigate to the **My Studios** page and identify the **Development Mode** title to be launched.
 
 3. Select the down arrow on the title to open the drop-down menu.
 
@@ -57,18 +54,10 @@ To launch a title within a paid account plan:
 
 ## Frequently asked questions
 
-Q: What happens when I launch my title for the world to sign up and play but it's still in PlayFab Development mode?
+Q: What happens when I launch my title for the world to sign up and play but it's still in PlayFab Development Mode?
 
-A: Because your title is in Development mode, it still has a 100K total player accounts limit. The core meters (Profile, Content and Configuration, and Events) continue to have no cost. When your title starts making a high number of service calls, it may be throttled, and would affect your overall player experience. To remove the player accounts limit, you have to move the title out of Development mode. At the same time, the core service meters start to charge your account normally, based on your tier of service.
+A: Because your title is in Development Mode, there is a limit on the total number of player accounts that can be created in that title. Once your title reaches that limit, all requests to create new player accounts will be denied which will impact the player experience.  To remove the player accounts limit, you have to move the title out of Development Mode. 
 
 Q: I'm using the **Free to Start** plan. Do I need to switch my title to Live at launch?
 
-A: In the **Free to Start** plan, you don't have the **Launch** option to switch your title from Development mode to Live. You must first upgrade to a paid tier (pay-as-you-go or higher) to have the launch option made available to you.
-
-Q: I'm only using PlayFab Party and it's free for Xbox Live users. What plan should I be using?
-
-A: You can choose to use any of the plans we offer&mdash;Pay-as-you-go, Standard, or Premium. You won't be charged when Xbox Live users use Party for chat and networking.
-
-Q: Do I have to switch my title to Live if I'm not expecting it to hit the **Free to Start** plan limits?
-
-A: You don't have to. However, it's worth noting that we don't support load testing of any kind in Development mode. That includes a limited release of a title to a closed community. If a title in Development mode starts making a high number of calls to the service, it may be throttled.
+A: In the **Free to Start** plan, you don't have the **Launch** option to switch your title from Development Mode to Live. You must first upgrade to a paid tier (pay-as-you-go or higher) to have the launch option made available to you.
\ No newline at end of file
diff --git a/playfab-docs/release-notes/2016.md b/playfab-docs/release-notes/2016.md
index 84a440a88..94d3380d4 100644
--- a/playfab-docs/release-notes/2016.md
+++ b/playfab-docs/release-notes/2016.md
@@ -6,7 +6,7 @@ ms.author: jenelleb
 ms.date: 07/12/2018
 ms.topic: article
 ms.service: azure-playfab
-keywords: playfab, development, release, apis, features
+keywords: playfab, development, release, APIs, features
 ms.localizationpriority: medium
 ---
 
@@ -14,13 +14,13 @@ ms.localizationpriority: medium
 
 ## 161121  
 
-Date: 2016-11-20
+Date: November 20, 2016
 
 ### API changes
 
 - Each Client API can now be individually enabled or disabled.
 - See our [blog post](https://blog.playfab.com/blog/permission-policies/) for details.
-- We are releasing a new feature called Scheduled Tasks.
+- We're releasing a new feature called Scheduled Tasks.
 - See our blog post for details: (Coming soon).
 
 ### New APIs
@@ -41,34 +41,34 @@ Date: 2016-11-20
 
 ### New PlayStream event
 
-- [title_permission_policy_changed](../api-references/events/title-permission-policy-changed.md)
+- [title_permission_policy_changed](../api-references/events/ApiAccessPolicy/title-permission-policy-changed.md)
 
 ### WindowsSDK specific changes
 
-- A new overhauled **WindowsSDK** will be published next week.
+- A new overhauled **WindowsSDK** is published next week.
 - See our blog post for a brief description.
-- If you are interested in previewing the upcoming changes, post here:
-  - <https://community.playfab.com/questions/3973/windowsc-sdk-vs2015-support.html>
+- If you're interested in previewing the upcoming changes, post here:
+  - <https://community.playfab.com/questions/3973/windowsc-SDK-vs2015-support.html>
 
 ## 161108  
 
-Date: 2016-11-07
+Date: November 7, 2016
 
 ### HOTFIX
 
-Version 1.0 of the overhauled [CSharpSDK](https://github.com/PlayFab/CSharpSDK) increased the .Net version requirement from 4.0 to 4.6. This was not intended. This hotfix removes the 4.6 only features, so that it will once again build on .Net 4.0 or higher.
+Version 1.0 of the overhauled [CSharpSDK](https://github.com/PlayFab/CSharpSDK) increased the .NET version requirement from 4.0 to 4.6. This isn't intended. This hotfix removes the 4.6 only features, so that it builds on .NET 4.0 or higher.
 
 ## 161107  
 
-Date: 2016-11-06
+Date: November 6, 2016
 
 ### API changes
 
 **Shared**
 
 - `CatalogItem`
-- `InitialLimitedEditionCount` ( out of beta )
-If `IsLImitedEdition` is `true`, then this determines amount of the item initially available. Note that this field is ignored if the catalog item already existed in this catalog, or the field is less than 1.
+- `InitialLimitedEditionCount` (out of beta)
+If `IsLImitedEdition` is `true`, then this determines amount of the item initially available. This field is ignored if the catalog item already existed in this catalog, or the field is less than 1.
 - Player display name uniqueness is now optional.
 - Player display name returned as Photon "Nickname" when players connect to Photon Cloud.
 
@@ -94,47 +94,47 @@ If `IsLImitedEdition` is `true`, then this determines amount of the item initial
 
 ## 161031  
 
-Date: 2016-10-30
+Date: October 30, 2016
 
-~~**Unreal Blueprints hotfix release**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**Unreal Blueprints hotfix release**~~ (UPDATED: This SDK is deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
 - ~~UnrealBlueprintSDK **upgrade warning**: There was a naming conflict between Android and the PlayFab "SourceType" enum. As a result, we've had to rename this blueprint-enum. This breaks any [Client/GetStoreItems](xref:titleid.playfabapi.com.client.title-widedatamanagement.getstoreitems) or [Admin/GetStoreItems](xref:titleid.playfabapi.com.admin.title-widedatamanagement.getstoreitems) PlayFab-api-nodes. The upgrade process in-editor is to delete and re-create each affected blueprint node.~~
 
 - ~~UnrealBlueprintSDK Specific Changes:~~
-  - ~~Fixed a minor bug where certain errors would not report correctly~~
+  - ~~Fixed a minor bug where certain errors wouldn't report correctly~~
   - ~~Fixed a name conflict that prevented making Android builds (ESourceType)~~
 
 ## 161017  
 
-Date: 2016-10-16
+Date: October 16, 2016
 
 ### Deprecation changes
 
-- `Client/GetUserCombinedInfo` has transitioned from `Proposed` to `Deprecated`, which means most SDKs using this will now throw an error. Please transition to [Client/GetPlayerCombinedInfo](xref:titleid.playfabapi.com.client.accountmanagement.getplayercombinedinfo).
-- Deprecated APIs from this patch note: [160822](#160822) have transitioned from deprecated to obsolete, according to this blog: [Deprecation Visibility](https://playfab.com/blog/deprecation-visibility/) and thus, those APIs have been removed from the newest version of the SDKs. If you update your SDK, you must now transition to the new replacement APIs.
-- `Password` in the `Admin UserCredentials` object has been deprecated. You no longer need to know your user's password to call the `Admin/ResetUsers` method.
+- `Client/GetUserCombinedInfo` has transitioned from `Proposed` to `Deprecated`, which means most SDKs using this will now throw an error. Transition to [Client/GetPlayerCombinedInfo](xref:titleid.playfabapi.com.client.accountmanagement.getplayercombinedinfo).
+- Deprecated APIs from this patch note: [160822](#160822) transitioned from deprecated to obsolete, according to this blog: [Deprecation Visibility](https://playfab.com/blog/deprecation-visibility/) and thus, those APIs were removed from the newest version of the SDKs. If you update your SDK, you must now transition to the new replacement APIs.
+- `Password` in the `Admin UserCredentials` object is deprecated. You no longer need to know your user's password to call the `Admin/ResetUsers` method.
 
 ### UnitySdk breaking changes
 
 - [UnitySdk](https://github.com/PlayFab/UnitySDK)
-  - If you are using reflection on PlayFab API-model types, you will have to convert your reflection logic from properties to fields (See UnitySdk Specific Changes below).
+  - If you're using reflection on PlayFab API-model types, you have to convert your reflection logic from properties to fields (See UnitySdk Specific Changes in the following section).
 
 ### API changes
 
 - **New PlayStream events:**
-  - ~~`gamelobby_started`~~ (UPDATED: This is deprecated. See [Lobby-Matchmaking-Notifications](../multiplayer/lobby/lobby-and-matchmaking-real-time-notifications.md))
-  - ~~`gamelobby_ended`~~(UPDATED: This is deprecated. See [Lobby-Matchmaking-Notifications](../multiplayer/lobby/lobby-and-matchmaking-real-time-notifications.md))
-  - [Client/AttributeInstall](xref:titleid.playfabapi.com.client.advertising.attributeinstall) request has deprecated `Android_Id` and converted to `Adid`. All SDKs have had some internal login hooks updated to account for this. This is not a breaking change, because it was always intended to use Google-AdvertisingId (Adid), and using the Android DeviceId here would not have worked properly. This change is merely for clarity and consistency
-  - For the GitHub add-on, revisions to CloudScript will no longer immediately go live. Instead a new revision will be made, and you make it live via Game Manager
+  - ~~`gamelobby_started`~~ (UPDATED: This is deprecated. See [Lobby-Matchmaking-Messages](../multiplayer/lobby/lobby-and-matchmaking-real-time-messages.md))
+  - ~~`gamelobby_ended`~~(UPDATED: This is deprecated. See [Lobby-Matchmaking-Messages](../multiplayer/lobby/lobby-and-matchmaking-real-time-messages.md))
+  - [Client/AttributeInstall](xref:titleid.playfabapi.com.client.advertising.attributeinstall) request deprecated `Android_Id` and converted to `Adid`. All SDKs had some internal login hooks updated to account for this. This isn't a breaking change, because it's intended to use Google-AdvertisingId (Adid), and using the Android DeviceId here doesn't work properly. This change is for clarity and consistency
+  - For the GitHub add-on, revisions to CloudScript no longer immediately go live. Instead a new revision is made, and you make it live via Game Manager
   - The default `helloWorld` CloudScript function described in this doc: [CloudScript quickstart](../live-service-management/service-gateway/automation/cloudscript/quickstart.md) was out of date. Updated the document to more closely match the current version (This is only relevant to new title creation)
 
 ### API Server bug fixes
 
-- Fixed a 500 error in [Server/ExecuteCloudScript](xref:titleid.playfabapi.com.server.server-sidecloudscript.executecloudscript): PlayFabId is now a mandatory parameter (Formerly it would error if it wasn't provided)
-- Fixed a 500 error in [Server/GetSharedGroupData](xref:titleid.playfabapi.com.server.sharedgroupdata.getsharedgroupdata): SharedGroupId is now a mandatory parameter (Formerly it would error if it wasn't provided)
-- Fixed a 500 error in [Server/AddSharedGroupMembers](xref:titleid.playfabapi.com.server.sharedgroupdata.addsharedgroupmembers): PlayFabIds is now a mandatory parameter (Formerly it would error if it wasn't provided)
-- Fixed a 500 error in [Server/RemoveSharedGroupMembers](xref:titleid.playfabapi.com.server.sharedgroupdata.removesharedgroupmembers): PlayFabIds is now a mandatory parameter (Formerly it would error if it wasn't provided)
-- Fixed a 500 error in [Server/DeleteSharedGroup](xref:titleid.playfabapi.com.server.sharedgroupdata.deletesharedgroup): SharedGroupId is now a mandatory parameter (Formerly it would error if it wasn't provided)
+- Fixed a 500 error in [Server/ExecuteCloudScript](xref:titleid.playfabapi.com.server.server-sidecloudscript.executecloudscript): PlayFabId is now a mandatory parameter. Formerly, the API threw an error if the PlayFabId wasn't provided.
+- Fixed a 500 error in [Server/GetSharedGroupData](xref:titleid.playfabapi.com.server.sharedgroupdata.getsharedgroupdata): SharedGroupId is now a mandatory parameter. Formerly, the API threw an error if the SharedGroupId wasn't provided.
+- Fixed a 500 error in [Server/AddSharedGroupMembers](xref:titleid.playfabapi.com.server.sharedgroupdata.addsharedgroupmembers): PlayFabIds is now a mandatory parameter. Formerly, the API threw an error if the PlayFabIds wasn't provided.
+- Fixed a 500 error in [Server/RemoveSharedGroupMembers](xref:titleid.playfabapi.com.server.sharedgroupdata.removesharedgroupmembers): PlayFabIds is now a mandatory parameter. Formerly, the API threw an error if the PlayFabIds wasn't provided.
+- Fixed a 500 error in [Server/DeleteSharedGroup](xref:titleid.playfabapi.com.server.sharedgroupdata.deletesharedgroup): SharedGroupId is now a mandatory parameter. Formerly, the API threw an error if the SharedGroupId wasn't provided.
 
 ### LuaSDK specific changes
 
@@ -144,9 +144,9 @@ Date: 2016-10-16
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - Model properties have been converted to fields so they display better in the Unity Inspector (where relevant).
-  - Fixed a bug where if a CloudScript function returns a primitive, it will now be properly deserialized and returned as FunctionResult (Formerly it would have been null).
-  - The PaperTrail package has been fixed: [UnityPlayFabPaperTrail.unitypackage](https://github.com/PlayFab/UnitySDK/blob/master/Packages/UnityPlayFabPaperTrail.unitypackage)
+  - Converted model properties to fields so they display better in the Unity Inspector (where relevant).
+  - Fixed a bug where if a CloudScript function returns a primitive, it's now properly deserialized and returned as FunctionResult. Formerly it's null.
+  - Fixed the PaperTrail package: [UnityPlayFabPaperTrail.unitypackage](https://github.com/PlayFab/UnitySDK/blob/master/Packages/UnityPlayFabPaperTrail.unitypackage)
 
 ### SDKGenerator specific changes
 
@@ -155,7 +155,7 @@ Date: 2016-10-16
 
 ## 161003  
 
-Date: 2016-10-02
+Date: October 2, 2016
 
 ### API changes
 
@@ -183,26 +183,26 @@ Date: 2016-10-02
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - [UnitySDK](https://github.com/PlayFab/UnitySDK) V0 repository is being retired. Everybody should please update to UnitySDK V2 available on our download page.
-  - `IDFA` and `AdvertisingId` will work properly on Unity 5.5 beta versions.
-  - CloudScript functions that return a primitive, such as an integer, will now deserialize correctly
-  - Minor improvements to Unity Compression, it should now be safe to enable compression in the PlayFabSharedSettings scriptable object.
+  - [UnitySDK](https://github.com/PlayFab/UnitySDK) V0 repository is being retired. Everybody should update to UnitySDK V2 available on our download page.
+  - `IDFA` and `AdvertisingId` work properly on Unity 5.5 beta versions.
+  - CloudScript functions that return a primitive, such as an integer, deserialize correctly
+  - Minor improvements to Unity Compression. It's now safe to enable compression in the PlayFabSharedSettings scriptable object.
 
 ### WindowsSDK specific problems
 
 - The .lib files published with this repo are now bigger than the GitHub max file-size limit.
-- The latest version does not have updated lib files, and we've begun looking at alternatives.
+- The latest version doesn't have updated lib files, and we've begun looking at alternatives.
 
 ## 160919  
 
-Date: 2016-09-18
+Date: September 18, 2016
 
 ### New APIs for payments
 
-- We are expanding our Payments API to include a standard way to refund and dispute purchases.
+- We're expanding our Payments API to include a standard way to refund and dispute purchases.
 - [Admin/RefundPurchase](xref:titleid.playfabapi.com.admin.playerdatamanagement.refundpurchase)
 - [Admin/ResolvePurchaseDispute](xref:titleid.playfabapi.com.admin.playerdatamanagement.resolvepurchasedispute)
-**A few friend-based APIs have been copied from the Client to the Server:**
+**Copied a few friend-based APIs from the Client to the Server:**
 
   - [Server/GetFriendLeaderboard](xref:titleid.playfabapi.com.server.playerdatamanagement.getfriendleaderboard)
   - [Server/AddFriend](xref:titleid.playfabapi.com.server.friendlistmanagement.addfriend)
@@ -233,12 +233,12 @@ Date: 2016-09-18
 
 ## 160912
 
-Date: 2016-09-11
+Date: September 11, 2016
 
 ### Unity and CSharp upgrade warning
 
-- The deprecation warnings described [below](#160822) have gone into effect. Deprecated APIs will now throw compiler errors when possible.
-Likewise, the documentation for those APIs have been filtered from the main documentation.
+- The deprecation warnings described in [160822](#160822) have gone into effect. Deprecated APIs will now throw compiler errors when possible.
+Likewise, we filtered the documentation for those APIs from the main documentation.
 
 ### API changes
 
@@ -249,11 +249,11 @@ Likewise, the documentation for those APIs have been filtered from the main docu
 ### LuaSDK specific changes
 
 - [LuaSDK](https://github.com/PlayFab/LuaSDK)
-  - Incremental Corona Support: There are new/interim zip-files which can be included in a Corona project. Proper Corona plugins are coming soon.
+  - Incremental Corona Support: There are new/interim zip-files that can be included in a Corona project. Proper Corona plugins are coming soon.
 
 ## 160829  
 
-Date: 2016-08-28
+Date: August 28, 2016
 
 ### API changes
 
@@ -266,10 +266,10 @@ Date: 2016-08-28
   - [Admin/GetPlayerTags](xref:titleid.playfabapi.com.admin.playstream.getplayertags)
   - [Admin/RemovePlayerTag](xref:titleid.playfabapi.com.admin.playstream.removeplayertag)
   
-We have introduced segment tags, which provide a way of directly putting players into particular segments. You can now add one or more segment tags to each player. And then, when creating a segment, you can define the segment based on the segment tag.
+We've introduced segment tags, which provide a way of directly putting players into particular segments. You can now add one or more segment tags to each player. And then, when creating a segment, you can define the segment based on the segment tag.
 
-One intended use for Segment Tags is for integration with external analytics providers, like Appuri. The external analytics provider can perform its own advanced segmentation, such as "Likely to Churn", and then set a tag on players that match that segment.
-All current deprecation changes have been released. Please see our blog post for details: <https://playfab.com/deprecation-visibility/>
+One intended use for Segment Tags is for integration with external analytics providers, like Appuri. The external analytics provider can perform its own advanced segmentation, such as "Likely to Churn," and then set a tag on players that match that segment.
+Released all current deprecation changes. See our blog post for details: <https://playfab.com/deprecation-visibility/>
 
 ### Cocos2d-xSDK specific changes
 
@@ -280,19 +280,19 @@ All current deprecation changes have been released. Please see our blog post for
 ### PostmanCollection specific changes
 
 - [PostmanCollection](https://github.com/PlayFab/PostmanCollection)
-  - Added a header to all API methods which will help our servers track SDK usage. (This header already exists on all other SDKs).
+  - Added a header to all API methods, which help our servers track SDK usage. (This header already exists on all other SDKs).
 
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
 
-  - We are pleased to announce the initial public beta release of our latest tool: Unity Editor Extensions. This plugin provides an easy-to-use interface for configuring and managing the PlayFab SDK. All Unity developers are encouraged to check out EdEx; There has never been an easier time to sign up and get started developing.
-  - Added an alternate implementation of `ExecuteCloudScript` which automatically parses `FunctionResult` into a target type, using a generic parameter.
+  - Unity Editor Extensions is now available as an initial public beta release. This plugin provides an easy-to-use interface for configuring and managing the PlayFab SDK. All Unity developers are encouraged to check out EdEx. Sign up and get started developing.
+  - Added an alternate implementation of `ExecuteCloudScript`, which automatically parses `FunctionResult` into a target type, using a generic parameter.
   - Failure cases in API methods are improved: Some cases that threw exceptions now properly report back to the error-callback (such as Web-Requests with no internet connection), and other cases report better information to the error-callback.
 
-~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED: This SDK is deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
-- ~~Fixed an issue where APIs containing an optional list field in the request would not post the request properly to the server. (Such as GetPlayerStatistics)~~
+- ~~Fixed an issue where APIs containing an optional list field in the request wouldn't post the request properly to the server. (Such as GetPlayerStatistics)~~
 
 ### SDKGenerator specific changes
 
@@ -301,14 +301,14 @@ All current deprecation changes have been released. Please see our blog post for
 
 ## 160822
 
-Date: 2016-08-21
+Date: August 21, 2016
 
 ### Global upgrade warning
 
 Some SDKs have gained warnings for APIs that have become deprecated.
-If you see these warnings, please resolve them ASAP, and migrate to the indicated replacement APIs.
-Many of these APIs will be removed from the SDK within the next couple of months.
-There is a blog post about this [here](https://blog.playfab.com/blog/deprecation-visibility/).
+If you see these warnings, Resolve them ASAP, and migrate to the indicated replacement APIs.
+Many of these APIs are removed from the SDK within the next couple of months.
+There's a blog post about this [here](https://blog.playfab.com/blog/deprecation-visibility/).
 
 ### Deprecation notices
 
@@ -388,16 +388,16 @@ There is a blog post about this [here](https://blog.playfab.com/blog/deprecation
 
 - **New PlayStream events**
 
-  - [player_tag_added](../api-references/events/player-tag-added.md)
-  - [player_tag_removed](../api-references/events/player-tag-removed.md)
-  - [title_catalog_updated](../api-references/events/title-catalog-updated.md)
-  - [title_store_updated](../api-references/events/title-store-updated.md)
+  - [player_tag_added](../api-references/events/PlayerIdentity/player-tag-added.md)
+  - [player_tag_removed](../api-references/events/PlayerIdentity/player-tag-removed.md)
+  - [title_catalog_updated](../api-references/events/CatalogV1/title-catalog-updated.md)
+  - [title_store_updated](../api-references/events/CatalogV1/title-store-updated.md)
 
 ### Global SDK changes
 
 - The example projects provided with the SDKs have all been updated, and no longer use deprecated APIs.
 - Several SDKs have compiler warnings and/or comments that describe deprecated elements of the API.
-- The [PostmanCollection](https://github.com/PlayFab/PostmanCollection) internal format changed slightly. It will be less convenient to have multiple future versions of our [PostmanCollection](https://github.com/PlayFab/PostmanCollection) loaded at the same time (You'll get a warning about duplicate IDs).
+- The [PostmanCollection](https://github.com/PlayFab/PostmanCollection) internal format changed slightly. It's less convenient to have multiple future versions of our [PostmanCollection](https://github.com/PlayFab/PostmanCollection) loaded at the same time (You get a warning about duplicate IDs).
 
 ### ActionScriptSDK specific changes
 
@@ -406,12 +406,12 @@ There is a blog post about this [here](https://blog.playfab.com/blog/deprecation
 
 ## 160815
 
-Date: 2016-08-14
+Date: August 14, 2016
 
 ### Unreal upgrade warning
 
 Required syntax changes for upgrading Unreal 4.12
-Best described by ZKShao in the pull request which helped resolve the problems: `<https://github.com/PlayFab/UnrealCppSdk/pull/32>`
+Best described by ZKShao in the pull request that helped resolve the problems: `<https://github.com/PlayFab/UnrealCppSdk/pull/32>`
 
 ### API changes
 
@@ -419,10 +419,10 @@ Best described by ZKShao in the pull request which helped resolve the problems:
 
 - **New PlayStream events:**
 
-  - [player_statistic_deleted](../api-references/events/player-statistic-deleted.md)
-  - [player_unlinked_account](../api-references/events/player-unlinked-account.md)
+  - [player_statistic_deleted](../api-references/events/Leaderboards/player-statistic-deleted.md)
+  - [player_unlinked_account](../api-references/events/PlayerIdentity/player-unlinked-account.md)
 
-~~**UnrealCppSdk & UnrealBlueprintSdk specific changes:**~~ (UPDATED : These SDKs have been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealCppSdk & UnrealBlueprintSdk specific changes:**~~ (UPDATED: These SDKs are deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
 - ~~Updated to support Unreal 4.12~~
 - ~~Sadly, this requires dropping support for Unreal 4.11.x, due to conflicting requirements~~
@@ -435,7 +435,7 @@ Best described by ZKShao in the pull request which helped resolve the problems:
   - Game-servers can begin testing with registering callbacks to PlayStream events, and react in real-time
   - PlayFabSDK no longer requires permissions on Android. (WP8 and iOS still requires internet in build settings)
   - Phasing in deprecation warnings for APIs are out of date.
-  - These will later become deprecation errors, and will eventually be removed from the sdk.
+  - These will later become deprecation errors, and will eventually be removed from the SDK.
   - Some bug fixes for compression
   - PlayFabSdk now works in Unity 5.0
   - Fixed specific devices on specific older unity versions, and expanded internal testing
@@ -444,7 +444,7 @@ Best described by ZKShao in the pull request which helped resolve the problems:
 
 ## 160801  
 
-Date: 2016-07-31
+Date: July 31, 2016
 
 ### API changes
 
@@ -461,65 +461,65 @@ Date: 2016-07-31
 
 - **New PlayStream Events**
 
-  - ~~[session_started]~~(UPDATED: This is deprecated. See [Lobby-Matchmaking-Notifications](../multiplayer/lobby/lobby-and-matchmaking-real-time-notifications.md))
-  - ~~[session_ended]~~(UPDATED: This is deprecated. See [Lobby-Matchmaking-Notifications](../multiplayer/lobby/lobby-and-matchmaking-real-time-notifications.md))
+  - ~~[session_started]~~(UPDATED: This is deprecated. See [Lobby-Matchmaking-Messages](../multiplayer/lobby/lobby-and-matchmaking-real-time-messages.md))
+  - ~~[session_ended]~~(UPDATED: This is deprecated. See [Lobby-Matchmaking-Messages](../multiplayer/lobby/lobby-and-matchmaking-real-time-messages.md))
   - Minor documentation updates.
 
 ## 160726  
 
-Date: 2016-07-25
+Date: July 25, 2016
 
 ### UnitySDK hotfix changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
   - Fixes for specific Devices on older Unity versions.
-  - Fix for specific `AdminApi` model classes which were being labeled as `PlayFabResultCommon` instead of `PlayFabRequestCommon`.
+  - Fix for specific `AdminApi` model classes that were being labeled as `PlayFabResultCommon` instead of `PlayFabRequestCommon`.
   - Known Issue: When using PlayFab UnitySdk, Google advertisingID and iOS IDFA no longer attribute correctly for Unity versions before 5.3.
   - The easiest fix is to upgrade your Unity3D version, but we will try to restore this in a later release of our SDK.
 
 ## 160725  
 
-Date: 2016-07-24
+Date: July 24, 2016
 
 ### API changes
 
 - **New PlayStream Event**
 
-  - [display_name_filtered](../api-references/events/display-name-filtered.md) (documentation available soon).
+  - [display_name_filtered](../api-references/events/Partner/display-name-filtered.md) (documentation available soon).
 
-  - Some API examples have been updated.
+  - Updated some API examples.
   - Lots of minor documentation updates.
 
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - Introduced a `PlayFabRequestCommon base-class`, which does compile-time type-checking for request objects passed to the API (This should not affect any users unless they're using non-standard request objects).
+  - Introduced a `PlayFabRequestCommon base-class`, which does compile-time type-checking for request objects passed to the API (This shouldn't affect any users unless they're using nonstandard request objects).
 
   - Fixed a null-reference bug in startup that some users have reported.
   - Fixed an issue with `ProductionEnvironmentUrl` in the `PlayFabSharedSettings` `ScriptableObject` that some users have reported.
 
 ## 160721  
 
-Date: 2016-07-20
+Date: July 20, 2016
 
 ### UnitySDK hotfix changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
   - Unity 4.7 works again, within the limitations of that version
-  - A bunch of small high-visibility fixes that have been noticed by many in the community have been fixed.
-  - UnitySDK V2 was promised to have full Windows Phone/Universal support (as well as other platforms like consoles). We're happy to say that all known issues have finally been fixed for all known platforms, and the PlayFab UnitySdk should work everywhere.
+  - Fixed a bunch of small high-visibility issues that many in the community noticed.
+  - UnitySDK V2 was promised to have full Windows Phone/Universal support (and other platforms like consoles). We're happy to say that all known issues have finally been fixed for all known platforms, and the PlayFab UnitySdk should work everywhere.
 
-  - Due to an unexpected side-effect in Unity, we won't be able to apply the `HideAndDontSave` flag to the PlayFab Http Object. [Details Here](https://answers.unity.com/questions/1218422/hideanddontsave-disables-ondestroy.html).
-  - We have added a set of extension functions to reflection, which make both standard C# and .NetCore C# do the same thing with the same lines of code, when possible. This extension it is not meant to be a complete solution for all possible reflection inconsistencies between those platforms.
+  - Due to an unexpected side-effect in Unity, we can't apply the `HideAndDontSave` flag to the PlayFab Http Object. [Details Here](https://answers.unity.com/questions/1218422/hideanddontsave-disables-ondestroy.html).
+  - We've added a set of extension functions to reflection, which make both standard C# and .NET Core C# do the same thing with the same lines of code, when possible. This extension isn't meant to be a complete solution for all possible reflection inconsistencies between those platforms.
 
 ## 160714  
 
-Date: 2016-07-13
+Date: July 13, 2016
 
 ### UnitySDK upgrade warning
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - We have released a new major revision for [UnitySDK](https://github.com/PlayFab/UnitySDK). <!--~~Please visit our [Upgrade Guide](https://github.com/PlayFab/UnitySDK/blob/master/UPGRADE.md)~~--> (UPDATE : The UPGRADE Guide is obsolete).
+  - We've released a new major revision for [UnitySDK](https://github.com/PlayFab/UnitySDK). <!--~~Visit our [Upgrade Guide](https://github.com/PlayFab/UnitySDK/blob/master/UPGRADE.md)~~--> (UPDATE: The UPGRADE Guide is obsolete).
 
 ### API changes
 
@@ -531,9 +531,9 @@ Date: 2016-07-13
   - [UnlinkTwitch](xref:titleid.playfabapi.com.client.accountmanagement.unlinktwitch)
   - [GetPlayFabIDsFromTwitchIDs](xref:titleid.playfabapi.com.client.accountmanagement.getplayfabidsfromtwitchids)
 - **New PlayStream Events:**
-  - [title_exceeded_limit](../api-references/events/title-exceeded-limit.md)
-  - [title_limit_changed](../api-references/events/title-limit-changed.md)
-  - [title_requested_limit_change](../api-references/events/title-requested-limit-change.md)
+  - [title_exceeded_limit](../api-references/events/Extension/title-exceeded-limit.md)
+  - [title_limit_changed](../api-references/events/Extension/title-limit-changed.md)
+  - [title_requested_limit_change](../api-references/events/Title/title-requested-limit-change.md)
 
 ### LumberyardSDK specific changes
 
@@ -542,45 +542,45 @@ Date: 2016-07-13
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - A new major revision of [UnitySdk](https://github.com/PlayFab/UnitySDK) is going to be released very soon (hopefully today).
-  - The original UnitySdk will be available here for a limited time [UPDATE: Old link removed].
-  - Version 2 of the [UnitySdk](https://github.com/PlayFab/UnitySDK) is currently available here: UnitySDKV2Beta [UPDATE: Old link removed], and will become the new [UnitySdk](https://github.com/PlayFab/UnitySDK) soon [UPDATE: Done].
+  - A new major revision of [UnitySdk](https://github.com/PlayFab/UnitySDK) is going to be released soon (hopefully today).
+  - The original UnitySdk is available here for a limited time [UPDATE: Old link removed].
+  - Version two of the [UnitySdk](https://github.com/PlayFab/UnitySDK) is currently available here: UnitySDKV2Beta [UPDATE: Old link removed], and becomes the new [UnitySdk](https://github.com/PlayFab/UnitySDK) soon [UPDATE: Done].
 
 ## 160705  
 
-Date: 2016-07-04
+Date: July 4, 2016
 
 ### API changes
 
 - **New API**
   - [GetPlayerCombinedInfo](xref:titleid.playfabapi.com.client.accountmanagement.getplayercombinedinfo)
   - Lots of updated descriptions.
-  - All login calls have been updated to optionally return the [GetPlayerCombinedInfo](xref:titleid.playfabapi.com.client.accountmanagement.getplayercombinedinfo#getplayercombinedinforesultpayload) results.
-  - `GetUserCombinedInfo` API will be deprecated in favor of [GetPlayerCombinedInfo](xref:titleid.playfabapi.com.client.accountmanagement.getplayercombinedinfo) in the near future.
+  - Updated all login calls to optionally return the [GetPlayerCombinedInfo](xref:titleid.playfabapi.com.client.accountmanagement.getplayercombinedinfo#getplayercombinedinforesultpayload) results.
+  - `GetUserCombinedInfo` API is deprecated in favor of [GetPlayerCombinedInfo](xref:titleid.playfabapi.com.client.accountmanagement.getplayercombinedinfo) soon.
 
 ### UnitySDK specific changes
 
-- GZip compression mode has been restored for api-requests done with `PlayFabSettings.RequestType = WebRequestType.UnityWww`;
+- Restored GZip compression mode for api-requests done with `PlayFabSettings.RequestType = WebRequestType.UnityWww`;
 
-- A `JsonProperty` attribute has been added to `SimpleJson` and supports alternate naming of fields/properties, and omitting nulls from the serialized json.
-- TimeSpans serialized with the default PlayFab `SimpleJson` strategy will now serialize as a float number of seconds. Formerly, they would serialize as structs which wasn't supported by the API or any cross-platform options.
-- Support for certain platforms (EG: consoles, iOS) that build using Mono2x mode will not be supported until <https://github.com/PlayFab/UnitySDK/blob/master/V2UPGRADE.md> goes live.
-- Support for Windows Universal will not be supported until <https://github.com/PlayFab/UnitySDK/blob/master/V2UPGRADE.md> goes live.
-- See this blog post for more details: <https://blog.playfab.com/blog/new-and-improved-unity-sdk-beta-preview>
+- Added a `JsonProperty` attribute to `SimpleJson` that supports alternate naming of fields/properties, and omitting nulls from the serialized json.
+- TimeSpans serialize with the default PlayFab `SimpleJson` strategy as a float number of seconds. Formerly, they serialize as structs, which aren't supported by the API or any cross-platform options.
+- Support for certain platforms (EG: consoles, iOS) that build using Mono2x mode isn't supported until <https://github.com/PlayFab/UnitySDK/blob/master/V2UPGRADE.md> goes live.
+- Support for Windows Universal isn't supported until <https://github.com/PlayFab/UnitySDK/blob/master/V2UPGRADE.md> goes live.
+- For more information, see this blog post: <https://blog.playfab.com/blog/new-and-improved-unity-SDK-beta-preview>
 (standalone and android work correctly and are supported for all options)
-- All platforms that can utilize IL2CPP are supported in that mode.
-- This version was initially launched with an issue where compression did not always work. It was hot-fixed on July-8. Initial downloads before this date may have compression issues, which can be solved by updating, or by disabling compression: (PlayFabSettings.CompressApiData = false;)
+- All platforms that can use IL2CPP are supported in that mode.
+- This version was initially launched with an issue where compression doesn't work consistently. It was hot-fixed on July-8. Initial downloads before this date may have compression issues, which can be solved by updating, or by disabling compression: (PlayFabSettings.CompressApiData = false;)
 
 ## 160627  
 
-Date: 2016-06-26
+Date: June 26, 2016
 
 ### UnitySDK upgrade warning
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - `PlayFab.Internal.Util` has been renamed to `PlayFab.Internal.PlayFabUtil`. The "Util" name is very common and exists in the root level for many projects, which causes name conflicts for those customers.
+  - Renamed `PlayFab.Internal.Util` to `PlayFab.Internal.PlayFabUtil`. The "Util" name is common and exists in the root level for many projects, which causes name conflicts for those customers.
 
-  - When updating PlayFab-UnitySdk, you may see some deprecation warnings if you are using PlayFab's implementation of SimpleJson. Please resolve these at your leisure.
+  - When updating PlayFab-UnitySdk, you may see some deprecation warnings if you're using PlayFab's implementation of SimpleJson. Resolve these at your leisure.
 
 ### API changes
 
@@ -591,28 +591,28 @@ Date: 2016-06-26
 
 - **New PlayStream events**
 
-  - [character_consumed_item](../api-references/events/character-consumed-item.md)
-  - [character_created](../api-references/events/character-created.md)
-  - [character_inventory_item_added](../api-references/events/character-inventory-item-added.md)
-  - [character_statistic_changed](../api-references/events/character-statistic-changed.md)
-  - [character_vc_item_purchased](../api-references/events/character-vc-item-purchased.md)
-  - [character_virtual_currency_balance_changed](../api-references/events/character-virtual-currency-balance-changed.md)
-  - [player_redeemed_coupon](../api-references/events/player-redeemed-coupon.md)
+  - [character_consumed_item](../api-references/events/Character/character-consumed-item.md)
+  - [character_created](../api-references/events/PlayerIdentity/character-created.md)
+  - [character_inventory_item_added](../api-references/events/Character/character-inventory-item-added.md)
+  - [character_statistic_changed](../api-references/events/Leaderboards/character-statistic-changed.md)
+  - [character_vc_item_purchased](../api-references/events/Character/character-vc-item-purchased.md)
+  - [character_virtual_currency_balance_changed](../api-references/events/Character/character-virtual-currency-balance-changed.md)
+  - [player_redeemed_coupon](../api-references/events/Player/player-redeemed-coupon.md)
 
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - Known issues: Windows Store apps, and non-IL2CPP build options do not work yet. Stay tuned for a blog post about these issues and our new repository: UnitySDKV2Beta [UPDATE: Old link removed].
+  - Known issues: Windows Store apps, and non-IL2CPP build options don't work yet. Stay tuned for a blog post about these issues and our new repository: UnitySDKV2Beta [UPDATE: Old link removed].
   - We discovered a name-conflict with the core `UnityEngine` DLL, specifically an empty namespace called ``SimpleJson``. As such, we've had to rename and reorganize our JSON classes... again. Many apologies.
 
 ## 160613  
 
-Date: 2016-06-12
+Date: June 12, 2016
 
 ### Global SDK upgrade warning
 
-- PlayFabSettings and PlayFabVersion: These files and their contents have been merged into PlayFabSettings.
-- If you were previously referencing the PlayFabVersion variables, update to the same/very-similar variable in PlayFabSettings.
+- PlayFabSettings and PlayFabVersion: Merged these files and their contents into PlayFabSettings.
+- If you were previously referencing the PlayFabVersion variables, update to the similar variable in PlayFabSettings.
 
 ### API changes
 
@@ -625,30 +625,30 @@ Date: 2016-06-12
 
 ### SDK global changes
 
-- Please note that `RunCloudScript` has been deprecated since March 2016, and will be removed from the sdks in the near future. Please convert to [ExecuteCloudScript](xref:titleid.playfabapi.com.client.server-sidecloudscript.executecloudscript) asap.
+- We deprecated `RunCloudScript` since March 2016, and it's removed from the SDKs soon. Convert to [ExecuteCloudScript](xref:titleid.playfabapi.com.client.server-sidecloudscript.executecloudscript) as soon as possible.
 
-- Please stay tuned for a blog post about an internal testing system we call Jenkernaught. Our example projects contain some changes oriented towards deeper testing to improve sdk stability and reliability. Some specifics:
-- All testing and examples for CloudScript have been updated to [ExecuteCloudScript](xref:titleid.playfabapi.com.client.server-sidecloudscript.executecloudscript), since RunCloudScript is deprecated.
-- All testing and examples for successful login have been updated to `LoginWithCustomID`, to make internal testing easier.
+- Stay tuned for a blog post about an internal testing system we call Jenkernaught. Our example projects contain some changes oriented towards deeper testing to improve SDK stability and reliability. Some specifics:
+- Updated all testing and examples for CloudScript to [ExecuteCloudScript](xref:titleid.playfabapi.com.client.server-sidecloudscript.executecloudscript), since RunCloudScript is deprecated.
+- Updated all testing and examples for successful login to `LoginWithCustomID`, to make internal testing easier.
 
 ### Cocos2d-xSDK specific changes
 
 - [Cocos2d-xSDK](https://github.com/PlayFab/Cocos2d-xSDK)
-  - `MultitypeVar` can contain a `PlayFabBaseModel` for the purposes of writing request objects. It still cannot receive an arbitrary json object for results.
+  - `MultitypeVar` can contain a `PlayFabBaseModel` for the purposes of writing request objects. It still can't receive an arbitrary json object for results.
   - Initial versioned release.
 
-~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED: This SDK is deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
-- ~~Removed version info from a bunch of header-comments to avoid spammy check ins (So, this is the last spammy check in)~~
+- ~~Removed version info from a bunch of header-comments to avoid spammy check-ins (So, this is the last spammy check in)~~
 - ~~A missing http header is now provided.~~
 
 ## 160606  
 
-Date: 2016-06-05
+Date: June 5, 2016
 
 ### Global SDK upgrade warning
 
-For consistency across all sdks, the `sdkRevision` variable was renamed to `sdkVersion` ([ActionScriptSDK](https://github.com/PlayFab/ActionScriptSDK), [JavaSDK](https://github.com/PlayFab/JavaSDK), [UnitySdk](https://github.com/PlayFab/UnitySDK)).
+For consistency across all SDKs, we renamed the `sdkRevision` variable to `sdkVersion` ([ActionScriptSDK](https://github.com/PlayFab/ActionScriptSDK), [JavaSDK](https://github.com/PlayFab/JavaSDK), [UnitySdk](https://github.com/PlayFab/UnitySDK)).
 If you were accessing `sdkRevision`, switch to `sdkVersion`.
 
 ### API changes
@@ -659,8 +659,8 @@ If you were accessing `sdkRevision`, switch to `sdkVersion`.
 
 - More steps towards the deprecation of `RunCloudScript`, so customers should plan to migrate to [ExecuteCloudScript](xref:titleid.playfabapi.com.client.server-sidecloudscript.executecloudscript) for live projects.
 
-- Internally, we are halfway through a push to improve testing multi-platform testing for all sdks. [SDKGenerator](https://github.com/PlayFab/SDKGenerator) users may find references to `Jenkernaught` and `buildIdentifier`. `Jenkernaught` is the code-name for the tech that enables this improved platform testing. `buildIdentifier` is a new variable in all sdks indicating the specific PlayFab-Jenkins job which generated a particular sdk version.
-- There will be blog-post describing what the `Jenkernaught` does, and more detailed test-framework changes omitted from here, so stay tuned.
+- Internally, we're halfway through a push to improve testing multi-platform testing for all SDKs. [SDKGenerator](https://github.com/PlayFab/SDKGenerator) users may find references to `Jenkernaught` and `buildIdentifier`. `Jenkernaught` is the code-name for the tech that enables this improved platform testing. `buildIdentifier` is a new variable in all SDKs indicating the specific PlayFab-Jenkins job which generated a particular SDK version.
+- There's a blog post describing what the `Jenkernaught` does, and more detailed test-framework changes omitted from here, so stay tuned.
 
 ### ActionScriptSDK specific changes
 
@@ -677,75 +677,75 @@ If you were accessing `sdkRevision`, switch to `sdkVersion`.
 ### JavaScriptSDK specific changes
 
 - [JavaScriptSDK](https://github.com/PlayFab/JavaScriptSDK)
-  - Added a utility function to the `PlayFabClientSDK: IsClientLoggedIn()`. Please use this to determine this condition.
+  - Added a utility function to the `PlayFabClientSDK: IsClientLoggedIn()`. Use this to determine this condition.
   - Minor `Jenkernaught` related test-changes example/testing project.
 
 ### NodeSDK specific changes
 
 - [NodeSDK](https://github.com/PlayFab/NodeSDK)
-  - Added a utility function to the `PlayFabClientSDK: IsClientLoggedIn()`. Please use this to determine this condition.
+  - Added a utility function to the `PlayFabClientSDK: IsClientLoggedIn()`. Use this to determine this condition.
   - Minor `Jenkernaught` related test-changes example/testing project.
 
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - Fixed a critical bug where PlayFab API calls would stop working if you changed scenes.
+  - Fixed a critical bug where PlayFab API calls stop working if you change scenes.
   - Adjusted the defaults for timestamp formats to be consistent with other PlayFab SDKs.
-  - We are still having issues with Windows-Phone and Windows-Universal for Unity versions 5.3 or higher, which we hope to fix soon.
+  - We're still having issues with Windows-Phone and Windows-Universal for Unity versions 5.3 or higher, which we hope to fix soon.
 
 ## 160523  
 
-Date: 2016-05-22
+Date: May 22, 2016
 
 ### Global SDK upgrade warning
 
-Various APIs that save versioned data (UserData, CharacterData, and others) have had a datatype change from int to uint. This will require some users to remove/alter some casting where our api was formerly inconsistent. Some developers may need to change some local variables from int to uint.
+Various APIs that save versioned data (UserData, CharacterData, and others) had a datatype change from int to uint. This requires some users to remove/alter some casting where our api was formerly inconsistent. Some developers may need to change some local variables from int to uint.
 
-~~**UnrealBlueprintSdk upgrade warning:**~~ ~~There was a naming conflict between xcode and some of the playfab enums. As a result, we've had to revise the blueprint-enums again, which breaks all PlayFab-api-nodes using enums. The upgrade process in-editor is to delete and re-create each affected blueprint node (they will throw in-editor-compiler warnings if they're affected).~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealBlueprintSdk upgrade warning:**~~ ~~There was a naming conflict between xcode and some of the playfab enums. As a result, we've had to revise the blueprint-enums again, which breaks all PlayFab-api-nodes using enums. The upgrade process in-editor is to delete and re-create each affected blueprint node (they will throw in-editor-compiler warnings if they're affected).~~ (UPDATED: This SDK is deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
 ### API changes
 
-- There were some `DataVersion` vars which were set to an inconsistent datatype (int and uint in various APIs). All of these have been changed to uint for consistency.
+- Some `DataVersion` vars used an inconsistent datatype (int and uint in various APIs). We changed all of these to uint for consistency.
 
-- Some additional options have been added to APIs related to Matchmaking.
-- The matchmaker now takes an additional parameter (`StartNewIfNoneFound`), which allows titles to determine whether a new server should spin up if no results are found in the matchmaking process. By default, `StartNewIfNoneFound` is `true`, meaning that a new session will be created if one cannot be found which matches the requirements. This allows titles with skill-based matchmaking to potentially "loosen" the requirements for a match, to get players with skill levels at the far ends of the bell curve into games more quickly.
+- Added more options to APIs related to Matchmaking.
+- The matchmaker now takes an extra parameter (`StartNewIfNoneFound`), which allows titles to determine whether a new server should spin up if no results are found in the matchmaking process. By default, `StartNewIfNoneFound` is `true`, meaning that a new session is created if one can't be found that matches the requirements. This allows titles with skill-based matchmaking to potentially "loosen" the requirements for a match, to get players with skill levels at the far ends of the bell curve into games more quickly.
 
-- Updated the custom game server logic with `GameInstanceState`, which determines whether the game session is available for matchmaking. Games which are `Closed` are not available for matchmaking, allowing developers to create game sessions which are specific to a group of players, as well as to prevent post-start joins of a game session in progress. By default, game servers start in an Open state.
+- Updated the custom game server logic with `GameInstanceState`, which determines whether the game session is available for matchmaking. Games which are `Closed` aren't available for matchmaking, allowing developers to create game sessions which are specific to a group of players, and to prevent post-start joins of a game session in progress. By default, game servers start in an Open state.
 - 
-  -~~New API: `SetGameServerInstanceState` call can be used by the server to set its state, and `StartOpen` has been added to the `GameModeInfo` used in calls to `ModifyMatchmakerGameModes`, to allow specifying whether sessions in a game mode start as `Open` (the default) or `Closed`.~~(UPDATED: This is deprecated. See [Servers](../multiplayer/servers/index.md))
+  -~~New API: `SetGameServerInstanceState` call can be used by the server to set its state, and `StartOpen` is added to the `GameModeInfo` used in calls to `ModifyMatchmakerGameModes`, to allow specifying whether sessions in a game mode start as `Open` (the default) or `Closed`.~~(UPDATED: This is deprecated. See [Servers](../multiplayer/servers/index.md))
 
-~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED: This SDK is deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
 - ~~Internal SDK updates that make it easier to execute and handle API calls from C++.~~
-- ~~Added an internal testing suite which allows thorough verification of PlayFab functionality on all target devices. (Example project only, not the core plugin)~~
+- ~~Added an internal testing suite that allows thorough verification of PlayFab functionality on all target devices. (Example project only, not the core plugin)~~
 - ~~A bunch of C++ code cleanup, and improvements on logging and warnings.~~
 - ~~Resolved a concurrency problem with multiple synchronous api calls for Blueprints and C++ calls.~~
 
 ## 160502  
 
-Date: 2016-05-01
+Date: May 1, 2016
 
 ### Global SDK upgrade warning
 
-If you were previously setting the `ConfirmationMessage` and `ForceLink` fields, simply remove them.
+If you were previously setting the `ConfirmationMessage` and `ForceLink` fields, remove them.
 
 ### API changes
 
 - New Admin API:
-  - ~~**SetStoreSegmentOverrides**~~ (UPDATE : This API has been removed)
+  - ~~**SetStoreSegmentOverrides**~~ (UPDATE: This API is removed)
   - Some deprecated and internal fields are no longer published with the SDK: ConfirmationMessage and ForceLink.
 
-~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED: This SDK is deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
 - ~~Revised the readme and the example project to use a simpler login process, and the new simpler ExecuteCloudScript method.~~
-- ~~When there is an api error, the details of that error will report more accurately and display better debug information.~~
-- ~~We are removing the "Beta" flagging from Unreal sdks, they are now a full member of our SDK collection, with full support and quality checks.~~
+- ~~When there's an API error, the details of that error report more accurately and display better debug information.~~
+- ~~We're removing the "Beta" flagging from Unreal SDKs, they're now a full member of our SDK collection, with full support and quality checks.~~
 
 ## 160425  
 
-Date: 2016-04-24
+Date: April 24, 2016
 
-~~**UnrealBlueprintSdk Upgrade warning:** Many blueprint-api-calls which have enum fields will have to be updated to utilize the enum dropdown. The old value will be lost, and must be re-set. This affects dozens of PlayFab blueprint nodes.~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealBlueprintSdk Upgrade warning:** Many blueprint-api-calls which have enum fields will have to be updated to utilize the enum dropdown. The old value will be lost, and must be reset. This affects dozens of PlayFab blueprint nodes.~~ (UPDATED: This SDK is deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
 ### API changes
 
@@ -757,19 +757,19 @@ Date: 2016-04-24
 ### Cocos2d-xSDK specific changes
 
 - [Cocos2d-xSDK](https://github.com/PlayFab/Cocos2d-xSDK)
-  - Cocos SDK has been overhauled.
-  - New testing framework, internal Http functionality has been converted.
+  - Overhauled the Cocos SDK.
+  - New testing framework, converted internal Http functionality.
   - Android, iOS, and Win32 platforms are all working.
   - Lots of other small fixes and improvements.
 
-~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED: This SDK is deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
 - ~~UnrealBlueprintSdk is nearing the end of its limited-support Beta period. As such, there will be some potentially breaking changes in the next few releases.~~
-- ~~There are data fields in the Api-specification defined as enums. Formerly, UnrealBlueprintSdk displayed these fields as arbitrary strings, and the user was expected to input the correct option. This has been fixed. All these fields have been converted to be enum-dropdowns in the blueprints.~~
+- ~~There are data fields in the Api-specification defined as enums. Formerly, UnrealBlueprintSdk displayed these fields as arbitrary strings, and the user was expected to input the correct option. This is fixed. All these fields are converted to be enum-dropdowns in the blueprints.~~
 
 ## 160414  
 
-Date: 2016-04-13
+Date: April 13, 2016
 
 ### API changes
 
@@ -780,11 +780,11 @@ Date: 2016-04-13
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
   - More automated testing to improve stability of SDKs (and some associated bug fixes)
-  - Specifically, a new PlayStream test and making tests more consistent across all sdks.
+  - Specifically, a new PlayStream test and making tests more consistent across all SDKs.
 
 ## 160328  
 
-Date: 2016-03-27
+Date: March 27, 2016
 
 ### API changes
 
@@ -792,7 +792,7 @@ Date: 2016-03-27
 
 - Minor revisions in the way that CloudScript is uploaded via Admin-API.
 - Continuing to revise and define API limits and overage definitions where needed.
-- "PlayFabId" input has been removed from the documentation on a few client APIs, which never used that value.
+- Removed "PlayFabId" input from the documentation on a few client APIs, which never used that value.
 - Lots of minor documentation updates.
 - New `ExecuteCloudScript` API, which replaces the older pattern of `GetCloudScriptUrl+RunCloudScript`.
 - This should make it easier for novice users to call CloudScript correctly.
@@ -801,21 +801,21 @@ Date: 2016-03-27
 
 - [Cocos2d-xSDK](https://github.com/PlayFab/Cocos2d-xSDK)
   - Project folder structure updated to be consistent across all platforms.
-  - This fixes the issue where iOS build would fail to import some code files.
+  - This fixes the issue where iOS build fails to import some code files.
   - Cocos is now tested and working for Win32 and iOS.
 
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - Fixing inconsistent `#define` options which led to errors with `ReadAllText` function.
-  - Known Issue (not resolved): `SimpleJson` does not serialize correctly when using the Player Setting Scripting Back end option: `Mono2x`. Until this is fixed, please use `IL2CPP` if possible.
+  - Fixing inconsistent `#define` options that led to errors with `ReadAllText` function.
+  - Known Issue (not resolved): `SimpleJson` doesn't serialize correctly when using the Player Setting Scripting Back end option: `Mono2x`. Until this is fixed, use `IL2CPP` if possible.
   - (A similar issue may be present when building for PlayStation&#174;.)
 
 "PlayStation" is a registered trademark or trademark of Sony Interactive Entertainment Inc.
 
 ## 160307  
 
-Date: 2016-03-06
+Date: March 6, 2016
 
 ### API changes
 
@@ -840,7 +840,7 @@ Date: 2016-03-06
 
 ## 160222  
 
-Date: 2016-02-21
+Date: February 21, 2016
 
 ### API changes
 
@@ -860,23 +860,23 @@ Date: 2016-02-21
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
   - Updated Helper Function Signatures in the testing harness.
-  - Added structural changes to switch our internal JSON serializer from JSON.net to SimpleJson (This is an effort to enable Universal Windows Builds).
+  - Added structural changes to switch our internal JSON serializer from JSON.NET to SimpleJson (This is an effort to enable Universal Windows Builds).
 
 ## 160215  
 
-Date: 2016-02-14
+Date: February 14, 2016
 
 ### API changes
 
 - Resettable Leaderboards and Player Statistics are now live.
-- `GetPlayFabIDsFromSteamIDs` accepts and returns string IDs for languages that cannot handle ulong values.
+- `GetPlayFabIDsFromSteamIDs` accepts and returns string IDs for languages that can't handle ulong values.
 
 - Minor changes to support Parse migrations.
 - Minor documentation adjustments.
 
 ## 160208  
 
-Date: 2016-02-07
+Date: February 7, 2016
 
 ### API changes
 
@@ -887,16 +887,16 @@ Date: 2016-02-07
   - `server.UnlockContainerItem`
   - `server.UnlockContainerItem`
   - `server.UnlockContainerInstance`
-- Added `admin.StatisticResetIntervalOption` for use in resetable leaderboards.
+- Added `admin.StatisticResetIntervalOption` for use in resettable leaderboards.
 
 ### UnitySdk specific changes
 
 - [UnitySdk](https://github.com/PlayFab/UnitySDK)
-  - Modified the project folder structure a bit, which may cause some file conflicts. Please see this [forum post](https://community.playfab.com/questions/321/206711137-Best-way-to-update-the-PlayFab-Unity-SDK-.html) for details.
+  - Modified the project folder structure a bit, which may cause some file conflicts. See this [forum post](https://community.playfab.com/questions/321/206711137-Best-way-to-update-the-PlayFab-Unity-SDK-.html) for details.
 
 ## 160201  
 
-Date: 2016-01-31
+Date: January 31, 2016
 
 ### API changes
 
@@ -912,7 +912,7 @@ Date: 2016-01-31
 
 ## 160125  
 
-Date: 2016-01-24
+Date: January 24, 2016
 
 ### API changes
 
@@ -922,22 +922,22 @@ Date: 2016-01-24
   - `Client.UpdateCharacterStatistics`
   - `Server.RevokeInventoryItem`
   - Fixed typo in `PurchaseItem___` -> `PurchaseItem___`.
-  - Updated `UserAccountInfo` to contain additional account details.
+  - Updated `UserAccountInfo` to contain more account details.
 
-~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealBlueprintSdk specific changes:**~~ (UPDATED: This SDK is deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
 - ~~Fixed a Client issue that prevented subsequent calls after login from working.~~
 
 ## 160118  
 
-Date: 2016-01-17
+Date: January 17, 2016
 
 ### API changes
 
-- New leaderboard apis are available:
+- New leaderboard APIs are available:
   - `GetLeaderboardAroundPlayer`
   - `GetFriendLeaderboardAroundPlayer`
-- Old leaderboard apis are deprecated:
+- Old leaderboard APIs are deprecated:
   - `GetFriendLeaderboardAroundCurrentUser`
   - `GetLeaderboardAroundCurrentUser`
 - Lots of minor documentation improvements.
@@ -956,7 +956,7 @@ Date: 2016-01-17
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
   - Deleted some internal testing systems (DemoScene folder) from the public SDK.
-  - We are prototyping new samples and event systems. Some of the underlying SDK changes are visible in the diff, but none of it is accessible yet. Stay tuned as it's almost done.
+  - We're prototyping new samples and event systems. Some of the underlying SDK changes are visible in the diff, but none of it's accessible yet. Stay tuned as it's almost done.
   - An alternate version of the unit-tests are available on the client, with client-only api calls.
 
 ### Cocos2d-xSDK & WindowsSDK/C++ specific changes
diff --git a/playfab-docs/release-notes/2017.md b/playfab-docs/release-notes/2017.md
index bb4132efa..91c496b8d 100644
--- a/playfab-docs/release-notes/2017.md
+++ b/playfab-docs/release-notes/2017.md
@@ -6,7 +6,7 @@ ms.author: jenelleb
 ms.date: 07/12/2018
 ms.topic: article
 ms.service: azure-playfab
-keywords: playfab, development, release, apis, features
+keywords: playfab, development, release, APIs, features
 ms.localizationpriority: medium
 ---
 
@@ -14,23 +14,23 @@ ms.localizationpriority: medium
 
 ## 171204  
 
-Date: 2017-12-04
+Date: December 4, 2017
 
 ### Unreal SDK changes (Cpp and Bp)
 
 - Updated both SDKs to **Unreal 4.18.1**.
-- Older versions will still work, but require un-commenting `#defines` in the \_.build.cs files.
+- Older versions still work, but require uncommenting `#defines` in the \_.build.cs files.
 
 ## 171127  
 
-Date: 2017-11-27
+Date: November 27, 2017
 
 ### API changes
 
 - An inventory feature allowing "Limited Edition" items is now released from beta.
 
-- This lets you define that only a fixed number of a particular `itemId` will be available in your game.
-- A virtual currency property has been removed from API methods that use "[ProfileModel](xref:titleid.playfabapi.com.client.accountmanagement.getplayerprofile#playerprofilemodel)", as that information was never actually provided or correct. It will return... someday.
+- This feature lets you define that only a fixed number of a particular `itemId` is available in your game.
+- Removed a virtual currency property from API methods that use "[ProfileModel](xref:titleid.playfabapi.com.client.accountmanagement.getplayerprofile#playerprofilemodel)", as that information is never provided or correct. It returns... someday.
 
 ### New API methods
 
@@ -39,7 +39,7 @@ Date: 2017-11-27
 - client.[GetPaymentToken](xref:titleid.playfabapi.com.client.playeritemmanagement.getpaymenttoken)
   - Used for [XSolla specific payment processing](../economy-monetization/economy/tutorials/non-receipt-payment-processing.md)
 - client.[ReportDeviceInfo](xref:titleid.playfabapi.com.client.analytics.reportdeviceinfo)
-  - This API method is not meant to be called directly. It is currently a built-in feature for Unity and Lumberyard SDKs. It can be disabled with the [API Policy](../api-references/api-access-policy.md). Additionally, we will be adding another option soon to disable in the title settings page in Game Manager.
+  - This API method isn't meant to be called directly. It's currently a built-in feature for Unity and Lumberyard SDKs. It can be disabled with the [API Policy](../api-references/api-access-policy.md). Additionally, we're adding another option soon to disable in the title settings page in Game Manager.
 
 ### Updated API method error codes
 
@@ -51,20 +51,20 @@ Date: 2017-11-27
 
 ### SDK specific updates
 
-- [UnitySdk](https://github.com/PlayFab/UnitySDK): We are now building all published unity package files with Unity 2017.2.0f3.
+- [UnitySdk](https://github.com/PlayFab/UnitySDK): We're now building all published unity package files with Unity 2017.2.0f3.
 - For testing, we internally updated to the latest for each major.minor version, from Unity 4.7.2f1 to 2017.1.2f1.
 - Unity Example Test Game Server: Fix applied to `HttpHelper` to fix SSL validation on `SignalR` requests.
 - [ActionScriptSDK](https://github.com/PlayFab/ActionScriptSDK): AirSdk in example updated to v27.
-- [Cocos2d-xSDK](https://github.com/PlayFab/Cocos2d-xSDK): We are still targeting 3.15.1, despite 3.16 Cocos release (stay tuned).
+- [Cocos2d-xSDK](https://github.com/PlayFab/Cocos2d-xSDK): We're still targeting 3.15.1, despite the 3.16 Cocos release (stay tuned).
 - SdkTestingCloudScript and [NodeSDK](https://github.com/PlayFab/NodeSDK): Updated the example VS projects to support VS/msbuild 2017.
-- WindowsSDK: This will be the last build of the nuget package targeting Visual Studio 2013:
-  - [WindowsSdk VS 2013 Nuget Package](https://www.nuget.org/packages/com.playfab.windowssdk.v120/1.19.171127)
-  - We are updating our automated build machines, and we won't be installing VS 2013 on the new ones.
-  - The [newer nuget package](https://www.nuget.org/packages/com.playfab.windowssdk.v140/) will continue to work on VS 2015 and 2017.
+- WindowsSDK: This is the last build of the NuGet package targeting Visual Studio 2013:
+  - [WindowsSdk VS 2013 NuGet Package](https://www.NuGet.org/packages/com.playfab.windowssdk.v120/1.19.171127)
+  - We're updating our automated build machines, and we aren't installing VS 2013 on the new ones.
+  - The [newer NuGet package](https://www.NuGet.org/packages/com.playfab.windowssdk.v140/) will continue to work on VS 2015 and 2017.
 
 ## 171106  
 
-Date: 2017-11-06
+Date: November 6, 2017
 
 ### New API methods
 
@@ -73,16 +73,16 @@ Date: 2017-11-06
 
 ### Updated PlayStream event
 
-- [sent_email](../api-references/events/sent-email.md) gains new fields: Body, and Subject.
+- [sent_email](../api-references/events/TitleCommunications/sent-email.md) gains new fields: Body, and Subject.
 
 ### All SDKs
 
 - **MINOR SDK BREAKING CHANGE:** `ForgetClientCredentials()` renamed to `ForgetAllCredentials()`.
-- This is part of a "coming soon" feature, which will be announced when complete.
+- This is part of a "coming soon" feature, which is announced when complete.
 
 ## 171102
 
-Date: 2017-11-02
+Date: November 2, 2017
 
 ### New PlayFab feature
 
@@ -103,36 +103,36 @@ Date: 2017-11-02
 
 ### New PlayStream events
 
-- [auth_token_validated](../api-references/events/auth-token-validated.md)
-- [player_updated_contact_email](../api-references/events/player-updated-contact-email.md)
-- [sent_email](../api-references/events/sent-email.md)
+- [auth_token_validated](../api-references/events/PlayerIdentity/auth-token-validated.md)
+- [player_updated_contact_email](../api-references/events/PlayerIdentity/player-updated-contact-email.md)
+- [sent_email](../api-references/events/TitleCommunications/sent-email.md)
 
 ### Unreal specific update
 
-- Our auto builder failed to publish the Unreal SDKs for build number 171016 and 171026. The issue with our auto-builder has been resolved, and version 171026 has been published after the fact, and releases will resume normally
+- Our auto builder failed to publish the Unreal SDKs for build number 171016 and 171026. We resolved the issue with our auto-builder, published version 171026 after the fact, and releases resumed normally
 
 ### Unity specific changes
 
-- **MINOR BREAKING CHANGE:** `ForgetClientCredentials` has been renamed to `ForgetAllCredentials`.
-- This is part of a new feature that will be coming soon. `ForgetClientCredentials` will be renamed to `ForgetAllCredentials` in all SDKs over the next few releases.
+- **MINOR BREAKING CHANGE:** Renamed `ForgetClientCredentials` to `ForgetAllCredentials`.
+- This is part of a new feature coming soon. We're renaming `ForgetClientCredentials` to `ForgetAllCredentials` in all SDKs over the next few releases.
 
 ## 171026  
 
-Date: 2017-10-26
+Date: October 26, 2017
 
 ### API documentation changes
 
 - Updating error codes for API methods.
 
-- Many error codes that are universal to all API methods have been removed from the per-API-method list. A new page will be made which describes universal error codes.
+- Removed many error codes that are universal to all API methods from the per-API-method list. A new page describes universal error codes.
 - **Removed Universal Codes:**
   - InvalidParams
   - OverLimit
   - DataUpdateRateExceeded
   - AccountBanned
 - These errors (and others, to be published in a separate document), can be returned from any API method and should be handled appropriately.
-- New error codes have been added to several dozen API methods, and a few false codes removed. The error code lists should be much more accurate for method-specific error returns. This is still an ongoing process, so there will be more updates.
-- Several API methods involving virtual currency can decrease the balance below zero. These have been labeled appropriately.
+- Added new error codes to several dozen API methods, and removed a few false codes. The error code lists should be much more accurate for method-specific error returns. This is still an ongoing process, so there are more updates.
+- Several API methods involving virtual currency can decrease the balance to less than zero. We labeled these appropriately.
 
 ### API changes
 
@@ -144,12 +144,12 @@ Date: 2017-10-26
 
 ### Game Manager changes
 
-- You can now delete titles using the new Admin/DeleteTitle API, or on the Game Manager studios page, as shown below.
+- You can now delete titles using the new Admin/DeleteTitle API, or on the Game Manager studios page, as shown in the following image.
    ![DelTitleGameManager](images/171026-DelTitleGameManager.png)
 
 ## 171016  
 
-Date: 2017-10-16
+Date: October 16, 2017
 
 ### API changes
 
@@ -158,8 +158,8 @@ Date: 2017-10-16
 
 ### New PlayStream events
 
-- [player_started_purchase](../api-references/events/player-started-purchase.md)
-- [player_paid_for_purchase](../api-references/events/player-paid-for-purchase.md)
+- [player_started_purchase](../api-references/events/Player/player-started-purchase.md)
+- [player_paid_for_purchase](../api-references/events/Player/player-paid-for-purchase.md)
 
 ### JavaScriptSDK specific changes
 
@@ -169,16 +169,16 @@ Date: 2017-10-16
 ### LuaSDK specific changes
 
 - [LuaSDK](https://github.com/PlayFab/LuaSDK)
-  - Our Lua publish pipeline has been fixed, and LuaSDK is being updated properly again.
+  - Fixed our Lua publish pipeline, and LuaSDK is being updated properly again.
 
 ### UnitySdk specific changes
 
 - [UnitySdk](https://github.com/PlayFab/UnitySDK)
-  - A [regression in Unity](https://issuetracker.unity3d.com/issues/unitywebrequest-getresponseheaders-method-returns-null-on-android-devices) has been handled on our side, and should no longer affect PlayFab customers.
+  - We handled a [regression in Unity](https://issuetracker.unity3d.com/issues/unitywebrequest-getresponseheaders-method-returns-null-on-android-devices) on our side, and it should no longer affect PlayFab customers.
 
-~~**UnrealCppSdk specific changes:**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealCppSdk specific changes:**~~ (UPDATED : This SDK is deprecated. For the new unreal SDK, refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
-- ~~One of our customers has made an add-on plugin to our SDK which integrates the Unreal OnlineSubsystem & the PlayFab SDK~~
+- ~~One of our customers has made an add-on plugin to our SDK, which integrates the Unreal OnlineSubsystem & the PlayFab SDK~~
 - ~~You can check it out [here](https://gitlab.com/mtuska/OnlineSubsystemPlayFab).~~
 
 ### Unicorn Battle example
@@ -187,30 +187,30 @@ Date: 2017-10-16
 
 ## 170925  
 
-Date: 2017-09-05
+Date: September 5, 2017
 
 ### API Changes
 
-- A handful of beta APIs that were never made public have been removed. This should not affect any current customers or live titles.
+- Removed a handful of beta APIs that were never made public. This shouldn't affect any current customers or live titles.
 - We bypassed the default language-level header checks in our CloudScript engine. This means several CloudScript http.request() headers that were formerly being rejected should now work.
 
 ### Global Push Notification update
 
-- Please see [our blog](https://blog.playfab.com/blog/push-sep-17) for details about the improvements to Push Notifications
+- See [our blog](https://blog.playfab.com/blog/push-sep-17) for details about the improvements to Push Notifications
 
 ### New PlayStream events
 
-- [player_device_info](../api-references/events/player-device-info.md)
+- [player_device_info](../api-references/events/PlayerIdentity/player-device-info.md)
 - Games using the latest UnitySDK can now see some basic analytics data about their customers. SnowFlake is ideal for viewing and analyzing this information, but it's also available in the PlayStream Event History.
 - player_updated_membership
 
 ### JavaScriptSDK specific changes
 
 - [JavaScriptSDK](https://github.com/PlayFab/JavaScriptSDK)
-  - A handful of mini-features that exist in other SDKs have been added to JavaScriptSDK:
+  - Added a handful of mini-features that exist in other SDKs to JavaScriptSDK:
   - You can now inject extra headers into requests (removing one of the blockers for Double Encrypted Logins with this SDK).
   - Added a new function: `PlayFabClientSDK.ForgetClientCredentials()`
-  - This is a convenience function that allows you to reset the client after shutting down or logging out.
+  - This is a convenience function that resets the client after shutting down or logging out.
   - `PlayFab.GenerateErrorReport()`
   - This is a convenience function that converts the error-result from a failed PlayFab call into a single complete description of how the call failed.
 - Added optional data relays into the PlayFab API requests:
@@ -222,40 +222,40 @@ Date: 2017-09-05
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - New experimental feature: This release of PlayFab UnitySDK now optionally allows you to see device information for your players. Example information you can see is: memory, resolution, user-agent, device-type, OS version, etc.
+  - New experimental feature: This release of PlayFab UnitySDK now optionally lets you see device information for your players. Example information you can see is: memory, resolution, user-agent, device-type, OS version, etc.
 
-~~**UnrealCppSdk specific changes:**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealCppSdk specific changes:**~~ (UPDATED : This SDK is deprecated. For the new unreal SDK, refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
 - ~~Updated to Unreal 4.17~~
-- ~~Split apart into 3 separate plugins, each with different functionality~~
-- ~~Pretty significant upgrades overall~~
+- ~~Split apart into three separate plugins, each with different functionality~~
+- ~~Significant upgrades overall~~
 
 ## 170828  
 
-Date: 2017-08-28
+Date: August 28, 2017
 
 ### Client API changes
 
-- ~~client.[GetCurrentGames].[result].Games[i].GameServerState has been deprecated, and replaced with [GameServerStateEnum]~~.
+- ~~client.[GetCurrentGames].[result].Games[i].GameServerState is deprecated, and replaced with [GameServerStateEnum]~~.
 ~~- GameServerState was serialized as an integer, which was an error. The new field is a proper enum-string.~~ (UPDATED: This is deprecated. See [Servers](../multiplayer/servers/index.md))
 
 ### Other API changes
 
-- The following API methods have been deprecated on Admin and Server APIs.
-  - [GetActionsOnPlayersInSegmentTaskInstance](xref:titleid.playfabapi.com.admin.scheduledtask.getactionsonplayersinsegmenttaskinstance) - This has accidentally been labeled as deprecated, but that was an error which will be reverted.
+- Deprecated the following API methods on Admin and Server APIs.
+  - [GetActionsOnPlayersInSegmentTaskInstance](xref:titleid.playfabapi.com.admin.scheduledtask.getactionsonplayersinsegmenttaskinstance) - This has accidentally been labeled as deprecated, but that was an error that is reverted.
 - [SendPushNotification](xref:titleid.playfabapi.com.server.accountmanagement.sendpushnotification) can now specify [TargetPlatforms](xref:titleid.playfabapi.com.server.accountmanagement.sendpushnotification#sendpushnotificationrequest)
-- Added some clarifications for which parameters work on which platforms for [SendPushNotificationRequest](xref:titleid.playfabapi.com.server.accountmanagement.sendpushnotification#sendpushnotificationrequest) (Using parameters not supported for a target platform is not recommended).
+- Added some clarifications for which parameters work on which platforms for [SendPushNotificationRequest](xref:titleid.playfabapi.com.server.accountmanagement.sendpushnotification#sendpushnotificationrequest) (Using parameters not supported for a target platform isn't recommended).
 - Added some info about [Shared Group](xref:titleid.playfabapi.com.client.sharedgroupdata.createsharedgroup) [restrictions](../community/associations/groups/using-shared-group-data.md) to the Shared Group documentation (specifically that they can't be used for anything like Guilds).
 - [Player Profiles](xref:titleid.playfabapi.com.client.accountmanagement.getplayerprofile#playerprofilemodel) can now store a player [contact email address](xref:titleid.playfabapi.com.client.accountmanagement.getplayerprofile#contactemailinfomodel).
 
 ### New PlayStream events
 
-- [entity_created](../api-references/events/entity-created.md)
-- [entity_logged_in](../api-references/events/entity-logged-in.md)
+- [entity_created](../api-references/events/PlayerIdentity/entity-created.md)
+- [entity_logged_in](../api-references/events/PlayerIdentity/entity-logged-in.md)
 
 ## 170814  
 
-Date: 2017-08-14
+Date: August 14, 2017
 
 ### API updates
 
@@ -263,12 +263,12 @@ Date: 2017-08-14
 
 ### CSharpSdk specific updates
 
-- SDK now includes a file called [NewtonSoftJsonWrapper.cs](https://github.com/PlayFab/CSharpSDK/blob/master/PlayFabSDK/source/Json/NewtonsoftWrapper.cs) which will let you swap out our included SimpleJson serializer with the NewtonSoft nuget package.
+- SDK now includes a file called [NewtonSoftJsonWrapper.cs](https://github.com/PlayFab/CSharpSDK/blob/master/PlayFabSDK/source/Json/NewtonsoftWrapper.cs), which will let you swap out our included SimpleJson serializer with the NewtonSoft NuGet package.
 - The file includes instructions on how to use it.
 
 ## 170807  
 
-Date: 2017-08-07
+Date: August 7, 2017
 
 ### New API methods
 
@@ -276,7 +276,7 @@ Date: 2017-08-07
 
 ### Deprecated API methods
 
-- These API methods never worked as fully and completely as they were supposed to. In an effort to clean this up, we've started over, and built the new [DeletePlayer](xref:titleid.playfabapi.com.admin.accountmanagement.deleteplayer) API above, and these are deprecated:
+- These API methods never worked as fully and completely as they were supposed to. To clean this up, we've started over, and built the new [DeletePlayer](xref:titleid.playfabapi.com.admin.accountmanagement.deleteplayer) API in the preceding section, and these are deprecated:
 - `admin.ResetUsers`
 - `admin.DeleteUsers`
 
@@ -286,29 +286,29 @@ Date: 2017-08-07
 
 ### PlayStream events
 
-- New Event: [auth_token_validated](../api-references/events/auth-token-validated.md)
-- New Event: [player_removed_title](../api-references/events/player-removed-title.md)
-- New Event: [player_updated_contact_email](../api-references/events/player-updated-contact-email.md)
-- New Event: [player_verified_contact_email](../api-references/events/player-verified-contact-email.md)
-- New Event: [sent_email](../api-references/events/sent-email.md) (Still in beta, but events are already public)
-- New Field in Event: [player_realmoney_purchase](../api-references/events/player-realmoney-purchase.md).TransactionId
+- New Event: [auth_token_validated](../api-references/events/PlayerIdentity/auth-token-validated.md)
+- New Event: [player_removed_title](../api-references/events/PlayerIdentity/player-removed-title.md)
+- New Event: [player_updated_contact_email](../api-references/events/PlayerIdentity/player-updated-contact-email.md)
+- New Event: [player_verified_contact_email](../api-references/events/PlayerIdentity/player-verified-contact-email.md)
+- New Event: [sent_email](../api-references/events/TitleCommunications/sent-email.md) (Still in beta, but events are already public)
+- New Field in Event: [player_realmoney_purchase](../api-references/events/Player/player-realmoney-purchase.md).TransactionId
 
 ~~**LumberyardSdk changes:**~~
 
 - ~~**UPGRADE WARNING:** This SDK is no longer compatible with previous versions of Lumberyard.~~
-- ~~This release of PlayFab LumberyardSdk no longer works with Lumberyard version 1.3. It has been upgraded and now targets Lumberyard 1.9. We will very likely have it targeting 1.10 in the near future, but again without backwards compatibility to 1.9 or earlier. See [our blog](https://blog.playfab.com/blog/cpp-sdk-updates) for details.~~
+- ~~This release of PlayFab LumberyardSdk no longer works with Lumberyard version 1.3. It's upgraded and now targets Lumberyard 1.9. We'll likely have it targeting 1.10 soon, but again without backwards compatibility to 1.9 or earlier. See [our blog](https://blog.playfab.com/blog/cpp-SDK-updates) for details.~~
 
-~~**UnrealCppSdk:**~~ (**UPDATED**: This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk)).
+~~**UnrealCppSdk:**~~ (**UPDATED**: This SDK is deprecated. For the new unreal SDK, refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK)).
 
-<!-- ~~This SDK has been discontinued, and will no longer be maintained. We will produce an upgrade guide so that users can switch to the UnrealBlueprintSdk. Please see this blog for more details.~~
+<!-- ~~This SDK is discontinued, and will no longer be maintained. We will produce an upgrade guide so that users can switch to the UnrealBlueprintSdk. See this blog for more details.~~
 - ~~See our [upgrade guide](https://github.com/PlayFab/UnrealBlueprintSDK/blob/master/UnrealCppSdkUpgradeGuide.md)~~-->
 
-~~**Unreal SDK:**~~ (**UPDATED**: This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**Unreal SDK:**~~ (**UPDATED**: This SDK is deprecated. For the new unreal SDK, refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
 - ~~The PlayFab UnrealBlueprintSdk is now rebranded as the "Unreal SDK"~~
-- ~~Unreal SDK has been updated to 4.16, with some minor fixes~~
+- ~~Unreal SDK is updated to 4.16, with some minor fixes~~
 - ~~We're also removing support for older versions of Unreal, which require older versions of Visual Studio~~
-- ~~We now support 4.14 thru 4.16~~
+- ~~We now support 4.14 through 4.16~~
 - ~~Your project may continue working for older versions of Visual Studio, but we can only support and test Visual Studio 2015 and later~~
 - ~~Read [our blog](https://blog.playfab.com/blog/visual-studio-2013-deprecation-notice) for more info~~
 
@@ -319,11 +319,11 @@ Date: 2017-08-07
 
 ## 170710  
 
-Date: 2017-07-10
+Date: July 10, 2017
 
 ### API changes
 
-- An Enterprise feature for double-encrypted logins has been released from beta, and is now live.
+- Released an Enterprise feature for double-encrypted logins from beta, and it's now live.
 - **New API methods:**
   - admin.[CreatePlayerSharedSecret](xref:titleid.playfabapi.com.admin.authentication.createplayersharedsecret)
   - admin.[DeletePlayerSharedSecret](xref:titleid.playfabapi.com.admin.authentication.deleteplayersharedsecret)
@@ -338,17 +338,17 @@ Date: 2017-07-10
 
 ### SDK breaking change
 
-- admin.[SetupPushNotificationRequest](xref:titleid.playfabapi.com.admin.title-widedatamanagement.setuppushnotification#setuppushnotificationrequest).Platform is now defined as an enum instead of a string. This is not a breaking change to the API (as enums are transmitted as strings), but it will require some users to convert their strings to the enum values in their code.
+- admin.[SetupPushNotificationRequest](xref:titleid.playfabapi.com.admin.title-widedatamanagement.setuppushnotification#setuppushnotificationrequest).Platform is now defined as an enum instead of a string. This isn't a breaking change to the API (as enums are transmitted as strings), but it requires some users to convert their strings to the enum values in their code.
 
 ### Changes in all SDKs
 
-- Minor SDK Breaking Change: Most SDKs have lost an optional field in multiple requests called UseSpecificVersion, which was an alternate way to define the adjacent Version field as null. Not all languages have the capability to define an integer as null in the request, and this field was only meant to be useful in relevant SDKs (Specifically Unreal). If you are using this field, just remove it, and set the adjacent Version field to null when appropriate.
+- Minor SDK Breaking Change: Most SDKs have lost an optional field in multiple requests called UseSpecificVersion, which was an alternate way to define the adjacent Version field as null. Not all languages have the capability to define an integer as null in the request, and this field was only meant to be useful in relevant SDKs (Specifically Unreal). If you're using this field, just remove it, and set the adjacent Version field to null when appropriate.
 
 ### Unity EditorExtensions update
 
-- The flags panel has been updated.
+- Updated the flags panel.
 - `ENABLE/DISABLE_IDFA` flag can be toggled now.
-- Displays non-PlayFab flags, and allows you to remove them (use with caution, don't remove flags you need).
+- Displays non-PlayFab flags, and lets you remove them (use with caution, don't remove flags you need).
 
 ### SDK Dependency updates
 
@@ -357,38 +357,38 @@ Date: 2017-07-10
 - [ActionScriptSDK](https://github.com/PlayFab/ActionScriptSDK) tested with AirSDK v26.
   - SDK unchanged, example updated to target v26.
 - [Cocos2d-xSDK](https://github.com/PlayFab/Cocos2d-xSDK) built, and tested with Cocos 3.15.1.
-- Cocos 3.14->3.15 contained changes that broke our example, which in turn meant the example had to be updated. The example still works with 3.13 thru 3.15, but the example probably won't work with older versions of Cocos SDK unchanged, and should continue to work with most of the latest 3.X Cocos versions.
+- Cocos 3.14->3.15 contained changes that broke our example, which in turn meant the example had to be updated. The example still works with 3.13 through 3.15, but the example might not work with older versions of Cocos SDK unchanged, and should work with most of the latest 3.X Cocos versions.
 
 ## 170612  
 
-Date: 2017-06-12
+Date: June 12, 2017
 
 ### Documentation changes
 
 - Many small revisions to dozens of API methods for clarity
-- Several documentation-groupings, each which only contained a single API method, have been merged into a single group called "Platform Specific Methods".
-- The "Matchmaking  APIs" group has been renamed to "Matchmaking" to be consistent with other groups.
+- Merged several documentation-groupings, each of which only contained a single API method, into a single group called "Platform Specific Methods".
+- Renamed the "Matchmaking APIs" group to "Matchmaking" to be consistent with other groups.
 - Many length-restricted string fields now describe the allowed ranges.
 
 ### Changes in all SDKs
 
-- Lots of broken links in all SDK readme's have been updated and fixed.
+- Updated and fixed lots of broken links in all SDK READMEs.
 
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
   - We now support multiple versions of the Android API and Google Play Services. Read more details [here](https://github.com/PlayFab/UnitySDK/tree/master/Packages).
-  - This concludes the planned changes to the Unity + Android Push-Plugin for now. Please let us know if you have any additional requests [here](https://community.playfab.com/questions/10840/android-plugin-upgrade-discussion.html).
+  - This concludes the planned changes to the Unity + Android Push-Plugin for now. Let us know if you have any more requests [here](https://community.playfab.com/questions/10840/android-plugin-upgrade-discussion.html).
 
 ## 170530  
 
-Date: 2017-05-30
+Date: May 30, 2017
 
 ### API changes
 
-- **BREAKING CHANGE:** In server.[ReportPlayer](xref:titleid.playfabapi.com.server.playeritemmanagement.reportplayer), the `titleId` field in  [ReportPlayerServerRequest](xref:titleid.playfabapi.com.server.playeritemmanagement.reportplayer#reportplayerserverrequest) has been immediately removed (not merely deprecated). All reports will now go to their own title, and cannot report to another title.
+- **BREAKING CHANGE:** In server.[ReportPlayer](xref:titleid.playfabapi.com.server.playeritemmanagement.reportplayer), we immediately removed the `titleId` field in [ReportPlayerServerRequest](xref:titleid.playfabapi.com.server.playeritemmanagement.reportplayer#reportplayerserverrequest) (not merely deprecated). All reports now go to their own title, and can't report to another title.
   - This had to be a breaking change as it was otherwise a mild cross-title exploit. [Contact us](https://community.playfab.com/questions/ask.html) if you need assistance with this change.
-- In client.[ReportPlayer](xref:titleid.playfabapi.com.client.accountmanagement.reportplayer) and server.[ReportPlayer](xref:titleid.playfabapi.com.server.playeritemmanagement.reportplayer), result.Updated has been deprecated in both cases. It was always true, and the API Call would always return an error if the player was over the report limit. This error condition has been updated to be OverLimit to match other limits.
+- In client.[ReportPlayer](xref:titleid.playfabapi.com.client.accountmanagement.reportplayer) and server.[ReportPlayer](xref:titleid.playfabapi.com.server.playeritemmanagement.reportplayer), we deprecated result.Updated in both cases. It's always true, and the API Call returns an error if the player is over the report limit. We changed this error condition to OverLimit to match other limits.
 - All [login methods](xref:titleid.playfabapi.com.client.authentication) can now return a [player profile object](xref:titleid.playfabapi.com.client.authentication.loginwithandroiddeviceid#playerprofilemodel), if requested, which contains information previously only available to leaderboard results.
 
 ### New API methods
@@ -405,81 +405,81 @@ Date: 2017-05-30
 
 - gameserverhost_started
 - gameserverhost_stopped
-- [player_set_profile_property](../api-references/events/player-set-profile-property.md)
+- [player_set_profile_property](../api-references/events/Player/player-set-profile-property.md)
 
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - Our Android Push plugin has been overhauled.
+  - Overhauled our Android Push plugin.
   - [Blog Post](https://blog.playfab.com/blog/push-upgrade-5-22)
   - [New/Updated Guide](../live-service-management/game-configuration/title-communications/push-notifications/push-notifications-for-android.md)
 
 ### CSharpSDK specific changes
 
 - [CSharpSDK](https://github.com/PlayFab/CSharpSDK)
-  - It is now possible to specify extra headers that will be injected into an API request.
+  - It's now possible to specify extra headers that are injected into an API request.
   - This is an Enterprise-Only feature, specifically for double-encrypted login requests.
 
 ## 170508  
 
-Date: 2017-05-08
+Date: May 8, 2017
 
 ### API changes
 
 - **BREAKING CHANGE:**
-  - [ExecuteCloudScript](xref:titleid.playfabapi.com.client.server-sidecloudscript.executecloudscript) will not serialize the return value of your call, if it is too large.
-  - [ExecuteCloudScript](xref:titleid.playfabapi.com.client.server-sidecloudscript.executecloudscript) will not serialize the logs for your call, if they are too large.
-- Under either of these conditions, the call will still return 200/successful, but the FunctionResult and/or Logs properties will be null.
+  - [ExecuteCloudScript](xref:titleid.playfabapi.com.client.server-sidecloudscript.executecloudscript) doesn't serialize the return value of your call if it's too large.
+  - [ExecuteCloudScript](xref:titleid.playfabapi.com.client.server-sidecloudscript.executecloudscript) doesn't serialize the logs for your call if they're too large.
+- Under either of these conditions, the call still returns 200/successful, but the FunctionResult and/or Logs properties are null.
 
 ### PlayStream event changes
 
-- [player_vc_item_purchased](../api-references/events/player-vc-item-purchased.md) and [character_vc_item_purchased](../api-references/events/character-vc-item-purchased.md) now contain a StoreId parameter indicating which store was used to make a purchase.
+- [player_vc_item_purchased](../api-references/events/Player/player-vc-item-purchased.md) and [character_vc_item_purchased](../api-references/events/Character/character-vc-item-purchased.md) now contain a StoreId parameter indicating which store was used to make a purchase.
 - **New event:**
-  - [title_profile_view_constraints_changed](../api-references/events/title-profile-view-constraints-changed.md)
+  - [title_profile_view_constraints_changed](../api-references/events/PlayerIdentity/title-profile-view-constraints-changed.md)
 
 ### CSharpSDK updates
 
 - [CSharpSDK](https://github.com/PlayFab/CSharpSDK)
-  - Some unused source files in [CSharpSDK](https://github.com/PlayFab/CSharpSDK) have been deleted.
-  - This should not affect any existing projects, or the Nuget package, as those files were not referenced by the Visual Studio Solution.
+  - Deleted some unused source files in [CSharpSDK](https://github.com/PlayFab/CSharpSDK).
+  - This shouldn't affect any existing projects, or the NuGet package, as those files weren't referenced by the Visual Studio Solution.
 
 ### Postman collection update
 
-- Several common request parameters now utilize environment variables.
+- Several common request parameters now use environment variables.
 - Specifically, TitleId={{TitleId}}, PlayFabId={{PlayFabId}}, CharacterId={{CharacterId}}, and CatalogVersion={{PrimaryCatalogName}}
 
 ## 170424  
 
-Date: 2017-04-24
+Date: April 24, 2017
 
 ### SDK hotfix release
 
 - **[JavaSDK](https://github.com/PlayFab/JavaSDK) Updates:**
   - We now publish Jar files for the SDK, one for code, and one for Java docs, which you can import into your Java project instead of copy-pasting code. Thanks to Will Iverson <!--(https://gamestudioone.com/)--> for helping us improve our [JavaSDK](https://github.com/PlayFab/JavaSDK) usability
 - **UnityEditorExtensions updates:**
-  - We have resolved some install-time exceptions. Specifically it is no longer required that you restart Unity after a first-time install.
+  - We've resolved some install-time exceptions. Specifically it's no longer required that you restart Unity after a first-time install.
   - Additionally, an issue where the Client API was sometimes disabled inappropriately is now fixed. (edited)
-- ~~**UnrealCppSdk Updates:**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+- ~~**UnrealCppSdk Updates:**~~ (UPDATED : This SDK is deprecated. For the new unreal SDK, refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 - ~~The titleId is now available from the Plugin interface~~
 
 ## 170411  
 
-Date: 2017-04-11
+Date: April 11, 2017
 
 ### API changes
 
-- New Enterprise Feature: Additional login encryption
-- You can utilize the Policy API methods to enforce Login Calls can require a second layer of encryption
+- New Enterprise Feature: More login encryption
+- You can use the Policy API methods to enforce Login Calls can require a second layer of encryption
 - See: [UpdatePolicy](xref:titleid.playfabapi.com.admin.authentication.updatepolicy) , specifically [UpdatePolicyRequest](xref:titleid.playfabapi.com.admin.authentication.updatepolicy#updatepolicyrequest).[Statements](xref:titleid.playfabapi.com.admin.authentication.updatepolicy#permissionstatement).[ApiConditions](xref:titleid.playfabapi.com.admin.authentication.updatepolicy#apicondition)
-- This feature is still partially in beta, and activating it is not suggested (yet - Coming Soon!)
+- This feature is still partially in beta, and activating it isn't suggested (yet - Coming Soon!)
 
 ### New PlayStream events
 
-- [player_receipt_validation](../api-references/events/player-receipt-validation.md)
+- [player_receipt_validation](../api-references/events/Player/player-receipt-validation.md)
 
 ### UnitySDK specific changes
 
-- It is now possible to specify extra headers that will be injected into an API request (This is required for the encrypted login calls above).
+- It's now possible to specify extra headers that are injected into an API request (This is required for the encrypted login calls in the preceding section).
 
 ### UnityEditorExtensions specific changes
 
@@ -487,56 +487,56 @@ Date: 2017-04-11
 
 ## 170406  
 
-Date: 2017-04-06
+Date: April 6, 2017
 
 ### Hot Fix for Unity Android Push plugin
 
 - Fixed Android 7.0+ Crash Bug.
-- Fixed Android missing Large Icon support ( Lollipop + ).
-- Fixed Android Small Icon support on Android 7.0+ ( now supports \_transparent.png ).
+- Fixed Android missing Large Icon support (Lollipop+).
+- Fixed Android Small Icon support on Android 7.0+ (now supports \_transparent.png).
 
 ## 170403  
 
-Date: 2017-04-03
+Date: April 3, 2017
 
 ### API changes
 
 - **Client & Server Leaderboard Methods:** Get-Leaderboard methods (such as client.[GetLeaderboard](xref:titleid.playfabapi.com.client.playerdatamanagement.getleaderboard)) previously gained new non-nullable parameters Version and UseSpecificVersion. The requirement that they were non-nullable was an API-breaking change. We have updated these properties to be fully optional.
-- **Client API:** The Items field of [GetPurchaseResult](xref:titleid.playfabapi.com.client.playeritemmanagement.getpurchase#getpurchaseresult) will be deprecated: This portion of the result is often incorrect or incomplete. It will eventually be replaced with a fully functional parameter.
+- **Client API:** The Items field of [GetPurchaseResult](xref:titleid.playfabapi.com.client.playeritemmanagement.getpurchase#getpurchaseresult) is deprecated: This portion of the result is often incorrect or incomplete. It's eventually replaced with a fully functional parameter.
 
 ### New PlayStream events
 
 - `player_display_name_filtered`
 
-~~**Unreal Specific Changes:**~~ (**UPDATED** : This SDK has been deprecated. For the new Unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**Unreal Specific Changes:**~~ (**UPDATED** : This SDK is deprecated. For the new Unreal SDK, refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
-- ~~UnrealCppSdk: An issue where PlayFab settings such as TitleId were lost when publishing a build has been fixed.
-Both SDKs have been tested and verified working with Unreal 4.15~~
+- ~~UnrealCppSdk: An issue where PlayFab settings such as TitleId were lost when publishing a build is fixed.
+Both SDKs are tested and verified working with Unreal 4.15~~
 
 ### JavaSDK specific changes
 
 - [JavaSDK](https://github.com/PlayFab/JavaSDK)
-  - [JavaSDK](https://github.com/PlayFab/JavaSDK) folder structure and testing has been restructured.
+  - Restructured [JavaSDK](https://github.com/PlayFab/JavaSDK) folder structure and testing.
   - The internal folder structure of the repo has changed a bit to accommodate Maven best practices.
   - Dependencies are now Maven controlled and no longer included with the SDK.
-  - Our internal automated testing has been converted to Maven command line.
-  - Our SDK is NOT available on Maven Central, as that effort has faltered. There is no ETA for completion at this time.
+  - Converted our internal automated testing to Maven command line.
+  - Our SDK isn't available on Maven Central, as that effort has faltered. There's no ETA for completion at this time.
 
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - Internal Unity version for testing and building asset bundles updated to 5.6.0. Our Unity SDK remains compatible with all versions of Unity from 4.7 thru 5.6.
-  - A compile issue with `UnityEditorExtensions` in Unity 5.6 has been fixed.
+  - Internal Unity version for testing and building asset bundles updated to 5.6.0. Our Unity SDK remains compatible with all versions of Unity from 4.7 through 5.6.
+  - Fixed a compile issue with `UnityEditorExtensions` in Unity 5.6.
 
 ## 170223  
 
-Date: 2017-02-22
+Date: February 22, 2017
 
 ### API changes
 
 - PlayFab leaderboards now store an avatar url for every player. This can be used to reference a player image for leaderboard entries.
-- All leaderboard APIs can now fetch a specific version of the leaderboard. This is for titles which are set to use Resetting Leaderboards.
-- Leaderboard entries now contain the [PlayerProfile](xref:titleid.playfabapi.com.client.accountmanagement.getplayerprofile#playerprofilemodel) which can be used to display more detailed leaderboards without additional API calls
+- All leaderboard APIs can now fetch a specific version of the leaderboard. This is for titles that are set to use Resetting Leaderboards.
+- Leaderboard entries now contain the [PlayerProfile](xref:titleid.playfabapi.com.client.accountmanagement.getplayerprofile#playerprofilemodel), which can be used to display more detailed leaderboards without extra API calls
 - PlayFab can now authenticate clients using Windows Hello and validate Windows store receipts
 
 ### New APIs
@@ -552,7 +552,7 @@ Date: 2017-02-22
 ```
 ### New PlayStream events
 
-- [player_changed_avatar](../api-references/events/player-changed-avatar.md)
+- [player_changed_avatar](../api-references/events/PlayerIdentity/player-changed-avatar.md)
 
 ### WindowsSDK specific changes
 
@@ -564,41 +564,41 @@ Date: 2017-02-22
 
 ## 170130  
 
-Date: 2017-01-29
+Date: January 29, 2017
 
 ### Breaking changes
 
-- The folder structure for [JavaScriptSDK](https://github.com/PlayFab/JavaScriptSDK) and [NodeSDK](https://github.com/PlayFab/NodeSDK) has been changed with today's major release. This may result in some broken connections for your project when you upgrade. (File names and file contents have not changed. New **TypeScript** files now exist, which did not exist before.)
+- Changed the folder structure for [JavaScriptSDK](https://github.com/PlayFab/JavaScriptSDK) and [NodeSDK](https://github.com/PlayFab/NodeSDK) with today's major release. This may result in some broken connections for your project when you upgrade. (File names and file contents didn't change. New **TypeScript** files now exist, which didn't exist before.)
 
 ### API changes
 
-- Added clarifying documentation to CDN APIs. Specifically mentioning that the CDN is not part of our free service.
+- Added clarifying documentation to CDN APIs. Specifically mentioning that the CDN isn't part of our free service.
 - Google login fixes (Blog Post Pending).
 
 ### New PlayStream events
 
 - `developer_logged_in`
 - `developer_registered`
-- [studio_created](../api-references/events/studio-created.md)
-- [studio_user_added](../api-references/events/studio-user-added.md)
-- [studio_user_invited](../api-references/events/studio-user-invited.md)
-- [studio_user_removed](../api-references/events/studio-user-removed.md)
+- [studio_created](../api-references/events/DeveloperIdentity/studio-created.md)
+- [studio_user_added](../api-references/events/DeveloperIdentity/studio-user-added.md)
+- [studio_user_invited](../api-references/events/DeveloperIdentity/studio-user-invited.md)
+- [studio_user_removed](../api-references/events/DeveloperIdentity/studio-user-removed.md)
 
 ### JavaScriptSDK specific changes
 
 - [JavaScriptSDK](https://github.com/PlayFab/JavaScriptSDK)
-  - Release day for a major upgrade!  Version number updated to 1.0.
+  - Release day for a major upgrade! Version number updated to 1.0.
   - TypeScript integration!
-  - Repository cleanup: Separating the sdk files from the example files.
-  - Our example project has been converted to TypeScript.
+  - Repository cleanup: Separating the SDK files from the example files.
+  - Converted our example project to TypeScript.
   - See [our blog](https://blog.playfab.com/blog/typescript/)!
 
 ### NodeSDK specific changes
 
 - [NodeSDK](https://github.com/PlayFab/NodeSDK)
-  - Release day for a major upgrade!  Version number updated to 1.0
+  - Release day for a major upgrade! Version number updated to 1.0
   - TypeScript integration!
-  - Our example project has been converted to TypeScript
+  - Converted our example project to TypeScript
   - See [our blog](https://blog.playfab.com/blog/typescript/)!
 
 ### CloudScript examples
@@ -607,14 +607,14 @@ Date: 2017-01-29
 - TypeScript integration!
 - See [our blog](https://blog.playfab.com/blog/typescript/)!
 - And [new repository](https://github.com/PlayFab/SdkTestingCloudScript)!
-- We will be expanding this repository over time.
+- We're expanding this repository over time.
 
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - Fixed an issue where where **JsonWrapper** did not work as expected in all cases.
+  - Fixed an issue where **JsonWrapper** doesn't work as expected in all cases.
   - See our forum post for details: <https://community.playfab.com/questions/7599/cloudscript-getplayercombinedinfo-little-problem.html>
-  - All of the following deprecated wrapper classes have been removed in favor of `PlayFab.Json.JsonWrapper`:
+  - Removed all of the following deprecated wrapper classes in favor of `PlayFab.Json.JsonWrapper`:
     - `PlayFab.Json.JsonConvert` (Use `PlayFab.Json.JsonWrapper`)
     - `PlayFab.Json.SimpleJson` (Use `PlayFab.Json.JsonWrapper` or `PlayFab.Json.PlayFabSimpleJson`)
     - `PlayFab.SimpleJson` (Use `PlayFab.Json.JsonWrapper` or `PlayFab.Json.PlayFabSimpleJson`)
@@ -622,16 +622,16 @@ Date: 2017-01-29
 
 ### Unity Editor Extensions
 
-- Resolved an issue where the PlayFab panel will re-load infinitely if your account cannot view any studios.
-- Resolved an issue where `PlayFabSharedSettings` (Scriptable Object) would sometimes not save properly if you picked your title from the PlayFab panel.
+- Resolved an issue where the PlayFab panel will re-load infinitely if your account can't view any studios.
+- Resolved an issue where `PlayFabSharedSettings` (Scriptable Object) doesn't save properly if you pick your title from the PlayFab panel.
 
 ## 170109  
 
-Date: 2017-01-08
+Date: January 8, 2017
 
 ### Breaking changes
 
-- Libs in older versions of WindowsSDK have been removed, and must be re-created in Visual Studio. Those libs never worked in vs2015, so it's highly suggested you just update to the latest WindowsSDK, published last week.
+- Removed libs in older versions of WindowsSDK, and they must be re-created in Visual Studio. Those libs never worked in vs2015, so it's highly suggested you just update to the latest WindowsSDK, published last week.
 
 ### API changes
 
@@ -644,26 +644,26 @@ Date: 2017-01-08
 ### SDKGenerator specific changes
 
 - [SDKGenerator](https://github.com/PlayFab/SDKGenerator)
-  - The [ActionScriptSDK](https://github.com/PlayFab/ActionScriptSDK) build script was inconsistent from the other SDKs. The [SDKGenerator](https://github.com/PlayFab/SDKGenerator) commands that build [ActionScriptSDK](https://github.com/PlayFab/ActionScriptSDK) have been simplified to match other SDKs. (No changes to the SDK itself.)
+  - The [ActionScriptSDK](https://github.com/PlayFab/ActionScriptSDK) build script was inconsistent from the other SDKs. We simplified the [SDKGenerator](https://github.com/PlayFab/SDKGenerator) commands that build [ActionScriptSDK](https://github.com/PlayFab/ActionScriptSDK) to match other SDKs. (No changes to the SDK itself.)
 
 ### UnitySdk specific changes
 
 - [UnitySdk](https://github.com/PlayFab/UnitySDK)
   - Some public elements in PlayFabSettings have gained Obsolete tags: `PlayFabSettings.PlayFabSharedSettings` `PlayFabSettings.DefaultPlayFabApiUrl` `PlayFabSettings.GetSharedSettingsObject()` `PlayFabSettings.ProductionEnvironmentUrl`
 
-These will be made private after a transition period.
+These are made private after a transition period.
 
 ### WindowsSDK specific changes
 
-- GitHub repo has been BFG'd, and all large files have been removed from the history. Please delete your clone or fork, and re-create it so that your history is clean.
+- BFG'd the GitHub repo, and removed all large files from the history. Delete your clone or fork, and re-create it so that your history is clean.
 
 ## 170102  
 
-Date: 2017-01-01
+Date: January 1, 2017
 
 ### API changes
 
-- `Client/GetUserCombinedInfo` has transitioned to fully obsolete, and has been removed from the SDK and documentation.
+- `Client/GetUserCombinedInfo` transitioned to fully obsolete, and we removed it from the SDK and documentation.
 
 ### Cocos2d-xSDK specific changes
 
@@ -675,15 +675,15 @@ Date: 2017-01-01
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - We have internally updated to Unity 5.5, and our **.unitypackage** files are built using this version
+  - We've internally updated to Unity 5.5, and our **.unitypackage** files are built using this version
   - As always, we continue to support *all Unity versions 4.7 and higher*.
 
-  - Added static constructors to many static classes, in order to solidify the initialization sequence in **Mono2x** compiler. This should resolve some of the `PlayFabSharedSettings` issues we've been seeing in iOS.
+  - Added static constructors to many static classes, to solidify the initialization sequence in **Mono2x** compiler. This should resolve some of the `PlayFabSharedSettings` issues we've been seeing in iOS.
   - **IDFA/ADID** will now work properly for Unity 5.6 beta.
-  - **KNOWN ISSUE:** Unity 5.6 beta builds do not work on **Windows Server** (**OS**), which includes PlayFab game-server hosting. Please contact Unity if this affects you.
+  - **KNOWN ISSUE:** Unity 5.6 beta builds don't work on **Windows Server** (**OS**), which includes PlayFab game-server hosting. Contact Unity if this affects you.
 
 ### WindowsSDK specific changes
 
 - Release day for a major upgrade!
-- Blog Post: [Windows SDK Update Released](https://api.playfab.com/blog/windows-sdk-update-released)
+- Blog Post: [Windows SDK Update Released](https://api.playfab.com/blog/windows-SDK-update-released)
 - Upgrade Guide: [PlayFab WindowsSdk v0.x -> v1.x Upgrade guide](https://github.com/PlayFab/WindowsSdk/blob/master/UpgradeGuide.md)
diff --git a/playfab-docs/release-notes/2018.md b/playfab-docs/release-notes/2018.md
index bf4f7bab0..b493cdf8f 100644
--- a/playfab-docs/release-notes/2018.md
+++ b/playfab-docs/release-notes/2018.md
@@ -6,7 +6,7 @@ ms.author: jenelleb
 ms.date: 07/12/2018
 ms.topic: article
 ms.service: azure-playfab
-keywords: playfab, development, release, apis, features
+keywords: playfab, development, release, APIs, features
 ms.localizationpriority: medium
 ---
 
@@ -14,12 +14,12 @@ ms.localizationpriority: medium
 
 ## 181218
 
-Date: 2018-12-18
+Date: December 18, 2018
 
 ### XPlatCppSdk specific changes
 
 - [XPlatCppSdk](https://github.com/PlayFab/XPlatCppSdk)
-  -**SDK Breaking Change** : Updated the folder structure for the ``XPlatCppSdk`` repo. If you are using the SDK with project references, an update to vcxproj files path would be required.
+  -**SDK Breaking Change** : Updated the folder structure for the ``XPlatCppSdk`` repo. If you're using the SDK with project references, an update to vcxproj files path would be required.
   - Adding Xbox support to the `XPlatCppSdk`. Refer to the C++ quickstart for Xbox.
   - **New API**
   - Added `PlayFabEventApi` to support Heavyweight (low throughput) and Lightweight (high throughput) custom events.
@@ -31,20 +31,20 @@ Date: 2018-12-18
 
 ## 181204
 
-Date: 2018-12-04
+Date: December 4, 2018
 
 ### XPlatCppSDK specific changes
 
 - [XPlatCppSDK](https://github.com/PlayFab/XPlatCppSDK)
   - Added support to build external dependencies.
-  - Updated nuget composition. This is not a breaking change. Added binaries for the external dependencies to the nuget and updated the properties sheet.
+  - Updated NuGet composition. This isn't a breaking change. Added binaries for the external dependencies to the NuGet and updated the properties sheet.
   - Bug fixes for **QoSAPI**.
 
 ### CSharpSDK specific changes
 
 - [CSharpSDK](https://github.com/PlayFab/CSharpSDK)
-  - Added .NET Standard 1.1/2.0 (plus .Net Core) support.
-  - Updated nuget composition. The package now contains binaries for .Net Standard 1.1/2.0 and portables also.
+  - Added .NET Standard 1.1/2.0 (plus .NET Core) support.
+  - Updated NuGet composition. The package now contains binaries for .NET Standard 1.1/2.0 and portables also.
   - Migrated VS project files to VS 2017 standard.
 
 ### UnitySDK specific changes
@@ -55,25 +55,25 @@ Date: 2018-12-04
 
 ## 181105
 
-Date: 2018-11-05
+Date: November 5, 2018
 
 ### API changes
 
 - PlayFab now supports login and account-linking with `OpenID`.
-- Additional XboxLive ID support, and enabling Xbox login via server.
+- More XboxLive ID support, and enabling Xbox login via server.
 
-In preparation for wider release of the service, we are rolling out PlayFab Multiplayer Servers 2.0 APIs. See [PlayFab Multiplayer Servers 2.0 (Thunderhead)](../multiplayer/servers/index.md) for more information
+In preparation for wider release of the service, we're rolling out PlayFab Multiplayer Servers 2.0 APIs. See [PlayFab Multiplayer Servers 2.0 (Thunderhead)](../multiplayer/servers/index.md) for more information
 
 ## 181001
 
-Date: 2018-10-01
+Date: October 1, 2018
 
 ### API changes
 
-- A variety of deprecations have taken effect, and those elements have been removed from SDKs and documentation.
-  - Some Admin API methods related to unreleased features have been hidden.
+- Various deprecations took effect, and we removed those elements from SDKs and documentation.
+  - Hid some Admin API methods related to unreleased features.
   - `server.DeleteUsers` deprecation has taken effect.
-  - A field deprecation for `ServerHostname`, spread across a variety of matchmaking related calls in admin, client, matchmaker, and server APIs has taken effect. `ServerIPV4Address` is the replacement.
+  - A field deprecation for `ServerHostname`, spread across various matchmaking related calls in admin, client, matchmaker, and server APIs has taken effect. `ServerIPV4Address` is the replacement.
 
 ### UnitySDK changes
 
@@ -82,11 +82,11 @@ Date: 2018-10-01
 ### All SDKs
 
 - The automated-build branch structure for GitHub repos is changing.
-  - The normal customer facing branches, "versioned" and "master" will be unchanged.
+  - The normal customer facing branches, "versioned" and "master" are unchanged.
 
 ## 180924
 
-Date: 2018-09-24
+Date: September 24, 2018
 
 ### API changes
 
@@ -95,7 +95,7 @@ Date: 2018-09-24
 
 ## 180917  
 
-Date: 2018-09-17
+Date: September 17, 2018
 
 ### API changes
 
@@ -103,12 +103,12 @@ Date: 2018-09-17
 - Unreal Marketplace Plugin:
   - Updated Marketplace Plugin to include our Blueprint interface.
   - [New Unreal Engine quickstart guide](../sdks/unreal/quickstart.md)
-  - [View in Unreal Marketplace](https://www.unrealengine.com/marketplace/playfab-sdk)
+  - [View in Unreal Marketplace](https://www.unrealengine.com/marketplace/playfab-SDK)
 
 
 ## 180906  
 
-Date: 2018-09-06
+Date: September 6, 2018
 
 ### New API
 
@@ -116,13 +116,13 @@ Date: 2018-09-06
 
 ### New PlayStream event documentation
 
-- [client_focus_change](../api-references/events/client-focus-change.md)
-- [client_session_start](../api-references/events/client-session-start.md)
-- [player_device_info](../api-references/events/player-device-info.md)
+- [client_focus_change](../api-references/events/Session/client-focus-change.md)
+- [client_session_start](../api-references/events/Session/client-session-start.md)
+- [player_device_info](../api-references/events/PlayerIdentity/player-device-info.md)
 
 ## 180829  
 
-Date: 2018-08-29
+Date: August 29, 2018
 
 ### API changes
 
@@ -142,14 +142,14 @@ Date: 2018-08-29
 
 ## 180809  
 
-Date: 2018-08-09
+Date: August 9, 2018
 
 ### API group changes
 
-- We have separated the Entity API Group into multiple new API Groups.
+- We've separated the Entity API Group into multiple new API Groups.
 - This is a big SDK breaking change for anybody using the former Entity API.
 - See our [Upgrade Guide](../live-service-management/game-configuration/entities/entity-api-restructure-upgrade-tutorial.md)!
-- (Please note, the links for blog and upgrade guide may not work yet, they're almost done.)
+- (Note: the links for blog and upgrade guide may not work yet, they're almost done.)
 
 ### API changes
 
@@ -162,9 +162,9 @@ Date: 2018-08-09
     - client.[UnlinkFacebookInstantGamesId](xref:titleid.playfabapi.com.client.accountmanagement.unlinkfacebookinstantgamesid) (not ready to use yet)
     - server.[GetPlayFabIDsFromFacebookInstantGamesIds](xref:titleid.playfabapi.com.client.accountmanagement.getplayfabidsfromfacebookinstantgamesids) (not ready to use yet).
 - **New PlayStream Events**
-  - `title_hopper_config_updated` event renamed to [title_queue_config_updated](../api-references/events/title-queue-config-updated.md)
+  - `title_hopper_config_updated` event renamed to [title_queue_config_updated](../api-references/events/Matchmaking/title-queue-config-updated.md)
 - **General changes**
-  - The parameter `ServerAddress` in many models has been deprecated in favor of the new `ServerIPV4Address`.
+  - Deprecated the parameter `ServerAddress` in many models in favor of the new `ServerIPV4Address`.
 
 ### Unreal (multiple SDKs) Specific Changes
 
@@ -178,13 +178,13 @@ Date: 2018-08-09
 ### UnitySDK and CSharpSDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK) and [CSharpSDK](https://github.com/PlayFab/CSharpSDK)
-  - Added a new structure called Plugin Manager. For now, this is just a foundation for future changes. Some old function signatures have been marked as obsolete, and should be updated. (No breaking changes though).
+  - Added a new structure called Plugin Manager. For now, this is just a foundation for future changes. We marked some old function signatures as obsolete, and you should update them. (No breaking changes though).
   - Found and resolved multiple issues with HTTPS.Put, which makes Entity Files more accessible on more platforms.
   - Bug fixes in the ScreenTime feature.
 
 ## 180716  
 
-Date: 2018-07-16
+Date: July 16, 2018
 
 ### UnitySDK changes
 
@@ -196,13 +196,13 @@ Date: 2018-07-16
 - [CSharpSDK](https://github.com/PlayFab/CSharpSDK)
   - Added [Plugin Manager API](https://github.com/PlayFab/CSharpSDK/blob/master/PluginManager.md) to C# SDK, to support optional custom implementations of JSON Serializer and HTTP client.
 
-  - ~~**UnrealCppSdk Changes:**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+  - ~~**UnrealCppSdk Changes:**~~ (UPDATED : This SDK is deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
-  - Unreal 4 C++ SDK is also published on [Unreal Marketplace!](https://www.unrealengine.com/marketplace/playfab-sdk)
+  - Unreal 4 C++ SDK is also published on [Unreal Marketplace!](https://www.unrealengine.com/marketplace/playfab-SDK)
 
 ## 180710  
 
-Date: 2018-07-10
+Date: July 10, 2018
 
 ### Unity hotfix release
 
@@ -210,16 +210,16 @@ Date: 2018-07-10
 
 ## 180709  
 
-Date: 2018-07-09
+Date: July 9, 2018
 
 ### Hotfix release
 
 - Fixing some minor issues with last week's deployments.
-- Everything in last week's release notes should now actually work as promised.
+- Everything in last week's release notes should now work as promised.
 
 ## 180706
 
-Date: 2018-07-06
+Date: July 6, 2018
 
 ### API changes
 
@@ -233,7 +233,7 @@ Date: 2018-07-06
 
 ## 180705  
 
-Date: 2018-07-05
+Date: July 5, 2018
 
 ### API changes
 
@@ -260,20 +260,20 @@ Date: 2018-07-05
 ### XPlatCppSDK specific changes
 
 - [XPlatCppSDK](https://github.com/PlayFab/XPlatCppSdk)
-  - Large results will now be parsed correctly.
+  - Large results are now parsed correctly.
 
 ## 180618  
 
-Date: 2018-06-18
+Date: June 18, 2018
 
 ### API changes
 
-- Added new error codes in a variety of API methods.
+- Added new error codes in various API methods.
 - Multiple entity-related PlayStream events now describe their [EntityLineage](../api-references/events/data-types/entitylineage.md).
 
 ## 180528  
 
-Date: 2018-05-28
+Date: May 28, 2018
 
 ### API changes
 
@@ -282,13 +282,13 @@ Date: 2018-05-28
   - Admin.[DeleteMasterPlayerAccount](xref:titleid.playfabapi.com.admin.accountmanagement.deletemasterplayeraccount)
   - Admin.[ExportMasterPlayerData](xref:titleid.playfabapi.com.admin.accountmanagement.exportmasterplayerdata)
   - This is a part of the new GDPR launch. See our blog [here](https://blog.playfab.com/blog/gdpr)
-- Updated Error codes in a variety of API methods
+- Updated Error codes in various API methods
 - New PlayStream Event:
-  - [player_data_exported](../api-references/events/player-data-exported.md)
+  - [player_data_exported](../api-references/events/PlayerIdentity/player-data-exported.md)
 
 ## 180514  
 
-Date: 2018-05-14
+Date: May 14, 2018
 
 ### XPlatCppSDK specific changes
 
@@ -297,31 +297,31 @@ Date: 2018-05-14
 
 ## 180507  
 
-Date: 2018-05-07
+Date: May 7, 2018
 
 ### API changes
 
 - **New API Method:**
   - entity.[GetProfiles](xref:titleid.playfabapi.com.profiles.accountmanagement.getprofiles)
 - **New PlayStream Events:**
-  - [entity_executed_cloud_script](../api-references/events/entity-executed-cloud-script.md)
+  - [entity_executed_cloud_script](../api-references/events/CloudScript/entity-executed-cloud-script.md)
 - **Updated API Method:**
   - client.[RegisterPlayFabUser](xref:titleid.playfabapi.com.client.authentication.registerplayfabuser) now returns [result](xref:titleid.playfabapi.com.client.authentication.registerplayfabuser#registerplayfabuserresult).[EntityToken](xref:titleid.playfabapi.com.client.authentication.registerplayfabuser#entitytokenresponse)
 
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - `HttpWebRequest` certificate validation security has been improved.
+  - Improved `HttpWebRequest` certificate validation security.
   - No longer default to ignoring all certificates.
   - Customers are expected to implement their own certificate validation, or call `PlayFab.Internal.PlayFabWebRequest.SkipCertificateValidation()`.
 
 ### WindowsSdk specific changes
 
 - Fixed hundreds of Level 4 warnings.
-- The version number published in `PlayFabSettings.cpp` has been corrected.
-- Most previous versions will have all had the wrong version number embedded in-code, and in call headers.
+- Corrected the version number published in `PlayFabSettings.cpp`.
+- Most previous versions have all had the wrong version number embedded in-code, and in call headers.
 
-### XPlatCppSDK has been created
+### Created XPlatCppSDK
 
 - [XPlatCppSDK](https://github.com/PlayFab/XPlatCppSDK)
   - Currently in beta.
@@ -329,25 +329,25 @@ Date: 2018-05-07
   - May become a replacement to Windows SDK (At least several months away).
   - Upgrade should require almost no breaking changes.
   - Some `cpprestsdk` strings should be converted to `std::string`.
-  - Some `web::json::value` types have been converted to `json::value`.
-  - timestamps are not fully tested in Linux.
+  - Converted some `web::json::value` types to `json::value`.
+  - timestamps aren't fully tested in Linux.
   - NuGet package
   - Uses lighter weight dependencies
   - Specifically `jsoncpp` and curl, rather than `cpprestsdk`.
-  - Uses `std::string` everywhere, rather than a mix of 2 string types.
+  - Uses `std::string` everywhere, rather than a mix of two string types.
   - Adds Linux Support.
 
 ## 180414  
 
-Date: 2018-04-14
+Date: April 14, 2018
 
-~~**UnrealCppSdk HotFix:**~~ (UPDATED : This SDK has been deprecated. For the new unreal SDK, please refer to [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-sdk))
+~~**UnrealCppSdk HotFix:**~~ (UPDATED : This SDK is deprecated. For the new unreal SDK, see [UnrealMarketplaceSDK](https://www.unrealengine.com/marketplace/playfab-SDK))
 
 - ~~Issues were discovered in the Entity API release for UnrealCppSdk. These are hot fixed, and the Entity API should now work as expected.~~
 
 ## 180409  
 
-Date: 2018-04-09
+Date: April 9, 2018
 
 ### API changes
 
@@ -364,24 +364,24 @@ Date: 2018-04-09
 
 ## 180403  
 
-Date: 2018-04-03
+Date: April 3, 2018
 
-### Unreal SDKs updated to support v4.17 thru 4.19
+### Unreal SDKs updated to support v4.17 through 4.19
 
-- Removing support for UE 4.14 thru 4.16 (Please update!)
+- Removing support for UE 4.14 through 4.16 (Update!)
 
 ## 180329  
 
-Date: 2018-03-29
+Date: March 29, 2018
 
 ### Unreal SDKs updated to support Entity APIs
 
 - Sorry for the delay!
-- This release still targets UE 4.17, and not 4.18 or 4.19. We are in-progress working on updating versions.
+- This release still targets UE 4.17, and not 4.18 or 4.19. We're in-progress working on updating versions.
 
 ## 180316  
 
-Date: 2018-03-16
+Date: March 16, 2018
 
 ### API changes
 
@@ -415,7 +415,7 @@ Date: 2018-03-16
 
 ## 180213  
 
-Date: 2018-02-13
+Date: February 13, 2018
 
 ### API changes
 
@@ -426,12 +426,12 @@ Date: 2018-02-13
 ### UnitySDK specific changes
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
-  - We are dropping support for older Unity versions, see our [blog post](https://blog.playfab.com/blog/unity-version-support).
+  - We're dropping support for older Unity versions, see our [blog post](https://blog.playfab.com/blog/unity-version-support).
   - Build files are now published using Unity version 2017.3.0f3.
 
 ## 180131  
 
-Date: 2018-01-31
+Date: January 31, 2018
 
 ### JavaSDK changes
 
@@ -440,7 +440,7 @@ Date: 2018-01-31
 
 ## 180129  
 
-Date: 2018-01-29
+Date: January 29, 2018
 
 ### UnitySDK specific changes
 
@@ -450,18 +450,18 @@ Date: 2018-01-29
 
 ## 180123  
 
-Date: 2018-01-23
+Date: January 23, 2018
 
 ### UnitySDK hotfix
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
   - PlayFab UnitySDK had an issue with Unity version 2017.1.
   - See the [forum post](https://community.playfab.com/questions/16734/error-cs1061-no-definition-for-sendwebrequesterror.html) for details.
-  - This has been resolved, PlayFab UnitySDK should work for all versions again.
+  - We resolved this. PlayFab UnitySDK should work for all versions again.
 
 ## 180122  
 
-Date: 2018-01-22
+Date: January 22, 2018
 
 ### API documentation update
 
@@ -477,7 +477,7 @@ Date: 2018-01-22
 - [NodeSDK](https://github.com/PlayFab/NodeSDK)
   - SDK Breaking Change: Require syntax for NodeSDK NPM package changed.
   - Major upgrade focused on NPM package.
-  - Formerly require statements did not follow the NPM convention, requiring multiple nonstandard require statements.
+  - Formerly require statements didn't follow the NPM convention, requiring multiple nonstandard require statements.
   - Now it requires a single require statement, and follows NPM conventions.
   - Major version number changed, this release is now 2.0.
   - 1.x to 2.x [Upgrade Guide](https://github.com/PlayFab/NodeSDK/blob/master/upgrade.md).
@@ -488,22 +488,22 @@ Date: 2018-01-22
 
 ## 180103
 
-Date: 2018-01-03
+Date: January 3, 2018
 
 ### LuaSDK specific updates
 
 - [LuaSDK](https://github.com/PlayFab/LuaSDK)/Defold/Corona
   - Bug fix update.
-  - Some platforms were producing a malformed URL which could not be resolved.
+  - Some platforms were producing a malformed URL that couldn't be resolved.
 
 ## 180102  
 
-Date: 2018-01-02
+Date: January 2, 2018
 
 ### UnitySDK specific updates
 
 - [UnitySDK](https://github.com/PlayFab/UnitySDK)
   - Bug fix update.
-  - In order to avoid an issue with response headers, compression should be disabled for all device builds. This update makes that possible.
+  - To avoid an issue with response headers, compression should be disabled for all device builds. This update makes that possible.
   - Alternately, switching to Web Request will also avoid the issue.
-  - A new HTTP option has been added for Unity versions > 2017.
+  - Added a new HTTP option for Unity versions > 2017.
diff --git a/playfab-docs/release-notes/2025.md b/playfab-docs/release-notes/2025.md
new file mode 100644
index 000000000..5f34b3bfc
--- /dev/null
+++ b/playfab-docs/release-notes/2025.md
@@ -0,0 +1,226 @@
+---
+title: PlayFab Services SDK Release Notes 2025
+author: stevenLizano29
+description: PlayFab Services SDK Release Notes for 2025.
+ms.author: v-stevenroj
+ms.date: 03/09/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, development, release, apis, features
+ms.localizationpriority: medium
+---
+# PlayFab Services SDK Release Notes 2025
+
+> [!NOTE]
+> For release notes about service releases and product updates, see the [release notes](https://github.com/PlayFab/PlayFab/releases) section on [PlayFab's public GitHub repository](https://github.com/PlayFab/PlayFab)
+
+## 251219
+
+Date: December 19, 2025
+
+ - Added StartDate field to Economy API
+ - Added error codes for new service errors
+
+## 251205
+
+Date: December 5, 2025
+
+ - Added GetPlayFabIDsFromOpenIdSubjectIdentifiers to the Client and Server APIs
+ - Added the following calls to the Server API:
+   - LinkTwitchAccount
+   - LoginWithTwitch
+   - UnlinkTwitchAccount
+ - Added error codes for new service errors
+
+## 251121
+
+Date: November 21, 2025
+
+ - Added MarketplaceConfigurationName to the Economy API
+ - Updated RestrictInvitesToLobbyOwner in the Multiplayer API
+ - Added error codes for new service errors
+
+## 251107
+
+Date: November 7, 2025
+
+ - Added PageSize and SkipToken pagination fields to multiple calls in the Progression API
+ - Added JwsReceiptData type to the Economy API
+ - Added error codes for new service errors
+
+## 251024
+
+Date: October 24, 2025
+
+ - Added AlternateIdType and AlternateIdValue fields to the Economy API
+ - Added error codes for new service errors
+
+## 251010
+
+Date: October 10, 2025
+
+ - Added error codes for new service errors
+
+## 250926
+
+Date: September 26, 2025
+
+ - Added RedeemAppleAppStoreWithJwsInventoryItems to the Economy API for Apple App Store JWS receipt validation
+ - Added error codes for new service errors
+
+## 250912
+
+Date: September 12, 2025
+
+ - Added UnlinkAggregationSourceFromStatistic to the Progression API
+ - Added LinkXboxId to the Server API
+ - Added time range query types for store metrics in the Admin API
+ - Added error codes for new service errors
+
+## 250815
+
+Date: August 15, 2025
+
+ - Added LeaderboardVersionEndConfig, LeaderboardEventEmissionConfig, and StatisticsEventEmissionConfig types to the Progression API
+ - Added pricing override types to the Economy API
+ - Added Apple and Xbox add-on configuration fields to the Addon API
+ - Added error codes for new service errors
+
+## 250801
+
+Date: August 1, 2025
+
+ - Added GetStoreMetrics to the Admin API
+ - Added error codes for new service errors
+
+## 250718
+
+Date: July 18, 2025
+
+ - Added CustomTags to GetTransactionHistory in the Economy API
+ - Added FunctionResultSize field to the CloudScript API
+ - Added error codes for new service errors
+
+## 250704
+
+Date: July 4, 2025
+
+ - Added ContinuationToken and Count fields to the Economy API
+ - Added error codes for new service errors
+
+## 250620
+
+Date: June 20, 2025
+
+ - Added VersionedCatalogsSource field to the Economy API
+ - Added error codes for new service errors
+
+## 250606
+
+Date: June 6, 2025
+
+ - Added clawback tracking fields to transaction history in the Economy API (TransactionClawbackDetails)
+ - Added StatisticNames filter to GetEntityStatistics in the Progression API
+ - Added error codes for new service errors
+
+## 250526
+
+Date: May 26, 2025
+
+ - Added the following calls to the Addon API for ToxMod management:
+   - CreateOrUpdateToxMod
+   - DeleteToxMod
+   - GetToxMod
+ - Renamed LinkBattleNet to LinkBattleNetAccount and UnlinkBattleNet to UnlinkBattleNetAccount in the Client API
+ - Added ExportVersionedCatalog to the Economy API. Removed UploadVersionedCatalog.
+ - Added the following Data Connection management calls to the Events API:
+   - DeleteDataConnection
+   - GetDataConnection
+   - ListDataConnections
+   - SetDataConnection
+   - SetDataConnectionActive
+ - Added the following calls to the Server API:
+   - LinkBattleNetAccount
+   - LoginWithBattleNet
+   - UnlinkBattleNetAccount
+ - Expanded Economy API catalog items with real-money price details across multiple storefronts
+ - Added error codes for new service errors
+
+## 250425
+
+Date: April 25, 2025
+
+ - Added Battle.net identity provider support with the following calls to the Client API:
+   - GetPlayFabIDsFromBattleNetAccountIds
+   - LinkBattleNet
+   - LoginWithBattleNet
+   - UnlinkBattleNet
+ - Added GetPlayFabIDsFromBattleNetAccountIds to the Server API
+ - Added the following login calls to the Server API:
+   - LoginWithAndroidDeviceID
+   - LoginWithCustomID
+   - LoginWithIOSDeviceID
+ - Added the following calls to the Economy API:
+   - CompleteVersionedCatalogUpload
+   - CreateVersionedCatalogUploadURL
+   - GetVersionedCatalogUploadStatus
+ - Added the following TrueSkill calls to the Multiplayer API:
+   - GetPlayerSkillForConditions
+   - GetPlayerSkillForConditionsFromModel
+ - Added error codes for new service errors
+
+## 250328
+
+Date: March 28, 2025
+
+ - Added DeleteVersionedCatalog to the Economy API
+ - Added RestrictInvitesToLobbyOwner to the Multiplayer API
+ - Added error codes for new service errors
+
+## 250314
+
+Date: March 14, 2025
+
+ - Added the following calls to the Economy API:
+   - GetVersionedCatalogItem
+   - UploadVersionedCatalog
+ - Added TrueSkill-related types to the Multiplayer API
+ - Added error codes for new service errors
+
+## 250228
+
+Date: February 28, 2025
+
+ - Cleaned up API spec schema formatting across all APIs. No functional API changes.
+
+## 250214
+
+Date: February 14, 2025
+
+ - Removed the following deprecated calls from the Economy API:
+   - Inventory/AddVirtualCurrencies
+   - Inventory/ConsumeInventoryItems
+   - Catalog/EvaluateDropTable
+   - Inventory/GetAccessTokens
+   - Inventory/GetReceiptIssuerCertificateAsJwk
+   - Inventory/GetReceiptIssuerCertificateAsPem
+   - Inventory/GetVirtualCurrencies
+   - Inventory/GrantInventoryItems
+   - Catalog/PurchaseItemByFriendlyId
+   - Catalog/PurchaseItemById
+   - Inventory/Redeem
+   - Inventory/RefreshSubscriptions
+   - Inventory/SetInventoryItems
+   - Inventory/SetVirtualCurrencies
+   - Inventory/SubtractVirtualCurrencies
+   - Inventory/UpdateInventoryItemsProperties
+ - Added UpdateLeaderboardDefinition and UpdateStatisticDefinition to the Progression API
+ - Added NextReset field to leaderboard definitions in the Progression API
+ - Added error codes for new service errors
+
+## 250117
+
+Date: January 17, 2025
+
+ - Added error codes for new service errors
+ - Added TransactionId to UpdateStatisticsRequest in the Progression API
\ No newline at end of file
diff --git a/playfab-docs/release-notes/images/171026-DelTitleGameManager.png b/playfab-docs/release-notes/images/171026-DelTitleGameManager.png
index 4e2d1a592..cd222ae28 100644
Binary files a/playfab-docs/release-notes/images/171026-DelTitleGameManager.png and b/playfab-docs/release-notes/images/171026-DelTitleGameManager.png differ
diff --git a/playfab-docs/release-notes/index.md b/playfab-docs/release-notes/index.md
index 478ad6e70..44ddebdd6 100644
--- a/playfab-docs/release-notes/index.md
+++ b/playfab-docs/release-notes/index.md
@@ -1,22 +1,80 @@
 ---
-title: PlayFab Services SDK Release Notes 2025
-author: amccalib
-description: PlayFab Services SDK Release Notes for 2025.
-ms.author: andmcc
-ms.date: 01/28/2025
+title: PlayFab Services SDK Release Notes 2026
+author: stevenLizano29
+description: PlayFab Services SDK Release Notes for 2026.
+ms.author: v-stevenroj
+ms.date: 04/10/2026
 ms.topic: article
 ms.service: azure-playfab
 keywords: playfab, development, release, apis, features
 ms.localizationpriority: medium
 ---
-# PlayFab Services SDK Release Notes 2025
+# PlayFab Services SDK Release Notes 2026
 
 > [!NOTE]
-> For release notes about service releases and product updates, see the [release notes](https://github.com/PlayFab/PlayFab/releases) section on [PlayFab's public GitHub repository](https://github.com/PlayFab/PlayFab)
+> For release notes about service releases and product updates, see the [release notes](https://github.com/PlayFab/PlayFab/releases) section on [PlayFab's public GitHub repository](https://github.com/PlayFab/PlayFab).
 
-## 250117
+## 260410
 
-Date: January 17, 2025
+Date: April 10, 2026
 
- - Added error codes for new service errors
- - Added TransactionId to UpdateStatisticsRequest in the Progression API
\ No newline at end of file
+- Added `ValidateApiPolicy` to the Admin API
+- Added `ExportPlayersInSegment` and `GetSegmentExport` to the Server API
+- Added `AggregationTargetEntityKeys` field to statistic update requests in the Progression API
+- Added `WestUs3` Azure region to the Multiplayer API
+- Added new VM families and sizes to the Multiplayer API (`Fasv6`, `Fasv7`, `Fadsv7`, `Eadsv5`, `Eadsv6`, `Eadsv7`, `Dadsv7`)
+- Added error codes for new service errors
+
+## 260327
+
+Date: March 27, 2026
+
+- Added `IncludeStatistics` parameter to `GetEntityProfile` and `GetEntityProfiles` in the Profiles API
+- Added `StatisticsColumnDetails` field to entity profile response in the Profiles API
+- Added `LastUpdated` field to `GetPolicy` response in the Admin API
+- Added `Warnings` field to `UpdatePolicy` response in the Admin API
+- Updated documentation for `GetPolicy` and `UpdatePolicy` request parameters in the Admin API
+- Added `PreconditionFailed` error code to `GetInventoryItems` and `TransferInventoryItems` in the Economy API
+- Added `StatisticUpdateNotAllowedWhileLinked` error code to the Progression API
+- Added error codes for new service errors
+
+## 260313
+
+Date: March 13, 2026
+
+- Renamed the `GetPlayersInSegmentDeprecated` error code to `GetPlayersInSegmentRetired`
+- Updated the `GetFriendsList` documentation in the Client and Server APIs to clarify Xbox friend's behavior
+- Updated the `FindFriendLobbies` documentation in the Multiplayer API to clarify mutual friends requirement
+- Added the `ProductDisabledForTitle` error code to multiple calls across the Client, Server, Admin, and Experimentation APIs
+- Added error codes for new service errors
+
+## 260227
+
+Date: February 27, 2026
+
+- Added `ProductDisabledForTitle` error code to multiple calls across the Client, Server, and Admin APIs
+- Added error codes for new service errors
+
+## 260213
+
+Date: February 13, 2026
+
+- Added `AddOrUpdateContactEmail` to the Server API
+- Added PubSub connection lifetime extension support to the Multiplayer API
+- Added error codes for new service errors
+
+## 260123
+
+Date: January 23, 2026
+
+- Removed `GetMicrosoftStoreAccessTokens` from the Economy API
+- Added error codes for new service errors
+
+## 260109
+
+Date: January 9, 2026
+
+- Added the following calls to the Server API:
+  - `UnlinkFacebookAccount`
+  - `UnlinkFacebookInstantGamesId`
+- Added error codes for new service errors
diff --git a/playfab-docs/release-notes/toc.yml b/playfab-docs/release-notes/toc.yml
index f889885f0..e42d3ab68 100644
--- a/playfab-docs/release-notes/toc.yml
+++ b/playfab-docs/release-notes/toc.yml
@@ -1,5 +1,7 @@
-- name: 2025 SDK Release Notes
+- name: 2026 SDK Release Notes
   href: ./index.md
+- name: 2025 SDK Release Notes
+  href: ./2025.md
 - name: 2024 SDK Release Notes
   href: ./2024.md
 - name: 2023 SDK Release Notes
diff --git a/playfab-docs/sdks/c-sharp/index.md b/playfab-docs/sdks/c-sharp/index.md
index 12319eeaf..1734e8737 100644
--- a/playfab-docs/sdks/c-sharp/index.md
+++ b/playfab-docs/sdks/c-sharp/index.md
@@ -39,7 +39,7 @@ The C# PlayFab SDK shouldn't be used if there's a more specific SDK that is suit
 Specific PlayFab SDK is available for:
 * [Unity PlayFab SDK GitHub repo](https://github.com/PlayFab/UnitySDK)
 
-For a full list of the different PlayFab SDKs, see [Azure PlayFab SDK](../playfab-sdk-intro.md).
+For a full list of the different PlayFab SDKs, see [PlayFab SDK](../playfab-sdk-intro.md).
 
 ## Using the SDK
 
diff --git a/playfab-docs/sdks/c-sharp/quickstart.md b/playfab-docs/sdks/c-sharp/quickstart.md
index 52210cccc..a39c5aad8 100644
--- a/playfab-docs/sdks/c-sharp/quickstart.md
+++ b/playfab-docs/sdks/c-sharp/quickstart.md
@@ -20,7 +20,7 @@ This quickstart helps you make your first PlayFab API call in the using the Clie
 
 ## Requirements
 
-- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).  
+- A [PlayFab developer account](https://developer.playfab.com).  
 - An installation of [Visual Studio](https://visualstudio.microsoft.com/).
 
 ## CSharp project setup
diff --git a/playfab-docs/sdks/c/async.md b/playfab-docs/sdks/c/async.md
index 187feff4c..2209100f0 100644
--- a/playfab-docs/sdks/c/async.md
+++ b/playfab-docs/sdks/c/async.md
@@ -16,7 +16,7 @@ An asynchronous API is an API that returns quickly but starts an asynchronous ta
 
 Traditionally, games have had little control over which thread executes the asynchronous task and which thread returns the results when using a completion callback. Some games are designed so that a section of the heap is only touched by a single thread to avoid any need for thread synchronization. If the completion callback isn't called from a thread the game controls, updating shared state with the result of an asynchronous task requires thread synchronization.
 
-The PlayFab Services SDK exposes an asynchronous C API that gives developers direct thread control when making an asynchronous API call, such as **PFAuthenticationLoginWithCustomIDAsync**, **PFDataGetFilesAsync**, or **PFProfilesGetProfileAsync**.
+The PlayFab Services SDK exposes an asynchronous C API that gives developers direct thread control when making an asynchronous API call, such as [**PFAuthenticationLoginWithCustomIDAsync**](../../api-references/c/pfauthentication/functions/pfauthenticationloginwithcustomidasync.md), [**PFDataGetFilesAsync**](../../api-references/c/pfdata/functions/pfdatagetfilesasync.md), or [**PFProfilesGetProfileAsync**](../../api-references/c/pfprofiles/functions/pfprofilesgetprofileasync.md).
 
 Here's a basic example calling **PFProfilesGetProfileAsync**:
 
@@ -104,7 +104,7 @@ Once the asynchronous task is complete, you can get the results.
 
 To get the result, most asynchronous API functions have a corresponding Result function to receive the result of the asynchronous call.
 
-In our example code, **PFProfilesGetProfileAsync** has a corresponding **PFProfilesGetProfileGetResult** function. You can use this function to retrieve the result of the function and act accordingly.
+In our example code, **PFProfilesGetProfileAsync** has a corresponding [**PFProfilesGetProfileGetResult**](../../api-references/c/pfprofiles/functions/pfprofilesgetprofilegetresult.md) function. You can use this function to retrieve the result of the function and act accordingly.
 
 For full details on retrieving results, see the documentation of each asynchronous API function.
 
diff --git a/playfab-docs/sdks/c/entity-handles.md b/playfab-docs/sdks/c/entity-handles.md
new file mode 100644
index 000000000..e3d89f467
--- /dev/null
+++ b/playfab-docs/sdks/c/entity-handles.md
@@ -0,0 +1,330 @@
+---
+title: Entity Handles
+author: amccalib
+description: Managing entity handles and token lifecycle in the PlayFab Services SDK
+ms.author: andmcc
+ms.date: 02/14/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, c++, windows, xbox, gdk, entity, handles, tokens
+ms.localizationpriority: medium
+---
+
+# Entity Handles
+
+A __PFEntityHandle__ is your primary credential for making PlayFab service calls. It represents an authenticated entity—either a player (title_player_account) or a title—and holds the entity token the SDK needs to authorize requests. Every login or authentication call returns a __PFEntityHandle__, and every service call requires one.
+
+## Getting an entity handle
+
+You don't create entity handles directly. Instead, you get one as an output of a successful login or authentication call.
+
+**Player login (Windows example):**
+
+```cpp
+PFAuthenticationLoginWithXUserRequest request{};
+request.createAccount = true;
+request.user = userHandle; // XUserHandle from XUserAddAsync
+
+XAsyncBlock async{};
+HRESULT hr = PFAuthenticationLoginWithXUserAsync(serviceConfigHandle, &request, &async);
+hr = XAsyncGetStatus(&async, true);
+
+PFEntityHandle entityHandle{ nullptr };
+size_t bufferSize{};
+hr = PFAuthenticationLoginWithXUserGetResultSize(&async, &bufferSize);
+
+std::vector<char> loginResultBuffer(bufferSize);
+PFAuthenticationLoginResult const* loginResult{};
+hr = PFAuthenticationLoginWithXUserGetResult(
+    &async, &entityHandle,
+    loginResultBuffer.size(), loginResultBuffer.data(),
+    &loginResult, nullptr);
+```
+
+**Title entity (server):**
+
+Title entities authenticate with a secret key instead of a user credential. The returned __PFEntityHandle__ works the same way, but it represents the title rather than a player. See [Accessing PlayFab with a title entity](server.md) for details.
+
+## Handle ownership and ref counting
+
+__PFEntityHandle__ is ref-counted. When you receive a handle from a login call, you own one reference. You can create additional references with [__PFEntityDuplicateHandle__](../../api-references/c/pfentity/functions/pfentityduplicatehandle.md) and release them with [__PFEntityCloseHandle__](../../api-references/c/pfentity/functions/pfentityclosehandle.md). The underlying entity object is destroyed only when the last reference is closed.
+
+**Rules:**
+
+- Every call to a login `GetResult` function or __PFEntityDuplicateHandle__ gives you a handle you must close.
+- Closing a handle doesn't invalidate other handles to the same entity.
+- Close all handles before calling [__PFServicesUninitializeAsync__](../../api-references/c/pfservices/functions/pfservicesuninitializeasync.md).
+
+```cpp
+// Duplicate a handle for another component
+PFEntityHandle secondHandle{ nullptr };
+HRESULT hr = PFEntityDuplicateHandle(entityHandle, &secondHandle);
+
+// Both handles are independently valid
+// ...
+
+// Each owner closes their own handle
+PFEntityCloseHandle(secondHandle);
+PFEntityCloseHandle(entityHandle);
+```
+
+## Getting entity info
+
+### Entity key
+
+The entity key identifies the entity (its type and ID). Use the two-call pattern: get the size first, then get the data.
+
+```cpp
+size_t size{};
+HRESULT hr = PFEntityGetEntityKeySize(entityHandle, &size);
+
+std::vector<char> buffer(size);
+PFEntityKey const* entityKey{};
+hr = PFEntityGetEntityKey(entityHandle, buffer.size(), buffer.data(), &entityKey, nullptr);
+
+// entityKey->type is "title_player_account" for players
+// entityKey->id is the entity's unique ID
+```
+
+### Entity token
+
+The entity token authorizes service calls. The SDK manages tokens automatically, but you can retrieve the current one if needed.
+
+```cpp
+XAsyncBlock async{};
+HRESULT hr = PFEntityGetEntityTokenAsync(entityHandle, &async);
+hr = XAsyncGetStatus(&async, true);
+
+size_t size{};
+hr = PFEntityGetEntityTokenResultSize(&async, &size);
+
+std::vector<char> buffer(size);
+const PFEntityToken* entityToken{};
+hr = PFEntityGetEntityTokenResult(&async, buffer.size(), buffer.data(), &entityToken, nullptr);
+
+// entityToken->token is the token string
+// entityToken->expiration is the optional expiration time (UTC)
+```
+
+### Checking entity type
+
+Use [__PFEntityIsTitlePlayer__](../../api-references/c/pfentity/functions/pfentityistitleplayer.md) as a quick check instead of inspecting the entity key type string:
+
+```cpp
+bool isTitlePlayer{};
+HRESULT hr = PFEntityIsTitlePlayer(entityHandle, &isTitlePlayer);
+```
+
+## Player entities vs. title entities
+
+Both player and title entities use __PFEntityHandle__, but they differ in what they can do:
+
+| | Player entity | Title entity |
+|---|---|---|
+| **How you get it** | Login call (e.g., `PFAuthenticationLoginWithXUserAsync`) | `PFAuthenticationGetEntityWithSecretKeyAsync` |
+| **Entity type** | `title_player_account` | `title` |
+| [**PFEntityIsTitlePlayer**](../../api-references/c/pfentity/functions/pfentityistitleplayer.md) | Returns `true` | Returns `false` |
+| [**PFEntityGetSecretKey**](../../api-references/c/pfentity/functions/pfentitygetsecretkey.md) | Fails with `E_PF_NOSECRETKEY` | Returns the secret key |
+| **Available APIs** | Client-prefixed and non-prefixed APIs | Server-prefixed and non-prefixed APIs |
+
+Non-prefixed APIs (e.g., Inventory, Leaderboards, Data) can generally be called by both player and title entities unless otherwise noted in their documentation. Client-prefixed APIs are player-only, and Server-prefixed APIs are title-only.
+
+__PFEntityGetSecretKey__ retrieves the secret key associated with a title entity. It fails for player entities because they don't have one.
+
+```cpp
+size_t keySize{};
+HRESULT hr = PFEntityGetSecretKeySize(entityHandle, &keySize);
+if (SUCCEEDED(hr))
+{
+    std::vector<char> secretKey(keySize);
+    hr = PFEntityGetSecretKey(entityHandle, secretKey.size(), secretKey.data(), nullptr);
+}
+```
+
+> [!NOTE]
+> __PFEntityGetSecretKey__ is only available on Windows, Linux, and macOS platforms.
+
+## Token event handlers
+
+The SDK automatically refreshes entity tokens before they expire. You can register callbacks to observe these events.
+
+### Token expired
+
+If automatic refresh fails (for example, the original login credential is no longer valid), the SDK fires the token-expired event. Register a handler to provide a new credential and retry the login.
+
+```cpp
+PFRegistrationToken registrationToken{};
+HRESULT hr = PFEntityRegisterTokenExpiredEventHandler(
+    nullptr,  // XTaskQueueHandle, or nullptr for default
+    nullptr,  // optional context
+    [](void* ctx, PFEntityKey const* entityKey)
+    {
+        // Re-authenticate the player with a fresh credential
+        // See relogin.md for a complete example
+    },
+    &registrationToken);
+```
+
+### Token refreshed
+
+Register a token-refreshed handler if you want to know when the SDK successfully refreshes a token in the background. This is informational—you don't need to take any action.
+
+```cpp
+PFRegistrationToken registrationToken{};
+HRESULT hr = PFEntityRegisterTokenRefreshedEventHandler(
+    nullptr,  // XTaskQueueHandle, or nullptr for default
+    nullptr,  // optional context
+    [](void* ctx, PFEntityKey const* entityKey, const PFEntityToken* newToken)
+    {
+        // Log the refresh or update cached token references
+    },
+    &registrationToken);
+```
+
+### When to register and unregister
+
+- **Register** handlers early, right after SDK initialization and before login. This ensures you don't miss any events.
+- **Unregister** handlers during shutdown, before you close entity handles.
+
+```cpp
+PFEntityUnregisterTokenExpiredEventHandler(expiredRegistrationToken);
+PFEntityUnregisterTokenRefreshedEventHandler(refreshedRegistrationToken);
+```
+
+For a complete walkthrough of token expiration handling and relogin, see [Handling Token Expiration](relogin.md).
+
+## Utility accessors
+
+You can retrieve the API endpoint and title ID from an entity handle. These come from the __PFServiceConfigHandle__ that was used during login.
+
+```cpp
+// Get API endpoint
+size_t endpointSize{};
+HRESULT hr = PFEntityGetAPIEndpointSize(entityHandle, &endpointSize);
+
+std::vector<char> endpoint(endpointSize);
+hr = PFEntityGetAPIEndpoint(entityHandle, endpoint.size(), endpoint.data(), nullptr);
+
+// Get title ID
+size_t titleIdSize{};
+hr = PFEntityGetTitleIdSize(entityHandle, &titleIdSize);
+
+std::vector<char> titleId(titleIdSize);
+hr = PFEntityGetTitleId(entityHandle, titleId.size(), titleId.data(), nullptr);
+```
+
+## Complete example
+
+This example demonstrates creating, duplicating, querying, and closing entity handles:
+
+```cpp
+#include <playfab/core/PFEntity.h>
+#include <playfab/services/PFServices.h>
+
+void EntityHandleExample(PFServiceConfigHandle serviceConfigHandle, XUserHandle userHandle)
+{
+    //
+    // Log in and get an entity handle
+    //
+    PFAuthenticationLoginWithXUserRequest request{};
+    request.createAccount = true;
+    request.user = userHandle;
+
+    XAsyncBlock asyncLogin{};
+    HRESULT hr = PFAuthenticationLoginWithXUserAsync(serviceConfigHandle, &request, &asyncLogin);
+    hr = XAsyncGetStatus(&asyncLogin, true);
+
+    PFEntityHandle entityHandle{ nullptr };
+    size_t resultSize{};
+    hr = PFAuthenticationLoginWithXUserGetResultSize(&asyncLogin, &resultSize);
+
+    std::vector<char> loginBuffer(resultSize);
+    PFAuthenticationLoginResult const* loginResult{};
+    hr = PFAuthenticationLoginWithXUserGetResult(
+        &asyncLogin, &entityHandle,
+        loginBuffer.size(), loginBuffer.data(),
+        &loginResult, nullptr);
+
+    //
+    // Register token event handlers
+    //
+    PFRegistrationToken expiredToken{};
+    hr = PFEntityRegisterTokenExpiredEventHandler(nullptr, nullptr,
+        [](void* ctx, PFEntityKey const* entityKey)
+        {
+            // Handle re-authentication
+        }, &expiredToken);
+
+    PFRegistrationToken refreshedToken{};
+    hr = PFEntityRegisterTokenRefreshedEventHandler(nullptr, nullptr,
+        [](void* ctx, PFEntityKey const* entityKey, const PFEntityToken* newToken)
+        {
+            // Log token refresh
+        }, &refreshedToken);
+
+    //
+    // Duplicate the handle for a subsystem
+    //
+    PFEntityHandle subsystemHandle{ nullptr };
+    hr = PFEntityDuplicateHandle(entityHandle, &subsystemHandle);
+
+    //
+    // Query entity info
+    //
+    bool isTitlePlayer{};
+    hr = PFEntityIsTitlePlayer(entityHandle, &isTitlePlayer);
+
+    size_t keySize{};
+    hr = PFEntityGetEntityKeySize(entityHandle, &keySize);
+
+    std::vector<char> keyBuffer(keySize);
+    PFEntityKey const* entityKey{};
+    hr = PFEntityGetEntityKey(entityHandle, keyBuffer.size(), keyBuffer.data(), &entityKey, nullptr);
+
+    //
+    // ... make service calls with entityHandle or subsystemHandle ...
+    //
+
+    //
+    // Cleanup: unregister handlers, then close all handles
+    //
+    PFEntityUnregisterTokenExpiredEventHandler(expiredToken);
+    PFEntityUnregisterTokenRefreshedEventHandler(refreshedToken);
+
+    PFEntityCloseHandle(subsystemHandle);
+    PFEntityCloseHandle(entityHandle);
+}
+```
+
+## API reference
+
+| Function | Description |
+|---|---|
+| [PFEntityDuplicateHandle](../../api-references/c/pfentity/functions/pfentityduplicatehandle.md) | Duplicates a handle, incrementing the ref count. Both handles must be closed independently. |
+| [PFEntityCloseHandle](../../api-references/c/pfentity/functions/pfentityclosehandle.md) | Closes a handle, decrementing the ref count. The entity is destroyed when the last handle is closed. |
+| [PFEntityGetEntityKeySize](../../api-references/c/pfentity/functions/pfentitygetentitykeysize.md) | Gets the buffer size needed to store the entity key. |
+| [PFEntityGetEntityKey](../../api-references/c/pfentity/functions/pfentitygetentitykey.md) | Gets the entity key (type and ID) for the entity. |
+| [PFEntityGetEntityTokenAsync](../../api-references/c/pfentity/functions/pfentitygetentitytokenasync.md) | Retrieves the cached entity token asynchronously. |
+| [PFEntityGetEntityTokenResultSize](../../api-references/c/pfentity/functions/pfentitygetentitytokenresultsize.md) | Gets the buffer size needed for the entity token result. |
+| [PFEntityGetEntityTokenResult](../../api-references/c/pfentity/functions/pfentitygetentitytokenresult.md) | Gets the entity token from a completed PFEntityGetEntityTokenAsync call. |
+| [PFEntityIsTitlePlayer](../../api-references/c/pfentity/functions/pfentityistitleplayer.md) | Returns whether the entity is a title_player_account. |
+| [PFEntityGetSecretKeySize](../../api-references/c/pfentity/functions/pfentitygetsecretkeysize.md) | Gets the buffer size needed for the secret key. Fails if the entity isn't a title entity. |
+| [PFEntityGetSecretKey](../../api-references/c/pfentity/functions/pfentitygetsecretkey.md) | Gets the secret key for a title entity. Only available on Windows, Linux, and macOS. |
+| [PFEntityGetAPIEndpointSize](../../api-references/c/pfentity/functions/pfentitygetapiendpointsize.md) | Gets the buffer size needed for the API endpoint string. |
+| [PFEntityGetAPIEndpoint](../../api-references/c/pfentity/functions/pfentitygetapiendpoint.md) | Gets the API endpoint from the entity's associated service config. |
+| __PFEntityGetTitleIdSize__ | Gets the buffer size needed for the title ID string. |
+| __PFEntityGetTitleId__ | Gets the title ID from the entity's associated service config. |
+| [PFEntityRegisterTokenExpiredEventHandler](../../api-references/c/pfentity/functions/pfentityregistertokenexpiredeventhandler.md) | Registers a callback for when automatic token refresh fails. |
+| [PFEntityUnregisterTokenExpiredEventHandler](../../api-references/c/pfentity/functions/pfentityunregistertokenexpiredeventhandler.md) | Unregisters a token-expired callback. |
+| [PFEntityRegisterTokenRefreshedEventHandler](../../api-references/c/pfentity/functions/pfentityregistertokenrefreshedeventhandler.md) | Registers a callback for when the SDK successfully refreshes a token. |
+| [PFEntityUnregisterTokenRefreshedEventHandler](../../api-references/c/pfentity/functions/pfentityunregistertokenrefreshedeventhandler.md) | Unregisters a token-refreshed callback. |
+
+For the complete API reference, see [PFEntity members](../../api-references/c/pfentity/pfentity_members.md).
+
+## See also
+
+- [Handling Token Expiration](relogin.md)
+- [Accessing PlayFab with a title entity](server.md)
+- [SDK Lifecycle](lifecycle.md)
+- [Quickstart: Windows](quickstart-gdk.md)
+- [Quickstart: Win32](quickstart-win32.md)
diff --git a/playfab-docs/sdks/c/event-pipeline/eventpipeline-tutorial.md b/playfab-docs/sdks/c/event-pipeline/eventpipeline-tutorial.md
index 5de18daa4..dacb359b0 100644
--- a/playfab-docs/sdks/c/event-pipeline/eventpipeline-tutorial.md
+++ b/playfab-docs/sdks/c/event-pipeline/eventpipeline-tutorial.md
@@ -16,7 +16,7 @@ This document is a quick step-by-step tutorial on how to use the Event Pipeline
 
 ## Step 1 - Initialize PlayFab Services SDK
 
-The first step is to initialize PF Service SDK using **PFServicesInitialize** and **PFServiceConfigCreateHandle** APIs.
+The first step is to initialize PF Service SDK using [**PFServicesInitialize**](../../../api-references/c/pfservices/functions/pfservicesinitialize.md) and [**PFServiceConfigCreateHandle**](../../../api-references/c/pfserviceconfig/functions/pfserviceconfigcreatehandle.md) APIs.
 
 The **PFServiceConfigCreateHandle** API receives a connection string and a title ID that can be obtained from your title on PlayFab Game Manager.
 
@@ -36,7 +36,7 @@ PFServiceConfigCreateHandle(
 
 ## Step 2 - Create Telemetry Event Pipeline
 
-Next, let's create a Telemetry Event Pipeline with a Telemetry Key using the **PFEventPipelineCreateTelemetryPipelineHandleWithKey** API. Telemetry Keys are created and managed through PlayFab Game Manager.
+Next, let's create a Telemetry Event Pipeline with a Telemetry Key using the [**PFEventPipelineCreateTelemetryPipelineHandleWithKey**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelinecreatetelemetrypipelinehandlewithkey.md) API. Telemetry Keys are created and managed through PlayFab Game Manager.
 
 When creating the PFEventPipelineTelemetryKeyConfig struct, we're passing the actual telemetry key and the service config handle we got during SDK initialization.
 
@@ -76,7 +76,7 @@ Also, since we're sending maxWaitTimeInSeconds and pollDelayInMs as null pointer
 
 We're also specifying a "Medium" compression level, setting this property compresses the body payloads and helps to optimize network resources utilization. 
 
-Then we proceed to call **PFEventPipelineUpdateConfiguration** passing the **PFEventPipelineHandle** that we got from previous step and the **PFEventPipelineConfig** struct.
+Then we proceed to call [**PFEventPipelineUpdateConfiguration**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineupdateconfiguration.md) passing the **PFEventPipelineHandle** that we got from previous step and the **PFEventPipelineConfig** struct.
 
 ```cpp
 uint32_t maxEvents = 10;
@@ -104,7 +104,7 @@ if (FAILED(hr))
 
 ## Step 4 - Emit event
 
-On this step, we proceed to emit just 1 event with name "TelemetryKeyEvent" through **PFEventPipelineEmitEvent** API.
+On this step, we proceed to emit just 1 event with name "TelemetryKeyEvent" through [**PFEventPipelineEmitEvent**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineemitevent.md) API.
 
 This event isn't linked to any entities since we haven't provided entity authentication so far.
 
@@ -134,7 +134,7 @@ if (FAILED(hr))
 
 Here, we want to get an Entity that we can use to start linking with our events.
 
-For this tutorial, we're calling **PFAuthenticationReLoginWithXUserAsync** API to get a valid **PFEntityHandle**.
+For this tutorial, we're calling [**PFAuthenticationReLoginWithXUserAsync**](../../../api-references/c/pfauthentication/functions/pfauthenticationreloginwithxuserasync.md) API to get a valid **PFEntityHandle**.
 
 > [!NOTE]
 > The userHandle object passed as part of the **PFAuthenticationLoginWithXUserRequest** is of XUserHandle type. The steps on how to get a valid XUserHandle are out of scope for this tutorial. For more information on this topic, see [XUserAddAsync](/gaming/gdk/_content/gc/reference/system/xuser/functions/xuseraddasync) documentation.
@@ -167,7 +167,7 @@ if (FAILED(hr))
 
 ## Step 6 - Add Entity to Pipeline
 
-Since we already got a valid Entity, we can call **PFEventPipelineAddUploadingEntity** and pass the Event Pipeline handle and the entity handle from the previous step. This action allows the pipeline to switch to use entity authentication.
+Since we already got a valid Entity, we can call [**PFEventPipelineAddUploadingEntity**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineadduploadingentity.md) and pass the Event Pipeline handle and the entity handle from the previous step. This action allows the pipeline to switch to use entity authentication.
 
 ```cpp
 HRESULT hr = PFEventPipelineAddUploadingEntity(
@@ -215,7 +215,7 @@ if (FAILED(hr))
 
 ## Step 8 - Close Event Pipeline handle
 
-Lastly, when we're done uploading events, the only thing we need to do is to call **PFEventPipelineCloseHandle** passing our pipeline handle.
+Lastly, when we're done uploading events, the only thing we need to do is to call [**PFEventPipelineCloseHandle**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineclosehandle.md) passing our pipeline handle.
 
 ```cpp
 PFEventPipelineCloseHandle(handle);
diff --git a/playfab-docs/sdks/c/event-pipeline/eventpipeline.md b/playfab-docs/sdks/c/event-pipeline/eventpipeline.md
index 3a18a3ee0..1840766af 100644
--- a/playfab-docs/sdks/c/event-pipeline/eventpipeline.md
+++ b/playfab-docs/sdks/c/event-pipeline/eventpipeline.md
@@ -68,7 +68,7 @@ If Telemetry Key auth is used, a **PFEventPipelineTelemetryKeyConfig** struct is
 
 1. A Telemetry Key that consists of a string that is created and managed via PlayFab Game Manager.
 
-2. A **PFServiceConfigHandle** that lets the SDK know which is the right service configuration that should be used for uploading the events. The service config handle is created during SDK Initialization by calling **PFServiceConfigCreateHandle**.
+2. A **PFServiceConfigHandle** that lets the SDK know which is the right service configuration that should be used for uploading the events. The service config handle is created during SDK Initialization by calling [**PFServiceConfigCreateHandle**](../../../api-references/c/pfserviceconfig/functions/pfserviceconfigcreatehandle.md).
 
 If the developer wants to use a Telemetry Key it's important to provide it at pipeline creation, since there's no way to add a Telemetry Key after the pipeline has been instantiated.
 
@@ -87,7 +87,18 @@ The configurable properties are:
 - **retryOnDisconnect**: The event pipeline will retry sending events that failed due to lost connection. Only available for Telemetry Event Pipeline.
 - **bufferSize**: The limit of the amount of events in the pipeline's buffer.
 
-In the case where **PFEventPipelineConfig** has only some properties specified, the ones being empty are overwritten and use the default values.
+### Default values
+
+| Property | Telemetry Pipeline | PlayStream Pipeline |
+|---|---|---|
+| **maxEventsPerBatch** | 5 | 5 |
+| **maxWaitTimeInSeconds** | 3 | 3 |
+| **pollDelayInMs** | 3000 | 10 |
+| **compressionLevel** | None (disabled) | None (disabled) |
+| **retryOnDisconnect** | true | N/A |
+| **bufferSize** | 1024 | 1024 |
+
+In the case where [**PFEventPipelineConfig**](../../../api-references/c/pfeventpipeline/structs/pfeventpipelineconfig.md) has only some properties specified, the ones being empty are overwritten and use the default values.
 
 For an example of how any of these properties can be updated for the event pipeline see _[Update Pipeline Configuration](#update-pipeline-configuration)_.
 
@@ -95,7 +106,7 @@ For an example of how any of these properties can be updated for the event pipel
 
 The Event Pipeline provides an option of compressing body payloads using GZIP Compression standard.
 
-The desired compression level can be specified inside the **PFEventPipelineConfig** struct that is part of the **PFEventPipelineUpdateConfiguration** API parameters.
+The desired compression level can be specified inside the **PFEventPipelineConfig** struct that is part of the [**PFEventPipelineUpdateConfiguration**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineupdateconfiguration.md) API parameters.
 
 A lower compression level achieves less compression but has the highest speed and a higher compression level achieves better compression rates but has the slowest compression speed. The difference in compression rates is all dependent on the type of data being sent. Depending on the size and randomness of the data, compression rates can be the same even on different levels.
 
@@ -113,9 +124,9 @@ However, if the game developer wants a "fire and forget" experience, can omit pr
 
 The event handlers that can be provided are as follows:
 
-- **PFEventPipelineBatchUploadSucceededEventHandler**: As the name suggests, it receives all the events that are successfully uploaded to PlayFab.
+- [**PFEventPipelineBatchUploadSucceededEventHandler**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelinebatchuploadsucceededeventhandler.md): As the name suggests, it receives all the events that are successfully uploaded to PlayFab.
 
-- **PFEventPipelineBatchUploadFailedEventHandler**: It will receive all the failed events after going through the pipeline retry logic.
+- [**PFEventPipelineBatchUploadFailedEventHandler**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelinebatchuploadfailedeventhandler.md): It will receive all the failed events after going through the pipeline retry logic.
 
 ### Pipeline creation examples
 
@@ -123,7 +134,7 @@ Below you can find different examples on how to instantiate an event pipeline ba
 
 1. **Telemetry Event Pipeline creation with Entity auth**
 
-    If the developer wants to send Telemetry Events and doesn't have the need of using Telemetry Key auth, the **PFEventPipelineCreateTelemetryPipelineHandleWithEntity** API serves for this purpose as seen in the next example:
+    If the developer wants to send Telemetry Events and doesn't have the need of using Telemetry Key auth, the [**PFEventPipelineCreateTelemetryPipelineHandleWithEntity**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelinecreatetelemetrypipelinehandlewithentity.md) API serves for this purpose as seen in the next example:
 
     ```cpp
     void EventPipelineCreation(PFEntityHandle entityHandle, XTaskQueueHandle taskQueueHandle)
@@ -253,7 +264,7 @@ As seen in the example, ***OnBatchUploadedHandler*** and ***OnBatchUploadFailedH
 
 ### Emitting events
 
-Emitting events is a straightforward operation once the event pipeline is already created. The game developer should call **PFEventPipelineEmitEvent** API that receives the existing event pipeline handle and the event they want to send.
+Emitting events is a straightforward operation once the event pipeline is already created. The game developer should call [**PFEventPipelineEmitEvent**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineemitevent.md) API that receives the existing event pipeline handle and the event they want to send.
 
 ```cpp
 void EmitEvent(PFEventPipelineHandle handle)
@@ -321,7 +332,7 @@ Make sure to set an adequate size of a buffer for your needs.
 
 If a pipeline was created using only a Telemetry Key configuration, there's a way to switch to Entity authentication or if you want to update your pipeline to use a different Entity.
 
-By using the **PFEventPipelineAddUploadingEntity**, it's possible to attach an entity to a running pipeline without the need of reinitialize it. It also replaces the existing entity, if any.
+By using the [**PFEventPipelineAddUploadingEntity**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineadduploadingentity.md), it's possible to attach an entity to a running pipeline without the need of reinitialize it. It also replaces the existing entity, if any.
 
 Example:
 
@@ -377,7 +388,7 @@ After this call, the pipeline will start logging any subsequent events linked to
 
 ### Switching to Telemetry Key auth
 
-Expanding on the previous scenario, if the developer wants to go back to Telemetry Auth and detach the event logging from the entity they can call **PFEventPipelineRemoveUploadingEntity** and pass the event pipeline handle like this:
+Expanding on the previous scenario, if the developer wants to go back to Telemetry Auth and detach the event logging from the entity they can call [**PFEventPipelineRemoveUploadingEntity**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineremoveuploadingentity.md) and pass the event pipeline handle like this:
 
 ```cpp
 void EventPipelineRemoveEntity(PFEventPipelineHandle handle)
@@ -398,7 +409,7 @@ This call removes the entity and effectively switches back to Telemetry Key auth
 
 ### **Update Pipeline configuration**
 
-Pipelines can be easily updated using the **PFEventPipelineUpdateConfiguration** API, which receives the existing event pipeline handle and a new configuration struct as follows:
+Pipelines can be easily updated using the [**PFEventPipelineUpdateConfiguration**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineupdateconfiguration.md) API, which receives the existing event pipeline handle and a new configuration struct as follows:
 
 ```cpp
 void EventPipelineUpdateConfiguration(PFEventPipelineHandle handle)
@@ -441,6 +452,23 @@ In case a Telemetry key is deactivated or if an invalid key is provided at pipel
 
 In the eventual case where the customer reactivates the key, the pipeline won't realize about that and will keep sending failures back through the failed event handler. It's worth mentioning that this behavior is session-based, which means that if the title is restarted, a new pipeline is created and will be able to upload events again.
 
+## Pipeline handle lifecycle
+
+Like other PlayFab handles, event pipeline handles use a duplicate/close pattern:
+
+- [**PFEventPipelineCloseHandle**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineclosehandle.md): Closes a pipeline handle. When the last handle to a pipeline is closed, the pipeline is destroyed and any remaining buffered events are flushed.
+- [**PFEventPipelineDuplicateHandle**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineduplicatehandle.md): Duplicates a pipeline handle. Both the original and duplicated handle must be closed independently with [**PFEventPipelineCloseHandle**](../../../api-references/c/pfeventpipeline/functions/pfeventpipelineclosehandle.md).
+
+```cpp
+// Duplicate a handle for use in another component
+PFEventPipelineHandle duplicatedHandle;
+HRESULT hr = PFEventPipelineDuplicateHandle(originalHandle, &duplicatedHandle);
+
+// When done, close both handles independently
+PFEventPipelineCloseHandle(duplicatedHandle);
+PFEventPipelineCloseHandle(originalHandle);
+```
+
 ## See also
 
 - [Event pipeline tutorial](eventpipeline-tutorial.md)
diff --git a/playfab-docs/sdks/c/http-config.md b/playfab-docs/sdks/c/http-config.md
new file mode 100644
index 000000000..3243f8e80
--- /dev/null
+++ b/playfab-docs/sdks/c/http-config.md
@@ -0,0 +1,137 @@
+---
+title: HTTP Configuration
+author: amccalib
+description: Configuring HTTP retry and compression settings in the PlayFab Services SDK
+ms.author: andmcc
+ms.date: 02/14/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, c++, windows, xbox, gdk, http, retry, compression
+ms.localizationpriority: medium
+---
+
+# HTTP Configuration
+
+The PlayFab Services SDK provides functions to configure how HTTP requests are made, including automatic retry behavior and response compression. These settings are global and apply to all PlayFab API calls made by the SDK.
+
+Configure HTTP settings after calling [**PFInitialize**](../../api-references/c/pfcore/functions/pfinitialize.md) and [**PFServicesInitialize**](../../api-references/c/pfservices/functions/pfservicesinitialize.md), but before making any API calls.
+
+## Retry settings
+
+The **PFHttpRetrySettings** struct controls how the SDK handles transient HTTP failures, such as throttling errors (HTTP 429). By default, the SDK automatically retries these failures with backoff.
+
+| Field | Type | Default | Description |
+|---|---|---|---|
+| `allowRetry` | `bool` | `true` | Controls whether the SDK automatically retries select errors. Some errors are never retried and are always returned directly. |
+| `minimumRetryDelayInSeconds` | `uint32_t` | 2 | The minimum number of seconds to wait before retrying a failed request. Can't be set below 2 seconds. |
+| `timeoutWindowInSeconds` | `uint32_t` | 20 | The maximum number of seconds the SDK attempts retries before returning the error to the caller. |
+
+For more information on which errors the SDK retries automatically, see [Handling PlayFab Errors](errors.md).
+
+### Set retry settings
+
+Call **PFSetHttpRetrySettings** to customize the retry behavior. For example, to increase the retry window for calls that can tolerate longer waits:
+
+```cpp
+PFHttpRetrySettings retrySettings{};
+retrySettings.allowRetry = true;
+retrySettings.minimumRetryDelayInSeconds = 4;
+retrySettings.timeoutWindowInSeconds = 60;
+
+HRESULT hr = PFSetHttpRetrySettings(&retrySettings);
+if (FAILED(hr))
+{
+    // Handle error
+}
+```
+
+### Get retry settings
+
+Call **PFGetHttpRetrySettings** to retrieve the current retry configuration:
+
+```cpp
+PFHttpRetrySettings currentSettings{};
+HRESULT hr = PFGetHttpRetrySettings(&currentSettings);
+if (SUCCEEDED(hr))
+{
+    printf("Retry enabled: %s\n", currentSettings.allowRetry ? "true" : "false");
+    printf("Min delay: %u seconds\n", currentSettings.minimumRetryDelayInSeconds);
+    printf("Timeout window: %u seconds\n", currentSettings.timeoutWindowInSeconds);
+}
+```
+
+### Disable automatic retries
+
+If you want to handle all retry logic yourself, disable automatic retries:
+
+```cpp
+PFHttpRetrySettings retrySettings{};
+retrySettings.allowRetry = false;
+retrySettings.minimumRetryDelayInSeconds = 2;
+retrySettings.timeoutWindowInSeconds = 20;
+
+HRESULT hr = PFSetHttpRetrySettings(&retrySettings);
+```
+
+## HTTP settings
+
+The **PFHttpSettings** struct controls general HTTP behavior for all SDK requests.
+
+| Field | Type | Default | Description |
+|---|---|---|---|
+| `requestResponseCompression` | `bool` | `false` | When enabled, the SDK requests that API responses be gzip-compressed by setting the `Accept-Encoding` header to `application/gzip`. |
+
+### Enable response compression
+
+Enabling response compression can reduce bandwidth usage, which is useful for calls that return large payloads. Call **PFSetHttpSettings** to enable it:
+
+```cpp
+PFHttpSettings httpSettings{};
+httpSettings.requestResponseCompression = true;
+
+HRESULT hr = PFSetHttpSettings(&httpSettings);
+if (FAILED(hr))
+{
+    // Handle error
+}
+```
+
+> [!NOTE]
+> To decompress a compressed response, **HCHttpCallResponseSetGzipCompressed** must be called before calling **HCHttpCallPerformAsync**.
+
+### Get HTTP settings
+
+Call **PFGetHttpSettings** to retrieve the current HTTP configuration:
+
+```cpp
+PFHttpSettings currentSettings{};
+HRESULT hr = PFGetHttpSettings(&currentSettings);
+if (SUCCEEDED(hr))
+{
+    printf("Response compression: %s\n", currentSettings.requestResponseCompression ? "enabled" : "disabled");
+}
+```
+
+## Typical initialization pattern
+
+The following example shows where HTTP configuration fits into the overall SDK initialization flow:
+
+```cpp
+// 1. Initialize the SDK
+HRESULT hr = PFInitialize(nullptr);
+hr = PFServicesInitialize(nullptr);
+
+// 2. Configure HTTP settings before making any API calls
+PFHttpRetrySettings retrySettings{};
+retrySettings.allowRetry = true;
+retrySettings.minimumRetryDelayInSeconds = 2;
+retrySettings.timeoutWindowInSeconds = 30;
+PFSetHttpRetrySettings(&retrySettings);
+
+PFHttpSettings httpSettings{};
+httpSettings.requestResponseCompression = true;
+PFSetHttpSettings(&httpSettings);
+
+// 3. Create service config and begin making API calls
+// ...
+```
diff --git a/playfab-docs/sdks/c/index.md b/playfab-docs/sdks/c/index.md
index baef72845..23f4a01fd 100644
--- a/playfab-docs/sdks/c/index.md
+++ b/playfab-docs/sdks/c/index.md
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 
 # PlayFab Services SDK for C/C++
 
-The new PlayFab Services SDK for C/C++ is currently available for the following platforms: Win32 (x64 only), Nintendo Switch, Sony PlayStation&#174;, iOS, macOS, Android, Linux, and the Microsoft GDK. Depending on the platform you're targeting, the way you acquire the SDK differs.
+The new PlayFab Services SDK for C/C++ is currently available for the following platforms: Win32 (x64 only), Nintendo Switch, PlayStation&#174;5, PlayStation&#174;4, iOS, macOS, Android, Linux, and the Microsoft GDK. Depending on the platform you're targeting, the way you acquire the SDK differs.
 
 ## Win32, iOS, macOS, Android, Linux
 
@@ -26,40 +26,40 @@ To learn more about the GDK, see the public documentation: [GDK documentation ho
 
 ## Nintendo Switch
 
-Before you can access the PlayFab Services SDK for Nintendo Switch, you need to confirm your registered developer status via the PlayFab page in Nintendo's middleware directory. See more information here: [Request access](../request-access-for-sdks-samples.md).
+Before you can access the PlayFab Services SDK for Nintendo Switch, you need to confirm your registered developer status via the PlayFab page in Nintendo's middleware directory. For more information, see [Request access](../request-access-for-sdks-samples.md).
 
 Once you've been granted access to the Switch SDK, you can download it from the git repo here: [PlayFabCSdk.Switch](https://dev.azure.com/PlayFabPrivate/Switch/_git/PlayFabCSdk.Switch).
 
-## Sony PlayStation
+## PlayStation 5 / PlayStation 4
 
-Before you can access the PlayFab Services SDK for PlayStation, you need to confirm your registered developer status via the PlayFab page in Sony's middleware directory. See more information here: [Request access](../request-access-for-sdks-samples.md).
+Confirm your developer status on the PlayFab page in the middleware directory of the developer portal before accessing the PlayFab Services SDK for PlayStation. For more information, see [Request access](../request-access-for-sdks-samples.md).
 
 Once you've been granted access to the PlayStation SDK, you can download it from the git repo here: [PlayFabCSdk.PS4](https://dev.azure.com/PlayFabPrivate/PS4/_git/PlayFabCSdk.PS4) and [PlayFabCSdk.PS5](https://dev.azure.com/PlayFabPrivate/PS5/_git/PlayFabCSdk.PS5).
 
 ## What this SDK includes
 
-The PlayFab Services SDK for C/C++ is for use by a game's runtime components (clients and servers) on Win32 (x64 only), Nintendo Switch, Sony PlayStation&#174;, iOS, macOS, Android, Linux, and the Microsoft GDK. It includes only the subset of feature areas and service calls appropriate for games running on those platforms.
+The PlayFab Services SDK for C/C++ is for use by a game's runtime components (clients and servers) on Win32 (x64 only), Nintendo Switch, PlayStation&#174;5, PlayStation&#174;4, iOS, macOS, Android, Linux, and the Microsoft GDK. It includes only the subset of feature areas and service calls appropriate for games running on those platforms.
 
 Here are some notable differences when compared to other, more general purpose, PlayFab SDKs:
-- The PlayFab Admin API is not included. This SDK is intended to be part of the game runtime (or dedicated server), not for tools or generic services.
+- The PlayFab Admin API isn't included. This SDK is intended to be part of the game runtime (or dedicated server), not for tools or generic services.
 - The PlayFab Server API is only available for select platforms that are used for hosting game servers, specifically Windows, Linux, and macOS.
-- The available login methods depend on the platform. For instance, LoginWithApple is only available on Apple devices.
+- The available sign in methods depends on the platform. For instance, LoginWithApple is only available on Apple devices.
 - This SDK removes some older or underutilized feature areas to reduce overall complexity. These areas include economy v1, player stats and leaderboards, and characters.
 
 ## Benefits of this SDK
 
-- Allows titles to control the memory allocations when calling Playfab Services. See [Managing Memory Allocations](memory.md) to learn more.
-- Allows titles to gain full control of thread handling when calling Playfab Services. See [Making async calls in the PlayFab Services SDK](async.md) to learn more.
+- Allows titles to control the memory allocations when calling PlayFab Services. See [Managing Memory Allocations](memory.md) to learn more.
+- Allows titles to gain full control of thread handling when calling PlayFab Services. See [Making async calls in the PlayFab Services SDK](async.md) to learn more.
 - Portable C interface that allows maximum compatibility across platforms, compilers, and languages.
 - High-performance telemetry pipeline with support for low-cost queuing and batch transmission of events.
 
 ## Platforms supported by this SDK
 
-This SDK is appropriate for x64 Win32 games and game servers, Nintendo Switch games, Sony PlayStation games, iOS games, Android games, macOS games, Linux games, and games utilizing the GDK on Windows and Xbox.
+This SDK is appropriate for x64 Win32 games and game servers, Nintendo Switch games, PlayStation games, iOS games, Android games, macOS games, Linux games, and games utilizing the GDK on Windows and Xbox.
 
 ## When not to use this SDK
 
-There are scenarios where this SDK is not appropriate:
+There are scenarios where this SDK isn't appropriate:
 
 - If your game utilizes a game engine for which there's already an engine-specific PlayFab SDK, that SDK is a better fit: [Unreal Engine](../unreal/index.md), [Unity3D](../unity3d/index.md).
 
@@ -77,8 +77,8 @@ There are scenarios where this SDK is not appropriate:
     - The macOS version of this SDK is available via GitHub. Follow the instructions here to start making basic calls to PlayFab: [Quickstart for macOS](quickstart-macos.md).
 - Linux
     - The Linux version of this SDK is available via GitHub. Follow the instructions here to start making basic calls to PlayFab: [Quickstart for Linux](./quickstart-linux.md).
-- Sony Playstation
-    - See [Sony Playstation](#sony-playstation)
+- Playstation
+    - See [PlayStation 5 / PlayStation 4](#playstation-5--playstation-4)
 - Nintendo Switch
     - See [Nintendo Switch](#nintendo-switch)
 
@@ -87,7 +87,8 @@ There are scenarios where this SDK is not appropriate:
 [API reference documentation](../../api-references/c/pfauthentication/pfauthentication_members.md)
 
 "PlayStation" is a registered trademark or trademark of Sony Interactive Entertainment Inc.
-
+<!--- 
 "PS4" is a registered trademark or trademark of Sony Interactive Entertainment Inc.
 
 "PS5" is a registered trademark or trademark of Sony Interactive Entertainment Inc.
+--->
\ No newline at end of file
diff --git a/playfab-docs/sdks/c/lifecycle.md b/playfab-docs/sdks/c/lifecycle.md
new file mode 100644
index 000000000..c810b14ac
--- /dev/null
+++ b/playfab-docs/sdks/c/lifecycle.md
@@ -0,0 +1,267 @@
+---
+title: SDK Lifecycle
+author: amccalib
+description: Initialization, configuration, and shutdown of the PlayFab Services SDK
+ms.author: andmcc
+ms.date: 02/14/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, c++, windows, xbox, gdk, initialization, shutdown, lifecycle
+ms.localizationpriority: medium
+---
+
+# SDK Lifecycle
+
+This page covers the complete startup and shutdown sequence for the PlayFab Services SDK. Every title follows the same high-level pattern: configure optional hooks, initialize Core, create a service configuration, initialize Services, do work, then shut down in reverse order.
+
+## Initialization sequence
+
+Initialization has four steps. The first is optional; the remaining three are required.
+
+```
+PFMemSetFunctions (optional)  →  PFInitialize  →  PFServiceConfigCreateHandle  →  PFServicesInitialize
+```
+
+### Step 1: Set custom memory hooks (optional)
+
+If your title uses a custom memory allocator, call [**PFMemSetFunctions**](../../api-references/c/pfplatform/functions/pfmemsetfunctions.md) before any other PlayFab API. This routes all SDK memory allocations through your own `alloc` and `free` callbacks.
+
+```cpp
+PFMemoryHooks hooks{};
+hooks.alloc = MyAllocFunction;
+hooks.free = MyFreeFunction;
+HRESULT hr = PFMemSetFunctions(&hooks);
+```
+
+> [!IMPORTANT]
+> [__PFMemSetFunctions__](../../api-references/c/pfplatform/functions/pfmemsetfunctions.md) must be called before [**PFInitialize**](../../api-references/c/pfcore/functions/pfinitialize.md). It can't be called again after hooks have been set.
+
+If you don't need custom memory management, skip this step. The SDK uses default allocation routines.
+
+### Step 2: Initialize PlayFab Core
+
+[__PFInitialize__](../../api-references/c/pfcore/functions/pfinitialize.md) sets up the SDK's global state, including the HTTP layer and background task queue. The exact signature varies by platform.
+
+#### Windows, Linux, iOS, and macOS
+
+```cpp
+HRESULT hr = PFInitialize(nullptr); // Uses a default threadpool queue
+```
+
+Pass an __XTaskQueueHandle__ if you want to control which queue handles background work. Pass `nullptr` to use the default threadpool queue.
+
+#### Android
+
+On Android, you must also provide the Java VM and application context so the SDK can initialize libHttpClient:
+
+```cpp
+HRESULT hr = PFInitialize(nullptr, javaVm, applicationContext);
+```
+
+> [!NOTE]
+> If you don't call __PFInitialize__ explicitly, [**PFServicesInitialize**](../../api-references/c/pfservices/functions/pfservicesinitialize.md) calls it internally with default parameters. This is fine for most titles. However, if you're using custom memory hooks via __PFMemSetFunctions__, you **must** call __PFInitialize__ yourself — otherwise [__PFServicesInitialize__](../../api-references/c/pfservices/functions/pfservicesinitialize.md) initializes Core before your memory hooks take effect, and the SDK uses default allocation routines instead.
+
+### Step 3: Create a service configuration
+
+[**PFServiceConfigCreateHandle**](../../api-references/c/pfserviceconfig/functions/pfserviceconfigcreatehandle.md) creates a handle that tells the SDK which PlayFab title and endpoint to target. You'll find both values in [Game Manager](https://developer.playfab.com).
+
+```cpp
+PFServiceConfigHandle serviceConfigHandle{ nullptr };
+HRESULT hr = PFServiceConfigCreateHandle(
+    "https://ABCDEF.playfabapi.com",    // API endpoint from Game Manager
+    "ABCDEF",                           // Title ID from Game Manager
+    &serviceConfigHandle);
+```
+
+The returned __PFServiceConfigHandle__ is required for all subsequent login calls.
+
+### Step 4: Initialize PlayFab Services
+
+__PFServicesInitialize__ sets up the Services layer (Inventory, Leaderboards, Friends, and so on) on top of Core.
+
+#### Windows, Linux, iOS, and macOS
+
+```cpp
+HRESULT hr = PFServicesInitialize(nullptr);
+```
+
+The parameter is reserved for future use; pass `nullptr`.
+
+#### Android
+
+On Android, pass an __HCInitArgs__ struct containing the Java VM and application context:
+
+```cpp
+HRESULT hr = PFServicesInitialize(nullptr, initArgs);
+```
+
+After this call succeeds, the SDK is ready. You can log in players and make service calls.
+
+## PFServiceConfigHandle lifecycle
+
+A __PFServiceConfigHandle__ is a ref-counted handle. The SDK manages its internal lifetime through reference counting, but you're responsible for closing every handle you own.
+
+| Function | Description |
+|---|---|
+| [**PFServiceConfigCreateHandle**](../../api-references/c/pfserviceconfig/functions/pfserviceconfigcreatehandle.md) | Creates a new handle. The initial ref count is 1. |
+| [**PFServiceConfigDuplicateHandle**](../../api-references/c/pfserviceconfig/functions/pfserviceconfigduplicatehandle.md) | Increments the ref count and returns a second handle. Both handles must be closed independently. |
+| [**PFServiceConfigCloseHandle**](../../api-references/c/pfserviceconfig/functions/pfserviceconfigclosehandle.md) | Decrements the ref count. When it reaches 0, the config is destroyed. |
+| [**PFServiceConfigGetAPIEndpoint**](../../api-references/c/pfserviceconfig/functions/pfserviceconfiggetapiendpoint.md) | Retrieves the API endpoint string. Call [**PFServiceConfigGetAPIEndpointSize**](../../api-references/c/pfserviceconfig/functions/pfserviceconfiggetapiendpointsize.md) first to determine the buffer size. |
+| [**PFServiceConfigGetTitleId**](../../api-references/c/pfserviceconfig/functions/pfserviceconfiggettitleid.md) | Retrieves the title ID string. Call [**PFServiceConfigGetTitleIdSize**](../../api-references/c/pfserviceconfig/functions/pfserviceconfiggettitleidsize.md) first to determine the buffer size. |
+
+### Duplicating a handle
+
+Use [__PFServiceConfigDuplicateHandle__](../../api-references/c/pfserviceconfig/functions/pfserviceconfigduplicatehandle.md) when you need to share a service config across components that manage their own lifetimes:
+
+```cpp
+PFServiceConfigHandle duplicatedHandle{ nullptr };
+HRESULT hr = PFServiceConfigDuplicateHandle(serviceConfigHandle, &duplicatedHandle);
+
+// Both handles are now valid and must be closed separately
+PFServiceConfigCloseHandle(duplicatedHandle);
+PFServiceConfigCloseHandle(serviceConfigHandle);
+```
+
+## Shutdown sequence
+
+Shutdown is the reverse of initialization. You must uninitialize Services before Core, and both calls are asynchronous.
+
+```
+Close handles  →  PFServicesUninitializeAsync  →  PFUninitializeAsync
+```
+
+### Step 1: Close all open handles
+
+Before tearing down the SDK, close every __PFEntityHandle__ and __PFServiceConfigHandle__ you own:
+
+```cpp
+PFEntityCloseHandle(entityHandle);
+entityHandle = nullptr;
+
+PFServiceConfigCloseHandle(serviceConfigHandle);
+serviceConfigHandle = nullptr;
+```
+
+### Step 2: Uninitialize Services
+
+[**PFServicesUninitializeAsync**](../../api-references/c/pfservices/functions/pfservicesuninitializeasync.md) tears down the Services layer. Wait for it to complete before proceeding.
+
+```cpp
+XAsyncBlock asyncServices{};
+HRESULT hr = PFServicesUninitializeAsync(&asyncServices);
+hr = XAsyncGetStatus(&asyncServices, true); // Blocking wait
+```
+
+### Step 3: Uninitialize Core
+
+After Services cleanup finishes, call [**PFUninitializeAsync**](../../api-references/c/pfcore/functions/pfuninitializeasync.md) to tear down Core:
+
+```cpp
+XAsyncBlock asyncCore{};
+HRESULT hr = PFUninitializeAsync(&asyncCore);
+hr = XAsyncGetStatus(&asyncCore, true); // Blocking wait
+```
+
+> [!NOTE]
+> If you didn't call __PFInitialize__ explicitly, you can skip __PFUninitializeAsync__. In that case, [__PFServicesUninitializeAsync__](../../api-references/c/pfservices/functions/pfservicesuninitializeasync.md) handles Core cleanup automatically. However, if you did call __PFInitialize__ yourself, you must call [__PFUninitializeAsync__](../../api-references/c/pfcore/functions/pfuninitializeasync.md) yourself.
+
+## Complete example
+
+This example shows the full lifecycle from initialization through shutdown on a Windows title:
+
+```cpp
+#include <playfab/services/PFServices.h>
+
+void RunPlayFab()
+{
+    //
+    // Optional: set custom memory hooks
+    //
+    PFMemoryHooks hooks{};
+    hooks.alloc = MyAllocFunction;
+    hooks.free = MyFreeFunction;
+    HRESULT hr = PFMemSetFunctions(&hooks);
+
+    //
+    // Initialize Core
+    //
+    hr = PFInitialize(nullptr);
+
+    //
+    // Create a service configuration
+    //
+    PFServiceConfigHandle serviceConfigHandle{ nullptr };
+    hr = PFServiceConfigCreateHandle(
+        "https://ABCDEF.playfabapi.com",
+        "ABCDEF",
+        &serviceConfigHandle);
+
+    //
+    // Initialize Services
+    //
+    hr = PFServicesInitialize(nullptr);
+
+    //
+    // Log in a player (Windows example using XUser)
+    //
+    PFAuthenticationLoginWithXUserRequest request{};
+    request.createAccount = true;
+    request.user = userHandle;
+
+    XAsyncBlock asyncLogin{};
+    hr = PFAuthenticationLoginWithXUserAsync(serviceConfigHandle, &request, &asyncLogin);
+    hr = XAsyncGetStatus(&asyncLogin, true);
+
+    size_t bufferSize{};
+    hr = PFAuthenticationLoginWithXUserGetResultSize(&asyncLogin, &bufferSize);
+
+    std::vector<char> loginResultBuffer(bufferSize);
+    PFAuthenticationLoginResult const* loginResult{};
+    PFEntityHandle entityHandle{ nullptr };
+    hr = PFAuthenticationLoginWithXUserGetResult(
+        &asyncLogin, &entityHandle,
+        loginResultBuffer.size(), loginResultBuffer.data(),
+        &loginResult, nullptr);
+
+    //
+    // ... make service calls ...
+    //
+
+    //
+    // Shutdown: close handles first
+    //
+    PFEntityCloseHandle(entityHandle);
+    entityHandle = nullptr;
+
+    PFServiceConfigCloseHandle(serviceConfigHandle);
+    serviceConfigHandle = nullptr;
+
+    //
+    // Shutdown: uninitialize Services, then Core
+    //
+    XAsyncBlock asyncServices{};
+    hr = PFServicesUninitializeAsync(&asyncServices);
+    hr = XAsyncGetStatus(&asyncServices, true);
+
+    XAsyncBlock asyncCore{};
+    hr = PFUninitializeAsync(&asyncCore);
+    hr = XAsyncGetStatus(&asyncCore, true);
+}
+```
+
+## Common mistakes
+
+| Mistake | What happens | Fix |
+|---|---|---|
+| Calling [**PFMemSetFunctions**](../../api-references/c/pfplatform/functions/pfmemsetfunctions.md) after [**PFInitialize**](../../api-references/c/pfcore/functions/pfinitialize.md) | The call fails. Memory hooks can only be set before initialization. | Move [**PFMemSetFunctions**](../../api-references/c/pfplatform/functions/pfmemsetfunctions.md) to the very first PlayFab call in your program. |
+| Calling [**PFUninitializeAsync**](../../api-references/c/pfcore/functions/pfuninitializeasync.md) before [**PFServicesUninitializeAsync**](../../api-references/c/pfservices/functions/pfservicesuninitializeasync.md) | Undefined behavior. Core is torn down while Services still depends on it. | Always uninitialize Services first, wait for completion, then uninitialize Core. |
+| Forgetting to call [**PFUninitializeAsync**](../../api-references/c/pfcore/functions/pfuninitializeasync.md) after explicit [**PFInitialize**](../../api-references/c/pfcore/functions/pfinitialize.md) | Core resources leak. The background queue and HTTP layer aren't cleaned up. | If you called [**PFInitialize**](../../api-references/c/pfcore/functions/pfinitialize.md), you must call [**PFUninitializeAsync**](../../api-references/c/pfcore/functions/pfuninitializeasync.md). |
+| Not waiting for async uninitialize to complete | The process may exit while cleanup is still in progress, causing crashes or hangs. | Use `XAsyncGetStatus(async, true)` or an __XAsyncBlock__ callback to wait for completion. |
+| Leaking __PFServiceConfigHandle__ or __PFEntityHandle__ | Ref-counted resources aren't freed and may prevent clean shutdown. | Close every handle you create or duplicate before calling uninitialize. |
+
+## See also
+
+- [Quickstart: Win32](quickstart-win32.md)
+- [Quickstart: Windows](quickstart-gdk.md)
+- [Debug Tracing](tracing.md)
+- [Asynchronous Programming Model](/gaming/gdk/_content/gc/system/overviews/async-programming-model)
diff --git a/playfab-docs/sdks/c/memory.md b/playfab-docs/sdks/c/memory.md
index f2cb2504d..53f84539b 100644
--- a/playfab-docs/sdks/c/memory.md
+++ b/playfab-docs/sdks/c/memory.md
@@ -17,20 +17,26 @@ With the C API in the PlayFab Services SDK, you can specify a function callback
 To manually specify your memory routines, you can take the following steps:
 
 * At the start of the game:
-    * Call **PFMemSetFunctions** to specify the allocation callbacks for assigning and releasing memory.
-    * Call **PFServicesInitialize** to initialize the library instance.
+    * Call [**PFMemSetFunctions**](../../api-references/c/pfplatform/functions/pfmemsetfunctions.md) to specify the allocation callbacks for assigning and releasing memory.
+    * Call [**PFInitialize**](../../api-references/c/pfcore/functions/pfinitialize.md) to initialize the PlayFab Core library.
+    * Call [**PFServicesInitialize**](../../api-references/c/pfservices/functions/pfservicesinitialize.md) to initialize the PlayFab Services library.
+
+> [!IMPORTANT]
+> The order matters. **PFMemSetFunctions** must come before **PFInitialize**, and **PFInitialize** must come before **PFServicesInitialize**. If you skip the explicit **PFInitialize** call, **PFServicesInitialize** initializes Core internally—but at that point your memory hooks aren't applied yet, so the SDK uses default allocation routines instead.
 
 ```cpp
     PFMemoryHooks playFabHooks{ MyAllocHook, MyFreeHook };
     PFMemSetFunctions(&playFabHooks);
-    HRESULT hr = PFServicesInitialize(nullptr); // Add your own error handling when FAILED(hr) == true
+    HRESULT hr = PFInitialize(nullptr); // Add your own error handling when FAILED(hr) == true
+    hr = PFServicesInitialize(nullptr); // Add your own error handling when FAILED(hr) == true
 ```
 
 * While the game is running:
-    * Any calls into the SDK that allocate or free memory will call the specified memory handling callbacks.
+    * Any calls into the SDK that allocate or free memory call the specified memory handling callbacks.
 
 * When the game exits:
-    * Call **PFServicesUninitializeAsync** to reclaim all resources associated with the SDK.
+    * Call [**PFServicesUninitializeAsync**](../../api-references/c/pfservices/functions/pfservicesuninitializeasync.md) to reclaim all resources associated with PlayFab Services.
+    * Call [**PFUninitializeAsync**](../../api-references/c/pfcore/functions/pfuninitializeasync.md) to reclaim all resources associated with PlayFab Core.
     * Clean up your game's custom memory manager.
 
 ## Reference
diff --git a/playfab-docs/sdks/c/quickstart-gdk.md b/playfab-docs/sdks/c/quickstart-gdk.md
index 1240fc2ba..03d22d339 100644
--- a/playfab-docs/sdks/c/quickstart-gdk.md
+++ b/playfab-docs/sdks/c/quickstart-gdk.md
@@ -80,6 +80,12 @@ Along with an __S_OK__ result, you get back a __PFEntityHandle__. You use this h
     hr = PFAuthenticationLoginWithXUserGetResult(&async, &entityHandle, loginResultBuffer.size(), loginResultBuffer.data(), &loginResult, nullptr);
 ```
 
+## Handling suspend and resume
+
+GDK games can be suspended for extended periods (for example, via Quick Resume). If the entity token expires during suspension, the SDK detects this on resume and notifies your game. You should register for the **TokenExpiredHandler** early in your game's lifecycle so you can re-authenticate and reconnect services when needed.
+
+For full details, see [Handling Token Expiration](relogin.md).
+
 ## Service Calls
 
 After logging the player in, you can now make calls to the PlayFab backend. Here's an example of a call to get files stored in PlayFab for the current player.
diff --git a/playfab-docs/sdks/c/relogin.md b/playfab-docs/sdks/c/relogin.md
index 87a83c0ae..85d3bfc0e 100644
--- a/playfab-docs/sdks/c/relogin.md
+++ b/playfab-docs/sdks/c/relogin.md
@@ -3,20 +3,36 @@ title: Handling Token Expiration
 author: amccalib
 description: Handling Token Expiration and Relogin in the PlayFab Services SDK
 ms.author: andmcc
-ms.date: 03/03/2023
+ms.date: 02/13/2026
 ms.topic: article
 ms.service: azure-playfab
-keywords: playfab, c++, windows, xbox, gdk, login
+keywords: playfab, c++, windows, xbox, gdk, login, suspend, resume, quick resume, token refresh
 ms.localizationpriority: medium
 ---
 
 # Handling Token Expiration
 
-The PlayFab Services SDK automatically attempts to handle relogin and token refresh in this SDK. When a PlayFab entity token expires, the SDK detects the failure and attempts to acquire a new entity token using the handle or token you originally provided to the login request. If this relogin succeeds, the SDK retries the original failed call automatically. Additionally, the **PFEntityHandle** returned by the original login call continues to be valid.
+The PlayFab Services SDK includes a background token refresh mechanism that helps keep your player's session active. Understanding how this mechanism works—and when your game needs to take action—is important, especially for Game Development Kit (GDK) titles that support suspend and resume.
 
-## Automatic refresh failure
+## How automatic token refresh works
 
-It's possible for automatic token refresh to fail. This failure could be because the handle or token you originally provided to the login request is no longer valid. To handle this scenario, your game can register for a callback to provide a new handle or token and retry the login. Use **PFEntityRegisterTokenExpiredEventHandler** to register for a callback and **PFAuthenticationReLoginWith\*Async** to provide the new handle or token and reattempt the login.
+The SDK runs a background worker that periodically checks the player's entity token. If the token is **still valid but approaching expiration** (within one hour of expiry), the SDK automatically reauthenticates using the credentials from the original sign-in call. If this refresh succeeds, the token is updated transparently and the **PFEntityHandle** continues to be valid. No action is required from your game.
+
+You can observe these silent token refreshes by registering a [**PFEntityRegisterTokenRefreshedEventHandler**](../../api-references/c/pfentity/functions/pfentityregistertokenrefreshedeventhandler.md) callback (see [Transparent refresh](#transparent-refresh)).
+
+## When your game must handle token expiration
+
+There are scenarios where the SDK **can't** automatically refresh the token:
+
+- **The token has already expired.** The automatic refresh only works when the token is still valid. If the token is fully expired—for example, after a long suspend/resume cycle—the SDK doesn't attempt an automatic relogin. Instead, it notifies your game via the **TokenExpiredHandler**.
+- **The original sign-in credentials are no longer valid.** If the handle or token originally provided to the sign-in request is no longer valid, automatic refresh fails and the **TokenExpiredHandler** is invoked.
+
+> [!IMPORTANT]
+> Registering a [**PFEntityTokenExpiredEventHandler**](../../api-references/c/pfentity/functions/pfentitytokenexpiredeventhandler.md) is recommended for all titles and is **essential** for GDK titles that support suspend and resume. Without this handler, your game has no way to recover from an expired token.
+
+### Registering the TokenExpiredHandler
+
+Use [**PFEntityRegisterTokenExpiredEventHandler**](../../api-references/c/pfentity/functions/pfentityregistertokenexpiredeventhandler.md) to register for a callback and **PFAuthenticationReLoginWith\*Async** to reauthenticate when the token expires.
 
 ```cpp
     PFRegistrationToken registrationTokenExpired{};
@@ -41,9 +57,24 @@ It's possible for automatic token refresh to fail. This failure could be because
     }, &registrationTokenExpired);
 ```
 
+## GDK: Suspend, resume, and Quick Resume
+
+On GDK platforms (Xbox consoles and Windows with the GDK), a game can be suspended for an extended period, such as when the player switches to another game and later returns via Quick Resume. During suspension, the entity token may expire. Because no code runs during suspension, the SDK's periodic background refresh can't keep the token alive.
+
+### What happens on resume
+
+When your game resumes, the SDK **immediately** detects the resumed state and checks the entity token. It doesn't wait for the next periodic refresh cycle. If the token expired during the suspend:
+
+1. The SDK detects the expired token.
+2. The **TokenExpiredHandler** callback is invoked.
+3. Your game must call **PFAuthenticationReLoginWith\*Async** from the handler to acquire a new token.
+
+> [!NOTE]
+> The token check on resume is triggered as soon as network connectivity is restored. If the network takes a moment to reinitialize after resume, the SDK waits for connectivity before checking the token. No token check is lost.
+
 ## Transparent refresh
 
-If you would like your game to know when the SDK automatically refreshes the player's entity token, you can register for a callback.
+If you would like your game to know when the SDK automatically refreshes the player's entity token, you can register for a callback. This handler is invoked when the SDK successfully refreshes a token that was approaching expiration—no action is required from your game.
 
 ```cpp
     PFRegistrationToken registrationTokenRefreshed{};
diff --git a/playfab-docs/sdks/c/server.md b/playfab-docs/sdks/c/server.md
index e64785abe..473ef2790 100644
--- a/playfab-docs/sdks/c/server.md
+++ b/playfab-docs/sdks/c/server.md
@@ -20,7 +20,7 @@ Note: At the moment, server functions are only available on the Win32 version of
 
 ## Authenticating a title entity
 
-After you create a __PFServiceConfigHandle__ in the initial steps, you can then get a title entity handle by calling __PFAuthenticationGetEntityWithSecretKeyAsync__. After the get entity call completes successfully, it will return __S_OK__ along with a __PFEntityHandle__. This process is similar to logging in as a player. The return type of __PFEntityHandle__ is the same, except in this case the entity handle represents a title entity rather than a player entity. We can call this entity a game server.
+After you create a __PFServiceConfigHandle__ in the initial steps, you can then get a title entity handle by calling [__PFAuthenticationGetEntityWithSecretKeyAsync__](../../api-references/c/pfauthentication/functions/pfauthenticationgetentitywithsecretkeyasync.md). After the get entity call completes successfully, it will return __S_OK__ along with a __PFEntityHandle__. This process is similar to logging in as a player. The return type of __PFEntityHandle__ is the same, except in this case the entity handle represents a title entity rather than a player entity. We can call this entity a game server.
 
 ```cpp
     PFAuthenticationGetEntityRequest request{};
diff --git a/playfab-docs/sdks/c/tracing.md b/playfab-docs/sdks/c/tracing.md
index fb3a23cf7..3309dd513 100644
--- a/playfab-docs/sdks/c/tracing.md
+++ b/playfab-docs/sdks/c/tracing.md
@@ -44,6 +44,16 @@ void CALLBACK TraceCallback(
 HCTraceSetClientCallback(TraceCallback);
 ```
 
+## Write traces to a file
+
+To write PlayFab trace output to a log file on disk, call [**PFTraceEnableTraceToFile**](../../api-references/c/pftrace/functions/pftraceenabletracetofile.md) with the directory where the trace file should be created. Call this function after initialization.
+
+```cpp
+PFTraceEnableTraceToFile("C:\\GameLogs\\PlayFabTraces");
+```
+
+This function is independent of the HCTrace functions above. You can use file tracing alongside debugger output and client callbacks.
+
 ## Reference
 
 [PlayFab API reference documentation](../../api-references/c/pftrace/pftrace_members.md)
diff --git a/playfab-docs/sdks/cocos2d-x/quickstart.md b/playfab-docs/sdks/cocos2d-x/quickstart.md
index 75f2acfc3..05d2e4fc6 100644
--- a/playfab-docs/sdks/cocos2d-x/quickstart.md
+++ b/playfab-docs/sdks/cocos2d-x/quickstart.md
@@ -14,13 +14,13 @@ ms.localizationpriority: medium
 
 This quickstart assists you in making your first PlayFab API call in the Cocos2d-x engine.
 
-Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com/en-us/sign-up). 
+Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com). 
 
 ## Cocos2d-x project setup
 
 OS: This guide is written for Windows 10, using Visual Studio 2015. Cocos works on most modern OSs and environments. The installation instructions are similar, but different for each combination.
 
-If you are building for other platforms, the files you need are the same, but you will need to do the project setup yourself. Visual Studio 2013 will have identical steps, but the screenshots provided here will look a bit different from yours.
+If you're building for other platforms, the files you need are the same, but you'll need to do the project setup yourself. Visual Studio 2013 has identical steps, but the screenshots provided here look a bit different from yours.
 
 1. Download and install Cocos2d-x
     - [https://www.cocos2d-x.org/download](https://www.cocos2d-x.org/download)
@@ -38,8 +38,8 @@ If you are building for other platforms, the files you need are the same, but yo
 
     - In the new console window enter this command:
       - `cocos new CocosGettingStarted -l cpp`
-        - Make sure your target sub-directory (**CocosGettingStarted**) does not already exist - This command will fail if the folder already exists.
-        - If you get a message that "'cocos' is not recognized as an internal or external command", you have not configured the cocos installation correctly (Go back to the Cocos windows installation guide).
+        - Make sure your target sub-directory (**CocosGettingStarted**) doesn't already exist - This command will fail if the folder already exists.
+        - If you get a message that "'cocos' isn't recognized as an internal or external command", you haven't configured the cocos installation correctly (Go back to the Cocos windows installation guide).
         - If successful, there will be a new folder **CocosGettingStarted**. This guide will refer to that directory location as `{CocosGettingStarted}`.
 
     - Successful output should appear similar to the example provided below.
@@ -87,9 +87,9 @@ PlayFab uses several Cocos libraries that have to be manually added to the depen
       `$(ProjectDir)..\cocos2d\external\zlib\include;$(ProjectDir)..\cocos2d\external\curl\include\win32;$(EngineRoot)cocos\audio\include;$(EngineRoot)external;$(EngineRoot)external\chipmunk\include\chipmunk;$(EngineRoot)extensions;..\Classes;..;%(AdditionalIncludeDirectories);$(_COCOS_HEADER_WIN32_BEGIN);$(_COCOS_HEADER_WIN32_END);..\cocos2d`
 
 > [!NOTE]
-> We are adding curl and zlib, which are libraries that come with Cocos, but are not enabled by default.
+> We're adding curl and zlib, which are libraries that come with Cocos, but aren't enabled by default.
 
-Your CocosGettingStarted project should now compile (and even run), but we are not yet making any PlayFab API calls.
+Your CocosGettingStarted project should now compile (and even run), but we aren't yet making any PlayFab API calls.
 
 Installation complete!
 
@@ -211,13 +211,13 @@ These files take the existing HelloWorldScene that is part of the new-Cocos-proj
 ## Finish and execute
 
 1. Build and Execute your Cocos Project: Dropdowns -> Debug -> Start Debugging.
-2. This may prompt you to build. Select **Yes**.
+2. This will prompt you to build. Select **Yes**.
 
 3. You should see a screen that says:
 
     **Congratulations, you made your first successful API call!**
 
-4. Now, you can start making other api calls, and building your game.  
+4. Now, you can start making other API calls, and building your game.  
 For a list of all available client API calls, see our [PlayFab API References](../../api-references/index.md) documentation.
   
 Happy coding!
@@ -228,8 +228,8 @@ This optional last section describes each part of source code above, in detail.
 
 - `HelloWorldScene.h`
   - This is only trivially modified from the default `HelloWorldScene.h` generated by Cocos.
-  - Specifically, it defines some Cocos GUI we are using, and the prototype for `OnLoginSuccess` and `OnLoginFail`.
-  - Everything else is just standard Cocos Engine functions.
+  - Specifically, it defines some Cocos GUI we're using, and the prototype for `OnLoginSuccess` and `OnLoginFail`.
+  - Everything else is standard Cocos Engine functions.
 
 - `HelloWorldScene.cpp`
   - `createScene()` is a standard Cocos Engine function.
@@ -241,7 +241,7 @@ This optional last section describes each part of source code above, in detail.
     - `PlayFab::ClientModels::LoginWithCustomIDRequest request;`
       - Most PlayFab API methods require input parameters, and those input parameters are packed into a request object.
       - Every API method requires a unique request object, with a mix of optional and mandatory parameters.
-        - For `LoginWithCustomIDRequest`, there is a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call.
+        - For `LoginWithCustomIDRequest`, there's a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call.
       - For login, most developers will want to use a more appropriate login method.
         - See the PlayFab Login documentation for a list of all login methods, and input parameters. Common choices are:
           - `LoginWithAndroidDeviceID`
@@ -252,7 +252,7 @@ This optional last section describes each part of source code above, in detail.
       - This begins the async request to `LoginWithCustomID`, and will invoke the `OnLoginSuccess` or `OnLoginFail` function when complete.
 
   - `update(float delta)`
-    - Simply setting the `statusMsg` variable does not update the on-screen text.
+    - Simply setting the `statusMsg` variable doesn't update the on-screen text.
     - This function sets the GUI text to match the contents of `statusMsg` every tick (not very efficient).
 
   - `OnLoginSuccess(result, customData)`
@@ -263,14 +263,14 @@ This optional last section describes each part of source code above, in detail.
     - If the error-function is called, your API call has failed.
     - API calls can fail for many reasons, and you should always attempt to handle failure.
     - Why API calls fail (In order of likelihood)
-      - `PlayFabSettings.TitleId` is not set. If you forget to set titleId to your title, then nothing will work.
+      - `PlayFabSettings.TitleId` isn't set. If you forget to set titleId to your title, then nothing will work.
         - In Cocos, the curl library will probably just crash your game if you fail to set titleId correctly.
-      - Request parameters. If you have not provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage`, `error.errorDetails`, or `error.GenerateErrorReport()` for more info.
+      - Request parameters. If you haven't provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage`, `error.errorDetails`, or `error.GenerateErrorReport()` for more info.
       - Device connectivity issue. Cell phones lose/regain connectivity constantly, and so any API call at any time can fail randomly, and then work immediately after. Going into a tunnel can disconnect you completely.
       - PlayFab server issue. As with all software, there can be issues. See our release notes for updates.
-      - The internet is not 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
-    - If you are having difficulty debugging an issue, and the information within the error callback is not sufficient, please visit us on our forums.
+      - The internet isn't 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
+    - If you're having difficulty debugging an issue, and the information within the error callback isn't sufficient, visit us on our forums.
 
-  - customData is a void-pointer which can be used in any way to establish context.
-    - In C++, it is harder to maintain the context of an API call, so we added the `customData` parameter, which can relay any object to the callback, which can be used however you like to establish context.
+  - customData is a void-pointer, which can be used in any way to establish context.
+    - In C++, it's harder to maintain the context of an API call, so we added the `customData` parameter, which can relay any object to the callback, which can be used however you like to establish context.
     - Thus, if you make API calls to retrieve inventory, you can pass a player, or inventory pointer as `customData`, and update the inventory on that object, in the callback.
diff --git a/playfab-docs/sdks/java/quickstart.md b/playfab-docs/sdks/java/quickstart.md
index b591416b5..96a305e62 100644
--- a/playfab-docs/sdks/java/quickstart.md
+++ b/playfab-docs/sdks/java/quickstart.md
@@ -14,7 +14,7 @@ ms.localizationpriority: medium
 
 This quickstart lets you get up and running with the PlayFab JavaSDK and simple Java program.
 
-Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com/en-us/sign-up). 
+Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com). 
 
 The goals for this tutorial are:  
 
@@ -56,7 +56,7 @@ If asked for the **Module**, select the first one in the list. Ensure that all t
 
 ## Project Setup with any IDE
 
-The main requirement is to have JAR files added to the classpath. Please consult the guide for your IDE on how to add JAR files to classpath.
+The main requirement is to have JAR files added to the classpath. Consult the guide for your IDE on how to add JAR files to classpath.
 
 ## Set up your first API call
 
@@ -163,7 +163,7 @@ This optional last section describes every line in `GettingStarted.java` in deta
   - `PlayFabClientModels.LoginWithCustomIDRequest request = new PlayFabClientModels.LoginWithCustomIDRequest();`
     - Most PlayFab API methods require input parameters, and those input parameters are packed into a request object.
     - Every API method requires a unique request object, with a mix of optional and mandatory parameters.
-      - For `LoginWithCustomIDRequest`, there is a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call.
+      - For `LoginWithCustomIDRequest`, there's a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call.
 
     - For login, most developers will want to use a more appropriate login method.
       - See the PlayFab Login documentation for a list of all login methods, and input parameters. Common choices are:
@@ -189,10 +189,10 @@ This optional last section describes every line in `GettingStarted.java` in deta
   - If (`result.Error != null`), the API call has failed.
     - API calls can fail for many reasons, and you should always attempt to handle failure.
     - Why API calls fail (In order of likelihood)
-      - `PlayFabSettings.TitleId` is not set. If you forget to set `TitleId` to your title, then nothing will work.
-      - Request parameters. If you have not provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage`, `error.errorDetails`, or `error.GenerateErrorReport()` for more info.
+      - `PlayFabSettings.TitleId` isn't set. If you forget to set `TitleId` to your title, then nothing will work.
+      - Request parameters. If you haven't provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage`, `error.errorDetails`, or `error.GenerateErrorReport()` for more info.
       - Device connectivity issue. Cell phones lose/regain connectivity constantly, and so any API call at any time can fail randomly, and then work immediately after. Going into a tunnel can disconnect you completely.
       - PlayFab server issue. As with all software, there can be issues. See our [release notes](../../release-notes/index.md) for updates.
-      - The internet is not 100% reliable. Sometimes the message is corrupted, or fails to reach the PlayFab server.
+      - The internet isn't 100% reliable. Sometimes the message is corrupted, or fails to reach the PlayFab server.
 
-  - If you are having difficulty debugging an issue, and the information within the error information is not sufficient, please visit us on our [forums](https://community.playfab.com/index.html).
+  - If you're having difficulty debugging an issue, and the information within the error information isn't sufficient, visit us on our [forums](https://community.playfab.com/index.html).
diff --git a/playfab-docs/sdks/javascript/quickstart.md b/playfab-docs/sdks/javascript/quickstart.md
index cfd2385f7..52d91f1ec 100644
--- a/playfab-docs/sdks/javascript/quickstart.md
+++ b/playfab-docs/sdks/javascript/quickstart.md
@@ -16,13 +16,13 @@ Get started with the PlayFab client library for JavaScript to authenticate a pla
 
 ## Prerequisites
 
-* A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up). For information about creating a Title and finding TitleId, see [Game Manager QuickStart](../../live-service-management/gamemanager/quickstart.md).
+* A [PlayFab developer account](https://developer.playfab.com). For information about creating a Title and finding TitleId, see [Game Manager QuickStart](../../live-service-management/gamemanager/quickstart.md).
 
 The QuickStart guide works in any operating system capable of running a web browser.
 
 ## JavaScript project setup
 
-Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com/en-us/sign-up). For information about creating a Title and finding TitleId, see [Game Manager QuickStart](../../live-service-management/gamemanager/quickstart.md).
+Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com). For information about creating a Title and finding TitleId, see [Game Manager QuickStart](../../live-service-management/gamemanager/quickstart.md).
 
 OS: This guide works in any OS capable of running a web browser.
 
@@ -97,11 +97,11 @@ To look up the correct format for the loginRequest object in this example, see t
 ## Run the code
 
 1. Open `PlayFabGettingStarted.html` in your favorite browser.
-2. Click the **Call LoginWithCustomID** button.
+2. Select the **Call LoginWithCustomID** button.
 3. You should see the following text in the Result section:
 "Congratulations, you made your first successful API call!"
 
-At this point, you can start making other api calls, and building your game.
+At this point, you can start making other API calls, and building your game.
 
 For a list of all available client API calls, see [PlayFab API References](../../api-references/index.md) documentation.
 
@@ -117,7 +117,7 @@ The HTML file has a few important lines:
 <script type="text/javascript" src="https://download.playfab.com/PlayFabClientApi.js"></script>
 ```
 
-This line loads the Client-SDK directly from the PlayFab CDN. Our CDN always hosts the latest version of PlayFabSDK. It may be safer for you to download the files, and use a fixed version: [PlayFab JavaScript SDK](https://aka.ms/playfabjavascriptsdkdownload)
+This line loads the Client-SDK directly from the PlayFab CDN. Our CDN always hosts the latest version of PlayFabSDK. It might be safer for you to download the files, and use a fixed version: [PlayFab JavaScript SDK](https://aka.ms/playfabjavascriptsdkdownload)
 
 ```html
 <script type="text/javascript" src="PlayFabGettingStarted.js"></script>
@@ -136,9 +136,9 @@ The functions in `PlayFabClientSDK` are named after the corresponding HTTP reque
   - `var loginRequest = { TitleId: PlayFab.settings.titleId, CustomId: "GettingStartedGuide", CreateAccount: true };`
     - Most PlayFab API methods require input parameters, and those input parameters are packed into a request object
     - Every API method requires a unique request object, with a mix of optional and mandatory parameters
-      - For `LoginWithCustomID`, there is a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call. `TitleId` is another mandatory parameter in JavaScript, and it must match `PlayFab.settings.titleId`.
+      - For `LoginWithCustomID`, there's a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call. `TitleId` is another mandatory parameter in JavaScript, and it must match `PlayFab.settings.titleId`.
       - For information about where to find `TitleId`, see [Game Manager QuickStart](../../live-service-management/gamemanager/quickstart.md).
-  - In this case, `TitleId`,  `customId`, and `CreateAccount` are from the Request Body of `LoginWithCustomID`. The Request Body fields are included as keys and values in the request object. The Session Ticket in the Request Header will be saved from login, so the SessionTicket is not included in the request object.
+  - In this case, `TitleId`,  `customId`, and `CreateAccount` are from the Request Body of `LoginWithCustomID`. The Request Body fields are included as keys and values in the request object. The Session Ticket in the Request Header will be saved from login, so the SessionTicket isn't included in the request object.
     
   - `PlayFabClientSDK.LoginWithCustomID(loginRequest, LoginCallback);`
     - This begins the async request to `LoginWithCustomID`, which will call `LoginCallback` when the API call is complete.
@@ -152,7 +152,7 @@ The functions in `PlayFabClientSDK` are named after the corresponding HTTP reque
   - `LoginCallback` contains two parameters: result, error
     - When successful, error will be null, and the result object will contain the requested information, according to the API called.
     - This result contains some basic information about the player, but for most users, login is simply a mandatory step before calling other APIs.
-  - If error is not `null`, your API call has failed.
+  - If error isn't `null`, your API call has failed.
 
 
 
@@ -162,12 +162,12 @@ The functions in `PlayFabClientSDK` are named after the corresponding HTTP reque
 - The error object includes the error name, error code, and error message. Together, this information should be sufficient to diagnose your error.
 - Global API Method Error Codes can be found in PlayFab's [Global API Method Error Codes](../../api-references/global-api-method-error-codes.md).
 - Why API calls fail (In order of likelihood)
-  - PlayFabSettings.TitleId is not set. If TitleId is not set, then nothing will work.
-  - Request parameters. If you have not provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage, error.errorDetails`, or `error.GenerateErrorReport()` for more info.
+  - PlayFabSettings.TitleId isn't set. If TitleId isn't set, then nothing will work.
+  - Request parameters. If you haven't provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage, error.errorDetails`, or `error.GenerateErrorReport()` for more info.
   - Device connectivity issue. Cell-phones lose/regain connectivity constantly, and so any API call at any time can fail randomly, and then work immediately after. Going into a tunnel can disconnect you completely.
 - PlayFab server issue. As with all software, there can be issues. See our [release notes](../../release-notes/index.md) for updates.
-    - The internet is not 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
-- If you are having difficulty debugging an issue, and the information within the error information is not sufficient, please visit us on our [forums](https://community.playfab.com/index.html).
+    - The internet isn't 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
+- If you're having difficulty debugging an issue, and the information within the error information isn't sufficient, visit us on our [forums](https://community.playfab.com/index.html).
 
 
 
diff --git a/playfab-docs/sdks/lua/quickstart-corona.md b/playfab-docs/sdks/lua/quickstart-corona.md
index c513a7ea8..5cbc71346 100644
--- a/playfab-docs/sdks/lua/quickstart-corona.md
+++ b/playfab-docs/sdks/lua/quickstart-corona.md
@@ -14,11 +14,11 @@ ms.localizationpriority: medium
 
 This quickstart assists you in making your first PlayFab API call in the Corona engine.
 
-Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com/en-us/sign-up). 
+Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com). 
 
 ## Corona Project Setup
 
-OS: This quickstart is written for Windows 10.  However, it should also work well with a Mac.
+OS: This quickstart is written for Windows. However, it should also work well with a Mac.
 
 1. Download and install Corona:  [https://coronalabs.com/](https://coronalabs.com/).
 
@@ -100,7 +100,7 @@ This optional last section describes each part of our example above, line-by-lin
   - `local loginRequest = { CustomId = "GettingStartedGuide", CreateAccount = true }`
     - Most PlayFab API methods require input parameters, and those input parameters are packed into a request object
     - Every API method requires a unique request object, with a mix of optional and mandatory parameters
-      - For `LoginWithCustomIDRequest`, there is a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call.
+      - For `LoginWithCustomIDRequest`, there's a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call.
   - `PlayFabClientApi.LoginWithCustomID(loginRequest, {OnLoginSuccess-function}, {OnLoginError-function})`
     - This begins the async request to `LoginWithCustomID`, which will call the first (`OnLoginSuccess`) callback if successful, or the second (`OnLoginError`) function for failures.
   - For login, most developers will want to use a more appropriate login method.
@@ -114,9 +114,9 @@ This optional last section describes each part of our example above, line-by-lin
     - `OnLoginError` is any function which accepts a single parameter (error).
       - API calls can fail for many reasons, and you should always attempt to handle failure.
       - Why API calls fail (In order of likelihood):
-        - `PlayFabSettings.TitleId` is not set. If you forget to set `titleId` to your title, then nothing will work.
-        - Request parameters. If you have not provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage`, `error.errorDetails`, or `error.GenerateErrorReport()` for more info.
+        - `PlayFabSettings.TitleId` isn't set. If you forget to set `titleId` to your title, then nothing will work.
+        - Request parameters. If you haven't provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage`, `error.errorDetails`, or `error.GenerateErrorReport()` for more info.
         - Device connectivity issue. Cell-phones lose/regain connectivity constantly, and so any API call at any time can fail randomly, and then work immediately after. Going into a tunnel can disconnect you completely.
         - PlayFab server issue. As with all software, there can be issues. See our [release notes](../../release-notes/index.md) for updates.
-        - The internet is not 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
-      - If you are having difficulty debugging an issue, and the information within the error information is not sufficient, please visit us on our [forums](https://community.playfab.com/index.html).
+        - The internet isn't 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
+      - If you're having difficulty debugging an issue, and the information within the error information isn't sufficient, visit us on our [forums](https://community.playfab.com/index.html).
diff --git a/playfab-docs/sdks/lua/quickstart-defold.md b/playfab-docs/sdks/lua/quickstart-defold.md
index 131e2e151..91edd2fb2 100644
--- a/playfab-docs/sdks/lua/quickstart-defold.md
+++ b/playfab-docs/sdks/lua/quickstart-defold.md
@@ -14,7 +14,7 @@ ms.localizationpriority: medium
 
 This quickstart assists you in making your first PlayFab API call using Defold.
 
-Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com/en-us/sign-up). 
+Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com). 
 
 ## Defold project setup
 
@@ -22,7 +22,7 @@ OS: This guide is written for Windows 10.  It should also work well with a Mac.
 
 1. Create an account and download defold, or log in at [https://www.defold.com/](https://www.defold.com/) (Uses Google O-Auth): [https://d.defold.com/stable/](https://d.defold.com/stable/).
 
-2. If you have not completed the Defold "Getting Started Tutorial", you should do that now.
+2. If you haven't completed the Defold "Getting Started Tutorial", you should do that now.
 
 3. Create a new project on the Defold Dashboard, as shown below.
 
@@ -46,19 +46,19 @@ OS: This guide is written for Windows 10.  It should also work well with a Mac.
 
     - **main/PfGettingStarted.gui**
 
-    - Right-click the  "main" folder -> **new** -> **Gui File** -> **PfGettingStarted.gui**.
+    - Select the  "main" folder -> **new** -> **Gui File** -> **PfGettingStarted.gui**.
 
     - **main/PfGettingStarted.gui_script**
 
-    - Right-click "main" folder -> **new** -> **Gui Script File** -> **PfGettingStarted.gui_script**.
+    - Select "main" folder -> **new** -> **Gui Script File** -> **PfGettingStarted.gui_script**.
 
 8. Hook up our new GUI in the main.collection.
 
-   - Double-click main.collection to open it.  
+   - Select main.collection to open it.  
 
    - In the Outline panel:
-      - Right-click **Add Game Object** (Optionally rename to **PfGui**).
-        - Right-Click the new object, **Add Component From File...**
+      - Select **Add Game Object** (Optionally rename to **PfGui**).
+        - Select the new object, **Add Component From File...**
           - PfGettingStarted.gui (Created above).
 
    - The Outline panel viewing main.collection should look like the example shown below.
@@ -205,7 +205,7 @@ max_nodes: 512
 
 ## Finish and execute
 
-First, make sure everything is saved and select another tab.  Then look for " * " markers - sometimes Defold doesn't refresh.
+First, make sure everything is saved and select another tab. Then look for " * " markers - sometimes Defold doesn't refresh.
 
 Then, build your game (Ctrl+b or dropdowns: **Project** -> **Build and Launch**). You should see the following text on your screen:
 
@@ -219,14 +219,14 @@ Happy coding!
 
 - `PfGettingStarted.gui`
   - Our instructions for `PfGettingStarted.gui` are for expediency, not instruction. This file is a GUI definition, which adds a text box to the screen, binds it to our other script: `PfGettingStarted.gui_script`. You would NOT typically edit these files in text-form.
-  - For proper instructions on how to build Defold GUI widgets, please read this guide:
+  - For proper instructions on how to build Defold GUI widgets, read this guide:
   - [GUI scenes in Defold](https://www.defold.com/manuals/gui/)
 
 - `PfGettingStarted.gui_script`
   - Require statements and setup.
     - `PlayFabClientApi` allows you to make Client API calls - This is why you're here.
     - IPlayFabHttps and PlayFabHttps_Defold:
-      - The PlayFab Defold plugins are built on the PlayFab LuaSdk. The Lua language does not have a proper HTTPS module. Each game-engine that uses Lua implements their own. These two variables tell PlayFabSdk how to access HTTPS. You only need to do this once in your project, in the first scene. Otherwise it's just required boilerplate
+      - The PlayFab Defold plugins are built on the PlayFab LuaSdk. The Lua language doesn't have a proper HTTPS module. Each game-engine that uses Lua implements their own. These two variables tell PlayFabSdk how to access HTTPS. You only need to do this once in your project, in the first scene. Otherwise it's required boilerplate
 
   - `PlayFabClientApi.settings.titleId = "144"`
     - Every project using PlayFab should create a unique title in the PlayFab website, which we call Game Manager. Find your `titleId` in Game Manager, and replace `144` with your `titleId`.
@@ -237,7 +237,7 @@ Happy coding!
   - `local loginRequest = { TitleId = PlayFabClientApi.settings.titleId, CustomId = "GettingStartedGuide", CreateAccount = true }`
     - Most PlayFab API methods require input parameters, and those input parameters are packed into a request object
     - Every API method requires a unique request object, with a mix of optional and mandatory parameters
-      - For `LoginWithCustomIDRequest`, there is a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call.
+      - For `LoginWithCustomIDRequest`, there's a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call.
     - For login, most developers will want to use a more appropriate login method
       - See the [PlayFab Login documentation](xref:titleid.playfabapi.com.client.authentication) for a list of all login methods, and input parameters. Common choices are:
         - [LoginWithAndroidDeviceID](xref:titleid.playfabapi.com.client.authentication.loginwithandroiddeviceid)
@@ -254,14 +254,14 @@ Happy coding!
   - `function OnLoginFailed(error)`
     - API calls can fail for many reasons, and you should always attempt to handle failure.
     - Why API calls fail (In order of likelihood)
-      - PlayFabSettings.TitleId is not set. If you forget to set titleId to your title, then nothing will work.
+      - PlayFabSettings.TitleId isn't set. If you forget to set titleId to your title, then nothing will work.
 
-      - Request parameters. If you have not provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage`, `error.errorDetails`, or `error.GenerateErrorReport()` for more info.
+      - Request parameters. If you haven't provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage`, `error.errorDetails`, or `error.GenerateErrorReport()` for more info.
       - Device connectivity issue. Cell-phones lose/regain connectivity constantly, and so any API call at any time can fail randomly, and then work immediately after. Going into a tunnel can disconnect you completely.
       - PlayFab server issue. As with all software, there can be issues. See our [release notes](../../release-notes/index.md) for updates.
-      - The internet is not 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
+      - The internet isn't 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
 
-    - If you are having difficulty debugging an issue, and the information within the error information is not sufficient, please visit us on our [forums](https://community.playfab.com/index.html)
+    - If you're having difficulty debugging an issue, and the information within the error information isn't sufficient, visit us on our [forums](https://community.playfab.com/index.html)
 
   - `local pfTestOutput = gui.get_node("pfOutput")`
     - This is another Defold GUI function. It fetches the `pfOutput` GUI object defined in our PfGettingStarted.gui file, and assigns it text to display to the user.
diff --git a/playfab-docs/sdks/nodejs/quickstart.md b/playfab-docs/sdks/nodejs/quickstart.md
index 3b4d9fe83..901e08a4f 100644
--- a/playfab-docs/sdks/nodejs/quickstart.md
+++ b/playfab-docs/sdks/nodejs/quickstart.md
@@ -18,7 +18,7 @@ Get started with the PlayFab client library for NodeJS to make your first PlayFa
 
 ## Prerequisites
 
-- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up). For information about creating a Title and finding TitleId, see [Game Manager QuickStart](../../live-service-management/gamemanager/quickstart.md).
+- A [PlayFab developer account](https://developer.playfab.com). For information about creating a Title and finding TitleId, see [Game Manager QuickStart](../../live-service-management/gamemanager/quickstart.md).
 - [Node.js](https://nodejs.org/en/download/)
 - Node must be in your PATH environment variable. If you used the installer, it's probably set for you to the default location: C:/Program Files (x86)/nodejs/
 
@@ -26,7 +26,7 @@ Get started with the PlayFab client library for NodeJS to make your first PlayFa
 
 ## Setting up
 
-The following commands work on Windows, MacOS, and Linux.
+The following commands work on Windows, macOS, and Linux.
 
 1. Create a new folder for your project {NodeProjLocation}:
 
@@ -38,7 +38,7 @@ The following commands work on Windows, MacOS, and Linux.
 
    `npm install playfab-sdk --save`
 
-   (Keep this window open (we'll use it again later.)
+   (Keep this window open (you'll use it again later.)
 
 PlayFab installation complete!
 
@@ -128,7 +128,7 @@ For the Node SDK, the functions in `PlayFabClientSDK` are named after the HTTP r
   - `var loginRequest = { TitleId: PlayFab.settings.titleId, CustomId: "GettingStartedGuide", CreateAccount: true };`
     - Most PlayFab API methods require input parameters, and those input parameters are packed into a request object.
     - Every API method requires a unique request object, with a mix of optional and mandatory parameters.
-      - For `LoginWithCustomIDRequest`, there is a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call. `TitleId` is another mandatory parameter in JavaScript, and it must match `PlayFab.settings.titleId`.
+      - For `LoginWithCustomIDRequest`, there's a mandatory parameter of `CustomId`, which uniquely identifies a player and `CreateAccount`, which allows the creation of a new account with this call. `TitleId` is another mandatory parameter in JavaScript, and it must match `PlayFab.settings.titleId`.
       - For information about where to find `TitleId`, see [Game Manager QuickStart](../../live-service-management/gamemanager/quickstart.md).
 - In this case, `TitleId`,  `customId`, and `CreateAccount` are from the Request Body of `LoginWithCustomID`.
   - `PlayFabClientSDK.LoginWithCustomID(loginRequest, LoginCallback);`
@@ -142,7 +142,7 @@ For the Node SDK, the functions in `PlayFabClientSDK` are named after the HTTP r
 - `LoginCallback` contains two parameters: `error` and `result`.
   - When successful, `error` will be `null`, and the `result` object will contain the requested information, according to the API called.
     - This `result` contains some basic information about the player, but for most users, login is simply a mandatory step before calling other APIs.
-- If error is not `null`, your API has failed.
+- If error isn't `null`, your API has failed.
 
 
 
@@ -151,13 +151,13 @@ For the Node SDK, the functions in `PlayFabClientSDK` are named after the HTTP r
 - API calls can fail for many reasons, and you should always attempt to handle failure.
 - The error object includes the error name, error code, and error message. Together, this information should be sufficient to diagnose your error.
 - Why API calls fail (In order of likelihood):
-  - `PlayFabSettings.TitleId` is not set. If you forget to set `TitleId` to your title, then nothing will work.
-  - Request parameters. If you have not provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage`, `error.errorDetails`, or `error.GenerateErrorReport()` for more info.
+  - `PlayFabSettings.TitleId` isn't set. If you forget to set `TitleId` to your title, then nothing will work.
+  - Request parameters. If you haven't provided the correct or required information for a particular API call, then it will fail. See `error.errorMessage`, `error.errorDetails`, or `error.GenerateErrorReport()` for more info.
   - Device connectivity issue. Cell-phones lose/regain connectivity constantly, and so any API call at any time can fail randomly, and then work immediately after. Going into a tunnel can disconnect you completely.
   - PlayFab server issue. As with all software, there can be issues. See our [release notes](../../release-notes/index.md) for updates.
-- The internet is not 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
+- The internet isn't 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
   - Global API Method Error Codes can be found in [Global API Method Error Codes](../../api-references/global-api-method-error-codes.md).
-  - If you are having difficulty debugging an issue, and the information within the error information is not sufficient, please visit us on our [forums](https://community.playfab.com/index.html).
+  - If you're having difficulty debugging an issue, and the information within the error information isn't sufficient, visit us on our [forums](https://community.playfab.com/index.html).
 
 
 
diff --git a/playfab-docs/sdks/platforms/playstation.md b/playfab-docs/sdks/platforms/playstation.md
index 8d1a7a948..769a8fa3a 100644
--- a/playfab-docs/sdks/platforms/playstation.md
+++ b/playfab-docs/sdks/platforms/playstation.md
@@ -1,7 +1,7 @@
 ---
-title: PlayFab Services for Sony PlayStation
+title: PlayFab Services for PlayStation
 author: amccalib
-description: PlayFab Services SDK options for Sony PlayStation
+description: PlayFab Services SDK options for PlayStation
 ms.author: andmcc
 ms.date: 06/23/2023
 ms.topic: article
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 
 # PlayFab Services SDKs for PlayStation&#174;4 and PlayStation&#174;5 
 
-The following SDKs are available for game client development on PS4™ and PS5®. The right SDK depends mostly on your choice of game engine.
+The following SDKs are available for game client development on PS4&trade; and PS5&trade;. The right SDK depends mostly on your choice of game engine.
 
 | PlayFab SDK    | Description | Learn More |
 |----------------|-------------|------------|
@@ -21,14 +21,10 @@ The following SDKs are available for game client development on PS4™ and PS5®
 | Unity          | Both an editor extension and stand-alone SDK for Unity3d. | [Unity SDK Overview](../unity3d/index.md) |
 | Legacy C++     | Our older cross-platform C++ SDK supports a simple REST-like interface with PlayFab across multiple platforms. | [Request Access](../request-access-for-sdks-samples.md) |
 
-## Getting Access to SDKs for PS4™ and PS5®
+## Getting Access to SDKs for PS4 and PS5
 
 Our PlayFab Services SDKs for Unreal and Unity are platform-agnostic. As such, they require no special access or permissions from PlayFab to utilize on any platform.
 
-To utilize our C/C++ or Legacy C++ SDKs on PS4™ and PS5®, you must confirm your developer status via DevNet. Once you have approval, we can grant access to the SDK. Learn more about this process here: [Request Access](../request-access-for-sdks-samples.md).
+To utilize our C/C++ or Legacy C++ SDKs on PS4 and PS5, you must confirm your developer status via DevNet. Once you have approval, we can grant access to the SDK. Learn more about this process here: [Request Access](../request-access-for-sdks-samples.md).
 
-"PlayStation" is a registered trademark or trademark of Sony Interactive Entertainment Inc.
-
-"PS4" is a registered trademark or trademark of Sony Interactive Entertainment Inc.
-
-"PS5" is a registered trademark or trademark of Sony Interactive Entertainment Inc.
+"PlayStation", "PS5", and "PS4" are registered trademarks or trademarks of Sony Interactive Entertainment Inc.
diff --git a/playfab-docs/sdks/playfab-cpp/quickstart-linux.md b/playfab-docs/sdks/playfab-cpp/quickstart-linux.md
index dfb006332..25bcdb455 100644
--- a/playfab-docs/sdks/playfab-cpp/quickstart-linux.md
+++ b/playfab-docs/sdks/playfab-cpp/quickstart-linux.md
@@ -22,7 +22,7 @@ This quickstart was written using Ubuntu 18.04 LTS.
 
 ## Requirements
 
-- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).  
+- A [PlayFab developer account](https://developer.playfab.com).  
 
 ## Linux C++ Project Setup
 
diff --git a/playfab-docs/sdks/playfab-cpp/quickstart-windows.md b/playfab-docs/sdks/playfab-cpp/quickstart-windows.md
index 2fd980d7f..24e701b19 100644
--- a/playfab-docs/sdks/playfab-cpp/quickstart-windows.md
+++ b/playfab-docs/sdks/playfab-cpp/quickstart-windows.md
@@ -23,7 +23,7 @@ This quickstart helps you make your first PlayFab API call in the using the Clie
 
 ## Requirements
 
-- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).  
+- A [PlayFab developer account](https://developer.playfab.com).  
 - An installation of [Visual Studio](https://visualstudio.microsoft.com/).
 
 ## Windows C++ project setup
diff --git a/playfab-docs/sdks/playfab-sdk-intro.md b/playfab-docs/sdks/playfab-sdk-intro.md
index ececa5ede..7a4fb679f 100644
--- a/playfab-docs/sdks/playfab-sdk-intro.md
+++ b/playfab-docs/sdks/playfab-sdk-intro.md
@@ -1,7 +1,7 @@
 ---
-title: Azure PlayFab SDKs
+title: PlayFab SDKs
 author: joannaleecy
-description: Azure PlayFab SDKs
+description: PlayFab SDKs
 ms.author: jenelleb
 ms.date: 03/04/2024
 ms.topic: article
@@ -27,7 +27,7 @@ For broad API categories in these SDKs, see [API REST operation groups](/rest/ap
 
 | Language                          | Platform/environments                     |
 |-----------------------------------|-------------------------------------------|
-| C/C++                             | [Windows (Win32), iOS, MacOS, Android, Linux](c/index.md), [GDK (Xbox and Windows)](c/index.md), [Switch](https://dev.azure.com/PlayFabPrivate/Switch/_git/PlayFabCSdk.Switch), [PlayStation 4](https://dev.azure.com/PlayFabPrivate/PS4/_git/PlayFabCSdk.PS4), [PlayStation 5](https://dev.azure.com/PlayFabPrivate/PS5/_git/PlayFabCSdk.PS5) |
+| C/C++                             | [Windows (Win32), iOS, macOS, Android, Linux](c/index.md), [GDK (Xbox and Windows)](c/index.md), [Switch](https://dev.azure.com/PlayFabPrivate/Switch/_git/PlayFabCSdk.Switch), [PlayStation 4](https://dev.azure.com/PlayFabPrivate/PS4/_git/PlayFabCSdk.PS4), [PlayStation 5](https://dev.azure.com/PlayFabPrivate/PS5/_git/PlayFabCSdk.PS5) |
 | Legacy C++                        | [Windows (Win32), iOS, Android, Linux](playfab-cpp/index.md), [Switch](https://dev.azure.com/PlayFabPrivate/Switch/_git/XPlatCppSdk-Private-Switch), [PlayStation 4](https://dev.azure.com/PlayFabPrivate/PS4/_git/XPlatCppSdk-Private-Ps4), [PlayStation 5](https://dev.azure.com/PlayFabPrivate/PS5/_git/XPlatCppSdk-Private-PS5) |
 | C#                                | [C#/.NET environments](c-sharp/index.md) besides Unity |
 | Java                              | [Android apps](java/index.md) |
diff --git a/playfab-docs/sdks/python/quickstart.md b/playfab-docs/sdks/python/quickstart.md
index b4ae6a03a..c2f28358d 100644
--- a/playfab-docs/sdks/python/quickstart.md
+++ b/playfab-docs/sdks/python/quickstart.md
@@ -22,7 +22,7 @@ A native Python project can be used a few ways:
 
 ## Prerequisites
 
-- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A [PlayFab developer account](https://developer.playfab.com).
 - [Python 3](https://www.python.org/downloads/) installed on your system.
   - You must also have the requests module installed.
 
@@ -31,7 +31,7 @@ A native Python project can be used a few ways:
 >
 
   
-If you are having difficulty debugging an issue, and the information provided the error information is not sufficient, please visit us on our [PlayFab forums](https://community.playfab.com/index.html).
+If you're having difficulty debugging an issue, and the information provided the error information isn't sufficient, visit us on our [PlayFab forums](https://community.playfab.com/index.html).
 
 ## Python project setup
 
@@ -41,7 +41,7 @@ If you are having difficulty debugging an issue, and the information provided th
 pip install playfab
 ```
 
-If `pip` is not in your path, use the following command instead.
+If `pip` isn't in your path, use the following command instead.
 
 ```cmd
 python -m pip install playfab
@@ -118,11 +118,11 @@ This optional last section describes each part of playfab_test.py in detail.
     - If the API call wasn't successful, failure will contain some error information and success will be `None`.
     - API calls can fail for many reasons, and you should always attempt to handle the failure.
     - Why API calls fail (In order of likelihood)
-      - `PlayFabSettings.TitleId` is not set. If you forget to set `titleId` to your title, then nothing will work.
-      - Request parameters. If you have not provided the correct or required information for a particular API call, then it will fail.
+      - `PlayFabSettings.TitleId` isn't set. If you forget to set `titleId` to your title, then nothing will work.
+      - Request parameters. If you haven't provided the correct or required information for a particular API call, then it will fail.
       - Device connectivity issue. Cell-phones lose/regain connectivity constantly, and so any API call at any time can fail randomly, and then work immediately after. Going into a tunnel can disconnect you completely.
       - PlayFab server issue. As with all software, there can be issues. See our [release notes](../../release-notes/index.md) for updates.
-      - The internet is not 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
+      - The internet isn't 100% reliable. Sometimes the message is corrupted or fails to reach the PlayFab server.
 
 - `PlayFabClientAPI.LoginWithCustomID`
   - Triggers the API call synchronously. When complete, the callback will be invoked.
diff --git a/playfab-docs/sdks/sdk-products.md b/playfab-docs/sdks/sdk-products.md
new file mode 100644
index 000000000..c9aa0d3e8
--- /dev/null
+++ b/playfab-docs/sdks/sdk-products.md
@@ -0,0 +1,76 @@
+---
+title: PlayFab SDK Products
+author: Jeffrey-Shi
+description: Overview of PlayFab SDK product lines - v1 Standalone SDKs and v2 Unified SDK
+ms.author: jeffshi
+ms.date: 02/10/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, playfab sdk, unified sdk, standalone sdk, sdk products
+ms.localizationpriority: medium
+---
+
+# PlayFab SDK Products
+
+The **PlayFab Unified SDK (v2)** is the next generation of PlayFab SDKs, consolidating all PlayFab client libraries into a single, cohesive product. It provides a modern, streamlined development experience with unified authentication, automatic token management, and consistent APIs across all components. This is the primary focus of ongoing SDK development and will receive new features and platform support going forward.
+
+**For new projects**, we recommend the **PlayFab Unified SDK (v2)** if the currently supported platforms meet your requirements. **Existing projects** using v1 Standalone SDKs can [migrate to v2](unified-sdk/migrating-from-v1.md) to take advantage of the unified architecture.
+
+The **v1 Standalone SDKs** remain supported for now and provide broader platform coverage for projects that require platforms not yet supported in v2.
+
+> [!IMPORTANT]
+> v1 and v2 SDKs cannot be used together in the same project. If you need a platform not yet supported in v2, use v1 for all components.
+
+## PlayFab Unified SDK (v2)
+
+The [PlayFab Unified SDK](unified-sdk/overview.md) provides a consistent, streamlined integration experience across all PlayFab components.
+
+### Key Benefits
+
+- **Single SDK**: One installation and update process for all PlayFab features
+- **Unified Authentication**: Authenticate once and use the resulting entity handle across all components
+- **Automatic Token Management**: Background token refresh prevents session expiration
+- **Consistent Programming Model**: Standardized patterns for initialization, API calls, and error handling
+- **Modern Development Practices**: Advanced memory management and thread control through XTaskQueue integration
+
+### Supported Platforms (v2)
+
+| Platform | Availability |
+|----------|--------------|
+| Windows (PC and Handheld) | Supported |
+| Xbox (One, Series S/X, Cloud) | Supported |
+| Steam Deck | Supported |
+| PlayStation 5 | Coming soon |
+| Nintendo Switch 2 | Coming soon |
+
+## PlayFab Standalone SDKs (v1)
+
+The [v1 Standalone SDKs](sdk-overview.md) consist of separate SDK packages for different PlayFab features. While still fully supported, they require managing multiple SDK installations and manual coordination between components.
+
+### SDK Components (v1)
+
+- **[PlayFab Services SDK](playfab-sdk-intro.md)**: LiveOps, economy, matchmaking, and data analytics
+- **[PlayFab Party SDK](../multiplayer/networking/party-sdks.md)**: Networking and voice/text chat communication
+- **[PlayFab Lobby and Matchmaking SDK](../multiplayer/lobby/lobby-matchmaking-sdks/lobby-matchmaking-sdks.md)**: Lobby and matchmaking features
+
+### Supported Platforms (v1)
+
+The v1 Standalone SDKs support a broader range of platforms:
+
+| Platform | Availability |
+|----------|--------------|
+| Windows (PC and Handheld) | Supported |
+| Xbox (One, Series S/X, Cloud) | Supported |
+| iOS | Supported |
+| macOS | Supported |
+| Android | Supported |
+| Linux | Supported |
+| PlayStation 4 | Supported (NDA required) |
+| PlayStation 5 | Supported (NDA required) |
+| Nintendo Switch | Supported (NDA required) |
+
+## See also
+
+- [PlayFab Unified SDK (v2)](unified-sdk/overview.md)
+- [Standalone SDKs overview (v1)](sdk-overview.md)
+- [Request access for SDKs and samples](request-access-for-sdks-samples.md)
diff --git a/playfab-docs/sdks/sdkgenerator/quickstart.md b/playfab-docs/sdks/sdkgenerator/quickstart.md
index d7d5b58a5..a47fc29e2 100644
--- a/playfab-docs/sdks/sdkgenerator/quickstart.md
+++ b/playfab-docs/sdks/sdkgenerator/quickstart.md
@@ -14,17 +14,17 @@ ms.localizationpriority: medium
 
 The SDK Generator is a node.js-based program that takes a JSON description of the PlayFab API, and uses it to generate out all the different SDKs that must be kept up to date. The SDK Generator project also contains the sources for all PlayFab SDKs on all platforms. If you want to make a change in an SDK, this is where the change has to go.
 
-Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com/en-us/sign-up). 
+Before you can call any PlayFab API, you must have a [PlayFab developer account](https://developer.playfab.com). 
 
 ## Prerequisites
 
 1. Any recent MS-Windows Operating System.
 2. You must have Node.js installed: <https://nodejs.org/>
    - The location of node.exe must be in your PATH environment variable. Default: C:\Program Files (x86)\nodejs\
-   - It is highly suggested that you install Node.js tools for Visual Studio: <https://beta.visualstudio.com/vs/node-js/>.
+   - It's highly suggested that you install Node.js tools for Visual Studio: <https://beta.visualstudio.com/vs/node-js/>.
 3. `SdkGenerator` requires several PlayFab repositories, cloned to your local machine, as sibling folders to `SdkGenerator`.
    - `<parent-folder>/SdkGenerator = <https://github.com/PlayFab/SDKGenerator>` (you're looking at it)
-   - `<parent-folder>/sdks/<targetSDK>` - For every SDK you want to generate, you should git-clone the PlayFab repository for that target into the "sdks" sub-folder first. In many cases, there are required files in the repo which are not generated.
+   - `<parent-folder>/sdks/<targetSDK>` - For every SDK you want to generate, you should git-clone the PlayFab repository for that target into the "sdks" subfolder first. In many cases, there are required files in the repo which aren't generated.
 4. `SdkGenerator` can be configured to read from other PlayFab repositories, cloned to your local machine, as sibling folders to SdkGenerator.
    - `<parent-folder>/API_Specs = <https://github.com/PlayFab/api_specs>`
 
@@ -72,13 +72,13 @@ Flags are optional, and can be used to generate console APIs.
 
 Setting up a new target in the `SdkGenerator` is fairly simple. This example has been added to the `SdkGenerator` for reference: [https://github.com/PlayFab/SDKGenerator/tree/master/targets/newTarget](https://github.com/PlayFab/SDKGenerator/tree/master/targets/newTarget).
 
-- Add a new sub-folder in [SdkGenerator/Targets](https://github.com/PlayFab/SDKGenerator/tree/master/targets).
+- Add a new subfolder in [SdkGenerator/Targets](https://github.com/PlayFab/SDKGenerator/tree/master/targets).
 - Add a "make.js" file to your new target.
   - Implement `makeClientAPI2`, `makeServerAPI`, and/or `makeCombinedAPI` in the file, as shown in the [NewTarget Example](https://github.com/PlayFab/SDKGenerator/blob/master/targets/newTarget/make.js).
-  - Optionally, you may use template files and source files, as described in the NewTarget example.
-- Add a new bat-file to generate your sdk in [SdkGenerator/SDKBuildScripts](https://github.com/PlayFab/SDKGenerator/tree/master/SDKBuildScripts).
+  - Optionally, you could use template files and source files, as described in the NewTarget example.
+- Add a new bat-file to generate your SDK in [SdkGenerator/SDKBuildScripts](https://github.com/PlayFab/SDKGenerator/tree/master/SDKBuildScripts).
 
-PlayFab sometimes accepts submissions for new SDKs. This process is extensive, and it has to be integrated with our automated build and testing system. For more information contact us on the forums.
+PlayFab sometimes accepts submissions for new SDKs. This process is extensive, and it has to be integrated with our automated build and testing system. For more information, contact us on the forums.
 
 ## Troubleshooting
 
@@ -88,6 +88,6 @@ For a complete list of available APIs, check out the [API References](../../api
 
 We love to hear from our developer community! Do you have ideas on how we can make our products and services better?
 
-Our Developer Success Team can assist with answering any questions as well as process any feedback you have about PlayFab services.
+Our Developer Success Team can assist with answering any questions and process any feedback you have about PlayFab services.
 
-[Forums, Support and Knowledge Base](https://community.playfab.com/)
+[Forums, Support, and Knowledge Base](https://community.playfab.com/)
diff --git a/playfab-docs/sdks/toc.yml b/playfab-docs/sdks/toc.yml
index fc4ee4cd1..1e7531ed8 100644
--- a/playfab-docs/sdks/toc.yml
+++ b/playfab-docs/sdks/toc.yml
@@ -1,150 +1,164 @@
 items:
-- name: Overview
-  href: sdk-overview.md
+- name: SDK Products
+  href: sdk-products.md
 - name: Request access
   href: request-access-for-sdks-samples.md
-- name: PlayFab Unified SDK
+- name: PlayFab Unified SDK (v2)
   href: unified-sdk/toc.yml
-- name: Services SDKs
+- name: PlayFab Unified SDK for Unreal Engine (v2)
+  href: unified-unreal/overview.md
+- name: PlayFab Standalone SDKs (v1)
   items:
   - name: Overview
-    href: playfab-sdk-intro.md
-  - name: Release notes
+    href: sdk-overview.md
+  - name: Services SDKs (v1)
     items:
-    - name: C/C++ SDK release notes
-      href: ../release-notes/playfab-c/toc.yml
-    - name: Other SDK release notes
-      href: ../release-notes/toc.yml
-  - name: Languages
-    href: languages/index.yml
-    items:
-    - name:  C/C++
-      href: c/index.md
+    - name: Overview
+      href: playfab-sdk-intro.md
+    - name: Release notes
+      items:
+      - name: C/C++ SDK release notes
+        href: ../release-notes/playfab-c/toc.yml
+      - name: Other SDK release notes
+        href: ../release-notes/toc.yml
+    - name: Languages
+      href: languages/index.yml
       items:
-        - name: Quickstart - Win32
-          href: c/quickstart-win32.md
+      - name: C/C++
+        href: c/index.md
+        items:
+          - name: Quickstart - Win32
+            href: c/quickstart-win32.md
+          - name: Quickstart - GDK
+            href: c/quickstart-gdk.md
+          - name: Quickstart - Android
+            href: c/quickstart-android.md
+          - name: Quickstart - iOS
+            href: c/quickstart-ios.md
+          - name: Quickstart - macOS
+            href: c/quickstart-macos.md
+          - name: Quickstart - Linux
+            href: c/quickstart-Linux.md
+          - name: Making Async Calls
+            href: c/async.md
+          - name: SDK Lifecycle
+            href: c/lifecycle.md
+          - name: Entity Handles
+            href: c/entity-handles.md
+          - name: Managing Memory
+            href: c/memory.md
+          - name: HTTP Configuration
+            href: c/http-config.md
+          - name: Handling Errors
+            href: c/errors.md
+          - name: Handling Token Expiration
+            href: c/relogin.md
+          - name: Debug Tracing
+            href: c/tracing.md
+          - name: Event Pipeline
+            href: c/event-pipeline/eventpipeline.md
+            items:
+            - name: Event Pipeline Tutorial
+              href: c/event-pipeline/eventpipeline-tutorial.md
+          - name: Initializing Servers
+            href: c/server.md
+      - name: Legacy C++
+        href: playfab-cpp/index.md
+        items:
         - name: Quickstart - GDK
-          href: c/quickstart-gdk.md
-        - name: Quickstart - Android
-          href: c/quickstart-android.md
-        - name: Quickstart - iOS
-          href: c/quickstart-ios.md
-        - name: Quickstart - macOS
-          href: c/quickstart-macos.md
+          href: playfab-cpp/quickstart-gdk.md
         - name: Quickstart - Linux
-          href: c/quickstart-Linux.md
-        - name: Making Async Calls
-          href: c/async.md
-        - name: Managing Memory
-          href: c/memory.md
-        - name: Handling Token Expiration
-          href: c/relogin.md
-        - name: Debug Tracing
-          href: c/tracing.md
-        - name: Event Pipeline
-          href: c/event-pipeline/eventpipeline.md
-          items:
-          - name: Event Pipeline Tutorial
-            href: c/event-pipeline/eventpipeline-tutorial.md
-        - name: Initializing Servers
-          href: c/server.md
-    - name: Legacy C++
-      href: playfab-cpp/index.md
-      items:
-      - name: Quickstart - GDK
-        href: playfab-cpp/quickstart-gdk.md
-      - name: Quickstart - Linux
-        href: playfab-cpp/quickstart-linux.md
-      - name: Quickstart - Windows
-        href: playfab-cpp/quickstart-windows.md
-    - name:  C#
-      href: c-sharp/index.md
-      items:
-      - name: Quickstart
-        href: c-sharp/quickstart.md
-    - name:  Java
-      href: java/index.md
-      items:
-      - name: Quickstart
-        href: java/quickstart.md
-    - name: JavaScript
-      href: javascript/index.md
-      items:
-      - name: Quickstart
-        href: javascript/quickstart.md
-    - name:  Lua
-      href: lua/index.md
-      items:
-      - name: Quickstart - Corona
-        href: lua/quickstart-corona.md
-      - name: Quickstart - Defold
-        href: lua/quickstart-defold.md
-    - name: NodeJS
-      href: nodejs/index.md
-      items:
-      - name: Quickstart
-        href: nodejs/quickstart.md
-    - name:  Objective-C
-      href: objective-c/index.md
-      items:
-      - name: Quickstart
-        href: objective-c/quickstart.md
-    - name: Python
-      href: python/index.md
-      items:
-      - name: Quickstart
-        href: python/quickstart.md
-  - name: Platforms
-    href: platforms/index.yml
-    items:
-    - name: Android
-      href: platforms/android.md
-    - name: iOS
-      href: platforms/ios.md
-    - name: macOS
-      href: platforms/macos.md
-    - name: Linux
-      href: platforms/linux.md
-    - name: Microsoft GDK
-      href: platforms/gdk.md
-    - name: Nintendo Switch
-      href: platforms/switch.md
-    - name: PlayStation
-      href: platforms/playstation.md
-    - name: Windows
-      href: platforms/windows.md
-    - name: Services and Tools
-      href: platforms/services.md
-  - name: Game engines
-    href: game-engines/index.yml
-    items:
-      - name: Cocos2d-x
-        href: cocos2d-x/index.md
+          href: playfab-cpp/quickstart-linux.md
+        - name: Quickstart - Windows
+          href: playfab-cpp/quickstart-windows.md
+      - name: C#
+        href: c-sharp/index.md
+        items:
+        - name: Quickstart
+          href: c-sharp/quickstart.md
+      - name: Java
+        href: java/index.md
         items:
         - name: Quickstart
-          href: cocos2d-x/quickstart.md
-      - name:  Unity3D
-        href: unity3d/index.md
+          href: java/quickstart.md
+      - name: JavaScript
+        href: javascript/index.md
         items:
         - name: Quickstart
-          href: unity3d/quickstart.md
-        - name: Installing the PlayFab SDK for Unity
-          href: unity3d/installing-unity3d-sdk.md
-      - name: Unreal Engine
-        href: unreal/index.md
+          href: javascript/quickstart.md
+      - name: Lua
+        href: lua/index.md
+        items:
+        - name: Quickstart - Corona
+          href: lua/quickstart-corona.md
+        - name: Quickstart - Defold
+          href: lua/quickstart-defold.md
+      - name: Node.js
+        href: nodejs/index.md
         items:
         - name: Quickstart
-          href: unreal/quickstart.md
-- name: Lobby and Matchmaking SDKs
-  href: ../multiplayer/lobby/lobby-matchmaking-sdks/toc.yml
-- name: Party SDKs
-  href: ../multiplayer/networking/party-sdks/toc.yml
+          href: nodejs/quickstart.md
+      - name: Objective-C
+        href: objective-c/index.md
+        items:
+        - name: Quickstart
+          href: objective-c/quickstart.md
+      - name: Python
+        href: python/index.md
+        items:
+        - name: Quickstart
+          href: python/quickstart.md
+    - name: Platforms
+      href: platforms/index.yml
+      items:
+      - name: Android
+        href: platforms/android.md
+      - name: iOS
+        href: platforms/ios.md
+      - name: macOS
+        href: platforms/macos.md
+      - name: Linux
+        href: platforms/linux.md
+      - name: Microsoft GDK
+        href: platforms/gdk.md
+      - name: Nintendo Switch
+        href: platforms/switch.md
+      - name: PS5 | PS4
+        href: platforms/playstation.md
+      - name: Windows
+        href: platforms/windows.md
+      - name: Services and Tools
+        href: platforms/services.md
+    - name: Game engines
+      href: game-engines/index.yml
+      items:
+        - name: Cocos2d-x
+          href: cocos2d-x/index.md
+          items:
+          - name: Quickstart
+            href: cocos2d-x/quickstart.md
+        - name: Unity3D
+          href: unity3d/index.md
+          items:
+          - name: Quickstart
+            href: unity3d/quickstart.md
+          - name: Installing the PlayFab SDK for Unity
+            href: unity3d/installing-unity3d-sdk.md
+        - name: Unreal Engine
+          href: unreal/index.md
+          items:
+          - name: Quickstart
+            href: unreal/quickstart.md
+  - name: Lobby and Matchmaking SDKs (v1)
+    href: ../multiplayer/lobby/lobby-matchmaking-sdks/toc.yml
+  - name: Party SDKs (v1)
+    href: ../multiplayer/networking/party-sdks/toc.yml
 - name: Multiplayer Server SDKs
   items:
   - name: Overview
     href: ../multiplayer/servers/server-sdks.md
   - name: Unreal Server SDK
-    href: ../multiplayer/servers/server-sdks/toc.yml
+    href: ../multiplayer/servers/server-sdks/unreal-gsdk/toc.yml
 - name: Tools and utilities
   href: tools/index.yml
   items:
@@ -153,7 +167,7 @@ items:
     items:
     - name: Quickstart
       href: sdkgenerator/quickstart.md
-  - name:  Postman
+  - name: Postman
     href: postman/index.md
     items:
     - name: Quickstart
diff --git a/playfab-docs/sdks/unified-unreal/overview.md b/playfab-docs/sdks/unified-unreal/overview.md
new file mode 100644
index 000000000..b029aaa6f
--- /dev/null
+++ b/playfab-docs/sdks/unified-unreal/overview.md
@@ -0,0 +1,79 @@
+---
+title: PlayFab for Unreal Engine Overview
+author: Jeffrey-Shi
+description: Overview of PlayFab for Unreal Engine, the next-generation integration built on the PlayFab Unified SDK
+ms.author: jeffshi
+ms.date: 02/01/2026
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, unreal engine, unified sdk, plugin, oss, onlinesubsystem, multiplayer, party
+ms.localizationpriority: medium
+---
+
+# PlayFab for Unreal Engine (v2 Unified)
+
+PlayFab for Unreal Engine (v2 Unified) is the next-generation integration built on top of the [PlayFab Unified SDK](../unified-sdk/overview.md). It provides comprehensive integration with PlayFab's backend services for Unreal Engine game developers, bringing the modern development practices and unified architecture of the Unified SDK to the Unreal Engine ecosystem.
+
+## Overview
+
+PlayFab for Unreal Engine provides a unified integration experience, consolidating all PlayFab components into a single distribution. This distribution includes two main components:
+
+- **PlayFabUnreal**: Core plugin providing authentication, services, and game saves. Deliver PlayFab functionalities such as economy, leaderboards, player data, statistics, and more.
+- **OnlineSubsystemPlayFab**: Online Subsystem (OSS) integration enabling Lobby, Matchmaking, Party networking, and Voice over Internet Protocol (VOIP). Includes cross-play, cross-platform communication, and accessibility features powered by Azure Cognitive Services such as real-time text chat translation and voice transcription.
+
+## Supported Platforms
+
+PlayFab for Unreal Engine is ready to power your games on these platforms today:
+
+- **Windows** (PC and Handheld)
+- **Xbox** (One, Series S|X, Cloud)
+- **Steam Deck**
+
+Support for additional platforms is in development. Check the [GitHub repository](https://github.com/PlayFab/PlayFabSDK_Unreal) for the latest platform availability updates.
+
+> [!IMPORTANT]
+> We recommend PlayFab for Unreal Engine (v2 Unified) for all new projects. It offers a modern, unified architecture with an improved developer experience.<br>
+ If your project requires a platform not yet supported in v2, use the [v1 PlayFab Unreal Plugin](../unreal/index.md) and [v1 OnlineSubsystem PlayFab](../../multiplayer/networking/party-unreal-engine-oss-overview.md) instead, as v1 and v2 cannot be used together in the same project.
+
+## Components
+
+### OnlineSubsystemPlayFab (OSS)
+
+The OnlineSubsystem PlayFab (OSS) provides full integration with Unreal Engine's Online Subsystem framework, enabling PlayFab's multiplayer and networking services through standard Unreal interfaces. This component includes:
+
+- **Lobby**: Create and manage game lobbies for multiplayer sessions using Unreal's session interfaces
+- **Matchmaking**: Connect players based on skill, preferences, and other criteria
+- **Party Data Communication**: Low-latency, cross-platform messaging for real-time multiplayer gameplay
+- **Party Voice Chat**: Integrated voice communication with Azure Cognitive Services features like speech-to-text and translation
+
+The OSS integrates seamlessly with Unreal Engine's existing networking patterns, letting you use familiar Unreal APIs while leveraging PlayFab's scalable backend infrastructure.
+
+### PlayFabUnreal Plugin
+
+The PlayFabUnreal plugin provides core PlayFab functionality:
+
+- **PlayFab Core**: Authentication and event pipeline (telemetry) services that form the foundation for all PlayFab operations
+- **PlayFab Services**: Game features including leaderboards, economy, player data, statistics, and catalog management
+- **PlayFab Game Saves**: Cross-platform cloud saves for preserving player progress across devices and sessions
+
+## Getting Started
+
+For setup instructions and detailed documentation, visit the GitHub repository:
+
+**[PlayFab Unreal Engine Plugin on GitHub](https://github.com/PlayFab/PlayFabSDK_Unreal)**
+
+The repository includes:
+
+- Installation and configuration guides
+- API reference documentation
+- Sample projects and code examples
+- Platform-specific setup instructions
+
+## Related Resources
+
+- [PlayFab Unified SDK Overview](../unified-sdk/overview.md)
+- [v1 PlayFab Unreal Plugin](../unreal/index.md)
+- [v1 OnlineSubsystem PlayFab](../../multiplayer/networking/party-unreal-engine-oss-overview.md)
+- [PlayFab Game Saves](../../player-progression/game-saves/overview.md)
+- [PlayFab Party](../../multiplayer/networking/party-sdks.md)
+- [PlayFab Multiplayer](../../multiplayer/lobby/lobby-matchmaking-sdks/lobby-matchmaking-sdks.md)
diff --git a/playfab-docs/sdks/unity3d/installing-unity3d-sdk.md b/playfab-docs/sdks/unity3d/installing-unity3d-sdk.md
index c88b9c77b..4bec0c56e 100644
--- a/playfab-docs/sdks/unity3d/installing-unity3d-sdk.md
+++ b/playfab-docs/sdks/unity3d/installing-unity3d-sdk.md
@@ -1,7 +1,7 @@
 ---
 title: Installing the PlayFab SDK Without Editor Extensions for Unity
 author: DanBehrendt
-description: This guide will help you install the PlayFab Unity 3D SDK and configure your project.
+description: This guide helps you install the PlayFab Unity 3D SDK and configure your project.
 ms.author: jenelleb
 ms.date: 1/25/2020
 ms.topic: article
@@ -10,19 +10,19 @@ keywords: playfab, unity3d, playfab unity sdk, csharp, unity
 ms.localizationpriority: medium
 ---
 
-# Installing the PlayFab SDK Without Editor Extensions for Unity
+# Installing the PlayFab SDK without Editor Extensions for Unity
 
 You have two options when installing the PlayFab Unity 3D SDK:
 
-- Install the PlayFab Unity Editor Extensions Asset Package. Then use Editor Extension to install the PlayFab Unity 3D SDK and configure your Unity Project.
+- Install the PlayFab Unity Editor Extensions Asset Package. Then use Editor Extensions to install the PlayFab Unity 3D SDK and configure your Unity Project.
 
     PlayFab Editor Extensions is a stand-alone Unity plug-in that streamlines getting started with PlayFab.
 
-    When a supported SDK is installed, additional service menus are available. These menus provide access to SDK configurations. These configuration settings are saved in a combination of places to ensure that the data persists throughout Unity compilations and deployments.
+    When a supported SDK is installed, other service menus are available. These menus provide access to SDK configurations. These configuration settings are saved in a combination of places to ensure that the data persists throughout Unity compilations and deployments.
 
-- Install the PlayFab Unity 3D SDK directly without using PlayFab Unity Editor Extensions. When you use this installation method, you configure your Unity Project directly by setting properties property values in your code.
+- Install the PlayFab Unity 3D SDK directly without using PlayFab Unity Editor Extensions. When you use this installation method, you configure your Unity Project directly by setting the property values in your code.
 
-This content assumes you that you have a [PlayFab developer account](https://developer.playfab.com/en-us/sign-up) and an existing Unity Project.
+This content assumes you that you have a [PlayFab developer account](https://developer.playfab.com) and an existing Unity Project.
 
 ## Download and install the SDK only
 
@@ -30,21 +30,21 @@ To install the SDK without using the PlayFab Unity Editor Extensions:
 
 1. Open your Unity project.
 2. Download the [PlayFab Unity3D SDK Asset Package](https://aka.ms/playfabunitysdkdownload) from the PlayFab GitHub repo.
-3. Navigate to where you downloaded the file, and double-click on the .UnityPackage file to open the **Import Unity Package** dialog in the Unity Editor.
+3. Navigate to where you downloaded the file, and double-click on the UnityPackage file to open the **Import Unity Package** dialog in the Unity Editor.
 4. To import the PlayFab Unity3D SDK into your project, select **Import**.
 
-## Setting the Title ID without using the editor extensions
+## Setting the Title ID without using the Editor Extensions
 
 To set the title:
 
-1. In the Unity Editor Project panel select the **Assets** folder.
+1. In the Unity Editor Project panel, select the **Assets** folder.
 2. Open the **Assets** > **PlayFabSdk** > **Shared** > **Public** > **Resources** folder.
 3. Select the PlayFabSettings Asset.
 4. In the **Inspector** window, set the **Title ID**.
 
     ![PlayFab Inspector Title ID Setting](media/playfab-shared-settings-title-id.png)
 
-If you are making a server build, be sure to provide the **Developer Secret Key** as well.
+If you're making a server build, be sure to provide the **Developer Secret Key** as well.
 
 ![PlayFab Developer Secret Key Setting](media/playfab-shared-settings-secret-key.png)
 
diff --git a/playfab-docs/sdks/unity3d/quickstart.md b/playfab-docs/sdks/unity3d/quickstart.md
index 656a2ded8..7204b670f 100644
--- a/playfab-docs/sdks/unity3d/quickstart.md
+++ b/playfab-docs/sdks/unity3d/quickstart.md
@@ -18,7 +18,7 @@ This quickstart helps you make your first PlayFab API call in the Unity engine.
 
 ## Requirements
 
-- A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+- A [PlayFab developer account](https://developer.playfab.com).
 - An installed copy of the Unity Editor. To install Unity for personal use via Unity Hub, or Unity+ for professional use, see [Download Unity](https://unity.com/download).
   > [!NOTE]
   > The PlayFab Unity SDK supports Unity Editor version 5.3 (released December 2015) and higher.
diff --git a/playfab-docs/sdks/unreal/quickstart.md b/playfab-docs/sdks/unreal/quickstart.md
index e2ff2eb0e..f3c6cf5d5 100644
--- a/playfab-docs/sdks/unreal/quickstart.md
+++ b/playfab-docs/sdks/unreal/quickstart.md
@@ -24,7 +24,7 @@ You can use the PlayFab plugin for the Unreal Engine to manage LiveOps for your
 
 ## Prerequisites
 
-* A [PlayFab developer account](https://developer.playfab.com/en-us/sign-up).
+* A [PlayFab developer account](https://developer.playfab.com).
 * An installation of [Visual Studio](https://visualstudio.microsoft.com/downloads/) that is configured for Unreal Engine. For information about configuring Visual Studio, see [Setting Up Visual Studio for Unreal Engine](https://docs.unrealengine.com/en-US/Programming/Development/VisualStudioSetup/index.html).
 * An installation of the [Unreal Engine](https://www.unrealengine.com/download). For information about installing the Unreal Engine, see the [Unreal Engine installation guide](https://docs.unrealengine.com/4.27/en-US/Basics/Projects/Browser/).
 * An installation of the PlayFab Unreal plugin. You can install the Unreal plugin from the [Unreal Engine marketplace](https://www.unrealengine.com/marketplace/playfab-sdk).
@@ -46,6 +46,8 @@ To enable the PlayFab Plugin:
 1. From the **Settings** menu, under **Game Specific Settings** select **Plugins**.
 2. Enable the **PlayFab** plugin and restart Unreal Engine as required.
 
+If "PlayFab" doesn't appear in **Plugins**, verify that the plugin is installed from the Unreal Marketplace. Restart Unreal Editor. Then open **Plugins** again and search for "PlayFab."
+
 ### Add PlayFab as a Module dependency in C++
 
 In Visual Studio, add PlayFab as a module dependency in your C++ project:
diff --git a/playfab-docs/test-documents/login-basics-best-practices-01.md b/playfab-docs/test-documents/login-basics-best-practices-01.md
new file mode 100644
index 000000000..bf8ac253d
--- /dev/null
+++ b/playfab-docs/test-documents/login-basics-best-practices-01.md
@@ -0,0 +1,123 @@
+---
+title: Login basics and best Practices
+author: antnguyen89
+description: Describes the basics and Best Practices for login and authentication of players in PlayFab.
+ms.author: antnguyen
+ms.date: 02/20/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, authentication
+ms.localizationpriority: medium
+---
+
+# Login basics and best practices
+
+## Platform-specific authentication tutorials
+
+While all of the platform-specific authentication tutorials demonstrate logging in with [LoginWithCustomID](xref:titleid.playfabapi.com.client.authentication.loginwithcustomid), the uses for this login in a published game are limited to pairing a PlayFab account to a pre-existing database, or another back-end system.
+
+Otherwise, it's rare for a published title to use a custom ID for a primary login, since in most cases you want to capture additional information on the player's platform.
+
+### Why we demonstrate this first
+
+Bluntly - because it's the easiest. A custom ID can be anything, and it makes it easier to call your first API. Once you get serious about developing and releasing your title, it's likely you'll switch to another login mechanism.
+
+### Best practice
+
+Unless you know *exactly* why you want `LoginWithCustomId` in your released title, you should migrate to another login mechanism before you launch.
+
+## Anonymous login mechanisms
+
+Anonymous login mechanisms are the simplest to use. They require *zero* input from the player, so there's no friction to the first time user experience - and the result is a unique account in PlayFab for each player. *This is the most common login mechanism*.
+
+These logins include:
+
+- [LoginWithIOSDeviceID](xref:titleid.playfabapi.com.client.authentication.loginwithiosdeviceid)
+- [LoginWithAndroidDeviceID](xref:titleid.playfabapi.com.client.authentication.loginwithandroiddeviceid)
+- [LoginWithCustomID](xref:titleid.playfabapi.com.client.authentication.loginwithcustomid)
+- [LoginWithNintendoSwitchDeviceId](xref:titleid.playfabapi.com.client.authentication.loginwithnintendoswitchdeviceid)
+
+Since they're anonymous, these methods can uniquely identify a device, *but contain no recoverable information about the player*. If the player loses or breaks their device, the account is lost, and may be difficult to recover. In most cases the account is orphaned and not retrievable.
+
+So why use it? Because it's the lowest possible barrier to entry for the player, requiring no interaction. It gets the player trying your game with minimal effort, while creating an account they can get back to for continuity (as long as they have that device).
+
+### Best practice
+
+Your game should use an *anonymous* login for creating a new account and linking new devices to an existing account. We recommend this because some players might abandon a game that asks for an e-mail or identifiable information.
+
+However, once the anonymous login is complete, you should provide the option to add *recoverable* login credentials, and provide some explanation regarding the benefits.
+
+In particular, you should make sure that paying customers are guided to the *recoverable* login systems, to prevent loss of their accounts. A free account lost forever is a disappointment...
+
+A paid account lost forever affects revenue.
+
+### iOS devices
+
+For iOS devices, the player ID changes if they uninstall your game, and then reinstall it. One way to make sure you have a consistent ID on iOS is to save the device ID for the player to the iTunes KeyChain, so that you can read it from there on game start, and use it to sign in.
+
+You must determine how to generate unique custom IDs for any other device or platform. Custom IDs are an effective alternative for other platforms or devices, but you must generate your custom IDs with care. If they're too simple, you risk hackers stealing the accounts of others.
+
+### Android devices
+
+For latest best practices, see [Google's guidelines on user data IDs](https://developer.android.com/training/articles/user-data-ids).
+
+> [!NOTE]
+> Binding a recoverable login is only required *once* per device. Once bound, the game can continue to use the anonymous login with no drawbacks. See the next section.
+
+An anonymous login is convenient for the player, but it *isn't* required. Your game can rely exclusively on a recoverable login mechanism. However, your players are happier if they *don't* have to type a password every time they log in.
+
+## Recoverable login mechanisms
+
+A *recoverable* login mechanism requires some identity information from the player. As described above, it can be paired with an anonymous login for the best player experience.
+
+### Pure PlayFab options
+
+The simplest options are:
+
+- [LoginWithPlayFab](xref:titleid.playfabapi.com.client.authentication.loginwithplayfab)
+- [LoginWithEmailAddress](xref:titleid.playfabapi.com.client.authentication.loginwithemailaddress)
+
+If used, the e-mail or username-plus-password are authenticated directly by PlayFab. The account is recoverable by the e-mail or username, *even* if the user forgets their password. The login is generally secure (you can implement your own password strength check into your game to improve this).
+
+### Third party API options
+
+These require separate API calls to another service, but don't require extra SDK installations:
+
+- [LoginWithKongregate](xref:titleid.playfabapi.com.client.authentication.loginwithkongregate)
+- [LoginWithSteam](xref:titleid.playfabapi.com.client.authentication.loginwithsteam)
+- [LoginWithTwitch](xref:titleid.playfabapi.com.client.authentication.loginwithtwitch)
+- [LoginWithGameCenter](xref:titleid.playfabapi.com.client.authentication.loginwithgamecenter) (iOS only, and provided you require secure authentication.)
+
+Secure authentication happens between your user, and the third party service API call.
+
+### Third party SDK options
+
+These require a separate SDK installed into your game. Secure authentication happens within the third party SDK.
+
+- [LoginWithFacebook](xref:titleid.playfabapi.com.client.authentication.loginwithfacebook)
+- [LoginWithGoogleAccount](xref:titleid.playfabapi.com.client.authentication.loginwithgoogleaccount)
+
+In all third party options, those services process the login credentials, and you pass a secure token to the appropriate PlayFab login method. PlayFab remains unaware of the login credentials for those services.
+
+### More best practices
+
+Use an appropriate anonymous login for a basic login, and encourage your player to link to a recoverable login. You should pick any one or more of the recoverable mechanisms with which you're comfortable and familiar.
+
+> [!TIP]
+> Account recovery only requires *one* recoverable login, so don't pressure your player to use all of them.
+
+## Insecure login mechanisms
+
+One benefit of recoverable login mechanisms is they're more secure than logging in with a custom ID, as they require verified authentication with a third party rather than relying on a user's custom ID remaining a shared secret.
+
+## Conclusion
+
+Anonymous login is great, and it provides the user with a fully automated login process. The downside is account recovery, which is sometimes impossible without a recoverable login.
+
+The following flow chart describes anonymous login followed by adding a recoverable login mechanism.
+
+![PayFab anonymous login and recoverable login mechanism](../media/tutorials/playfab-anonymous-login-and-recoverable-login.png)  
+
+### Best practice
+
+Use the appropriate anonymous login for your device, paired with one, or more options for account recovery.
diff --git a/playfab-docs/test-documents/multiple-logins-01.md b/playfab-docs/test-documents/multiple-logins-01.md
new file mode 100644
index 000000000..d1669b31c
--- /dev/null
+++ b/playfab-docs/test-documents/multiple-logins-01.md
@@ -0,0 +1,245 @@
+---
+title: Handling Multiple PlayFab Logins
+author: antnguyen89
+description: Describes how to use SDK features to manage multiple logins from a single client.
+ms.author: antnguyen
+ms.date: 02/20/2025
+ms.topic: article
+ms.service: azure-playfab
+keywords: playfab, authentication, sdk, unity, unreal
+ms.localizationpriority: medium
+---
+
+# Handling multiple PlayFab logins
+
+By default, most PlayFab SDKs cache player login results. This caching can be convenient in the most common scenario when you expect a single player login. In games where you support multiple concurrent players or servers where you manage both players' authentication material and server credentials, that caching can get in the way. To facilitate these scenarios, PlayFab SDKs contain both static and instanced API classes.
+
+## Static versus instanced API classes
+
+Most examples and sample code for PlayFab are built using static API classes. In Unity, for example, you might see a reference to __PlayFabClientAPI__. These static classes write to and read from static state within the SDK. Their dependence on static state makes it difficult to use these classes when you're working with multiple players within the same game client. Instanced API classes avoid these problems in exchange for increased management and tracking requirements on your part. In cases where you need to support multiple simultaneous PlayFab logins, we recommend using instanced API classes.
+
+In the Unity SDK, __PlayFabClientInstanceAPI__ is the instanced version of __PlayFabClientAPI__. All other API classes follow a similar naming pattern. When using the instanced version of an API class, you must create an instance of the class before you can call any methods. To create an instance, you have to specify some extra context. For most classes, the extra required context is just the player's authentication context. In Unity, this context is __PlayFabAuthenticationContext__. Some classes contain login calls. For these calls, you might not have a player's authentication context yet. If that's the case, you only have to provide basic settings like a title ID. These settings are passed in via a __PlayFabApiSettings__ object.
+
+## Using instanced API classes
+
+Once you have an instanced API class created with an appropriate authentication context or API settings object, it can be used similarly to a static class. All of the request and response objects are identical. The only difference is that you're responsible for tracking the lifetime of the instance and ensure that any potential callers of PlayFab are provided an appropriate instance. When you're dealing with multiple players, you require multiple instances of any API classes, one per player. It's often easiest to manage these instances encapsulated behind a player object as an owner, but that is left to you.
+
+Instanced classes that log in a player (such as __PlayFabClientInstanceAPI__) also create and cache the authentication context for that player within the API class instance. This feature allows you to easily reference the authentication context when creating any more classes you need.
+
+## Unity example
+
+This sample code demonstrates how multiple players can log in to a game and have independent state tracked in separate class instances. In this example, the API classes and basic functionality are encapsulated behind a simplistic __PlayFabPlayer__ object. When the game starts, we log in two players and then get any data stored in PlayFab for each of those players.
+
+```csharp
+using PlayFab;
+using PlayFab.ClientModels;
+using PlayFab.DataModels;
+using System.Collections.Generic;
+using UnityEngine;
+
+public class PlayFabLogin : MonoBehaviour
+{
+    PlayFabPlayer player1 = new PlayFabPlayer();
+    PlayFabPlayer player2 = new PlayFabPlayer();
+
+    // Start is called before the first frame update
+    void Start()
+    {
+        if (string.IsNullOrEmpty(PlayFabSettings.staticSettings.TitleId))
+        {
+            // Please change the titleId below to your own titleId from PlayFab Game Manager.
+            PlayFabSettings.staticSettings.TitleId = "";
+        }
+
+        player1.Login("testLogin1");
+        player2.Login("testLogin2");
+    }
+
+    // Update is called once per frame
+    void Update()
+    {
+        if (player1.loggedIn && !player1.dataLoaded && !player1.dataLoading)
+        {
+            player1.LoadData();
+        }
+        if (player2.loggedIn && !player2.dataLoaded && !player2.dataLoading)
+        {
+            player2.LoadData();
+        }
+    }
+}
+
+class PlayFabPlayer
+{
+    public bool loggedIn = false;
+    public bool dataLoading = false;
+    public bool dataLoaded = false;
+    public string PlayFabId;
+    public Dictionary<string, ObjectResult> playerData;
+
+    private PlayFabClientInstanceAPI clientApi;
+    private PlayFabDataInstanceAPI dataApi;
+
+    public void Login(string customId)
+    {
+        clientApi = new PlayFabClientInstanceAPI(PlayFabSettings.staticSettings);
+
+        var request = new LoginWithCustomIDRequest { CustomId = customId, CreateAccount = true };
+
+        clientApi.LoginWithCustomID(request, result =>
+        {
+            PlayFabId = result.PlayFabId;
+            loggedIn = true;
+            dataApi = new PlayFabDataInstanceAPI(clientApi.authenticationContext);
+            Debug.Log("Login call succeeded.");
+        }, error =>
+        {
+            Debug.LogWarning("Something went wrong with the login call.");
+            Debug.LogError("Here's some debug information:");
+            Debug.LogError(error.GenerateErrorReport());
+        });
+    }
+
+    public void LoadData()
+    {
+        dataLoading = true;
+        var request = new GetObjectsRequest { Entity = new PlayFab.DataModels.EntityKey { Id = clientApi.authenticationContext.EntityId, Type = clientApi.authenticationContext.EntityType } };
+
+        dataApi.GetObjects(request, result =>
+        {
+            playerData = result.Objects;
+            dataLoaded = true;
+            dataLoading = false;
+            Debug.Log("Player data loaded.");
+        }, error =>
+        {
+            Debug.LogWarning("Something went wrong with the GetObjects call.");
+            Debug.LogError("Here's some debug information:");
+            Debug.LogError(error.GenerateErrorReport());
+        });
+    }
+}
+```
+
+## Unreal example
+
+This code sample demonstrates an actor in Unreal that contains its own PlayFab login context. It shows how to encapsulate PlayFab API instance classes within an __ALoginActor__ class. Multiple __ALoginActor__ instances can be added to a map, given their own CustomIds, and perform PlayFab operations independently.
+
+LoginActor.h:
+```cpp
+#pragma once
+
+#include "CoreMinimal.h"
+#include "GameFramework/Actor.h"
+#include "PlayFab.h"
+#include "Core/PlayFabError.h"
+#include "Core/PlayFabClientDataModels.h"
+#include "Core/PlayFabClientAPI.h"
+#include "Core/PlayFabDataAPI.h"
+#include "LoginActor.generated.h"
+
+UCLASS()
+class MINUE_PF_MARKET_API ALoginActor : public AActor
+{
+	GENERATED_BODY()
+	
+public:	
+	// Sets default values for this actor's properties
+	ALoginActor();
+
+    // Please change the TitleId below to your own TitleId from PlayFab Game Manager.
+	UPROPERTY(EditAnywhere, config, Category = Settings)
+	FString TitleId = TEXT("");
+
+	UPROPERTY(EditAnywhere, config, Category = Settings)
+	FString CustomId = TEXT("ExampleCustomId");
+
+protected:
+	// Called when the game starts or when spawned
+
+	virtual void BeginPlay() override;
+
+	void OnLoginSuccess(const PlayFab::ClientModels::FLoginResult& Result);
+	void OnGetObjectsSuccess(const PlayFab::DataModels::FGetObjectsResponse& Result);
+	void OnError(const PlayFab::FPlayFabCppError& ErrorResult) const;
+
+public:	
+	bool LoggedIn = false;
+
+	// Called every frame
+	virtual void Tick(float DeltaTime) override;
+
+	PlayFabClientPtr clientAPI = nullptr;
+	PlayFabDataPtr dataAPI = nullptr;
+
+	TMap<FString, PlayFab::DataModels::FObjectResult> PlayerData;
+	bool DataLoaded = false;
+};
+```
+
+LoginActor.cpp:
+```cpp
+#include "LoginActor.h"
+
+ALoginActor::ALoginActor()
+{
+ 	// Set this actor to call Tick() every frame.  You can turn this off to improve performance if you don't need it.
+	PrimaryActorTick.bCanEverTick = true;
+}
+
+void ALoginActor::Tick(float DeltaTime)
+{
+    Super::Tick(DeltaTime);
+}
+
+void ALoginActor::BeginPlay()
+{
+	Super::BeginPlay();
+    GetMutableDefault<UPlayFabRuntimeSettings>()->TitleId = TitleId;
+
+    clientAPI = IPlayFabModuleInterface::Get().GetClientAPI();
+    dataAPI = IPlayFabModuleInterface::Get().GetDataAPI();
+
+    PlayFab::ClientModels::FLoginWithCustomIDRequest request;
+    request.CustomId = CustomId;
+    request.CreateAccount = true; 
+
+    clientAPI->LoginWithCustomID(request,
+        PlayFab::UPlayFabClientAPI::FLoginWithCustomIDDelegate::CreateUObject(this, &ALoginActor::OnLoginSuccess),
+        PlayFab::FPlayFabErrorDelegate::CreateUObject(this, &ALoginActor::OnError)
+    );
+}
+
+void ALoginActor::OnLoginSuccess(const PlayFab::ClientModels::FLoginResult& Result)
+{
+    UE_LOG(LogTemp, Log, TEXT("Login call succeeded."));
+    LoggedIn = true;
+
+    PlayFab::DataModels::FGetObjectsRequest dataRequest;
+    dataRequest.AuthenticationContext = Result.AuthenticationContext;
+    dataRequest.Entity.Id = Result.EntityToken->Entity->Id;
+    dataRequest.Entity.Type = Result.EntityToken->Entity->Type;
+
+    dataAPI->GetObjects(
+        dataRequest,
+        PlayFab::UPlayFabDataAPI::FGetObjectsDelegate::CreateUObject(this, &ALoginActor::OnGetObjectsSuccess),
+        PlayFab::FPlayFabErrorDelegate::CreateUObject(this, &ALoginActor::OnError)
+    );
+}
+
+void ALoginActor::OnError(const PlayFab::FPlayFabCppError& ErrorResult) const
+{
+    UE_LOG(LogTemp, Error, TEXT("Something went wrong with your API call.\nHere's some debug information:\n%s"), *ErrorResult.GenerateErrorReport());
+}
+
+void ALoginActor::OnGetObjectsSuccess(const PlayFab::DataModels::FGetObjectsResponse& Result)
+{
+    PlayerData = Result.Objects;
+    DataLoaded = true;
+	UE_LOG(LogTemp, Log, TEXT("Player data loaded."));    
+}
+```
+
+## Server authentication
+
+Similar to how instanced API classes allow a game client to handle multiple players, they allow servers to handle a combination of title and player authentication or even multiple titles simultaneously. The basic pattern is nearly identical. Instantiate an API class to handle server login, provide that instance the appropriate __PlayFabApiSettings__ object, and then call an authentication API. If you're on a server, that API is commonly __PlayFabAuthenticationInstanceAPI.GetEntityToken__. Just like a player login, the result of a __GetEntityToken__ call is cached in the API class instance and can be referenced to create more API class instances via the __authenticationContext__ instance property.
\ No newline at end of file
diff --git a/playfab-docs/whats-new/toc.yml b/playfab-docs/whats-new/toc.yml
index 016339489..a735f94d7 100644
--- a/playfab-docs/whats-new/toc.yml
+++ b/playfab-docs/whats-new/toc.yml
@@ -3,8 +3,10 @@ items:
 ##  href: whats-new.md
 - name: Previous Release Notes
   items:
-  - name: 2025 SDK Release Notes
+  - name: 2026 SDK Release Notes
     href: /playfab-docs/release-notes/index.md
+  - name: 2025 SDK Release Notes
+    href: /playfab-docs/release-notes/2025.md
   - name: Lobby and Matchmaking SDK Release Notes
     href: ../multiplayer/lobby/lobby-matchmaking-sdks/lobby-and-matchmaking-release-notes.md
   - name: PlayFab Party SDK Release Notes
diff --git a/scripts/validate-docs.ps1 b/scripts/validate-docs.ps1
new file mode 100644
index 000000000..c94c3a671
--- /dev/null
+++ b/scripts/validate-docs.ps1
@@ -0,0 +1,576 @@
+<#
+.SYNOPSIS
+    Validates PlayFab documentation files for common authoring issues.
+
+.DESCRIPTION
+    Checks changed (or all) Markdown and toc.yml files for:
+    - Missing/invalid frontmatter fields (including calendar date validation)
+    - Raw HTML usage
+    - Broken TOC links (href pointing to non-existent files)
+    - Missing image alt-text and broken image paths
+    - Heading structure issues (duplicate H1, heading skips, H1/title mismatch)
+    - Cross-repo link formatting
+    - Broken internal markdown links
+    - Broken include references
+    - Code blocks without language specifiers
+    - Orphaned redirect files (still on disk but listed in redirection JSON)
+    - Writing style issues (Latin abbreviations, em dashes, filler words,
+      contractions, hyphenated prefixes) — skips inline code and blockquotes
+
+.PARAMETER All
+    Validate all files under playfab-docs/ instead of just changed files.
+
+.PARAMETER Path
+    Validate a specific file or directory.
+
+.EXAMPLE
+    .\scripts\validate-docs.ps1              # changed files vs main
+    .\scripts\validate-docs.ps1 -All         # entire docs folder
+    .\scripts\validate-docs.ps1 -Path playfab-docs/economy-monetization
+#>
+
+param(
+    [switch]$All,
+    [string]$Path
+)
+
+$ErrorActionPreference = "Continue"
+$repoRoot = Split-Path -Parent $PSScriptRoot
+Push-Location $repoRoot
+try { # matched by Pop-Location at script end
+
+# --- Pre-compiled regexes (avoid recompilation per-line) ---
+
+$rxFrontmatter     = [regex]::new('(?s)^---\r?\n(.*?)\r?\n---', 'Compiled')
+$rxCodeFence       = [regex]::new('^\s*(`{3,}|~{3,})', 'Compiled')
+$rxRawHtml         = [regex]::new('<\s*(div|span|table|tr|td|th|thead|tbody|p|a|img|ul|ol|li|h[1-6]|strong|em|b|i|u|s|hr|pre|code|blockquote|form|input|button|select|style|script)\b[^>]*>', 'Compiled')
+$rxEmptyAlt        = [regex]::new('!\[\]\(', 'Compiled')
+$rxHeading         = [regex]::new('^(#{1,6})\s+(.+)$', 'Compiled')
+$rxCrossRepoMd     = [regex]::new('\]\(/gaming/[^)]+\.md\)', 'Compiled')
+$rxMdLink          = [regex]::new('\[([^\]]*)\]\(([^)]+)\)', 'Compiled')
+$rxInclude         = [regex]::new('\[!INCLUDE\s+\[[^\]]*\]\(([^)]+)\)', 'Compiled')
+$rxLatinAbbrev     = [regex]::new('(?<!\w)(e\.g\.|i\.e\.|etc\.|vs\.)', 'Compiled')
+$rxSpacedEmDash    = [regex]::new('\s\u2014|\u2014\s', 'Compiled')
+$rxFiller          = [regex]::new('(?i)\b(strongly|very|really)\b', 'Compiled')
+$rxContraction     = [regex]::new('(?i)\b(cannot|does not|do not|will not|is not|are not|has not|have not|should not|would not|could not|did not)\b', 'Compiled')
+$rxHyphenPrefix    = [regex]::new('(?i)\bre-(authenticate|authorize|configure|connect|create|deploy|enable|establish|evaluate|generate|initialize|install|register|run|send|start|try|use|validate|download|upload|build|load|check|discover|implement|write)\b', 'Compiled')
+$rxImageRef        = [regex]::new('!\[([^\]]*)\]\(([^)]+)\)', 'Compiled')
+$rxInlineCode      = [regex]::new('`[^`]+`', 'Compiled')
+
+# --- File-existence cache (avoids redundant Test-Path calls) ---
+
+$existsCache = @{}
+function Test-PathCached($resolvedPath) {
+    if (-not $existsCache.ContainsKey($resolvedPath)) {
+        $existsCache[$resolvedPath] = (Test-Path $resolvedPath)
+    }
+    return $existsCache[$resolvedPath]
+}
+
+# --- Collect files to validate ---
+
+$mdFiles = @()
+$tocFiles = @()
+
+if ($Path) {
+    $resolvedPath = Resolve-Path $Path -ErrorAction SilentlyContinue
+    if (-not $resolvedPath) {
+        Write-Host "ERROR: Path '$Path' not found." -ForegroundColor Red
+        exit 1
+    }
+    if (Test-Path $resolvedPath -PathType Container) {
+        $mdFiles = Get-ChildItem -Path $resolvedPath -Recurse -Filter "*.md" | Select-Object -ExpandProperty FullName
+        $tocFiles = Get-ChildItem -Path $resolvedPath -Recurse -Filter "toc.yml" | Select-Object -ExpandProperty FullName
+    } else {
+        if ($resolvedPath -match '\.md$') { $mdFiles = @($resolvedPath.Path) }
+        if ($resolvedPath -match 'toc\.yml$') { $tocFiles = @($resolvedPath.Path) }
+    }
+} elseif ($All) {
+    $docsPath = Join-Path $repoRoot "playfab-docs"
+    $mdFiles = Get-ChildItem -Path $docsPath -Recurse -Filter "*.md" | Select-Object -ExpandProperty FullName
+    $tocFiles = Get-ChildItem -Path $docsPath -Recurse -Filter "toc.yml" | Select-Object -ExpandProperty FullName
+} else {
+    # Changed files vs main (with CI support)
+    $changedFiles = @()
+    $useThreeDotDiff = $false
+
+    if ($env:GITHUB_ACTIONS -and $env:GITHUB_BASE_REF) {
+        # CI: use the PR base ref with three-dot diff
+        $baseBranch = "origin/$env:GITHUB_BASE_REF"
+        $useThreeDotDiff = $true
+    } else {
+        # Local: try main, then origin/main, then fall back to HEAD
+        $baseBranch = $null
+        $tryMain = git rev-parse --verify main 2>$null
+        if ($tryMain) {
+            $baseBranch = "main"
+        } else {
+            $tryOriginMain = git rev-parse --verify origin/main 2>$null
+            if ($tryOriginMain) {
+                $baseBranch = "origin/main"
+            }
+        }
+    }
+
+    if ($useThreeDotDiff) {
+        $changedFiles = git --no-pager diff --name-only "$baseBranch...HEAD" 2>&1
+        if ($LASTEXITCODE -ne 0) {
+            Write-Error "ERROR: Failed to detect changed files in CI. 'git diff $baseBranch...HEAD' exited with code $LASTEXITCODE."
+            Write-Error "Output: $changedFiles"
+            exit 1
+        }
+    } elseif ($baseBranch) {
+        $changedFiles = git --no-pager diff --name-only $baseBranch 2>&1
+        if ($LASTEXITCODE -ne 0) {
+            Write-Error "ERROR: Failed to detect changed files. 'git diff --name-only $baseBranch' exited with code $LASTEXITCODE."
+            Write-Error "Output: $changedFiles"
+            exit 1
+        }
+    } else {
+        # No base branch found — check uncommitted changes
+        $changedFiles = git --no-pager diff --name-only HEAD 2>$null
+        if (-not $changedFiles) {
+            $changedFiles = git --no-pager diff --name-only --cached 2>$null
+        }
+        if (-not $changedFiles) {
+            $changedFiles = git --no-pager status --porcelain 2>$null | ForEach-Object { ($_ -replace '^.{3}', '').Trim() }
+        }
+    }
+
+    if ($changedFiles) {
+        $mdFiles = $changedFiles | Where-Object { $_ -match '\.md$' -and $_ -match '^playfab-docs/' } |
+            ForEach-Object { Join-Path $repoRoot $_ } |
+            Where-Object { Test-Path $_ }
+        $tocFiles = $changedFiles | Where-Object { $_ -match 'toc\.yml$' -and $_ -match '^playfab-docs/' } |
+            ForEach-Object { Join-Path $repoRoot $_ } |
+            Where-Object { Test-Path $_ }
+    }
+}
+
+if ($mdFiles.Count -eq 0 -and $tocFiles.Count -eq 0) {
+    Write-Host "No files to validate." -ForegroundColor Yellow
+    Write-Host "Use -All to validate the entire docs folder, or -Path to target a specific path."
+    exit 0
+}
+
+# --- Issue tracking ---
+
+$errors = [System.Collections.Generic.List[object]]::new()
+$warnings = [System.Collections.Generic.List[object]]::new()
+$cleanFiles = [System.Collections.Generic.List[string]]::new()
+
+function Add-Error($file, $line, $check, $message) {
+    $script:errors.Add([PSCustomObject]@{
+        File = $file; Line = $line; Check = $check; Message = $message
+    })
+}
+function Add-Warning($file, $line, $check, $message) {
+    $script:warnings.Add([PSCustomObject]@{
+        File = $file; Line = $line; Check = $check; Message = $message
+    })
+}
+
+# --- Frontmatter parser ---
+
+function Get-Frontmatter($rawContent) {
+    $m = $rxFrontmatter.Match($rawContent)
+    if ($m.Success) { return $m.Groups[1].Value }
+    return $null
+}
+
+function Get-FrontmatterField($yaml, $fieldName) {
+    $escapedFieldName = [regex]::Escape($fieldName)
+    if ($yaml -match "(?m)^${escapedFieldName}:\s*(.+)$") {
+        return $Matches[1].Trim().Trim('"').Trim("'")
+    }
+    return $null
+}
+
+# --- Validate Markdown files ---
+
+$alwaysRequiredFields = @("author", "ms.author", "ms.topic", "ms.date", "ms.service")
+$articleRequiredFields = @("title", "description")
+$validTopics = @("article", "conceptual", "reference", "include", "hub-page", "overview", "release-notes", "quickstart", "tutorial")
+
+foreach ($file in $mdFiles) {
+    $relPath = [IO.Path]::GetRelativePath($repoRoot, $file) -replace '\\', '/'
+    $fileIssues = $false
+    $fileDir = Split-Path $file -Parent
+    $isApiRef = ($relPath -match '^playfab-docs/api-references/')
+
+    # Read file content (single read, derive both raw and lines)
+    try {
+        $lines = @(Get-Content $file -ErrorAction Stop)
+    } catch {
+        Add-Error $relPath 0 "FILE_READ_ERROR" "Could not read file: $($_.Exception.Message)"
+        continue
+    }
+    $rawContent = $lines -join "`n"
+
+    # --- 1. Frontmatter checks ---
+    $yaml = Get-Frontmatter $rawContent
+    if (-not $yaml) {
+        Add-Error $relPath 1 "MISSING_FRONTMATTER" "No YAML frontmatter found"
+        # Skip body checks — missing frontmatter causes noisy false positives
+        continue
+    } else {
+        # Read ms.topic first to determine which fields are required
+        $topicValue = Get-FrontmatterField $yaml "ms.topic"
+        $isInclude = ($topicValue -eq "include")
+
+        $fieldsToCheck = $alwaysRequiredFields
+        if (-not $isInclude) {
+            $fieldsToCheck = $alwaysRequiredFields + $articleRequiredFields
+        }
+
+        foreach ($field in $fieldsToCheck) {
+            $value = Get-FrontmatterField $yaml $field
+            if (-not $value) {
+                Add-Error $relPath 1 "MISSING_FIELD" "Required field '$field' is missing"
+                $fileIssues = $true
+            } elseif ($field -eq "ms.topic" -and $value -notin $validTopics) {
+                Add-Error $relPath 1 "INVALID_VALUE" "ms.topic '$value' is not valid (expected: $($validTopics -join ', '))"
+                $fileIssues = $true
+            } elseif ($field -eq "ms.service" -and $value -ne "azure-playfab") {
+                Add-Error $relPath 1 "INVALID_VALUE" "ms.service must be 'azure-playfab' (got '$value')"
+                $fileIssues = $true
+            } elseif ($field -eq "ms.date") {
+                $datePattern = '^(0?[1-9]|1[0-2])/(0?[1-9]|[12][0-9]|3[01])/\d{4}$'
+                if ($value -notmatch $datePattern) {
+                    Add-Error $relPath 1 "INVALID_FORMAT" "ms.date must be in MM/DD/YYYY format (got '$value')"
+                    $fileIssues = $true
+                } else {
+                    $parsedDate = [datetime]::MinValue
+                    if (-not [datetime]::TryParseExact($value, [string[]]@('M/d/yyyy','MM/dd/yyyy','M/dd/yyyy','MM/d/yyyy'), [System.Globalization.CultureInfo]::InvariantCulture, [System.Globalization.DateTimeStyles]::None, [ref]$parsedDate)) {
+                        Add-Error $relPath 1 "INVALID_DATE" "ms.date '$value' is not a valid calendar date"
+                        $fileIssues = $true
+                    }
+                }
+            } elseif ($field -eq "description" -and $value.Length -gt 160) {
+                if ($isApiRef) {
+                    Add-Warning $relPath 1 "TOO_LONG" "description must be 160 characters or fewer (got $($value.Length) characters)"
+                } else {
+                    Add-Error $relPath 1 "TOO_LONG" "description must be 160 characters or fewer (got $($value.Length) characters)"
+                }
+                $fileIssues = $true
+            }
+        }
+    }
+
+    # --- Get body (below frontmatter) ---
+    $inFrontmatter = $false
+    $frontmatterEnd = 0
+    for ($i = 0; $i -lt $lines.Count; $i++) {
+        if ($lines[$i] -match '^---\s*$') {
+            if (-not $inFrontmatter) { $inFrontmatter = $true }
+            else { $frontmatterEnd = $i + 1; break }
+        }
+    }
+
+    # If closing --- delimiter wasn't found, skip body checks to avoid noisy false positives
+    if ($frontmatterEnd -eq 0) {
+        if (-not $fileIssues) { $cleanFiles.Add($relPath) }
+        continue
+    }
+
+    # --- Body checks (single pass) ---
+    $inCodeBlock = $false
+    $codeFenceLen = 0
+    $codeFenceChar = ''
+    $h1Count = 0
+    $h1Text = $null
+    $h2Set = @{}
+    $lastHeadingLevel = 0
+    $titleValue = Get-FrontmatterField $yaml "title"
+
+    for ($i = $frontmatterEnd; $i -lt $lines.Count; $i++) {
+        $line = $lines[$i]
+
+        # --- Code fence toggle (handles 3+ backticks/tildes, with optional language suffix) ---
+        $fenceMatch = $rxCodeFence.Match($line)
+        if ($fenceMatch.Success) {
+            $fence = $fenceMatch.Groups[1].Value
+            if (-not $inCodeBlock) {
+                $inCodeBlock = $true
+                $codeFenceLen = $fence.Length
+                $codeFenceChar = $fence[0]
+                # Warn on bare code blocks (no language specifier)
+                $afterFence = $line.Substring($fenceMatch.Index + $fenceMatch.Length).Trim()
+                if (-not $afterFence) {
+                    Add-Warning $relPath ($i + 1) "BARE_CODE_BLOCK" "Code block has no language specifier — add one (e.g., ``````json, ``````csharp)"
+                    $fileIssues = $true
+                }
+            } elseif ($fence[0] -eq $codeFenceChar -and $fence.Length -ge $codeFenceLen) {
+                # Only close if same fence character and at least as many
+                $inCodeBlock = $false
+            }
+            continue
+        }
+        if ($inCodeBlock) { continue }
+
+        # --- Raw HTML detection (excluding <br> which is legitimate in Learn docs) ---
+        $htmlMatch = $rxRawHtml.Match($line)
+        if ($htmlMatch.Success) {
+            $tag = $htmlMatch.Groups[1].Value
+            Add-Error $relPath ($i + 1) "RAW_HTML" "HTML tag <$tag> is not permitted — use standard Markdown syntax"
+            $fileIssues = $true
+        }
+
+        # --- Missing alt-text ---
+        if ($rxEmptyAlt.IsMatch($line)) {
+            Add-Warning $relPath ($i + 1) "MISSING_ALT_TEXT" "Image has empty alt-text (needed for accessibility)"
+            $fileIssues = $true
+        }
+
+        # --- Image path validation ---
+        foreach ($im in $rxImageRef.Matches($line)) {
+            $imgPath = $im.Groups[2].Value.Trim()
+            if ($imgPath -match '^(https?://|data:)') { continue }
+            $imgPath = $imgPath -replace '[?#].*$', ''
+            $resolvedImg = [System.IO.Path]::GetFullPath((Join-Path $fileDir $imgPath))
+            if (-not (Test-PathCached $resolvedImg)) {
+                Add-Error $relPath ($i + 1) "BROKEN_IMAGE" "Image file not found: $($im.Groups[2].Value)"
+                $fileIssues = $true
+            }
+        }
+
+        # --- Heading structure ---
+        $headingMatch = $rxHeading.Match($line)
+        if ($headingMatch.Success) {
+            $level = $headingMatch.Groups[1].Value.Length
+            $text = $headingMatch.Groups[2].Value.Trim()
+
+            if ($level -eq 1) {
+                $h1Count++
+                if ($h1Count -eq 1) { $h1Text = $text }
+                if ($h1Count -gt 1) {
+                    Add-Error $relPath ($i + 1) "DUPLICATE_H1" "Multiple H1 headings found"
+                    $fileIssues = $true
+                }
+            }
+            if ($level -eq 2) {
+                if ($h2Set.ContainsKey($text)) {
+                    Add-Warning $relPath ($i + 1) "DUPLICATE_H2" "Duplicate H2 heading: '$text'"
+                    $fileIssues = $true
+                }
+                $h2Set[$text] = $true
+            }
+            if ($lastHeadingLevel -gt 0 -and $level -gt $lastHeadingLevel + 1) {
+                Add-Warning $relPath ($i + 1) "HEADING_SKIP" "Heading level skipped: H$lastHeadingLevel to H$level"
+                $fileIssues = $true
+            }
+            $lastHeadingLevel = $level
+        }
+
+        # --- Cross-repo .md extension check ---
+        if ($rxCrossRepoMd.IsMatch($line)) {
+            Add-Warning $relPath ($i + 1) "CROSS_REPO_MD_EXTENSION" "Cross-repo link should not end with .md"
+            $fileIssues = $true
+        }
+
+        # --- Broken internal links ---
+        foreach ($lm in $rxMdLink.Matches($line)) {
+            $linkTarget = $lm.Groups[2].Value.Trim()
+            # Skip external URLs, xref links, mailto, anchors-only
+            if ($linkTarget -match '^(https?://|xref:|mailto:|#)') { continue }
+            # Skip Learn extensions like [!INCLUDE, [!NOTE, [!div
+            if ($lm.Groups[1].Value -match '^!') { continue }
+            # Only check .md links
+            if ($linkTarget -notmatch '\.md(\?|#|$)') { continue }
+            # Strip anchor and query string
+            $linkPath = $linkTarget -replace '[?#].*$', ''
+            $resolvedPath = [System.IO.Path]::GetFullPath((Join-Path $fileDir $linkPath))
+            if (-not (Test-PathCached $resolvedPath)) {
+                Add-Error $relPath ($i + 1) "BROKEN_INTERNAL_LINK" "File not found: $linkTarget"
+                $fileIssues = $true
+            }
+        }
+
+        # --- Include reference validation ---
+        $includeMatch = $rxInclude.Match($line)
+        if ($includeMatch.Success) {
+            $includePath = $includeMatch.Groups[1].Value
+            $resolvedInclude = [System.IO.Path]::GetFullPath((Join-Path $fileDir $includePath))
+            if (-not (Test-PathCached $resolvedInclude)) {
+                Add-Error $relPath ($i + 1) "BROKEN_INCLUDE" "Include file not found: $includePath"
+                $fileIssues = $true
+            }
+        }
+
+        # --- Writing style checks (skip blockquote/alert lines and strip inline code) ---
+        $isBlockquote = $line -match '^\s*>'
+        if (-not $isBlockquote) {
+            $styleLine = $rxInlineCode.Replace($line, '')
+
+            if ($rxLatinAbbrev.IsMatch($styleLine)) {
+                $abbr = $rxLatinAbbrev.Match($styleLine).Value
+                Add-Warning $relPath ($i + 1) "LATIN_ABBREVIATION" "Avoid '$abbr' — use 'for example,', 'that is,', 'and so on', or 'compared to'"
+                $fileIssues = $true
+            }
+
+            if ($rxSpacedEmDash.IsMatch($styleLine)) {
+                Add-Warning $relPath ($i + 1) "SPACED_EM_DASH" "Remove spaces around em dashes — use 'word—word' not 'word — word'"
+                $fileIssues = $true
+            }
+
+            if ($rxFiller.IsMatch($styleLine)) {
+                $word = $rxFiller.Match($styleLine).Groups[1].Value
+                Add-Warning $relPath ($i + 1) "FILLER_WORD" "Avoid filler word '$word'"
+                $fileIssues = $true
+            }
+
+            if ($rxContraction.IsMatch($styleLine)) {
+                $phrase = $rxContraction.Match($styleLine).Groups[1].Value
+                Add-Warning $relPath ($i + 1) "MISSING_CONTRACTION" "Use a contraction instead of '$phrase'"
+                $fileIssues = $true
+            }
+
+            if ($rxHyphenPrefix.IsMatch($styleLine)) {
+                $hpMatch = $rxHyphenPrefix.Match($styleLine)
+                $word = $hpMatch.Value
+                $corrected = $word -replace '-', ''
+                Add-Warning $relPath ($i + 1) "HYPHENATED_PREFIX" "Remove hyphen — use '$corrected' instead of '$word'"
+                $fileIssues = $true
+            }
+        }
+    }
+
+    # --- H1 vs title match (after full scan) ---
+    if ($titleValue -and $h1Text -and $h1Text -ne $titleValue) {
+        Add-Warning $relPath 0 "H1_TITLE_MISMATCH" "H1 heading '$h1Text' does not match frontmatter title '$titleValue'"
+        $fileIssues = $true
+    }
+
+    if (-not $fileIssues) { $cleanFiles.Add($relPath) }
+}
+
+# --- Validate TOC files ---
+
+foreach ($tocFile in $tocFiles) {
+    $relPath = [IO.Path]::GetRelativePath($repoRoot, $tocFile) -replace '\\', '/'
+    $tocDir = Split-Path $tocFile -Parent
+    $fileIssues = $false
+    $tocLines = Get-Content $tocFile
+
+    for ($i = 0; $i -lt $tocLines.Count; $i++) {
+        if ($tocLines[$i] -match 'href:\s*(.+)\s*$') {
+            $href = $Matches[1].Trim().Trim('"').Trim("'")
+            # Strip inline YAML comments (# preceded by whitespace)
+            $href = $href -replace '\s+#.*$', ''
+            # Strip fragment identifiers
+            $href = $href -replace '#.*$', ''
+
+            # Skip external URLs, mailto, and other protocol links
+            if ($href -match '^https?://') { continue }
+            if ($href -match '^[a-zA-Z]+:') { continue }
+            # Skip fragment-only links (href was just #anchor, now empty after strip)
+            if (-not $href -or $href -match '^#') { continue }
+
+            # Normalize path separators in href to be OS-agnostic
+            $normalizedHref = $href -replace '\\', '/'
+
+            # Handle absolute paths
+            if ($normalizedHref.StartsWith('/')) {
+                # Only validate paths under /playfab-docs/ — others are cross-repo Learn references
+                if ($normalizedHref -notmatch '^/playfab-docs/') { continue }
+                $targetPath = Join-Path $repoRoot $normalizedHref.TrimStart('/')
+            } else {
+                $targetPath = Join-Path $tocDir $normalizedHref
+            }
+
+            # Validate .md and .yml files exist on disk
+            $ext = [System.IO.Path]::GetExtension($normalizedHref).ToLowerInvariant()
+            if ($ext -in @('.md', '.yml')) {
+                $targetPath = [System.IO.Path]::GetFullPath($targetPath)
+                if (-not (Test-PathCached $targetPath)) {
+                    Add-Error $relPath ($i + 1) "BROKEN_TOC_LINK" "File not found: $href"
+                    $fileIssues = $true
+                }
+            }
+        }
+    }
+
+    if (-not $fileIssues) { $cleanFiles.Add($relPath) }
+}
+
+# --- Detect orphaned redirect files ---
+
+$redirectFile = Join-Path $repoRoot ".openpublishing.redirection.json"
+if (Test-Path $redirectFile) {
+    try {
+        $redirectData = Get-Content $redirectFile -Raw | ConvertFrom-Json
+        foreach ($redir in $redirectData.redirections) {
+            $sourcePath = $redir.source_path
+            if (-not $sourcePath) { continue }
+            $fullSource = Join-Path $repoRoot ($sourcePath -replace '/', [IO.Path]::DirectorySeparatorChar)
+            if (Test-Path $fullSource) {
+                $relSource = $sourcePath -replace '\\', '/'
+                Add-Warning $relSource 0 "ORPHANED_REDIRECT" "File still exists but is listed in .openpublishing.redirection.json — consider deleting it"
+            }
+        }
+    } catch {
+        Write-Warning "Could not parse .openpublishing.redirection.json: $($_.Exception.Message)"
+    }
+}
+
+# --- Report ---
+
+$totalFiles = $mdFiles.Count + $tocFiles.Count
+$totalIssues = $errors.Count + $warnings.Count
+
+Write-Host ""
+Write-Host "=======================================" -ForegroundColor Cyan
+Write-Host " PlayFab Docs Validation Report" -ForegroundColor Cyan
+Write-Host "=======================================" -ForegroundColor Cyan
+Write-Host ""
+Write-Host "Files reviewed: $totalFiles ($($mdFiles.Count) markdown, $($tocFiles.Count) TOC)"
+Write-Host "Issues found:   $totalIssues ($($errors.Count) errors, $($warnings.Count) warnings)"
+Write-Host ""
+
+if ($errors.Count -gt 0) {
+    Write-Host "--- ERRORS (must fix) ---" -ForegroundColor Red
+    $grouped = $errors | Group-Object File
+    foreach ($group in $grouped) {
+        Write-Host "  $($group.Name)" -ForegroundColor White
+        foreach ($issue in $group.Group) {
+            $lineStr = if ($issue.Line -gt 0) { "line $($issue.Line)" } else { "" }
+            Write-Host "    X $($issue.Check) ($lineStr): $($issue.Message)" -ForegroundColor Red
+        }
+    }
+    Write-Host ""
+}
+
+if ($warnings.Count -gt 0) {
+    Write-Host "--- WARNINGS (should fix) ---" -ForegroundColor Yellow
+    $grouped = $warnings | Group-Object File
+    foreach ($group in $grouped) {
+        Write-Host "  $($group.Name)" -ForegroundColor White
+        foreach ($issue in $group.Group) {
+            $lineStr = if ($issue.Line -gt 0) { "line $($issue.Line)" } else { "" }
+            Write-Host "    ! $($issue.Check) ($lineStr): $($issue.Message)" -ForegroundColor Yellow
+        }
+    }
+    Write-Host ""
+}
+
+if ($cleanFiles.Count -gt 0) {
+    Write-Host "--- CLEAN FILES ---" -ForegroundColor Green
+    foreach ($f in $cleanFiles) {
+        Write-Host "    OK $f" -ForegroundColor Green
+    }
+    Write-Host ""
+}
+
+# Exit code
+if ($errors.Count -gt 0) {
+    Write-Host "RESULT: FAILED ($($errors.Count) errors)" -ForegroundColor Red
+    exit 1
+} elseif ($warnings.Count -gt 0) {
+    Write-Host "RESULT: PASSED WITH WARNINGS ($($warnings.Count) warnings)" -ForegroundColor Yellow
+    exit 0
+} else {
+    Write-Host "RESULT: PASSED" -ForegroundColor Green
+    exit 0
+}
+
+} finally { Pop-Location } # matches Push-Location at script start