From: Federico Caselli Date: Wed, 18 Jan 2023 22:02:36 +0000 (+0100) Subject: avoid confusion in rst comment X-Git-Tag: rel_2_0_0rc3~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8b4b26e709c906134d5277c3fa2220aa5c4bb428;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git avoid confusion in rst comment Change-Id: I6e971f7445ae19f73097516b58776ab05a5371f1 --- diff --git a/doc/build/tutorial/metadata.rst b/doc/build/tutorial/metadata.rst index 5d1733fc6f..730190be31 100644 --- a/doc/build/tutorial/metadata.rst +++ b/doc/build/tutorial/metadata.rst @@ -53,7 +53,7 @@ constructed programmatically, either directly by using the option to load some or all table information from an existing database, called :term:`reflection`. -.. note: the word "simply" is used below. While I dont like this word, I am +.. comment: the word "simply" is used below. While I dont like this word, I am using it here to stress that creating the MetaData directly will not introduce complexity (as long as one knows to associate it w/ declarative base)