3.0.1: README.md: typo

README.md

@@ -192,8 +192,8 @@ $ safe-rm -rf /path/to
 To keep the performance of `safe-rm` and avoid conducting unnecessary file system traversing, this would not prevent `/path/to/be/protected/foo` from removing.
 
 Pay **ATTENTION** that:
-- Before adding protected rules, i.e. placing the `.gitignore` inside the `"~/.safe-rm/"` directory, it requires `git` to be installed in your environment
-- The protected rules file applies to the root directory (/), which This means that the patterns defined within it need to be relative to the root directory.
+- Before adding protected rules, i.e. placing the `".gitignore"` inside the `"~/.safe-rm/"` directory, it requires `git` to be installed in your environment
+- The `".gitignore"` patterns apply to the root directory (`"/"`), which means that the patterns defined within it need to be relative to the root directory.
 - Avoid adding `/` in the protected rules file, or everything will be protected
 
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "safe-rm",
-  "version": "3.0.0",
+  "version": "3.0.1",
   "description": "A much safer replacement of bash rm with nearly full functionalities and options of the rm command!",
   "bin": {
     "safe-rm": "./bin/rm.sh"