QUA-1806: Clean up Enrichment Datastore FAQ and remove internal flag

[RafaelOsiro]

Overview

Refines the Datastore Enrichment FAQ. Engineering flagged an internal flag exposed in the "Which connectors support enrichment?" answer; this PR removes that detail and aligns the rest of the page with our writing standards (no em-dashes, plain-language wording, consistent bold for UI values).

Key Changes

• Remove internal flag: rewrote the "Which connectors support enrichment?" answer to drop the internal flag and the "write-back capabilities" jargon, pointing readers to the Supported Enrichment Datastores list instead.
• Em-dash cleanup: replaced em-dashes with periods, commas, semicolons, or colons across the linking, settings, unlinking, storage, operations, troubleshooting, and API sections.
• Wording polish: tightened the "Maximum Source Examples per Anomaly" entry, reworded the Scan flow bullet to mention records written to dedicated enrichment tables, and standardized None as None in remediation references.
• Alignment fixes: aligned the troubleshooting prefix-conflict bullet with the existing prefix-uniqueness wording, and added a note in the post-unlink cleanup answer about per-container tables that remain under Append/Overwrite remediation.

Pages to Test

• http://localhost:8000/source-datastore/enrichment-datastore/faq/

[greptile-apps]

Greptile Summary

This PR cleans up the Enrichment Datastore FAQ page: it removes an exposed internal implementation flag (enrichment_only=true and "write-back capabilities" jargon) from the connector-support answer, replaces all em-dashes with standard punctuation throughout, and standardises bold formatting for UI values such as None.

• The "Which connectors support enrichment?" answer now describes support in plain terms ("Many JDBC connectors and all cloud object storage (DFS) connectors") and defers to the Supported Enrichment Datastores reference page.
• The post-unlink cleanup answer gains a new sentence noting that Append/Overwrite remediation leaves behind per-container tables; and the Scan flow step 4 is reworded from "source tables are replicated" to "records are written to dedicated enrichment tables" for accuracy.
• The range 1 to 1,000,000,000 is dropped from the Maximum Source Examples entry, and a new undefined term ("anomalous source container") appears in the cleanup section.

Confidence Score: 4/5

Documentation-only change that removes an internal implementation detail and standardises formatting; safe to merge with minor wording observations.

The change is purely editorial — no code, no schema, no API contract is altered. The removal of the valid input range for "Maximum Source Examples per Anomaly" and the introduction of the undefined term "anomalous source container" are small wording gaps that could leave users without enough context, but neither causes incorrect information to be published.

docs/source-datastore/enrichment-datastore/faq.md — the two small wording gaps noted in comments (undefined "container" term and removed range) are worth a quick second read.

Important Files Changed

Filename	Overview
docs/source-datastore/enrichment-datastore/faq.md	Documentation-only cleanup: removes internal enrichment_only=true flag, replaces all em-dashes with appropriate punctuation, standardises bold for UI values, and adds a note about per-container tables left behind after Append/Overwrite remediation. One new sentence introduces the term "anomalous source container" without a definition anchor.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Source Datastore] -->|Link| B[Enrichment Datastore]
    A -->|Scan| C{Remediation Strategy}
    C -->|None| D[Anomaly metadata only stored in Qualytics]
    C -->|Append| E[Source records appended to dedicated enrichment tables]
    C -->|Overwrite| F[Enrichment tables replaced with latest anomalous records]
    E --> G[Per-container tables remain after unlinking]
    F --> G
    A -->|Unlink| H[Connection severed, data preserved in enrichment datastore]
    H --> I[Manual cleanup required via database tools]

Loading

_{Reviews (1): Last reviewed commit: "docs(enrichment-faq): remove internal fl..." | Re-trigger Greptile}

[greptile-apps]

Undefined term "anomalous source container"

The new sentence introduces "one table per anomalous source container" without defining what "container" means in this context. Elsewhere in the doc the vocabulary is "tables", "schema", or "source datastore". A user who hasn't read the enrichment overview may not know whether "container" means a database table, a schema, a file path, or something else. Consider replacing it with the same terminology used in the rest of the page (e.g., "one table per source table that contained anomalous records") or linking to the glossary entry for "container".

[greptile-apps]

Range information removed without replacement

The previous answer included "Range: 1 to 1,000,000,000" for Maximum Source Examples per Anomaly, which was actionable input-validation guidance. The new text only says "Default is 10" and redirects to a recommendations section. If the recommendations page does not restate the valid range, users who need to set a specific large value have no way to confirm the upper bound without consulting the product UI or API docs directly.