Update _overviews/scala3-book/scala-for-python-devs.md

Co-authored-by: Lionel Parreaux <lionel.parreaux@gmail.com>

Author: mariogalic

_overviews/scala3-book/scala-for-python-devs.md

@@ -1300,7 +1300,7 @@ cd myapp
 sbt compile
 ```
 
-would automatically resolve all dependencies for that particular project. The location of downloaded dependencies is largely an implementation detail of the build tool that users do not interact with directly. For example, if we delete the whole sbt dependencies cache, one the next compilation of the project, sbt will simply re-resolve automatically all the required dependencies. 
+automatically resolves all dependencies for that particular project. The location of downloaded dependencies is largely an implementation detail of the build tool, and users do not have to interact with these downloaded dependencies directly. For example, if we delete the whole sbt dependencies cache, on the next compilation of the project, sbt simply resolves and downloads all the required dependencies again, automatically.
 
 This differs from Python were by default dependencies are installed at system-wide or user-wide directories, so to obtain an isolated environment on a per-project basis we have to create a corresponding virtual environment. For example, using `venv` module we might create one for a particular project like so