diff --git a/doc/src/analyze/cpu-usage-analyzer.qdoc b/doc/src/analyze/cpu-usage-analyzer.qdoc
index 873abff8c08..dddea53102f 100644
--- a/doc/src/analyze/cpu-usage-analyzer.qdoc
+++ b/doc/src/analyze/cpu-usage-analyzer.qdoc
@@ -346,11 +346,11 @@
         \li Some versions of Perf will not start recording unless given a
             certain minimum sampling frequency. Try with a
             \uicontrol {Sampling Frequency} of 1000.
-        \li On some devices, for example Boundary Devices i.MX6 Boards, the
-            Perf support is not very stable and the Linux kernel may randomly
-            fail to record data after some time. Perf can use different types
-            of events to trigger samples. You can get a list of available event
-            types by running \c {perf list} on the device and add
+        \li On some devices, in particular various i.MX6 Boards, the hardware
+            performance counters are dysfunctional and the Linux kernel may
+            randomly fail to record data after some time. Perf can use different
+            types of events to trigger samples. You can get a list of available
+            event types by running \c {perf list} on the device and add
             \c {-e <event type>} to the \uicontrol {Additional arguments} field
             to change the event type to be used. The choice of event type
             affects the performance and stability of the sampling.