aboutsummaryrefslogtreecommitdiff
path: root/docs/config/howto_mediaproxy.md
diff options
context:
space:
mode:
authorkaniini <ariadne@dereferenced.org>2019-08-04 04:32:09 +0000
committerkaniini <ariadne@dereferenced.org>2019-08-04 04:32:09 +0000
commitb9497ead3513ba3b93e9a4549e482f4a720aa83d (patch)
treec23fe2d35bdf2f8aa3943ffe34eaa37cf8297eab /docs/config/howto_mediaproxy.md
parentb1fb5b93aeea5ae95c9d4cfc3ded8e330f2b0a66 (diff)
parent9b9453ceaf492ef3af18c12ce67e144a718fd65a (diff)
downloadpleroma-b9497ead3513ba3b93e9a4549e482f4a720aa83d.tar.gz
Merge branch 'develop' into 'develop'
Fix a stale link and a few typos See merge request pleroma/pleroma!1529
Diffstat (limited to 'docs/config/howto_mediaproxy.md')
-rw-r--r--docs/config/howto_mediaproxy.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/config/howto_mediaproxy.md b/docs/config/howto_mediaproxy.md
index ed70c3ed4..16c40c5db 100644
--- a/docs/config/howto_mediaproxy.md
+++ b/docs/config/howto_mediaproxy.md
@@ -1,8 +1,8 @@
# How to activate mediaproxy
## Explanation
-Without the `mediaproxy` function, Pleroma don't store any remote content like pictures, video etc. locally. So every time you open Pleroma, the content is loaded from the source server, from where the post is coming. This can result in slowly loading content or/and increased bandwidth usage on the source server.
-With the `mediaproxy` function you can use the cache ability of nginx, to cache these content, so user can access it faster, cause it's loaded from your server.
+Without the `mediaproxy` function, Pleroma doesn't store any remote content like pictures, video etc. locally. So every time you open Pleroma, the content is loaded from the source server, from where the post is coming. This can result in slowly loading content or/and increased bandwidth usage on the source server.
+With the `mediaproxy` function you can use nginx to cache this content, so users can access it faster, because it's loaded from your server.
## Activate it