summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorChris <xchrisx@uber.space>2019-08-12 18:42:41 +0200
committerChris <xchrisx@uber.space>2019-08-12 18:58:17 +0200
commit24c97b77f50f29d9296a005e9f3f5ba0a38319b1 (patch)
tree0eb05b5cea284ef7a0810ee5a2495fadad3cea37 /README
parentc9036df21135235ae00ee3f2813fbffffe02da4d (diff)
downloadtqca-24c97b77f50f29d9296a005e9f3f5ba0a38319b1.tar.gz
tqca-24c97b77f50f29d9296a005e9f3f5ba0a38319b1.zip
Replace Qt branding with TQt ones.
Signed-off-by: Chris <xchrisx@uber.space>
Diffstat (limited to 'README')
-rw-r--r--README4
1 files changed, 2 insertions, 2 deletions
diff --git a/README b/README
index b909bc3..2a7f471 100644
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-Qt Cryptographic Architecture
+TQt Cryptographic Architecture
-----------------------------
Version: API v1.0, Plugin v1
Author: Justin Karneges <justin@affinix.com>
@@ -20,7 +20,7 @@ upgrading a crypto plugin. Also, by pushing crypto functionality into
plugins, your application is free of legal issues, such as export
regulation.
-And of course, you get a very simple crypto API for Qt, where you can
+And of course, you get a very simple crypto API for TQt, where you can
do things like:
TQString hash = QCA::SHA1::hashToString(blockOfData);