docs: fix incorrect description in custom repo example

automatically stop the node in the custom repo example

docs: update custom repo example

Author: jacobheun

examples/custom-ipfs-repo/README.md

@@ -5,7 +5,6 @@ This example shows you how to customize your repository, including where your da
 * If you want to store data somewhere that’s not on your local disk, like S3, a Redis instance, a different machine on your local network, or in your own database system, like MongoDB or Postgres, you might use a custom datastore.
 * If you have multiple browser windows or workers sharing the same IPFS storage, you might want to use a custom lock to coordinate between them. (Locking is currently only used to ensure a single IPFS instance can access a repo at a time. This check is done on `repo.open()`. A more complex lock, coupled with a custom datastore, could allow for safe writes to a single datastore from multiple IPFS nodes.)
 
-
 You can find full details on customization in the [IPFS Repo Docs](https://github.com/ipfs/js-ipfs-repo#setup).
 
 ## Run this example
@@ -18,7 +17,7 @@ You can find full details on customization in the [IPFS Repo Docs](https://githu
 ## Other Options
 
 ### Custom Repo Lock
-This example sets the repo locker to `false`, preventing any locking from happening. If you would like to control how locking happens, such as with a centralized S3 IPFS Repo, you can pass in your own custom lock. See [custom-lock.js](./custom-lock.js) for an example of a custom lock that can be used for [datastore-s3](https://github.com/ipfs/js-datastore-s3).
+This example uses one of the locks that comes with IPFS Repo. If you would like to control how locking happens, such as with a centralized S3 IPFS Repo, you can pass in your own custom lock. See [custom-lock.js](./custom-lock.js) for an example of a custom lock that can be used for [datastore-s3](https://github.com/ipfs/js-datastore-s3).
 
 ```js
 const S3Lock = require('./custom-lock')

examples/custom-ipfs-repo/index.js

@@ -90,4 +90,10 @@ node.on('ready', () => {
     .catch((err) => {
       console.log('File Processing Error:', err)
     })
+    // After everything is done, shut the node down
+    // We don't need to worry about catching errors here
+    .then(() => {
+      console.log('\n\nStopping the node')
+      return node.stop()
+    })
 })