From d5eeb51bc053d75f647136026de522d6ee3bf725 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 19 Sep 2021 11:36:53 -0400
Subject: [PATCH] Doc: fix typos.

"PGcon" should be "PGconn".  Noted by D. Frey.

Discussion: https://postgr.es/m/163191739352.4680.16994248583642672629@wrigleys.postgresql.org
---
 doc/src/sgml/lobj.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/lobj.sgml b/doc/src/sgml/lobj.sgml
index 012e44c7361..59c34710926 100644
--- a/doc/src/sgml/lobj.sgml
+++ b/doc/src/sgml/lobj.sgml
@@ -453,7 +453,7 @@ pg_int64 lo_tell64(PGconn *conn, int fd);
      <indexterm><primary>lo_truncate</primary></indexterm>
      To truncate a large object to a given length, call
 <synopsis>
-int lo_truncate(PGcon *conn, int fd, size_t len);
+int lo_truncate(PGconn *conn, int fd, size_t len);
 </synopsis>
      This function truncates the large object
      descriptor <parameter>fd</parameter> to length <parameter>len</parameter>.  The
@@ -481,7 +481,7 @@ int lo_truncate(PGcon *conn, int fd, size_t len);
      When dealing with large objects that might exceed 2GB in size,
      instead use
 <synopsis>
-int lo_truncate64(PGcon *conn, int fd, pg_int64 len);
+int lo_truncate64(PGconn *conn, int fd, pg_int64 len);
 </synopsis>
      This function has the same
      behavior as <function>lo_truncate</function>, but it can accept a