From 49c4747a87a4a14fb14eb0784be04dc7a1bca649 Mon Sep 17 00:00:00 2001 From: Adam Szatrowski Date: Wed, 12 Oct 2016 19:27:57 -0400 Subject: Replace uses of the phrase "comprised of" in docs --- doc/build/core/schema.rst | 2 +- doc/build/orm/nonstandard_mappings.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/build/core/schema.rst b/doc/build/core/schema.rst index 8553ebcbf..21d1805f7 100644 --- a/doc/build/core/schema.rst +++ b/doc/build/core/schema.rst @@ -10,7 +10,7 @@ This section references SQLAlchemy **schema metadata**, a comprehensive system o database schemas. The core of SQLAlchemy's query and object mapping operations are supported by -*database metadata*, which is comprised of Python objects that describe tables +*database metadata*, which is composed of Python objects that describe tables and other schema-level objects. These objects are at the core of three major types of operations - issuing CREATE and DROP statements (known as *DDL*), constructing SQL queries, and expressing information about structures that diff --git a/doc/build/orm/nonstandard_mappings.rst b/doc/build/orm/nonstandard_mappings.rst index 4645a8029..780154ae3 100644 --- a/doc/build/orm/nonstandard_mappings.rst +++ b/doc/build/orm/nonstandard_mappings.rst @@ -9,7 +9,7 @@ Mapping a Class against Multiple Tables Mappers can be constructed against arbitrary relational units (called *selectables*) in addition to plain tables. For example, the :func:`~.expression.join` -function creates a selectable unit comprised of +function creates a selectable unit composed of multiple tables, complete with its own composite primary key, which can be mapped in the same way as a :class:`.Table`:: -- cgit v1.2.1