Doc: Fix typos

Change-Id: I29d5576902a5d1ea25558e980081952d9157f7f0
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
This commit is contained in:
Sze Howe Koh 2015-01-02 20:06:08 +08:00
parent 0f5b970894
commit c49641a117
10 changed files with 12 additions and 12 deletions

View File

@ -136,7 +136,7 @@
byte in the buffer, \c numUsedBytes is \c BufferSize - 1 and the
\c bufferNotEmpty condition is signalled. At that point, two
things can happen: Either the consumer thread takes over and
reads that byte, or the consumer gets to produce a second byte.
reads that byte, or the producer gets to produce a second byte.
The producer-consumer model presented in this example makes it
possible to write highly concurrent multithreaded applications.

View File

@ -178,7 +178,7 @@ QThreadPrivate::~QThreadPrivate()
event loop by calling exec() and runs a Qt event loop inside the thread.
You can use worker objects by moving them to the thread using
QObject::moveToThread.
QObject::moveToThread().
\snippet code/src_corelib_thread_qthread.cpp worker
@ -256,7 +256,7 @@ QThreadPrivate::~QThreadPrivate()
\l{Mandelbrot Example}, as that is the name of the QThread subclass).
Note that this is currently not available with release builds on Windows.
\sa {Thread Support in Qt}, QThreadStorage, {Synchronizing Threads}
\sa {Thread Support in Qt}, QThreadStorage, {Synchronizing Threads},
{Mandelbrot Example}, {Semaphores Example}, {Wait Conditions Example}
*/

View File

@ -3945,7 +3945,7 @@ QByteArray QByteArray::fromRawData(const char *data, int size)
copies of it exist that have not been modified.
This function can be used instead of fromRawData() to re-use
existings QByteArray objects to save memory re-allocations.
existing QByteArray objects to save memory re-allocations.
\sa fromRawData(), data(), constData()
*/

View File

@ -484,7 +484,7 @@ QDebug operator<<(QDebug dbg, const QMargins &m) {
/*!
\fn bool QMarginsF::isNull() const
Returns \c true if all margins are is 0; otherwise returns
Returns \c true if all margins are 0; otherwise returns
false.
*/

View File

@ -726,7 +726,7 @@ static const short QXmlStreamReader_tokenTypeString_indices[] = {
/*!
\property QXmlStreamReader::namespaceProcessing
the namespace-processing flag of the stream reader
The namespace-processing flag of the stream reader
This property controls whether or not the stream reader processes
namespaces. If enabled, the reader processes namespaces, otherwise
@ -3315,7 +3315,7 @@ QTextCodec *QXmlStreamWriter::codec() const
/*!
\property QXmlStreamWriter::autoFormatting
\since 4.4
the auto-formatting flag of the stream writer
The auto-formatting flag of the stream writer
This property controls whether or not the stream writer
automatically formats the generated XML data. If enabled, the

View File

@ -48,7 +48,7 @@ static const char * const start_xpm[]={
//! [1]
QPixmap myPixmap;
myPixmap->setMask(myPixmap->createHeuristicMask());
myPixmap.setMask(myPixmap.createHeuristicMask());
//! [1]
//! [2]

View File

@ -605,7 +605,7 @@ QList<QByteArray> QNetworkReply::rawHeaderList() const
/*!
Returns the attribute associated with the code \a code. If the
attribute has not been set, it returns an invalid QVariant (type QMetaType::Unknown).
attribute has not been set, it returns an invalid QVariant (type QMetaType::UnknownType).
You can expect the default values listed in
QNetworkRequest::Attribute to be applied to the values returned by

View File

@ -805,7 +805,7 @@
{QWidget::addAction}().
\endquotation
If you don't include the function name with the \b{\\overlaod}
If you don't include the function name with the \b{\\overload}
command, then instead of the "This function overloads..." line
with the link to the documentation for the primary version, you
get the old standard line:

View File

@ -219,7 +219,7 @@
\section1 Custom Widgets in Layouts
When you make your own widget class, you should also communicate its layout
properties. If the widget has a one of Qt's layouts, this is already taken
properties. If the widget uses one of Qt's layouts, this is already taken
care of. If the widget does not have any child widgets, or uses manual
layout, you can change the behavior of the widget using any or all of the
following mechanisms:

View File

@ -7235,7 +7235,7 @@ QByteArray QWidget::saveGeometry() const
/*!
\since 4.2
Restores the geometry and state top-level widgets stored in the
Restores the geometry and state of top-level widgets stored in the
byte array \a geometry. Returns \c true on success; otherwise
returns \c false.