Commit 01ddd2f7 authored by Peter Eisentraut's avatar Peter Eisentraut

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
parent e6159885
...@@ -1448,7 +1448,7 @@ ...@@ -1448,7 +1448,7 @@
known as <firstterm>local objects</firstterm>. known as <firstterm>local objects</firstterm>.
</para> </para>
<para> <para>
Most local objects belong to a specific Most local objects reside in a specific
<glossterm linkend="glossary-schema">schema</glossterm> in their <glossterm linkend="glossary-schema">schema</glossterm> in their
containing database, such as containing database, such as
<glossterm linkend="glossary-relation">relations</glossterm> (all types), <glossterm linkend="glossary-relation">relations</glossterm> (all types),
...@@ -1458,7 +1458,7 @@ ...@@ -1458,7 +1458,7 @@
are enforced to be unique. are enforced to be unique.
</para> </para>
<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-extension">extensions</glossterm>,
<glossterm linkend="glossary-cast">data type casts</glossterm>, and <glossterm linkend="glossary-cast">data type casts</glossterm>, and
<glossterm linkend="glossary-foreign-data-wrapper">foreign data wrappers</glossterm>. <glossterm linkend="glossary-foreign-data-wrapper">foreign data wrappers</glossterm>.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment