docs: update FAQ license wording

[tianzhou]

Summary

• Update the FAQ license answer to reference Apache License 2.0
• Keep the free-to-use/all-features-included wording

Tests

• Not run (docs-only change)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
pgconsole	Ready	Preview, Comment	Jun 25, 2026 11:30am

[Copilot]

Pull request overview

Updates the FAQ’s license wording to accurately describe pgconsole’s licensing in the documentation while preserving the existing “free to use / all features included” messaging.

Changes:

• Replace “source available” phrasing with an explicit reference to the Apache License 2.0 (linking to LICENSE).
• Normalize the formatting of the License and Certifications answers (remove unintended indentation).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[greptile-apps]

Greptile Summary

This docs-only PR corrects the FAQ license section to accurately reflect the project's Apache License 2.0 instead of the vaguer "source available" phrasing, and also fixes a missing newline at end of file.

• The new Apache License 2.0 link and label are consistent with the actual LICENSE file at the repo root.
• The "free to use, with all features included" statement is preserved unchanged.

Confidence Score: 5/5

Safe to merge — a single documentation line is updated with a factually correct license name that matches the repo's own LICENSE file.

The change replaces an imprecise 'source available' label with the specific 'Apache License 2.0' name, which is verified against the repo's LICENSE file. A missing end-of-file newline is also corrected. No logic, configuration, or code is touched.

No files require special attention.

Important Files Changed

Filename	Overview
docs/getting-started/faq.mdx	Updates license wording from 'source available' to 'Apache License 2.0' (verified against repo LICENSE file) and adds missing newline at end of file.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[FAQ: License Section] --> B{Old Wording}
    B --> C["'source available' link"]
    A --> D{New Wording}
    D --> E["Apache License 2.0 link"]
    E --> F[Links to /blob/main/LICENSE]
    F --> G[LICENSE file: Apache 2.0 ✓]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[FAQ: License Section] --> B{Old Wording}
    B --> C["'source available' link"]
    A --> D{New Wording}
    D --> E["Apache License 2.0 link"]
    E --> F[Links to /blob/main/LICENSE]
    F --> G[LICENSE file: Apache 2.0 ✓]

Loading

_{Reviews (1): Last reviewed commit: "docs: update FAQ license wording" | Re-trigger Greptile}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
pgconsole	🟢 Ready	View Preview	Jun 25, 2026, 11:37 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.