The first one does say the directory to create it in.
The second one isn't relevant, workspaces are only for modules.
The third one specifies that go.work files define their own workspaces, there is nowhere in particular that you need to place them.

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.

For questions please refer to https://github.com/golang/go/wiki/Questions

Thanks Sean,

Not sure I agree with the assessment, but per your last comment, I added the bug here because the page itself links to "report an issue". Maybe that should link to what you have above.

https://go.dev/doc/tutorial/workspaces (see footer of page)

2. From the command prompt, create a directory for your code called workspace.

$ mkdir workspace
$ cd workspace

...
Initialize the workspace
In the workspace directory, run:

$ go work init ./hello

Sean,
I did indeed see that. What I didn't see is why (or is that the standard place going forward). I know at some point some blogs are high-level tutorials and others are the details. Just trying to figure out what is the expected/right way, but felt like it just wasn't clear. Will keep at it, I am probably just bouncing around too many pages. Thanks again for your time.