Skip to content

[No QA] [NO QA] Update Book-a-Flight.md #90563

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stephanieelliott merged 1 commit into from
May 15, 2026
+1 −1
Merged

[No QA] [NO QA] Update Book-a-Flight.md #90563

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/articles/travel/booking-travel/Book-a-Flight.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ If you don’t see **Book travel**, ask a Workspace Admin to [enable Expensify T
## What happens after booking with Expensify Travel

- Your company’s travel policy may require approval before final confirmation.
- You’ll receive a confirmation email after booking.
- You’ll receive a confirmation email that includes the relevant booking details.
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot May 15, 2026

Choose a reason for hiding this comment

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

The changed line itself looks good -- no governance violations.

However, this file has several pre-existing issues worth addressing (not introduced by this PR):

  1. Extra # heading (line 20): # How to book a flight should be ## How to book a flight -- only one # heading (the article title) is allowed, plus the optional # FAQ. (HELP_AUTHORING_GUIDELINES.md Section 4)

  2. Missing internalScope in YAML frontmatter (lines 1-5): The metadata block is missing the required internalScope field. (HELP_AUTHORING_GUIDELINES.md Section 3, TEMPLATE.md)

  3. Non-task-based heading (line 39): ## What happens after booking with Expensify Travel does not start with a question word applied to the user. Consider: ## What happens after you book with Expensify Travel. (HELP_AUTHORING_GUIDELINES.md Section 2)

  4. Full URLs instead of relative links (lines 17, 51): Cross-links must use relative paths, not full URLs like https://help.expensify.com/... or https://docs.expensify.com. (HELP_AUTHORING_GUIDELINES.md Section 7)

  5. Link inside numbered steps (line 17): The link to enable Expensify Travel appears adjacent to navigation steps. Links should not be placed inside procedural step instructions. (HELP_AUTHORING_GUIDELINES.md Section 7)

- The booking receipt will automatically sync with your Expensify account.
- If your card is connected to Expensify, the receipt will merge with the credit card expense.

Expand Down
Loading