From 2a90cb69e18e0c0637f3f93702e7b2f7808ff1b2 Mon Sep 17 00:00:00 2001
From: Robert Haas <rhaas@postgresql.org>
Date: Tue, 15 Mar 2016 16:28:17 -0400
Subject: [PATCH] Fix typos.

Thomas Reiss
---
 doc/src/sgml/monitoring.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index de79fde6be3..7055c37a0b1 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -663,7 +663,7 @@ postgres   27093  0.0  0.0  30096  2752 ?        Ss   11:34   0:00 postgres: ser
         <listitem>
          <para>
           <literal>Lock</>: The backend is waiting for a heavyweight lock.
-          Heayweight locks, also known as lock manager locks or simply locks,
+          Heavyweight locks, also known as lock manager locks or simply locks,
           primarily protect SQL-visible objects such as tables.  However,
           they are also used to ensure mutual exclusion for certain internal
           operations such as relation extension.  <literal>wait_event</> will
@@ -971,7 +971,7 @@ postgres   27093  0.0  0.0  30096  2752 ?        Ss   11:34   0:00 postgres: ser
         <row>
          <entry morerows="15"><literal>LWLockTranche</></entry>
          <entry><literal>clog</></entry>
-         <entry>Waiting for I/O on a clog (transcation status) buffer.</entry>
+         <entry>Waiting for I/O on a clog (transaction status) buffer.</entry>
         </row>
         <row>
          <entry><literal>commit_timestamp</></entry>