mintro: Renamed --dependencies --> --scan-dependencies

2 files changed, 7 insertions, 13 deletions

diff --git a/docs/markdown/IDE-integration.md b/docs/markdown/IDE-integration.md
index 35ce883..7bbec5d 100644
--- a/docs/markdown/IDE-integration.md
+++ b/docs/markdown/IDE-integration.md
@@ -187,13 +187,10 @@ The list of all _found_ dependencies can be acquired from
 `intro-dependencies.json`. Here, the name, compiler and linker arguments for
 a dependency are listed.
 
-### Using `--dependencies` without a build directory
+### Scanning for dependecie with `--scan-dependencies`
 
-It is also possible to get most targets without a build directory. This can be
-done by running `meson introspect --dependencies /path/to/meson.build`.
-
-However, the generated output is vastly different from running the introspection
-command with a build directory.
+It is also possible to get most dependencies used without a build directory.
+This can be done by running `meson introspect --scan-dependencies /path/to/meson.build`.
 
 The output format is as follows:
 
diff --git a/docs/markdown/snippets/introspect_deps_no_bd.md b/docs/markdown/snippets/introspect_deps_no_bd.md
index a28b667..cfae58b 100644
--- a/docs/markdown/snippets/introspect_deps_no_bd.md
+++ b/docs/markdown/snippets/introspect_deps_no_bd.md
@@ -1,10 +1,7 @@
-## `introspect --dependencies` can now be used without configured build directory
+## `introspect --scan-dependencies` can now be used to scan for dependencies used in a project
 
-It is now possible to run `meson introspect --dependencies /path/to/meson.build`
-without a configured build directory.
-
-However, the generated output is vastly different from running the introspection
-command with a build directory.
+It is now possible to run `meson introspect --scan-dependencies /path/to/meson.build`
+without a configured build directory to scan for dependencies.
 
 The output format is as follows:
 
@@ -25,4 +22,4 @@ in the `meson.build` (all dependencies are required by default). The
 inside a conditional block. In a real meson run these dependencies might not be
 used, thus they _may_ not be required, even if the `required` key is set. The
 `has_fallback` key just indicates whether a fallback was directly set in the
-`dependency()` function.
\ No newline at end of file
+`dependency()` function.