diff --git a/src/docs/contributor/n_plus_one.diviner b/src/docs/contributor/n_plus_one.diviner
index 21bac266e7..86781f5b05 100644
--- a/src/docs/contributor/n_plus_one.diviner
+++ b/src/docs/contributor/n_plus_one.diviner
@@ -63,9 +63,6 @@ are no longer paying the overhead of issuing hundreds of extra queries. This
 will perform much better (although, as with all performance changes, you should
 verify this claim by measuring it).
 
-See also @{method:LiskDAO::loadRelatives} method which provides an abstraction
-to prevent this problem.
-
 = Detecting the Problem =
 
 Beyond reasoning about it while figuring out how to load the data you need, the
diff --git a/src/infrastructure/storage/lisk/LiskDAO.php b/src/infrastructure/storage/lisk/LiskDAO.php
index 66348c6da7..75363b113d 100644
--- a/src/infrastructure/storage/lisk/LiskDAO.php
+++ b/src/infrastructure/storage/lisk/LiskDAO.php
@@ -122,9 +122,6 @@
  * @{method:loadAllWhere} returns a list of objects, while
  * @{method:loadOneWhere} returns a single object (or `null`).
  *
- * There's also a @{method:loadRelatives} method which helps to prevent the 1+N
- * queries problem.
- *
  * = Managing Transactions =
  *
  * Lisk uses a transaction stack, so code does not generally need to be aware