diff --git a/NEWS b/NEWS
index 556a0252..f63eb426 100644
--- a/NEWS
+++ b/NEWS
@@ -25,7 +25,7 @@ v0.x.x (xxxx-xx-xx)
     been heavily parallelized.
   - The impact is especially visible with traces containing large amounts
     of data. The framerate improvement in such cases can be ~30x.
-  - Consequently, the profiler GUI will now produce all-core spikes when
+  - Consequently, the profiler GUI will now produce multi-core spikes when
     rendering frames. This may have impact on the profiled application's
     performance, if both the application and the profiler GUI are running
     on the same machine. If this is a problem, you may consider the capture
diff --git a/profiler/src/main.cpp b/profiler/src/main.cpp
index f967353f..fc5678b9 100644
--- a/profiler/src/main.cpp
+++ b/profiler/src/main.cpp
@@ -567,7 +567,7 @@ static void DrawContents()
                 ImGui::Indent();
                 if( ImGui::RadioButton( "Enabled", s_config.threadedRendering ) ) { s_config.threadedRendering = true; SaveConfig(); }
                 ImGui::SameLine();
-                tracy::DrawHelpMarker( "Uses all available CPU cores for rendering. May affect performance of the profiled application when running on the same machine." );
+                tracy::DrawHelpMarker( "Uses multiple CPU cores for rendering. May affect performance of the profiled application when running on the same machine." );
                 if( ImGui::RadioButton( "Disabled", !s_config.threadedRendering ) ) { s_config.threadedRendering = false; SaveConfig(); }
                 ImGui::SameLine();
                 tracy::DrawHelpMarker( "Restricts rendering to a single CPU core. Can reduce profiler frame rate." );