Skip to content

Commit 7a426de

Browse files
jhedbergkartben
authored andcommitted
doc: gsg: Clarify west workspace naming requirements
The way the instructions were formulated, it was possible for someone to get the impression that only a specific name of the workspace is allowable. Clarify that the name and location can be freely chosen. Signed-off-by: Johan Hedberg <johan.hedberg@silabs.com>
1 parent f62079b commit 7a426de

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

doc/develop/getting_started/index.rst

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -207,8 +207,10 @@ Get Zephyr and install Python dependencies
207207
******************************************
208208

209209
Next, clone Zephyr and its :ref:`modules <modules>` into a new :ref:`west
210-
<west>` workspace named :file:`zephyrproject`. You'll also install Zephyr's
211-
additional Python dependencies in a `Python virtual environment`_.
210+
<west>` workspace. In the following instructions the name :file:`zephyrproject`
211+
is used for the workspace, however in practice its name and location can be freely
212+
chosen. You'll also install Zephyr's additional Python dependencies in a
213+
`Python virtual environment`_.
212214

213215
.. _Python virtual environment: https://docs.python.org/3/library/venv.html
214216

0 commit comments

Comments
 (0)