docs: factory instead of generator

Author: jacobheun

README.md

@@ -240,9 +240,9 @@ Creates and returns an instance of an IPFS node. Use the `options` argument to s
 
 - `libp2p` (object or function(ipfs, config)) add custom modules to the libp2p stack of your node
 
-    The libp2p option allows you to build your libp2p node by configuration, or via a generator. If you are looking to just modify the below options, using the object format is the quickest way to get the default features of libp2p. If you need to create a more customized libp2p node, such as with custom transports or peer/content routers that need some of the ipfs data on startup, a generator is a great way to achieve this.
+    The libp2p option allows you to build your libp2p node by configuration, or via a factory. If you are looking to just modify the below options, using the object format is the quickest way to get the default features of libp2p. If you need to create a more customized libp2p node, such as with custom transports or peer/content routers that need some of the ipfs data on startup, a factory is a great way to achieve this.
 
-    You can see the generator in action in the [custom libp2p example](examples/custom-libp2p).
+    You can see the factory in action in the [custom libp2p example](examples/custom-libp2p).
 
     - `modules` (object):
         - `transport` (Array<[libp2p.Transport](https://github.com/libp2p/interface-transport)>): An array of Libp2p transport classes/instances to use _instead_ of the defaults. See [libp2p/interface-transport](https://github.com/libp2p/interface-transport) for details.

examples/custom-libp2p/README.md

@@ -1,6 +1,6 @@
 # Customizing the libp2p node
 
-This example shows you how to make full use of the ipfs configuration to create a libp2p generator function. As IPFS applications become more complex, their needs for a custom libp2p node also grow. Instead of fighting with configuration options, you can use your own libp2p generator to get exactly what you need. This example shows you how.
+This example shows you how to make full use of the ipfs configuration to create a libp2p factory function. As IPFS applications become more complex, their needs for a custom libp2p node also grow. Instead of fighting with configuration options, you can use your own libp2p factory to get exactly what you need. This example shows you how.
 
 ## Run this example
 

examples/custom-libp2p/index.js

@@ -13,13 +13,13 @@ const SECIO = require('libp2p-secio')
 const assert = require('assert')
 
 /**
- * This is the generator we will use to generate our fully customized libp2p node.
+ * This is the factory we will use to create our fully customized libp2p node.
  *
  * @param {*} _ipfsNode The ipfs node. This houses the PeerInfo and PeerBook that modules may need
  * @param {*} _ipfsConfig The config that is fetched from the ipfs-repo
  * @returns {Libp2p} Our new libp2p node
  */
-const libp2pGenerator = (_ipfsNode, _ipfsConfig) => {
+const libp2pFactory = (_ipfsNode, _ipfsConfig) => {
   // Set convenience variables to clearly showcase some of the useful things that are available
   const peerInfo = _ipfsNode._peerInfo
   const peerBook = _ipfsNode._peerBook
@@ -89,9 +89,9 @@ const libp2pGenerator = (_ipfsNode, _ipfsConfig) => {
   })
 }
 
-// Now that we have our custom generator, let's start up the ipfs node!
+// Now that we have our custom factory, let's start up the ipfs node!
 const node = new IPFS({
-  libp2p: libp2pGenerator
+  libp2p: libp2pFactory
 })
 
 // Listen for the node to start, so we can log out some metrics