libp2p 2.7.1-a4f0db1e9 → 2.7.2-5b084e968

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -56,7 +56,7 @@ We are in the process of writing better documentation, blog posts, tutorials and
56
56
  - Articles
57
57
  - [The overview of libp2p](https://github.com/libp2p/libp2p#description)
58
58
 
59
- To sum up, libp2p is a "network stack" -- a protocol suite -- that cleanly separates concerns, and enables sophisticated applications to only use the protocols they absolutely need, without giving up interoperability and upgradeability. libp2p grew out of IPFS, but it is built so that lots of people can use it, for lots of different projects.
59
+ To sum up, libp2p is a "network stack" -- a protocol suite -- that cleanly separates concerns, and enables sophisticated applications to only use the protocols they absolutely need, without giving up interoperability and upgradability. libp2p grew out of IPFS, but it is built so that lots of people can use it, for lots of different projects.
60
60
 
61
61
  # Roadmap
62
62
 
@@ -98,7 +98,7 @@ You can find multiple examples on the [examples repo](https://github.com/libp2p/
98
98
  ## Run unit tests
99
99
 
100
100
  ```sh
101
- # run all the unit tsts
101
+ # run all the unit tests
102
102
  > npm test
103
103
 
104
104
  # run just Node.js tests
@@ -171,7 +171,7 @@ And [many others...](https://github.com/libp2p/js-libp2p/network/dependents)
171
171
  The libp2p implementation in JavaScript is a work in progress. As such, there are a few things you can do right now to help out:
172
172
 
173
173
  - Go through the modules and **check out existing issues**. This would be especially useful for modules in active development. Some knowledge of IPFS/libp2p may be required, as well as the infrastructure behind it - for instance, you may need to read up on p2p and more complex operations like muxing to be able to help technically.
174
- - **Perform code reviews**. Most of this has been developed by @diasdavid, which means that more eyes will help a) speed the project along b) ensure quality and c) reduce possible future bugs.
174
+ - **Perform code reviews**. More eyes will help a) speed the project along b) ensure quality and c) reduce possible future bugs.
175
175
  - **Add tests**. There can never be enough tests.
176
176
 
177
177
  # API Docs