From 741fb0056eda5e7bd03deb0719121f88b4b9e34a Mon Sep 17 00:00:00 2001
From: Daniel Gustafsson <dgustafsson@postgresql.org>
Date: Wed, 13 Dec 2023 11:32:13 +0100
Subject: [PATCH] docs: Fix typo in pg_stat_statements documentation

Commit dc9f8a79830 accidentally misspelled minimum as minimun.
---
 doc/src/sgml/pgstatstatements.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/pgstatstatements.sgml b/doc/src/sgml/pgstatstatements.sgml
index acfacf828ce..44dd4db7ce7 100644
--- a/doc/src/sgml/pgstatstatements.sgml
+++ b/doc/src/sgml/pgstatstatements.sgml
@@ -770,7 +770,7 @@
       view are discarded, it will also reset the statistics in the
       <structname>pg_stat_statements_info</structname> view.
       When <structfield>minmax_only</structfield> is <literal>true</literal> only the
-      values of minimun and maximum planning and execution time will be reset (i.e.
+      values of minimum and maximum planning and execution time will be reset (i.e.
       <structfield>min_plan_time</structfield>, <structfield>max_plan_time</structfield>,
       <structfield>min_exec_time</structfield> and <structfield>max_exec_time</structfield>
       fields). The default value for <structfield>minmax_only</structfield> parameter is
-- 
2.39.5