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

diff --git a/doc/src/sgml/glossary.sgml b/doc/src/sgml/glossary.sgml
index 41f3e5ee86ba6b4f6a1588848606d83a908edae5..c8d0440e80f50a220cbd4a6b9d9dcdad5a238023 100644 (file)
--- a/doc/src/sgml/glossary.sgml
+++ b/doc/src/sgml/glossary.sgml
@@ -1448,7 +1448,7 @@
       known as <firstterm>local objects</firstterm>.
      </para>
      <para>
-      Most local objects belong to a specific
+      Most local objects reside in a specific
       <glossterm linkend="glossary-schema">schema</glossterm> in their
       containing database, such as
       <glossterm linkend="glossary-relation">relations</glossterm> (all types),
@@ -1458,7 +1458,7 @@
       are enforced to be unique.
      </para>
      <para>
-      There also exist local objects that do not belong to schemas; some examples are
+      There also exist local objects that do not reside in schemas; some examples are
       <glossterm linkend="glossary-extension">extensions</glossterm>,
       <glossterm linkend="glossary-cast">data type casts</glossterm>, and
       <glossterm linkend="glossary-foreign-data-wrapper">foreign data wrappers</glossterm>.