cleaning note is not specific to Windows

docs/development.md

@@ -107,6 +107,14 @@ and automatic backups will be disabled - so please don't use this except on a te
 If LOGTERM is set before starting Anki, warnings and error messages that are normally placed
 in the collection2.log file will also be printed on stdout.
 
+## Cleaning
+
+Unlike the old Make system, a "clean build" should almost never be required
+unless you are debugging issues with the build system. But if need to get
+things to a fresh state, you can run `bazel clean --expunge`. Afte doing so,
+make sure you remove the ts/node_modules folder, or subsequent build commands
+will fail with a "no such file or directory node_modules/anki" message.
+
 ## Mixing development and study
 
 You may wish to create a separate profile with File>Switch Profile for use

docs/windows.md

@@ -55,8 +55,9 @@ the first time you run Bazel, restoring it from the Defender settings should all
 
 **Source folder**:
 
-Anki's source files do not need to be in a specific location, but it's best
+Anki's source files do not need to be in a specific location other than on the
-to avoid long paths, as they can cause problems.
+same drive as `\bazel`, but it's best to avoid long paths, as they can cause
+problems.
 
 ## Build failures
 
@@ -91,11 +92,3 @@ Note that where the instructions on that page say "bazel", please use ".\bazel"
 instead. This runs bazel.bat inside the Anki source folder, instead of
 calling Bazel directly. This takes care of setting up the path and output folder
 correctly, which avoids issues with long path names.
-
-## Cleaning notes
-
-Unlike the old Make system, a "clean build" should almost never be required
-unless you are debugging issues with the build system. But if you need to run
-"bazel clean --expunge", make sure you remove the ts/node_modules folder
-afterwards, or it will cause a "no such file or directory node_modules/anki"
-error on the subsequent build on Windows.