Fix --no-color documentation (#451)

Author: genevieveluyt

README.md

@@ -218,9 +218,9 @@ Auditors can also be run individually.
 | -f    | --manifest         | Path to the yaml configuration to audit. Only used in manifest mode. You may use `-` to read from stdin.                                               |
 | -n    | --namespace        | Only audit resources in the specified namespace. Not currently supported in manifest mode.                                                             |
 | -g    | --includegenerated | Include generated resources in scan  (such as Pods generated by deployments). If you would like kubeaudit to produce results for generated resources (for example if you have custom resources or want to catch orphaned resources where the owner resource no longer exists) you can use this flag. |
-| -m    | --minseverity      | Set the lowest severity level to report (one of "error", "warning", "info") (default "info")                                                           |
-| -e    | --exitcode         | Exit code to use if there are results with severity of "error". Conventionally, 0 is used for success and all non-zero codes for an error. (default 2) |
-|       | --no-color         | Don't use colors in the output (the default is true) |
+| -m    | --minseverity      | Set the lowest severity level to report (one of "error", "warning", "info") (default is "info")                                                           |
+| -e    | --exitcode         | Exit code to use if there are results with severity of "error". Conventionally, 0 is used for success and all non-zero codes for an error. (default is 2) |
+|       | --no-color         | Don't use colors in the output (default is false) |
 
 ## Configuration File