Remove the repository pinning part, its not a real lock anyway

Signed-off-by: Marek Kubica <[email protected]>

Author: Leonidas-from-XIV

doc/tutorials/dune-package-management/locking.md

@@ -1,13 +1,12 @@
 # Locking Your Dependencies
 
 In the default use-case Dune will automatically determine which packages to
-install, including solving compatible versions and installing their
-dependencies recursively.
+install, by reading the package constrains, determining compatible versions and
+installing the dependencies automatically.
 
 For many projects this is a good and acceptable behavior as users often want to
 use new versions of their dependencies. However some projects might want to
-keep a fixed set of dependencies that is only updated manually. This can be
-done in multiple ways.
+keep a fixed set of (transitive) dependencies that is only updated manually.
 
 ## Create a lock directory manually
 
@@ -25,40 +24,21 @@ Solution for dune.lock:
 ```
 
 Whenever Dune encounters a `dune.lock` folder, it will use the set of
-dependencies defined in the lock. The lock will not be updated until a user
-creates a new lock by running `dune pkg lock` again.
+dependencies defined in the lock. It contains all the metadata about package
+names and versions, their dependencies & source locations that are necesary to
+build the projects dependencies.
 
-On the next build, Dune will read the solution from the `dune.lock` directory,
-download and build the dependencies and then continue on building the project
-as usual.
+On the next build, Dune will read the stored solver solution from the
+`dune.lock` directory, download and build the dependencies and then continue on
+building the project as usual.
+
+The lock directory will not be updated until a new lock directory is created,
+by rerunning `dune pkg lock`.
 
 :::{note}
 This approach is similar to using `opam switch export --full --freeze` to
 export the configuration of a switch.
 :::
 
-## Pin the package repositories to a commit
-
-A way to ensure that dependencies won't change due to package updates is to pin
-the package repositories to a fixed commit.
-
-::::
-
-::::{dropdown} `dune-workspace`
-:icon: file-code
-
-:::{literalinclude} locking/dune-workspace
-:language: dune
-:::
-
-
-::::
-
-On the next build, Dune will check out out these specific two repositories at
-the specified commit and use them for resolving all dependencies. It will then
-download and build the dependencies as usual.
-
-:::{note}
-This approach is similar to pinning OPAM repositories by explicitely setting
-them to known versions using commands like `opam repository add <name> <fixed-url>`.
-:::
+Deleting the lock directory switches Dune back into automatically determining
+dependency versions via the declared package constraints.