3 files changed, 11 insertions, 3 deletions
diff --git a/docs/markdown/Adding-new-projects-to-wrapdb.md b/docs/markdown/Adding-new-projects-to-wrapdb.md
index 4420de5..58b27ba 100644
--- a/docs/markdown/Adding-new-projects-to-wrapdb.md
+++ b/docs/markdown/Adding-new-projects-to-wrapdb.md
@@ -37,11 +37,10 @@ Each project gets its own repo. It is initialized like this:
 
     git init
     git add readme.txt
-    git commit -a -m 'Start of project foobar.'
-    git tag commit_zero -a -m 'A tag that helps get revision ids for releases.'
+    git add LICENSE.build
+    git commit -a -m 'Create project foobar'
     git remote add origin <repo url>
     git push -u origin master
-    git push --tags
 
 Note that this is the *only* commit that will ever be made to master branch. All other commits are done to branches.
 
diff --git a/docs/markdown/FAQ.md b/docs/markdown/FAQ.md
index f4cf89b..398604a 100644
--- a/docs/markdown/FAQ.md
+++ b/docs/markdown/FAQ.md
@@ -288,3 +288,9 @@ has a option called `wrap-mode` which can be used to disable wrap
 downloads altogether with `--wrap-mode=nodownload`. You can also
 disable dependency fallbacks altogether with `--wrap-mode=nofallback`,
 which also implies the `nodownload` option.
+
+If on the other hand, you want meson to always use the fallback
+for dependencies, even when an external dependency exists and could
+satisfy the version requirements, for example in order to make
+sure your project builds when fallbacks are used, you can use
+`--wrap-mode=forcefallback` since 0.46.0.
diff --git a/docs/markdown/snippets/new-wrap-mode.md b/docs/markdown/snippets/new-wrap-mode.md
new file mode 100644
index 0000000..e33dd83
--- /dev/null
+++ b/docs/markdown/snippets/new-wrap-mode.md
@@ -0,0 +1,3 @@
+A new wrap mode was added, `--wrap-mode=forcefallback`. When this is set,
+dependencies for which a fallback was provided will always use it, even
+if an external dependency exists and satisfies the version requirements.