Git commit 0d847a0230a9f643a197a43599775b4146eb08e7 by luz paz. Committed on 01/12/2021 at 15:22. Pushed by nicolasfella into branch 'master'.
Fix various typos Found via `codespell -q 3 -S *.notifyrc,*.desktop -L claus,te` M +1 -1 applets/kickoff/package/contents/ui/Footer.qml M +1 -1 applets/kickoff/package/contents/ui/KickoffItemDelegate.qml M +1 -1 applets/kimpanel/package/contents/ui/main.qml M +1 -1 applets/taskmanager/package/contents/ui/code/layout.js M +1 -1 applets/taskmanager/package/contents/ui/code/tools.js M +1 -1 applets/taskmanager/plugin/smartlaunchers/smartlauncherbackend.h M +1 -1 containments/desktop/package/contents/config/main.xml M +5 -5 design/CHANGELOG-4.3 M +3 -3 design/CHANGELOG-4.4 M +3 -3 design/activities M +3 -3 design/notifications M +1 -1 design/remotewidgets M +1 -1 design/screensaver M +2 -2 design/security M +1 -1 design/systemtraywidget M +1 -1 design/tooltips M +1 -1 doc/plasma-desktop/index.docbook M +1 -1 kcms/kded/kcmkded.cpp M +1 -1 kcms/keyboard/README M +2 -2 kcms/keyboard/layout_memory.cpp M +1 -1 kcms/keyboard/tastenbrett/qml/KeyCap.qml M +1 -1 kcms/keyboard/tastenbrett/qml/main.qml M +1 -1 kcms/landingpage/package/contents/ui/main.qml M +1 -1 kcms/runners/plugininstaller/ScriptJob.cpp M +1 -1 solid-device-automounter/SETTINGS https://invent.kde.org/plasma/plasma-desktop/commit/0d847a0230a9f643a197a43599775b4146eb08e7 diff --git a/applets/kickoff/package/contents/ui/Footer.qml b/applets/kickoff/package/contents/ui/Footer.qml index 6d21acf8b..825619b37 100644 --- a/applets/kickoff/package/contents/ui/Footer.qml +++ b/applets/kickoff/package/contents/ui/Footer.qml @@ -193,7 +193,7 @@ PlasmaExtras.PlasmoidHeading { anchors.left: parent.left height: root.height width: tabBar.width - z: 1 // Has to be above contentItem to recieve mouse wheel events + z: 1 // Has to be above contentItem to receive mouse wheel events WheelHandler { id: tabScrollHandler acceptedDevices: PointerDevice.Mouse | PointerDevice.TouchPad diff --git a/applets/kickoff/package/contents/ui/KickoffItemDelegate.qml b/applets/kickoff/package/contents/ui/KickoffItemDelegate.qml index 0f0c4fd6a..95486af4e 100644 --- a/applets/kickoff/package/contents/ui/KickoffItemDelegate.qml +++ b/applets/kickoff/package/contents/ui/KickoffItemDelegate.qml @@ -221,7 +221,7 @@ T.ItemDelegate { } onClicked: if (mouse.button === Qt.LeftButton) { root.forceActiveFocus(Qt.MouseFocusReason) - root.action.trigger() // clicked() is emmitted when action is triggered + root.action.trigger() // clicked() is emitted when action is triggered } else if (mouse.button === Qt.RightButton) { root.forceActiveFocus(Qt.MouseFocusReason) root.clicked() // does not trigger the action diff --git a/applets/kimpanel/package/contents/ui/main.qml b/applets/kimpanel/package/contents/ui/main.qml index 12ab9b98b..a2f4f72de 100644 --- a/applets/kimpanel/package/contents/ui/main.qml +++ b/applets/kimpanel/package/contents/ui/main.qml @@ -74,7 +74,7 @@ Item { } } - //depending on the form factor, we are calculating only one dimention, second is always the same as root/parent + //depending on the form factor, we are calculating only one dimension, second is always the same as root/parent implicitHeight: kimpanel.vertical ? cellHeight * Math.ceil(count / rowsOrColumns) : kimpanel.height implicitWidth: !kimpanel.vertical ? cellWidth * Math.ceil(count / rowsOrColumns) : kimpanel.width diff --git a/applets/taskmanager/package/contents/ui/code/layout.js b/applets/taskmanager/package/contents/ui/code/layout.js index 02b432bcf..e47cd60cd 100644 --- a/applets/taskmanager/package/contents/ui/code/layout.js +++ b/applets/taskmanager/package/contents/ui/code/layout.js @@ -148,7 +148,7 @@ function preferredMaxHeight() { // Hence in case the user prefers icons smaller than the // height of his font, the font height will win even if the // text will stay invisible. We leave it for the future - // developers to improve this expresssion if the named + // developers to improve this expression if the named // corner case turns out to be important. PlasmaCore.Units .iconSizes[iconSizes[plasmoid.configuration.iconSize]], diff --git a/applets/taskmanager/package/contents/ui/code/tools.js b/applets/taskmanager/package/contents/ui/code/tools.js index d69ff2037..6912ee992 100644 --- a/applets/taskmanager/package/contents/ui/code/tools.js +++ b/applets/taskmanager/package/contents/ui/code/tools.js @@ -172,7 +172,7 @@ function activateTask(index, model, modifiers, task) { // Option 4: show group dialog/textual list // ======================================== // This is also the final fallback option if Tooltips or Present windows - // are chosen but not actully available + // are chosen but not actually available else { if (groupDialog.visible) { task.hideToolTipTemporarily(); diff --git a/applets/taskmanager/plugin/smartlaunchers/smartlauncherbackend.h b/applets/taskmanager/plugin/smartlaunchers/smartlauncherbackend.h index c7b62e2e9..7d404a323 100644 --- a/applets/taskmanager/plugin/smartlaunchers/smartlauncherbackend.h +++ b/applets/taskmanager/plugin/smartlaunchers/smartlauncherbackend.h @@ -103,7 +103,7 @@ private: QHash<QString, QString> m_launcherUrlToStorageId; // these rules can be configured in the taskmanagerrulesrc in the "Unity Launcher Mapping" section // key is the actual desktop file name of the application (some-broken-app-beta.desktop) - // vaue is how it actually announces itself on the Unity API (some-broken-app.desktop) + // value is how it actually announces itself on the Unity API (some-broken-app.desktop) QHash<QString, QString> m_unityMappingRules; // Application Jobs diff --git a/containments/desktop/package/contents/config/main.xml b/containments/desktop/package/contents/config/main.xml index 3b46d5a10..277c68b8b 100644 --- a/containments/desktop/package/contents/config/main.xml +++ b/containments/desktop/package/contents/config/main.xml @@ -99,7 +99,7 @@ <default></default> </entry> <entry name="viewMode" type="Int"> - <label>The Folder View view mode (used only by the widget full represntation): 0 = Grid, 1 = List</label> + <label>The Folder View view mode (used only by the widget full representation): 0 = Grid, 1 = List</label> <default>0</default> </entry> <entry name="iconSize" type="Int"> diff --git a/design/CHANGELOG-4.3 b/design/CHANGELOG-4.3 index 6cb984cd8..095e57c0f 100644 --- a/design/CHANGELOG-4.3 +++ b/design/CHANGELOG-4.3 @@ -60,7 +60,7 @@ Other Libraries * libplasmaclock * Text to speech service (KTTSD) to read aloud the time * Holidays shown in pop-up calendar -* libtaskmanager: signficant stability fixes, particularly crashes in closeGroup or add(Task) caused by changes in the grouping strategy +* libtaskmanager: significant stability fixes, particularly crashes in closeGroup or add(Task) caused by changes in the grouping strategy Developer Documentation ----------------------- @@ -126,7 +126,7 @@ Plugins/Addons * Microblogging (was KDE Twitter) * Added support for other Twitter API based services like identi.ca (that is based on laconi.ca) * Pager - * User can choose to do nothing, toogle the desktop or the dashboard when he click on the current desktop. + * User can choose to do nothing, toggle the desktop or the dashboard when he click on the current desktop. * Notes * Highlight current line * Change font size with Control + Scrollwheel @@ -142,7 +142,7 @@ Plugins/Addons * Ability to show/hide icons based on category * Jobs show file/dir progress and ETA * Jobs are grouped together: one group for running jobs and one for completed jobs. - * Completed jobs have a different appearence and allow the user to open the destination file/directory. + * Completed jobs have a different appearance and allow the user to open the destination file/directory. * Notifications now show custom images like kopete's contact images. * Multiple trays in the same Plasma application supported. * Can configure whether or not notifications/jobs should autohide shortly after appearing. @@ -200,7 +200,7 @@ Plugins/Addons * Runners * Converter - * If not exact unit found offer possible mathes. + * If not exact unit found offer possible matches. * ScriptEngines * Simple JavaScript API @@ -212,7 +212,7 @@ Plugins/Addons * Bugfixes * Plasmoids and Containments * Show Desktop - * Fix keyboard shorcuts BUG:180661 + * Fix keyboard shortcuts BUG:180661 * News * Better alternate background color for generated css. BUG: 185527 * correctly use feed urls with parameters BUG:178936 diff --git a/design/CHANGELOG-4.4 b/design/CHANGELOG-4.4 index 8abfc3eb4..b7a6d051b 100644 --- a/design/CHANGELOG-4.4 +++ b/design/CHANGELOG-4.4 @@ -41,7 +41,7 @@ Generic shell ------------- * NEW library in workspace called plasmagenericshell that contains elements shared by the desktop shell, the netbook shell and the screensaver one, such as: * Wallpaper setup UI - * Mouse plugins configuratin UI + * Mouse plugins configuration UI * NEW Widgets Explorer that replaces the old applet browser. It shows all the available widgets in an horizontal or vertical list with a tabbar to chose the available categories and an input field to search among all installed widgets. @@ -73,7 +73,7 @@ New components: * Search and Launch: full screen krunner interface with bookmarks support for the search results * Netpanel: a simple panel * Applets: - * Searchbox: lauches searches on the Search and launch containment + * Searchbox: launches searches on the Search and launch containment * Current app control: provides a titlebar in the panel with a button to quickly switch windows * Dataengines: * Searchandlaunch: communication between searchbox and search and launch containment @@ -115,7 +115,7 @@ Plugins/Addons * SystemTray * now can embed other plasmoids * supports the finalized version of the StatusNotifier specification - * old notifications remains accessible for a while, separed by application name, browseable with a tabbar widget + * old notifications remains accessible for a while, separated by application name, browseable with a tabbar widget * Tasks * clicking on a window preview now activates that window * mouse over on a window preview highlights the window if the highlight windows KWin effect is activated diff --git a/design/activities b/design/activities index 58c3bbc25..f086bb9d7 100644 --- a/design/activities +++ b/design/activities @@ -38,7 +38,7 @@ In 4.5 ------ all important code so far has been in kdebase. -runtime/activitymanager/ is a kded service that manages activities; it controls the list of activities and which one is currrent. It uses a config file to store the IDs and names, so that this information is available even when nepomuk is down; other data, like the icon, is fetched through nepomuk. +runtime/activitymanager/ is a kded service that manages activities; it controls the list of activities and which one is current. It uses a config file to store the IDs and names, so that this information is available even when nepomuk is down; other data, like the icon, is fetched through nepomuk. workspace/libs/kworkspace contains KActivityController, KActivityConsumer, and KActivityInfo - classes that talk to the activity manager over dbus and provide an easy API. Controller inherits Consumer, and is meant only for workspace (kwin and plasma); the other two are meant for use by any application, and will move to kdelibs when they've had a chance to mature. @@ -53,7 +53,7 @@ Future * kwin needs to automatically associate a window with the activities for its resources. * applications need to start advertising what resources they've got in what windows -* it needs to be easy to associate documents with activites (in dolphin?) +* it needs to be easy to associate documents with activities (in dolphin?) * the taskbar & pager shouldn't show windows from other activities (but perhaps there should be a way to reach them in case you forget where one is) * I'd like to see a plasmoid that can go in the panel for quick activity switching @@ -77,7 +77,7 @@ I think it's worth trying to re-use it. If it works, it gives us some basic supp So, how do we re-use it? well, for an application that's on exactly one activity, that's easy: tell it to quit, store its sssion key somewhere along with the activity id, and when it's time to restore that activity you start it again with that key. If an application is on >1 running activity, merely tell it that one of its activities has quit. if it's activity-aware it should close down stuff that belongs to that activity; if not, oh well, at least nothing is lost. When its last aactivity is closed, we tell it to quit, and save the key with every activity it was associated with, so that as soon as one of them is opened it gets restored. -We will have to be careful that logging out doesn't duplicate any session stuff that activites handle, of course; and once this is in place we may also be able to offer the option of only opening a single activity on login. +We will have to be careful that logging out doesn't duplicate any session stuff that activities handle, of course; and once this is in place we may also be able to offer the option of only opening a single activity on login. Oh, and we'll have to watch that the windows created as an application is restored get associated with the correct activities. I'm not sure how much work that is; depends how hard it is to go from a WID to a PID to a session key. diff --git a/design/notifications b/design/notifications index 4c8239b76..044efa322 100644 --- a/design/notifications +++ b/design/notifications @@ -16,7 +16,7 @@ Visualization components Alert -As soon as notifications arrive, they are placed in the NotificationStack widget: it is an automatic popup, so in order to disturb the user workflow as less as possible, the size is kept fairly small, limiting the maximum nuber of notification displayed. For the same reason ony one notification at a time is displayed: the oldest (newest?) one, with the others partially covered, but permitting to still see the title. +As soon as notifications arrive, they are placed in the NotificationStack widget: it is an automatic popup, so in order to disturb the user workflow as less as possible, the size is kept fairly small, limiting the maximum number of notification displayed. For the same reason only one notification at a time is displayed: the oldest (newest?) one, with the others partially covered, but permitting to still see the title. Moving the mouse over the title of the semi-hidden notifications will show them completely. The NotificationStack window is always on top of every other window. When a new notification arrives it is added in the NotificationStack with the following strategy: @@ -37,7 +37,7 @@ Clicking anywhere in the stack area hides the whole stack, but in order to preve Information If the user missed some notification, it's possible to view the old ones by manually invoking a different ui by hitting the "i" button. -The notifications are contained in a widget called NotificationScroller, that appears as a popup window. A tabbar lets the user filter the notifications by the sender application (useful for instance if the user is looking for informations about completition of an old running file tranfer or battery warning notices). +The notifications are contained in a widget called NotificationScroller, that appears as a popup window. A tabbar lets the user filter the notifications by the sender application (useful for instance if the user is looking for information about completion of an old running file transfer or battery warning notices). Notifications are in a scrolling view that permits a fairly large amount of those to be displayed without using too much screen space. It features also the following behaviour: * If a new notification arrives the current status of the widget is not changed, to not interrupt the user workflow. (current selected tab and scrollbar value) @@ -63,5 +63,5 @@ When the user opens the main widget popup that contains the NotificationScroller * The body contains * The source and destination URLs * A progressbar to show the job status - * Optional extra informations such as file size, transfer speed and size already transfered + * Optional extra information such as file size, transfer speed and size already transferred diff --git a/design/remotewidgets b/design/remotewidgets index 27d501da0..fc6daa5fb 100644 --- a/design/remotewidgets +++ b/design/remotewidgets @@ -22,7 +22,7 @@ Security The plasma shell can control the security aspects of remote widgets, combined with a system wide config file (/etc/plasma-remotewidgets.conf) containing rules that can allow/disallow certain machines access to certain published widgets/services/engines. As a plasma shell you've got the following options: -* Use one of the sensible presets in which case you don't have to case about security. The only thing you'll need to do is set the desired behavior using AuthorizationManager::self()->setAuthorizationPolicy(). This will set the AuthorizationInterface implementation to one of the ones built in into libplasma. Do note that even when you whish to use the default policy (DenyAll), you should still call this function, since that automatically locks this value so a potential malicious plasma plugin can't change this to serve it's own evil desires. +* Use one of the sensible presets in which case you don't have to case about security. The only thing you'll need to do is set the desired behavior using AuthorizationManager::self()->setAuthorizationPolicy(). This will set the AuthorizationInterface implementation to one of the ones built in into libplasma. Do note that even when you wish to use the default policy (DenyAll), you should still call this function, since that automatically locks this value so a potential malicious plasma plugin can't change this to serve it's own evil desires. * Supply your own behavior by implementing AuthorizationInterface, set authorizationPolicy to custom, and use AuthorizationManager::self()->setAuthorizationInterface() to your own implementation. Security wise, every incoming message will get processed as follows: diff --git a/design/screensaver b/design/screensaver index 37c703335..8e2e3a293 100644 --- a/design/screensaver +++ b/design/screensaver @@ -51,7 +51,7 @@ security Plasmoids on the screensaver obviously present a security risk. this is being minimized as described in the security document. what makes it interesting is that we're less concerned with malicious -plasmoids and more with malicious (or mischevious) users; a locked screen left unattended should not +plasmoids and more with malicious (or mischievous) users; a locked screen left unattended should not end up with goatse on it, or files deleted. Future Work diff --git a/design/security b/design/security index f3dee85e4..5470a403c 100644 --- a/design/security +++ b/design/security @@ -18,7 +18,7 @@ This type of security relies heavily on plasmoid developers. Each plasmoid's .de Features the plasmoid would like but does not require should be guarded by hasAuthorization, and set to Optional in the .desktop. [example](http://websvn.kde.org/?view=rev&revision=967792). All the plasmoids in workspace and kdeplasma-addons should probably be reviewed before release. some of them don't have an active maintainer to take responsibility. -Currenly, plasmoids that don't mention a constraint are assumed to not use it. however, by release time the opposite should be true. this is just so that they don't *all* disappear from the screensaver before anyone has a chance to review their plasmoids. +Currently, plasmoids that don't mention a constraint are assumed to not use it. however, by release time the opposite should be true. this is just so that they don't *all* disappear from the screensaver before anyone has a chance to review their plasmoids. Note that this will not remove existing instances of plasmoids. It only hides them from the appletbrowser. Users who really really want to can edit the config file to add unsafe applets. Existing constraints/features: @@ -51,7 +51,7 @@ misc I'm not sure what categories these fall under. -category exclusion: entire categories of plasmoids can be excluded from hte appletbrowser. for example, application launchers are excluded from the screensaver because they'd never ever be wanted there. +category exclusion: entire categories of plasmoids can be excluded from the appletbrowser. for example, application launchers are excluded from the screensaver because they'd never ever be wanted there. configuration locking: on the screensaver, config dialogs can't be accessed while the screen is locked. however, it's possible for a c++ plasmoid to override showConfigurationInterface and circumvent this. diff --git a/design/systemtraywidget b/design/systemtraywidget index 8bd9f689f..47c83634f 100644 --- a/design/systemtraywidget +++ b/design/systemtraywidget @@ -23,7 +23,7 @@ this, along with the central Manager, allows any Task to be shared simultaneousl multiple widgets. Notifications and Jobs don't have this problem as they simply provide access to -data which the ui is reponsible for showing in some way. +data which the ui is responsible for showing in some way. Also provided in the core is a Task specifically for managing the Extenders of a host Plasma::Applet for Jobs and Notifications call, rather creatively, ExtenderTask. diff --git a/design/tooltips b/design/tooltips index 7d4bbb587..96f1398c0 100644 --- a/design/tooltips +++ b/design/tooltips @@ -18,7 +18,7 @@ Registering Tooltips -------------------- ToolTipManger is quite simple to use: simply call setWidgetToolTipContent using the struct ToolTipContent. This causes the widget to be registered if it isn't already. Alternatively, for widgets that fill the data on demand, call registerWidget directly. -Widgets are unregistered automatically upon destruction, but can also be manually unregsitered by calling ToolTipMnager::unregisterWidget. +Widgets are unregistered automatically upon destruction, but can also be manually unregistered by calling ToolTipMnager::unregisterWidget. An event filter is registered on each registered widget and hover events that occur trigger calls to showToolTip and hideToolTip. The hover events are not, however, filtered out. diff --git a/doc/plasma-desktop/index.docbook b/doc/plasma-desktop/index.docbook index 858351c5c..925f5d7d7 100644 --- a/doc/plasma-desktop/index.docbook +++ b/doc/plasma-desktop/index.docbook @@ -534,7 +534,7 @@ you've entered more than two characters. You can open the settings dialog to learn about &krunner;’s functionality, provided by plugins. You can navigate through the matches using the tab and arrow keys. </para> -<!-- whitout tab no arrow keys--> +<!-- without tab no arrow keys--> <screenshot> <screeninfo>&krunner; dialog</screeninfo> <mediaobject> diff --git a/kcms/kded/kcmkded.cpp b/kcms/kded/kcmkded.cpp index 6bd42cb5e..9d4683792 100644 --- a/kcms/kded/kcmkded.cpp +++ b/kcms/kded/kcmkded.cpp @@ -169,7 +169,7 @@ void KDEDConfig::getModuleStatus() // Check if the user just tried starting a module that then disabled itself again. // Some kded modules disable themselves on start when they deem themselves unnecessary - // based on some configuration independ of kded or the current environment. + // based on some configuration independent of kded or the current environment. // At least provide some feedback and not leave the user wondering why the service doesn't start. if (!m_lastStartedModule.isEmpty() && !runningModules.contains(m_lastStartedModule)) { Q_EMIT showSelfDisablingModulesHint(); diff --git a/kcms/keyboard/README b/kcms/keyboard/README index 25c50b47f..2c5dccc35 100644 --- a/kcms/keyboard/README +++ b/kcms/keyboard/README @@ -1,5 +1,5 @@ This is new project to replace keyboard (kcmmisc) and kxkb -to manage keyboard harware configuration and layouts. +to manage keyboard hardware configuration and layouts. Components: diff --git a/kcms/keyboard/layout_memory.cpp b/kcms/keyboard/layout_memory.cpp index 88e55ee9d..8af06d313 100644 --- a/kcms/keyboard/layout_memory.cpp +++ b/kcms/keyboard/layout_memory.cpp @@ -59,7 +59,7 @@ QString LayoutMemory::getCurrentMapKey() NET::WindowType windowType = winInfo.windowType(NET::NormalMask | NET::DesktopMask | NET::DialogMask); qCDebug(KCM_KEYBOARD, ) << "window type" << windowType; - // we ignore desktop type so that our keybaord layout applet on desktop could change layout properly + // we ignore desktop type so that our keyboard layout applet on desktop could change layout properly if (windowType == NET::Desktop) return previousLayoutMapKey; if (windowType != NET::Unknown && windowType != NET::Normal && windowType != NET::Dialog) @@ -73,7 +73,7 @@ QString LayoutMemory::getCurrentMapKey() NET::WindowType windowType = winInfo.windowType(NET::NormalMask | NET::DesktopMask | NET::DialogMask); qCDebug(KCM_KEYBOARD, ) << "window type" << windowType; - // we ignore desktop type so that our keybaord layout applet on desktop could change layout properly + // we ignore desktop type so that our keyboard layout applet on desktop could change layout properly if (windowType == NET::Desktop) return previousLayoutMapKey; if (windowType != NET::Unknown && windowType != NET::Normal && windowType != NET::Dialog) diff --git a/kcms/keyboard/tastenbrett/qml/KeyCap.qml b/kcms/keyboard/tastenbrett/qml/KeyCap.qml index 43cf29180..e18455cd2 100644 --- a/kcms/keyboard/tastenbrett/qml/KeyCap.qml +++ b/kcms/keyboard/tastenbrett/qml/KeyCap.qml @@ -9,7 +9,7 @@ import QtQuick 2.12 Item { property QtObject key - // NB: we scale hight only by a portion of the available space if + // NB: we scale height only by a portion of the available space if // some of the levels aren't there. Visually it looks weird when some // labels are full center, so let's still bias them towards an edge, but // increase the height ever so slightly diff --git a/kcms/keyboard/tastenbrett/qml/main.qml b/kcms/keyboard/tastenbrett/qml/main.qml index de455d704..27f2ad681 100644 --- a/kcms/keyboard/tastenbrett/qml/main.qml +++ b/kcms/keyboard/tastenbrett/qml/main.qml @@ -170,7 +170,7 @@ Window { height: section.height // Fix rotation to mod90, we cannot spin around as that'd put the text upside down ;) - // Unclear if spinning around like that is in fact desired for anyting, if so I guess + // Unclear if spinning around like that is in fact desired for anything, if so I guess // we need to counter rotate text or something. rotation: section.angle != 0 ? section.angle % 90 : section.angle transformOrigin: Item.TopLeft diff --git a/kcms/landingpage/package/contents/ui/main.qml b/kcms/landingpage/package/contents/ui/main.qml index 75306f5db..dea481275 100644 --- a/kcms/landingpage/package/contents/ui/main.qml +++ b/kcms/landingpage/package/contents/ui/main.qml @@ -174,7 +174,7 @@ KCM.SimpleKCM { } Item { - // This is outside the loaded in order to have perfect label alignemnt + // This is outside the loaded in order to have perfect label alignment Layout.preferredHeight: Kirigami.Units.smallSpacing visible: feedbackLoader.visible } diff --git a/kcms/runners/plugininstaller/ScriptJob.cpp b/kcms/runners/plugininstaller/ScriptJob.cpp index 2dd5d62d2..f0100728c 100644 --- a/kcms/runners/plugininstaller/ScriptJob.cpp +++ b/kcms/runners/plugininstaller/ScriptJob.cpp @@ -29,7 +29,7 @@ void ScriptJob::executeOperation(const QFileInfo &fileInfo, const QString &mimeT installerPath = file.absoluteFilePath(); } } - // We want the user to be exactly aware of whats going on + // We want the user to be exactly aware of what's going on if (install || installerPath.isEmpty()) { ScriptConfirmationDialog dlg(installerPath, install, fileInfo.absolutePath()); if (dlg.exec() == QDialog::Accepted) { diff --git a/solid-device-automounter/SETTINGS b/solid-device-automounter/SETTINGS index c6308a30f..062d8e55a 100644 --- a/solid-device-automounter/SETTINGS +++ b/solid-device-automounter/SETTINGS @@ -1,6 +1,6 @@ This document describes the kded_device_automounterrc settings and how they affect behavior. -General/AutomountUnknownDevices:If true, all devices get mounted regardles of +General/AutomountUnknownDevices:If true, all devices get mounted regardless of the other conditions. General/AutomountOnPlugin: When this is set to true, devices might get
