X-Git-Url: https://git.heureux-cyclage.org/?p=lhc%2Fweb%2Fwiklou.git;a=blobdiff_plain;f=docs%2Fdatabase.txt;h=6e88d681f4781823d2e6e90da87d94e5baa92a86;hp=dbc92044de29a9a7204b45c4d40ef49c58cd8948;hb=478a58f63101f2b47d18a618296b5e7970fa3f24;hpb=3e88f9fa2a5a00bc1330560accf8e9d09c8be42a

diff --git a/docs/database.txt b/docs/database.txt
index dbc92044de..6e88d681f4 100644
--- a/docs/database.txt
+++ b/docs/database.txt
@@ -71,7 +71,7 @@ want to write code destined for Wikipedia.
 It's often the case that the best algorithm to use for a given task
 depends on whether or not replication is in use. Due to our unabashed
 Wikipedia-centrism, we often just use the replication-friendly version,
-but if you like, you can use wfGetLB()->getServerCount() > 1 to
+but if you like, you can use LoadBalancer::getServerCount() > 1 to
 check to see if replication is in use.
 
 === Lag ===
@@ -107,7 +107,7 @@ in the session, and then at the start of each request, waiting for the
 slave to catch up to that position before doing any reads from it. If
 this wait times out, reads are allowed anyway, but the request is
 considered to be in "lagged slave mode". Lagged slave mode can be
-checked by calling wfGetLB()->getLaggedSlaveMode(). The only
+checked by calling LoadBalancer::getLaggedReplicaMode(). The only
 practical consequence at present is a warning displayed in the page
 footer.