Porting over my Personal SFCC DevOps Projects to New SFCC DevOps GitHub Org

Author: manifestinteractive

docs/actions.md

@@ -1,4 +1,4 @@
-![Logo](img/logo.png "Logo")
+![Logo](https://sfccdevops.s3.amazonaws.com/logo-128.png "Logo")
 
 **[↤ Developer Overview](../README.md#developer-overview)**
 

docs/cmd-a11y.md

@@ -1,4 +1,4 @@
-![Logo](img/logo.png "Logo")
+![Logo](https://sfccdevops.s3.amazonaws.com/logo-128.png "Logo")
 
 **[↤ Developer Overview](../README.md#developer-overview)**
 

docs/cmd-auth.md

@@ -1,4 +1,4 @@
-![Logo](img/logo.png "Logo")
+![Logo](https://sfccdevops.s3.amazonaws.com/logo-128.png "Logo")
 
 **[↤ Developer Overview](../README.md#developer-overview)**
 

docs/cmd-help.md

@@ -1,4 +1,4 @@
-![Logo](img/logo.png "Logo")
+![Logo](https://sfccdevops.s3.amazonaws.com/logo-128.png "Logo")
 
 **[↤ Developer Overview](../README.md#developer-overview)**
 

docs/img/logo.png

@@ -1,4 +1,4 @@
-![Logo](img/logo.png "Logo")
+![Logo](https://sfccdevops.s3.amazonaws.com/logo-128.png "Logo")
 
 **[↤ Developer Overview](../README.md)**
 
@@ -23,4 +23,4 @@ Troubleshooting
 
 The default timeout for testing is 30,000 milliseconds.  If you get this error, that means the URL you are testing took longer to load than the maximum timeout.
 
-You can fix this by increasing the timeout by either adding in a CLI argument like this `--timeout 100000` or adding a `"timeout": 100000` to your config file.  You can adjust this number to be as long as you need.
+You can fix this by increasing the timeout by either adding in a CLI argument like this `--timeout 100000` or adding a `"timeout": 100000` to your config file.  You can adjust this number to be as long as you need.