From 53ad41cbd9eca06c9d6f7440c867b83a9463dc3f Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 11 Sep 2020 11:07:33 -0400 Subject: [PATCH] fix typos Change-Id: I7649576bd1e100fd6f8968f0256b074263943a44 --- doc/build/orm/declarative_tables.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/build/orm/declarative_tables.rst b/doc/build/orm/declarative_tables.rst index bbad7a321b..2aff8bbc2d 100644 --- a/doc/build/orm/declarative_tables.rst +++ b/doc/build/orm/declarative_tables.rst @@ -6,7 +6,7 @@ Table Configuration with Declarative ============================================= As introduced at :ref:`orm_declarative_mapping`, the Declarative style -includses the ability to generate a mapped :class:`_schema.Table` object +includes the ability to generate a mapped :class:`_schema.Table` object at the same time, or to accommodate a :class:`_schema.Table` or other :class:`_sql.FromClause` object directly. @@ -51,7 +51,7 @@ collection of this :class:`_schema.Table` object. The :class:`_schema.Column` objects can omit their "name" field, which is usually the first positional argument to the :class:`_schema.Column` constructor; the declarative system will assign the key associated with each :class:`_schema.Column` as the name, -to produce a :class:`_schema.Table` that is equvialent to:: +to produce a :class:`_schema.Table` that is equivalent to:: # equivalent Table object produced user_table = Table( -- 2.47.3