aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPierce McGoran <pleroma@mokou.io>2019-08-04 03:12:38 +0000
committerPierce McGoran <pleroma@mokou.io>2019-08-04 03:12:38 +0000
commit9b9453ceaf492ef3af18c12ce67e144a718fd65a (patch)
treec23fe2d35bdf2f8aa3943ffe34eaa37cf8297eab
parentc10a3e035b2761b1d8419d39b8392d499abe9aae (diff)
downloadpleroma-9b9453ceaf492ef3af18c12ce67e144a718fd65a.tar.gz
Fix some typos and rework a few lines in 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