aboutsummaryrefslogtreecommitdiffstats
path: root/SQLiteStudio3/coreSQLiteStudio/services/pluginmanager.h
diff options
context:
space:
mode:
authorLibravatarUnit 193 <unit193@unit193.net>2021-12-17 07:06:30 -0500
committerLibravatarUnit 193 <unit193@unit193.net>2021-12-17 07:06:30 -0500
commit1fdc150116cad39aae5c5da407c3312b47a59e3a (patch)
tree123c79a4d7ad2d45781ba03ce939f7539fb428d8 /SQLiteStudio3/coreSQLiteStudio/services/pluginmanager.h
parentfeda8a7db8d1d7c5439aa8f8feef7cc0dd2b59a0 (diff)
New upstream version 3.3.3+dfsg1.upstream/3.3.3+dfsg1
Diffstat (limited to 'SQLiteStudio3/coreSQLiteStudio/services/pluginmanager.h')
-rw-r--r--SQLiteStudio3/coreSQLiteStudio/services/pluginmanager.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/SQLiteStudio3/coreSQLiteStudio/services/pluginmanager.h b/SQLiteStudio3/coreSQLiteStudio/services/pluginmanager.h
index f771c2c..65aa8fa 100644
--- a/SQLiteStudio3/coreSQLiteStudio/services/pluginmanager.h
+++ b/SQLiteStudio3/coreSQLiteStudio/services/pluginmanager.h
@@ -344,7 +344,7 @@ class API_EXPORT PluginManager : public QObject
* the other one, if the first one is already loaded - and vice versa.
*
* Declaring conflicts for a plugin can be useful for example if somebody wants to proivde an alternative
- * implementation of SQLite2 database plugin, etc. In that case SQLiteStudio won't get confused in
+ * implementation of SQLCipher database plugin, etc. In that case SQLiteStudio won't get confused in
* deciding which plugin to use for supporting such databases.
*/
virtual QStringList getConflicts(const QString& pluginName) const = 0;