[No QA] Update Chat-Features-and-Moderation-Tools.md

[brianlee-expensify]

Explanation of Change

Fixed Issues

$
PROPOSAL:

Tests

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

• Verify that no errors appear in the JS console

PR Author Checklist

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://872ed186.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/chat/Chat-Features-and-Moderation-Tools

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes three small wording changes in the "Leave a Chat Room" section of the Chat Features and Moderation Tools article. Two changes improve terminology consistency ("room" to "chat room"), and one replaces a prohibited UI reference ("Click the 3-dot menu in the top right") with a more accurate instruction ("Click the chat room header"). The changes are directionally positive and address a real governance violation, though one introduces a minor new concern.

Scores Summary

• Readability: 8/10 - The revised steps are clear, concise, and easy to follow. The consistent use of "chat room" improves scannability and reduces ambiguity.
• AI Readiness: 6/10 - The changes themselves do not affect metadata, heading structure, or retrieval optimization. The section heading "# Leave a Chat Room" is already task-based which is good, though it uses a # heading in violation of the single-#-title rule (pre-existing issue, not introduced by this PR).
• Style Compliance: 7/10 - The removal of "3-dot menu" is a clear improvement against the prohibited language list. However, the replacement instruction "Click the chat room header" should be verified against the actual UI flow to ensure it is accurate and deterministic per the naming conventions. Additionally, step 2 still uses "Click" as the verb -- governance does not prohibit "Click," but consistency with the rest of the article and the three-dots convention (which uses "Select") would be worth considering.

Key Findings

• Positive: The PR removes a prohibited phrase ("Click the 3-dot menu") from step 2, which directly violates the Three Dots Menu Rule in HELPSITE_NAMING_CONVENTIONS.md. This is a meaningful compliance improvement.
• Positive: Changing "room" to "chat room" in two places improves consistency and specificity, aligning with the deterministic writing rule (be literal, be exact, be consistent).
• Note: The replacement instruction "Click the chat room header" is a different UI path than the original "Click the 3-dot menu in the top right." This is not just a phrasing fix but a change in the described user flow. The reviewer should confirm this accurately reflects the current UI behavior for reaching the Leave option.
• Pre-existing: Line 120 in the file still contains "Click the 3-dot menu" in the Flag section, which remains a governance violation. This was not introduced by this PR, but it represents an opportunity for a follow-up fix.

Recommendations

1. Verify UI accuracy: Confirm that clicking the chat room header is the correct path to reach the Leave option in the current product UI. If the three-dots menu is still involved, the step should instead use the governed format: Select the three dots **(⋮)**.
2. Consider a follow-up PR: The same file has another instance of the prohibited "3-dot menu" phrasing at line 120 (in the Flag section). A follow-up PR to address that would bring the full article closer to compliance.

Files Reviewed

• docs/articles/new-expensify/chat/Chat-Features-and-Moderation-Tools.md - 3 lines changed. Terminology improvement and prohibited phrase removal. Verify UI accuracy of new step 2.

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.4.0-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.0-7 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅