diff options
| author | Quentin Dufour <quentin@deuxfleurs.fr> | 2021-12-08 14:40:14 +0100 |
|---|---|---|
| committer | Quentin Dufour <quentin@deuxfleurs.fr> | 2021-12-08 14:40:14 +0100 |
| commit | e9358054acb653142203b3580b70e6be20a91c63 (patch) | |
| tree | b7b7235d59052f6c4bad745881c846d446800f1b /doc | |
| parent | f9e5520ffb74bdb222a114245284d32e42373a57 (diff) | |
| download | garage-e9358054acb653142203b3580b70e6be20a91c63.tar.gz garage-e9358054acb653142203b3580b70e6be20a91c63.zip | |
Typos and dead links
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/book/src/connect/apps.md | 2 | ||||
| -rw-r--r-- | doc/book/src/connect/index.md | 2 | ||||
| -rw-r--r-- | doc/book/src/design/benchmarks.md | 2 | ||||
| -rw-r--r-- | doc/book/src/intro.md | 2 |
4 files changed, 4 insertions, 4 deletions
diff --git a/doc/book/src/connect/apps.md b/doc/book/src/connect/apps.md index 20075f43..14d69ef8 100644 --- a/doc/book/src/connect/apps.md +++ b/doc/book/src/connect/apps.md @@ -109,7 +109,7 @@ Do not change the `use_path_style` and `legacy_auth` entries, other configuratio Peertube proposes a clever integration of S3 by directly exposing its endpoint instead of proxifying requests through the application. In other words, Peertube is only responsible of the "control plane" and offload the "data plane" to Garage. In return, this system is a bit harder to configure, especially with Garage that supports less feature than other older S3 backends. -We show that it is still possible to configure Garage with Peertube, allowing you to spread the load and the bandiwdth usage on the Garage cluster. +We show that it is still possible to configure Garage with Peertube, allowing you to spread the load and the bandwidth usage on the Garage cluster. ### Enable path-style access by patching Peertube diff --git a/doc/book/src/connect/index.md b/doc/book/src/connect/index.md index 703b19d4..60a3b03b 100644 --- a/doc/book/src/connect/index.md +++ b/doc/book/src/connect/index.md @@ -1,4 +1,4 @@ -# Connect it to... +# Integrations Garage implements the Amazon S3 protocol, which makes it compatible with many existing software programs. diff --git a/doc/book/src/design/benchmarks.md b/doc/book/src/design/benchmarks.md index 5a63f902..a219a3ce 100644 --- a/doc/book/src/design/benchmarks.md +++ b/doc/book/src/design/benchmarks.md @@ -19,7 +19,7 @@ This serie of benchmarks quantifies the impact of this design choice. We start with a controlled environment, all the instances are running on the same (powerful enough) machine. To control the network latency, we simulate the network with [mknet](https://git.deuxfleurs.fr/trinity-1686a/mknet) (a tool we developped, based on `tc` and the linux network stack). -To mesure S3 endpoints latency, we use our own tool [s3lat](git.deuxfleurs.fr/quentin/s3lat/) to observe only the intra-cluster latency and not some contention on the nodes (CPU, RAM, disk I/O, network bandwidth, etc.). +To mesure S3 endpoints latency, we use our own tool [s3lat](https://git.deuxfleurs.fr/quentin/s3lat/) to observe only the intra-cluster latency and not some contention on the nodes (CPU, RAM, disk I/O, network bandwidth, etc.). Compared to other benchmark tools, S3Lat sends only one (small) request at the same time and measures its latency. We selected 5 standard endpoints that are often in the critical path: ListBuckets, ListObjects, GetObject, PutObject and RemoveObject. diff --git a/doc/book/src/intro.md b/doc/book/src/intro.md index 10f9c0a2..5d6e2cf0 100644 --- a/doc/book/src/intro.md +++ b/doc/book/src/intro.md @@ -22,7 +22,7 @@ Garage is an **open-source** distributed **storage service** you can **self-host </p> <p align="center" style="text-align:center; margin-bottom: 5rem;"> -<a href="/design/use_cases.html">⮞ learn more about use cases ⮜</a> +<a href="/design/goals.html#use-cases">⮞ learn more about use cases ⮜</a> </p> Garage implements the **[Amazon S3 API](https://docs.aws.amazon.com/AmazonS3/latest/API/Welcome.html)** and thus is already **compatible** with many applications: |