summaryrefslogtreecommitdiffstats
path: root/doc/html/activeqt-dotnet.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/activeqt-dotnet.html')
-rw-r--r--doc/html/activeqt-dotnet.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/html/activeqt-dotnet.html b/doc/html/activeqt-dotnet.html
index a65d0d3c3..e0cfa0d83 100644
--- a/doc/html/activeqt-dotnet.html
+++ b/doc/html/activeqt-dotnet.html
@@ -106,7 +106,7 @@ is presented, which includes using a thin MC++ wrapper class around
the normal TQt/C++ class. Then, the automated way is presented, which
utilizes the <a href="activeqt.html#ActiveTQt">ActiveTQt</a> framework as a generic bridge. The advantage of
the first method is that it gives the application developer full
-control, while the second method retquires less coding and relieves the
+control, while the second method requires less coding and relieves the
developer of dealing with the conversion between managed and normal
data objects.
<p> The impatient reader, who right away wants to see a <a href="qpushbutton.html">TQPushButton</a> and a
@@ -405,7 +405,7 @@ available to .NET. This has the positive side effect that the same
API is automatically available in <a href="http://www.trolltech.com/products/qsa">TQSA</a>, the cross platform
scripting solution for TQt applications, and to COM clients in general.
<p> When using the "IJW" method, in priciple the only limitation is the
-time retquired to write the wrapper classes and data type conversion
+time required to write the wrapper classes and data type conversion
functions.
<p> <h3> Performance Considerations
</h3>