Improve wording

STYLEGUIDE.md

@@ -1,12 +1,12 @@
-## Bash Styleguide
+## Bash Style Guide
 
 If you've not done much Bash development before you may find these debugging tips useful: http://wiki.bash-hackers.org/scripting/debuggingtips.
 
 ---
 ##### Scripts must start with `#!/usr/bin/env bash`
 
 ---
-##### Scripts must use `set -e`
+##### Use `set -e`
 
 If the return value of a command can be ignored, suffix it with `|| true`:
 
@@ -19,7 +19,7 @@ command_that_should_not_fail
 Note that ignoring an exit status with `|| true` is not a good practice though. Generally speaking, it's better to handle the error.
 
 ---
-##### Scripts should not check exit status via `$?` manually
+##### Avoid manually checking exit status with `$?`
 
 Rely on `set -e` instead:
 
@@ -40,7 +40,7 @@ fi
 ```
 
 ---
-##### Scripts must include a usage, description and optional examples
+##### Include a usage, description and optional examples
 
 Use this format:
 
@@ -87,15 +87,15 @@ fi
 ```
 
 ---
-##### Scripts should not use Bash arrays
+##### Avoid Bash arrays
 
 Main issues:
 
 * Portability
 * Important bugs in Bash versions < 4.3
 
 ---
-##### Scripts should use `test` or `[` whenever possible
+##### Use `test` or `[` whenever possible
 
 ```bash
 test -f /etc/passwd
@@ -132,7 +132,7 @@ done
 ```
 
 ---
-##### Scripts should use `$[x+y*z]` for mathematical expressions
+##### Use `$[x+y*z]` for mathematical expressions
 
 ```bash
 local n=1
@@ -144,7 +144,7 @@ n=$(($n+1))
 ```
 
 ---
-##### Scripts should use variables sparingly
+##### Use variables sparingly
 
 Short paths and other constants should be repeated liberally throughout code since they
 can be search/replaced easily if they ever change.
@@ -163,7 +163,9 @@ rsync /data/user/db remote:/data/user/db
 ```
 
 ---
-##### Scripts should use lowercase variables for locals, and uppercase for variables inherited or exported via the environment
+##### Use lowercase and uppercase variable names
+
+Use lowercase variables for locals and internal veriables, and uppercase for variables inherited or exported via the environment
 
 ```bash
 #!/usr/bin/env bash
@@ -176,7 +178,7 @@ git rev-list
 ```
 
 ---
-##### Scripts should use `${var}` for interpolation only when required
+##### Use `${var}` for interpolation only when required
 
 ```bash
 greeting=hello
@@ -185,7 +187,7 @@ echo ${greeting}world
 ```
 
 ---
-##### Scripts should use functions sparingly, opting for small/simple/sequential scripts instead whenever possible
+##### Use functions sparingly, opting for small/simple/sequential scripts instead whenever possible
 
 When defining functions, use the following style:
 
@@ -198,7 +200,7 @@ my_function() {
 ```
 
 ---
-##### Scripts should use `<<heredocs` when dealing with multi-line strings
+##### Use `<<heredocs` when dealing with multi-line strings
 
 - `<<eof` and `<< eof` will allow interpolation
 - `<<"eof"` and `<<'eof'` will disallow interpolation
@@ -220,7 +222,7 @@ eof
 ```
 
 ---
-##### Scripts should quote variables that could reasonably have a space now or in the future
+##### Quote variables that could reasonably have a space now or in the future
 
 ```bash
 if [ ! -z "$packages" ]; then
@@ -229,7 +231,7 @@ fi
 ```
 
 ---
-##### Scripts should use two space indentation
+##### Use two space indentation
 
 ---
 ##### Scripts should not produce errors or warnings when checked with ShellCheck
@@ -238,7 +240,7 @@ Use inline comments to disable specific tests, and explain why the test has been
 
 ```bash
 hexToAscii() {
-  # shellcheck disable=SC2059 # $1 needs to be interpretted as a formatted string
+  # shellcheck disable=SC2059 # $1 needs to be interpreted as a formatted string
   printf "\x$1"
 }
 ```