Code

Ticket #12668: multi-db-typos.diff

File multi-db-typos.diff, 1.3 KB (added by mattimustang, 4 years ago)
Line 
1Index: docs/topics/db/multi-db.txt
2===================================================================
3--- docs/topics/db/multi-db.txt (revision 12277)
4+++ docs/topics/db/multi-db.txt (working copy)
5@@ -149,8 +149,8 @@
6 object instance that is related to the read or write operation that is
7 underway. This might be the instance that is being saved, or it might
8 be an instance that is being added in a many-to-many relation. In some
9-cases, no instance hint will be provided at all. The router check for
10-the existence of an instance hint, and determine if hat hint should be
11+cases, no instance hint will be provided at all. The router checks for
12+the existence of an instance hint, and determine if that hint should be
13 used to alter routing behavior.
14 
15 Using routers
16@@ -192,7 +192,7 @@
17     doesn't provide any solution for handling replication lag (i.e.,
18     query inconsistencies introduced because of the time taken for a
19     write to propagate to the slaves). It also doesn't consider the
20-    interaction of transactions with the database utiliztion strategy.
21+    interaction of transactions with the database utilization strategy.
22 
23 So - what does this mean in practice? Say you want ``contrib.auth`` to
24 exist on the 'credentials' database, and you want all other models in a