diff --git a/.wordlist.txt b/.wordlist.txt index 8def358..e8b56ab 100644 --- a/.wordlist.txt +++ b/.wordlist.txt @@ -27,6 +27,7 @@ BoltDB boolean Bugfixes busybox +caching CD certDir checksum diff --git a/docs/articles/clustering.md b/docs/articles/clustering.md index 36ece28..73ad728 100644 --- a/docs/articles/clustering.md +++ b/docs/articles/clustering.md @@ -176,7 +176,7 @@ An existing zot cluster (see [Figure 1](#figure1)) can easily be expanded with n For easy scaling, the following conditions must be met: -- All zot servers in the cluster use remote storage at a single shared S3 backend. There is no local cacheing in the zot servers. +- All zot servers in the cluster use remote storage at a single shared S3 backend. There is no local caching in the zot servers. - Each repo is served by one zot server, and that server is solely responsible for serving all images of that repo. - A repo in storage can be written to only by the zot server associated with that repo. - The URI format sent to the load balancer must be /v2//: