[No QA] make copy less wordy for help doc article

[blimpich]

Explanation of Change

Fixed Issues

$ n/a
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

[OSBotify]

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

Updated articles:

• articles/new-expensify/connections/netsuite/Configure-Netsuite

[github-actions]

HelpDot Documentation Review

Overall Assessment
This PR is a focused copy edit to a single bullet in Configure NetSuite (docs/articles/new-expensify/connections/netsuite/Configure-Netsuite.md). It trims two redundant "Consolidated Travel Billing" qualifiers from the Sync Consolidated Travel Billing Settlements description: "reconcile Consolidated Travel Billing settlements" becomes "reconcile settlements," and "Consolidated Travel Billing settlement account" becomes "settlement account." The feature name is already established earlier in the same sentence, so the change reduces wordiness without losing meaning. Scoped purely on the diff.

Scores Summary

• Readability: 9/10 - The edit improves concision and flow; the leading clause already names the feature, so dropping the repeated qualifiers makes the sentence easier to scan.
• AI Readiness: 8/10 - The full feature name still appears at the start of the bullet, preserving semantic retrieval. No metadata, headings, or hierarchy were touched, so retrieval signal is unchanged.
• Style Compliance: 9/10 - UI labels (Sync Consolidated Travel Billing Settlements, Reconciliation account) remain exact and bolded per naming conventions. The change does not introduce vague or prohibited language.

Key Findings

• Clean, low-risk concision edit that follows the "be concise and actionable" core principle.
• Full feature name is retained once at the start of the bullet, so discoverability is not weakened by the trimming.
• No regressions introduced: UI terminology, bolding, and toggle references all stay compliant.
• Note (pre-existing, not introduced by this PR): the surrounding file uses multiple top-level headings (Step 1/2/3) and "Step N" phrasing, which conflicts with the single-title and task-based heading rules. Out of scope for this diff and should not block it.

Recommendations

• Approve as a clean copy edit; no changes required for the proposed diff.
• Optional follow-up (separate PR): address the file structural heading issues to bring it fully in line with the authoring guidelines.

Files Reviewed

• docs/articles/new-expensify/connections/netsuite/Configure-Netsuite.md - Single-line copy edit; compliant and improves readability.

Note: Detailed line-by-line feedback has been provided as inline comments.