Skip to content

Commit 01ddd2f

Browse files
committed
doc: Make terminology in glossary consistent
Use "reside in" rather than "belong to" for objects in a schema. Previous use was a mix of the two. Author: Alvaro Herrera <alvherre@alvh.no-ip.org> Discussion: https://www.postgresql.org/message-id/202106021932.idmbjjaqk7ke@alvherre.pgsql
1 parent e615988 commit 01ddd2f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/src/sgml/glossary.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1448,7 +1448,7 @@
14481448
known as <firstterm>local objects</firstterm>.
14491449
</para>
14501450
<para>
1451-
Most local objects belong to a specific
1451+
Most local objects reside in a specific
14521452
<glossterm linkend="glossary-schema">schema</glossterm> in their
14531453
containing database, such as
14541454
<glossterm linkend="glossary-relation">relations</glossterm> (all types),
@@ -1458,7 +1458,7 @@
14581458
are enforced to be unique.
14591459
</para>
14601460
<para>
1461-
There also exist local objects that do not belong to schemas; some examples are
1461+
There also exist local objects that do not reside in schemas; some examples are
14621462
<glossterm linkend="glossary-extension">extensions</glossterm>,
14631463
<glossterm linkend="glossary-cast">data type casts</glossterm>, and
14641464
<glossterm linkend="glossary-foreign-data-wrapper">foreign data wrappers</glossterm>.

0 commit comments

Comments
 (0)