From e0520213979abcc5e58330c83b784c6b8d596500 Mon Sep 17 00:00:00 2001 From: David Dias Date: Wed, 22 Aug 2018 09:12:58 +0200 Subject: [PATCH] docs: Improve wording on the Readme --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 52e97d58..0c178e2d 100644 --- a/README.md +++ b/README.md @@ -93,9 +93,9 @@ npm install --save libp2p You can find multiple examples on the [examples folder](/examples) that will guide you through using libp2p for several scenarios. -### Extending libp2p skeleton +### Creating your own libp2p bundle -libp2p becomes very simple and basically acts as a glue for every module that compose this library. Since it can be highly customized, it requires some setup. What we recommend is to have a libp2p build for the system you are developing taking into account in your needs (e.g. for a browser working version of libp2p that acts as the network layer of IPFS, we have a built and minified version that browsers can require). +The libp2p module acts as a glue for every libp2p module that you can use top create your own libp2p bundle. Creating your own libp2p bundle gives you a lot of freedom when it comes to customize it with features and default setup. We recommend creating your own libp2p bundle for the app you are developing that takes in account your needs (e.g. for a browser working version of libp2p that acts as the network layer of IPFS, we have a built one that leverages the Browser transports). **Example:**