From 88ea30ea53a48ca2b3c653051188a4f282747890 Mon Sep 17 00:00:00 2001
From: Areku95 <35227123+Areku95@users.noreply.github.com>
Date: Mon, 8 Jan 2018 15:55:47 +0100
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index df28345..aba0a76 100644
--- a/README.md
+++ b/README.md
@@ -9,7 +9,7 @@ So, naturally, I searched a solution to replicate this for Synology HyperBackup.
 
 First of all, I'm using CMS (Centralized Managed System) | https://www.synology.com/knowledgebase/DSM/help/CMS/cms_desc
 
-This allows to manage multiple NAS, and, for this case, collect HyperBackup Notifications. CMS use a SQL Lite DataBase to store notifications. This means that it's very simple to query this kind of DataBase.
+This Synology package allows to manage multiple NAS, and, for this case, collect HyperBackup Notifications. CMS use a SQL Lite DataBase to store notifications. This means that it's very simple to query this kind of DataBase.
 
 Imagine we have a dozain of NAS, all connected to the CMS host. Backup Notifications are enabled on each NAS.
 The host will receive all notifications relating to backups.