From 2a48d0838b46963b134b4351d4da0dd352cbd8bf Mon Sep 17 00:00:00 2001
From: erikjohnston <erikjohnston@users.noreply.github.com>
Date: Tue, 26 Sep 2023 16:01:35 +0000
Subject: deploy: 88ba67eb91215a708f321e16559fe3c2c0d0a407

---
 latest/postgres.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'latest/postgres.html')

diff --git a/latest/postgres.html b/latest/postgres.html
index f3e98fda6e..4c487267ab 100644
--- a/latest/postgres.html
+++ b/latest/postgres.html
@@ -342,7 +342,7 @@ of <code>COLLATE</code> and <code>CTYPE</code> unless the config flag <code>allo
 <code>database</code> section of the config, is set to true. Using different locales can cause issues if the locale library is updated from
 underneath the database, or if a different version of the locale is used on any
 replicas.</p>
-<p>If you have a databse with an unsafe locale, the safest way to fix the issue is to dump the database and recreate it with
+<p>If you have a database with an unsafe locale, the safest way to fix the issue is to dump the database and recreate it with
 the correct locale parameter (as shown above). It is also possible to change the
 parameters on a live database and run a <code>REINDEX</code> on the entire database,
 however extreme care must be taken to avoid database corruption.</p>
-- 
cgit 1.5.1