Fixed the lock config

Nyholm · Nyholm · commit b7d19e1d3d9b · 2021-04-22T09:29:35.000+02:00
diff --git a/lock.rst b/lock.rst
@@ -153,11 +153,9 @@ this behavior by using the ``lock`` key like:
                 ->resource('lock', ['%env(LOCK_DSN)%'])
 
                 // named locks
-                ->resource('lock', [
-                    'invoice' => ['semaphore', 'redis://r2.docker'],
-                    'report' => 'semaphore',
-                ])
-            ;
+                ->resource('invoice', ['semaphore', 'redis://r2.docker'])
+                ->resource('report', ['semaphore'])
+                ;
         };
 
 Locking a Resource
@@ -277,13 +275,12 @@ provides :ref:`named lock <reference-lock-resources-name>`:
 
         return static function (FrameworkConfig $framework) {
             $framework->lock()
-                ->resource('lock', [
-                    'invoice' => ['semaphore', 'redis://r2.docker'],
-                    'report' => 'semaphore',
-                ])
+                ->resource('invoice', ['semaphore', 'redis://r2.docker'])
+                ->resource('report', ['semaphore']);
             ;
         };
 
+
 Each name becomes a service where the service id is part of the name of the
 lock (e.g. ``lock.invoice.factory``). An autowiring alias is also created for
 each lock using the camel case version of its name suffixed by ``LockFactory``
