From 38c46fcafd753588cf855a97ad8faaab390abf73 Mon Sep 17 00:00:00 2001
From: asritha <101123140+asritha420@users.noreply.github.com>
Date: Fri, 7 Feb 2025 12:29:22 -0500
Subject: [PATCH] docs(typo): PostgresQL corrected to PostgreSQL (#32188)

---
 docs/docs/installation/architecture.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/installation/architecture.mdx b/docs/docs/installation/architecture.mdx
index 85b42398b..e94f7258c 100644
--- a/docs/docs/installation/architecture.mdx
+++ b/docs/docs/installation/architecture.mdx
@@ -45,7 +45,7 @@ This is the core application. Superset operates like this:
 
 This is where chart and dashboard definitions, user information, logs, etc. are stored. Superset is tested to work with PostgreSQL and MySQL databases as the metadata database (not be confused with a data source like your data warehouse, which could be a much greater variety of options like Snowflake, Redshift, etc.).
 
-Some installation methods like our Quickstart and PyPI come configured by default to use a SQLite on-disk database. And in a Docker Compose installation, the data would be stored in a PostgresQL container volume. Neither of these cases are recommended for production instances of Superset.
+Some installation methods like our Quickstart and PyPI come configured by default to use a SQLite on-disk database. And in a Docker Compose installation, the data would be stored in a PostgreSQL container volume. Neither of these cases are recommended for production instances of Superset.
 
 For production, a properly-configured, managed, standalone database is recommended. No matter what database you use, you should plan to back it up regularly.