docs: update directive docs

Author: joscha

docs/directive.md

@@ -1,6 +1,6 @@
 # The dependency-tree's directive
 
-In most cases, statical source code analysis works quite well for purposes that the dependency-tree tool aims to target. However, this approach doesn't work for some rare, yet important cases. Since most of the application's code depends on the configuration files indirectly an ability to link these files with the application's source code became crucial. For example, the tool is currently unable to build a correct dependency graph between a file with available agent queues in it (e.g. `production/buildkite/queues.json`) and the application's source code. Another example where there is no full (AST processing) support for a particular language (e.g. `*.ejs`, `*.sh`, etc) in the dependency-tree tool but since we use this language in critical paths of the system it's important to build dependency graph correctly for such cases.
+In most cases, statical source code analysis works quite well for purposes that the dependency-tree tool aims to target. However, this approach doesn't work for some rare, yet important cases. Since most of the application's code depends on the configuration files indirectly an ability to link these files with the application's source code became crucial. For example, the tool is currently unable to build a correct dependency graph between some configuration files and the application's source code. Another example where there is no full (AST processing) support for a particular language (e.g. `*.ejs`, `*.sh`, etc) in the dependency-tree tool but since we use this language in critical paths of the system it's important to build dependency graph correctly for such cases.
 
 The approach to address this problem could look like to annotate some of the files with pieces of metadata that let the tool know how to build a dependency graph.