Merge pull request #159 from ipfs-cluster/release-v1.1.1

Release v1.1.1

content/documentation/_index.md

@@ -11,7 +11,7 @@ aliases = [
 
 # Documentation
 
-<div class="tipbox tip">Updated to version <a href="https://github.com/ipfs-cluster/ipfs-cluster/blob/master/CHANGELOG.md">1.1.0 (see the Changelog)</a>.</div>
+<div class="tipbox tip">Updated to version <a href="https://github.com/ipfs-cluster/ipfs-cluster/blob/master/CHANGELOG.md">1.1.1 (see the Changelog)</a>.</div>
 
 Welcome to IPFS Cluster documentation. The different sections of the documentation will explain how to setup, start, and operate a Cluster. Operating a production IPFS Cluster can be a daunting task if you are not familiar with concepts around [IPFS](https://ipfs.io) and peer-2-peer networking ([libp2p](https://libp2p.io) in particular). We aim to provide comprehensive documentation and guides but we are always open for improvements: documentation issues can be submitted to the [ipfs-cluster-website repository](https://github.com/ipfs-cluster/ipfs-cluster-website).
 

content/documentation/reference/api.md

@@ -74,7 +74,7 @@ As a final tip, this table provides a quick summary of methods available.
 |`GET`       |`/monitor/metrics/{metric}`    |Get a list of current metrics seen by this peer |
 |`GET`       |`/health/alerts`       |Display a list of alerts (metric expiration events) |
 |`GET`       |`/health/graph`        |Get connection graph |
-|`GET`       |`/health/alerts`       |Get connection graph |
+|`GET`       |`/health/bandwidth`    |Get bandwidth statistics for libp2p protocols |
 |`POST`      |`/ipfs/gc`             |Perform GC in the IPFS nodes |
 |`POST`      |`/token`               |Generate a new JWT token for current user |
 |`GET`      |`/health`               |Returns 204. Does not require auth. |

content/news/captains_log.md

@@ -49,7 +49,7 @@ Finally, it is very important to remark that we recently finished the [Sharding
 
 During the last weeks we've been working hard on making the first "live" deployment of IPFS Cluster. I am happy to announce that a 10-peer cluster runs on ipfs-gateway nodes, maintaining a >2000-length pinset.
 
-The nodes are distributed, run a vanilla IPFS Cluster docker container mounting a volume with a customized cluster configuration, which uses higher-than-default timeouts and intervals. The injection of the pin-set took a while, but enventually every pin in every node became PINNED. In one occasion, a single IPFS node hanged while pinning. After re-starting the IPFS node in question, all pins in the queue became PIN_ERRORs, but they could easily be fixed with a `recover` operation.
+The nodes are distributed, run a vanilla IPFS Cluster docker container mounting a volume with a customized cluster configuration, which uses higher-than-default timeouts and intervals. The injection of the pin-set took a while, but eventually every pin in every node became PINNED. In one occasion, a single IPFS node hanged while pinning. After re-starting the IPFS node in question, all pins in the queue became PIN_ERRORs, but they could easily be fixed with a `recover` operation.
 
 Additionally, the [IPFS IRC Pinbot](https://github.com/ipfs/pinbot-irc) now supports cluster-pinning, by using the IPFS Cluster proxy to ipfs, which intercepts pin requests and performs them in cluster. This allowed us to reuse the `go-ipfs-api` library to interact with cluster.