diff --git a/doc/src/analyze/cpu-usage-analyzer.qdoc b/doc/src/analyze/cpu-usage-analyzer.qdoc
index dddea53102f..b5d4b094a36 100644
--- a/doc/src/analyze/cpu-usage-analyzer.qdoc
+++ b/doc/src/analyze/cpu-usage-analyzer.qdoc
@@ -350,15 +350,14 @@
             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.
-            \c {-e cpu-clock} is a safe but relatively slow option as it
-            does not use the hardware performance counters, but drives the
-            sampling from software. After the sampling has failed, reboot the
-            device. The kernel may have disabled important parts of the
-            performance counters system.
+            event types by running \c {perf list} on the device and then choose
+            the respective event types in the settings. The choice of event type
+            affects the performance and stability of the sampling. The
+            \c {cpu-clock} \c {software} event is a safe but relatively slow
+            option as it does not use the hardware performance counters, but
+            drives the sampling from software. After the sampling has failed,
+            reboot the device. The kernel may have disabled important parts of
+            the performance counters system.
     \endlist
 
     Output from the helper program that processes the data is displayed in the