diff --git a/.github/site/src/SUMMARY.md b/.github/site/src/SUMMARY.md
index 65b56c1..f17f98b 100644
--- a/.github/site/src/SUMMARY.md
+++ b/.github/site/src/SUMMARY.md
@@ -1,6 +1,6 @@
 ./ Summary
 
-- [Overview](./overview.md)
+- [Start](./overview.md)
     - [System requirements](./system-requirements.md)
     - [Installation](./installation.md)
     - [Setup](./setup.md)
diff --git a/.github/site/src/overview.md b/.github/site/src/start.md
similarity index 100%
rename from .github/site/src/overview.md
rename to .github/site/src/start.md
diff --git a/README.md b/README.md
index 47e23cf..afe482b 100644
--- a/README.md
+++ b/README.md
@@ -1,15 +1,17 @@
 # Goral
 
+> Save your time with Goral to setup the whole observability/monitoring stack when you start
+
 Observability toolkit for small projects. Easy-to-use and compatible with industry standards.
 
 ## Overview
 
-Goral is a simple observability daemon developed with the following idea in mind: when you have your favorite application in its infantry, you usually don't need a full-blown observability toolkit (which require much more setup, maintenance and resources) around as the amount of data is not so huge. It is especially true for pet projects when you just want to test an idea and deploy the app at some free-tier commodity VPS.
+Goral is a simple observability daemon developed with the following idea in mind: when you have your favorite application in its infantry, you usually don't need a full-blown observability toolkit (which requires much more setup, maintenance and resources) around as the amount of data is not so huge. It is especially true for pet projects when you just want to test an idea and deploy the app at some free-tier commodity VPS.
 
 So Goral provides the following features being deployed next to your app(s):
 * [Periodic healthchecks](https://maksimryndin.github.io/goral/healthcheck.html) (aka [liveness probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/))
 * [Metrics collection](https://maksimryndin.github.io/goral/metrics.html) (fully compatible with Prometheus to be easily replaced with more advanced stack as your project grows)
-* Logs collection (importing logs from stdout/stderr of the target process)
+* [Logs](https://maksimryndin.github.io/goral/logs.html) collection (importing logs from stdout/stderr of the target process)
 * [System telemetry](https://maksimryndin.github.io/goral/system.html) (CPU, Memory, Free/Busy storage space etc)
 * A general key-value appendable log storage (see [the user case](https://maksimryndin.github.io/goral/kv-log.html))
 * Features are modular - all [services](https://maksimryndin.github.io/goral/services.html) are switched on/off in the configuration.
@@ -17,7 +19,7 @@ So Goral provides the following features being deployed next to your app(s):
 * You can configure different messengers and/or channels for every [service](https://maksimryndin.github.io/goral/services.html) to get notifications on errors, liveness updates, system resources overlimit etc
 * All the data collected is stored in Google Sheet with an automatic quota and limits checks and automatic data rotation - old data is deleted with a preliminary notification via configured messenger (see below). That way you don't have to buy a separate storage or overload your app VPS with Prometheus, ELK etc. Just a lean process next to your brilliant one which just sends app data in batches to Google Sheets for your ease of use. Google Sheets allow you to build your own diagrams over the metrics and analyse them, analyse liveness statistics and calculate uptime etc.
 * You can configure different spreadsheets and messengers for every service
-* You can configure [rules](https://maksimryndin.github.io/goral/rules.html) for notifications by messenger for any data.
+* You can configure [rules](https://maksimryndin.github.io/goral/rules.html) for notifications by messengers for any data.
 
 ## Licence