summaryrefslogtreecommitdiff
path: root/docs/markdown/Tutorial.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/markdown/Tutorial.md')
-rw-r--r--docs/markdown/Tutorial.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/markdown/Tutorial.md b/docs/markdown/Tutorial.md
index 6b248b519..c5a4e6bcf 100644
--- a/docs/markdown/Tutorial.md
+++ b/docs/markdown/Tutorial.md
@@ -74,7 +74,7 @@ Now we are ready to build our code.
```
$ cd builddir
-$ ninja
+$ meson compile
```
Once that is done we can run the resulting binary.
@@ -124,12 +124,12 @@ or the like. Instead we just type the exact same command as if we were
rebuilding our code without any build system changes.
```
-$ ninja
+$ meson compile
```
Once you have set up your build directory the first time, you don't
ever need to run the `meson` command again. You always just run
-`ninja`. Meson will automatically detect when you have done changes to
+`meson compile`. Meson will automatically detect when you have done changes to
build definitions and will take care of everything so users don't have
to care. In this case the following output is produced.