docs: Minor fixes for getting started
- Fixed unit test location in the output directory while
clarifying the compiler dependent path.
- Use "source" instead of "." for consistency with earlier use.
Change-Id: I13bebfebd240231d47ffbdbeb552d6646ab41eb6
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/13796
Commit-Queue: Keir Mierle <keir@google.com>
Reviewed-by: Keir Mierle <keir@google.com>
Reviewed-by: Armando Montanez <amontanez@google.com>
diff --git a/docs/getting_started.md b/docs/getting_started.md
index 737be91..2e7571a 100644
--- a/docs/getting_started.md
+++ b/docs/getting_started.md
@@ -77,7 +77,7 @@
See below for equivalent Windows commands, and for more details on what each
part does.
-**Note:** After running bootstrap once, use `. ./activate.sh` (or
+**Note:** After running bootstrap once, use `source ./activate.sh` (or
`activate.bat` on Windows) to re-activate the environment without
re-bootstrapping.
@@ -225,10 +225,10 @@
Try running the `pw_status` test manually:
```bash
-$ ./host_[compiler]/obj/pw_status/status_test
+$ ./out/host_{clang,gcc}_debug/obj/pw_status/test/status_test
```
-Depending on your host OS, `[compiler]` will default to either Clang or GCC.
+Depending on your host OS, the compiler will default to either `clang` or `gcc`.
## Building for a Device
