chore(docs): clarify wording in env modification section

- Added a clarifying comment for PATH export command
- Rewrote section title, to clearly stated what the commands needed for  
I thought a section about modifying PATH env to make Go globally accessible sounded a bit misleading.
The section doesn't clearly point out that the command `export PATH` should be added to bashrc or zshrc, and should not be executed in terminal session (since persistence is desired). This confusion is created because the section's block combines both command for env modify and reload in one block without much emphasis on where the commands should go to.
This commit is contained in:
TheBedDev 2026-03-10 13:28:06 +00:00 committed by GitHub
commit 833ed03ba1
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -87,9 +87,9 @@ If `wails3 doctor` passes, you're done. [Skip to First App →](/quick-start/fir
sudo pacman -S go
```
**Add to PATH** (add to `~/.bashrc` or `~/.zshrc`):
**Modify enviromental variables to make Go globally accessable**:
```bash
export PATH=$PATH:/usr/local/go/bin:~/go/bin
export PATH=$PATH:/usr/local/go/bin:~/go/bin # Append to the end of ~/.bashrc or ~/.zshrc for persistence.
source ~/.bashrc # Reload
```