Wording fixes and mention CLI options on WebAssembly testing

Author: kateinoigakukun

Sources/Testing/Testing.docc/TemporaryGettingStarted.md

@@ -148,7 +148,7 @@ section of
 #### Running tests for WebAssembly
 
 To run tests for WebAssembly, install a Swift SDK for WebAssembly by following
-[the instructions](https://book.swiftwasm.org/getting-started/setup-snapshot.html).
+[these instructions](https://book.swiftwasm.org/getting-started/setup-snapshot.html).
 
 Because `swift test` doesn't know what WebAssembly environment you'd like to use
 to run your tests, building tests and running them are two separate steps. To
@@ -159,11 +159,20 @@ swift build --swift-sdk wasm32-unknown-wasi --build-tests
 ```
 
 After building tests, you can run them using a [WASI](https://wasi.dev/)-compliant
-WebAssembly runtime, such as [Wasmtime](https://wasmtime.dev/) or
+WebAssembly runtime such as [Wasmtime](https://wasmtime.dev/) or
 [WasmKit](https://github.com/swiftwasm/WasmKit). For example, to run tests using
 Wasmtime, use the following command (replace `{YOURPACKAGE}` with your package's
 name):
 
 ```sh
 wasmtime .build/debug/{YOURPACKAGE}PackageTests.wasm
 ```
+
+Most WebAssembly runtimes forward trailing arguments to the WebAssembly program,
+so you can pass command-line options of the testing library. For example, to list
+all tests and filter them by name, use the following commands:
+
+```sh
+wasmtime .build/debug/{YOURPACKAGE}PackageTests.wasm --list-tests
+wasmtime .build/debug/{YOURPACKAGE}PackageTests.wasm --filter "FoodTruckTests.foodTruckExists"
+```