diff --git a/docs/documentation/style-guide.md b/docs/documentation/style-guide.md
index bb11c1343a696763e74c057d291062aed7533115..f1efaee7615f1c17c5b8f47ff9d0c7b2f10ca887 100644
--- a/docs/documentation/style-guide.md
+++ b/docs/documentation/style-guide.md
@@ -245,3 +245,8 @@ yourusername      git@github.com:yourusername/civicrm-core.git (push)
 ```
 
 Authors should also not put any comments within the examples themselves, whereas any comments should go outside of the code block in regular paragraphs. Where possible each command should be its own comment block. When it is crucial for the user to understand the directory in which to run the command, include a separate code block before hand with a `cd` command.
+
+!!! tip "Write portable shell commands"
+
+    Most system administrators use `bash` as their interactive command-line, but some administrators customize their systems to use `csh`, `zsh`, or similar. 
+    These systems are usually very similar -- but may differ if there are complex conditionals, job-controls, etc. See [bash-hackers.org](http://wiki.bash-hackers.org/scripting/nonportable) for tips on writing portable shell commands.