From d436451152e31dc9e980d9ea0458c7943796ded3 Mon Sep 17 00:00:00 2001 From: Martin Rotter Date: Thu, 5 Nov 2020 13:59:16 +0100 Subject: [PATCH] Work on docs. --- resources/docs/Documentation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/resources/docs/Documentation.md b/resources/docs/Documentation.md index da52a3f91..4c01c345c 100644 --- a/resources/docs/Documentation.md +++ b/resources/docs/Documentation.md @@ -14,7 +14,7 @@ * [Downloading new messages](#downloading-new-messages) * [Generating debug log file](#generating-debug-log-file) -![RSS Guard](images/rssguard.png){:width="64px"} + # Foreword First, let me say, that you can contact RSS Guard's lead developer via [e-mail](mailto:rotter.martinos@gmail.com) or just submit a ticket here in the repository. @@ -169,7 +169,7 @@ Here you can find some useful insights into RSS Guard's modus operandi. ## Cleaning database Your RSS Guard's database can grow really big over time, therefore you might need to do its cleanup regularly. There is a dialog `Cleanup database` in `Tools` menu to do just that for you, but note that RSS Guard should run just fine even with thousands of messages. -![`Cleanup database` dialog](images/cleanup-db.png) + ## Portable user data RSS Guard checks "config directory" (this is `C:\Users\\AppData\Local` directory on Windows) for existence of file: