1 files changed, 1 insertions, 1 deletions

diff --git a/documentation/content/en/books/developers-handbook/tools/_index.adoc b/documentation/content/en/books/developers-handbook/tools/_index.adoc
index d6ef9ec467..608851ecc7 100644
--- a/documentation/content/en/books/developers-handbook/tools/_index.adoc
+++ b/documentation/content/en/books/developers-handbook/tools/_index.adoc
@@ -530,7 +530,7 @@ In other words, this is the rule which tells make how to re-compile [.filename]#
 
 So, when you type `make`, it will make sure that [.filename]#foo# is up to date with respect to your latest changes to [.filename]#foo.c#.
 This principle can be extended to [.filename]#Makefile#'s with hundreds of targets-in fact, on FreeBSD,
-it is possible to compile the entire operating system just by typing `make world` in the appropriate directory!
+it is possible to compile the entire operating system just by typing `make buildworld` at the top level directory in the src tree.
 
 Another useful property of makefiles is that the targets do not have to be programs.
 For instance, we could have a make file that looks like this: