From 07ded570e2bd441b390f7e877b1e15bc5ed7792c Mon Sep 17 00:00:00 2001
From: Hafitz Setya <71178188+breakdowns@users.noreply.github.com>
Date: Thu, 11 Feb 2021 19:46:48 +0700
Subject: [PATCH] Update README.md

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

diff --git a/README.md b/README.md
index fa7ea12..cc51deb 100644
--- a/README.md
+++ b/README.md
@@ -27,6 +27,6 @@ python3 generate_drive_token.py
 
 <p><a href="https://heroku.com/deploy?template=https://github.com/breakdowns/slam-mirrorbot"> <img src="https://www.herokucdn.com/deploy/button.svg" alt="Deploy to Heroku" /></a></p>
 
-Note: Doing authorizations ( /authorize command ) through telegram wont be permanent as heroku uses ephemeral filesystem. They will be reset on each dyno boot. As a workaround you can:
+Heroku Note: Doing authorizations ( /authorize command ) through telegram wont be permanent as heroku uses ephemeral filesystem. They will be reset on each dyno boot. As a workaround you can:
 - Make a file authorized_chats.txt and write the user names and chat_id of you want to authorize, each separated by new line
 - Then force add authorized_chats.txt to git and push it to heroku