move notes a bit down

Author: radoering

docs/cli.md

@@ -475,9 +475,19 @@ poetry init
 The `install` command reads the `pyproject.toml` file from the current project,
 resolves the dependencies, and installs them.
 
+```bash
+poetry install
+```
+
+If there is a `poetry.lock` file in the current directory,
+it will use the exact versions from there instead of resolving them.
+This ensures that everyone using the library will get the same versions of the dependencies.
+
+If there is no `poetry.lock` file, Poetry will create one after dependency resolution.
+
 {{% note %}}
 **When to use `install` vs `update`:**
-- Use `poetry install` to install dependencies as specified in `poetry.lock` (or resolve dependencies and create the lock file if it's missing).
+- Use `poetry install` to install dependencies as specified in `poetry.lock` (or resolve dependencies and create the lock file if it is missing).
   This is what you run after cloning a project. For reproducible installs, prefer `poetry sync`,
   which also removes packages that are not in the lock file.
 - Use `poetry update` when you want to update dependencies to their latest versions (within the constraints from the `pyproject.toml`)
@@ -492,16 +502,6 @@ system site-packages available in your virtual environment, you should use `poet
 because `poetry sync` will normally not work well in these cases.
 {{% /note %}}
 
-```bash
-poetry install
-```
-
-If there is a `poetry.lock` file in the current directory,
-it will use the exact versions from there instead of resolving them.
-This ensures that everyone using the library will get the same versions of the dependencies.
-
-If there is no `poetry.lock` file, Poetry will create one after dependency resolution.
-
 If you want to exclude one or more dependency groups for the installation, you can use
 the `--without` option.