Move most important takeaway to the top

Author: mariogalic

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

@@ -1293,25 +1293,25 @@ Follow the links below for more details:
 
 ## How to setup a virtual environnement in Scala?
 
-By default Python and Python modules are installed at system-wide directories or user-wide directories. Virtual environments are a way of obtaining an isolated environment on a per-project basis. Typical flow to configure the virtual environment using for example `venv` module in Python might be something like so
+In Scala there is no need to explicitly setup an equivalent of Python's virtual environnement. By default, build tools manage project's dependencies such that user does not have to think about site directories. For example using `sbt` build tool we specify dependencies inside `build.sbt` file under `libraryDependencies` setting, then executing
 
 ```
 cd myapp
-python3 -m venv myapp-env
-source myapp-env/bin/activate
-pip install -r requirements.txt
+sbt compile
 ```
 
-This installs all the dependencies under project's directory `myapp/myapp-env` and alters the shell environmental variable `PATH` to look up dependencies from `myapp-env`.
+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 were to delete the whole sbt dependencies cache, one the next compilation of the project, sbt will simply re-resolve automatically all the required dependencies.
 
-In Scala there is no need to explicitly setup an equivalent of Python's virtual environnement. By default, build tools manage project's dependencies such that user does not have to explicitly think about site directories. For example using `sbt` build tool we specify dependencies inside `build.sbt` file under `libraryDependencies` setting, then executing
+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
 
 ```
 cd myapp
-sbt compile
+python3 -m venv myapp-env
+source myapp-env/bin/activate
+pip install -r requirements.txt
 ```
 
-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 were to delete the whole sbt dependencies cache, one next compilation of the project, sbt will simply re-resolve automatically all the required dependencies.
+This installs all the dependencies under project's directory `myapp/myapp-env` and alters the shell environmental variable `PATH` to look up dependencies from `myapp-env`.
 
 
 [collections-classes]: {% link _overviews/scala3-book/collections-classes.md %}