diff --git a/content/spin/v2/testing-apps.md b/content/spin/v2/testing-apps.md
index 2cb861165..0aeb72ca4 100644
--- a/content/spin/v2/testing-apps.md
+++ b/content/spin/v2/testing-apps.md
@@ -210,7 +210,7 @@ Then we edit the `my-app` application's manifest (the `spin.toml` file) by addin
 [component.my-component.tool.spin-test]
 source = "tests/target/wasm32-wasi/release/tests.wasm"
 build = "cargo component build --release"
-dir = "tests"
+workdir = "tests"
 ```
 
 ## Updating the App to Pass the Tests
@@ -326,4 +326,4 @@ test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; fini
 
 `spin-test` is still in the early days of development, so you’re likely to run into things that don’t quite work yet. We’d love to hear about your experience so we can prioritize which features and bugs to fix first. We’re excited about the future potential of using WebAssembly components for testing, and we look forward to hearing about your experiences as we continue the development of `spin-test`.
 
-You might also like to learn about `spin doctor` which is a command-line tool that detects and helps fix issues preventing applications from building and running. For more information see the [troubleshooting applications page](./troubleshooting-application-dev.md).
\ No newline at end of file
+You might also like to learn about `spin doctor` which is a command-line tool that detects and helps fix issues preventing applications from building and running. For more information see the [troubleshooting applications page](./troubleshooting-application-dev.md).