in Toolkit sbt example, avoid having two subprojects

_includes/_markdown/install-munit.md

@@ -16,13 +16,14 @@ Alternatively, you can require just a specific version of MUnit:
 {% tab 'sbt' %}
 In your build.sbt file, you can add the dependency on toolkit-test:
 ```scala
-lazy val example = project.in(file("example"))
+lazy val example = project.in(file("."))
   .settings(
     scalaVersion := "3.3.3",
     libraryDependencies += "org.scala-lang" %% "toolkit-test" % "0.1.7" % Test
   )
 ```
-Here the `Test` configuration means that the dependency is only used by the source files in `example/src/test`.
+
+Here the `Test` configuration means that the dependency is only used by the source files in `src/test`.
 
 Alternatively, you can require just a specific version of MUnit:
 ```scala

_includes/_markdown/install-os-lib.md

@@ -15,7 +15,7 @@ Alternatively, you can require just a specific version of OS-Lib:
 {% tab 'sbt' %}
 In your `build.sbt`, you can add a dependency on the toolkit:
 ```scala
-lazy val example = project.in(file("example"))
+lazy val example = project.in(file("."))
   .settings(
     scalaVersion := "3.3.3",
     libraryDependencies += "org.scala-lang" %% "toolkit" % "0.1.7"

_includes/_markdown/install-sttp.md

@@ -15,7 +15,7 @@ Alternatively, you can require just a specific version of sttp:
 {% tab 'sbt' %}
 In your build.sbt file, you can add a dependency on the Toolkit:
 ```scala
-lazy val example = project.in(file("example"))
+lazy val example = project.in(file("."))
   .settings(
     scalaVersion := "3.3.3",
     libraryDependencies += "org.scala-lang" %% "toolkit" % "0.1.7"

_includes/_markdown/install-upickle.md

@@ -15,7 +15,7 @@ Alternatively, you can require just a specific version of UPickle:
 {% tab 'sbt' %}
 In your build.sbt file, you can add the dependency on the Toolkit:
 ```scala
-lazy val example = project.in(file("example"))
+lazy val example = project.in(file("."))
   .settings(
     scalaVersion := "3.3.3",
     libraryDependencies += "org.scala-lang" %% "toolkit" % "0.1.7"

_overviews/toolkit/testing-run-only.md

@@ -22,7 +22,7 @@ scala-cli test example --test-only example.MyTests
 {% tab 'sbt' %}
 To run a single `example.MyTests` suite in sbt, use the `testOnly` task:
 ```
-sbt:example> example/testOnly example.MyTests
+sbt:example> testOnly example.MyTests
 ```
 {% endtab %}
 {% tab 'Mill' %}

_overviews/toolkit/testing-run.md

@@ -27,7 +27,7 @@ scala-cli test example
 {% tab 'sbt' %}
 In the sbt shell, the following command runs all the tests of the project `example`:
 ```
-sbt:example> example/test
+sbt:example> test
 # MyTests:
 #   + sum of two integers 0.006s
 # [info] Passed: Total 1, Failed 0, Errors 0, Passed 1
@@ -74,7 +74,7 @@ test("failing test") {
 ```
 # MyTests:
 #   + sum of two integers 0.008s
-# ==> X MyTests.failing test  0.015s munit.ComparisonFailException: ./example/MyTests.test.scala:13
+# ==> X MyTests.failing test  0.015s munit.ComparisonFailException: ./MyTests.test.scala:13
 # 12:    val expected = 4
 # 13:    assertEquals(obtained, expected)
 # 14:  }