about summary refs log tree commit diff
path: root/Etc
diff options
context:
space:
mode:
authorJens Schleusener <Jens.Schleusener@fossies.org>2020-01-09 13:39:44 +0000
committerDaniel Shahaf <danielsh@apache.org>2020-01-09 13:42:02 +0000
commit11dbe4c286330f81fae5ac6d5f698f5ddb748710 (patch)
tree747b3a6ea08312efe98446fd90222d2f0a72d064 /Etc
parent4858e868dcf809016a1cb5680327d66d551353ae (diff)
downloadzsh-11dbe4c286330f81fae5ac6d5f698f5ddb748710.tar.gz
zsh-11dbe4c286330f81fae5ac6d5f698f5ddb748710.tar.xz
zsh-11dbe4c286330f81fae5ac6d5f698f5ddb748710.zip
45269: Fix misspellings in completions and elsewhere.
Diffstat (limited to 'Etc')
-rw-r--r--Etc/FAQ.yo2
1 files changed, 1 insertions, 1 deletions
diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo
index 5c28b4089..d1f8b7d83 100644
--- a/Etc/FAQ.yo
+++ b/Etc/FAQ.yo
@@ -2244,7 +2244,7 @@ sect(What is multibyte input?)
   zsh will be able to use any such encoding as long as it contains ASCII as
   a single-octet subset and the system can provide information about other
   characters.  However, in the case of Unicode, UTF-8 is the only one you
-  are likely to enounter that is useful in zsh.
+  are likely to encounter that is useful in zsh.
 
   (In case you're confused: Unicode is the character set, while UTF-8 is
   an encoding of it.  You might hear about other encodings, such as UCS-2