diff --git a/doc/content/tools/profiler.html b/doc/content/tools/profiler.html
index aa7bc57125..8fd3463213 100644
--- a/doc/content/tools/profiler.html
+++ b/doc/content/tools/profiler.html
@@ -5,12 +5,9 @@
Profiling
=========
-Rubinius has both an instrumenting profiler and a sampling profiler. (TODO:
-The sampling profiler has Ruby code left over from shotgun but no VM support
-code yet in the C++ VM.) An instrumenting profiler inserts or uses code around
-every call. Calls can be to regular Ruby methods, Procs, blocks, FFI
-functions, and native C-API functions. A sampling profiler takes a snapshot of
-what method is executing at regular intervals.
+Rubinius has an instrumenting profiler that provides precise timing for all
+methods that are run. The profiler is implemented at the VM level and the data
+is provided for Ruby code to process.
VM Profiler
-----------
diff --git a/lib/rubinius/documentation/site/tools/profiler/index.html b/lib/rubinius/documentation/site/tools/profiler/index.html
index fa840cb244..2521c2e217 100644
--- a/lib/rubinius/documentation/site/tools/profiler/index.html
+++ b/lib/rubinius/documentation/site/tools/profiler/index.html
@@ -10,12 +10,9 @@
Profiling
-
Rubinius has both an instrumenting profiler and a sampling profiler. (TODO:
-The sampling profiler has Ruby code left over from shotgun but no VM support
-code yet in the C++ VM.) An instrumenting profiler inserts or uses code around
-every call. Calls can be to regular Ruby methods, Procs, blocks, FFI
-functions, and native C-API functions. A sampling profiler takes a snapshot of
-what method is executing at regular intervals.
+
Rubinius has an instrumenting profiler that provides precise timing for all
+methods that are run. The profiler is implemented at the VM level and the data
+is provided for Ruby code to process.
VM Profiler