From 908df202b9d220cdb44f5b34d342f53d04f49242 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org>
Date: Wed, 13 Nov 2019 19:28:48 -0500
Subject: [PATCH] fix cache page based on linus feedback

---
 tsa/howto/cache.mdwn | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/tsa/howto/cache.mdwn b/tsa/howto/cache.mdwn
index 6111082e..f3c9f5ea 100644
--- a/tsa/howto/cache.mdwn
+++ b/tsa/howto/cache.mdwn
@@ -1,6 +1,6 @@
-A caching service is a set of services keeping a smaller cache of
+A caching service is a set of reverse proxies keeping a smaller cache of
 content in memory to speed up access to resources on a slower backend
-server.
+web server.
 
 [[!toc levels=3]]
 
@@ -15,7 +15,8 @@ over or close to 90%.
 ## Traffic inspection
 
 A quick way to see how much traffic is flowing through the cache is to
-fire up [slurm](https://screenshots.debian.net/package/slurm) on the public interface:
+fire up [slurm](https://screenshots.debian.net/package/slurm) on the public interface of the caching server
+(currently `cache01` and `cache-02`):
 
     slurm -i eth0
 
@@ -87,7 +88,7 @@ geographically distinct areas that run a webserver acting as a
 the [proxy module](https://nginx.org/en/docs/http/ngx_http_proxy_module.html) for the <https://blog.torproject.org/> website
 (and eventually others, see [ticket #32462](https://trac.torproject.org/projects/tor/ticket/32462)). DNS for the site
 points to `cache.torproject.org`, an alias for the caching servers,
-which are currently two: `cache01.torproject.org` [sic] and
+which are currently two: `cache01.torproject.org` [[sic](https://en.wikipedia.org/wiki/Sic)] and
 `cache-02`. An HTTPS certificate for the site was issued through
 [[letsencrypt]]. Like the Nginx configuration, the certificate is
 deployed by Puppet in the `roles::cache` class.
-- 
GitLab