Skip to content

Fixed some grammar issues in HM Supported database types #6923

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
merged 1 commit into from
Jul 28, 2025
Merged

Fixed some grammar issues in HM Supported database types #6923

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
4 changes: 2 additions & 2 deletions advocacy_docs/edb-postgres-ai/hybrid-manager/overview/database_types/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ navigation:

---

Selecting the right Postgres database cluster type when creating new clusters in the Hybrid Manager (HM) is crucial for optimizing your database environment. EDB offers a range of options, each tailored to different needs, from basic single-node deployments to highly resilient, distributed solutions.
Selecting the right Postgres database cluster type when creating new clusters in the Hybrid Manager (HM) is crucial for optimizing your database environment. EDB offers a wide range of solutions, each tailored for different needs, from basic single-node deployments to highly resilient distributed solutions.

## Distributed High Availability

Expand All @@ -19,7 +19,7 @@ Distributed High Availability (DHA) clusters are powered by EDB Postgres Distrib
**Who should pick this option?**

- Organizations requiring ultra-high availability and near-zero downtime.
- Applications that demand distributed deployments with low latency access for users.
- Applications that demand distributed deployments with low latency access.
- Businesses with mission-critical applications where continuous operation and data consistency across multiple active nodes are paramount.
- Scenarios requiring uninterrupted online database maintenance and in-place major version upgrades without impacting availability.

Expand Down