   problematic because if `lib/c.ex` changes, `lib/a.ex` also has to
   recompile due to this indirect compile time dependency.
 
-  This interpretation is the same regardless if `--source` or `--sink`
-  flags are used. For example, if we use the `--sink lib/c.ex` flag,
-  we would see the same tree:
+  The flags `--source` or `--sink` does not change how you read the
+  graph. For example, if we use the `--sink lib/c.ex` flag, we would
+  see the same tree:
 
       lib/a.ex
       `-- lib/b.ex (compile)

  those options with `--label` and `--only-nodes` to get all files that exhibit a certain
  property, for example:

      # To get the tree that depend on lib/foo.ex at compile time
      mix xref graph --label compile --sink lib/foo.ex


      The labels are "compile", "export" and "runtime". See
      "Dependencies types" section below

    * `--only-nodes` - only shows the node names (no edges).
      Generally useful with the `--sink` flag

    * `--only-direct` - the `--label` option will restrict itself
      to only direct dependencies instead of transitive ones
