From fe57c203b6c5104ffacef50f104d625d3fb73031 Mon Sep 17 00:00:00 2001
From: Justin Pryzby <pryzbyj@telsasoft.com>
Date: Tue, 29 Mar 2022 11:18:59 -0500
Subject: [PATCH 08/19] doc review: CREATE DATABASE STRATEGY

9c08aea6a3090a396be334cc58c511edab05776a
---
 doc/src/sgml/ref/create_database.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/create_database.sgml b/doc/src/sgml/ref/create_database.sgml
index b2bb3da5fdb..ed0cbe3473c 100644
--- a/doc/src/sgml/ref/create_database.sgml
+++ b/doc/src/sgml/ref/create_database.sgml
@@ -132,7 +132,7 @@ CREATE DATABASE <replaceable class="parameter">name</replaceable>
         available. This strategy writes a small record to the write-ahead log
         for each tablespace used by the target database. Each such record
         represents copying an entire directory to a new location at the
-        filesystem level. While this does reduce the write-ahed
+        filesystem level. While this does reduce the write-ahead
         log volume substantially, especially if the template database is large,
         it also forces the system to perform a checkpoint both before and
         after the creation of the new database. In some situations, this may
-- 
2.17.1

