Adviser, Advisor, and the Cost of One Letter

SECTION 01

Treat the statutory spelling as a domain token

The portal uses “investment adviser” as its canonical UI and federal/NASAA term while preserving Virginia Code's “investment advisor” when state statutory language is named or quoted.

Spelling becomes architecture when it names a regulated actor. The repository consistently uses adviser in product identity, module identifiers, and general federal/NASAA-oriented UI copy. That choice follows the Investment Advisers Act and Uniform Investment Adviser Law Examination vocabulary; it is not a claim that advisor is invalid or merely informal. Virginia Code § 13.1-501 itself defines “investment advisor” and “investment advisor representative,” while also referring to the federal Investment Advisers Act and a federal covered advisor.

The useful rule is therefore jurisdiction-aware, not a global search-and-replace: use adviser for canonical portal copy and federal/NASAA terminology; preserve advisor when naming, quoting, or closely tracking Virginia statutory terminology; and preserve every authority's exact title. A content editor should never silently normalize one legislature's term into another spelling, because the altered language becomes harder to trace back to primary authority.

SECTION 02

Encode the distinction in authoring, not in memory

A typed content system can make terminology review mechanical while leaving room for legitimate source quotations and synonym explanations.

The curriculum graph separates machine identifiers from display text. Identifiers such as series65-adviser-regulation remain stable even if a heading is refined, while citations carry the exact title and jurisdiction of their authority. That separation prevents a copy edit from breaking database relationships, routes, or assessment templates. It also lets validation flag suspicious uses in learner-facing text without rewriting source metadata.

A practical editorial check tokenizes prose outside URLs and citations, reports advisor occurrences, and asks for an explicit disposition: synonym explanation, verbatim title, or correction. Reporting is safer than unconditional mutation because the word can be intentional. The same review should reject compound claims such as licensed adviser unless the specific registration context supports them; completing a curriculum or passing a practice threshold never confers a regulatory status.

const alternateSpelling = /\badvisor(?:s|y)?\b/gi;

function terminologyFlags(copy: string) {
  return [...copy.matchAll(alternateSpelling)].map(({ 0: token, index }) => ({
    token,
    index,
    dispositionRequired: true,
  }));
}

SECTION 03

Normalize discovery while preserving display fidelity

Search can equate adviser and advisor without collapsing the stored vocabulary that citations, routes, and reports depend on.

Search normalization belongs at the query boundary. A request for advisor regulation can expand to both spellings, while the result card continues to display the authored adviser wording. The index should retain the original field alongside a normalized search field so excerpts remain faithful. This design also keeps analytics honest: the application can record the submitted query token without fragmenting content identifiers into two near-duplicate taxonomies.

Do not normalize whole source records. URLs, citations, titles, and quoted passages are evidence and should be immutable once included in a published release. If an authority changes its preferred language, that is a source revision with a verification date, not a reason to mutate every historical session snapshot. The difference matters because a learner's completed session must remain reviewable against the content actually delivered at that time.

SECTION 04

Make the editorial contract testable

Terminology quality comes from small, repeatable assertions across authored copy, metadata, and user-state labels.

A release check should verify three independent properties: legal titles have not been paraphrased, canonical product copy uses adviser, and every credential-like phrase carries an educational limitation where needed. Tests should inspect structured fields rather than rendered HTML so a future design does not weaken the policy. The same rules can run before content export and again against the published database representation.

This is also why the series begins with language rather than infrastructure. Once a term becomes a route slug, concept identifier, database value, test locator, or analytics dimension, changing it is a migration. Establishing the domain lexicon early reduces that cost and makes later technical articles precise: adviser is a regulated-domain term, RIAexam.com is the application, and advisor remains a discoverable English variant rather than a competing model object.

• Keep source titles and quoted language exact.
• Keep identifiers stable across copy revisions.
• Expand synonyms at retrieval boundaries, not inside evidence records.
• Pair educational roles and progress labels with explicit non-credential guardrails.