btrfs-progs: tests: fix source path for testsuite

[platform/upstream/btrfs-progs.git] / Documentation / btrfs.asciidoc

diff --git a/Documentation/btrfs.asciidoc b/Documentation/btrfs.asciidoc
index 1c37abf..8253023 100644 (file)
--- a/Documentation/btrfs.asciidoc
+++ b/Documentation/btrfs.asciidoc
@@ -19,12 +19,15 @@ There are also standalone tools for some tasks like *btrfs-convert* or
 *btrfstune* that were separate historically and/or haven't been merged to the
 main utility. See section 'STANDALONE TOOLS' for more details.
 
+For other topics (mount options, etc) please refer to the separate manual
+page `btrfs`(5).
+
 COMMAND SYNTAX
 --------------
 
-Any command name can be shortened as far as it stays unambiguous,
-however it is recommended to use full command names in scripts.
-All command groups have their manual page named *btrfs-<group>*.
+Any command name can be shortened so long as the shortened form is unambiguous,
+however, it is recommended to use full command names in scripts.  All command
+groups have their manual page named *btrfs-<group>*.
 
 For example: it is possible to run *btrfs sub snaps* instead of
 *btrfs subvolume snapshot*.
@@ -103,10 +106,10 @@ COMMANDS
 STANDALONE TOOLS
 ----------------
 
-There are several standalone tools to provide certain functionality. If the
-functionality proves to be useful, the standalone tools are declared obsolete
-and their functionality copied to the main tool. The deprecation period is long
-(years) and the obsolete binaries are still provided.
+New functionality could be provided using a standalone tool. If the functionality
+proves to be useful, then the standalone tool is declared obsolete and its
+functionality is copied to the main tool. Obsolete tools are removed after a
+long (years) depreciation period.
 
 Tools that are still in active use without an equivalent in *btrfs*: