Updated Triggering TypeScript Bot (markdown)

Triggering-TypeScript-Bot.md

@@ -11,8 +11,12 @@ The currently recognized commands are:
 * [`user test this`](https://typescript.visualstudio.com/TypeScript/_build?definitionId=47) - This runs the nightly-tested `user` suite against the PR and against main (this takes around 30 minutes). The bot will post a summary comment comparing results from the two.
 * [`user test tsserver`](https://typescript.visualstudio.com/TypeScript/_build?definitionId=47) - This runs the nightly-tested `user` suite against the PR and against main (this takes around 30 minutes). The bot will post a summary comment comparing results from the two. This variant also tests tsserver, not just tsc.
 * [`user test this slower`](https://typescript.visualstudio.com/TypeScript/_build?definitionId=24) - The older version of the user tests, and run on only a single container, meaning it takes around 1h 30m. The nightly run is run using this build.
-* [`test top100`](https://typescript.visualstudio.com/TypeScript/_build?definitionId=47) - This runs the top 100 Typescript repos on github, by stars, against the PR and against main (this takes around 30 minutes). The bot will post a summary comment comparing results from the two.
-* [`test tsserver top100`](https://typescript.visualstudio.com/TypeScript/_build?definitionId=47) - This runs the top 100 Typescript repos on github, by stars, against the PR and against main (this takes around 30 minutes). The bot will post a summary comment comparing results from the two. This variant also tests tsserver, not just tsc.
+* [`test top100`](https://typescript.visualstudio.com/TypeScript/_build?definitionId=47) - This runs the top 100 TypeScript repos on GitHub, by stars, against the PR and against main (this takes around 30 minutes). The bot will post a summary comment comparing results from the two.
+
+  Note that `100` can be replaced with any other number up to 3 digits. For example, `test top200`, `test top50`, or `test top999` will all work.
+* [`test tsserver top100`](https://typescript.visualstudio.com/TypeScript/_build?definitionId=47) - This runs the top 100 TypeScript repos on GitHub, by stars, against the PR and against main (this takes around 30 minutes). The bot will post a summary comment comparing results from the two. This variant tests tsserver, not tsc.
+
+  Note that `100` can be replaced with any other number up to 3 digits. For example, `test top200`, `test top50`, or `test top999` will all work.
 * [`perf test`](https://typescript.visualstudio.com/TypeScript/_build?definitionId=22) - This queues a build on our perf server using the code from the PR - once started (which will only happen once any currently running build is done), this takes around 40 minutes. The bot should post the results of the perf test run back into the triggering PR once done.
 * [`perf test faster`](https://typescript.visualstudio.com/TypeScript/_build?definitionId=45) - This is the same as the above, but only runs the node 12 host tests - so the results should be less complete, but come back in around 1/3rd the time.
 * [`pack this`](https://typescript.visualstudio.com/TypeScript/_build?definitionId=19) - This creates a build which does a build, runs an LKG, runs normal tests, and then packs the result into an installable tarball (which can be downloaded from the build artifacts on the azure pipelines build status page), perfect for installing with `npm i <URL to tarball>` to test with.