diff --git a/README.md b/README.md
index 541937e2..9e9ee22e 100644
--- a/README.md
+++ b/README.md
@@ -93,13 +93,15 @@ jobs:
       # Run Linter against code base #
       ################################
       - name: Lint Code Base
-        uses: github/super-linter@v2.0.0
+        uses: docker://github/super-linter:v2.0.0
         env:
           VALIDATE_ALL_CODEBASE: false
           VALIDATE_ANSIBLE: false
 ...
 ```
 
+**NOTE:** Using the line:`uses: docker://github/super-linter:v2.0.0` will pull the image down from **DockerHub** and run the **GitHub Super-Linter**. Using the line: `uses: github/super-linter@v2.0.0` will build and compile the **GitHub Super-Linter** at build time. This can be far more costly in time...
+
 ## Environment variables
 The super-linter allows you to pass the following `ENV` variables to be able to trigger different functionality.
 
diff --git a/TEMPLATES/README.md b/TEMPLATES/README.md
index bcd84269..c1ed7152 100644
--- a/TEMPLATES/README.md
+++ b/TEMPLATES/README.md
@@ -2,7 +2,5 @@
 
 The files in this folder are template rules for the linters that will run against your code base. If you chose to copy these to your local repository in the directory: `.github/` they will be used at runtime. If they are not present, they will be used by default in the linter run.  
 
-
-
 The file(s) will be parsed at run time on the local branch to load all rules needed to run the **Super-Linter** **GitHub** Action.  
 The **GitHub** Action will inform the user via the **Checks API** on the status and success of the process.