Tweak test generator documentation (#497)

* Tweak test generators docs

* More updates

* More work

* CLI

* Docs

* More work

* Tweaks

* Minor rewording

* Work

* Update building/tooling/test-generators.md

Co-authored-by: mk-mxp <[email protected]>

* Update building/tooling/test-generators.md

Co-authored-by: mk-mxp <[email protected]>

* Update building/tooling/test-generators.md

Co-authored-by: mk-mxp <[email protected]>

* Update building/tooling/test-generators.md

Co-authored-by: mk-mxp <[email protected]>

* Update building/tooling/test-generators.md

Co-authored-by: mk-mxp <[email protected]>

* Update building/tooling/test-generators.md

Co-authored-by: mk-mxp <[email protected]>

* Update building/tooling/test-generators.md

Co-authored-by: mk-mxp <[email protected]>

* Update building/tracks/new/implement-tooling.md

Co-authored-by: mk-mxp <[email protected]>

* Update building/tooling/README.md

Co-authored-by: mk-mxp <[email protected]>

* Clarify nesting

* Update building/tooling/test-generators.md

Co-authored-by: mk-mxp <[email protected]>

---------

Co-authored-by: mk-mxp <[email protected]>

Author: ErikSchierboom

building/tooling/README.md

@@ -46,5 +46,5 @@ Track tooling is usually (mostly) written in the track's language.
 
 ```exercism/caution
 While you're free to use additional languages, each additional language will make it harder to find people that can maintain or contribute to the track.
-We recommend using the track's language where possible, only using additional languages when it cannot be avoided.
+We recommend using the track's language where possible, because it makes maintaining or contributing easier.
 ```