DOCS-4447: updates profiler for WT changes

- notes that numYield and lockStats are not output for WT databases

Signed-off-by: Allison Moore <[email protected]>

Author: schmalliso

source/reference/database-profiler.txt

@@ -207,7 +207,14 @@ operation.
    data that MongoDB has not yet fully read into memory. This allows
    other operations that have data in memory to complete while MongoDB
    reads in data for the yielding operation. For more information,
-   see :ref:`the FAQ on when operations yield <faq-concurrency-yielding>`.
+   see :ref:`the FAQ on when operations yield
+   <faq-concurrency-yielding>`.
+
+   .. versionchanged:: 2.8.0
+      :data:`system.profile.numYeild` does not apply to databases
+      using the :doc:`WiredTiger </core/storage>` storage engine, and
+      as such, is not included in the profiler output for
+      those databases.
 
 .. data:: system.profile.lockStats
 
@@ -233,6 +240,12 @@ operation.
 
       The time in microseconds the operation spent waiting to acquire a
       specific lock.
+   
+   .. versionchanged:: 2.8.0
+      :data:`system.profile.lockStats` does not apply to databases
+      using the :doc:`WiredTiger </core/storage>` storage engine, and
+      as such, is not included in the profiler output for
+      those databases.
 
 .. data:: system.profile.nreturned