From d24939b3abae34519ea745d977dc1d86197f019e Mon Sep 17 00:00:00 2001 From: John Gardner Date: Wed, 22 Dec 2021 18:42:22 +1100 Subject: [PATCH] Fix caps and missing hyphens --- SC1015.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/SC1015.md b/SC1015.md index 8dee099..16ce090 100644 --- a/SC1015.md +++ b/SC1015.md @@ -14,18 +14,18 @@ echo "hello world" ### Rationale: -Blog software and word processors frequently replaces ASCII quotes `""` with fancy Unicode quotes, `“”`. To bash, Unicode quotes are considered regular literals and not quotes at all. +Blog software and word processors frequently replaces ASCII quotes `""` with fancy Unicode quotes, `“”`. To Bash, Unicode quotes are considered regular literals and not quotes at all. Simply delete them and retype them in your editor. ### Status: -This error was retired after 0.4.5. In this version and earlier, ShellCheck parsed slanted quotes as a valid double quote. This meant that the warning could not simply be ignored. It has since been replaced by [[SC1110]] (outside quotes) and [[SC1111]] (inside double quotes). +This error was retired after 0.4.5. In this version and earlier, ShellCheck parsed slanted quotes as a valid double quote. This meant that the warning could not simply be ignored. It has since been replaced by [[SC1110]] (outside quotes) and [[SC1111]] (inside double-quotes). ### Exceptions -If you really want literal Unicode double quotes, you can put them in single quotes (or Unicode single quotes in double quotes) to make shellcheck ignore them, e.g., +If you really want literal Unicode double quotes, you can put them in single-quotes (or Unicode single-quotes in double-quotes) to make ShellCheck ignore them, e.g., ```sh printf 'Warning: “wakeonlan” is not installed.\n' -``` \ No newline at end of file +```