[No QA] Update View-the-Top-Categories-report.md#81473
[No QA] Update View-the-Top-Categories-report.md#81473stephanieelliott merged 1 commit intostephanieelliott-patch-31from
Conversation
stephanieelliott
merged commit ba937e8
into
stephanieelliott-patch-31
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| ## How to interpret the Top Categories report | ||
|
|
||
| Each row represents a single expense category, sorted in descending order by total spend. Columns include: | ||
| Each category entry represents a single expense category, ordered from highest to lowest total spend. The report shows: |
There was a problem hiding this comment.
Readability violation: "ordered from highest to lowest total spend" is unnecessarily verbose. The original phrase "sorted in descending order" is more concise and clearer. Simplify to maintain scannability.
| - **Total amount spent** in that category | ||
|
|
||
| Click any row to view all expenses tied to that category. | ||
| Select a category to review all expenses included in that grouping. |
There was a problem hiding this comment.
Readability violation: "Select a category to review all expenses included in that grouping" is unnecessarily wordy. "Grouping" is vague corporate jargon. The original "Click any row to view all expenses tied to that category" was clearer and more direct.
|
|
||
| ## How to switch the Top Categories report to table view | ||
|
|
||
| By default, the Top Categories report displays a bar chart. The table view shows expense categories sorted in descending order by total spend. |
There was a problem hiding this comment.
Readability violation: This sentence repeats information that was just stated in the previous sentence. The second sentence "The table view shows expense categories sorted in descending order by total spend" is redundant - this was already explained in line 50. Remove the duplicate information.
| 1. Click **View** in the top navigation tabs. | ||
| 2. Select **Table**. | ||
|
|
||
| The table view shows expense categories as rows sorted in descending order by total spend. |
There was a problem hiding this comment.
Readability violation: This sentence duplicates information already provided in the introduction (line 77). The explanation of what table view shows is repeated three times in this section. Remove this redundant sentence to improve clarity and scannability.
|
|
||
| --- | ||
|
|
||
| ## How to switch the Top Categories report to table view |
There was a problem hiding this comment.
AI Readiness violation: Heading uses vague pronoun "the Top Categories report" when it should be more descriptive. Consider: "How to switch Top Categories from chart to table view" or "How to view Top Categories as a table" for better AI parsing and user clarity.
HelpDot Documentation ReviewOverall AssessmentThis PR introduces minor improvements to the Top Categories report documentation by refining language for clarity and adding a new section on switching to table view. The changes are generally well-written but contain some style and consistency issues that impact overall quality. Scores Summary
Key FindingsPositive Aspects:
Issues Identified:
RecommendationsPriority Actions:
Suggestions for Enhancement:
Files Reviewed
Note: This PR has already been merged. Recommendations apply to future documentation updates for this file. |
github-actions
bot
changed the title
|
A preview of your ExpensifyHelp changes have been deployed to https://72514168.helpdot.pages.dev ⚡️ Updated articles: |
|
🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.18-0 🚀
|
|
🚀 Deployed to production by https://github.com/lakchote in version: 9.3.18-8 🚀
|
2 participants
Explanation of Change
Fixed Issues
$
PROPOSAL:
Tests
Offline tests
QA Steps
// TODO: These must be filled out, or the issue title must include "[No QA]."
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectioncanBeMissingparam foruseOnyxtoggleReportand notonIconClick)src/languages/*files and using the translation methodSTYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))npm run compress-svg)Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari