From 2709d943afa301a693ad91014ef8de1bbacc73d3 Mon Sep 17 00:00:00 2001
From: Frank Prins <25006490+PrinsFrank@users.noreply.github.com>
Date: Mon, 10 Aug 2020 17:36:34 +0200
Subject: [PATCH] Move note about when it is not necessary to commit the
 lockfile from the "Updating dependencies to their latest version" section to
 the "Commit your composer.lock file to version control" section

---
 doc/01-basic-usage.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/01-basic-usage.md b/doc/01-basic-usage.md
index 5dd1726bd..45e1cc727 100644
--- a/doc/01-basic-usage.md
+++ b/doc/01-basic-usage.md
@@ -142,6 +142,9 @@ reinstalling the project you can feel confident the dependencies installed are
 still working even if your dependencies released many new versions since then.
 (See note below about using the `update` command.)
 
+> **Note:** For libraries it is not necessary to commit the lock
+> file, see also: [Libraries - Lock file](02-libraries.md#lock-file).
+
 ## Updating dependencies to their latest versions
 
 As mentioned above, the `composer.lock` file prevents you from automatically getting
@@ -165,9 +168,6 @@ If you only want to install, upgrade or remove one dependency, you can explicitl
 php composer.phar update monolog/monolog [...]
 ```
 
-> **Note:** For libraries it is not necessary to commit the lock
-> file, see also: [Libraries - Lock file](02-libraries.md#lock-file).
-
 ## Packagist
 
 [Packagist](https://packagist.org/) is the main Composer repository. A Composer