From 356dcb20cef387a5eea5f8fcbfe123b24e3bb928 Mon Sep 17 00:00:00 2001 From: Dimitris Apostolou Date: Fri, 12 Nov 2021 23:33:37 +0200 Subject: github #82: Fix typos --- Etc/FAQ.yo | 4 ++-- Etc/NEWS-4.3 | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'Etc') diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo index 20f6449f1..235a205d3 100644 --- a/Etc/FAQ.yo +++ b/Etc/FAQ.yo @@ -333,7 +333,7 @@ sect(What's the latest version?) Changes of this kind are almost always forced by an awkward or unnecessary feature in the original design (as perceived by current users), or to enhance compatibility with other Bourne shell - derivatives, or (mostly in the 3.0 series) to provide POSIX compliancy. + derivatives, or (mostly in the 3.0 series) to provide POSIX compliance. sect(Where do I get it?) @@ -871,7 +871,7 @@ label(25) the most obvious difference from zsh is that it does not attempt to emulate the Korn shell. Since both shells are under active development it is probably not sensible to be too specific here. - Broadly, bash has paid more attention to standards compliancy + Broadly, bash has paid more attention to standards compliance (i.e. POSIX) for longer, and has so far avoided the more abstruse interactive features (programmable completion, etc.) that zsh has. diff --git a/Etc/NEWS-4.3 b/Etc/NEWS-4.3 index 19b3daada..8d93af134 100644 --- a/Etc/NEWS-4.3 +++ b/Etc/NEWS-4.3 @@ -139,7 +139,7 @@ The new shell option POSIX_CD, active in emulations of POSIX-based shells, makes the cd builtin POSIX-compatible. The POSIX_JOBS option already referred to has various other -compatibility enchancements. +compatibility enhancements. The new shell option POSIX_STRINGS makes a null character in $'...' expansion terminate the string, as is already the case in bash. This is -- cgit 1.4.1