selectby -> select_by

diff --git a/doc/build/content/datamapping.txt b/doc/build/content/datamapping.txt
index 68a17bea90517f228d28a295a71b066035981bef..ba70e05a082fd3b9060c9ac72a8f7efffaf86c98 100644 (file)
--- a/doc/build/content/datamapping.txt
+++ b/doc/build/content/datamapping.txt
@@ -446,7 +446,7 @@ Another way to specify joins more explicitly is to use the `from_obj` parameter
 
 In the above example, the `join` function by default creates a natural join between the two tables, so we were able to avoid having to specify the join condition between `users` and `addresses` explicitly.
 
-#### Creating Joins Using selectby() {@name=relselectby}
+#### Creating Joins Using select\_by() {@name=relselectby}
 
 Another way that joins can be created is by using the `select_by` method of `Query`, which has the ability to create joins across relationships automatically.  This method is in many circumstances more convenient than, but not as flexible as, the more SQL-level approach using the `select()` method described in the previous section.