NIT refactor using directives usage in directives, options & docs

- get rid of unnecessary commas and double quote escapes
- bump versions where applicable
- misc typo fixes & tweaks

Author: Gedochao

modules/cli/src/main/scala/scala/cli/commands/test/TestOptions.scala

@@ -53,7 +53,7 @@ object TestOptions {
        |A source file is treated as a test source if:
        |  - the file name ends with `.test.scala`
        |  - the file comes from a directory that is provided as input, and the relative path from that file to its original directory contains a `test` directory
-       |  - it contains the `//> using target.scope "test"` directive (Experimental)
+       |  - it contains the `//> using target.scope test` directive (Experimental)
        |
        |${HelpMessages.commandConfigurations(cmdName)}
        |

modules/directives/src/main/scala/scala/build/preprocessing/directives/Dependency.scala

@@ -22,7 +22,7 @@ import scala.cli.commands.SpecificationLevel
 @DirectiveExamples("//> using test.dep org.scalatest::scalatest:3.2.10")
 @DirectiveExamples("//> using test.dep org.scalameta::munit:0.7.29")
 @DirectiveExamples(
-  "//> using dep \"tabby:tabby:0.2.3,url=https://github.com/bjornregnell/tabby/releases/download/v0.2.3/tabby_3-0.2.3.jar\""
+  "//> using dep tabby:tabby:0.2.3,url=https://github.com/bjornregnell/tabby/releases/download/v0.2.3/tabby_3-0.2.3.jar"
 )
 @DirectiveUsage(
   "//> using dep org:name:ver | //> using deps org:name:ver org2:name2:ver2",

modules/directives/src/main/scala/scala/build/preprocessing/directives/Exclude.scala

@@ -11,8 +11,8 @@ import scala.util.Try
 
 @DirectiveGroupName("Exclude sources")
 @DirectiveExamples("//> using exclude utils.scala")
-@DirectiveExamples("//> using exclude \"examples/*\" \"*/resources/*\"")
-@DirectiveExamples("//> using exclude \"*.sc\"")
+@DirectiveExamples("//> using exclude examples/* */resources/*")
+@DirectiveExamples("//> using exclude *.sc")
 @DirectiveUsage(
   "`//> using exclude `_pattern_ | `//> using exclude `_pattern_ _pattern_ …",
   """`//> using exclude` _pattern_

modules/directives/src/main/scala/scala/build/preprocessing/directives/JavaOptions.scala

@@ -8,7 +8,7 @@ import scala.build.{Positioned, options}
 import scala.cli.commands.SpecificationLevel
 
 @DirectiveGroupName("Java options")
-@DirectiveExamples("//> using javaOpt -Xmx2g, -Dsomething=a")
+@DirectiveExamples("//> using javaOpt -Xmx2g -Dsomething=a")
 @DirectiveExamples("//> using test.javaOpt -Dsomething=a")
 @DirectiveUsage(
   "//> using javaOpt _options_",

modules/directives/src/main/scala/scala/build/preprocessing/directives/JavaProps.scala

@@ -9,7 +9,7 @@ import scala.build.{Positioned, options}
 import scala.cli.commands.SpecificationLevel
 
 @DirectiveGroupName("Java properties")
-@DirectiveExamples("//> using javaProp foo1=bar, foo2")
+@DirectiveExamples("//> using javaProp foo1=bar foo2")
 @DirectiveExamples("//> using test.javaProp foo3=bar foo4")
 @DirectiveUsage(
   "//> using javaProp _key=val_",

modules/directives/src/main/scala/scala/build/preprocessing/directives/RequirePlatform.scala

@@ -11,7 +11,7 @@ import scala.cli.commands.SpecificationLevel
 @DirectivePrefix("target.")
 @DirectiveDescription("Require a Scala platform for the current file")
 @DirectiveExamples("//> using target.platform scala-js")
-@DirectiveExamples("//> using target.platform scala-js, scala-native")
+@DirectiveExamples("//> using target.platform scala-js scala-native")
 @DirectiveExamples("//> using target.platform jvm")
 @DirectiveUsage(
   "//> using target.platform _platform_",

modules/directives/src/main/scala/scala/build/preprocessing/directives/ScalaVersion.scala

@@ -10,7 +10,7 @@ import scala.cli.commands.SpecificationLevel
 @DirectiveExamples("//> using scala 3.0.2")
 @DirectiveExamples("//> using scala 2.13")
 @DirectiveExamples("//> using scala 2")
-@DirectiveExamples("//> using scala 2.13.6, 2.12.16")
+@DirectiveExamples("//> using scala 2.13.6 2.12.16")
 @DirectiveUsage(
   "//> using scala _version_+",
   "`//> using scala` _version_+"

modules/directives/src/main/scala/scala/build/preprocessing/directives/Sources.scala

@@ -12,7 +12,7 @@ import scala.util.Try
 @DirectiveGroupName("Custom sources")
 @DirectiveExamples("//> using file utils.scala")
 @DirectiveUsage(
-  "`//> using file `_path_ | `//> using files `_path1_, _path2_ …",
+  "`//> using file `_path_ | `//> using files `_path1_ _path2_ …",
   """`//> using file` _path_
     |
     |`//> using files` _path1_ _path2_ …

website/docs/commands/compile.md

@@ -31,7 +31,7 @@ For a full list of options, run `scala-cli compile --help`, or check the options
 `--test` makes Scala CLI compile main and test scopes:
 
 ```scala title=Sample.test.scala
-//> using dep org.scalameta::munit:0.7.29
+//> using dep org.scalameta::munit:1.0.2
 class Test extends munit.FunSuite {
   test("sample") {
     assert(2 + 2 == 4)
@@ -487,7 +487,7 @@ For example, to exclude all files in the `example/scala` directory, add the foll
  `project.file` file:
 
 ```scala title=project.scala
-//> using exclude "example/scala"
+//> using exclude example/scala
 ```
 
 ## Compile-Only Dependencies
@@ -499,7 +499,7 @@ To declare a compile-only dependency, you should use the `compileOnly.dep` direc
 option. For instance, to include the `jsoniter-scala-macros` library at compile-time, you would use:
 
 ```scala title=CompileOnly.scala
-//> using compileOnly.dep "com.github.plokhotnyuk.jsoniter-scala::jsoniter-scala-macros:2.23.2"
+//> using compileOnly.dep com.github.plokhotnyuk.jsoniter-scala::jsoniter-scala-macros:2.23.2
 ```
 
 or by using the `--compile-lib` command line option:

website/docs/commands/export.md

@@ -3,7 +3,7 @@ title: Export ⚡️
 sidebar_position: 27
 ---
 
-In case your project outgrows the cabapilities of Scala CLI (e.g support for modules) it may be beneficial
+In case your project outgrows the capabilities of Scala CLI (e.g support for modules) it may be beneficial
 to switch to a build tool such as SBT or Mill.
 The `export` sub-command allows to do that by converting a Scala CLI project into an SBT or Mill configuration.
 Additionally the sub-command supports the JSON format for custom analysis of projects.