From 3471f19fc56e41b2ee6236ea3016dfa30a76c0ff Mon Sep 17 00:00:00 2001 From: Christophe Giboudeaux Date: Tue, 13 Jul 2021 23:20:57 +0200 Subject: Fix typos found by codespell GIT_SILENT --- docs/DESIGN.kconfig | 8 ++++---- docs/options.md | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/DESIGN.kconfig b/docs/DESIGN.kconfig index 68994aed..d2f2056a 100644 --- a/docs/DESIGN.kconfig +++ b/docs/DESIGN.kconfig @@ -53,8 +53,8 @@ void deleteEntry(key); // Remove entry Note that there is a subtle difference between revertToDefault() and deleteEntry(). revertToDefault() will change the entry to the default value set by the system administrator (Via e.g. $KDEDIR/share/config) or, if no such default was set, -non-existant. -deleteEntry() will make the entry non-existant. +non-existent. +deleteEntry() will make the entry non-existent. Entries are marked "immutable" if the key is followed by [$i]. This means that a user can not override these entries. @@ -103,7 +103,7 @@ KConfig XT ========== My buzzword picker offered KConfig XT ("eXtended Technology") and KConfig NG -("Next Generation"). Since the planned changes are ment to be evolutionary +("Next Generation"). Since the planned changes are meant to be evolutionary rather than revolutionary, KConfig NG was dropped. Goals @@ -216,7 +216,7 @@ myconfig.kcfg-codegen: Implementation specific code generation instructions choses the actual name. KConfigDialogManager: Class that links widgets in a dialog up with their - corresponding confguration options in a configuration + corresponding configuration options in a configuration object derived from KConfigSkeleton. MyConfigWidget: Dialog generated from a .ui description file. Widget names diff --git a/docs/options.md b/docs/options.md index 4a6e9bc1..b57713de 100644 --- a/docs/options.md +++ b/docs/options.md @@ -48,11 +48,11 @@ Once this is done, the immutable entries or groups cannot be overridden by later files of the same name (and, if the file is immutable, later files will be ignored entirely). -Note that a similar effect to file immutability can be acheived by using file +Note that a similar effect to file immutability can be achieved by using file system permissions to prevent the user from writing to their local versions of the configuration file, although (since this is normally a setup error), the user will be warned that the configuration file is not writable. This warning -can be supressed by adding the following setting to either the relevant +can be suppressed by adding the following setting to either the relevant configuration file or the `kdeglobals` file: [General] -- cgit v1.2.1