Update README.md

Author: ME-ON1

README.md

@@ -1,25 +1,33 @@
 # LC-SyncInAction
 
-Why take the effort of copy/pasting manually when you can make use of technology to do it for ya.
+Why take the effort of copy/pasting your solution manually when you can make use of technology to do it for ya while you can grind more in Leetcode. 
 
 LC-SyncInAction solves this problem and takes your cookie in his hand to pull and push your Accepted solution everyday.
 
-First run will pull all your Accepted solutions from LC ( which will take **1h 46 min to 2h 30 min approx** ) and create those submission in the current repository in the specified directory (root, if not provided )  
+First run will pull all your Accepted solutions from LC ( which will take **1h 45 min to 2h 30 min approx** ) and create a file of those submission in the current repository in the specified directory (root, if not provided ) 
 
-All the run afterwards will fetch your last 20 Accepted submission everyday at 8AM UTC ( 1:30 IST ) daily.
+Every file created using this tool follows this naming convention : <submission_id>_<title_slug_of_problem> 
+
+All the run afterwards will won't take long as the first run ( will be completed in few seconds :) ) and will fetch last 20 submissions and this step can be customized according to your preferred timing with the help of [schedule](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#scheduled-events)
 
 ### Requirements : 
 
 `cookie` value from the request headers  https://leetcode.com/<your-username> 
 
-This cookie value has to be saved as a repository secret named as `cookieVal` which **has to be** passed as `${{ secrets.cookieVal }}` into action step [you can look here on how to do save a repository secret](https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)
+This cookie value has to be saved in repository secret named as `cookieVal` which **has to be** passed as `${{ secrets.cookieVal }}` into action step [you can look here on how to do save a repository secret](https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)
 
 You can also pass location of directory, to option `solution_location` , where would you like to collect all your solutions ( the default is root directory ). 
 
 ## Usage
 
-Example use case of this action in your WORKFLOWS.
+Make a WORKFLOW file under `.github` folder by any name of your choice and start writing github actions. 
 
+Example use case of action in your WORKFLOWS.
+    
+    on: 
+        schedule: 
+            - cron : '0 8 * * *' # your favourable timing
+    
     jobs : 
       build :
         run-on : ubuntu-latest 
@@ -30,10 +38,18 @@ Example use case of this action in your WORKFLOWS.
             with :
               cookieVal : ${{ secrets.cookieVal }} # secrets.cookieVal coming from repository secret    
               solution_location : 'path/to/directory'  # if any , default is root '.'
+          
+        # dependency, to write newly created files to the root directory of the repository.  
+    
+        - name: pushing the changes!!
+        uses: stefanzweifel/git-auto-commit-action@v4
+        with:
+          commit_message: Adding new LC solutions # or anything you want to add.
 
+If you need to look at examples check [.github/WORKFLOWS](https://github.com/ME-ON1/Leetcode-SyncInAction/tree/main/.github/WORKFLOWS) to understand a bit more.
 
 ## License
 
-The scripts and documentation in this project are released under the [MIT License]()
+The scripts and documentation in this project are released under the [MIT License](https://github.com/ME-ON1/Leetcode-SyncInAction/blob/main/LICENSE)