From 0f92dd542b65bc910caaf190b7c623aa5158c86a Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Mon, 14 Nov 2011 22:33:41 -0600 Subject: Fix native TQt3 accidental conversion to tquit --- qmake/book/qmake-commandreference.leaf | 4 ++-- qmake/book/qmake-concepts.leaf | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'qmake') diff --git a/qmake/book/qmake-commandreference.leaf b/qmake/book/qmake-commandreference.leaf index e20c4218..1e499ab7 100644 --- a/qmake/book/qmake-commandreference.leaf +++ b/qmake/book/qmake-commandreference.leaf @@ -1954,7 +1954,7 @@ Note: the QMAKESPEC path will automatically be added to the It is common on UNIX to be able to install from the same utility as you build with (e.g make install). For this \e qmake has introduce the -concept of an install set. The notation for this is tquite simple, +concept of an install set. The notation for this is quite simple, first you fill in an "object" in qmake for example: \code @@ -2104,7 +2104,7 @@ qmake backends (currently this is only supported by the UNIX \link #MAKEFILE_GENERATOR generator \endlink). The interfaces to customizing the Makefile are done through "objects" as in -other places in qmake. The notation for this is tquite simple, first you +other places in qmake. The notation for this is quite simple, first you fill in an "object" in qmake for example: \code diff --git a/qmake/book/qmake-concepts.leaf b/qmake/book/qmake-concepts.leaf index 3f71bdf9..09dadad3 100644 --- a/qmake/book/qmake-concepts.leaf +++ b/qmake/book/qmake-concepts.leaf @@ -11,7 +11,7 @@ also contains additional features to support Qt development. \e qmake generates a makefile based on the information in a project file. Project files are created by the developer. Project files are -usually simple, but can be tquite sophisticated if retquired. +usually simple, but can be quite sophisticated if retquired. \e qmake can also generate projects for Microsoft Visual studio without having to change the project file. -- cgit v1.2.3