diff --git a/README b/README
index 2806675e8f97ea5ebe3b2e59345a60dd2f3d5ccf..f088185ad4ccc354d5ae6361debdefddd5505d20 100644
--- a/README
+++ b/README
@@ -26,22 +26,22 @@ cd $BUILD_DIRECTORY
 qmake $SOURCE_DIRECTORY/qtcreator.pro
 make (or mingw32-make or nmake or jom, depending on your platform)
 
-QmlDesigner, QmlInspector require private headers
--------------------------------------------------
+QmlDesigner requires private headers from Qt 4.7.1
+--------------------------------------------------
 
-The QmlDesigner and QmlInspector plugins depend on "private" Qt headers,
-specifically from the QtDeclarative module. These private headers always end
-with an "_p.h", and Nokia does not make any promises to keep the files or API's
-binary or source compatible between releases. This means that when compiled,
-the two plugins have a dependency to the exact Qt version they were compiled
-with. Running Qt Creator with the plugins against updated Qt libraries (also for
-patch releases) might lead to link time failures, or even crashes.
+The QmlDesigner plugin depends on "private" headers from Qt 4.7.1, specifically from
+the  QtDeclarative module. These private headers always end with an "_p.h", and Nokia
+does not make any promises to keep the files or API's binary or source compatible
+between releases. This means that when compiled, the plugin has a dependency to the
+exact Qt version it was compiled with. Running Qt Creator with the plugin against
+updated Qt libraries (also for patch releases) might lead to link time failures,
+or even crashes.
 
-If you want to disable the plugins, you can pass "QT_PRIVATE_HEADERS=" to qmake:
+If you want to disable the plugin, you can pass "QT_PRIVATE_HEADERS=" to qmake:
 
   qmake "QT_PRIVATE_HEADERS=" $SOURCE_DIRECTORY/qtcreator.pro
 
-Anyhow, the plugins will not be compiled when the private header files needed
+Anyhow, the plugin will not be compiled when the private header files needed
 are not found. This might be the case when you are using a Qt version from your
 distribution, or when you installed your self-compiled Qt to a separate
 directory via 'make install'. You can fix this by either re-building your Qt