From d40e1514640e4eeac0edea6e41c6ac22d19b9681 Mon Sep 17 00:00:00 2001
From: davegson <3080765+davegson@users.noreply.github.com>
Date: Wed, 8 Sep 2021 14:08:07 +0200
Subject: [PATCH] Finetune release text

---
 _publications/2021-09-08-portmaster-release-6-22.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_publications/2021-09-08-portmaster-release-6-22.md b/_publications/2021-09-08-portmaster-release-6-22.md
index 100e93b..ed43381 100644
--- a/_publications/2021-09-08-portmaster-release-6-22.md
+++ b/_publications/2021-09-08-portmaster-release-6-22.md
@@ -36,6 +36,6 @@ Maybe you are experiencing issues others have had problems with too. While typin
 
 ![when reporting a bug, the portmaster searches through public issues locally and displays related issues](/assets/img/blog/local-search.png)
 
-Portmaster can do this because it downloads all public issues from our update server when it also updates the malware/trackers/etc filter lists. This way Portmaster never pings GitHub servers while still being able to show related issues locally, which you then can open to read into the reports and discussions.
+Portmaster receives public GitHub issues from the Safing update server, which acts as a proxy. The update server regularly bundles all public issues and then distributes it to Portmaster clients together with intelligence data, such as the newest malware/trackers/etc filter lists. This way, Portmaster never pings GitHub servers while still being able to show related issues locally, which you then can open to read into the reports and discussions.
 
 For the curious, extended docs on how the update system works is planned - you can always [follow the next page]({{ site.next_page_url }}) to keep up to date with our work.