Skip to content

[No QA] Update Book-a-Hotel.md#79064

Merged
stephanieelliott merged 1 commit into
stephanieelliott-patch-22from
stephanieelliott-patch-22-1
Jan 8, 2026
Merged

[No QA] Update Book-a-Hotel.md#79064
stephanieelliott merged 1 commit into
stephanieelliott-patch-22from
stephanieelliott-patch-22-1

Conversation

@stephanieelliott

Copy link
Copy Markdown
Contributor

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

  • 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: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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 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 used JaimeGPT to get English > Spanish translation. I then posted it 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • 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.ts 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 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(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • 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.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • 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.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@stephanieelliott
stephanieelliott requested a review from a team as a code owner January 8, 2026 04:17
@melvin-bot

melvin-bot Bot commented Jan 8, 2026

Copy link
Copy Markdown

Concierge reviewer checklist:

  • I have verified the accuracy of the article
    • The article is within a hub that makes sense, and the navigation is correct
    • All processes, screenshots, and examples align with current product behavior.
    • All links within the doc have been verified for correct destination and functionality.
  • I have verified the readability of the article
    • The article's language is clear, concise, and free of jargon.
    • The grammar, spelling, and punctuation are correct.
    • The article contains at least one image, or that an image is not necessary
  • I have verified the formatting of the article
    • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
    • The article has proper text spacing and breaks for readability.
  • I have verified the article has the appropriate tone and style
    • The article's tone is professional, friendly, and suitable for the target audience.
    • The article's tone, terminology, and voice are consistent throughout.
  • I have verified the overall quality of the article
    • The article is not missing any information, nor does it contain redundant information.
    • The article fully addresses user needs.
  • I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @twisterdotcom

@melvin-bot
melvin-bot Bot requested a review from twisterdotcom January 8, 2026 04:17
@melvin-bot

melvin-bot Bot commented Jan 8, 2026

Copy link
Copy Markdown

@twisterdotcom Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot removed the request for review from a team January 8, 2026 04:17
@stephanieelliott
stephanieelliott merged commit e33761f into stephanieelliott-patch-22 Jan 8, 2026
14 of 17 checks passed
@stephanieelliott
stephanieelliott deleted the stephanieelliott-patch-22-1 branch January 8, 2026 04:17

# How to search and book a hotel
# How to book a hotel

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heading level violation: This should be ## (H2) instead of # (H1). Only the article title at the top should use H1. All major sections should use H2 (##).

<div id="new-expensify" markdown="1">

Book hotels easily using Expensify’s integrated travel tool. This guide covers how to search for hotels, filter options, complete your booking, and view your travel details in New Expensify.
Book hotels easily with Expensify Travel. This guide covers how to search for hotels, filter options, complete your booking, and view your travel details in New Expensify.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Readiness violation: Remove this introductory sentence. The article should start directly with the first H2 section. Introductory summaries should be in the YAML description field only (which is already present).

To modify or cancel a booking:
1. Tap the green ➕ **Create** button at the bottom of your screen, then choose **Book travel**.
2. In the window that opens, click the **Trips** tab.
3. Find your trip and click **Modify or Cancel**

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Readiness violation: The answer "It will be SmartScanned and added to your next report automatically" uses the pronoun "It" without clear context. Start with the subject: "The hotel receipt will be SmartScanned and added to your next report automatically."

@github-actions

github-actions Bot commented Jan 8, 2026

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR updates the "Book a Hotel" documentation with improved clarity and consistency. The changes streamline navigation instructions, modernize terminology, and enhance the user experience. The updates are well-aligned with New Expensify's current interface patterns.

Scores Summary

  • Readability: 8/10 - Clear, concise language with improved flow. Minor inconsistencies in heading hierarchy and a few formatting choices could be refined.
  • AI Readiness: 7/10 - Good descriptive headings and clear context. Could benefit from more specific feature names in headings and consistent navigation terminology.
  • Style Compliance: 8/10 - Good adherence to Expensify voice with proper terminology (workspace, Workspace Admin). Some minor terminology inconsistencies remain.

Key Findings

Positive Aspects:

  • Simplified and modernized language ("Book hotels easily with Expensify Travel" vs. the wordier original)
  • More specific navigation instructions using the ➕ Create button pattern
  • Improved help-seeking guidance directing users to Workspace Admins rather than Account Managers
  • Better clarity in post-booking instructions ("upload the final bill manually" vs. "you'll need to upload")
  • Enhanced "What if my plans change?" section with detailed step-by-step instructions

Issues Identified:

  1. Heading Hierarchy Inconsistency: The document uses both H1 (#) and H2 (##) for top-level sections. HelpDot standard is to use only H1 and H2, but mixing them at the same level creates confusion. Example: "# How to book a hotel" followed later by "## What happens after booking with Expensify Travel"
  2. Incomplete Update: Line 9 (intro paragraph) wasn't updated to match the simplified language used in the heading changes
  3. Terminology Inconsistency: "Expensify Travel" vs. "the travel tool" vs. "booking tool" - should standardize throughout
  4. Metadata Not Updated: The description field (line 3) still refers to "Expensify's integrated travel tool" but the content now says "Expensify Travel"

Recommendations

Priority Actions:

  1. Standardize heading levels: Choose either H1 or H2 for all main sections (recommend H2 for consistency with "## Where to find Expensify Travel")
  2. Update the intro paragraph (line 9) to match the simplified language: "Book hotels easily with Expensify Travel..."
  3. Standardize terminology: Use "Expensify Travel" consistently throughout instead of mixing with "travel tool" and "booking tool"
  4. Update YAML metadata: Change description to reference "Expensify Travel" for consistency

Suggestions for Enhancement:

  • Consider making FAQ headings more descriptive for AI discoverability (e.g., "## Can I choose specific hotel brands when booking?" instead of "## Can I choose specific hotel brands?")
  • The "Book travel" button label could be more explicit in the first section heading

Files Reviewed

  • docs/articles/travel/booking-travel/Book-a-Hotel.md: Good improvements with minor consistency issues to address

Overall Verdict: Strong documentation update that improves user experience. Addressing the heading hierarchy and terminology consistency issues would elevate this to excellent quality.

Book hotels easily with Expensify Travel. This guide covers how to search for hotels, filter options, complete your booking, and view your travel details in New Expensify.

# How to access the travel tool
## Where to find Expensify Travel

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Readiness improvement: Good change to H2! However, consider making the heading more specific by including "Expensify Travel" in the heading for better AI context. Suggestion: "## Where to find the Expensify Travel booking tool"


From the left-hand menu, select **Reports > Trips**.
Click the green **+** button in the bottom-left corner, then choose **Book travel**.
Tap the green ➕ **Create** button at the bottom of your screen, then choose **Book travel**.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Readability violation: The instruction says "Tap the green ➕ Create button" but previously it was "Click the green + button". Ensure consistency - is this for mobile (tap) or desktop (click)? If it works on both, use "Click" as it's more universal, or specify the platform.

Tap the green ➕ **Create** button at the bottom of your screen, then choose **Book travel**.

If you don’t see this option, reach out to your Account Manager or Concierge to schedule a travel demo and enable the feature for your account.
If you don’t see **Book travel**, ask a Workspace Admin to [enable Expensify Travel](https://help.expensify.com/articles/travel/company-setup/Enable-Travel-on-a-Workspace) on the workspace.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Terminology violation: Use "workspace" instead of "the workspace". Also consider capitalizing "Workspace Admin" for consistency with Expensify terminology: "ask a Workspace Admin to enable Expensify Travel on your workspace."


# What happens next
## What happens after booking with Expensify Travel

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Readiness violation: The heading "What happens after booking with Expensify Travel" is verbose. Consider shortening while maintaining clarity: "## After booking" or "## What happens after booking"

- You’ll receive a confirmation email after booking.
- The hotel receipt will automatically be added to your Expensify account.
- Note: If your hotel booking is post-paid, then you'll need to upload your final hotel bill to your Expensify account instead.
- If your hotel is post-paid, upload the final bill manually to your Expensify account after checkout.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Readability improvement: Good simplification! However, "upload the final bill manually" is slightly redundant - "upload" already implies manual action. Consider: "upload the final bill to your Expensify account after checkout."


You can cancel or modify your booking if the hotel’s policy allows it.
You can cancel or modify the booking if the hotel’s policy allows.
Cancellation policies are shown during booking. Changes made via support incur a $25 booking change fee.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Readability violation: Remove "the" before "booking" - it reads more naturally as: "You can cancel or modify your booking if the hotel's policy allows."


Manage bookings by going to **Reports > Trips > My Trips**.
To modify or cancel a booking:
1. Tap the green ➕ **Create** button at the bottom of your screen, then choose **Book travel**.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Readability violation: Inconsistent terminology - earlier the instructions said "Tap" but here it says "Tap" again, and then "click" in step 3. Standardize to either "Click" throughout (for cross-platform) or specify when to use "Tap" vs "Click".

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@IuliiaHerets

Copy link
Copy Markdown

@stephanieelliott, if we need to QA this, please add a repro steps

@twisterdotcom twisterdotcom changed the title Update Book-a-Hotel.md [No QA] Update Book-a-Hotel.md Jan 20, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Beamanator in version: 9.3.5-7 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants